RFC 3152 (rfc3152) - Page 1 of 4
Delegation of IP6
Alternative Format: Original Text Document
Network Working Group R. Bush
Request for Comments: 3152 RGnet
BCP: 49 August 2001
Updates: 2874, 2772, 2766, 2553, 1886
Category: Best Current Practice
Delegation of IP6.ARPA
Status of this Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
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 an acronym for "Address and Routing Parameters Area") be
used for technical infrastructure sub-domains when possible. It is
already in use for IPv4 reverse mapping and has been established as
the location for E.164 numbering on the Internet [RFC 2916 RFC 3026].
IETF consensus was reached that the IP6.ARPA domain be used for
address to DNS name mapping for the IPv6 address space [RFC 2874].
2. Obsoleted Usage
This document deprecates references to IP6.INT in [RFC 1886] section
2.5, [RFC 2553] section 6.2.3, [RFC 2766] section 4.1, [RFC 2772]
section 7.1.c, and [RFC 2874] section 2.5.
In this context, 'deprecate' means that the old usage is not
appropriate for new implementations, and IP6.INT will likely be
phased out in an orderly fashion.
Bush Best Current Practice
