By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668.
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 valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 20, 2005.
Copyright (C) The Internet Society (2004). All Rights Reserved.
RFC 3152 delegates IP6.ARPA for reverse IPv6 delegations. For RIRs (RIPE NCC, ARIN, APNIC, LACNIC and soon AFRINIC) there has been a possibility to use the IP6.ARPA tree since that time. As the 6bone (E.F.F.3.ARPA) delegation is now also established and vendors have had the time for 3 years already to support IP6.ARPA we request IANA to remove the IP6.INT delegation per 9/9/2004. Note that IP6.INT was deprecated per RFC3152 already.
Delegation of IP6.ARPA [RFC3152]Bush, R., Delegation of IP6.ARPA, August 2001., dated August 2001, delegates IP6.ARPA for IPv6 reverse delegations and also deprecates the usage of IP6.INT. For RIRs (RIPE NCC, ARIN, APNIC, LACNIC and soon AFRINIC) there has been a possiblity to use the IP6.ARPA tree since that time. As 6bone's E.F.F.3.ARPA delegation [RFC3681]Bush, R. and R. Fink, Delegation of E.F.F.3.IP6.ARPA, January 2004. is now also established and vendors have had the time for 3 years already to support IP6.ARPA we request IANA to remove the IP6.INT delegation per 9/9/2004.
This memo requests that the IANA removes the delegation of the IP6.INT domain following instructions to be provided by the IAB.
As we are removing the IP6.INT tree, there are no security concerns. Implementations should already have stopped using IP6.INT as per RFC3152.
|[RFC3152]||Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152, August 2001.|
|[RFC3681]||Bush, R. and R. Fink, "Delegation of E.F.F.3.IP6.ARPA", BCP 80, RFC 3681, January 2004.|
|Unfix / SixXS|
|Gouda 2807 LW|
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at email@example.com.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
Funding for the RFC Editor function is currently provided by the Internet Society.