Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

9 module online course

Start now!
back to overview

IPv6 Resources on

As expected, ARIN wasn’t that far behind APNIC and RIPE in IPv4 allocations and is now down to the last /8. Maybe it’s time for the last denialists to wake up and start considering IPv6 (or not – consultants love panicking customers)… and the new IPv6 resources page on might help you get IPv6-fluent (hint: don’t miss the must-read documents section).

Please read our Blog Commenting Policy before writing a comment.


  1. I have a question as to why /64 is the boundary for VLSM that breaks critical functions such as RA, ND, SEND etc. For a home network, a /48 is a RIDICULOUS amount of addresses to have at your disposal. Why can I not make a couple of /120 networks in ULA space, have DHCP servers that can work with /120, and then get a PD DHCP from my carrier and let it autoconfig the GUA space for my hosts?

    It doesn't make much sense to me.

    1. The /64 boundary has special meaning only for SLAAC, everything else works on any subnet mask.

      As for /48 being ridiculous and a few other things, I totally agree with you, but the arguments have turned into religion years ago - just join any major IPv6 mailing list (v6ops comes to mind) and enjoy the show.


Constructive courteous comments are most welcome. Anonymous trolling will be removed with prejudice.