<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>Ah, I get it now. So basically in other words if I
want to setup a 6to4 relay either I have</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>to make it private, in which case I will definitely only be
de-encapsulating 6to4 traffic that is originating</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>from my network, or make it public, in which case I will
still definitely only be de-encapsulating</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>6to4 traffic that is originating from my network, but there
is only a small increased chance that I will</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>be re-encapsulating </FONT></SPAN><SPAN
class=708510122-14052009><FONT face=Arial color=#0000ff size=2>incoming traffic
to my network and forwarding it to customers, since it is</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>completely up to how far my IPv6 advertisement is
propagated, but almost certainly I will be</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>de-encapsulating traffic for a whole lot of other
networks.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>Am I correct in assuming this is a severe disincentive to
putting up IPv6 public relays? ;-)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>I guess that is why RFC3964 was written. Looks like
the Linksys code is a dud, then.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2>Ted</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=708510122-14052009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><FONT face=Arial color=#0000ff
size=2></FONT><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
ipv6-ops-bounces+tedm=ipinc.net@lists.cluenet.de
[mailto:ipv6-ops-bounces+tedm=ipinc.net@lists.cluenet.de] <B>On Behalf Of
</B>Steve Wilcox<BR><B>Sent:</B> Thursday, May 14, 2009 2:49 PM<BR><B>To:</B>
Ted Mittelstaedt<BR><B>Cc:</B> ipv6-ops@lists.cluenet.de<BR><B>Subject:</B>
Re: Question about 6to4<BR></FONT><BR></DIV>
<DIV></DIV>Hey Ted,<BR> you sort of answered your own question - the
aggregate is announced as an anycast and the v6 routing table doesn't know
where the individual v6 packets are destined.<BR><BR>So the v6 packets find
their way to the nearest 6to4 relay, that then converts to v4 and its routed
out as v4. As you say HE is one major sink for that, as a result of them being
so well connected.<BR><BR>Thats one of the downsides with 6to4 - the packet
may go in the wrong direction in v6 before passing through the relay and then
heading in the opposite direction to find the v4
endpoint.<BR><BR>Steve<BR><BR><BR>
<DIV class=gmail_quote>On Thu, May 14, 2009 at 10:32 PM, Ted Mittelstaedt
<SPAN dir=ltr><<A
href="mailto:tedm@ipinc.net">tedm@ipinc.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Hi
All,<BR><BR> I apologize in advance if this has been asked before a
million times but<BR>I have what is probably a stupid question about
6to4.<BR><BR> We are in process of connecting to native IPv6, I am
currently getting<BR>the IPv6 BGP table from our upstream.<BR><BR> I
see that Linksys is supporting IPv6 out-of-the-box in some of
it's<BR>routers, via 6to4<BR><BR> I figured this might be useful for
some of our customers, to setup<BR>a 6to4 relay router for these Linksys
devices to use. I have found plenty<BR>of info on the Internet to
setup a router as a 6to4 relay.<BR><BR> My question concerns how
exactly 6to4 -works-<BR><BR> My understanding is that RFC3068 defines
2002:c058:6301:: as the<BR>anycast for the (in this case) customer router to
find the 6to4 relay I<BR>create. And that a 6to4 relay then uses a
manufactured 2002:: IPv6<BR>address formed by using it's IPv4 address with
the 2002:: prefix, and<BR>that any 6to4 routers tunneled into it are using
their manufactured<BR>2002:xxxx:: addresses.<BR><BR> So, if this is the
case then wouldn't every 6to4 relay that's advertising<BR>on the Intenet be
present in the IPv6 BGP table?<BR><BR> In looking at the various IPv6
looking glasses on the Internet, I see<BR>a handful of 2002:: routes out
there.<BR><BR> But there seems to be no consistency anywhere.
Most of the looking<BR>glasses<BR>seem to show Hurricaine Electric's
2002:: advertisement, including my<BR>own table.<BR><BR> But beyond
that, the advertisements for other relays seem to exist in<BR>one router,
but not in others.<BR><BR> Advertisements for native routes do seem to
be consistent.<BR><BR> How exactly do routers know where to forward
IPv6 packets destined for<BR>a given 6to4 2002:: address if there is
no route in their table? And if<BR>they are just sending 6to4 traffic
to HE then how does HE know what to<BR>do with it if it's not for their
network?<BR><BR>Thanks,<BR><FONT
color=#888888>Ted<BR><BR><BR></FONT></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>Network Operations - Standards & Design<BR>Google
Inc.<BR>E: <A
href="mailto:stevewilcox@google.com">stevewilcox@google.com</A><BR>M: +44 7920
041930<BR></BLOCKQUOTE></BODY></HTML>