Network Working Group K. Ishiguro
Request for Comments: 5329 V. Manral
Category: Standards Track IP Infusion, Inc
A. Davey
Data Connection Limited
A. Lindem, Ed.
Redback Networks
September 2008
Network Working Group K. Ishiguro
Request for Comments: 5329 V. Manral
Category: Standards Track IP Infusion, Inc
A. Davey
Data Connection Limited
A. Lindem, Ed.
Redback Networks
September 2008
Traffic Engineering Extensions to OSPF Version 3
OSPF版本3的流量工程扩展
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 IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
Abstract
摘要
This document describes extensions to OSPFv3 to support intra-area Traffic Engineering (TE). This document extends OSPFv2 TE to handle IPv6 networks. A new TLV and several new sub-TLVs are defined to support IPv6 networks.
本文档描述了OSPFv3的扩展，以支持区域内流量工程（TE）。本文档扩展了OSPFv2 TE以处理IPv6网络。定义了一个新的TLV和几个新的子TLV以支持IPv6网络。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Requirements Notation ......................................2
2. Intra-Area-TE-LSA ...............................................3
2.1. Intra-Area-TE-LSA Payload ..................................4
3. Router IPv6 Address TLV .........................................4
4. Link TLV ........................................................5
4.1. Link ID Sub-TLV ............................................6
4.2. Neighbor ID Sub-TLV ........................................6
4.3. Local Interface IPv6 Address Sub-TLV .......................6
4.4. Remote Interface IPv6 Address Sub-TLV ......................7
5. Security Considerations .........................................8
6. Management Considerations .......................................8
7. IANA Considerations .............................................9
8. References ......................................................9
8.1. Normative References .......................................9
8.2. Informative References ....................................10
Acknowledgments ...................................................10
1. Introduction ....................................................2
1.1. Requirements Notation ......................................2
2. Intra-Area-TE-LSA ...............................................3
2.1. Intra-Area-TE-LSA Payload ..................................4
3. Router IPv6 Address TLV .........................................4
4. Link TLV ........................................................5
4.1. Link ID Sub-TLV ............................................6
4.2. Neighbor ID Sub-TLV ........................................6
4.3. Local Interface IPv6 Address Sub-TLV .......................6
4.4. Remote Interface IPv6 Address Sub-TLV ......................7
5. Security Considerations .........................................8
6. Management Considerations .......................................8
7. IANA Considerations .............................................9
8. References ......................................................9
8.1. Normative References .......................................9
8.2. Informative References ....................................10
Acknowledgments ...................................................10
OSPFv3 has a very flexible mechanism for adding new LS types. Unknown LS types are flooded properly based on the flooding scope bits in the LS type [OSPFV3]. This document defines the Intra-Area-TE-LSA to OSPFv3.
OSPFv3有一个非常灵活的机制来添加新的LS类型。根据LS类型[OSPFV3]中的泛洪作用域位，正确泛洪未知LS类型。本文件定义了OSPFv3的区域内TE LSA。
For Traffic Engineering, this document uses "Traffic Engineering Extensions to OSPF" [TE] as a base for TLV definitions. New TLVs and sub-TLVs are added to [TE] to extend TE capabilities to IPv6 networks. Some existing TLVs and sub-TLVs require clarification for OSPFv3 applicability.
对于流量工程，本文件使用“OSPF的流量工程扩展”[TE]作为TLV定义的基础。[TE]中添加了新的TLV和子TLV，以将TE功能扩展到IPv6网络。一些现有TLV和子TLV需要澄清OSPFv3的适用性。
GMPLS [GMPLS] and the Diff-Serv MPLS extensions [TE-DIFF] are based on [TE]. These functions can also be extended to OSPFv3 by utilizing the TLVs and sub-TLVs described in this document.
GMPLS[GMPLS]和Diff-Serv MPLS扩展[TE-Diff]基于[TE]。通过使用本文档中描述的TLV和子TLV，这些功能也可以扩展到OSPFv3。
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-KEYWORDS].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC-关键词]中的描述进行解释。
A new LS type is defined for the Intra-Area-TE-LSA. This is different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are used to advertise TE information [OPAQUE]. The LSA function code is 10, the U-bit is set, and the scope is set to 01 for area-scoping. When the U-bit is set to 1, an OSPFv3 router must flood the LSA at its defined flooding scope even if it does not recognize the LS type [OSPFV3].
为区域内TE LSA定义了新的LS类型。这与OSPFv2流量工程[TE]不同，OSPFv2流量工程[TE]使用不透明LSA发布TE信息[不透明]。LSA功能代码为10，设置U位，范围设置为01，用于区域范围。当U位设置为1时，OSPFv3路由器必须在其定义的泛洪范围内泛洪LSA，即使它不识别LS类型[OSPFv3]。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS age |1|0|1| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- TLVs -+
| ... |
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS age |1|0|1| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- TLVs -+
| ... |
OSPFv3 Intra-Area-TE-LSA
OSPFv3区内TE LSA
The Link State ID of an Intra-Area-TE-LSA is an arbitrary value used to maintain multiple Traffic Engineering LSAs. The Link State ID has no topological significance.
区域内TE LSA的链路状态ID是用于维护多个流量工程LSA的任意值。链接状态ID没有拓扑意义。
The format of the TLVs within the body of an Intra-Area-TE-LSA is the same as the format used by the Traffic Engineering extensions to OSPF [TE]. The LSA payload consists of one or more nested Type/Length/Value (TLV) triplets. The format of each TLV is:
区域内TE LSA主体内TLV的格式与OSPF[TE]的流量工程扩展所使用的格式相同。LSA有效负载由一个或多个嵌套类型/长度/值（TLV）三元组组成。每个TLV的格式为：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Format
TLV格式
The Length field defines the length of the value portion in octets (thus, a TLV with no value portion would have a length of 0). The TLV is padded to 4-octet alignment; padding is not included in the Length field (so a 3-octet value would have a length of 3, but the total size of the TLV would be 8 octets). Nested TLVs are also 32- bit aligned. For example, a 1-byte value would have the Length field set to 1, and 3 octets of padding would be added to the end of the value portion of the TLV. Unrecognized types are ignored.
长度字段以八位字节定义值部分的长度（因此，没有值部分的TLV的长度为0）。TLV填充为4-八位组对齐；长度字段中不包括填充（因此3个八位字节的值的长度为3，但TLV的总大小为8个八位字节）。嵌套TLV也是32位对齐的。例如，一个1字节的值将把Length字段设置为1，并在TLV的值部分的末尾添加3个八位字节的填充。将忽略无法识别的类型。
An Intra-Area-TE-LSA contains one top-level TLV. There are two applicable top-level TLVs:
区域内TE LSA包含一个顶级TLV。有两种适用的顶级TLV：
2 - Link TLV
双链路TLV
3 - Router IPv6 Address TLV
3-路由器IPv6地址TLV
The Router IPv6 Address TLV advertises a reachable IPv6 address. This is a stable IPv6 address that SHOULD be reachable if there is connectivity to the OSPFv3 router.
路由器IPv6地址TLV播发可到达的IPv6地址。这是一个稳定的IPv6地址，如果连接到OSPFv3路由器，应该可以访问该地址。
The Router IPv6 Address TLV has type 3, length 16, and a value containing a 16-octet local IPv6 address. A link-local address MUST NOT be specified for this TLV. It MUST appear in exactly one Traffic Engineering LSA originated by an OSPFv3 router supporting the TE extensions. The Router IPv6 Address TLV is a top-level TLV as defined in "Traffic Engineering Extensions to OSPF" [TE], and only one top-level TLV may be contained in an LSA.
路由器IPv6地址TLV的类型为3，长度为16，值包含16个八位组的本地IPv6地址。不得为此TLV指定链路本地地址。它必须出现在支持TE扩展的OSPFv3路由器发起的一个流量工程LSA中。路由器IPv6地址TLV是“OSPF流量工程扩展”[TE]中定义的顶级TLV，一个LSA中只能包含一个顶级TLV。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Router IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Router IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 3. Length A 16-bit field that indicates the length of the value portion in octets. For this TLV, it is always 16. Value A stable and routable IPv6 address.
键入设置为3的16位字段。长度以八位字节表示值部分长度的16位字段。对于这个TLV，它总是16。请指定一个稳定且可路由的IPv6地址。
Router IPv6 Address TLV
路由器IPv6地址TLV
The Link TLV describes a single link and consists of a set of sub-TLVs [TE]. All of the sub-TLVs in [TE] other than the Link ID sub-TLV are applicable to OSPFv3. The Link ID sub-TLV can't be used in OSPFv3 since it is defined to use the OSPFv2 identification for the Designated Router (DR) on multi-access networks. In OSPFv2, neighbors on point-to-point networks and virtual links are identified by their Router IDs while neighbors on broadcast, Non-Broadcast Multi-Access (NBMA), and Point-to-Multipoint links are identified by their IPv4 interface addresses (refer to section 8.2 in [OSPFV2]). The IPv4 interface address is not known to OSPFv3. In contrast to OSPFv2, OSPFv3 always identifies neighboring routers by their Router IDs (refer to section 2.11 in [OSPFV3]).
链路TLV描述单个链路，由一组子TLV[TE]组成。[TE]中除链路ID子TLV之外的所有子TLV都适用于OSPFv3。链路ID子TLV不能在OSPFv3中使用，因为它被定义为在多址网络上使用指定路由器（DR）的OSPFv2标识。在OSPFv2中，点对点网络和虚拟链路上的邻居由其路由器ID标识，而广播、非广播多址（NBMA）和点对多点链路上的邻居由其IPv4接口地址标识（请参阅[OSPFv2]中的第8.2节）。OSPFv3不知道IPv4接口地址。与OSPFv2不同，OSPFv3总是通过路由器ID识别相邻路由器（请参阅[OSPFv3]中的第2.11节）。
Three new sub-TLVs for the Link TLV are defined:
为链路TLV定义了三个新的子TLV：
18 - Neighbor ID (8 octets)
18-邻居ID（8个八位字节）
19 - Local Interface IPv6 Address (16N octets, where N is the number of IPv6 addresses)
19-本地接口IPv6地址（16N个八位字节，其中N是IPv6地址数）
20 - Remote Interface IPv6 Address (16N octets, where N is the number of IPv6 addresses)
20-远程接口IPv6地址（16N个八位字节，其中N是IPv6地址数）
The Neighbor ID sub-TLV is mandatory for OSPFv3 Traffic Engineering support. It MUST appear exactly once in a Link TLV. All other sub-TLVs defined in this document SHOULD NOT occur more than once in a Link TLV. If a sub-TLV is specified more than once, instances subsequent to the first are ignored.
邻居ID子TLV对于OSPFv3流量工程支持是必需的。它必须在链接TLV中恰好出现一次。本文件中定义的所有其他子TLV在链路TLV中不应出现一次以上。如果多次指定子TLV，则忽略第一个TLV之后的实例。
The Link ID sub-TLV is used in OSPFv2 to identify the other end of the link. In OSPFv3, the Neighbor ID sub-TLV MUST be used for link identification. In OSPFv3, the Link ID sub-TLV SHOULD NOT be sent and MUST be ignored upon receipt.
链路ID子TLV在OSPFv2中用于标识链路的另一端。在OSPFv3中，必须使用邻居ID子TLV进行链路标识。在OSPFv3中，链路ID子TLV不应发送，并且在收到时必须忽略。
In OSPFv2, the Link ID is used to identify the other end of a link. In OSPFv3, the combination of Neighbor Interface ID and Neighbor Router ID is used for neighbor link identification. Both are advertised in the Neighbor ID sub-TLV.
在OSPFv2中，链路ID用于标识链路的另一端。在OSPFv3中，邻居接口ID和邻居路由器ID的组合用于邻居链路标识。两者都在邻居ID子TLV中公布。
Neighbor Interface ID and Neighbor Router ID values are the same as described in RFC 5340 [OSPFV3], A.4.3 Router-LSAs.
邻居接口ID和邻居路由器ID值与RFC 5340[OSPFV3]，A.4.3路由器LSA中描述的相同。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 18 | 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 18 | 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 18. Length A 16-bit field that indicates the length of the value portion in octets. For this sub-TLV, it is always 8. Value The neighbor's Interface ID and Router ID.
键入设置为18的16位字段。长度以八位字节表示值部分长度的16位字段。对于该子TLV，它始终为8。为邻居的接口ID和路由器ID赋值。
Neighbor ID Sub-TLV
邻居ID子TLV
The Local Interface IPv6 Address sub-TLV specifies the IPv6 address(es) of the interface corresponding to this link. If there are multiple local addresses assigned to the link, then they MAY all be listed in this sub-TLV. Link-local addresses MUST NOT be included in this sub-TLV.
本地接口IPv6地址子TLV指定与此链接对应的接口的IPv6地址。如果有多个本地地址分配给链路，则它们可能都列在此子TLV中。链路本地地址不得包含在此子TLV中。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 19 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Local Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| o |
| o |
| o |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Local Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 19 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Local Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| o |
| o |
| o |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Local Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 19. Length A 16-bit field that indicates the length of the value portion in octets. For this sub-TLV, it MUST always be a multiple of 16 octets dependent on the number of IPv6 global addresses advertised. Value A list of one or more local IPv6 interface addresses each consuming 16 octets.
键入设置为19的16位字段。长度以八位字节表示值部分长度的16位字段。对于此子TLV，它必须始终是16个八位字节的倍数，具体取决于播发的IPv6全局地址数。值一个或多个本地IPv6接口地址的列表，每个地址使用16个八位字节。
Local Interface IPv6 Address Sub-TLV
本地接口IPv6地址子TLV
The Remote Interface IPv6 Address sub-TLV advertises the IPv6 address(es) associated with the neighbor's interface. This sub-TLV and the Local Interface IPv6 Address sub-TLV are used to discern amongst parallel links between OSPFv3 routers. If the link type is multi-access, the Remote Interface IPv6 Address MAY be set to ::. Alternately, an implementation MAY choose not to send this sub-TLV. Link-local addresses MUST NOT be advertised in this sub-TLV. Neighbor addresses advertised in link-LSAs with a prefix length of 128 and the LA-bit set MAY be advertised.
远程接口IPv6地址子TLV播发与邻居接口关联的IPv6地址。此子TLV和本地接口IPv6地址子TLV用于区分OSPFv3路由器之间的并行链路。如果链接类型为多访问，则远程接口IPv6地址可以设置为：。或者，实现可以选择不发送此子TLV。链接本地地址不得在此子TLV中公布。在前缀长度为128且LA位集的链路lsa中通告的邻居地址可以被通告。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 20 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Remote Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| o |
| o |
| o |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Remote Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 20 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Remote Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| o |
| o |
| o |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+- Remote Interface IPv6 Address -+-+-+-+
| |
+-+-+-+- -+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type A 16-bit field set to 20. Length A 16-bit field that indicates the length of the value portion in octets. For this sub-TLV, it MUST be a multiple of 16 octets dependent on the number of IPv6 global addresses advertised. Value A variable-length Remote Interface IPv6 Address list.
键入设置为20的16位字段。长度以八位字节表示值部分长度的16位字段。对于此子TLV，它必须是16个八位字节的倍数，具体取决于播发的IPv6全局地址数。值为可变长度远程接口IPv6地址列表。
Remote Interface IPv6 Address Sub-TLV
远程接口IPv6地址子TLV
The function described in this document does not create any new security issues for the OSPFv3 protocol. Security considerations for the base OSPFv3 protocol [OSPFV3] and OSPFv2 Traffic Engineering [TE] are applicable to OSPFv3 Traffic Engineering.
本文档中描述的功能不会给OSPFv3协议带来任何新的安全问题。基本OSPFv3协议[OSPFv3]和OSPFv2流量工程[TE]的安全注意事项适用于OSPFv3流量工程。
The typical management interface for routers running the new extensions to OSPF for intra-area Traffic Engineering is Simple Network Management Protocol (SNMP) based. The extra management
运行OSPF新扩展以进行区域内流量工程的路由器的典型管理接口是基于简单网络管理协议（SNMP）的。额外管理
objects for configuration operations and statistics are defined in [OSPFV3-MIB], and an implementation of the extensions defined in this document SHOULD provide for the appropriate hooks or instrumentation that allow for the MIB objects to be implemented.
[OSPFV3-MIB]中定义了用于配置操作和统计的对象，本文档中定义的扩展的实现应提供适当的钩子或工具，以便实现MIB对象。
The following MIB variables have been added to the OSPFv3 MIB in support of TE:
以下MIB变量已添加到OSPFv3 MIB中，以支持TE：
ospfv3AreaTEEnabled This TruthValue MIB variable in the ospfv3AreaEntry table entry indicates whether or not OSPFv3 TE advertisement for OSPFv3 interfaces is enabled for the corresponding area. The default value is FALSE.
OSPFV3reateEnabled ospfv3AreaEntry表项中的此TruthValue MIB变量指示是否为相应区域启用OSPFv3接口的OSPFv3 TE播发。默认值为FALSE。
ospfv3IfTEDisabled This TruthValue MIB variable in the ospfv3IfEntry table entry indicates whether or not OSPFv3 TE advertisement for OSPFv3 for the corresponding interface is disabled. This MIB variable is only applicable if ospfv3AreaTEEnabled is TRUE for the interface's area. The default value is FALSE.
OSPFV3IFEDISABLED ospfv3IfEntry表项中的此TruthValue MIB变量指示是否禁用相应接口的OSPFv3 TE OSPFv3播发。仅当接口区域的OSPFV3reateEnabled为TRUE时，此MIB变量才适用。默认值为FALSE。
The following IANA assignments have been made from existing registries:
已从现有登记处进行了以下IANA分配：
1. The OSPFv3 LSA type function code 10 has been assigned to the OSPFv3 Intra-Area-TE-LSA.
1. OSPFv3 LSA类型功能代码10已分配给OSPFv3区域内TE LSA。
2. The Router IPv6 Address TLV type 3 has been assigned from the existing registry for OSPF TE TLVs.
2. 路由器IPv6地址TLV类型3已从OSPF TE TLV的现有注册表分配。
3. The Neighbor ID (18), Local Interface IPv6 Address (19), and Remote Interface IPv6 Address (20) sub-TLVs have been assigned from the existing registry for OSPF TE sub-TLVs.
3. 已从OSPF TE子TLV的现有注册表中分配了邻居ID（18）、本地接口IPv6地址（19）和远程接口IPv6地址（20）子TLV。
[OSPFV2] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[OSPFV2]Moy，J.，“OSPF版本2”，STD 54，RFC 23281998年4月。
[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, July 2008.
[OSPFV3]Coltun，R.，Ferguson，D.，Moy，J.，和A.Lindem，“IPv6的OSPF”，RFC 53402008年7月。
[RFC-KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-关键词]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[TE] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering (TE) Extensions to OSPF Version 2", RFC 3630, September 2003.
[TE]Katz，D.，Kompella，K.，和D.Yeung，“OSPF版本2的交通工程（TE）扩展”，RFC 3630，2003年9月。
[GMPLS] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 4203, October 2005.
[GMPLS]Kompella，K.，Ed.，和Y.Rekhter，Ed.，“支持通用多协议标签交换（GMPLS）的OSPF扩展”，RFC 4203，2005年10月。
[OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The OSPF Opaque LSA Option", RFC 5250, July 2008.
[不透明]Berger，L.，Bryskin，I.，Zinin，A.，和R.Coltun，“OSPF不透明LSA选项”，RFC 5250，2008年7月。
[OSPFV3-MIB] Joyal, D. and V. Manral, "Management Information Base for OSPFv3", Work in Progress, September 2007.
[OSPFV3-MIB]Joyal，D.和V.Manral，“OSPFV3的管理信息库”，正在进行的工作，2007年9月。
[TE-DIFF] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi-Protocol Label Switching (MPLS) Support of Differentiated Services", RFC 3270, May 2002.
[TE-DIFF]Le Faucheur，F.，Wu，L.，Davie，B.，Davari，S.，Vaananen，P.，Krishnan，R.，Cheval，P.，和J.Heinanen，“区分服务的多协议标签交换（MPLS）支持”，RFC 32702002年5月。
Acknowledgments
致谢
Thanks to Kireeti Kompella, Alex Zinin, Adrian Farrell, and Mach Chen for their comments.
感谢Kireeti Kompella、Alex Zinin、Adrian Farrell和Mach Chen的评论。
Thanks to Vijay K. Gurbani for providing the General Area Review Team (Gen-ART) review.
感谢Vijay K.Gurbani提供一般区域审查团队（Gen ART）审查。
Thanks to Rob Austein for providing the Security Directorate (secdir) review.
感谢Rob Austein提供安全理事会（secdir）审查。
Thanks to Dan Romascanu for providing the text for the "Management Considerations" section in the context of the IESG review.
感谢Dan Romascanu在IESG审查中为“管理考虑”部分提供了文本。
Thanks to Dave Ward, Tim Polk, Jari Arkko, and Pasi Eronen for comments and relevant discussion in the context of the IESG review.
感谢Dave Ward、Tim Polk、Jari Arkko和Pasi Eronen在IESG审查中提出的意见和相关讨论。
The RFC text was produced using Marshall Rose's xml2rfc tool.
RFC文本是使用Marshall Rose的xml2rfc工具生成的。
Authors' Addresses
作者地址
Kunihiro Ishiguro IP Infusion, Inc. 1188 East Arques Avenue, Sunnyvale, CA 94085 USA
Kunihiro Ishiguro IP输液公司，地址：美国加利福尼亚州桑尼维尔东阿克斯大道1188号，邮编94085
EMail: kunihiro@ipinfusion.com
EMail: kunihiro@ipinfusion.com
Vishwas Manral IP Infusion, Inc #41, Ground Floor, 5th Cross Road 8th Main Road Vasanth Nagar, Bangalore 560052 India
印度班加罗尔Vasanth Nagar第八主干道第五十字路第41层Vishwas Manral IP输液公司，邮编560052
EMail: vishwas@ipinfusion.com
EMail: vishwas@ipinfusion.com
Alan Davey Data Connection Limited 100 Church Street Enfield EN2 6BQ UK
Alan Davey数据连接有限公司100 Church Street Enfield EN2 6BQ英国
EMail: Alan.Davey@dataconnection.com
EMail: Alan.Davey@dataconnection.com
Acee Lindem Redback Networks 102 Carric Bend Court Cary, NC 27519 USA
美国北卡罗来纳州卡里克本德法院102号Acee Lindem Redback Networks 27519
EMail: acee@redback.com
EMail: acee@redback.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.