Some advice on IPv6 planning and ARIN request, please

Mon Jul 10 09:33:03 UTC 2017

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2017-07-08 23:00, Radu-Adrian Feurdean wrote:

> On Sat, Jul 8, 2017, at 19:13, Mel Beckman wrote:

>> That open atmosphere was by design. It's why IPv6 uses 128-bit addresses,
> 
> That's for hosts. When you care more about subnets, it's shortened to 64
> bits.

Indeed.  Especielly if you do hierarchical delegation within your
organization, you will often have sparse allocations at several
levels.  A /48 for an organization might seem like reasonably lots
with 65536 subnets, but if that organization in turn delegates to
departments, and they have more than 16 departments, each department
might only get a /56 (256 subnets).  Try to delegate that one step
further, and you can't do any reasonable allocation strategy, but
have to allocate subnet by subnet.

I managed to get a full /52 from our host university, but they
initially wanted to give us only a /56.  Of course, they can only
give out a few /52:s; other departments will have less structured
address plans than us.

- -- 
Thomas Bellman,  National Supercomputer Centre,  Linköping Univ., Sweden
"Life IS pain, highness.  Anyone who tells   !  bellman @ nsc . liu . se
 differently is selling something."          !  Make Love -- Nicht Wahr!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJZY0nPAAoJEGqUdKqa3HTs7GoQAKK0EmX/p/FO+TEIf8d2p1jL
yNM1awpOwa3EyulVhtSFNY/vROrXny5IhY1ikKmWftvDF54629KM1G72ZGtfgsWd
I6is2jUef7ZA5KLjkEd2UUVc2y/PPZ/KDG6aLABFIGPDYMSzXnVLJwTi8HWZrhWw
XoV1IN+xQkp1bAWTVEmWiPyL+y4ee0pfgvJm3GjgHJwFIusJX5+ia6UXcPTZKNFL
tBMNJDx8hq2d28V9oJ7dIIjgWeHgKxpyuMcRNyG1Bn5AJ5rF+mQvllEq4ea+um6z
IkHF4c7Atfi9p4ueY66uAMLuzt2tAkuIKqct8K8KHwDtcKcHHdK03+717V6KBQGS
tLKdAoOUEGEFumUujkE39CJyVMUapY6njX5aObmH4hBm6H1Nk8kZFje0IlEvfMU+
uY5FuEC6VNBWwmHN6g25izsRC+DynA2kA/vlCNsT9eZkQ91KW3HRoFTutGr9qs14
7nGdxVWV6azkFR3gJIHH8epIYqisMiQS5uquJmUBkFLhxfz+6zI5p6QJe+kIakyc
GkyP7oAps8HbT3YcPcRRKhyhVvhx9yWjkP1emXZD7mgENriANFrawIVb5719dsAV
QkYV7SfvDZQJCN7TR3u4se5Zd3XcdmnkQhoVAyjesUDFc1Krbhi8aVkUGv/3Aznu
5GwFW7AH9iuAUVP3XfkV
=HKC1
-----END PGP SIGNATURE-----