Network Working Group R. Bush
Request for Comments: 3681 IIJ
BCP: 80 R. Fink
Category: Best Current Practice January 2004
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
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.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
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.
本文件讨论了授权E.F.F.3.IP6.ARPA DNS区域的必要性，以实现对6bone地址的反向查找，并对实现此目的所需的过程提出了具体建议。
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].
6bone的地址空间由[RFC2471]分配，七年来，它为IPv6实验提供了一个网络，用于多种用途。到目前为止，对6bone地址的反向查找已经通过IP6.INT完成。现在重要的是，成千上万的6bone用户能够更新他们的IPv6软件以使用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.
尽管6bone的使用寿命有限，但由于IETF正在讨论逐步淘汰计划[I-D.fink-6bone-Phase-out]，可能还有2.5到3.5年的运行时间。在剩余的6bone生存期内，需要3ffe:：/16地址空间的IP6.ARPA反向查找服务。
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).
6bone和RIR社区之间正在就让RIR提供这项服务进行讨论。在2003年3月的旧金山IETF会议上，人们一致认为6骨为自己提供这种服务更实际。这将减轻RIR提供该服务的成本，但仍为IP6.ARPA管理局提供在达到计划的6bone终止日期（目前预计为2006年6月6日）时终止服务的能力。
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.
6bone操作社区内的当前计划是在6bone注册表数据库中为顶级6bone地址空间持有者提供新的inet6num属性，以请求委托给其反向路径服务器。
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.
本备忘录要求IANA将E.F.F.3.IP6.ARPA域委托给6bone，如IAB提供的说明所述。根据6bone 3FFE:：/16地址空间的授权，此区域内的名称将在顶级6bone ISP（称为PTLA）中进一步授权。
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.
虽然IPv4中利用了地址到名称映射的DNS欺骗，但E.F.F.3.IP6.ARPA区域的授权不会对internet的安全造成新的威胁。
[RFC2471] Hinden, R., Fink, R. and J. Postel, "IPv6 Testing Address Allocation", RFC 2471, December 1998.
[RFC2471]Hinden，R.，Fink，R.和J.Postel，“IPv6测试地址分配”，RFC 24711998年12月。
[I-D.fink-6bone-phaseout] Fink, R. and R. Hinden, "6bone (IPv6 Testing Address Allocation) Phaseout", Work in Progress.
[I-D.fink-6bone-phaseout]fink，R.和R.Hinden，“6bone（IPv6测试地址分配）淘汰”，工作正在进行中。
[RFC3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152, August 2001.
[RFC3152]Bush，R.，“IP6.ARPA的授权”，BCP 49，RFC 3152，2001年8月。
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.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
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 Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
Randy Bush IIJ 5147 Crystal Springs Bainbrisge Island, WA 98110 US
兰迪·布什IIJ 5147水晶泉美国华盛顿州班布里奇岛98110
Phone: +1 206 780 0431
EMail: randy@psg.com
URI: http://psg.com/~randy/
Phone: +1 206 780 0431
EMail: randy@psg.com
URI: http://psg.com/~randy/
Robert Fink Truckee, CA US
罗伯特·芬克·特鲁基，加利福尼亚州
EMail: bob@thefinks.com
EMail: bob@thefinks.com
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may 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 on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。