[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00658) Re: new suggestion for mobile node implementation
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 00658) Re: new suggestion for mobile node implementation
- From: itojun@xxxxxxxxxx
- Date: Thu, 02 Aug 2001 16:03:22 +0900
- Cc: mipl@xxxxxxxxxxxxxxxxxxxxxxxxx, takamiya@xxxxxxxxxxxxx
- In-reply-to: takamiya's message of Thu, 02 Aug 2001 13:31:56 +0900. <20010802133156J.takamiya@po.ntts.co.jp>
- List-subscribe: <mailto:usagi-users-ctl@linux-ipv6.org?body=subscribe>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Sender: itojun@xxxxxxxxxx
> This is Takamiya, a core member of USAGI.
> We are thinking about introducing new virtual device for Mobile
> Node in Mobile IPv6.
Bump-in-the wire mobile-ip6 implementation? there are multiple
problem with it. I don't recommend this approach.
1. how many types of L2 can you support with this approach?
2. MTU issues. TCP segment size computation should consider
mobile-ip6 extension headers, and with bump-in-the-wire
approach this is not possible.
3. scope zones. If you have a MIPv6 virtual device, the scope zone
gets different from the other interfaces. If you throw a packet
to ff02::1%mip6, what will happen?
4. You also need to duplicate L3 fragmentation code, into mip6 virtual
device code, as well as IPv6 output logic.
itojun