[108748] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IPv6 Wow

daemon@ATHENA.MIT.EDU (Alain Durand)
Thu Oct 23 18:46:28 2008

Date: Thu, 23 Oct 2008 18:46:05 -0400
From: Alain Durand <alain_durand@cable.comcast.com>
To: <alh-ietf@tndh.net>, Nathan Ward <nanog@daork.net>,
	Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <027a01c93560$3e5c2ad0$bb148070$@net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org




On 10/23/08 6:39 PM, "Tony Hain" <alh-ietf@tndh.net> wrote:

>  A properly
> implemented client will do the longest prefix match against that set, so a
> 6to4 client will go directly to the content provider's 6to4 router, while a
> native client will take the direct path.

Not quite.
Say the server has native IPv6 address 2001::1 and 6to4 IPv6 2002::X.
Say the client has native IPv6 address 2003::1 and 6to4 IPv6 2002::Y.
Longest prefix match will choose 6to4 over native IPv6. Not good.

  - Alain.




home help back first fref pref prev next nref lref last post