Network Working Group R. Hinden
Request for Comments: 2373 Nokia
Obsoletes: 1884 S. Deering
Category: Standards Track Cisco Systems
July 1998
Network Working Group R. Hinden
Request for Comments: 2373 Nokia
Obsoletes: 1884 S. Deering
Category: Standards Track Cisco Systems
July 1998
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 (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. 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节点所需的地址。
Table of Contents
目录
1. Introduction.................................................2
2. IPv6 Addressing..............................................2
2.1 Addressing Model.........................................3
2.2 Text Representation of Addresses.........................3
2.3 Text Representation of Address Prefixes..................5
2.4 Address Type Representation..............................6
2.5 Unicast Addresses........................................7
2.5.1 Interface Identifiers................................8
2.5.2 The Unspecified Address..............................9
2.5.3 The Loopback Address.................................9
2.5.4 IPv6 Addresses with Embedded IPv4 Addresses.........10
2.5.5 NSAP Addresses......................................10
2.5.6 IPX Addresses.......................................10
2.5.7 Aggregatable Global Unicast Addresses...............11
2.5.8 Local-use IPv6 Unicast Addresses....................11
2.6 Anycast Addresses.......................................12
2.6.1 Required Anycast Address............................13
2.7 Multicast Addresses.....................................14
1. Introduction.................................................2
2. IPv6 Addressing..............................................2
2.1 Addressing Model.........................................3
2.2 Text Representation of Addresses.........................3
2.3 Text Representation of Address Prefixes..................5
2.4 Address Type Representation..............................6
2.5 Unicast Addresses........................................7
2.5.1 Interface Identifiers................................8
2.5.2 The Unspecified Address..............................9
2.5.3 The Loopback Address.................................9
2.5.4 IPv6 Addresses with Embedded IPv4 Addresses.........10
2.5.5 NSAP Addresses......................................10
2.5.6 IPX Addresses.......................................10
2.5.7 Aggregatable Global Unicast Addresses...............11
2.5.8 Local-use IPv6 Unicast Addresses....................11
2.6 Anycast Addresses.......................................12
2.6.1 Required Anycast Address............................13
2.7 Multicast Addresses.....................................14
2.7.1 Pre-Defined Multicast Addresses.....................15
2.7.2 Assignment of New IPv6 Multicast Addresses..........17
2.8 A Node's Required Addresses.............................17
3. Security Considerations.....................................18
APPENDIX A: Creating EUI-64 based Interface Identifiers........19
APPENDIX B: ABNF Description of Text Representations...........22
APPENDIX C: CHANGES FROM RFC-1884..............................23
REFERENCES.....................................................24
AUTHORS' ADDRESSES.............................................25
FULL COPYRIGHT STATEMENT.......................................26
2.7.1 Pre-Defined Multicast Addresses.....................15
2.7.2 Assignment of New IPv6 Multicast Addresses..........17
2.8 A Node's Required Addresses.............................17
3. Security Considerations.....................................18
APPENDIX A: Creating EUI-64 based Interface Identifiers........19
APPENDIX B: ABNF Description of Text Representations...........22
APPENDIX C: CHANGES FROM RFC-1884..............................23
REFERENCES.....................................................24
AUTHORS' ADDRESSES.............................................25
FULL COPYRIGHT STATEMENT.......................................26
This specification defines the addressing architecture of the IP Version 6 protocol. It includes a detailed description of the currently defined address formats for IPv6 [IPV6].
本规范定义了IP版本6协议的寻址体系结构。它包括当前定义的IPv6[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, and Sue Thomson.
作者要感谢保罗·弗朗西斯、斯科特·布拉德纳、吉姆·邦德、布赖恩·卡彭特、马特·克劳福德、黛博拉·埃斯特林、罗杰·法曼、鲍勃·芬克、彼得·福特、鲍勃·吉利根、迪米特里·哈斯金、汤姆·哈什、克里斯蒂安·惠特马、托尼·李、格雷格·明索尔、托马斯·纳滕、埃里克·诺德马克、雅科夫·雷克特、比尔·辛普森和苏·汤姆森的贡献。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC 2119]中所述进行解释。
IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces. There are three types of addresses:
IPv6地址是接口和接口集的128位标识符。有三种类型的地址：
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 "subscriber". When this name is used with the term "ID" for identifier after the name (e.g., "subscriber ID"), it refers to the contents of the named field. When it is used with the term "prefix" (e.g. "subscriber prefix") it refers to all of the address 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 zero-valued fields or end in zeros.
在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 be assigned multiple IPv6 addresses of any type (unicast, anycast, and multicast) or scope. Unicast addresses with 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数据包的源或目标的接口，不需要作用域大于链路作用域的单播地址。这对于点到点接口有时很方便。此寻址模型有一个例外：
An 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 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 the hexadecimal values of the eight 16-bit pieces of the address. Examples:
1. 首选形式是x:x:x:x:x:x:x:x:x，其中“x”是八个16位地址的十六进制值。示例：
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
1080:0:0:0:8:800:200C:417A
1080:0: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 multiple groups of 16-bits of zeros. The "::" can only appear once in an address. The "::" can also be used to compress the leading and/or trailing zeros in an address.
2. 由于某些分配特定类型IPv6地址的方法，地址通常包含长的零位字符串。为了便于写入包含零位的地址，可以使用一种特殊的语法来压缩零。使用“：”表示多组16位零。“：：”在地址中只能出现一次。“：：”还可用于压缩地址中的前导和/或尾随零。
For example the following addresses:
例如，以下地址：
1080:0: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 addresses
1080:0: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 addresses
may be represented as:
可代表为：
1080::8:800:200C:417A a unicast address
FF01::101 a multicast address
::1 the loopback address
:: the unspecified addresses
1080::8:800:200C:417A a unicast address
FF01::101 a multicast address
::1 the loopback address
:: the unspecified addresses
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 the decimal values of the four low-order 8-bit pieces of the address (standard IPv4 representation). Examples:
3. 在处理IPv4和IPv6节点的混合环境时，有时更方便的另一种形式是x:x:x:x:x:x:d.d.d.d，其中“x”是地址的六个高阶16位段的十六进制值，“d”是地址的四个低阶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 addresses prefixes are written in CIDR notation. An IPv6 address prefix is represented by the notation:
IPv6地址前缀的文本表示方式类似于以CIDR表示法编写IPv4地址前缀的方式。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 12AB00000000CD3 (hexadecimal):
例如，以下是60位前缀12AB00000000CD3（十六进制）的法律表示：
12AB:0000:0000:CD30:0000:0000:0000:0000/60
12AB::CD30:0:0:0:0/60
12AB:0:0:CD30::/60
12AB:0000:0000:CD30:0000:0000:0000:0000/60
12AB::CD30:0:0:0:0/60
12AB:0:0:CD30::/60
The following are NOT legal representations of the above prefix:
以下内容不是上述前缀的法律陈述：
12AB:0:0:CD3/60 may drop leading zeros, but not trailing zeros,
within any 16-bit chunk of the address
12AB:0:0:CD3/60 may drop leading zeros, but not trailing zeros,
within any 16-bit chunk of the address
12AB::CD30/60 address to left of "/" expands to
12AB:0000:0000:0000:0000:000:0000:CD30
12AB::CD30/60 address to left of "/" expands to
12AB:0000:0000:0000:0000:000:0000:CD30
12AB::CD3/60 address to left of "/" expands to
12AB:0000:0000:0000:0000:000:0000:0CD3
12AB::CD3/60 address to left of "/" expands to
12AB:0000:0000:0000:0000:000: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 combined as follows:
当写入节点地址和该节点地址的前缀（例如，节点的子网前缀）时，这两个可以按如下方式组合：
the node address 12AB:0:0:CD30:123:4567:89AB:CDEF
and its subnet number 12AB:0:0:CD30::/60
the node address 12AB:0:0:CD30:123:4567:89AB:CDEF
and its subnet number 12AB:0:0:CD30::/60
can be abbreviated as 12AB:0:0:CD30:123:4567:89AB:CDEF/60
can be abbreviated as 12AB:0:0:CD30:123:4567:89AB:CDEF/60
The specific type of an IPv6 address is indicated by the leading bits in the address. The variable-length field comprising these leading bits is called the Format Prefix (FP). The initial allocation of these prefixes is as follows:
IPv6地址的特定类型由地址中的前导位指示。包含这些前导位的可变长度字段称为格式前缀（FP）。这些前缀的初始分配如下所示：
Allocation Prefix Fraction of
(binary) Address Space
----------------------------------- -------- -------------
Reserved 0000 0000 1/256
Unassigned 0000 0001 1/256
Allocation Prefix Fraction of
(binary) Address Space
----------------------------------- -------- -------------
Reserved 0000 0000 1/256
Unassigned 0000 0001 1/256
Reserved for NSAP Allocation 0000 001 1/128 Reserved for IPX Allocation 0000 010 1/128
保留用于NSAP分配0000 001 1/128保留用于IPX分配0000 010 1/128
Unassigned 0000 011 1/128 Unassigned 0000 1 1/32 Unassigned 0001 1/16
未分配0000 011 1/128未分配0000 1 1/32未分配0001 1/16
Aggregatable Global Unicast Addresses 001 1/8 Unassigned 010 1/8 Unassigned 011 1/8 Unassigned 100 1/8 Unassigned 101 1/8 Unassigned 110 1/8
可聚合全局单播地址001 1/8未分配010 1/8未分配011 1/8未分配100 1/8未分配101 1/8未分配110 1/8
Unassigned 1110 1/16 Unassigned 1111 0 1/32 Unassigned 1111 10 1/64 Unassigned 1111 110 1/128 Unassigned 1111 1110 0 1/512
未分配1110 1/16未分配1111 0 1/32未分配1111 10 1/64未分配1111 110 1/128未分配1111 1110 1/512
Link-Local Unicast Addresses 1111 1110 10 1/1024 Site-Local Unicast Addresses 1111 1110 11 1/1024
链路本地单播地址1111110101/1024站点本地单播地址1111110111/1024
Multicast Addresses 1111 1111 1/256
多播地址11111111 1/256
Notes:
笔记：
(1) The "unspecified address" (see section 2.5.2), the loopback address (see section 2.5.3), and the IPv6 Addresses with Embedded IPv4 Addresses (see section 2.5.4), are assigned out of the 0000 0000 format prefix space.
(1) “未指定地址”（见第2.5.2节）、环回地址（见第2.5.3节）和带有嵌入式IPv4地址的IPv6地址（见第2.5.4节）在0000 0000格式前缀空间外分配。
(2) The format prefixes 001 through 111, except for Multicast Addresses (1111 1111), are all required to have to have 64-bit interface identifiers in EUI-64 format. See section 2.5.1 for definitions.
(2) 除了多播地址（1111111）之外，格式前缀001到111都必须具有EUI-64格式的64位接口标识符。定义见第2.5.1节。
This allocation supports the direct allocation of aggregation addresses, local use addresses, and multicast addresses. Space is reserved for NSAP addresses and IPX addresses. The remainder of the address space is unassigned for future use. This can be used for expansion of existing use (e.g., additional aggregatable addresses, etc.) or new uses (e.g., separate locators and identifiers). Fifteen percent of the address space is initially allocated. The remaining 85% is reserved for future use.
此分配支持聚合地址、本地使用地址和多播地址的直接分配。为NSAP地址和IPX地址保留空间。剩余的地址空间将取消分配以供将来使用。这可用于扩展现有用途（例如，额外的可聚合地址等）或新用途（例如，单独的定位器和标识符）。最初分配了15%的地址空间。剩下的85%留作将来使用。
Unicast addresses are distinguished from multicast addresses by the value of the high-order octet of the addresses: a value of FF (11111111) identifies an address as a multicast address; any other value identifies an address as a unicast address. Anycast addresses are taken from the unicast address space, and are not syntactically distinguishable from unicast addresses.
单播地址通过地址的高阶八位组的值与多播地址区分：FF（11111111）的值将地址标识为多播地址；任何其他值将地址标识为单播地址。选播地址取自单播地址空间，在语法上与单播地址不可区分。
IPv6 unicast addresses are aggregatable with contiguous bit-wise masks similar to IPv4 addresses under Class-less Interdomain Routing [CIDR].
IPv6单播地址可以使用连续的位掩码进行聚合，类似于无类域间路由[CIDR]下的IPv4地址。
There are several forms of unicast address assignment in IPv6, including the global aggregatable global unicast address, the NSAP address, the IPX hierarchical address, the site-local address, the link-local address, and the IPv4-capable host address. Additional address types can be defined in the future.
IPv6中有几种形式的单播地址分配，包括全局可聚合全局单播地址、NSAP地址、IPX分层地址、站点本地地址、链路本地地址和支持IPv4的主机地址。以后可以定义其他地址类型。
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 |
+------------------------------------------------+----------------+
Still more sophisticated hosts may be aware of other hierarchical boundaries in the unicast address. 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单播地址的内部结构，但路由器通常会知道路由协议操作的一个或多个层次边界。根据路由器在路由层次结构中所处的位置，路由器之间的已知边界会有所不同。
Interface identifiers in IPv6 unicast addresses are used to identify interfaces on a link. They are required to be unique on that link. They may also be unique over a broader scope. In many cases an interface's identifier will be the same as that interface's link-layer address. The same interface identifier may be used on multiple interfaces on a single node.
IPv6单播地址中的接口标识符用于标识链路上的接口。它们在该链接上必须是唯一的。在更广泛的范围内，它们也可能是独一无二的。在许多情况下，接口的标识符将与该接口的链路层地址相同。同一接口标识符可用于单个节点上的多个接口。
Note that the use of the same interface identifier on multiple interfaces of a single node does not affect the interface identifier's global uniqueness or each IPv6 addresses global uniqueness created using that interface identifier.
请注意，在单个节点的多个接口上使用相同的接口标识符不会影响接口标识符的全局唯一性，或者每个IPv6都会解决使用该接口标识符创建的全局唯一性。
In a number of the format prefixes (see section 2.4) Interface IDs are required to be 64 bits long and to be constructed in IEEE EUI-64 format [EUI64]. EUI-64 based Interface identifiers may have global scope when a global token is available (e.g., IEEE 48bit MAC) or may have local scope where a global token is not available (e.g., serial links, tunnel end-points, etc.). It is required that the "u" bit (universal/local bit in IEEE EUI-64 terminology) be inverted when forming the interface identifier from the EUI-64. The "u" bit is set to one (1) to indicate global scope, and it is set to zero (0) to indicate local scope. The first three octets in binary of an EUI-64 identifier are as follows:
在许多格式前缀（见第2.4节）中，接口ID要求为64位长，并以IEEE EUI-64格式[EUI64]构造。基于EUI-64的接口标识符可以在全局令牌可用时具有全局作用域（例如，IEEE 48位MAC），也可以在全局令牌不可用时具有局部作用域（例如，串行链路、隧道端点等）。当从EUI-64形成接口标识符时，要求“u”位（IEEE EUI-64术语中的通用/本地位）反转。“u”位设置为一（1）表示全局范围，设置为零（0）表示局部范围。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" are the bits of the company_id. Appendix A: "Creating EUI-64 based Interface Identifiers" provides examples on the creation of different EUI-64 based interface identifiers.
以互联网标准位顺序编写，其中“u”是通用/本地位，“g”是单个/组位，“c”是公司id的位。附录A：“创建基于EUI-64的接口标识符”提供了创建不同基于EUI-64的接口标识符的示例。
The motivation for inverting the "u" bit when forming the interface identifier is to make it easy for system administrators to hand configure local scope identifiers when hardware tokens are not available. This is expected to be case for serial links, tunnel end-points, etc. 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 ::1, ::2, etc.
在形成接口标识符时反转“u”位的动机是，当硬件令牌不可用时，系统管理员可以轻松地手动配置本地作用域标识符。串行链路、隧道端点等的情况预计也是如此。替代方案是采用0200:0:0:1、0200:0:0:2等形式，而不是更简单的：：1、：：2等。
The use of the universal/local bit in the IEEE EUI-64 identifier is to allow development of future technology that can take advantage of interface identifiers with global scope.
在IEEE EUI-64标识符中使用通用/本地位是为了开发未来技术，该技术可以利用具有全局范围的接口标识符。
The details of forming interface identifiers are defined in the appropriate "IPv6 over <link>" specification such as "IPv6 over Ethernet" [ETHER], "IPv6 over FDDI" [FDDI], etc.
形成接口标识符的详细信息在适当的“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.
未指定的地址不得用作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 may never be assigned to any physical interface. It may be thought of as being associated with a virtual interface (e.g., the loopback interface).
单播地址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.
环回地址不得用作在单个节点外部发送的IPv6数据包中的源地址。目标地址为环回的IPv6数据包不得发送到单个节点之外，也不得由IPv6路由器转发。
The IPv6 transition mechanisms [TRAN] include a technique for hosts and routers to dynamically tunnel IPv6 packets over IPv4 routing infrastructure. IPv6 nodes that utilize this technique are assigned special IPv6 unicast addresses that carry an IPv4 address in the low-order 32-bits. This type of address is termed an "IPv4-compatible IPv6 address" and has the format:
IPv6转换机制[TRAN]包括主机和路由器通过IPv4路由基础设施动态隧道IPv6数据包的技术。使用此技术的IPv6节点被分配特殊的IPv6单播地址，这些地址携带低阶32位的IPv4地址。这种类型的地址称为“IPv4兼容IPv6地址”，其格式为：
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
A second type of IPv6 address which holds an embedded IPv4 address is also defined. This address is used to represent the addresses of IPv4-only nodes (those that *do not* support IPv6) as IPv6 addresses. This type of address is termed an "IPv4-mapped IPv6 address" and has the format:
还定义了第二种类型的IPv6地址，该地址包含嵌入式IPv4地址。此地址用于将仅IPv4节点（那些*不*支持IPv6的节点）的地址表示为IPv6地址。这种类型的地址称为“IPv4映射IPv6地址”，其格式为：
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+
This mapping of NSAP address into IPv6 addresses is defined in [NSAP]. This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs. However, it also defines a set of mechanisms for the support of OSI NSAP addressing in an IPv6 network. These mechanisms are the ones that must be used if such support is required. This document also defines a mapping of IPv6 addresses within the OSI address format, should this be required.
NSAP地址到IPv6地址的映射在[NSAP]中定义。本文件建议已计划或部署OSI NSAP寻址计划的网络实施者，以及希望部署或过渡到IPv6的网络实施者，应重新设计本机IPv6寻址计划以满足其需求。但是，它还定义了一组机制，用于支持IPv6网络中的OSI NSAP寻址。如果需要这种支持，就必须使用这些机制。如果需要，本文档还定义了OSI地址格式中IPv6地址的映射。
This mapping of IPX address into IPv6 addresses is as follows:
IPX地址到IPv6地址的映射如下：
| 7 | 121 bits |
+-------+---------------------------------------------------------+
|0000010| to be defined |
+-------+---------------------------------------------------------+
| 7 | 121 bits |
+-------+---------------------------------------------------------+
|0000010| to be defined |
+-------+---------------------------------------------------------+
The draft definition, motivation, and usage are under study.
定义、动机和用法草案正在研究中。
The global aggregatable global unicast address is defined in [AGGR]. This address format is designed to support both the current provider based aggregation and a new type of aggregation called exchanges. The combination will allow efficient routing aggregation for both sites which connect directly to providers and who connect to exchanges. Sites will have the choice to connect to either type of aggregation point.
全局可聚合全局单播地址在[AGGR]中定义。此地址格式旨在支持当前基于提供程序的聚合和一种称为Exchange的新型聚合。这种组合将允许直接连接到提供商和连接到交换机的两个站点进行有效的路由聚合。站点可以选择连接到任一类型的聚合点。
The IPv6 aggregatable global unicast address format is as follows:
IPv6可聚合全局单播地址格式如下：
| 3| 13 | 8 | 24 | 16 | 64 bits |
+--+-----+---+--------+--------+--------------------------------+
|FP| TLA |RES| NLA | SLA | Interface ID |
| | ID | | ID | ID | |
+--+-----+---+--------+--------+--------------------------------+
| 3| 13 | 8 | 24 | 16 | 64 bits |
+--+-----+---+--------+--------+--------------------------------+
|FP| TLA |RES| NLA | SLA | Interface ID |
| | ID | | ID | ID | |
+--+-----+---+--------+--------+--------------------------------+
Where
哪里
001 Format Prefix (3 bit) for Aggregatable Global Unicast Addresses TLA ID Top-Level Aggregation Identifier RES Reserved for future use NLA ID Next-Level Aggregation Identifier SLA ID Site-Level Aggregation Identifier INTERFACE ID Interface Identifier
001可聚合全局单播地址的格式前缀（3位）TLA ID顶级聚合标识符保留供将来使用NLA ID下一级聚合标识符SLA ID站点级聚合标识符接口ID接口标识符
The contents, field sizes, and assignment rules are defined in [AGGR].
内容、字段大小和分配规则在[AGGR]中定义。
There are two types of local-use unicast addresses defined. These are Link-Local and Site-Local. The Link-Local is for use on a single link and the Site-Local is for use in a single site. 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 auto-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 have the following format:
站点本地地址的格式如下：
| 10 |
| bits | 38 bits | 16 bits | 64 bits |
+----------+-------------+-----------+----------------------------+
|1111111011| 0 | subnet ID | interface ID |
+----------+-------------+-----------+----------------------------+
| 10 |
| bits | 38 bits | 16 bits | 64 bits |
+----------+-------------+-----------+----------------------------+
|1111111011| 0 | subnet ID | interface ID |
+----------+-------------+-----------+----------------------------+
Site-Local addresses are designed to be used for addressing inside of a site without the need for a global prefix.
站点本地地址设计用于在站点内部寻址，而不需要全局前缀。
Routers must not forward any packets with site-local source or destination addresses outside of the site.
路由器不得转发站点本地源地址或目标地址在站点外部的任何数据包。
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 address prefix P that identifies the topological region in which all interfaces belonging to that anycast address reside. Within the region identified by P, each member of the anycast set must be advertised 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 advertisement 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 advertised as a separate routing entry throughout the entire internet, which presents
注意，在最坏情况下，选播集的前缀P可以是空前缀，即，该集的成员可以没有拓扑局部性。在这种情况下，选播地址必须作为一个单独的路由条目在整个互联网上公布，这将呈现
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.
对支持多少这样的“全局”选播集有严格的扩展限制。因此，预计对全局选播集的支持可能不可用或非常有限。
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 aggregation or sequence of aggregations. 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.
选播地址的一个预期用途是识别属于提供因特网服务的组织的路由器集。这些地址可以用作IPv6路由报头中的中间地址，以使数据包通过特定的聚合或聚合序列来传递。其他一些可能的用途是识别连接到特定子网的路由器集，或者识别进入特定路由域的路由器集。
There is little experience with widespread, arbitrary use of internet anycast addresses, and some known complications and hazards when using them in their full generality [ANYCST]. Until more experience has been gained and solutions agreed upon for those problems, the following restrictions are imposed on IPv6 anycast addresses:
在广泛、任意使用互联网选播地址方面，几乎没有经验，在完全通用的情况下使用这些地址时，存在一些已知的复杂性和危害[ANYCST]。在获得更多经验并就这些问题达成解决方案之前，IPv6选播地址将受到以下限制：
o An anycast address must not be used as the source address of an IPv6 packet.
o 选播地址不得用作IPv6数据包的源地址。
o An anycast address must not be assigned to an IPv6 host, that is, it may be assigned to an IPv6 router only.
o 不得将选播地址分配给IPv6主机，也就是说，只能将其分配给IPv6路由器。
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 which 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 which they have interfaces.
发送到子网路由器选播地址的数据包将被发送到子网上的一个路由器。所有路由器都需要支持其具有接口的子网的子网路由器选播地址。
The subnet-router anycast address is intended to be used for applications where a node needs to communicate with one of a set of routers on a remote subnet. For example when a mobile host needs to communicate with one of the mobile agents on its "home" subnet.
子网路由器选播地址用于节点需要与远程子网上的一组路由器之一通信的应用。例如，当移动主机需要与其“主”子网上的一个移动代理通信时。
An IPv6 multicast address is an identifier for a group of nodes. A node 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 |
+--------+----+----+---------------------------------------------+
11111111 at the start of the address identifies the address as being a multicast address.
地址开头的11111111将该地址标识为多播地址。
+-+-+-+-+
flgs is a set of 4 flags: |0|0|0|T|
+-+-+-+-+
+-+-+-+-+
flgs is a set of 4 flags: |0|0|0|T|
+-+-+-+-+
The high-order 3 flags are reserved, and must be initialized to 0.
高阶3标志是保留的，必须初始化为0。
T = 0 indicates a permanently-assigned ("well-known") multicast address, assigned by the global internet numbering authority.
T=0表示由全球互联网编号机构分配的永久分配（“已知”）多播地址。
T = 1 indicates a non-permanently-assigned ("transient") multicast address.
T=1表示非永久分配（“暂时”）多播地址。
scop is a 4-bit multicast scope value used to limit the scope of the multicast group. The values are:
scop是一个4位多播作用域值，用于限制多播组的作用域。这些数值是：
0 reserved 1 node-local scope 2 link-local scope 3 (unassigned) 4 (unassigned) 5 site-local scope 6 (unassigned) 7 (unassigned) 8 organization-local scope 9 (unassigned) A (unassigned) B (unassigned) C (unassigned)
0保留1节点本地范围2链接本地范围3（未分配）4（未分配）5站点本地范围6（未分配）7（未分配）8组织本地范围9（未分配）A（未分配）B（未分配）C（未分配）
D (unassigned) E global scope F reserved
D（未分配）E保留全局范围F
group ID identifies the multicast group, either permanent or transient, within the given scope.
组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 node as the sender.
FF01: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 at 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 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数据包中的源地址，也不得出现在任何路由标头中。
The following well-known multicast addresses are pre-defined:
以下众所周知的多播地址是预定义的：
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
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
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 (node-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 (node-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
The above multicast address is computed as a function of a node's
unicast and anycast addresses. The solicited-node multicast address
is formed by taking the low-order 24 bits of the 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
The above multicast address is computed as a function of a node's
unicast and anycast addresses. The solicited-node multicast address
is formed by taking the low-order 24 bits of the 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 the associated Solicited-Node multicast addresses for every unicast and anycast address it is assigned.
节点需要计算并加入分配给它的每个单播和选播地址的相关请求节点多播地址。
The current approach [ETHER] to map IPv6 multicast addresses into IEEE 802 MAC addresses takes the low order 32 bits of the IPv6 multicast address and uses it to create a MAC address. Note that Token Ring networks are handled differently. This is defined in [TOKEN]. Group ID's less than or equal to 32 bits will generate unique MAC addresses. Due to this new IPv6 multicast addresses should be assigned so that the group identifier is always in the low order 32 bits as shown in the following:
当前将IPv6多播地址映射到IEEE 802 MAC地址的方法[ETHER]采用IPv6多播地址的低阶32位，并使用它创建MAC地址。请注意，令牌环网络的处理方式不同。这在[TOKEN]中定义。组ID小于或等于32位将生成唯一的MAC地址。因此，应分配新的IPv6多播地址，以便组标识符始终处于低位32位，如下所示：
| 8 | 4 | 4 | 80 bits | 32 bits |
+------ -+----+----+---------------------------+-----------------+
|11111111|flgs|scop| reserved must be zero | group ID |
+--------+----+----+---------------------------+-----------------+
| 8 | 4 | 4 | 80 bits | 32 bits |
+------ -+----+----+---------------------------+-----------------+
|11111111|flgs|scop| reserved must be zero | group ID |
+--------+----+----+---------------------------+-----------------+
While this limits the number of permanent IPv6 multicast groups to 2^32 this is unlikely to be a limitation in the future. If it becomes necessary to exceed this limit in the future multicast will still work but the processing will be sightly slower.
虽然这将永久IPv6多播组的数量限制为2^32，但这在将来不太可能成为限制。如果有必要在将来超过这个限制，多播仍然可以工作，但处理速度会明显减慢。
Additional IPv6 multicast addresses are defined and registered by the IANA [MASGN].
其他IPv6多播地址由IANA[MASGN]定义和注册。
A host is required to recognize the following addresses as identifying itself:
主机需要将以下地址识别为标识自身的地址：
o Its Link-Local Address for each interface o Assigned Unicast Addresses o Loopback Address o All-Nodes Multicast Addresses o Solicited-Node Multicast Address for each of its assigned unicast and anycast addresses o Multicast Addresses of all other groups to which the host belongs.
o 每个接口的链路本地地址o分配的单播地址o环回地址o所有节点多播地址o请求的节点多播地址o分配的每个单播和选播地址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 the interfaces it is configured to act as a router on. o All other Anycast addresses with which the router has been configured. o All-Routers Multicast Addresses
o 子网路由器选播地址用于其配置为充当路由器的接口。o配置路由器的所有其他选播地址。o所有路由器多播地址
o Multicast Addresses of all other groups to which the router belongs.
o 路由器所属的所有其他组的多播地址。
The only address prefixes which should be predefined in an implementation are the:
实现中应预定义的唯一地址前缀是：
o Unspecified Address o Loopback Address o Multicast Prefix (FF) o Local-Use Prefixes (Link-Local and Site-Local) o Pre-Defined Multicast Addresses o IPv4-Compatible Prefixes
o 未指定地址o环回地址o多播前缀（FF）o本地使用前缀（链路本地和站点本地）o预定义多播地址o IPv4兼容前缀
Implementations should assume all other addresses are unicast unless specifically configured (e.g., anycast addresses).
实现应该假设所有其他地址都是单播的，除非特别配置（例如，选播地址）。
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]中定义。
APPENDIX A : Creating EUI-64 based Interface Identifiers
--------------------------------------------------------
APPENDIX A : Creating EUI-64 based Interface Identifiers
--------------------------------------------------------
Depending on the characteristics of a specific link or node there are a number of approaches for creating EUI-64 based interface identifiers. This appendix describes some of these approaches.
根据特定链路或节点的特性，有多种方法可用于创建基于EUI-64的接口标识符。本附录描述了其中一些方法。
Links or Nodes with EUI-64 Identifiers
带有EUI-64标识符的链接或节点
The only change needed to transform an EUI-64 identifier to an interface identifier is to invert the "u" (universal/local) bit. For example, a globally unique EUI-64 identifier of the form:
将EUI-64标识符转换为接口标识符所需的唯一更改是反转“u”（通用/本地）位。例如，表格的全局唯一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" are 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" are 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 MAC's
具有IEEE 802 48位MAC的链路或节点
[EUI64] defines a method to create a EUI-64 identifier from an IEEE 48bit MAC identifier. This is to insert two octets, with hexadecimal values of 0xFF and 0xFE, in the middle of the 48 bit MAC (between the company_id and vendor supplied id). For example the 48 bit MAC with global scope:
[EUI64]定义了从IEEE 48位MAC标识符创建EUI-64标识符的方法。这是为了插入两个八位字节，具有0xFF和0xFE的十六进制值，在48位MAC的中间（在PosiySyid和供应商提供的ID之间）。例如，具有全局作用域的48位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" are 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" are 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 48bit MAC addresses are available (on an interface or a node), an implementation should use them to create interface identifiers due to their availability and uniqueness properties.
当IEEE 802 48位MAC地址可用时（在接口或节点上），由于其可用性和唯一性属性，实现应使用它们来创建接口标识符。
Links with Non-Global Identifiers
与非全局标识符的链接
There are a number of types of links that, while multi-access, do not have globally unique link identifiers. Examples include LocalTalk and Arcnet. The method to create an EUI-64 formatted 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:
有许多类型的链接在多址访问时没有全局唯一的链接标识符。示例包括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 must be chosen that are unique for the link.
有许多链接没有任何类型的内置标识符。其中最常见的是串行链路和配置的隧道。必须为链接选择唯一的接口标识符。
When no built-in identifier is available on a link the preferred approach is to use a global interface identifier from another interface or one which is assigned to the node itself. To use this approach no other interface connecting the same node to the same link may use the same identifier.
当链路上没有内置标识符时，首选方法是使用来自另一个接口或分配给节点本身的接口的全局接口标识符。要使用这种方法，将同一节点连接到同一链路的其他接口不能使用相同的标识符。
If there is no global 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 on the link. There are many possible approaches to select a link-unique interface identifier. They include:
如果链接上没有可用的全局接口标识符，则实现需要创建本地作用域接口标识符。唯一的要求是它在链接上是唯一的。选择链路唯一接口标识符的方法有很多。这些措施包括：
Manual Configuration Generated Random Number Node Serial Number (or other node-specific token)
手动配置生成的随机数节点序列号（或其他特定于节点的令牌）
The link-unique interface identifier should be generated in a manner 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>”规范。强烈建议将碰撞检测算法作为任何自动算法的一部分来实现。
APPENDIX B: ABNF Description of Text Representations
----------------------------------------------------
APPENDIX B: ABNF Description of Text Representations
----------------------------------------------------
This appendix defines the text representation of IPv6 addresses and prefixes in Augmented BNF [ABNF] for reference purposes.
本附录以增广BNF[ABNF]定义了IPv6地址和前缀的文本表示形式，以供参考。
IPv6address = hexpart [ ":" IPv4address ]
IPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT
IPv6address = hexpart [ ":" IPv4address ]
IPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT
IPv6prefix = hexpart "/" 1*2DIGIT
IPv6prefix = hexpart "/" 1*2DIGIT
hexpart = hexseq | hexseq "::" [ hexseq ] | "::" [ hexseq ]
hexseq = hex4 *( ":" hex4)
hex4 = 1*4HEXDIG
hexpart = hexseq | hexseq "::" [ hexseq ] | "::" [ hexseq ]
hexseq = hex4 *( ":" hex4)
hex4 = 1*4HEXDIG
APPENDIX C: CHANGES FROM RFC-1884
---------------------------------
APPENDIX C: CHANGES FROM RFC-1884
---------------------------------
The following changes were made from RFC-1884 "IP Version 6 Addressing Architecture":
对RFC-1884“IP版本6寻址体系结构”进行了以下更改：
- Added an appendix providing a ABNF description of text representations. - Clarification that link unique identifiers not change after reboot or other interface reconfigurations. - Clarification of Address Model based on comments. - Changed aggregation format terminology to be consistent with aggregation draft. - Added text to allow interface identifier to be used on more than one interface on same node. - Added rules for defining new multicast addresses. - Added appendix describing procedures for creating EUI-64 based interface ID's. - Added notation for defining IPv6 prefixes. - Changed solicited node multicast definition to use a longer prefix. - Added site scope all routers multicast address. - Defined Aggregatable Global Unicast Addresses to use "001" Format Prefix. - Changed "010" (Provider-Based Unicast) and "100" (Reserved for Geographic) Format Prefixes to Unassigned. - Added section on Interface ID definition for unicast addresses. Requires use of EUI-64 in range of format prefixes and rules for setting global/local scope bit in EUI-64. - Updated NSAP text to reflect working in RFC1888. - Removed protocol specific IPv6 multicast addresses (e.g., DHCP) and referenced the IANA definitions. - Removed section "Unicast Address Example". Had become OBE. - Added new and updated references. - Minor text clarifications and improvements.
- 增加了一个附录，提供了文本表示的ABNF说明。-说明重新启动或其他接口重新配置后，链接唯一标识符不会更改。-根据评论澄清地址模型。-更改了聚合格式术语，以与聚合草案一致。-添加了允许在同一节点上的多个接口上使用接口标识符的文本。-添加了定义新多播地址的规则。-增加了描述创建基于EUI-64的接口ID的程序的附录添加了用于定义IPv6前缀的符号。-已将请求节点多播定义更改为使用更长的前缀。-添加了站点范围所有路由器多播地址。-定义了使用“001”格式前缀的可聚合全局单播地址。-将“010”（基于提供商的单播）和“100”（保留用于地理位置）格式前缀更改为未分配。-增加了关于单播地址接口ID定义的部分。需要在格式前缀范围内使用EUI-64，以及在EUI-64中设置全局/局部范围位的规则。-更新NSAP文本，以反映RFC1888中的工作。-删除了特定于协议的IPv6多播地址（例如DHCP）并引用了IANA定义。-删除了“单播地址示例”部分。已成为OBE。-添加了新的和更新的参考资料。-次要的文本澄清和改进。
REFERENCES
参考资料
[ABNF] Crocker, D., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[ABNF]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
[AGGR] Hinden, R., O'Dell, M., and S. Deering, "An Aggregatable Global Unicast Address Format", RFC 2374, July 1998.
[AGGR]Hinden，R.，O'Dell，M.，和S.Deering，“一种可聚合的全球单播地址格式”，RFC 2374，1998年7月。
[AUTH] Atkinson, R., "IP Authentication Header", RFC 1826, August 1995.
[AUTH]Atkinson，R.，“IP认证头”，RFC 1826，1995年8月。
[ANYCST] Partridge, C., Mendez, T., and W. Milliken, "Host Anycasting Service", RFC 1546, November 1993.
[ANYCST]帕特里奇，C.，门德斯，T.，和W.米利肯，“主持任意广播服务”，RFC 1546，1993年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 Pacekts over Ethernet Networks", Work in Progress.
[以太]Crawford，M.，“通过以太网传输IPv6起搏器”，正在进行中。
[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority", http://standards.ieee.org/db/oui/tutorials/EUI64.html, March 1997.
[EUI64]IEEE，“64位全局标识符（EUI-64）注册机构指南”，http://standards.ieee.org/db/oui/tutorials/EUI64.html，1997年3月。
[FDDI] Crawford, M., "Transmission of IPv6 Packets over FDDI Networks", Work in Progress.
[FDDI]Crawford，M.，“通过FDDI网络传输IPv6数据包”，正在进行中。
[IPV6] Deering, S., and R. Hinden, Editors, "Internet Protocol, Version 6 (IPv6) Specification", RFC 1883, December 1995.
[IPV6]Deering，S.和R.Hinden，编辑，“互联网协议，第6版（IPV6）规范”，RFC 1883，1995年12月。
[MASGN] Hinden, R., and S. Deering, "IPv6 Multicast Address Assignments", RFC 2375, July 1998.
[MASGN]Hinden，R.和S.Deering，“IPv6多播地址分配”，RFC 23751998年7月。
[NSAP] Bound, J., Carpenter, B., Harrington, D., Houldsworth, J., and A. Lloyd, "OSI NSAPs and IPv6", RFC 1888, August 1996.
[NSAP]Bound，J.，Carpenter，B.，Harrington，D.，Houldsworth，J.，和A.Lloyd，“OSI NSAP和IPv6”，RFC 18881996年8月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[TOKEN] Thomas, S., "Transmission of IPv6 Packets over Token Ring Networks", Work in Progress.
[TOKEN]Thomas，S.，“通过令牌环网传输IPv6数据包”，正在进行中。
[TRAN] Gilligan, R., and E. Nordmark, "Transition Mechanisms for IPv6 Hosts and Routers", RFC 1993, April 1996.
[TRAN]Gilligan，R.和E.Nordmark，“IPv6主机和路由器的过渡机制”，RFC 1993，1996年4月。
AUTHORS' ADDRESSES
作者地址
Robert M. Hinden Nokia 232 Java Drive Sunnyvale, CA 94089 USA
Robert M.Hinden诺基亚232 Java Drive Sunnyvale，加利福尼亚州，美国94089
Phone: +1 408 990-2004
Fax: +1 408 743-5677
EMail: hinden@iprg.nokia.com
Phone: +1 408 990-2004
Fax: +1 408 743-5677
EMail: hinden@iprg.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
Phone: +1 408 527-8213
Fax: +1 408 527-8254
EMail: deering@cisco.com
Phone: +1 408 527-8213
Fax: +1 408 527-8254
EMail: deering@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。