[sig-policy] prop-076: Requiring aggregation for IPv6 subsequent allocat
The proposal, 'Requiring aggregation for IPv6 subsequent allocations',
has been sent to the Policy SIG for review. It will be presented at the
Policy SIG at APNIC 28 in Beijing, China, 25-28 August 2009.
We invite you to review and comment on the proposal on the mailing list
before the meeting.
The comment period on the mailing list before an APNIC meeting is an
important part of the policy development process. We encourage you to
express your views on the proposal:
- Do you support or oppose this proposal?
- Does this proposal solve a problem you are experiencing? If
so, tell the community about your situation.
- Do you see any disadvantages in this proposal?
- Is there anything in the proposal that is not clear?
- What changes could be made to this proposal to make it more
Information about this and other policy proposals is available from:
Randy, Jian and Ching-Heng
prop-076-v001: Requiring aggregation for IPv6 subsequent allocations
Authors: Tomohiro Fujisaki
<fujisaki at syce dot net>
Date: 29 July 2009
This is a proposal to make it a condition that LIRs aggregate subsequent
IPv6 allocations that they receive from APNIC.
2. Summary of the current problem
The initial IPv6 address allocation criteria requires that LIRs:
"Plan to provide IPv6 connectivity to organizations to which it will
make assignments, by advertising that connectivity through its
single aggregated address allocation."
However, there is no similar aggregation requirement in the criteria for
For consistency, the routing requirement should be applied also in
subsequent allocation criteria.
3. Situation in other RIRs
The LACNIC community is currently discussing the following proposal
to remove the requirement to announce an initial allocation as a
single prefix in favour of announcing the prefix with the minimum
possible level of disaggregation:
2007-01: Modifications to the IPv6 Prefix Initial Allocation Policy
The RIPE community is currently discussing the following proposal
remove routing requirements from IPv6 policy:
2009-06: Removing Routing Requirements from the IPv6 Address
AfriNIC and ARIN initial IPv6 allocation criteria require a plan to
aggregate, with no requirement for aggregation for subsequent allocation
criteria. Neither RIR is has any proposal to modify these criteria.
This is a proposal to add the requirement under the subsequent IPv6
allocation criteria to aggregate subsequent IPv6 allocations as a single
- By describing clearly in the policy as a requirement, it may
contribute to limiting routing expansion of the global IPv6
routing table in the future.
- This proposal may just be a nonbinding requirement.
- APNIC policy may be more strict than other regions if other
RIR communities decided to remove aggregation requirement from
6. Effect on APNIC members
APNIC members will be required to aggregate subsequent allocations as a
7. Effect on NIRs
Same as above.
 See section 5.2.1, "IPv6 Address Allocation and Assignment Policy"