This was mentioned in the NGtrans meeting in Pittsburgh,
and no such an anycast address doesn't currently exist.
What would be needed would be to get a prefix short
enough to pass the prefix length filters in the Internet,
and then just use 1 of the addresses in that large prefix.
(Some would argue that having packets take the scenic
route as you describe is desirable, however.)
-Dave
> -----Original Message-----
> From: Brad Huntting [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 27, 2000 2:46 PM
> To: f.johan.beisser
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
>
>
>
> > http://www.kfu.com/~nsayer/6to4/
>
> Actually this web page brings up another issue that a freind and
> I were discussing just yesterday. Anyone who's actually tried to
> use 6to4 (2002::/16) has probably noticed that they need a default
> route to reach the 6bone. But even assuming you actually find such
> a router it is almost always on the far side of the Internet; which
> means that your packets get to take the scenic route on their way
> to the 6bone.
>
> One simple solution to this would seem to be to use a well known
> IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> gateways.
>
> In this way, anyone using 6to4 could reliably use 2002:(a.b.c.d)::1
> (actual IPv6 address syntax will vary) as a default route to the
> 6bone.
>
> 6to4 gateways would advertise to the their IPv4 peers that they
> have a route for "a.b.c.d". And for their IPv6 peers (the 6bone)
> they can advertise a route for 2002::/16.
>
> Does anyone see a problem with this? I dont suppose there's already
> a block of IPv4 address space set aside for anycast?
>
>
> brad
