Re: [sig-policy] [Sig-policy-chair] prop-099 IPv6 Reservation for Large
Hash: SHA1
Hi Sanjaya.
Thanks.
On 8/22/11 5:48 AM, Sanjaya wrote:
> Hi Gaurab and all,
>
> The binary chop algorithm that APNIC Secretariat use to allocate
> IPv6 does not specifically reserve space. The algorithm simply
> maximizes the "distance" between neighbouring allocations. As more
> space gets allocated, this distance will be reduced and
> fragmentation could occur. But we could ask for more space from
> IANA when that time comes.
>
I think it would make sense to make this aspect more prominent
somewhere on the website, or as part of the communications that is
sent to people applying for IPv6. May be Prof. Li can highlight if
this covers some of his concerns.
>
> Pool block Reservation Maximum number size size limit of
> accounts /13 /28 32,768 /13 /24
> 2,048 /13 /20 128 /13 /16 8
This is a good plan. We could always debate on the limit but I think
your limits are fine. Deciding who falls into which Pool may be more
complex though. Do you really need policies to implement something so
sensible :).
I am inclined to think we are heading more into discussing all of
these as part of the WG that Andy proposed earlier on the list, so
that multiple aspects of IPv6 delegation can be considered into a
single document, rather then trying to get a patchwork of policies to
fill in the gaps inherited from v4.
thanks
-gaurab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5SQJwACgkQSo7fU26F3X2QigCguWIM6x2jVKbTUjSu5klE+OVf
ug4AoPS5xxnSMfsUyrBObLM2qMBLsEyM
=dr9Q
-----END PGP SIGNATURE-----