<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16766"></HEAD>
<BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px"
id=MailContainerBody leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT face=Calibri>Comments in italic below.</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>-Ahmed</FONT></DIV>
<DIV style="FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A
title="mailto:B.Candler@pobox.com CTRL + Click to follow link"
href="mailto:B.Candler@pobox.com">Brian Candler</A> </DIV>
<DIV><B>Sent:</B> Wednesday, June 08, 2011 5:53 PM</DIV>
<DIV><B>To:</B> <A title=ahmed@tamkien.com href="mailto:ahmed@tamkien.com">Ahmed
Abu-Abed</A> </DIV>
<DIV><B>Cc:</B> <A title=menog@menog.net
href="mailto:'menog@menog. net'">'menog@menog. net'</A> ; <A
title="mailto:IPv6Jordan@ipv6forum.com CTRL + Click to follow link"
href="mailto:IPv6Jordan@ipv6forum.com">IPv6jordan</A> </DIV>
<DIV><B>Subject:</B> Re: [menog] Rapid IPv6 deployment for World IPv6
Day</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV>On Wed, Jun 08, 2011 at 12:56:39PM +0300, Ahmed Abu-Abed
wrote:<BR>> World IPv6 Day ends at 3am KSA/Jordan time June
9th.<BR>> <BR>> To setup a computer with IPv6 public
address over any IPv4 connection<BR>> (3G, ADSL, dial-up,
etc. and even behind nested NATs) for World IPv6<BR>> Day
testing then I suggest downloading the Freenet6 client and
running<BR>> it with default settings. Then use it to
access Google, Youtube,<BR>> Facebook, CNN, etc. or ping
their sites.<BR><BR>This is arguably missing the point of IPv6 day.</DIV><FONT
face=Calibri></FONT><FONT face=Calibri></FONT>
<DIV><FONT face=Calibri></FONT><FONT face=Calibri></FONT><FONT
face=Calibri></FONT><BR>If you want to play with a v6 tunnel client, you can do
this any day. You<BR>simply point your browser at <A
title="http://ipv6.google.com/ CTRL + Click to follow link"
href="http://ipv6.google.com/">http://ipv6.google.com/</A> or<BR><A
title="http://www.v6.facebook.com/ CTRL + Click to follow link"
href="http://www.v6.facebook.com/">http://www.v6.facebook.com/</A> to see if it
works.<BR></DIV>
<DIV><FONT face=Calibri><EM>>> The purpose of World IPv6 Day
(W6D) was for everyone to participate and test the behavior of standard web
portal URLs on both IPv4 and IPv6 connections. 99% of
internet users do not have access to native dual stack connections, hence
tunneling to IPv6 servers is the only solution for users to access the websites
over a v6 connection.</EM></FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV>However, the Internet migration strategy is dual-stack. There will never
be<BR>any requirement for users to install tunnel clients on their
machines.<BR></DIV>
<DIV><FONT face=Calibri><EM>>> Until the whole internet AND web
content AND networks AND applications move to IPv6 ONLY then there
will be a need for tunneling. Dual-stacking is needed but it doesn't solve the
IPv4 depletion issue, and multi-level NATing (CGN and LSN, etc) creates its own
set of problems. Forward tunneling, IPv6-in-IPv4 is in use now for rapid IPv6
access, while reverse tunneling IPv4-in-IPv6 will be needed in the future
when networks IPv6-only with legacy IPv4 content.</EM></FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><EM><FONT face=Calibri></FONT></EM><EM><FONT
face=Calibri></FONT></EM><EM><FONT face=Calibri></FONT></EM><BR>The fundamental
reason for v6 day is to encourage *content providers* to<BR>enable both v4 and
v6 concurrently on their *well-known* URL (i.e. return<BR>both AAAA and A
records), and then see how many of their (non-v6) users are<BR>broken by doing
this. That would be users whose local v6 stack is broken,<BR>or who are on
a network which announces v6 connectivity when it doesn't<BR>actually have
it.<BR></DIV>
<DIV><FONT face=Calibri><EM>>> See my first comment
above.</EM></FONT></DIV>
<DIV><FONT face=Calibri></FONT><FONT face=Calibri></FONT><FONT
face=Calibri></FONT><FONT face=Calibri></FONT><BR>So, this is what's different
for v6 day:<BR><BR>$ dig <A href="http://www.google.com">www.google.com</A>
aaaa<BR>...<BR>;; ANSWER SECTION:<BR><A
href="http://www.google.com">www.google.com</A>. 86094 IN CNAME <A
href="http://www.l.google.com">www.l.google.com</A>.<BR><A
href="http://www.l.google.com">www.l.google.com</A>. 218 IN AAAA
2a00:1450:400c:c01::93<BR><BR>Previously, you'd have got an empty response (and
the client would then<BR>look for an A record instead).<BR><BR>The hope is that
this will give confidence to those websites to run both v4<BR>and v6 permanently
on their main URL.<BR><BR>Regards,<BR><BR>Brian.</DIV></BODY></HTML>