<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I understand the vastness of the IPv6 address space, and to be fair,
the same words were likely uttered a couple decades ago with IPv4,
but in any case I was more just hoping to learn an answer beyond
'Just Because'.<br>
<br>
A couple I've found while googling, and one of the responses
on-list:<br>
<br>
1) (and probably most importantly) a lot of IPv6 features rely on
a subnet size of /64 (SLAAC given as the example)<br>
2) Route summarisation i.e. if we had trillions of /96's or
smaller to learn in a full table (and given an IPv6 route takes up
something like 4x the space), these are quite large routing tables.<br>
<br>
It's mind boggling to think, how many /64's I can essentially hand
out with my single allocation of /32. If I'm not mistaken, there are
as many /64's in a /32, as there is IPv4 address' available in
total?!<br>
<br>
<div class="moz-cite-prefix">On 02/07/14 22:21, Matthew Scutter
wrote:<br>
</div>
<blockquote
cite="mid:CALubygT11u+Ss0L7i65HYAUtup=ffqjBDiUW8uPAcBQSh4B=Vg@mail.gmail.com"
type="cite">
<div dir="ltr"><a moz-do-not-send="true"
href="http://www.wolframalpha.com/input/?i=2%5E64+%2F+population+of+earth">http://www.wolframalpha.com/input/?i=2%5E64+%2F+population+of+earth</a><br>
<div>We'll be fine for the foreseeable future, and probably a
while beyond it.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jul 2, 2014 at 9:31 PM, Joseph
Goldman <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:joe@apcs.com.au" target="_blank">joe@apcs.com.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mark,<br>
<br>
Going a bit off-topic, towards IPv6 in general as I'm still
catching up on the standards of use for IPv6, but I am yet
to understand the reason for recommendations to give such
large blocks to customers?<br>
<br>
You talk about a /64 being handed out to customers, even
this I found exceptionally large for a home, which even with
smart devices becoming the norm would you say its likely to
reach 100 needed IP's? let alone thousands?<br>
<br>
You go on to say other RFC's are even trying to recommend
/56's, or even /48 to be better by your own personal
opinion. Why so large? Why not /96's or even smaller?<br>
<br>
I'm in no way knocking the idea, I am genuinely curious as
to the reasons behind the recommendations.<br>
<br>
Thanks in advance!<br>
Joe
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 02/07/14 21:14, Mark ZZZ Smith wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
The following recently published RFC might be of
interest to people on this list.<br>
<br>
RFC7278 - "Extending an IPv6 /64 Prefix from a Third
Generation Partnership Project (3GPP) Mobile Interface
to a LAN Link"<br>
<br>
<a moz-do-not-send="true"
href="http://tools.ietf.org/html/rfc7278"
target="_blank">http://tools.ietf.org/html/rfc7278</a><br>
<br>
Earlier versions of the 3GPP standards (i.e.,
basically mobile phone data standards) didn't
recognise or realise that smartphones would also be
able to temporarily become IP routers/Wifi hotspots,
and therefore didn't specify DHCPv6-PD. This RFC
describes how to take a /64 from the phone to carrier
link and use it/share it with the phone's Wifi LAN
interface when the phone is acting as an IPv6 router.
It may seem a bit obscure, however it provides some
examples of how IPv6's capabilities can be used to
novelly overcome this limitation. It certainly isn't a
recommendation to give a customer a single /64 rather
than many of them (i.e., as per RFC6177, a /56, or
better IMO, a /48 as per the considerations in
RFC3177), but it does show how that can be worked
around with some limitations.<br>
<br>
Regards,<br>
Mark.<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net"
target="_blank">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>