wdiff draft-ymbk-ip6-arpa-delegation-01.txt draft-ymbk-ip6-arpa-delegation-02.txt

INTERNET-DRAFT Randy Bush
draft-ymbk-ip6-arpa-delegation-01.txt Verio
01.01.25

Delegation of IP6.ARPA

This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents validA new Request for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It Comments is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work now available in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list online RFC libraries.

BCP 49
RFC 3152

Title: Delegation of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

0. Abstract IP6.ARPA
Author(s): R. Bush
Status: Best Current Practice
Date: August 2001
Mailbox: randy@psg.com
Pages: 4
Characters: 5727
Updates: 2874, 2772, 2766, 2553, 1886
See Also: BCP 49

I-D Tag: draft-ymbk-ip6-arpa-delegation-02.txt

URL: ftp://ftp.rfc-editor.org/in-notes/rfc3152.txt

This document discusses the need for delegation of the IP6.ARPA DNS
zone, and specifies a plan for the technical operation thereof.

1. Why IP6.ARPA?

In the IPv6 address space, there is a need for 'reverse mapping' of
addresses to DNS names analogous to that provided by the IN-ADDR.ARPA
zone for IPv4.

The IAB recommended that the ARPA top level domain (the name is now
considered

This document specifies an acronym for "Address and Routing Parameters Area") be
used for technical infrastructure sub-domains when possible. It is
already in use Internet Best Current Practices for IPv4 reverse mapping and has been established as
the location for E.164 numbering on the
Internet [RFC2916 RFC3026].

IETF consensus was reached that the IP6.ARPA domain be used for
address to DNS name mapping Community, and requests discussion and suggestions for the IPv6 address space [RFC2874].

INTERNET-DRAFT Delegation
improvements. Distribution of IP6.ARPA 01.01.25

2. Osoleted Usage this memo is unlimited.

This document deprecates references announcement is sent to IP6.INT in [RFC2553] section
6.2.3, [RFC2766] section 4.1, [RFC2772] section 7.1.c, and [RFC2874]
section 2.5.

3. IANA Considerations

This memo requests that the IANA delegate the IP6.ARPA domain
following instructions to be provided by IETF list and the IAB. Names within this
zone are RFC-DIST list.
Requests to be further delegated added to or deleted from the regional IP registries in
accordance with the delegation of IPv6 address space to those
registries. The names allocated IETF distribution list
should be hierarchic in accordance
with the address space assignment.

4. Security Considerations

While DNS spoofing of address to name mapping has been exploited in
IPv4, delegation of the IP6.ARPA zone creates no new threats sent to the
security of the internet.

5. References

[RFC2553]
Basic Socket Interface Extensions for IPv6. R. Gilligan, S. Thom-
son, J. Bound, W. Stevens. March 1999.

[RFC2766]
Network Address Translation - Protocol Translation (NAT-PT). G.
Tsirtsis, P. Srisuresh. February 2000.

[RFC2772]
6Bone Backbone Routing Guidelines. R. Rockell, R. Fink. February
2000.

[RFC2874]
DNS Extensions IETF-REQUEST@IETF.ORG. Requests to Support IPv6 Address Aggregation and Renumbering.
M. Crawford, C. Huitema. July 2000.

[RFC2916]
E.164 number and DNS. P. Faltstrom. September 2000.

[RFC3026]
Liaison to IETF/ISOC on ENUM. R. Blane. January 2001.

INTERNET-DRAFT Delegation of IP6.ARPA 01.01.25

6. Author's Address

Randy Bush
5147 Crystal Springs
Bainbridge Island, WA US-98110
+1 206 780 0431
randy@psg.com

7. Full Copyright Statement

This document and translations of it may be copied and furnished
added to others,
and derivative works that comment on or otherwise explain it or assist in
its implementation may deleted from the RFC-DIST distribution list should
be prepared, copied, published and distributed, in
whole or in part, without restriction of any kind, provided that the above
copyright notice and this paragraph are included sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on all such copies and
derivative works. However, this document itself obtaining RFCs via FTP or EMAIL may not be modified in any
way, such as obtained by removing the copyright notice or references sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the Internet
Society or other Internet organizations, except as needed message body
help: ways_to_get_rfcs. For example:

To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the purpose
author of
developing Internet standards in which case the procedures for copyrights
defined RFC in the Internet Standards process must be followed, question, or as required to translate it into languages other than English.

The limited permissions granted above RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are perpetual and will not for
unlimited distribution.echo
Submissions for Requests for Comments should be revoked
by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS IS"
basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.