Thank you for that reference.
The example in your slides shows a situation where a /27 is required
over a multi year period but that under the current system this is
allocated as two /29s and a /28. Your presentation claims that this
causes problems with non-optimal network design.
I am interested to hear from Sanjaya or the hostmasters if this would
actually be a problem in reality.
If I were a member who came to APNIC with comprehensive documentation
showing a network rollout over 5 years which needed a /27, would this
be allocated under provisions in the following section of
apnic-089-v010
------
5.2.3 Larger initial allocations
Initial allocations larger than /32 may be justified if:
a) The organization provides comprehensive documentation of planned
IPv6 infrastructure which would require a larger allocation;
------
In other words, if I can show that I have a need for larger network,
can this be currently addressed without the need to change policy.
Regards,
Dean
On Fri, Jul 20, 2012 at 12:45 AM, Xing Li <xing at cernet dot edu dot cn> wrote:
Hi, Dean,
Thanks for your question.
Dean Pemberton 写道:
The proposal states the following:
This proposal extends the IPv6 request process to allow large ISPs to
request multiple prefixes within a single, contiguous, reserved space.
------
I would like to understand how this is not catered for already by the
sparse allocation policy employed by the APNIC host masters.
This policy states that subsequent allocations are made from a contiguous
range where possible.
The current APNIC policy can ensure that subsequent allocations are made
from a contiguous range. However, inside the SP's network, each Pop cannot
have a contiguous range without renumbering of the addresses of initial
allocation.
The 099 will ensure the aggregated IPv6 range to the peers as well as
aggregated IPv6 range in each Pop via multiple prefixes in the initial
allocation, and subsequent allocation.
The comparison is shown in the page 6 of my presentation at
http://meetings.apnic.net/33/policy/agenda/proposal-099/prop-099-v1.pdf
If you have any questions, please let me know.
Regards,
xing
--
Regards,
Dean
------------------------------------------------------------------------
* sig-policy: APNIC SIG on resource management policy
*
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/sig-policy