<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>I thought this excerpt from
the ISOC member newsletter of March might be of interest.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><st1:City w:st="on"><st1:place
w:st="on"><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Pierre</span></font></st1:place></st1:City><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>2. Features<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>IETF 71 Samples the
IPv6-only Internet<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>- Contributed by Leslie
Daigle<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>In mid-March, the IETF put a
spotlight on the next generation of Internet addressing by switching off
attendees' access to IPv4 during its Wednesday plenary meeting. For an hour,
Internet engineers at the meeting could only access the Internet using an IPv6
network; their machines had to connect to the network using IPv6, and they
could only reach other IPv6 Internet sites. By choosing not to provide
IPv4/IPv6 protocol translation (NAT-PT), this event was targeted a little
differently than similar ones at NANOG and APRICOT meetings earlier in the
year. Stepping beyond questions of transition, the intent was to provide engineers
with some first-hand experience in working with IPv6 in the wild.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>The network managers for
these events are well-versed in providing IPv6 connectivity, so it was clear
from the outset that providing IPv6 would not be the challenge. Russ Housley, Chair
of the IETF, announced the planned "IPv4 outage" in December, giving
prospective attendees plenty of time to prepare. The subsequent discussion on
the IETF's general discussion mailing list highlighted that the biggest hurdle
would be user reluctance. In many ways, this mirrors the state of IPv6
diffusion in the world today.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Nevertheless, the
announcement clearly motivated several IETF attendees to prepare for the event.
Several made sure that their home networks and Internet resources were
IPv6-capable in time for the event. The big news of the day was Google's
announcement, at the IETF meeting, of an IPv6-accessible site for their search
engine (<a href="http://ipv6.google.com/">http://ipv6.google.com</a>). <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>This drew a round of
appreciative applause from the plenary attendees.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>At its peak, about 190
computers were connected to the IPv6-only network during the IETF plenary
IPv6-only hour, reaching out to a combined total of some 750 different global
IPv6 addresses. The biggest hurdle was known in advance of the plenary
meeting: Windows XP does not support DNS resolution over IPv6. But persistence
and a quick fix to BIND software allowed a work around for the intent Windows
XP users!<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Relatively few glitches were
reported, though there were some challenges with global routing. This is not
surprising, given that IPv6 deployment is still only as diffused as the very
early days of the Internet.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>No single one of these IPv6
events is going to cause an instant increase in the amount of IPv6 activity on
the Internet. However, they are breaking down the barriers of fear,
uncertainty, and doubt, allowing core Internet engineers and operators to
discuss "how" to deploy IPv6, not "if" IPv6 is deployable.
For the IETF, the value of this event will be seen in on-going working group
meetings, as more participants have their own first-hand IPv6 usage experience
to draw on.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Information about the IETF
71 IPv6 event, including notes of lessons learned and pointers to related materials,
are available at:<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'> <a
href="http://wiki.tools.isoc.org/IETF71_IPv4_Outage">http://wiki.tools.isoc.org/IETF71_IPv4_Outage</a></span></font><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p>
</div>
</body>
</html>