Network Working Group R. Hinden
Request for Comments: 4291 Nokia
Obsoletes: 3513 S. Deering
Category: Standards Track Cisco Systems
February 2006
Network Working Group R. Hinden
Request for Comments: 4291 Nokia
Obsoletes: 3513 S. Deering
Category: Standards Track Cisco Systems
February 2006
IP Version 6 Addressing Architecture
IP版本6寻址体系结构
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.
本规范定义了IP版本6（IPv6）协议的寻址体系结构。该文档包括IPv6寻址模型、IPv6地址的文本表示、IPv6单播地址、选播地址和多播地址的定义，以及IPv6节点所需的地址。
This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture".
本文件废除了RFC 3513“IP版本6寻址体系结构”。
Table of Contents
目录
1. Introduction ....................................................2
2. IPv6 Addressing .................................................2
2.1. Addressing Model ...........................................3
2.2. Text Representation of Addresses ...........................4
2.3. Text Representation of Address Prefixes ....................5
2.4. Address Type Identification ................................6
2.5. Unicast Addresses ..........................................6
2.5.1. Interface Identifiers ...............................7
2.5.2. The Unspecified Address .............................9
2.5.3. The Loopback Address ................................9
2.5.4. Global Unicast Addresses ............................9
2.5.5. IPv6 Addresses with Embedded IPv4 Addresses ........10
2.5.6. Link-Local IPv6 Unicast Addresses ..................11
2.5.7. Site-Local IPv6 Unicast Addresses ..................11
2.6. Anycast Addresses .........................................12
2.6.1. Required Anycast Address ...........................12
2.7. Multicast Addresses .......................................13
2.7.1. Pre-Defined Multicast Addresses ....................15
2.8. A Node's Required Addresses ...............................17
3. Security Considerations ........................................18
4. IANA Considerations ............................................18
5. Acknowledgements ...............................................18
6. References .....................................................18
6.1. Normative References ......................................18
6.2. Informative References ....................................18
Appendix A: Creating Modified EUI-64 Format Interface Identifiers .20
Appendix B: Changes from RFC 3513 .................................22
1. Introduction ....................................................2
2. IPv6 Addressing .................................................2
2.1. Addressing Model ...........................................3
2.2. Text Representation of Addresses ...........................4
2.3. Text Representation of Address Prefixes ....................5
2.4. Address Type Identification ................................6
2.5. Unicast Addresses ..........................................6
2.5.1. Interface Identifiers ...............................7
2.5.2. The Unspecified Address .............................9
2.5.3. The Loopback Address ................................9
2.5.4. Global Unicast Addresses ............................9
2.5.5. IPv6 Addresses with Embedded IPv4 Addresses ........10
2.5.6. Link-Local IPv6 Unicast Addresses ..................11
2.5.7. Site-Local IPv6 Unicast Addresses ..................11
2.6. Anycast Addresses .........................................12
2.6.1. Required Anycast Address ...........................12
2.7. Multicast Addresses .......................................13
2.7.1. Pre-Defined Multicast Addresses ....................15
2.8. A Node's Required Addresses ...............................17
3. Security Considerations ........................................18
4. IANA Considerations ............................................18
5. Acknowledgements ...............................................18
6. References .....................................................18
6.1. Normative References ......................................18
6.2. Informative References ....................................18
Appendix A: Creating Modified EUI-64 Format Interface Identifiers .20
Appendix B: Changes from RFC 3513 .................................22
This specification defines the addressing architecture of the IP Version 6 protocol. It includes the basic formats for the various types of IPv6 addresses (unicast, anycast, and multicast).
本规范定义了IP版本6协议的寻址体系结构。它包括各种类型的IPv6地址（单播、选播和多播）的基本格式。
IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces (where "interface" is as defined in Section 2 of [IPV6]). There are three types of addresses:
IPv6地址是接口和接口集的128位标识符（其中“接口”的定义见[IPv6]第2节）。有三种类型的地址：
Unicast: An identifier for a single interface. A packet sent to a unicast address is delivered to the interface identified by that address.
单播：单个接口的标识符。发送到单播地址的数据包被发送到由该地址标识的接口。
Anycast: An identifier for a set of interfaces (typically belonging to different nodes). A packet sent to an anycast address is delivered to one of the interfaces identified by that address (the "nearest" one, according to the routing protocols' measure of distance).
选播：一组接口（通常属于不同节点）的标识符。发送到选播地址的数据包被发送到该地址标识的接口之一（根据路由协议的距离度量，“最近的”接口）。
Multicast: An identifier for a set of interfaces (typically belonging to different nodes). A packet sent to a multicast address is delivered to all interfaces identified by that address.
多播：一组接口（通常属于不同节点）的标识符。发送到多播地址的数据包被发送到该地址标识的所有接口。
There are no broadcast addresses in IPv6, their function being superseded by multicast addresses.
IPv6中没有广播地址，它们的功能被多播地址取代。
In this document, fields in addresses are given a specific name, for example, "subnet". When this name is used with the term "ID" for identifier after the name (e.g., "subnet ID"), it refers to the contents of the named field. When it is used with the term "prefix" (e.g., "subnet prefix"), it refers to all of the address from the left up to and including this field.
在本文档中，地址中的字段有一个特定的名称，例如“子网”。当此名称与名称后的标识符术语“ID”（例如，“子网ID”）一起使用时，它指的是命名字段的内容。当它与术语“前缀”（例如，“子网前缀”）一起使用时，它指的是从左到右的所有地址，包括该字段。
In IPv6, all zeros and all ones are legal values for any field, unless specifically excluded. Specifically, prefixes may contain, or end with, zero-valued fields.
在IPv6中，除非明确排除，否则所有0和1都是任何字段的合法值。具体来说，前缀可能包含零值字段，或以零值字段结尾。
IPv6 addresses of all types are assigned to interfaces, not nodes. An IPv6 unicast address refers to a single interface. Since each interface belongs to a single node, any of that node's interfaces' unicast addresses may be used as an identifier for the node.
所有类型的IPv6地址都分配给接口，而不是节点。IPv6单播地址指单个接口。由于每个接口属于单个节点，因此该节点的任何接口的单播地址都可以用作该节点的标识符。
All interfaces are required to have at least one Link-Local unicast address (see Section 2.8 for additional required addresses). A single interface may also have multiple IPv6 addresses of any type (unicast, anycast, and multicast) or scope. Unicast addresses with a scope greater than link-scope are not needed for interfaces that are not used as the origin or destination of any IPv6 packets to or from non-neighbors. This is sometimes convenient for point-to-point interfaces. There is one exception to this addressing model:
所有接口都要求至少有一个链路本地单播地址（其他所需地址见第2.8节）。单个接口还可以具有任意类型（单播、选播和多播）或作用域的多个IPv6地址。对于不用作任何IPv6数据包到非邻居或来自非邻居的源或目标的接口，不需要作用域大于链路作用域的单播地址。这对于点到点接口有时很方便。此寻址模型有一个例外：
A unicast address or a set of unicast addresses may be assigned to multiple physical interfaces if the implementation treats the multiple physical interfaces as one interface when presenting it to the internet layer. This is useful for load-sharing over multiple physical interfaces.
如果实现在将多个物理接口呈现给因特网层时将其视为一个接口，则可以将单播地址或一组单播地址分配给多个物理接口。这对于多个物理接口上的负载共享非常有用。
Currently, IPv6 continues the IPv4 model in that a subnet prefix is associated with one link. Multiple subnet prefixes may be assigned to the same link.
目前，IPv6延续了IPv4模式，即子网前缀与一条链路相关联。可以为同一链路分配多个子网前缀。
There are three conventional forms for representing IPv6 addresses as text strings:
将IPv6地址表示为文本字符串有三种常规形式：
1. The preferred form is x:x:x:x:x:x:x:x, where the 'x's are one to four hexadecimal digits of the eight 16-bit pieces of the address. Examples:
1. 首选形式是x:x:x:x:x:x:x:x:x，其中“x”是八个16位地址的一到四个十六进制数字。示例：
ABCD:EF01:2345:6789:ABCD:EF01:2345:6789
ABCD:EF01:2345:6789:ABCD:EF01:2345:6789
2001:DB8:0:0:8:800:200C:417A
2001:DB8:0:0:8:800:200C:417A
Note that it is not necessary to write the leading zeros in an individual field, but there must be at least one numeral in every field (except for the case described in 2.).
请注意，无需在单个字段中写入前导零，但每个字段中必须至少有一个数字（2.中描述的情况除外）。
2. Due to some methods of allocating certain styles of IPv6 addresses, it will be common for addresses to contain long strings of zero bits. In order to make writing addresses containing zero bits easier, a special syntax is available to compress the zeros. The use of "::" indicates one or more groups of 16 bits of zeros. The "::" can only appear once in an address. The "::" can also be used to compress leading or trailing zeros in an address.
2. 由于某些分配特定类型IPv6地址的方法，地址通常包含长的零位字符串。为了便于写入包含零位的地址，可以使用一种特殊语法来压缩零。使用“：”表示一组或多组16位零。“：：”在地址中只能出现一次。“：：”还可用于压缩地址中的前导或尾随零。
For example, the following addresses
例如，以下地址
2001:DB8:0:0:8:800:200C:417A a unicast address
FF01:0:0:0:0:0:0:101 a multicast address
0:0:0:0:0:0:0:1 the loopback address
0:0:0:0:0:0:0:0 the unspecified address
2001:DB8:0:0:8:800:200C:417A a unicast address
FF01:0:0:0:0:0:0:101 a multicast address
0:0:0:0:0:0:0:1 the loopback address
0:0:0:0:0:0:0:0 the unspecified address
may be represented as
可代表为
2001:DB8::8:800:200C:417A a unicast address
FF01::101 a multicast address
::1 the loopback address
:: the unspecified address
2001:DB8::8:800:200C:417A a unicast address
FF01::101 a multicast address
::1 the loopback address
:: the unspecified address
3. An alternative form that is sometimes more convenient when dealing with a mixed environment of IPv4 and IPv6 nodes is x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal values of the six high-order 16-bit pieces of the address, and the 'd's are
3. 在处理IPv4和IPv6节点的混合环境时，有时更方便的另一种形式是x:x:x:x:x:x:d.d.d.d，其中“x”是地址的六个高阶16位段的十六进制值，“d”是
the decimal values of the four low-order 8-bit pieces of the address (standard IPv4 representation). Examples:
地址的四个低阶8位片段的十进制值（标准IPv4表示）。示例：
0:0:0:0:0:0:13.1.68.3
0:0:0:0:0:0:13.1.68.3
0:0:0:0:0:FFFF:129.144.52.38
0:0:0:0:0:FFFF:129.144.52.38
or in compressed form:
或以压缩形式：
::13.1.68.3
::13.1.68.3
::FFFF:129.144.52.38
::FFFF:129.144.52.38
The text representation of IPv6 address prefixes is similar to the way IPv4 address prefixes are written in Classless Inter-Domain Routing (CIDR) notation [CIDR]. An IPv6 address prefix is represented by the notation:
IPv6地址前缀的文本表示方式类似于IPv4地址前缀以无类域间路由（CIDR）表示法[CIDR]编写的方式。IPv6地址前缀由以下符号表示：
ipv6-address/prefix-length
ipv6地址/前缀长度
where
哪里
ipv6-address is an IPv6 address in any of the notations listed in Section 2.2.
ipv6地址是第2.2节中列出的任何符号中的ipv6地址。
prefix-length is a decimal value specifying how many of the leftmost contiguous bits of the address comprise the prefix.
prefix length是一个十进制值，指定地址最左边的连续位中有多少位组成前缀。
For example, the following are legal representations of the 60-bit prefix 20010DB80000CD3 (hexadecimal):
例如，以下是60位前缀20010DB80000CD3（十六进制）的法律表示：
2001:0DB8:0000:CD30:0000:0000:0000:0000/60
2001:0DB8::CD30:0:0:0:0/60
2001:0DB8:0:CD30::/60
2001:0DB8:0000:CD30:0000:0000:0000:0000/60
2001:0DB8::CD30:0:0:0:0/60
2001:0DB8:0:CD30::/60
The following are NOT legal representations of the above prefix:
以下内容不是上述前缀的法律陈述：
2001:0DB8:0:CD3/60 may drop leading zeros, but not trailing
zeros, within any 16-bit chunk of the address
2001:0DB8:0:CD3/60 may drop leading zeros, but not trailing
zeros, within any 16-bit chunk of the address
2001:0DB8::CD30/60 address to left of "/" expands to
2001:0DB8:0000:0000:0000:0000:0000:CD30
2001:0DB8::CD30/60 address to left of "/" expands to
2001:0DB8:0000:0000:0000:0000:0000:CD30
2001:0DB8::CD3/60 address to left of "/" expands to
2001:0DB8:0000:0000:0000:0000:0000:0CD3
2001:0DB8::CD3/60 address to left of "/" expands to
2001:0DB8:0000:0000:0000:0000:0000:0CD3
When writing both a node address and a prefix of that node address (e.g., the node's subnet prefix), the two can be combined as follows:
写入节点地址和该节点地址的前缀（例如，节点的子网前缀）时，可按如下方式将两者结合：
the node address 2001:0DB8:0:CD30:123:4567:89AB:CDEF
and its subnet number 2001:0DB8:0:CD30::/60
the node address 2001:0DB8:0:CD30:123:4567:89AB:CDEF
and its subnet number 2001:0DB8:0:CD30::/60
can be abbreviated as 2001:0DB8:0:CD30:123:4567:89AB:CDEF/60
can be abbreviated as 2001:0DB8:0:CD30:123:4567:89AB:CDEF/60
The type of an IPv6 address is identified by the high-order bits of the address, as follows:
IPv6地址的类型由地址的高位标识，如下所示：
Address type Binary prefix IPv6 notation Section
------------ ------------- ------------- -------
Unspecified 00...0 (128 bits) ::/128 2.5.2
Loopback 00...1 (128 bits) ::1/128 2.5.3
Multicast 11111111 FF00::/8 2.7
Link-Local unicast 1111111010 FE80::/10 2.5.6
Global Unicast (everything else)
Address type Binary prefix IPv6 notation Section
------------ ------------- ------------- -------
Unspecified 00...0 (128 bits) ::/128 2.5.2
Loopback 00...1 (128 bits) ::1/128 2.5.3
Multicast 11111111 FF00::/8 2.7
Link-Local unicast 1111111010 FE80::/10 2.5.6
Global Unicast (everything else)
Anycast addresses are taken from the unicast address spaces (of any scope) and are not syntactically distinguishable from unicast addresses.
选播地址取自单播地址空间（任何范围），在语法上与单播地址不可区分。
The general format of Global Unicast addresses is described in Section 2.5.4. Some special-purpose subtypes of Global Unicast addresses that contain embedded IPv4 addresses (for the purposes of IPv4-IPv6 interoperation) are described in Section 2.5.5.
第2.5.4节描述了全局单播地址的一般格式。第2.5.5节描述了包含嵌入式IPv4地址（用于IPv4-IPv6互操作）的一些特殊用途的全局单播地址子类型。
Future specifications may redefine one or more sub-ranges of the Global Unicast space for other purposes, but unless and until that happens, implementations must treat all addresses that do not start with any of the above-listed prefixes as Global Unicast addresses.
未来的规范可能会出于其他目的重新定义全局单播空间的一个或多个子范围，但除非发生这种情况，否则实现必须将所有不以上述任何前缀开头的地址视为全局单播地址。
IPv6 unicast addresses are aggregatable with prefixes of arbitrary bit-length, similar to IPv4 addresses under Classless Inter-Domain Routing.
IPv6单播地址可以使用任意位长度的前缀进行聚合，类似于无类域间路由下的IPv4地址。
There are several types of unicast addresses in IPv6, in particular, Global Unicast, site-local unicast (deprecated, see Section 2.5.7), and Link-Local unicast. There are also some special-purpose subtypes of Global Unicast, such as IPv6 addresses with embedded IPv4 addresses. Additional address types or subtypes can be defined in the future.
IPv6中有几种类型的单播地址，特别是全局单播、站点本地单播（已弃用，请参见第2.5.7节）和链路本地单播。还有一些特殊用途的全局单播子类型，例如带有嵌入式IPv4地址的IPv6地址。以后可以定义其他地址类型或子类型。
IPv6 nodes may have considerable or little knowledge of the internal structure of the IPv6 address, depending on the role the node plays (for instance, host versus router). At a minimum, a node may consider that unicast addresses (including its own) have no internal structure:
IPv6节点可能对IPv6地址的内部结构有相当多或很少的了解，这取决于节点所扮演的角色（例如，主机与路由器）。至少，节点可以考虑单播地址（包括其自身）没有内部结构：
| 128 bits |
+-----------------------------------------------------------------+
| node address |
+-----------------------------------------------------------------+
| 128 bits |
+-----------------------------------------------------------------+
| node address |
+-----------------------------------------------------------------+
A slightly sophisticated host (but still rather simple) may additionally be aware of subnet prefix(es) for the link(s) it is attached to, where different addresses may have different values for n:
稍微复杂的主机（但仍然相当简单）还可能知道其连接到的链路的子网前缀，其中不同的地址可能具有不同的n值：
| n bits | 128-n bits |
+-------------------------------+---------------------------------+
| subnet prefix | interface ID |
+-------------------------------+---------------------------------+
| n bits | 128-n bits |
+-------------------------------+---------------------------------+
| subnet prefix | interface ID |
+-------------------------------+---------------------------------+
Though a very simple router may have no knowledge of the internal structure of IPv6 unicast addresses, routers will more generally have knowledge of one or more of the hierarchical boundaries for the operation of routing protocols. The known boundaries will differ from router to router, depending on what positions the router holds in the routing hierarchy.
虽然一个非常简单的路由器可能不知道IPv6单播地址的内部结构，但路由器通常会知道路由协议操作的一个或多个层次边界。根据路由器在路由层次结构中所处的位置，路由器之间的已知边界会有所不同。
Except for the knowledge of the subnet boundary discussed in the previous paragraphs, nodes should not make any assumptions about the structure of an IPv6 address.
除了前面段落中讨论的子网边界知识外，节点不应对IPv6地址的结构进行任何假设。
Interface identifiers in IPv6 unicast addresses are used to identify interfaces on a link. They are required to be unique within a subnet prefix. It is recommended that the same interface identifier not be assigned to different nodes on a link. They may also be unique over a broader scope. In some cases, an interface's identifier will be derived directly from that interface's link-layer address. The same interface identifier may be used on multiple interfaces on a single node, as long as they are attached to different subnets.
IPv6单播地址中的接口标识符用于标识链路上的接口。它们在子网前缀中必须是唯一的。建议不要将同一接口标识符分配给链路上的不同节点。在更广泛的范围内，它们也可能是独一无二的。在某些情况下，接口的标识符将直接从该接口的链接层地址派生。同一接口标识符可用于单个节点上的多个接口，只要它们连接到不同的子网。
Note that the uniqueness of interface identifiers is independent of the uniqueness of IPv6 addresses. For example, a Global Unicast address may be created with a local scope interface identifier and a Link-Local address may be created with a universal scope interface identifier.
请注意，接口标识符的唯一性与IPv6地址的唯一性无关。例如，可以使用本地作用域接口标识符创建全局单播地址，并且可以使用通用作用域接口标识符创建链路本地地址。
For all unicast addresses, except those that start with the binary value 000, Interface IDs are required to be 64 bits long and to be constructed in Modified EUI-64 format.
对于所有单播地址（以二进制值000开头的地址除外），接口ID要求为64位长，并以修改的EUI-64格式构造。
Modified EUI-64 format-based interface identifiers may have universal scope when derived from a universal token (e.g., IEEE 802 48-bit MAC or IEEE EUI-64 identifiers [EUI64]) or may have local scope where a global token is not available (e.g., serial links, tunnel end-points) or where global tokens are undesirable (e.g., temporary tokens for privacy [PRIV]).
当从通用令牌（例如，IEEE 802 48位MAC或IEEE EUI-64标识符[EUI64]）派生时，修改的基于EUI-64格式的接口标识符可能具有通用范围，或者可能具有全局令牌不可用（例如，串行链路、隧道端点）或全局令牌不需要的局部范围（例如，隐私临时代币[PRIV]）。
Modified EUI-64 format interface identifiers are formed by inverting the "u" bit (universal/local bit in IEEE EUI-64 terminology) when forming the interface identifier from IEEE EUI-64 identifiers. In the resulting Modified EUI-64 format, the "u" bit is set to one (1) to indicate universal scope, and it is set to zero (0) to indicate local scope. The first three octets in binary of an IEEE EUI-64 identifier are as follows:
当从IEEE EUI-64标识符形成接口标识符时，通过反转“u”位（IEEE EUI-64术语中的通用/本地位）形成修改的EUI-64格式接口标识符。在修改后的EUI-64格式中，“u”位设置为一（1）表示通用范围，设置为零（0）表示局部范围。IEEE EUI-64标识符的前三个二进制八位字节如下：
0 0 0 1 1 2
|0 7 8 5 6 3|
+----+----+----+----+----+----+
|cccc|ccug|cccc|cccc|cccc|cccc|
+----+----+----+----+----+----+
0 0 0 1 1 2
|0 7 8 5 6 3|
+----+----+----+----+----+----+
|cccc|ccug|cccc|cccc|cccc|cccc|
+----+----+----+----+----+----+
written in Internet standard bit-order, where "u" is the universal/local bit, "g" is the individual/group bit, and "c" is the bits of the company_id. Appendix A, "Creating Modified EUI-64 Format Interface Identifiers", provides examples on the creation of Modified EUI-64 format-based interface identifiers.
以互联网标准位顺序编写，其中“u”是通用/本地位，“g”是单个/组位，“c”是公司id的位。附录A“创建修改的EUI-64格式接口标识符”提供了创建修改的EUI-64格式接口标识符的示例。
The motivation for inverting the "u" bit when forming an interface identifier is to make it easy for system administrators to hand configure non-global identifiers when hardware tokens are not available. This is expected to be the case for serial links and tunnel end-points, for example. The alternative would have been for these to be of the form 0200:0:0:1, 0200:0:0:2, etc., instead of the much simpler 0:0:0:1, 0:0:0:2, etc.
在形成接口标识符时反转“u”位的动机是，当硬件令牌不可用时，系统管理员可以轻松地手动配置非全局标识符。例如，对于串行链路和隧道端点，预计情况就是如此。另一种选择是，它们的形式为0200:0:0:1、0200:0:0:2等，而不是更简单的0:0:0:1、0:0:0:2等。
IPv6 nodes are not required to validate that interface identifiers created with modified EUI-64 tokens with the "u" bit set to universal are unique.
IPv6节点无需验证使用“u”位设置为universal的修改过的EUI-64令牌创建的接口标识符是否唯一。
The use of the universal/local bit in the Modified EUI-64 format identifier is to allow development of future technology that can take advantage of interface identifiers with universal scope.
在修改后的EUI-64格式标识符中使用通用/本地位是为了开发未来技术，该技术可以利用具有通用范围的接口标识符。
The details of forming interface identifiers are defined in the appropriate "IPv6 over <link>" specification, such as "IPv6 over Ethernet" [ETHER], and "IPv6 over FDDI" [FDDI].
形成接口标识符的详细信息在适当的“IPv6 over<link>”规范中定义，例如“IPv6 over Ethernet”[Ethernet]和“IPv6 over FDDI”[FDDI]。
The address 0:0:0:0:0:0:0:0 is called the unspecified address. It must never be assigned to any node. It indicates the absence of an address. One example of its use is in the Source Address field of any IPv6 packets sent by an initializing host before it has learned its own address.
地址0:0:0:0:0:0:0:0称为未指定地址。决不能将其分配给任何节点。它表示没有地址。它的一个使用示例是在初始化主机读入自己的地址之前发送的任何IPv6数据包的源地址字段中。
The unspecified address must not be used as the destination address of IPv6 packets or in IPv6 Routing headers. An IPv6 packet with a source address of unspecified must never be forwarded by an IPv6 router.
未指定的地址不得用作IPv6数据包的目标地址或在IPv6路由标头中使用。源地址为未指定的IPv6数据包决不能由IPv6路由器转发。
The unicast address 0:0:0:0:0:0:0:1 is called the loopback address. It may be used by a node to send an IPv6 packet to itself. It must not be assigned to any physical interface. It is treated as having Link-Local scope, and may be thought of as the Link-Local unicast address of a virtual interface (typically called the "loopback interface") to an imaginary link that goes nowhere.
单播地址0:0:0:0:0:0:0:0:1称为环回地址。节点可以使用它向自身发送IPv6数据包。不得将其分配给任何物理接口。它被视为具有链路本地作用域，并且可以被认为是虚拟接口（通常称为“环回接口”）到无处可去的假想链路的链路本地单播地址。
The loopback address must not be used as the source address in IPv6 packets that are sent outside of a single node. An IPv6 packet with a destination address of loopback must never be sent outside of a single node and must never be forwarded by an IPv6 router. A packet received on an interface with a destination address of loopback must be dropped.
环回地址不得用作在单个节点外部发送的IPv6数据包中的源地址。目标地址为环回的IPv6数据包不得发送到单个节点之外，也不得由IPv6路由器转发。必须丢弃在目标地址为环回的接口上接收的数据包。
The general format for IPv6 Global Unicast addresses is as follows:
IPv6全局单播地址的一般格式如下：
| n bits | m bits | 128-n-m bits |
+------------------------+-----------+----------------------------+
| global routing prefix | subnet ID | interface ID |
+------------------------+-----------+----------------------------+
| n bits | m bits | 128-n-m bits |
+------------------------+-----------+----------------------------+
| global routing prefix | subnet ID | interface ID |
+------------------------+-----------+----------------------------+
where the global routing prefix is a (typically hierarchically-structured) value assigned to a site (a cluster of subnets/links), the subnet ID is an identifier of a link within the site, and the interface ID is as defined in Section 2.5.1.
如果全局路由前缀是分配给站点（子网/链路集群）的值（通常为分层结构），则子网ID是站点内链路的标识符，接口ID如第2.5.1节所定义。
All Global Unicast addresses other than those that start with binary 000 have a 64-bit interface ID field (i.e., n + m = 64), formatted as described in Section 2.5.1. Global Unicast addresses that start with binary 000 have no such constraint on the size or structure of the interface ID field.
除以二进制000开头的地址外，所有全局单播地址都有一个64位接口ID字段（即n+m=64），格式如第2.5.1节所述。以二进制000开头的全局单播地址对接口ID字段的大小或结构没有这样的约束。
Examples of Global Unicast addresses that start with binary 000 are the IPv6 address with embedded IPv4 addresses described in Section 2.5.5. An example of global addresses starting with a binary value other than 000 (and therefore having a 64-bit interface ID field) can be found in [GLOBAL].
以二进制000开头的全局单播地址的示例是第2.5.5节中描述的带有嵌入式IPv4地址的IPv6地址。在[global]中可以找到以除000以外的二进制值开始的全局地址示例（因此具有64位接口ID字段）。
Two types of IPv6 addresses are defined that carry an IPv4 address in the low-order 32 bits of the address. These are the "IPv4-Compatible IPv6 address" and the "IPv4-mapped IPv6 address".
定义了两种类型的IPv6地址，它们以地址的低位32位携带IPv4地址。这些是“IPv4兼容IPv6地址”和“IPv4映射IPv6地址”。
The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6 transition. The format of the "IPv4-Compatible IPv6 address" is as follows:
“IPv4兼容IPv6地址”的定义有助于IPv6转换。“IPv4兼容IPv6地址”的格式如下：
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" must be a globally-unique IPv4 unicast address.
注意：“IPv4兼容IPv6地址”中使用的IPv4地址必须是全局唯一的IPv4单播地址。
The "IPv4-Compatible IPv6 address" is now deprecated because the current IPv6 transition mechanisms no longer use these addresses. New or updated implementations are not required to support this address type.
“IPv4兼容IPv6地址”现在已被弃用，因为当前的IPv6转换机制不再使用这些地址。支持此地址类型不需要新的或更新的实现。
A second type of IPv6 address that holds an embedded IPv4 address is defined. This address type is used to represent the addresses of IPv4 nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 address" is as follows:
定义了第二种类型的IPv6地址，该地址包含嵌入的IPv4地址。此地址类型用于将IPv4节点的地址表示为IPv6地址。“IPv4映射IPv6地址”的格式如下：
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+
See [RFC4038] for background on the usage of the "IPv4-mapped IPv6 address".
有关“IPv4映射IPv6地址”使用的背景信息，请参见[RFC4038]。
Link-Local addresses are for use on a single link. Link-Local addresses have the following format:
链路本地地址用于单个链路。链接本地地址具有以下格式：
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
Link-Local addresses are designed to be used for addressing on a single link for purposes such as automatic address configuration, neighbor discovery, or when no routers are present.
链路本地地址设计用于在单个链路上寻址，用于自动地址配置、邻居发现或不存在路由器时。
Routers must not forward any packets with Link-Local source or destination addresses to other links.
路由器不得将带有链路本地源地址或目标地址的任何数据包转发到其他链路。
Site-Local addresses were originally designed to be used for addressing inside of a site without the need for a global prefix. Site-local addresses are now deprecated as defined in [SLDEP].
站点本地地址最初设计用于在站点内部寻址，而不需要全局前缀。站点本地地址现在已被弃用，如[SLDEP]中所定义。
Site-Local addresses have the following format:
站点本地地址的格式如下：
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111011| subnet ID | interface ID |
+----------+-------------------------+----------------------------+
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111011| subnet ID | interface ID |
+----------+-------------------------+----------------------------+
The special behavior of this prefix defined in [RFC3513] must no longer be supported in new implementations (i.e., new implementations must treat this prefix as Global Unicast).
[RFC3513]中定义的此前缀的特殊行为在新实现中不得再受支持（即，新实现必须将此前缀视为全局单播）。
Existing implementations and deployments may continue to use this prefix.
现有的实现和部署可能会继续使用此前缀。
An IPv6 anycast address is an address that is assigned to more than one interface (typically belonging to different nodes), with the property that a packet sent to an anycast address is routed to the "nearest" interface having that address, according to the routing protocols' measure of distance.
IPv6选播地址是分配给多个接口（通常属于不同节点）的地址，其特性是根据路由协议的距离度量，发送到选播地址的数据包被路由到具有该地址的“最近”接口。
Anycast addresses are allocated from the unicast address space, using any of the defined unicast address formats. Thus, anycast addresses are syntactically indistinguishable from unicast addresses. When a unicast address is assigned to more than one interface, thus turning it into an anycast address, the nodes to which the address is assigned must be explicitly configured to know that it is an anycast address.
使用任何定义的单播地址格式，从单播地址空间分配选播地址。因此，选播地址在语法上与单播地址无法区分。当一个单播地址分配给多个接口，从而将其转换为选播地址时，分配该地址的节点必须明确配置为知道它是选播地址。
For any assigned anycast address, there is a longest prefix P of that address that identifies the topological region in which all interfaces belonging to that anycast address reside. Within the region identified by P, the anycast address must be maintained as a separate entry in the routing system (commonly referred to as a "host route"); outside the region identified by P, the anycast address may be aggregated into the routing entry for prefix P.
对于任何分配的选播地址，该地址有一个最长前缀P，用于标识属于该选播地址的所有接口所在的拓扑区域。在P标识的区域内，选播地址必须作为路由系统中的一个单独条目进行维护（通常称为“主机路由”）；在由P标识的区域之外，选播地址可以聚合到前缀P的路由条目中。
Note that in the worst case, the prefix P of an anycast set may be the null prefix, i.e., the members of the set may have no topological locality. In that case, the anycast address must be maintained as a separate routing entry throughout the entire Internet, which presents a severe scaling limit on how many such "global" anycast sets may be supported. Therefore, it is expected that support for global anycast sets may be unavailable or very restricted.
注意，在最坏情况下，选播集的前缀P可以是空前缀，即，该集的成员可以没有拓扑局部性。在这种情况下，选播地址必须在整个互联网中作为一个单独的路由条目进行维护，这对支持多少这样的“全局”选播集提出了严格的扩展限制。因此，预计对全局选播集的支持可能不可用或非常有限。
One expected use of anycast addresses is to identify the set of routers belonging to an organization providing Internet service. Such addresses could be used as intermediate addresses in an IPv6 Routing header, to cause a packet to be delivered via a particular service provider or sequence of service providers.
选播地址的一个预期用途是识别属于提供因特网服务的组织的路由器集。这些地址可以用作IPv6路由报头中的中间地址，以使分组经由特定服务提供者或服务提供者序列来递送。
Some other possible uses are to identify the set of routers attached to a particular subnet, or the set of routers providing entry into a particular routing domain.
其他一些可能的用途是识别连接到特定子网的路由器集，或者识别进入特定路由域的路由器集。
The Subnet-Router anycast address is predefined. Its format is as follows:
子网路由器选播地址是预定义的。其格式如下：
| n bits | 128-n bits |
+------------------------------------------------+----------------+
| subnet prefix | 00000000000000 |
+------------------------------------------------+----------------+
| n bits | 128-n bits |
+------------------------------------------------+----------------+
| subnet prefix | 00000000000000 |
+------------------------------------------------+----------------+
The "subnet prefix" in an anycast address is the prefix that identifies a specific link. This anycast address is syntactically the same as a unicast address for an interface on the link with the interface identifier set to zero.
选播地址中的“子网前缀”是标识特定链路的前缀。该选播地址在语法上与接口标识符设置为零的链路上接口的单播地址相同。
Packets sent to the Subnet-Router anycast address will be delivered to one router on the subnet. All routers are required to support the Subnet-Router anycast addresses for the subnets to which they have interfaces.
发送到子网路由器选播地址的数据包将被发送到子网上的一个路由器。所有路由器都需要支持其具有接口的子网的子网路由器选播地址。
The Subnet-Router anycast address is intended to be used for applications where a node needs to communicate with any one of the set of routers.
子网路由器选播地址用于节点需要与路由器组中的任何一个进行通信的应用。
An IPv6 multicast address is an identifier for a group of interfaces (typically on different nodes). An interface may belong to any number of multicast groups. Multicast addresses have the following format:
IPv6多播地址是一组接口（通常在不同节点上）的标识符。一个接口可以属于任意数量的多播组。多播地址具有以下格式：
| 8 | 4 | 4 | 112 bits |
+------ -+----+----+---------------------------------------------+
|11111111|flgs|scop| group ID |
+--------+----+----+---------------------------------------------+
| 8 | 4 | 4 | 112 bits |
+------ -+----+----+---------------------------------------------+
|11111111|flgs|scop| group ID |
+--------+----+----+---------------------------------------------+
binary 11111111 at the start of the address identifies the address as being a multicast address.
地址开头的二进制11111将该地址标识为多播地址。
+-+-+-+-+
flgs is a set of 4 flags: |0|R|P|T|
+-+-+-+-+
+-+-+-+-+
flgs is a set of 4 flags: |0|R|P|T|
+-+-+-+-+
The high-order flag is reserved, and must be initialized to 0.
高阶标志是保留的，必须初始化为0。
T = 0 indicates a permanently-assigned ("well-known") multicast address, assigned by the Internet Assigned Numbers Authority (IANA).
T=0表示由Internet分配号码管理局（IANA）分配的永久分配（“已知”）多播地址。
T = 1 indicates a non-permanently-assigned ("transient" or "dynamically" assigned) multicast address.
T=1表示非永久分配（“瞬态”或“动态”分配）多播地址。
The P flag's definition and usage can be found in [RFC3306].
P标志的定义和用法见[RFC3306]。
The R flag's definition and usage can be found in [RFC3956].
R标志的定义和用法见[RFC3956]。
scop is a 4-bit multicast scope value used to limit the scope of the multicast group. The values are as follows:
scop是一个4位多播作用域值，用于限制多播组的作用域。数值如下：
0 reserved 1 Interface-Local scope 2 Link-Local scope 3 reserved 4 Admin-Local scope 5 Site-Local scope 6 (unassigned) 7 (unassigned) 8 Organization-Local scope 9 (unassigned) A (unassigned) B (unassigned) C (unassigned) D (unassigned) E Global scope F reserved
0保留1接口本地作用域2链接本地作用域3保留4管理员本地作用域5站点本地作用域6（未分配）7（未分配）8组织本地作用域9（未分配）A（未分配）B（未分配）C（未分配）D（未分配）E全局作用域F保留
Interface-Local scope spans only a single interface on a node and is useful only for loopback transmission of multicast.
接口局部作用域仅跨越节点上的单个接口，并且仅对多播的环回传输有用。
Link-Local multicast scope spans the same topological region as the corresponding unicast scope.
链路本地多播作用域跨越与相应单播作用域相同的拓扑区域。
Admin-Local scope is the smallest scope that must be administratively configured, i.e., not automatically derived from physical connectivity or other, non-multicast-related configuration.
Admin Local scope是必须进行管理配置的最小范围，即不能自动从物理连接或其他与多播无关的配置派生。
Site-Local scope is intended to span a single site.
现场局部范围旨在跨越单个现场。
Organization-Local scope is intended to span multiple sites belonging to a single organization.
组织本地范围旨在跨越属于单个组织的多个站点。
scopes labeled "(unassigned)" are available for administrators to define additional multicast regions.
标记为“（未分配）”的作用域可供管理员定义其他多播区域。
group ID identifies the multicast group, either permanent or transient, within the given scope. Additional definitions of the multicast group ID field structure are provided in [RFC3306].
组ID标识给定范围内的永久或暂时多播组。[RFC3306]中提供了多播组ID字段结构的其他定义。
The "meaning" of a permanently-assigned multicast address is independent of the scope value. For example, if the "NTP servers group" is assigned a permanent multicast address with a group ID of 101 (hex), then
永久分配的多播地址的“含义”与作用域值无关。例如，如果为“NTP服务器组”分配了组ID为101（十六进制）的永久多播地址，则
FF01:0:0:0:0:0:0:101 means all NTP servers on the same interface (i.e., the same node) as the sender.
FF01:0:0:0:0:0:0:101表示与发送方位于同一接口（即同一节点）上的所有NTP服务器。
FF02:0:0:0:0:0:0:101 means all NTP servers on the same link as the sender.
FF02:0:0:0:0:0:0:101表示与发送方位于同一链路上的所有NTP服务器。
FF05:0:0:0:0:0:0:101 means all NTP servers in the same site as the sender.
FF05:0:0:0:0:0:0:101表示与发送方位于同一站点中的所有NTP服务器。
FF0E:0:0:0:0:0:0:101 means all NTP servers in the Internet.
FF0E:0:0:0:0:0:0:101表示Internet上的所有NTP服务器。
Non-permanently-assigned multicast addresses are meaningful only within a given scope. For example, a group identified by the non-permanent, site-local multicast address FF15:0:0:0:0:0:0:101 at one site bears no relationship to a group using the same address at a different site, nor to a non-permanent group using the same group ID with a different scope, nor to a permanent group with the same group ID.
非永久分配的多播地址仅在给定范围内有意义。例如，一个站点上由非永久性站点本地多播地址FF15:0:0:0:0:101标识的组与在不同站点使用相同地址的组、使用不同作用域的相同组ID的非永久性组以及具有相同组ID的永久性组没有关系。
Multicast addresses must not be used as source addresses in IPv6 packets or appear in any Routing header.
多播地址不得用作IPv6数据包中的源地址，也不得出现在任何路由标头中。
Routers must not forward any multicast packets beyond of the scope indicated by the scop field in the destination multicast address.
路由器不得转发超出目标多播地址中scop字段指示范围的任何多播数据包。
Nodes must not originate a packet to a multicast address whose scop field contains the reserved value 0; if such a packet is received, it must be silently dropped. Nodes should not originate a packet to a multicast address whose scop field contains the reserved value F; if such a packet is sent or received, it must be treated the same as packets destined to a global (scop E) multicast address.
节点不得向scop字段包含保留值0的多播地址发起数据包；如果接收到这样的数据包，则必须悄悄地丢弃它。节点不应向scop字段包含保留值F的多播地址发起数据包；如果发送或接收此类数据包，则必须将其视为发送到全局（scop E）多播地址的数据包。
The following well-known multicast addresses are pre-defined. The group IDs defined in this section are defined for explicit scope values.
以下众所周知的多播地址是预定义的。本节中定义的组ID是为显式范围值定义的。
Use of these group IDs for any other scope values, with the T flag equal to 0, is not allowed.
不允许将这些组ID用于T标志等于0的任何其他范围值。
Reserved Multicast Addresses: FF00:0:0:0:0:0:0:0
FF01:0:0:0:0:0:0:0
FF02:0:0:0:0:0:0:0
FF03:0:0:0:0:0:0:0
FF04:0:0:0:0:0:0:0
FF05:0:0:0:0:0:0:0
FF06:0:0:0:0:0:0:0
FF07:0:0:0:0:0:0:0
FF08:0:0:0:0:0:0:0
FF09:0:0:0:0:0:0:0
FF0A:0:0:0:0:0:0:0
FF0B:0:0:0:0:0:0:0
FF0C:0:0:0:0:0:0:0
FF0D:0:0:0:0:0:0:0
FF0E:0:0:0:0:0:0:0
FF0F:0:0:0:0:0:0:0
Reserved Multicast Addresses: FF00:0:0:0:0:0:0:0
FF01:0:0:0:0:0:0:0
FF02:0:0:0:0:0:0:0
FF03:0:0:0:0:0:0:0
FF04:0:0:0:0:0:0:0
FF05:0:0:0:0:0:0:0
FF06:0:0:0:0:0:0:0
FF07:0:0:0:0:0:0:0
FF08:0:0:0:0:0:0:0
FF09:0:0:0:0:0:0:0
FF0A:0:0:0:0:0:0:0
FF0B:0:0:0:0:0:0:0
FF0C:0:0:0:0:0:0:0
FF0D:0:0:0:0:0:0:0
FF0E:0:0:0:0:0:0:0
FF0F:0:0:0:0:0:0:0
The above multicast addresses are reserved and shall never be assigned to any multicast group.
上述多播地址为保留地址，不得分配给任何多播组。
All Nodes Addresses: FF01:0:0:0:0:0:0:1
FF02:0:0:0:0:0:0:1
All Nodes Addresses: FF01:0:0:0:0:0:0:1
FF02:0:0:0:0:0:0:1
The above multicast addresses identify the group of all IPv6 nodes, within scope 1 (interface-local) or 2 (link-local).
上述多播地址标识范围1（接口本地）或范围2（链路本地）内的所有IPv6节点组。
All Routers Addresses: FF01:0:0:0:0:0:0:2
FF02:0:0:0:0:0:0:2
FF05:0:0:0:0:0:0:2
All Routers Addresses: FF01:0:0:0:0:0:0:2
FF02:0:0:0:0:0:0:2
FF05:0:0:0:0:0:0:2
The above multicast addresses identify the group of all IPv6 routers, within scope 1 (interface-local), 2 (link-local), or 5 (site-local).
上述多播地址标识范围1（接口本地）、2（链路本地）或5（站点本地）内的所有IPv6路由器组。
Solicited-Node Address: FF02:0:0:0:0:1:FFXX:XXXX
Solicited-Node Address: FF02:0:0:0:0:1:FFXX:XXXX
Solicited-Node multicast address are computed as a function of a
node's unicast and anycast addresses. A Solicited-Node multicast
address is formed by taking the low-order 24 bits of an address
(unicast or anycast) and appending those bits to the prefix
FF02:0:0:0:0:1:FF00::/104 resulting in a multicast address in the
range
Solicited-Node multicast address are computed as a function of a
node's unicast and anycast addresses. A Solicited-Node multicast
address is formed by taking the low-order 24 bits of an address
(unicast or anycast) and appending those bits to the prefix
FF02:0:0:0:0:1:FF00::/104 resulting in a multicast address in the
range
FF02:0:0:0:0:1:FF00:0000
FF02:0:0:0:0:1:FF00:0000
to
到
FF02:0:0:0:0:1:FFFF:FFFF
FF02:0:0:0:0:1:FFFF:FFFF
For example, the Solicited-Node multicast address corresponding to the IPv6 address 4037::01:800:200E:8C6C is FF02::1:FF0E:8C6C. IPv6 addresses that differ only in the high-order bits (e.g., due to multiple high-order prefixes associated with different aggregations) will map to the same Solicited-Node address, thereby reducing the number of multicast addresses a node must join.
例如，与IPv6地址4037:：01:800:200E:8C6C对应的请求节点多播地址是FF02:：1:FF0E:8C6C。仅在高阶位上不同（例如，由于与不同聚合相关联的多个高阶前缀）的IPv6地址将映射到同一请求的节点地址，从而减少节点必须加入的多播地址的数量。
A node is required to compute and join (on the appropriate interface) the associated Solicited-Node multicast addresses for all unicast and anycast addresses that have been configured for the node's interfaces (manually or automatically).
节点需要（在适当的接口上）计算并加入（手动或自动）为节点接口配置的所有单播和选播地址的相关请求节点多播地址。
A host is required to recognize the following addresses as identifying itself:
主机需要将以下地址识别为标识自身的地址：
o Its required Link-Local address for each interface.
o 每个接口所需的链接本地地址。
o Any additional Unicast and Anycast addresses that have been configured for the node's interfaces (manually or automatically).
o 为节点接口配置的任何其他单播和选播地址（手动或自动）。
o The loopback address.
o 环回地址。
o The All-Nodes multicast addresses defined in Section 2.7.1.
o 第2.7.1节中定义的所有节点多播地址。
o The Solicited-Node multicast address for each of its unicast and anycast addresses.
o 每个单播和选播地址的请求节点多播地址。
o Multicast addresses of all other groups to which the node belongs.
o 节点所属的所有其他组的多播地址。
A router is required to recognize all addresses that a host is required to recognize, plus the following addresses as identifying itself:
路由器需要识别主机需要识别的所有地址，加上以下地址以识别自身：
o The Subnet-Router Anycast addresses for all interfaces for which it is configured to act as a router.
o 子网路由器选播地址，用于配置为充当路由器的所有接口。
o All other Anycast addresses with which the router has been configured.
o 配置路由器的所有其他选播地址。
o The All-Routers multicast addresses defined in Section 2.7.1.
o 第2.7.1节中定义的所有路由器多播地址。
IPv6 addressing documents do not have any direct impact on Internet infrastructure security. Authentication of IPv6 packets is defined in [AUTH].
IPv6寻址文档对Internet基础设施安全没有任何直接影响。IPv6数据包的身份验证在[AUTH]中定义。
The "IPv4-Compatible IPv6 address" is deprecated by this document. The IANA should continue to list the address block containing these addresses at http://www.iana.org/assignments/ipv6-address-space as "Reserved by IETF" and not reassign it for any other purpose. For example:
本文档不推荐使用“IPv4兼容IPv6地址”。IANA应继续列出包含以下地址的地址块：http://www.iana.org/assignments/ipv6-address-space 作为“IETF保留”，不得将其重新分配用于任何其他目的。例如：
0000::/8 Reserved by IETF [RFC3513] [1]
0000::/8 Reserved by IETF [RFC3513] [1]
The IANA has added the following note and link to this address block.
IANA已将以下注释和链接添加到此地址块。
[5] 0000::/96 was previously defined as the "IPv4-Compatible IPv6 address" prefix. This definition has been deprecated by RFC 4291.
[5] 0000:：/96以前定义为“IPv4兼容IPv6地址”前缀。此定义已被RFC 4291弃用。
The IANA has updated the references for the IPv6 Address Architecture in the IANA registries accordingly.
IANA已相应地更新了IANA注册中心中IPv6地址体系结构的参考。
The authors would like to acknowledge the contributions of Paul Francis, Scott Bradner, Jim Bound, Brian Carpenter, Matt Crawford, Deborah Estrin, Roger Fajman, Bob Fink, Peter Ford, Bob Gilligan, Dimitry Haskin, Tom Harsch, Christian Huitema, Tony Li, Greg Minshall, Thomas Narten, Erik Nordmark, Yakov Rekhter, Bill Simpson, Sue Thomson, Markku Savela, Larry Masinter, Jun-ichiro Itojun Hagino, Tatuya Jinmei, Suresh Krishnan, and Mahmood Ali.
作者要感谢保罗·弗朗西斯、斯科特·布拉德纳、吉姆·邦德、布赖恩·卡彭特、马特·克劳福德、黛博拉·埃斯特林、罗杰·法曼、鲍勃·芬克、彼得·福特、鲍勃·吉利根、迪米特里·哈斯金、汤姆·哈什、克里斯蒂安·惠特马、托尼·李、格雷格·明索尔、托马斯·纳滕、埃里克·诺德马克、雅科夫·雷克特、比尔·辛普森、苏·汤姆森、以及，马尔库·萨维拉、拉里·马辛特、伊藤俊一郎·哈吉诺、塔图亚·金美、苏雷什·克里希南和马哈茂德·阿里。
[IPV6] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[IPV6]Deering，S.和R.Hinden，“互联网协议，第6版（IPV6）规范”，RFC 2460，1998年12月。
[AUTH] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402, November 1998.
[AUTH]Kent，S.和R.Atkinson，“IP认证头”，RFC 2402，1998年11月。
[CIDR] Fuller, V., Li, T., Yu, J., and K. Varadhan, "Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy", RFC 1519, September 1993.
[CIDR]Fuller，V.，Li，T.，Yu，J.，和K.Varadhan，“无类域间路由（CIDR）：地址分配和聚合策略”，RFC 1519，1993年9月。
[ETHER] Crawford, M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998.
[Ethernet]Crawford，M.，“通过以太网传输IPv6数据包”，RFC 2464，1998年12月。
[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority", http://standards.ieee.org/regauth/oui/tutorials/EUI64.html, March 1997.
[EUI64]IEEE，“64位全局标识符（EUI-64）注册机构指南”，http://standards.ieee.org/regauth/oui/tutorials/EUI64.html，1997年3月。
[FDDI] Crawford, M., "Transmission of IPv6 Packets over FDDI Networks", RFC 2467, December 1998.
[FDDI]Crawford，M.，“通过FDDI网络传输IPv6数据包”，RFC 2467，1998年12月。
[GLOBAL] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global Unicast Address Format", RFC 3587, August 2003.
[GLOBAL]Hinden，R.，Deering，S.和E.Nordmark，“IPv6全球单播地址格式”，RFC 3587，2003年8月。
[PRIV] Narten, T. and R. Draves, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", RFC 3041, January 2001.
[PRIV]Narten，T.和R.Draves，“IPv6中无状态地址自动配置的隐私扩展”，RFC 3041，2001年1月。
[RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2005.
[RFC3513]Hinden，R.和S.Deering，“互联网协议版本6（IPv6）寻址体系结构”，RFC 3513，2005年4月。
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast Addresses", RFC 3306, August 2002.
[RFC3306]Haberman，B.和D.Thaler，“基于单播前缀的IPv6多播地址”，RFC3306，2002年8月。
[RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address", RFC 3956, November 2004.
[RFC3956]Savola，P.和B.Haberman，“将集合点（RP）地址嵌入IPv6多播地址”，RFC 3956，2004年11月。
[RFC4038] Shin, M-K., Hong, Y-G., Hagino, J., Savola, P., and E. Castro, "Application Aspects of IPv6 Transition", RFC 4038, March 2005.
[RFC4038]Shin，M-K.，Hong，Y-G.，Hagino，J.，Savola，P.，和E.Castro，“IPv6过渡的应用方面”，RFC 4038，2005年3月。
[SLDEP] Huitema, C. and B. Carpenter, "Deprecating Site Local Addresses", RFC 3879, September 2004.
[SLDEP]Huitema，C.和B.Carpenter，“不推荐现场本地地址”，RFC 38792004年9月。
Appendix A: Creating Modified EUI-64 Format Interface Identifiers
附录A：创建修改的EUI-64格式接口标识符
Depending on the characteristics of a specific link or node, there are a number of approaches for creating Modified EUI-64 format interface identifiers. This appendix describes some of these approaches.
根据特定链路或节点的特性，有多种方法可用于创建修改后的EUI-64格式接口标识符。本附录描述了其中一些方法。
Links or Nodes with IEEE EUI-64 Identifiers
具有IEEE EUI-64标识符的链路或节点
The only change needed to transform an IEEE EUI-64 identifier to an interface identifier is to invert the "u" (universal/local) bit. An example is a globally unique IEEE EUI-64 identifier of the form:
将IEEE EUI-64标识符转换为接口标识符所需的唯一更改是反转“u”（通用/本地）位。一个示例是全局唯一的IEEE EUI-64标识符，其形式如下：
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+----------------+
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+----------------+
where "c" is the bits of the assigned company_id, "0" is the value of the universal/local bit to indicate universal scope, "g" is individual/group bit, and "m" is the bits of the manufacturer-selected extension identifier. The IPv6 interface identifier would be of the form:
其中，“c”是分配的公司id的位，“0”是通用/本地位的值，以指示通用范围，“g”是单个/组位，“m”是制造商选择的扩展标识符的位。IPv6接口标识符的格式为：
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|cccccc1gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+----------------+
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|cccccc1gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+----------------+
The only change is inverting the value of the universal/local bit.
唯一的变化是反转通用/本地位的值。
Links or Nodes with IEEE 802 48-bit MACs
具有IEEE 802 48位MAC的链路或节点
[EUI64] defines a method to create an IEEE EUI-64 identifier from an IEEE 48-bit MAC identifier. This is to insert two octets, with hexadecimal values of 0xFF and 0xFE (see the Note at the end of appendix), in the middle of the 48-bit MAC (between the company_id and vendor-supplied id). An example is the 48-bit IEEE MAC with Global scope:
[EUI64]定义了从IEEE 48位MAC标识符创建IEEE EUI-64标识符的方法。这是为了插入两个八位字节，其值为0xFF和0xFE（参见附录末尾的注释），在48位MAC的中间（在PosiySyid和供应商提供的ID之间）。例如，具有全局范围的48位IEEE MAC：
|0 1|1 3|3 4|
|0 5|6 1|2 7|
+----------------+----------------+----------------+
|cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+
|0 1|1 3|3 4|
|0 5|6 1|2 7|
+----------------+----------------+----------------+
|cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+
where "c" is the bits of the assigned company_id, "0" is the value of the universal/local bit to indicate Global scope, "g" is individual/group bit, and "m" is the bits of the manufacturer-selected extension identifier. The interface identifier would be of the form:
其中，“c”是分配的公司id的位，“0”是通用/本地位的值，以指示全局范围，“g”是单个/组位，“m”是制造商选择的扩展标识符的位。接口标识符的形式如下：
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|cccccc1gcccccccc|cccccccc11111111|11111110mmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+----------------+
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|cccccc1gcccccccc|cccccccc11111111|11111110mmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+----------------+
When IEEE 802 48-bit MAC addresses are available (on an interface or a node), an implementation may use them to create interface identifiers due to their availability and uniqueness properties.
当IEEE 802 48位MAC地址可用时（在接口或节点上），由于其可用性和唯一性属性，实现可以使用它们来创建接口标识符。
Links with Other Kinds of Identifiers
与其他类型标识符的链接
There are a number of types of links that have link-layer interface identifiers other than IEEE EUI-64 or IEEE 802 48-bit MACs. Examples include LocalTalk and Arcnet. The method to create a Modified EUI-64 format identifier is to take the link identifier (e.g., the LocalTalk 8-bit node identifier) and zero fill it to the left. For example, a LocalTalk 8-bit node identifier of hexadecimal value 0x4F results in the following interface identifier:
除了IEEE EUI-64或IEEE 802 48位MAC之外，还有许多类型的链路具有链路层接口标识符。示例包括LocalTalk和Arcnet。创建修改后的EUI-64格式标识符的方法是获取链接标识符（例如，LocalTalk 8位节点标识符）并将其向左零填充。例如，十六进制值0x4F的LocalTalk 8位节点标识符会产生以下接口标识符：
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|0000000000000000|0000000000000000|0000000000000000|0000000001001111|
+----------------+----------------+----------------+----------------+
|0 1|1 3|3 4|4 6|
|0 5|6 1|2 7|8 3|
+----------------+----------------+----------------+----------------+
|0000000000000000|0000000000000000|0000000000000000|0000000001001111|
+----------------+----------------+----------------+----------------+
Note that this results in the universal/local bit set to "0" to indicate local scope.
请注意，这将导致通用/本地位设置为“0”，以指示本地范围。
Links without Identifiers
没有标识符的链接
There are a number of links that do not have any type of built-in identifier. The most common of these are serial links and configured tunnels. Interface identifiers that are unique within a subnet prefix must be chosen.
有许多链接没有任何类型的内置标识符。其中最常见的是串行链路和配置的隧道。必须选择子网前缀中唯一的接口标识符。
When no built-in identifier is available on a link, the preferred approach is to use a universal interface identifier from another interface or one that is assigned to the node itself. When using this approach, no other interface connecting the same node to the same subnet prefix may use the same identifier.
当链路上没有内置标识符时，首选方法是使用来自另一个接口或分配给节点本身的接口的通用接口标识符。使用此方法时，将同一节点连接到同一子网前缀的其他接口不能使用相同的标识符。
If there is no universal interface identifier available for use on the link, the implementation needs to create a local-scope interface identifier. The only requirement is that it be unique within a subnet prefix. There are many possible approaches to select a subnet-prefix-unique interface identifier. These include the following:
如果链接上没有可用的通用接口标识符，则实现需要创建本地作用域接口标识符。唯一的要求是它在子网前缀中是唯一的。有许多可能的方法可以选择子网前缀唯一接口标识符。这些措施包括：
Manual Configuration Node Serial Number Other Node-Specific Token
手动配置节点序列号其他节点特定令牌
The subnet-prefix-unique interface identifier should be generated in a manner such that it does not change after a reboot of a node or if interfaces are added or deleted from the node.
子网前缀唯一接口标识符的生成方式应确保在节点重新启动后，或者在节点中添加或删除接口后，该标识符不会发生更改。
The selection of the appropriate algorithm is link and implementation dependent. The details on forming interface identifiers are defined in the appropriate "IPv6 over <link>" specification. It is strongly recommended that a collision detection algorithm be implemented as part of any automatic algorithm.
适当算法的选择取决于链路和实现。有关形成接口标识符的详细信息，请参见相应的“IPv6 over<link>”规范。强烈建议将碰撞检测算法作为任何自动算法的一部分来实现。
Note: [EUI-64] actually defines 0xFF and 0xFF as the bits to be inserted to create an IEEE EUI-64 identifier from an IEEE MAC-48 identifier. The 0xFF and 0xFE values are used when starting with an IEEE EUI-48 identifier. The incorrect value was used in earlier versions of the specification due to a misunderstanding about the differences between IEEE MAC-48 and EUI-48 identifiers.
注：[EUI-64]实际上将0xFF和0xFF定义为要插入的位，以从IEEE MAC-48标识符创建IEEE EUI-64标识符。当以IEEE EUI-48标识符开始时，使用0xFF和0xFE值。由于对IEEE MAC-48和EUI-48标识符之间差异的误解，本规范早期版本中使用了不正确的值。
This document purposely continues the use of 0xFF and 0xFE because it meets the requirements for IPv6 interface identifiers (i.e., that they must be unique on the link), IEEE EUI-48 and MAC-48 identifiers are syntactically equivalent, and that it doesn't cause any problems in practice.
本文档有意继续使用0xFF和0xFE，因为它满足IPv6接口标识符的要求（即，它们在链路上必须是唯一的），IEEE EUI-48和MAC-48标识符在语法上是等效的，并且在实践中不会引起任何问题。
Appendix B: Changes from RFC 3513
附录B：RFC 3513的变更
The following changes were made from RFC 3513, "IP Version 6 Addressing Architecture":
对RFC 3513“IP版本6寻址体系结构”进行了以下更改：
o The restrictions on using IPv6 anycast addresses were removed because there is now sufficient experience with the use of anycast addresses, the issues are not specific to IPv6, and the GROW working group is working in this area.
o 取消了对使用IPv6选播地址的限制，因为现在在使用选播地址方面有足够的经验，这些问题不是IPv6特有的，GROW工作组正在这方面开展工作。
o Deprecated the Site-Local unicast prefix. Changes include the following:
o 不推荐使用站点本地单播前缀。变化包括：
- Removed Site-Local from special list of prefixes in Section 2.4.
- 将Site Local从第2.4节中的前缀特殊列表中删除。
- Split section titled "Local-use IPv6 Unicast Addresses" into two sections, "Link-Local IPv6 Unicast Addresses" and "Site-Local IPv6 Unicast Addresses".
- 将标题为“本地使用IPv6单播地址”的部分分为两部分，“链接本地IPv6单播地址”和“站点本地IPv6单播地址”。
- Added text to new section describing Site-Local deprecation.
- 向新部分添加了描述站点本地不推荐的文本。
o Changes to resolve issues raised in IAB response to Robert Elz appeal. Changes include the following:
o 变更以解决IAB对Robert Elz上诉的回应中提出的问题。变化包括：
- Added clarification to Section 2.5 that nodes should make no assumptions about the structure of an IPv6 address.
- 在第2.5节中增加了澄清，即节点不应对IPv6地址的结构进行任何假设。
- Changed the text in Section 2.5.1 and Appendix A to refer to the Modified EUI-64 format interface identifiers with the "u" bit set to one (1) as universal.
- 更改了第2.5.1节和附录A中的文本，以引用修改后的EUI-64格式接口标识符，将“u”位设置为一（1）作为通用。
- Added clarification to Section 2.5.1 that IPv6 nodes are not required to validate that interface identifiers created in Modified EUI-64 format with the "u" bit set to one are unique.
- 增加了对第2.5.1节的澄清，即IPv6节点无需验证以修改后的EUI-64格式创建的接口标识符（u位设置为1）是否唯一。
o Changed the reference indicated in Section 2.5.4 "Global Unicast Addresses" to RFC 3587.
o 将第2.5.4节“全局单播地址”中的参考更改为RFC 3587。
o Removed mention of NSAP addresses in examples.
o 删除示例中提到的NSAP地址。
o Clarified that the "x" in the textual representation can be one to four digits.
o 澄清文本表示中的“x”可以是一到四位数字。
o Deprecated the "IPv6 Compatible Address" because it is not being used in the IPv6 transition mechanisms.
o 不推荐使用“IPv6兼容地址”，因为它未在IPv6转换机制中使用。
o Added the "R" and "P" flags to Section 2.7 on multicast addresses, and pointers to the documents that define them.
o 在关于多播地址的第2.7节中添加了“R”和“P”标志，以及指向定义它们的文档的指针。
o Editorial changes.
o 编辑上的改动。
Authors' Addresses
作者地址
Robert M. Hinden Nokia 313 Fairchild Drive Mountain View, CA 94043 USA
Robert M.Hinden诺基亚313飞兆半导体山景大道，加利福尼亚州94043
Phone: +1 650 625-2004
EMail: bob.hinden@nokia.com
Phone: +1 650 625-2004
EMail: bob.hinden@nokia.com
Stephen E. Deering Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA
Stephen E.Deering Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134-1706
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（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 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 provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。