[sig-nir] NIR SIG proposal: NIR operational policy document revision
We invite you to review and comment on the proposal
"NIR operational policy document revision"
which has been sent to NIR SIG for the review. We encourage you to:
- Ask the proposer questions if anything in the proposal is
- Point out advantages and disadvantages you see in the proposal
- State whether you support or oppose the proposal
The proposal's history can be found at:
Mailing list discussions will be taken into account as an important part
of the policy development process when the proposal will be discussed at
the upcoming NIR SIG at APNIC25 (Taipei, Taiwan, 25-29 February 2008).
We are looking forward to hear your comments on the proposal!
Izumi Okutani, David Chen
sig-nir-chair at apnic dot net
prop-054-v001: NIR operational policy document revision
<sanjaya at apnic dot net>
<terry at apnic dot net>
Date: 14 January 2008
This is a proposal to revise the reverse zone delegation section of the
policy document APNIC-103-v001, "Operational policies for National
Internet Registries in the APNIC region".
The APNIC-103-v001 document was written in 2002 and specifies a reverse
delegation management process that does not take into accounts newer
systems and technologies that have been developed since then.
The current document refers only to in-addr.arpa and contains no
reference to ip6.arpa.
3. Situation in other RIRs
Not applicable, as most of the other RIRs have neither NIRs nor shared
zone management arrangement with their NIRs.
It is proposed that:
4.1 Section 3.4 of APNIC-103-v001 be updated to include a reference to
reverse DNS delegations in ip6.arpa.
4.2 The two processes for delegating reverse zones specified in section
3.4 of APNIC-103-v001 be replaced with the following two processes:
Reverse DNS zones may be managed using the currently supported
automated process documented at:
Reverse DNS delegations resource guide
Reverse DNS delegations may be managed using MyAPNIC.
4.3 "Appendix: Details of flat file view of a zone" be removed from
APNIC-103-v001 as it is no longer needed.
- The revised processes are less prescriptive on the technical
implementation, and would therefore be more flexible in
anticipating future operational changes.
- The revised processes include ip6.arpa, which is not mentioned
in the current document.
- NIRs may have to move to newer systems for delegating reverse
zones from time to time as the APNIC Secretariat adopts the
To ensure that NIRs have enough time to adapt to the changes,
the APNIC Secretariat will commit to a six-month notice period
between announcing changes to the system and expected
implementation by NIRs.
Effect on APNIC
Having a less technically prescriptive document gives the APNIC
Secretariat the flexibility to adopt systems and technology that will
best serve APNIC members.
Effect on NIRs
NIRs will retain their ability to choose technology options, but
should also be prepared from time to time to move on to newer systems
to support their members as APNIC upgrades its systems to keep pace
with current and future technologies and mechanisms.