<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" 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)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: [arin-ppml] The non-deployment of IPv6</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:NewCenturySchlbk;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
h1
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:14.0pt;
font-family:NewCenturySchlbk;
font-weight:bold;}
h2
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:12.0pt;
font-family:NewCenturySchlbk;
font-weight:normal;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.SPCI-503Report, li.SPCI-503Report, div.SPCI-503Report
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level1 lfo1;
font-size:14.0pt;
font-family:NewCenturySchlbk;
font-weight:bold;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:888152470;
mso-list-type:hybrid;
mso-list-template-ids:1337115686 -1630604664 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-style-link:"SPCI-503 Report";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1583182679;
mso-list-type:hybrid;
mso-list-template-ids:-1614647274 -1520770074 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:6000;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Arial;
mso-fareast-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>It is interesting that we are now finally
worried about the root causes of the v6 “non-deployment”. Some
of us have been worrying this for years…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>To me it comes down to a few points:<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><span style='mso-list:Ignore'>-<font size=1 face="Times New Roman"><span
style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font size=2 color=navy
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>Cost of
conversion! We need a truly seamless v4 to v6 interface to reduce
implementation costs and risks. As it is, every year that goes by without
v6 implementation increases its implementation cost and conversion risks; thus adding
more resistance every year to conversion.<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in'><font size=2 color=navy
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><span style='mso-list:Ignore'>-<font size=1 face="Times New Roman"><span
style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font size=2 color=navy
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>We need
to get IPv6 addresses in the hands of the developers; especially the small greenfields.
Perhaps our past address allocation policies just might have something to do
with the problem. In the mid 80’s to early 90’s, an email
request with almost zero justification would get 50 or 100 class Cs or a class
B without regards to the size of the entity or what industry it was part of.
Are we still too restrictive for the greenfields and new technology developers?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><span style='mso-list:Ignore'>-<font size=1 face="Times New Roman"><span
style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font size=2 color=navy
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>The
vendors all need to show, advertise, and evangelize that their v6 products coexist
harmlessly with existing v4 infrastructures so that a network owning
organization (agency, enterprise, etc) will see no risk in adding v6 support to
their networks.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><span style='mso-list:Ignore'>-<font size=1 face="Times New Roman"><span
style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font size=2 color=navy
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>New
products and new product versions need to support both v4 and v6 seamlessly. A
few folks have the right idea but not enough.<o:p></o:p></span></font></p>
<div>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Take care</span></font><font color=navy><span
style='color:navy'> <br>
</span></font><font size=2 color=navy face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:navy'>Terry</span></font><font color=navy><span
style='color:navy'> </span></font><o:p></o:p></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
arin-ppml-bounces@arin.net [mailto:arin-ppml-bounces@arin.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Durand, Alain<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, December 08, 2009
11:29 AM<br>
<b><span style='font-weight:bold'>To:</span></b> matthew@matthew.at; Ted
Mittelstaedt<br>
<b><span style='font-weight:bold'>Cc:</span></b> arin ppml<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [arin-ppml] The
non-deployment of IPv6</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Calibri><span
style='font-size:11.0pt;font-family:Calibri'>On 12/8/09 2:01 PM, "Matthew
Kaufman" <<a href="matthew@matthew.at">matthew@matthew.at</a>>
wrote:</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt;
font-family:Calibri'>Ted Mittelstaedt wrote:<br>
><br>
> I agree that content providers NEED to be dual-stacked first,...<br>
And where will they be getting the IPv4 for that side of
"dual-stacked"<br>
from after runout?<br>
<br>
===> This is where a technology like dual-stack lite comes to play. See<br>
<a href="http://www.ietf.org/id/draft-ietf-softwire-dual-stack-lite-02.txt">http://www.ietf.org/id/draft-ietf-softwire-dual-stack-lite-02.txt</a><br>
<br>
And if that's via a mechanism that actually works well enough, then why<br>
would we need IPv6?<br>
<br>
===> Because a packet that flows natively over IPv6 is a packet that does
not have to go through the IPv4 NAT infrastructure.<br>
In other words, the more v6 traffic, the less we spend on NATs.<br>
<br>
- Alain.</span></font><o:p></o:p></p>
</div>
</div>
</body>
</html>