| To: | davem@xxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Tue, 03 Aug 2004 01:19:12 -0700 (PDT) |
| Cc: | herbert@xxxxxxxxxxxxxxxxxxx, kazunori@xxxxxxxxxxxx, netdev@xxxxxxxxxxx, usagi-core@xxxxxxxxxxxxxx, kuznet@xxxxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx |
| In-reply-to: | <20040802190914.303ccfbe.davem@redhat.com> |
| Organization: | USAGI Project |
| References: | <20040730171205.114f22ba.kazunori@miyazawa.org> <20040802074147.GA16381@gondor.apana.org.au> <20040802190914.303ccfbe.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <20040802190914.303ccfbe.davem@xxxxxxxxxx> (at Mon, 2 Aug 2004
19:09:14 -0700), "David S. Miller" <davem@xxxxxxxxxx> says:
> An intesting solution would be to use stacked destinations, which
> do no actual encapsulation (or perhaps do the routing header work)
> and merely represent the hop-by-hop path. Then the PMTU propagation
> machinery can be used, and route lookups will go through a slower path
> to find these special stacked hop-by-hop routes.
Well, I think it would probably be another rt6_info{} member
rt6i_srcrt (or something like that).
--yoshfuji
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: iproute2 and kernel headers, YOSHIFUJI Hideaki / 吉藤英明 |
|---|---|
| Next by Date: | Re: [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup, YOSHIFUJI Hideaki / 吉藤英明 |
| Previous by Thread: | Re: [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup, David S. Miller |
| Next by Thread: | Re: [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |