[arin-ppml] Draft Policy ARIN-2013-3: Tiny IPv6 Allocations for ISPs

[Seth Mattinen]

On 3/27/13 6:48 PM, David Farmer wrote:
> On 3/27/13 20:36 , Seth Mattinen wrote:
> 
>> One really nice thing about the IPv6 /32 /48 /56 /64 system is no arcane
>> math exercises. But who really needs simplicity.
> 
> If you said /32 /48 /64, I'd agree.  However, /56 isn't on a (16 bit)
> boundary, its on a byte (8 bit) boundary, but so is /40 for that matter.
>  However, overall our IPv6 policy is aligned on nibble (4 bit)
> boundaries, and /36 is aligned on a nibble boundary.  For what its
> worth, given the Hex representation used in IPv6 the math shouldn't be
> that hard if you stay on nibble boundaries.
> 


I included /56 because if I'd said /32 /48 /64 someone would have told
me about /56 as a midway point between /64 and /48 for home users that
need more than one subnet. I personally stick to the /32 /48 /64 system.

~Seth