<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-AU" link="blue" vlink="purple"><div><p class="MsoNormal" style="margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm;line-height:14.4pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">IPv6 addresses are assigned to organizations in much larger blocks as compared to IPv4 address assignments—the recommended allocation is a</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/48</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">block
 which contains 2<sup>80</sup>addresses, being 2<sup>48</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">or about</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">2.8×10<sup>14</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">times
 larger than the entire IPv4 address space of 2<sup>32</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">addresses and about</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">7.2×10<sup>16</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">times
 larger than the</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/8</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">blocks
 of IPv4 addresses, which are the largest allocations of IPv4 addresses. The total pool, however, is sufficient for the foreseeable future, because there are 2<sup>128</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">or
 about</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">3.4×10<sup>38</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(340</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><a href="http://en.wikipedia.org/wiki/10%5E12" title="10^12" target="_blank"><span style="color:#0b0080">trillion</span></a></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">trillion
 trillion) unique IPv6 addresses.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm;line-height:14.4pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Each RIR can divide each of its multiple</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/23</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">blocks
 into 512</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/32</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">blocks,
 typically one for each ISP; an ISP can divide its</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/32</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">block
 into</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">65536</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/48</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">blocks,
 typically one for each customer;<sup><a href="http://en.wikipedia.org/wiki/IPv6_address#cite_note-16" target="_blank"><span style="color:#0b0080">[16]</span></a></sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">customers
 can create</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">65536</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/64</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">networks
 from their assigned</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Courier New"">/48</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">block,
 each having 2<sup>64</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">addresses. In contrast, the entire IPv4 address space has only 2<sup>32</sup></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(about4.3×10<sup>9</sup>)
 addresses.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm;line-height:14.4pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">By design, only a very small fraction of the address space will actually be used. The large address space ensures that addresses are almost always available, which makes the use of</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><a href="http://en.wikipedia.org/wiki/Network_address_translation" title="Network address translation" target="_blank"><span style="color:#0b0080">network
 address translation</span></a></span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(NAT) for the purposes of address conservation completely unnecessary. NAT has
 been increasingly used for IPv4 networks to help alleviate</span><span style="font-family:"Arial","sans-serif""> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><a href="http://en.wikipedia.org/wiki/IPv4_address_exhaustion" title="IPv4 address exhaustion" target="_blank"><span style="color:#0b0080">IPv4
 address exhaustion</span></a>.</span></p></div></div></blockquote><div><br></div><div>However many trillion, quadrillion or quintillion ip addresses are possible with IPv6 there will always be a shortage at some point...</div>
<div>Any technological renewal wave will show that to be true, so we _will_ run out of IPv6...</div><div>Maybe we'll want to assign each gene an ip address as will as its associated body cell... hahaha</div><div> </div>
</div>-- <br>Best regards.<div>Gus</div>