Network Working Group G. Huston
Request for Comments: 4147 APNIC
Category: Informational August 2005
Network Working Group G. Huston
Request for Comments: 4147 APNIC
Category: Informational August 2005
Proposed Changes to the Format of the IANA IPv6 Registry
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 Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document proposes a revised format for the IANA IPv6 address registries. Rather than providing a formal definition of the format, it is described by giving examples of the (current as of preparation of this document) contents of the registries in the proposed format. The proposed format would bring the IANA IPv6 address registries into alignment with the current IPv6 Address Architecture specification, as well as update it to a more useful and generally accepted format.
本文件提出了IANA IPv6地址注册的修订格式。本文没有提供格式的正式定义，而是以拟议格式举例说明登记册（截至编写本文件之时）的内容。建议的格式将使IANA IPv6地址注册与当前的IPv6地址体系结构规范保持一致，并将其更新为更有用和普遍接受的格式。
This document proposes a revised format for the IANA IPv6 address registries. The proposed format would bring the IANA IPv6 address registries into alignment with the current IPv6 Address Architecture specification, as well as update it to a more useful and generally accepted format.
本文件提出了IANA IPv6地址注册的修订格式。建议的格式将使IANA IPv6地址注册与当前的IPv6地址体系结构规范保持一致，并将其更新为更有用和普遍接受的格式。
The current (as of preparation of this document) IANA IPv6 registries [iana-ipv6-registry] [iana-ipv6-tla] are based on a now-deprecated address architecture that used the concept of Top Level Aggregation Identifiers (TLAs) and sub-TLAs. The current IPv6 Address Architecture [RFC3513] uses the terminology of Global Identifiers instead of TLAs and sub-TLAs.
当前（截至本文件编制之时）IANA IPv6注册表[IANA-IPv6-registry][IANA-IPv6-tla]基于一种现已弃用的地址体系结构，该体系结构使用顶级聚合标识符（tla）和子tla的概念。当前的IPv6地址体系结构[RFC3513]使用全局标识符的术语，而不是TLA和子TLA。
The proposed format for the IPv6 address registry is indicated by example, using the registry state that is current as of preparation of this document, in Figure 1. The registry explicitly notes which entity is placing a reservation on an address block and notes the defining RFC document for each allocation.
IPv6地址注册表的建议格式如图1所示，使用本文档编写时的当前注册表状态。注册表会明确记录哪个实体正在地址块上放置保留，并记录每个分配的定义RFC文档。
The proposed format of the registry is a title line, the date of the last change to the registry, the registry in a tabular format, notes and references.
登记册的拟议格式为标题行、登记册上次更改的日期、表格格式的登记册、注释和参考资料。
The table uses 4 columns. Within the table, the first column contains an IPv6 address prefix, using a hexadecimal notation of the address prefix and a prefix length. There are no overlapping address blocks in the first column, and the set of address blocks in the registry spans the entire IPv6 address space. The second column denotes the current disposition of the address block, using notation derived from the defining RFC document. The third column contains a reference to the RFC that describes the current disposition of the address block. The fourth column uses numeric footnote notation to reference any additional text associated with the address block.
该表使用4列。在表中，第一列包含IPv6地址前缀，使用地址前缀的十六进制表示法和前缀长度。第一列中没有重叠的地址块，注册表中的地址块集跨越整个IPv6地址空间。第二列使用从定义RFC文档派生的符号表示地址块的当前配置。第三列包含对RFC的引用，RFC描述了地址块的当前配置。第四列使用数字脚注表示法引用与地址块关联的任何附加文本。
The notes in the registry may include a summary of previous disposition status values associated with an address block, as this summary is specifically not included in the registry table. The notes are numbered sequentially.
注册表中的注释可能包括与地址块相关联的先前处置状态值的摘要，因为此摘要不包括在注册表表中。音符按顺序编号。
The reference section uses a conventional citation format. The references include documents referenced in the registry table and documents referenced in the notes.
参考部分使用传统的引文格式。参考文件包括注册表表中引用的文件和注释中引用的文件。
-----------------------------------------------------
-----------------------------------------------------
INTERNET PROTOCOL VERSION 6 ADDRESS SPACE
INTERNET协议版本6地址空间
[last updated 13 January 2005]
[最后更新日期：2005年1月13日]
IPv6 Prefix Allocation Reference Note
----------- ---------- --------- ----
0000::/8 Reserved by IETF RFC3513 [1]
0100::/8 Reserved by IETF RFC3513
0200::/7 Reserved by IETF RFC4048 [2]
0400::/6 Reserved by IETF RFC3513
0800::/5 Reserved by IETF RFC3513
1000::/4 Reserved by IETF RFC3513
2000::/3 Global Unicast RFC3513 [3]
4000::/3 Reserved by IETF RFC3513
IPv6 Prefix Allocation Reference Note
----------- ---------- --------- ----
0000::/8 Reserved by IETF RFC3513 [1]
0100::/8 Reserved by IETF RFC3513
0200::/7 Reserved by IETF RFC4048 [2]
0400::/6 Reserved by IETF RFC3513
0800::/5 Reserved by IETF RFC3513
1000::/4 Reserved by IETF RFC3513
2000::/3 Global Unicast RFC3513 [3]
4000::/3 Reserved by IETF RFC3513
6000::/3 Reserved by IETF RFC3513
8000::/3 Reserved by IETF RFC3513
A000::/3 Reserved by IETF RFC3513
C000::/3 Reserved by IETF RFC3513
E000::/4 Reserved by IETF RFC3513
F000::/5 Reserved by IETF RFC3513
F800::/6 Reserved by IETF RFC3513
FA00::/7 Reserved by IETF RFC3513
FC00::/7 Reserved by IETF RFC3513
FE00::/9 Reserved by IETF RFC3513
FE80::/10 Link Local Unicast RFC3513
FEC0::/10 Reserved by IETF RFC3879 [4]
FF00::/8 Multicast RFC3513
6000::/3 Reserved by IETF RFC3513
8000::/3 Reserved by IETF RFC3513
A000::/3 Reserved by IETF RFC3513
C000::/3 Reserved by IETF RFC3513
E000::/4 Reserved by IETF RFC3513
F000::/5 Reserved by IETF RFC3513
F800::/6 Reserved by IETF RFC3513
FA00::/7 Reserved by IETF RFC3513
FC00::/7 Reserved by IETF RFC3513
FE00::/9 Reserved by IETF RFC3513
FE80::/10 Link Local Unicast RFC3513
FEC0::/10 Reserved by IETF RFC3879 [4]
FF00::/8 Multicast RFC3513
Notes:
笔记：
[0] The IPv6 address management function was formally delegated to IANA in December 1995 [RFC1881].
[0] IPv6地址管理功能于1995年12月正式委托给IANA[RFC1881]。
[1] The "unspecified address", the "loopback address", and the IPv6 Addresses with Embedded IPv4 Addresses are assigned out of the 0000::/8 address block.
[1] 从0000:：/8地址块中分配“未指定地址”、“环回地址”和带有嵌入式IPv4地址的IPv6地址。
[2] 0200::/7 was previously defined as an OSI NSAP-mapped prefix set [RFC1888]. This definition has been deprecated as of December 2004 [RFC4048].
[2] 0200:：/7以前定义为OSI NSAP映射前缀集[RFC1888]。截至2004年12月，该定义已被弃用[RFC4048]。
[3] The IPv6 Unicast space encompasses the entire IPv6 address range with the exception of FF00::/8. [RFC3513] IANA unicast address assignments are currently limited to the IPv6 unicast address range of 2000::/3. IANA assignments from this block are registered in the IANA registry: iana-ipv6-unicast-address-assignments.
[3] IPv6单播空间包含除FF00:：/8之外的整个IPv6地址范围。[RFC3513]IANA单播地址分配目前仅限于IPv6单播地址范围2000:：/3。来自此块的IANA分配在IANA注册表中注册：IANA-ipv6-unicast-address-assignments。
[4] FEC0::/10 was previously defined as a Site-Local scoped address prefix. This definition has been deprecated as of September 2004 [RFC3879].
[4] FEC0:：/10以前定义为站点本地作用域地址前缀。截至2004年9月，该定义已被弃用[RFC3879]。
References:
参考资料：
[RFC1881] The IAB and IESG, "IPv6 Address Allocation Management", RFC 1881, December 1995.
[RFC1881]IAB和IESG，“IPv6地址分配管理”，RFC18811995年12月。
[RFC1888] J. Bound et al, "OSI NSAPs and IPv6", RFC 1888, August 1996.
[RFC1888]J.Bound等人，“OSI NSAP和IPv6”，RFC 18881996年8月。
[RFC3513] R. Hinden and S. Deering, "IP Version 6 Addressing Architecture", RFC 3513, April 2003.
[RFC3513]R.Hinden和S.Deering，“IP版本6寻址体系结构”，RFC3513，2003年4月。
[RFC3879] C. Huitema and B. Carpenter, "Deprecating Site Local Addresses", RFC 3879, September 2004.
[RFC3879]C.Huitema和B.Carpenter，“不推荐现场本地地址”，RFC 3879，2004年9月。
[RFC4048] B. Carpenter, "RFC 1888 Is Obsolete", RFC 4048, April 2005.
[RFC4048]B.Carpenter，“RFC 1888已过时”，RFC 4048，2005年4月。
-----------------------------------------------------
-----------------------------------------------------
Figure 1
图1
o The textual preamble at the start of the registry has been removed, in deference to the use of standard IPv6 prefix notation in the registry.
o 已删除注册表开始处的文本前导，这与注册表中使用标准IPv6前缀表示法不同。
o Binary prefix notation has been replaced by standard IPv6 prefix hexadecimal notation, and the fraction of address space column has been replaced with the reference to the relevant RFC that defines the disposition of the address block. Footnote references are also displayed in a consistent fashion.
o 二进制前缀表示法已替换为标准IPv6前缀十六进制表示法，地址空间列的分数已替换为对定义地址块配置的相关RFC的引用。脚注引用也以一致的方式显示。
o The terminology "Unassigned" has been replaced by the more precise phrase "Reserved by IETF", indicating the body that has the token to permit reassignment of the status of this address block.
o 术语“未分配”已被更精确的短语“由IETF保留”取代，表示具有允许重新分配该地址块状态的令牌的主体。
o The "Formerly Site-Local" entry in the body of the registry has been replaced with an explicit reference to deprecation. A similar treatment is proposed for 0200::/8, although the RFC number for the deprecation document has yet to be assigned. There is a distinction drawn between the current status of a registry and the set of registry actions that have lead to the current state. The registry table describes the current status of the registry, while the text footnotes are used to describe the set of transactions leading to the current state, including any former states.
o 注册表正文中的“以前的站点本地”条目已替换为对弃用的显式引用。建议对0200:：/8进行类似的处理，尽管弃用文档的RFC编号尚未分配。注册表的当前状态与导致当前状态的注册表操作集之间存在区别。注册表表描述注册表的当前状态，而文本脚注用于描述导致当前状态的一组事务，包括任何以前的状态。
o Annotations that are references to footnotes are included in the registry in a separate column.
o 参考脚注的注释包含在注册表中的单独一栏中。
o The text commentary on unicast, multicast and anycast addresses has been removed, as there is no distinction between anycast and unicast addresses and multicast addresses are explicitly flagged in the registry.
o 单播、多播和选播地址的文本注释已删除，因为在选播和单播地址之间没有区别，并且多播地址在注册表中显式标记。
o A note and a corresponding reference to RFC1881 was added to record the formal delegation of the IPv6 address management function to IANA.
o 添加了对RFC1881的注释和相应参考，以记录IPv6地址管理功能正式委托给IANA的情况。
The proposed registry format for Global Unicast IPv6 address block allocations is indicated by example, using the registry state that was current as of preparation of this document, in Figure 2. The registry notes the current allocations, and does not include any notation of intended future allocations or reservations. All address space not listed in this registry forms the IANA unallocated address pool, to be allocated by IANA as per the prevailing address allocation policies.
全局单播IPv6地址块分配的建议注册表格式如图2所示，使用本文档编制时的当前注册表状态。登记处记录当前的分配情况，不包括任何预期未来分配或保留的注释。本注册表中未列出的所有地址空间构成IANA未分配地址池，由IANA根据现行地址分配策略进行分配。
The proposed format of the registry is a title line, the date of the last change to the registry, the registry in a tabular format, notes and references.
登记册的拟议格式为标题行、登记册上次更改的日期、表格格式的登记册、注释和参考资料。
The table uses 4 columns. Within the table, the first column is an IPv6 address prefix, using a hexadecimal notation of the address prefix and a prefix length. There are no overlapping address blocks in the first column. The entries here describe only IANA allocations of address blocks. Temporary IANA reservations for future allocations, allocation expansion windows and any other internal IANA states are not described in this registry. The second column describes the current disposition of the address block, by noting either the Regional Internet Registry (RIR) to whom the address block was assigned, or the intended use of the address block. The third column is the date of the IANA allocation, including the day of the month. The fourth column uses numeric footnote notation to reference any additional text associated with the address block.
该表使用4列。在表中，第一列是IPv6地址前缀，使用地址前缀的十六进制表示法和前缀长度。第一列中没有重叠的地址块。这里的条目仅描述地址块的IANA分配。对于未来分配、分配扩展窗口和任何其他内部IANA状态的临时IANA保留，不在本注册表中描述。第二列描述了地址块的当前配置，说明了地址块分配给的区域Internet注册表（RIR）或地址块的预期用途。第三列是IANA分配的日期，包括当月的日期。第四列使用数字脚注表示法引用与地址块关联的任何附加文本。
The notes in the registry may include a summary of previous disposition status values associated with an address block, as this summary is specifically not included in the registry table. The notes are numbered sequentially.
注册表中的注释可能包括与地址块相关联的先前处置状态值的摘要，因为此摘要不包括在注册表表中。音符按顺序编号。
The reference section uses a conventional citation format. The references include documents referenced in the registry table and documents referenced in the notes.
参考部分使用传统的引文格式。参考文件包括注册表表中引用的文件和注释中引用的文件。
-----------------------------------------------------
-----------------------------------------------------
IPV6 GLOBAL UNICAST ADDRESS ASSIGNMENTS
IPV6全局单播地址分配
[last updated 13 January 2005]
[最后更新日期：2005年1月13日]
Global Unicast Prefix Assignment Date Note
--------------------- ---------- ------ ----
2001:0000::/23 IANA 01 Jul 99 [1]
2001:0200::/23 APNIC 01 Jul 99
2001:0400::/23 ARIN 01 Jul 99
2001:0600::/23 RIPE NCC 01 Jul 99
2001:0800::/23 RIPE NCC 01 May 02
2001:0A00::/23 RIPE NCC 02 Nov 02
2001:0C00::/23 APNIC 01 May 02 [2]
2001:0E00::/23 APNIC 01 Jan 03
2001:1200::/23 LACNIC 01 Nov 02
2001:1400::/23 RIPE NCC 01 Feb 03
2001:1600::/23 RIPE NCC 01 Jul 03
2001:1800::/23 ARIN 01 Apr 03
2001:1A00::/23 RIPE NCC 01 Jan 04
2001:1C00::/22 RIPE NCC 01 May 04
2001:2000::/20 RIPE NCC 01 May 04
2001:3000::/21 RIPE NCC 01 May 04
2001:3800::/22 RIPE NCC 01 May 04
2001:4000::/23 RIPE NCC 11 Jun 04
2001:4200::/23 ARIN 01 Jun 04
2001:4400::/23 APNIC 11 Jun 04
2001:4600::/23 RIPE NCC 17 Aug 04
2001:4800::/23 ARIN 24 Aug 04
2001:4A00::/23 RIPE NCC 15 Oct 04
2001:4C00::/23 RIPE NCC 17 Dec 04
2001:5000::/20 RIPE NCC 10 Sep 04
2001:8000::/19 APNIC 30 Nov 04
2001:A000::/20 APNIC 30 Nov 04
2002::/16 6to4 01 Feb 01 [3]
2003:0000::/18 RIPE NCC 12 Jan 05
3FFE::/16 6BONE 01 Dec 98 [4]
Global Unicast Prefix Assignment Date Note
--------------------- ---------- ------ ----
2001:0000::/23 IANA 01 Jul 99 [1]
2001:0200::/23 APNIC 01 Jul 99
2001:0400::/23 ARIN 01 Jul 99
2001:0600::/23 RIPE NCC 01 Jul 99
2001:0800::/23 RIPE NCC 01 May 02
2001:0A00::/23 RIPE NCC 02 Nov 02
2001:0C00::/23 APNIC 01 May 02 [2]
2001:0E00::/23 APNIC 01 Jan 03
2001:1200::/23 LACNIC 01 Nov 02
2001:1400::/23 RIPE NCC 01 Feb 03
2001:1600::/23 RIPE NCC 01 Jul 03
2001:1800::/23 ARIN 01 Apr 03
2001:1A00::/23 RIPE NCC 01 Jan 04
2001:1C00::/22 RIPE NCC 01 May 04
2001:2000::/20 RIPE NCC 01 May 04
2001:3000::/21 RIPE NCC 01 May 04
2001:3800::/22 RIPE NCC 01 May 04
2001:4000::/23 RIPE NCC 11 Jun 04
2001:4200::/23 ARIN 01 Jun 04
2001:4400::/23 APNIC 11 Jun 04
2001:4600::/23 RIPE NCC 17 Aug 04
2001:4800::/23 ARIN 24 Aug 04
2001:4A00::/23 RIPE NCC 15 Oct 04
2001:4C00::/23 RIPE NCC 17 Dec 04
2001:5000::/20 RIPE NCC 10 Sep 04
2001:8000::/19 APNIC 30 Nov 04
2001:A000::/20 APNIC 30 Nov 04
2002::/16 6to4 01 Feb 01 [3]
2003:0000::/18 RIPE NCC 12 Jan 05
3FFE::/16 6BONE 01 Dec 98 [4]
Notes:
笔记：
[0] The assignable Global Unicast Address space is defined in [RFC3513] as being the address block defined by the prefix 2000::/3. All address space in this block not listed in the table above is reserved by IANA for future allocation.
[0] 可分配的全局单播地址空间在[RFC3513]中定义为前缀2000:：/3定义的地址块。IANA保留了上表中未列出的该块中的所有地址空间，以供将来分配。
[1] The prefix assigned to the IANA, 2001:0000::/23, is for assignment for testing, experimental and trial usage by IANA [RFC2928].
[1] 分配给IANA的前缀，2001:0000:：/23，用于分配给IANA进行测试、实验和试用[RFC2928]。
[2] 2001:0DB8::/32 has been assigned as a NON-ROUTABLE range to be used for documentation purposes [RFC3849].
[2] 2001:0DB8:：/32已被指定为不可路由的范围，用于文档编制[RFC3849]。
[3] 2002::/16 is reserved for use in 6to4 deployments [RFC3056]
[3] 2002::/16 is reserved for use in 6to4 deployments [RFC3056]
[4] 3FFE::/16 is an experimental allocation to the 6BONE [RFC2471]. This prefix will be returned to the unassigned address pool on the 6th June 2006 [RFC3701].
[4] 3FFE:：/16是对6BONE[RFC2471]的实验性分配。此前缀将于2006年6月6日返回到未分配地址池[RFC3701]。
References:
参考资料：
[RFC2471] R. Hinden, R. Fink and J. Postel, "IPv6 Testing Address Allocation", RFC 2471, December 1998.
[RFC2471]R.Hinden，R.Fink和J.Postel，“IPv6测试地址分配”，RFC 24711998年12月。
[RFC2928] R. Hinden, S. Deering, R. Fink and T. Hain, "Initial IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.
[RFC2928]R.Hinden，S.Deering，R.Fink和T.Hain，“初始IPv6子TLA ID分配”，RFC 29282000年9月。
[RFC3056] B. Carpenter and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001.
[RFC3056]B.Carpenter和K.Moore，“通过IPv4云连接IPv6域”，RFC 3056，2001年2月。
[RFC3513] R. Hinden and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2003.
[RFC3513]R.Hinden和S.Deering，“互联网协议版本6（IPv6）寻址体系结构”，RFC 3513，2003年4月。
[RFC3701] R. Fink and R. Hinden, "6bone (IPv6 Testing Address Allocation) Phaseout", RFC 3701, March 2004.
[RFC3701]R.Fink和R.Hinden，“6bone（IPv6测试地址分配）逐步淘汰”，RFC 37012004年3月。
[RFC3849] G. Huston, A. Lord, A and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004.
[RFC3849]G.Huston，A.Lord，A和P.Smith，“为文档保留IPv6地址前缀”，RFC 3849，2004年7月。
-----------------------------------------------------
-----------------------------------------------------
Figure 2
图2
o The current registry name "iana-ipv6-tla-assignments" should be changed to "iana-ipv6-unicast-address-assignments".
o 当前注册表名“iana-ipv6-tla-assignments”应更改为“iana-ipv6-unicast-address-assignments”。
o The title of the registry has been altered to remove the reference to "TOP LEVEL AGGREGATION IDENTIFIER".
o 注册表的标题已更改，以删除对“顶级聚合标识符”的引用。
o The TLA and Sub-TLA identifier assignments have been rolled into a single set of address prefixes and their assignment.
o TLA和子TLA标识符分配已被合并为一组地址前缀及其分配。
o The text commentary at the start of the registry contents has been removed.
o 注册表内容开头的文字注释已删除。
o Binary value notation of the address prefixes has been removed.
o 已删除地址前缀的二进制值表示法。
o Further commentary on assignments, such as the planned phaseout of the 6BONE, is placed in a footnote.
o 关于任务的进一步评论，如计划逐步淘汰6BONE，见脚注。
o The registry continuation lines using ellipsis notation have been removed.
o 已删除使用省略号表示法的注册表延续行。
o Only assigned addresses are listed. All unassigned addresses, marked in the original IANA registry with the assignment note of "(future assignment)" have been removed, as has the entry marked "reserved *)".
o 仅列出分配的地址。所有未分配的地址，在原始IANA注册表中标记为“（未来分配）”的分配注释，以及标记为“保留*）”的条目，都已被删除。
o Address assignments are listed using prefix size notation of the actual allocation, rather than reporting the allocation in sub-units of /23 prefixes.
o 地址分配使用实际分配的前缀大小表示法列出，而不是以/23前缀的子单位报告分配。
o The date of the IANA action includes the day of the month as well as the month and year.
o IANA行动的日期包括每月的日期以及月份和年份。
IANA is advised to adopt these formats for the IPv6 address registry and the IPv6 Global Unicast address registry.
建议IANA对IPv6地址注册表和IPv6全局单播地址注册表采用这些格式。
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 reference from the IANA address registry to the RIR, and a trustable reference from the RIR's registry to a Local Internet Registry or end-user Internet Service Provider.
Internet路由系统的安全性依赖于对地址块的唯一控制断言进行身份验证的能力。验证此类断言的措施依赖于验证地址块是否构成现有分配地址块的一部分，以及是否存在从IANA地址注册表到RIR的可信引用，以及从RIR注册表到本地Internet注册表或最终用户Internet服务提供商的可信引用。
The proposed format for the IANA registry is a small step towards the creation of a registry 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注册表发布格式，以及使用文件签名和相关证书机制，以允许应用程序确认注册表内容是最新的，并且已由IANA发布。
This document was prepared with the assistance of Kurt Lindqvist, Thomas Narten, Paul Wilson, David Kessens, Bob Hinden and Brian Haberman. Pekka Savola, Brian Carpenter, Christian Huitema and Michael Patton provided helpful review comments.
本文件由库尔特·林克维斯特、托马斯·纳滕、保罗·威尔逊、大卫·凯森斯、鲍勃·欣登和布赖恩·哈伯曼协助编写。佩卡·萨沃拉、布赖恩·卡彭特、克里斯蒂安·惠特马和迈克尔·巴顿提供了有益的评论。
[RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2003.
[RFC3513]Hinden，R.和S.Deering，“互联网协议版本6（IPv6）寻址体系结构”，RFC 3513，2003年4月。
[iana-ipv6-registry] IANA, "IANA IPv6 Address Registry", December 2004.
[iana-ipv6-registry]iana，“iana ipv6地址注册表”，2004年12月。
[iana-ipv6-tla] IANA, "IANA Registry of IPv6 Top Level Aggregation Identifier Assignments", December 2004.
[iana-ipv6-tla]iana，“ipv6顶级聚合标识符分配的iana注册”，2004年12月。
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 Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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编辑功能的资金目前由互联网协会提供。