Re: [sig-policy] prop-073-v002: Automatic allocation/assignment of IPv6
Hash: SHA1
Hi,
>
> This is a proposal to simplify the criteria for a member requesting an
> initial block of IPv6 addresses where the member already has an IPv4
> assignment or allocation.
I agree with this part of the proposal.
>
> Under this proposal, APNIC would reserve the appropriately sized IPv6
> block for each APNIC member that has IPv4 addresses but does not yet
> have IPv6 addresses.
I have an issue with 'reserving' based on member's current v4 address
allocation. This assumes that the companies will remain static, will not
request (or acquire) more v4 addresses before they actually deploy v6.
Also, I have an implementation question on this though. How does the
reserving of address space work with the binary chop/ sparse allocation
practiced by APNIC currently.
For example, if someone has a v4 allocation currently, and are assigned
a /32, but say in 2 years time when they are actually ready to request
for v6, they may need a /30. how does the reserved address work in this
case ? If the secretariat has to actually do any work to change the
'reserved' allocation to a 'regular' allocation, it's still double the
work, and would not achieve much.
>
> It is further proposed that members holding IPv4 addresses be able to
> request the IPv6 space reserved for them through a simple one-step
> process.
>
This is probably the main objective of the revised proposal, and I agree
with this.
How this is implemented - pre-reservation or a single click (may be even
automated verification ), is something i'd not want to put into the
proposal.
- -gaurab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqHrR8ACgkQSo7fU26F3X1NRgCeJoqldRVpKL5ebKOF4a0cGzXF
qPIAoKHGQltrEalfGvQgPF8KvmQAm+We
=nIOm
-----END PGP SIGNATURE-----