[sig-dns] Final call for comments: [prop-030-v002] " Deprecation of ip6.int reverse DNS service in APNIC"

[Save Vocea <save@apnic.net>]

Dear colleagues

APNIC welcomes comments, questions, and suggestions on the following  
policy
proposal:

____________________

Final call for comments: [prop-030-v002]
" Deprecation of ip6.int reverse DNS service in APNIC"
____________________

This is the final call for comments on policy proposal [prop-030-v002]
"Deprecation of ip6.int reverse DNS service in APNIC".

This is a proposal that APNIC cease devoting resources to support the
operation of the ip6.int domain at a date to be determined jointly with
the other RIRs.

This proposal was presented at APNIC 20 and the following consensus was
reached:

   "The SIG accepted by consensus the proposed policy process,
    which requires the text proposal to be sent to the mailing
    list one month before the meeting, an eight week comment
    period on the mailing list after the meeting, and final
    endorsement from EC."

This proposal is now submitted to the sig-dns mailing list for an
eight week discussion period. At the end of that period, if consensus
appears to have been achieved, the Chair of the DNS Operations SIG will
ask the Executive Council to endorse the proposal for implementation.

*   Send all comments and questions to:   <sig-dns@apnic.net>
*   Deadline for comments:                16 November 2005


_____________________________________________________________________

Proposal details
_____________________________________________________________________

Author:      Sanjaya <sanjaya@apnic.net>

Version:      2.0

Date:         8 September 2005


Introduction
------------

The use of the ip6.int domain was deprecated in August 2001 (RFC  
3152). It
has been replaced by ip6.arpa domain. The RFC indicated that the use  
of the
ip6.int domain was "likely be phased out in an orderly fashion".

An individual Internet Draft has been submitted by Geoff Huston
(draft-huston-ip6-int-03.txt) to deprecate ip6.int, and proposing  
that the
Regional Internet Registries are no longer required to maintain the
delegation of entries in ip6.int. The date nominated in that draft is
1 September 2005. This draft has been submitted into the IETF's  
Standards
track and is currently being considered by the IESG for adoption as  
an RFC.

APNIC has stopped accepting updates to ip6.int domain for the last  
one year,
since June 2004. However, the APNIC DNS servers are still getting  
roughly 5
queries per minute on this domain.


Proposal Summary
----------------

With the acceptance of draft-huston-ip6-int-03 as an RFC, it is proposed
that APNIC cease devoting resources to support the operation of this
deprecated domain, at a date no earlier than 1 June 2006.


Situation in other RIRs
-----------------------

Other RIRs are facing this issue, and are likely to take action in due
course. LACNIC has consulted its community and is currently preparing to
cease ip6.int support. ARIN, RIPE and AFRINIC can be expected to
present this issue in their respective communities at a later date.


Details of your proposal
------------------------

APNIC domain name servers will cease answering ip6.int reverse domain
queries after a specific date. The cut off date is to be determined
jointly with the other RIRs.

The following steps are proposed to ensure orderly cutoff and minimise
operational impact:

- Notify the parties who have been sending ip6.int queries to APNIC
  servers (2 weeks after EC approval)
- Monitor the DNS traffic for ip6.int queries
- Send final reminder to the parties still sending ip6.int queries
  (4 weeks before 1 June 2006)
- Send public announcements through newsletter, website, MyAPNIC,
  mailing lists (as needed)
- Notify root ip6.int to remove APNIC delegation on the cutoff date
  (1 week and 1 day prior)
- Remove ip6.int entries in APNIC domain name servers and restart the
  service (cutoff date to be determined later)
- Report completion of the project in APNIC 22 meeting (September 2006)


Advantages and disadvantages of adopting the proposed policy
------------------------------------------------------------

With the implementation of this policy, only one IPv6 reverse DNS  
service
is maintained: ip6.arpa. This should prevent confusion by the end  
users and
network administrators, while freeing APNIC resources to more productive
work.

Legacy IPv6 applications that use ip6.int domain and do not support
ip6.arpa will no longer obtain valid DNS results. However, since  
updates to
ip6.int ceased some time ago, such results have been incomplete or
inaccurate for at least 1 year. Additionally it is expected that the
affected parties will have been well informed by the IETF's standards
action as well as by the operational steps outlined above.


Effect on APNIC members
-----------------------

- Members using legacy IPv6 applications should migrate to the latest
  version that supports ip6.arpa
- Members receiving ip6.int delegation from APNIC should cease operating
  their ip6.int domain.


Effect on NIRs
--------------

- NIRs receiving ip6.int delegation from APNIC should cease operating
  their ip6.int domain.


References
----------

- RFC3152 Delegation of IP6.ARPA
  http://www.ietf.org/rfc/rfc3152.txt

- Geoff Huston, Deprecation of "ip6.int"
  http://www.ietf.org/internet-drafts/draft-huston-ip6-int-03.txt


____________________

References
____________________

Proposal details including full text of proposal, presentations, links
to relevant meeting minutes, and links to mailing list discussions are
available at:

     http://www.apnic.net/docs/policy/proposals/prop-030-v002.html


--
Savenaca Vocea, Policy Development Manager, APNIC   <save@apnic.net>
http:// 
www.apnic.net                                                        
ph/fx +61 7 3858 3100/99