[129256] in North American Network Operators' Group
Re: Comcast enables 6to4 relays
daemon@ATHENA.MIT.EDU (Mitchell Warden)
Tue Aug 31 02:22:26 2010
To: "Graham Beneke" <graham@apolix.co.za>, nanog@nanog.org
From: "Mitchell Warden" <wardenm@wardenm.net>
In-Reply-To: 4C7C8D4D.5090107@apolix.co.za
Date: Tue, 31 Aug 2010 16:22:03 +1000
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
=20
> The list seems to be showing relays that announce both the IPv4 and th=
e=20
> IPv6 anycast prefixes.
>=20
> I have noticed a number of deployments that announce the (in)famous IP=
v4=20
> prefix and then consider their deployment complete. I suspect that the=
re=20
> is a lack of 2002::/16 announcements and this would be contributing to=
=20
> the regular problems with return paths.
>=20
> Obviously the IPv6 content networks benefit the most from having a rel=
ay=20
> translating back to IPv4.
>=20
> Anyone have experience with this=3F
>=20
> --=20
> Graham Beneke
>=20
>=20
Is there a reason not to advertise more specific prefixes from 2002::/16=
to ensure that traffic for your v4 routes comes back to your own 6to4 r=
outer=3F
If for example all my users have v4 addresses in 192.0.2.0/24, I could a=
dvertise 2002:C002:0000::/40 instead of or in addition to the full 2002:=
:/16.
Cheers.
Mitchell
