[sig-policy] IPv4 final /8 proposals
Hash: SHA1
Dear Colleagues
As you know, we have a lot of proposals to discuss in Hong Kong. Before
we meet to discuss the proposals in Hong Kong, we would like to make as
much progress as possible in discussions on the mailing list.
Discussing proposals in depth on this list before the meeting has two
big advantages:
- It helps us with time constraints in Hong Kong if we can begin to
sort out arguments for and against proposals on the list.
- It helps proposal authors amend their proposals in response to
community feedback and therefore present proposals more likely
to meet the community's needs during the Policy SIG in Hong Kong.
There are seven proposals directly related to APNIC's final /8 policy.
To help Policy SIG members begin discussion on these proposals, we
suggest taking the following steps:
1. Read the policy proposal summaries below
2. Start discussing the proposals (some initial questions to help
generate discussion are included below)
1. Summary of IPv4 final /8 amendment proposals
- -----------------------------------------------
prop-085: Eligibility for critical infrastructure assignments from the
final /8
- Permit critical Internet infrastructure to receive a single
/24 from final /8.
prop-093: Reducing the minimum delegation size for the final /8 policy
- Reduce the minimum delegation size in final /8 to a /24,
with organizations able to request and receive delegations
from APNIC up to a total of /22.
- Expand eligibility for a delegation from final /8 to
include any organization that can meet existing
assignment criteria.
prop-088: Distribution of IPv4 addresses once the final /8 period
starts
- Any IPv4 addresses APNIC may receive after the final
/8 policy is activated are to be distributed according
to the final /8 policy framework.
prop-092: Distribution of space outside final /8
- The final /8 given to APNIC by the IANA to be the specific
/8 block to which final /8 policies apply.
- Any IPv4 addresses APNIC may receive after the final /8
policy is activated are to be distributed according to the
allocation policies in place before the final /8 policy
framework was implemented.
prop-089: Additional criterion for final /8 allocations (and
assignments)
- To receive space under the final /8 policy, organizations
must demonstrate a viable IPv6 deployment.
prop-091: Changing final /8 to final /9
- Split the final /8 given to APNIC into two /9s:
- One /9 to be allocated according to pre-final /8
allocation policies
- The remaining /9 to be distributed according to the
final /8 allocation policies
prop-094: Adding alternative criteria to renumbering requirement in
final /8 policy
- Permit organizations requesting their initial allocation
from APNIC under the final /8 phase to choose between two
criteria:
- Commit to renumber out of upstream provider's space
(existing criteria)
- Demonstrate that the usage rate of their IPv4 space from
their upstream provider(s) has reached 80% utilization
2. Next step: we need YOU!
- ---------------------------
Some initial questions to help the community begin discussion on the
above proposals are:
- Which proposals would APNIC be able to implement together?
- Which proposals would it be difficult for APNIC to implement
together?
- What are the actual issues with the current final /8 policy that
need to be fixed? For this, we would suggest people review the
discussion held at the APNIC 30 plenary, including the
discussion document linked from the plenary page:
http://meetings.apnic.net/30/program/plenary
- - Gaurab, Ching-Heng, and Terence
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1Pi2sACgkQSo7fU26F3X3LCACdGp02RUSGGJRAjwXmve5ef4mz
vzAAn0BpHhPZ+tRJ2T2fAbmC7E4dtV2o
=eIex
-----END PGP SIGNATURE-----