<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.hoenzb
{}
span.EmailStyle19
{font-family:"Arial","sans-serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle22
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Rhetorical question: Why not making the v4 to v6 transition as painless from the protocol design phase? When it was the time that the brains of Internet
(or ARPAnet) realized that it was no longer small play in a few labs/colleges, the protocol should have been redone to make the addressing space extensible. RFC1883 was done in 1995. At that time, the hardware was not fast enough to do 128-bit addressing
lookup, so the only sensible way should have been an extensible numbering/addressing scheme.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">If we had a backwards compatible v6, life would be much different, and on the better side, IMHO.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">yi</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> owner-arin@sprint.net [mailto:owner-arin@sprint.net]
<b>On Behalf Of </b>Matthew Wilder<br>
<b>Sent:</b> Tuesday, April 16, 2013 3:13 PM<br>
<b>To:</b> bjones@vt.edu; John Von Essen<br>
<b>Cc:</b> arin-discuss<br>
<b>Subject:</b> Re: [arin-discuss] IPv6 as justification for IPv4?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">John and Brian,</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">The comparison is laudable, however it doesn’t take into account a few differences which end up having a significant impact on the implementation of the solution.
Hopefully as you read this not as discouraging news but rather realistic challenges and their resulting impacts. Here are what I believe to be the most significant differences:</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"><span style="">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">Y2K was an event which was absolutely certain in timing. IPv4 Address depletion was predicted two decades ago. Yet it only occurred at a global level through
IANA a couple of years ago, and at APNIC then RIPE, but has yet to occur at ARIN, LACNIC and AFRINIC. And then each provider has varying pools, and if some providers are not experiencing subscriber growth, IPv4 depletion isn’t actually something to worry
about. The point is IPv4 exhaust is not as universally necessary and coincidental as Y2K was.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"><span style="">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">Y2K didn’t have significant inter-operability challenges. Each standalone system required patches or perhaps in some cases synchronization was required within
an entity’s system, but at least it was all within their control. In the case of the internet, the end to end ecosystem includes myriad equipment manufacturers (including consumer electronic), OS makers, ISPs, content providers, and so on. No single entity
controls the ecosystem, but it is shared by many, many participants, which means that perfect co-ordination is out of the question, which means transition is necessary. The point here is unlike Y2K, you can’t just go out and fix the problem once and for all.
At minimum there are a few phases you need to plan for.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">In addition, there are a few barriers to IPv6 including familiarity of the staff with IPv4 over IPv6. In the case of Y2K the date format was not changing to a
degree that necessitated serious training for the staff to understand a new format. Additionally the transition phase(s) resulting from point 2 means additional cost for a likely long period of time operating dual-stack in some form. I could go on with other
reasons, but I think these constitute the major differences between Y2K and IPv6.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">Now with the “bad” news behind us, I would back up Lee’s comments of the positive signs of IPv6 deployment. Google statistics show that the industry recently
passed the 1% threshold of traffic over IPv6. This may not seem like a major milestone, but the S curve model, which is used also to represent the spread of a virus in a population increases its slope significantly when a tipping point like this is achieved.
By the end of 2015, Google data predicts 10-14% of internet traffic will be IPv6, and by the end of 2020 it will be 70%. And I am not aware of a major provider that is not ramping up their IPv6 effort.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">Hopefully this message is ultimately encouraging. I am personally excited to think that IPv6 will represent the majority of traffic by the end of the decade.
That’s awesome!</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue">mw</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:blue"> </span></p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> arin-discuss-bounces@arin.net [mailto:arin-discuss-bounces@arin.net]
<b>On Behalf Of </b>Brian Jones<br>
<b>Sent:</b> April 16, 2013 11:31 AM<br>
<b>To:</b> John Von Essen<br>
<b>Cc:</b> arin-discuss<br>
<b>Subject:</b> Re: [arin-discuss] IPv6 as justification for IPv4?</span></p>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Just an observation from your observation...</p>
</div>
<div>
<p class="MsoNormal">If we were sufficiently motivated we could fully implement IPv6 quickly... Thinking back to the Y2K software and hardware upgrades it demonstrates what can be done when it is deemed absolutely necessary...</p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
</p>
<div>
<p class="MsoNormal">--<br>
Brian</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
<div>
<p class="MsoNormal">On Tue, Apr 16, 2013 at 1:32 PM, John Von Essen <<a href="mailto:john@quonix.net" target="_blank">john@quonix.net</a>> wrote:</p>
<p class="MsoNormal">Just for thought....<br>
<br>
Lets say in the future (5 years from now), the entire world has switched over to IPv6 and IPv4 is completely dead in the public space.<br>
<br>
Since v6 space is so huge and abundant, the fees by Arin, Apnic, etc.,. should be almost nothing compared to what they are now since the effort to manage and give it out will be minimal. The blocks are so large, that 99% of Orgs would request one block, and
never ever need to make another request again. So the number of support tickets by Arin for resource requests would be a fraction of what they are now. Not to mention, there wont be as many small multi-homed ISP's applying since getting IP space from upstreams
will no longer be "difficult".<br>
<br>
This means in the future that bodies like Arin will get smaller, with less staff, and a much smaller operating budget.<br>
<br>
Hmmm, maybe this is why IPv4 is still around, and will remain for a very very long time.<br>
<br>
Heck, if we can upgrade every computers OS for Y2K, we can switch the world over to IPv6 and kill v4 once and for all.<span style="color:#888888"><br>
<br>
<span class="hoenzb">-John</span></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
On Apr 16, 2013, at 1:14 PM, Jesse D. Geddis wrote:</p>
<p class="MsoNormal" style="margin-bottom:12.0pt">What's funny is the model some these guys are arguing for is a tax model like:<br>
<br>
We pay 10% until our income is $100,000<br>
<br>
At which point we should pay no more than $10,000 total in taxes/fees on all income past a trillion and into infinity. It doesn't make sense...<br>
<br>
If you're going to make a linear scale keep it linear.<br>
<br>
Jesse Geddis<br>
LA Broadband LLC<br>
<br>
On Apr 16, 2013, at 6:55 AM, "<a href="mailto:rlc@usfamily.net" target="_blank">rlc@usfamily.net</a>" <<a href="mailto:rlc@usfamily.net" target="_blank">rlc@usfamily.net</a>> wrote:</p>
<p class="MsoNormal">If I understand the ARIN revenue "needs" as approximately $8 per class C<br>
correctly, that means we are paying almost 6x more than that (in our particular<br>
case). It would seem that a lot of you on the list don't seem to care that big<br>
ISP's get their IP's at a discounted rate, thus putting the rest of us at a<br>
market disadvantage. I knew exactly where the thread go when I pulled it<br>
(nowhere), but it is amusing to watch the action.<br>
<br>
I did see somewhat of a new bizarre response this time around, though. Someone<br>
actually likened this to getting the rich to "pay their fair share". Perhaps<br>
they didn't notice, but nobody was advocating for a progressive tax. Quite<br>
the contrary, we are talking about a "flat tax" to replace the current heavily<br>
REGRESSIVE tax. Thus, that was one of the most preposterous responses ever.<br>
<br>
I have heard continual whining about lack of IPv6 adoption, while ARIN refuses<br>
to adopt policies to encourage it. Stop the whining, or do something about it.<br>
<br>
In the meantime, the big ISP's will continue to pull the strings.<br>
<br>
_______________________________________________<br>
ARIN-Discuss<br>
You are receiving this message because you are subscribed to<br>
the ARIN Discussion Mailing List (<a href="mailto:ARIN-discuss@arin.net" target="_blank">ARIN-discuss@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</p>
<p class="MsoNormal">_______________________________________________<br>
ARIN-Discuss<br>
You are receiving this message because you are subscribed to<br>
the ARIN Discussion Mailing List (<a href="mailto:ARIN-discuss@arin.net" target="_blank">ARIN-discuss@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</p>
<p class="MsoNormal"><br>
_______________________________________________<br>
ARIN-Discuss<br>
You are receiving this message because you are subscribed to<br>
the ARIN Discussion Mailing List (<a href="mailto:ARIN-discuss@arin.net" target="_blank">ARIN-discuss@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</p>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.<br>
</font>
</body>
</html>