Network Working Group G. Huston
Request for Comments: 4773 APNIC
Category: Informational December 2006
Network Working Group G. Huston
Request for Comments: 4773 APNIC
Category: Informational December 2006
Administration of the IANA Special Purpose IPv6 Address Block
IANA专用IPv6地址块的管理
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
Abstract
摘要
This is a direction to IANA concerning the management of the IANA Special Purpose IPv6 address assignment registry.
这是向IANA发出的有关IANA专用IPv6地址分配注册表管理的指示。
This is a direction to IANA concerning the management of the IANA Special Purpose IPv6 address assignment registry.
这是向IANA发出的有关IANA专用IPv6地址分配注册表管理的指示。
[RFC2928] specified the assignment of the IPv6 address prefix to IANA. The rationale for this allocation is:
[RFC2928]指定将IPv6地址前缀分配给IANA。这种分配的理由是：
"The block of Sub-TLA IDs assigned to the IANA (i.e., 2001:
0000::/29 - 2001:01F8::/29) is for assignment for testing and
experimental usage to support activities such as the 6bone, and
for new approaches like exchanges." [RFC2928]
"The block of Sub-TLA IDs assigned to the IANA (i.e., 2001:
0000::/29 - 2001:01F8::/29) is for assignment for testing and
experimental usage to support activities such as the 6bone, and
for new approaches like exchanges." [RFC2928]
This address allocation to IANA was intended to support testing and experimental activities. A more general view of the roles of IANA with respect to address allocation functions is documented in [RFC2860]:
分配给IANA的地址旨在支持测试和实验活动。[RFC2860]中记录了IANA在地址分配功能方面的作用的更一般视图：
"4.3. [...] Note that [...] (b) assignments of specialised address blocks (such as multicast or anycast blocks), and (c) experimental assignments are not considered to be policy issues, and shall remain subject to the provisions of this Section 4. (For purposes of this MOU, the term "assignments" includes allocations.)" [RFC2860]
“4.3.[…]请注意[…]（b）专用地址块（如多播或选播块）的分配和（c）实验性分配不被视为政策问题，应遵守本第4节的规定。（就本谅解备忘录而言，“分配”一词包括分配）。”[RFC2860]
The reference to section 4 here is to the general technical work for the IANA:
此处参考第4节是指IANA的一般技术工作：
"4.1. The IANA will assign and register Internet protocol parameters only as directed by the criteria and procedures specified in RFCs, including Proposed, Draft, and full Internet Standards and Best Current Practice documents, and any other RFC that calls for IANA assignment." [RFC2860]
“4.1.IANA将仅按照RFC中规定的标准和程序分配和注册互联网协议参数，包括提议的、草案的和完整的互联网标准和最佳实践文件，以及要求IANA分配的任何其他RFC。”[RFC2860]
This document directs IANA to undertake designation of special purpose address blocks within the purview of direct assignments by the IANA under the terms of the assignment criteria specified in RFC 2928.
本文件指示IANA根据RFC 2928规定的分配标准，在IANA直接分配的范围内指定特殊用途地址块。
This document directs IANA to open a Special Purpose IPv6 address registry for the management of these IANA-designated address blocks. Special Purpose registrations to be made from this registry include addresses for experimental purposes, as described in [RFC2928], and other special purpose cases, as documented in IESG-reviewed published RFCs, according to the provisions described in section 4.1 of [RFC2860].
本文档指导IANA打开一个专用IPv6地址注册表，用于管理这些IANA指定的地址块。根据[RFC2860]第4.1节的规定，从该注册中心进行的特殊目的注册包括[RFC2928]中所述的实验目的地址，以及IESG审查的已发布RFC中记录的其他特殊目的情况。
IANA maintains an "IANA IPv6 Address Special Purpose Registry". The registry records current IANA address designations from the IANA-managed Special Purpose IPv6 address pool.
IANA维护一个“IANA IPv6地址专用注册表”。注册表记录来自IANA管理的专用IPv6地址池的当前IANA地址指定。
This recommendation concerns the management of the address pool assigned by the IETF to the IANA in July 1999 by [RFC2928], namely 2001:0000::/23. Following the policies outlined in [RFC2434], further assignments of address space to IANA for subsequent designation of address prefixes for the purposes listed here shall be undertaken only through an IETF Consensus action. Such directions for assignments of address space to augment the IANA-managed special purpose address pool should, in the general course of events, be consistent with prevailing IANA IPv6 address management policies [IPv6-Policies].
本建议涉及IETF于1999年7月通过[RFC2928]分配给IANA的地址池的管理，即2001:0000:：/23。按照[RFC2434]中概述的政策，仅可通过IETF协商一致行动，向IANA进一步分配地址空间，以便随后指定用于此处所列目的的地址前缀。在事件的一般过程中，为扩充IANA管理的专用地址池而分配地址空间的此类指示应与现行IANA IPv6地址管理策略[IPv6策略]一致。
IANA may undertake IPv6 address designations in support of special purposes as requested in "IANA Considerations" sections in IESG-reviewed RFCs, where an address is requested with an intended use of the designated address block for the purpose of testing or experimental usage activities initiated by IETF, or for specialised use of the address block in a context (e.g., anycast) associated with an Internet Standards track protocol.
IANA可按照IESG评审的RFC中“IANA注意事项”部分的要求进行IPv6地址指定，以支持特殊用途，其中地址的请求是为了指定地址块的预期用途，用于IETF发起的测试或实验使用活动，或在与互联网标准跟踪协议相关联的上下文（例如，选播）中专门使用地址块。
The IANA IPv6 Special Purpose Address Registry records, for all current address designations undertaken by IANA:
IANA IPv6专用地址注册表记录IANA进行的所有当前地址指定：
1. The designated address prefix.
1. 指定的地址前缀。
2. The RFC that called for the IANA address designation.
2. 要求IANA地址指定的RFC。
3. The date the designation was made.
3. 指定的日期。
4. The date the use designation is to be terminated (if specified as a limited-use designation).
4. 终止使用标识的日期（如果指定为限制使用标识）。
5. The nature of the purpose of the designated address (e.g., unicast experiment or protocol service anycast).
5. 指定地址用途的性质（例如，单播实验或协议服务选播）。
6. For experimental unicast applications and otherwise as appropriate, the registry will also identify the entity and related contact details to whom the address designation has been made.
6. 对于实验性单播应用程序和其他适当的应用程序，注册中心还将确定地址指定对象的实体和相关联系方式。
7. The registry will also note, for each designation, the intended routing scope of the address, indicating whether the address is intended to be routable only in scoped, local, or private contexts, or whether the address prefix is intended to be routed globally.
7. 注册表还将注意到，对于每个指定，地址的预期路由范围，指示地址是否仅在范围、本地或私有上下文中可路由，或者地址前缀是否打算全局路由。
8. The date in the IANA registry is the date of the IANA action, i.e., the day IANA records the allocation.
8. IANA注册表中的日期是IANA行动的日期，即IANA记录分配的日期。
The IANA registry notes, as a general comment, that address prefixes listed in the Special Purpose Address Registry are not guaranteed routability in any particular local or global context.
IANA注册中心指出，作为一般性意见，特殊用途地址注册中心中列出的地址前缀在任何特定的本地或全局上下文中都不能保证可路由性。
IANA will not maintain further sub-registries for any special purpose address block designated according to this direction.
IANA不会为根据本指令指定的任何特殊用途地址块维护进一步的子注册表。
Security of the Internet's routing system relies on the ability to authenticate an assertion of unique control of an address block. Measures to authenticate such assertions rely on validation that the address block forms part of an existing allocated address block, and that there is a trustable and unique reference in the IANA address registries.
Internet路由系统的安全性依赖于对地址块的唯一控制断言进行身份验证的能力。验证此类断言的措施依赖于验证地址块是否构成现有已分配地址块的一部分，以及IANA地址注册表中是否存在可信任且唯一的引用。
The proposed registry is intended to provide an authoritative source of information regarding the currency and intended purpose of special use IPv6 address blocks that are designated from the IANA-
拟议的注册旨在提供有关IANA指定的特殊用途IPv6地址块的货币和预期用途的权威信息来源-
administered Special Use registry. This is a small step towards the creation of a comprehensive registry framework that can be used as a trust point for commencing a chain of address validation. Consideration should be given to IANA registry publication formats that are machine parseable, and also the use of file signatures and associated certificate mechanisms to allow applications to confirm that the registry contents are current, and that they have been published by the IANA.
管理特殊用途登记处。这是创建一个全面的注册表框架的一小步，该框架可用作启动地址链验证的信任点。应考虑机器可解析的IANA注册表发布格式，以及使用文件签名和相关证书机制，以允许应用程序确认注册表内容是最新的，并且已由IANA发布。
The document was prepared with the assistance of Leslie Daigle, Brian Haberman, Bob Hinden, David Kessens, Kurt Lindqvist, Thomas Narten, and Paul Wilson.
该文件是在莱斯利·戴格尔、布赖恩·哈伯曼、鲍勃·欣登、大卫·凯森斯、库尔特·林克维斯特、托马斯·纳滕和保罗·威尔逊的协助下编写的。
[IPv6-Policies] IANA, "IPv6 Allocation and Assignment Policy", June 2002.
[IPv6政策]IANA，“IPv6分配和分配政策”，2002年6月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority", RFC 2860, June 2000.
[RFC2860]Carpenter，B.，Baker，F.和M.Roberts，“关于互联网分配号码管理局技术工作的谅解备忘录”，RFC 28602000年6月。
[RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.
[RFC2928]Hinden，R.，Deering，S.，Fink，R.，和T.Hain，“初始IPv6子TLA ID分配”，RFC 29282000年9月。
Author's Address
作者地址
Geoff Huston Asia Pacific Network Information Centre
杰夫休斯顿亚太网络信息中心
EMail: gih@apnic.net
URI: http://www.apnic.net
EMail: gih@apnic.net
URI: http://www.apnic.net
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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, THE IETF TRUST, 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
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.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和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.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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 ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。