<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Scott,<div><br></div><div>Let's put the true numbers in a little bit of perspective...</div><div><br></div><div>First, when 4.2 billion addresses seemed like a lot, it was because the internet was not anticipated to be something everyone would use every day. It was expected to be a research community project used by a much smaller research community and if that had continued to be the case, 4.2 billion addresses would still seem like a lot.</div><div><br></div><div>Compared to 6,8 Billion people, however, 4.2 billion addresses (actually more like 3.2 billion unicast addresses) doesn't seem like much at all.</div><div><br></div><div>On the other hand... Consider that there are approximately 30,000 ISPs world-wide.</div><div><br></div><div>If we were to give every single ISP a pair of /28s (that's 32 of the current /32 allocations) in each of the 5 regions (AfriNIC, APNIC, ARIN, LACNIC, RIPE), we would still only consume the majority of the current single /12 allocated to each RIR. There would still be 506 /12s left in the current /3.</div><div><br></div><div>There were some very good reasons to give out IPv4 addresses like candy, and, having done so is one of the major contributing factors to the success and broad deployment of the internet. Is it remotely possible that in 50 or 60 years, we will still be using IPv6 addressing and that current liberal allocation efforts could prove to be unwise for that future? Actually, yes, it is possible.</div><div><br></div><div>However, I propose that we approach that logically.</div><div><br></div><div>For the time being, liberal allocation seems to have little consequence and provide the best opportunities for improving the user experience and the scalability of the network.</div><div><br></div><div>As such, let's go ahead and be liberal in our allocations and assignments. Give each end site no less than a /48 (even a residential customer). Let's try this experiment until we</div><div>have used up 20 /12s. If we get to the point where we have used 20 of the first 512 /12s in less than 30 years, then, we have plenty of time after that point to develop different</div><div>allocation policy for the remaining 492 /12s before we exhaust the first 1/8th of the address space.</div><div><br></div><div>OK?</div><div><br></div><div>Owen</div><div><br><div><div>On Sep 13, 2010, at 10:46 AM, Scott Morris wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">
There really isn't a great repository for things, at least that I've
seen... But keep in mind that the binary works the same in IPv6 as
it does in IPv4. :)<br>
<br>
So when you look at a /21, do you look at it as 2000'ish IPv4
addresses? (At which point a single /64 is more than enough)<br>
Or do you look at it as 8 x /24 networks (at which point a /61 is
the technical equivalent)<br>
<br>
/64 is used by many people as the de facto "network" addressing for
any subnet because of all the magical EUI-64 addressing to work
(e.g. less whiny customer calls = better). But anyone doing DHCPv6
will quickly learn that a /64 is a SERIOUS amount of addresses than
can be broken down internally to any variation they really feel
like. (/126 = /30, etc.)<br>
<br>
So to best answer that questions, you have to know a little about
your customer and how they'll use the addresses. /56 seems to be
the way many folks are going with things, but that's 256 /64
networks or the veritable "boatload" of addresses that will be
wasted beyond belief.<br>
<br>
Remember in the old days everyone gave out IPv4 addresses like
candy. Back then 4.2 billion addresses seemed like a lot... Today,
340 undecillion addresses seems like a lot... Times change though!<br>
<div class="moz-signature">
<style type="text/css">p.p1 { margin: 0px; font: 12px Helvetica; min-height: 14px; }p.p2 { margin: 0px; font: 12px Helvetica; }p.p3 { margin: 0px; font: 12px Helvetica; color: rgb(4, 255, 191); }p.p4 { margin: 0px; font: 12px Helvetica; color: rgb(11, 4, 255); }</style><div><span class="Apple-converted-space"> </span><br class="webkit-block-placeholder"></div><p class="p1"><br>
</p><p class="p2"><b>Scott Morris</b>, CCIE<i>x4</i>
(R&S/ISP-Dial/Security/Service Provider) #4713,</p><p class="p2">CCDE #2009::D, JNCIE-M #153, JNCIS-ER, CISSP, et al.</p><p class="p2">CCSI #21903, JNCI-M, JNCI-ER</p><p class="p3"><a class="moz-txt-link-abbreviated" href="mailto:swm@emanon.com">swm@emanon.com</a></p><p class="p1"><br>
</p><p class="p4">Knowledge is power.</p><p class="p4">Power corrupts.</p><p class="p4">Study hard and be Eeeeviiiil......</p>
</div>
<br>
On 9/13/10 1:24 PM, Schnell, Darryl wrote:
<blockquote cite="mid:C31D7F2AE868E84895D378A5B9E42340E40A4FAE74@EXCHANGE2K7.corp.ptd.net" type="cite">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 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:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1"><p class="MsoNormal">Can anyone recommend a good IPV6 website
for Beginners? I’ve
read about eight web sites which say the same things and I
feel like my head is
going to explode. I guess the problem I’m having is trying to
understand
how an IPv4 CIDR notation translates in an IPv6 CIDR in order
to fill out ARIN
IPV6 Allocation Template future usage section. My actual
question is –<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">If I assigned a customer say an IPV4 /21 in
IPV6 this would
translate into a /56? If I’m not mistaken a /56 would
translate into something
like 65,000 host addresses? That just seems like a lot of
hosts to me,
especially when most of the time I’m working with networks
that are /26
or smaller. I guess my big problem is confusion over labeling.
What would be
the equivalent of a /26, /27, /28 or have we done away with
blocks that small
and simply would just assign a /56 instead?<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Does any of the gibberish I wrote make any
sense at all?<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Any help anyone can offer is much
appreciated.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">D -<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
</div>
_______________________________________________<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">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">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>Please contact info@arin.net if you experience any issues.</blockquote></div><br></div></body></html>