Internet Engineering Task Force (IETF) C. Petrie
Request for Comments: 8050 RIPE NCC
Category: Standards Track T. King
ISSN: 2070-1721 DE-CIX
May 2017
Internet Engineering Task Force (IETF) C. Petrie
Request for Comments: 8050 RIPE NCC
Category: Standards Track T. King
ISSN: 2070-1721 DE-CIX
May 2017
Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path Extensions
带有BGP附加路径扩展的多线程路由工具包（MRT）路由信息导出格式
Abstract
摘要
This document extends the Multi-threaded Routing Toolkit (MRT) export format for Border Gateway Protocol (BGP) routing information by supporting the advertisement of multiple paths in BGP extensions.
本文档通过支持在BGP扩展中公布多条路径，扩展了边界网关协议（BGP）路由信息的多线程路由工具包（MRT）导出格式。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8050.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8050.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. MRT Subtypes for Types BGP4MP/BGP4MP_ET . . . . . . . . . . . 3
4. MRT Subtypes for Type TABLE_DUMP_V2 . . . . . . . . . . . . . 3
4.1. AFI/SAFI-Specific RIB Subtypes . . . . . . . . . . . . . 4
4.2. RIB_GENERIC_ADDPATH Subtype . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5.1. BGP4MP/BGP4MP_ET Subtype Codes . . . . . . . . . . . . . 5
5.2. TABLE_DUMP_V2 Subtype Codes . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. MRT Subtypes for Types BGP4MP/BGP4MP_ET . . . . . . . . . . . 3
4. MRT Subtypes for Type TABLE_DUMP_V2 . . . . . . . . . . . . . 3
4.1. AFI/SAFI-Specific RIB Subtypes . . . . . . . . . . . . . 4
4.2. RIB_GENERIC_ADDPATH Subtype . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5.1. BGP4MP/BGP4MP_ET Subtype Codes . . . . . . . . . . . . . 5
5.2. TABLE_DUMP_V2 Subtype Codes . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
The MRT record format [RFC6396] was developed to provide researchers and engineers a means to encapsulate, export, and archive routing protocol transactions and RIB snapshots.
MRT记录格式[RFC6396]的开发旨在为研究人员和工程师提供一种封装、导出和归档路由协议事务和RIB快照的方法。
The Advertisement of Multiple Paths in BGP [RFC7911] defines a BGP extension to allow the advertisement of multiple paths for the same address prefix without the new paths implicitly replacing any previous ones.
BGP[RFC7911]中多条路径的公布定义了一个BGP扩展，允许为同一地址前缀公布多条路径，而无需新路径隐式替换任何以前的路径。
This document contains an optional extension to the MRT format [RFC6396] and introduces additional definitions of MRT subtype fields to permit representation of multiple path advertisements [RFC7911].
本文档包含MRT格式[RFC6396]的可选扩展，并引入了MRT子类型字段的其他定义，以允许表示多路径广告[RFC7911]。
MRT parsers are usually stateless. In order to parse BGP messages that contain data structures that depend on the capabilities negotiated during the BGP session setup, the MRT subtypes are utilized. The Advertisement of Multiple Paths [RFC7911] extension for BGP alters the encoding of the BGP Network Layer Reachability Information (NLRI) format for withdraws and announcements. Therefore, new BGP4MP/BGP4MP_ET subtypes as defined in [RFC6396] are required to signal to an MRT parser how to parse the NLRI.
MRT解析器通常是无状态的。为了解析包含数据结构的BGP消息，这些数据结构取决于BGP会话设置期间协商的功能，使用了MRT子类型。BGP多路径[RFC7911]扩展的公布改变了BGP网络层可达性信息（NLRI）格式的编码，用于撤销和公告。因此，需要[RFC6396]中定义的新BGP4MP/BGP4MP_ET子类型向MRT解析器发出如何解析NLRI的信号。
In Section 4.3 of the MRT specification [RFC6396], RIB subtypes are specified. Prefix length and prefix fields are encoded in the same manner as the BGP NLRI encoding. In order to support Path Identifier information as defined in [RFC7911], new subtypes need to be added.
MRT规范[RFC6396]第4.3节规定了肋骨亚型。前缀长度和前缀字段的编码方式与BGP NLRI编码相同。为了支持[RFC7911]中定义的路径标识符信息，需要添加新的子类型。
The following two sections define the required subtypes.
以下两部分定义了所需的子类型。
This document defines the following new subtypes:
本文档定义了以下新的子类型：
o BGP4MP_MESSAGE_ADDPATH
o BGP4MP\u消息\u添加路径
o BGP4MP_MESSAGE_AS4_ADDPATH
o BGP4MP_消息_AS4_添加路径
o BGP4MP_MESSAGE_LOCAL_ADDPATH
o BGP4MP\u消息\u本地\u添加路径
o BGP4MP_MESSAGE_AS4_LOCAL_ADDPATH
o BGP4MP_消息_AS4_本地_添加路径
The fields of these message types are identical to the equivalent non-additional-path versions specified in Section 4.4 of [RFC6396]. These enhancements continue to encapsulate the entire BGP message in the BGP message field.
这些消息类型的字段与[RFC6396]第4.4节中规定的等效非附加路径版本相同。这些增强功能继续将整个BGP消息封装在BGP消息字段中。
This document defines the following new subtypes:
本文档定义了以下新的子类型：
o RIB_IPV4_UNICAST_ADDPATH
o RIB\u IPV4\u单播\u添加路径
o RIB_IPV4_MULTICAST_ADDPATH
o RIB\u IPV4\u多播\u添加路径
o RIB_IPV6_UNICAST_ADDPATH
o RIB_IPV6_单播_添加路径
o RIB_IPV6_MULTICAST_ADDPATH
o RIB\u IPV6\u多播\u添加路径
o RIB_GENERIC_ADDPATH
o 肋骨\通用\添加路径
The fields of these message types are identical to the equivalent non-additional-path versions specified in Section 4.3 of [RFC6396]. However, for the case of the 4 AFI/SAFI-specific RIB subtypes, the existing RIB Entries field is redefined as detailed in the sections below.
这些消息类型的字段与[RFC6396]第4.3节中规定的等效非附加路径版本相同。但是，对于4个AFI/SAFI特定的肋骨子类型，现有肋骨条目字段将重新定义，如下节所述。
In order to preserve the record compaction achieved by using the most common subtypes and allow multiple RIB Entries to be stored in a single TABLE_DUMP_V2 record, the existing RIB Entries field is redefined for use within the new AFI/SAFI-specific RIB subtypes defined by this document as follows:
为了保留通过使用最常见的子类型实现的记录压缩，并允许将多个RIB条目存储在单个表格_DUMP_V2记录中，现有RIB条目字段被重新定义，以便在本文档定义的新AFI/SAFI特定RIB子类型中使用，如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originated Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Path Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attribute Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Attributes... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originated Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Path Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attribute Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Attributes... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: RIB Entries for AFI/SAFI-Specific RIB Subtypes with Support for Additional Paths
图1：支持其他路径的AFI/SAFI特定肋骨子类型的肋骨条目
This adds a field to the RIB Entries record to store the Path Identifier when used with the RIB_IPV4_UNICAST_ADDPATH, RIB_IPV4_MULTICAST_ADDPATH, RIB_IPV6_UNICAST_ADDPATH, and RIB_IPV6_MULTICAST_ADDPATH subtypes.
当与RIB_IPV4_单播_ADDPATH、RIB_IPV4_多播_ADDPATH、RIB_IPV6_单播_ADDPATH和RIB_IPV6_多播_ADDPATH子类型一起使用时，将向RIB条目记录添加一个字段，以存储路径标识符。
The fields of this subtype are identical to the equivalent non-additional-path versions specified in Section 4.3.3 of [RFC6396]. These fields continue to encapsulate the raw and additional-path-enabled AFI/SAFI/NLRI in the record, and the raw attributes in the RIB Entries.
此子类型的字段与[RFC6396]第4.3.3节中规定的等效非附加路径版本相同。这些字段继续封装记录中的原始和附加路径启用AFI/SAFI/NLRI，以及RIB条目中的原始属性。
For clarity, the RIB Entries in this subtype are not redefined.
为清楚起见，未重新定义此子类型中的肋骨条目。
IANA has assigned the subtype codes defined below in the "Multi-threaded Routing Toolkit (MRT)" registry <https://www.iana.org/assignments/mrt>.
IANA已在“多线程路由工具包（MRT）”注册表中分配了以下定义的子类型代码<https://www.iana.org/assignments/mrt>.
The following have been registered in the "BGP4MP Subtype Codes" and "BGP4MP_ET Subtype Codes" registries:
以下内容已在“BGP4MP子类型代码”和“BGP4MP_ET子类型代码”注册表中注册：
8 BGP4MP_MESSAGE_ADDPATH (RFC 8050)
8 BGP4MP_消息_添加路径（RFC 8050）
9 BGP4MP_MESSAGE_AS4_ADDPATH (RFC 8050)
9 BGP4MP_消息_AS4_添加路径（RFC 8050）
10 BGP4MP_MESSAGE_LOCAL_ADDPATH (RFC 8050)
10 BGP4MP消息本地地址路径（RFC 8050）
11 BGP4MP_MESSAGE_AS4_LOCAL_ADDPATH (RFC 8050)
11 BGP4MP_消息_AS4_本地_添加路径（RFC 8050）
The following have been registered in the "TABLE_DUMP_V2 Subtype Codes" registry:
以下内容已在“TABLE_DUMP_V2子类型代码”注册表中注册：
8 RIB_IPV4_UNICAST_ADDPATH (RFC 8050)
8 RIB_IPV4_单播_添加路径（RFC 8050）
9 RIB_IPV4_MULTICAST_ADDPATH (RFC 8050)
9 RIB_IPV4_多播_添加路径（RFC 8050）
10 RIB_IPV6_UNICAST_ADDPATH (RFC 8050)
10 RIB_IPV6_单播_添加路径（RFC 8050）
11 RIB_IPV6_MULTICAST_ADDPATH (RFC 8050)
11 RIB_IPV6_多播_添加路径（RFC 8050）
12 RIB_GENERIC_ADDPATH (RFC 8050)
12肋条一般添加路径（RFC 8050）
It is not believed that this document adds any additional security considerations. However, the security considerations of [RFC6396] are equally applicable to this document, because this document permits the export of more detailed routing data.
不认为本文件添加了任何其他安全注意事项。然而，[RFC6396]的安全考虑同样适用于本文件，因为本文件允许导出更详细的路由数据。
An organization that uses the MRT format to store their BGP routing information should be aware that supporting these extensions permits more detailed network path information to be stored and should consider the implications of this within their environment.
使用MRT格式来存储它们的BGP路由信息的组织应该知道支持这些扩展允许更详细的网络路径信息被存储，并且应该考虑这在它们的环境中的影响。
An organization that peers with public BGP collectors and enables the capability for additional paths on a peering session should be aware that it is exporting not only its best paths, but potentially other paths within its networks. The BGP peer should consider any and all implications of exposing this additional data.
与公共BGP采集器进行对等并在对等会话上启用附加路径功能的组织应该知道，它不仅导出其最佳路径，而且可能导出其网络中的其他路径。BGP对等体应该考虑暴露这些附加数据的任何和所有含义。
[RFC6396] Blunk, L., Karir, M., and C. Labovitz, "Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format", RFC 6396, DOI 10.17487/RFC6396, October 2011, <http://www.rfc-editor.org/info/rfc6396>.
[RFC6396]Blunk，L.，Karir，M.，和C.Labovitz，“多线程路由工具包（MRT）路由信息导出格式”，RFC 6396，DOI 10.17487/RFC6396，2011年10月<http://www.rfc-editor.org/info/rfc6396>.
[RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder, "Advertisement of Multiple Paths in BGP", RFC 7911, DOI 10.17487/RFC7911, July 2016, <http://www.rfc-editor.org/info/rfc7911>.
[RFC7911]Walton，D.，Retana，A.，Chen，E.，和J.Scudder，“BGP中多路径的广告”，RFC 7911，DOI 10.17487/RFC7911，2016年7月<http://www.rfc-editor.org/info/rfc7911>.
Authors' Addresses
作者地址
Colin Petrie RIPE NCC Stationsplein 11 Amsterdam 1012 AB The Netherlands
科林·佩特里（Colin Petrie）位于荷兰阿姆斯特丹1012 AB 11号NCC车站
Email: cpetrie@ripe.net
Email: cpetrie@ripe.net
Thomas King DE-CIX Management GmbH Lichtstrasse 43i Cologne 50825 Germany
Thomas King DE-CIX管理有限公司Lichtstrasse 43i科隆50825德国
Email: thomas.king@de-cix.net
Email: thomas.king@de-cix.net