Delegation of E.F.F.3.IP6.ARPA
RFC 3681

Document Type RFC - Best Current Practice (January 2004; No errata)
Also known as BCP 80
Was draft-ymbk-6bone-arpa-delegation (individual in int area)
Last updated 2018-07-19
Stream IETF
Formats plain text html pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3681 (Best Current Practice)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Thomas Narten
Send notices to (None)
Network Working Group                                            R. Bush
Request for Comments: 3681                                           IIJ
BCP: 80                                                          R. Fink
Category: Best Current Practice                             January 2004

                     Delegation of E.F.F.3.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 (2004).  All Rights Reserved.


   This document discusses the need for delegation of the
   E.F.F.3.IP6.ARPA DNS zone in order to enable reverse lookups for
   6bone addresses, and makes specific recommendations for the process
   needed to accomplish this.

1.  6bone and DNS

   The 6bone, whose address space was allocated by [RFC2471], has
   provided a network for IPv6 experimentation for numerous purposes for
   seven years.  Up to the present time, reverse lookups for 6bone
   addresses have been accomplished through IP6.INT.  It is now
   important that the thousands of 6bone users be able to update their
   IPv6 software to use IP6.ARPA [RFC3152].

   Although the 6bone has a limited life, as a phaseout plan is being
   discussed at the IETF at this time [I-D.fink-6bone-phaseout], there
   is likely to be 2.5 to 3.5 more years of operation.  During this
   remaining 6bone lifetime IP6.ARPA reverse lookup services for the
   3ffe::/16 address space are required.

   Discussions have been underway between the 6bone and RIR communities,
   about having the RIRs perform this service.  It was agreed at the San
   Francisco IETF meeting in March 2003 that it was more practical for
   the 6bone to provide this service for itself.  This would relieve the
   RIRs of the costs of providing this service, yet still provide the
   IP6.ARPA authority the ability to terminate the service when the
   planned 6bone termination date is reached (currently anticipated to
   be June 6, 2006).

Bush & Fink              Best Current Practice                  [Page 1]
RFC 3681             Delegation of E.F.F.3.IP6.ARPA         January 2004

   The current planning within the 6bone operational community is to
   provide new inet6num attributes in the 6bone registry database for
   top level 6bone address space holders to request delegation to their
   reverse path servers.

2.  IANA Considerations

   This memo requests that the IANA delegate the E.F.F.3.IP6.ARPA domain
   to the 6bone, as will be described in instructions to be provided by
   the IAB.  Names within this zone are to be further delegated within
   the top level 6bone ISPs (known as pTLAs) in accordance with the
   delegation of 6bone 3FFE::/16 address space.

3.  Security Considerations

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

4.  References

4.1.  Normative References

   [RFC2471]                 Hinden, R., Fink, R. and J. Postel, "IPv6
                             Testing Address Allocation", RFC 2471,
                             December 1998.

4.2.  Informative References

   [I-D.fink-6bone-phaseout] Fink, R. and R. Hinden, "6bone (IPv6
                             Testing Address Allocation) Phaseout", Work
                             in Progress.

   [RFC3152]                 Bush, R., "Delegation of IP6.ARPA", BCP 49,
                             RFC 3152, August 2001.

Bush & Fink              Best Current Practice                  [Page 2]
RFC 3681             Delegation of E.F.F.3.IP6.ARPA         January 2004

5.  Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
Show full document text