Internet Engineering Task Force (IETF) Z. Li
Request for Comments: 8549 R. Gu
Category: Standards Track China Mobile
ISSN: 2070-1721 J. Dong
Huawei Technologies
April 2019
Internet Engineering Task Force (IETF) Z. Li
Request for Comments: 8549 R. Gu
Category: Standards Track China Mobile
ISSN: 2070-1721 J. Dong
Huawei Technologies
April 2019
Export of BGP Community Information in IP Flow Information Export (IPFIX)
在IP流信息导出（IPFIX）中导出BGP社区信息
Abstract
摘要
By introducing new Information Elements (IEs), this document extends the existing BGP-related IEs to enable IP Flow Information Export (IPFIX) to export BGP community information, including the BGP Standard Communities defined in RFC 1997, BGP Extended Communities defined in RFC 4360, and BGP Large Communities defined in RFC 8092. According to the network operator's BGP community planning, network traffic information can then be accumulated and analyzed at the BGP community granularity, which represents the traffic of different kinds of customers, services, or geographical regions. Network traffic information at the BGP community granularity is useful for network traffic analysis and engineering.
通过引入新的信息元素，本文档扩展了现有BGP相关的IEs，使IP流信息导出（IPFIX）能够导出BGP社区信息，包括RFC 1997中定义的BGP标准社区、RFC 4360中定义的BGP扩展社区以及RFC 8092中定义的BGP大型社区。根据网络运营商的BGP社区规划，可以在BGP社区粒度上收集和分析网络流量信息，该粒度表示不同类型客户、服务或地理区域的流量。BGP社区粒度的网络流量信息对于网络流量分析和工程非常有用。
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 https://www.rfc-editor.org/info/rfc8549.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8549.
Copyright Notice
版权公告
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.
版权（c）2019 IETF信托基金和被确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. Terminology .....................................................5
3. Traffic Collection Based on BGP Community .......................6
4. IEs for BGP Standard Community ..................................7
5. IEs for BGP Extended Community ..................................8
6. IEs for BGP Large Community .....................................8
7. Operational Considerations ......................................9
8. Security Considerations ........................................10
9. IANA Considerations ............................................11
10. References ....................................................13
10.1. Normative References .....................................13
10.2. Informative References ...................................14
Appendix A. Encoding Example .....................................16
A.1. Template Record ...........................................16
A.2. Data Set ..................................................17
Acknowledgements ..................................................18
Authors' Addresses ................................................18
1. Introduction ....................................................3
2. Terminology .....................................................5
3. Traffic Collection Based on BGP Community .......................6
4. IEs for BGP Standard Community ..................................7
5. IEs for BGP Extended Community ..................................8
6. IEs for BGP Large Community .....................................8
7. Operational Considerations ......................................9
8. Security Considerations ........................................10
9. IANA Considerations ............................................11
10. References ....................................................13
10.1. Normative References .....................................13
10.2. Informative References ...................................14
Appendix A. Encoding Example .....................................16
A.1. Template Record ...........................................16
A.2. Data Set ..................................................17
Acknowledgements ..................................................18
Authors' Addresses ................................................18
IP Flow Information Export (IPFIX) [RFC7011] provides network administrators with traffic flow information using the Information Elements (IEs) defined in the "IPFIX Information Elements" registry [IANA-IPFIX]. Based on the traffic flow information, network administrators know the amount and direction of the traffic in their network and can then optimize the network when needed. For example, the collected information could be used for traffic monitoring and, optionally, for traffic optimization according to the operator's policy.
IP流信息导出（IPFIX）[RFC7011]使用“IPFIX信息元素”注册表[IANA-IPFIX]中定义的信息元素向网络管理员提供流量信息。根据流量信息，网络管理员知道网络中的流量和方向，然后可以在需要时优化网络。例如，所收集的信息可用于交通监控，并根据运营商的政策可选地用于交通优化。
The "IPFIX Information Elements" registry [IANA-IPFIX] defines the following IEs for traffic flow information export in different granularities: sourceIPv4Address, sourceIPv4Prefix, destinationIPv4Address, destinationIPv4Prefix, bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address, etc. In some circumstances, however, traffic flow information based on these IEs may not be completely suitable or sufficient, especially when traffic engineering and optimization are executed in Tier 1 or Tier 2 operators' backbone networks. For example, flow information based on IP address or IP prefix may provide much too fine granularity for a large network. On the contrary, flow information based on Autonomous System Number (ASN) may be too coarse.
“IPFIX信息元素”注册表[IANA-IPFIX]定义了以下不同粒度的交通流信息导出IE：sourceIPv4Address、sourceIPv4Prefix、destinationIPv4Address、destinationIPv4Prefix、BGPSourceNumber、BGPDestationAsNumber、bgpNextHopIPv4Address等。但是，在某些情况下，基于这些IEs的交通流信息可能并不完全合适或充分，尤其是在一级或二级运营商主干网中执行交通工程和优化时。例如，基于IP地址或IP前缀的流信息可能为大型网络提供太细的粒度。相反，基于自治系统编号（ASN）的流量信息可能过于粗糙。
BGP community is a BGP path attribute that includes Standard Communities [RFC1997], Extended Communities [RFC4360], and Large Communities [RFC8092]. The BGP community attribute has a variety of use cases, one of which is to use BGP community with planned specific values to represent groups of customers, services, and geographical or topological regions, as used by operators in their networks. Detailed examples can be found in [RFC4384], [RFC8195], and Section 3 of this document. To understand the traffic generated 1) by different kinds of customers, 2) from different geographical or topological regions, or 3) by different kinds of customers from different regions, we need the community information corresponding to the traffic flow information exported by IPFIX. Network traffic statistics at the BGP community granularity are useful not only for traffic analysis, but also for use by other applications, such as traffic optimization applications located in an IPFIX Collector, Software-Defined Networking (SDN) controller, or PCE. [COMMUNITY-TE] also states that analyzing network traffic information at the BGP community granularity is preferred for inbound traffic engineering. However, the "IPFIX Information Elements" registry [IANA-IPFIX] lacked IEs defined for the BGP community attribute.
BGP社区是一个BGP路径属性，包括标准社区[RFC1997]、扩展社区[RFC4360]和大型社区[RFC8092]。BGP community属性有多种用例，其中一种是使用具有计划特定值的BGP community来表示运营商在其网络中使用的客户、服务和地理或拓扑区域组。详细示例见本文件的[RFC4384]、[RFC8195]和第3节。为了了解1）不同类型的客户产生的流量，2）来自不同地理或拓扑区域，或3）来自不同区域的不同类型的客户产生的流量，我们需要与IPFIX导出的流量信息相对应的社区信息。BGP社区粒度的网络流量统计信息不仅对流量分析有用，而且可供其他应用程序使用，例如位于IPFIX收集器、软件定义网络（SDN）控制器或PCE中的流量优化应用程序。[COMMUNITY-TE]还指出，在BGP社区粒度上分析网络流量信息是入站流量工程的首选。但是，“IPFIX信息元素”注册表[IANA-IPFIX]缺少为BGP社区属性定义的IEs。
Flow information based on the BGP community attribute may be collected by an IPFIX Mediator (defined in [RFC6183]). The IPFIX Mediator is responsible for the correlation between flow information and the BGP community attribute. However, no IEs are defined in [RFC6183] for exporting BGP community information in IPFIX. Furthermore, to correlate the BGP community attribute with the flow information, the IPFIX Mediator needs to learn BGP routes and perform lookups in the BGP routing table to get the matching entry for a specific flow. BGP route learning and routing table lookup are not trivial for an IPFIX Mediator. The IPFIX Mediator is mainly introduced to reduce the performance requirement for the Exporter [RFC5982]. In fact, to obtain information for the already-defined BGP-related IEs, such as bgpSourceAsNumber, bgpDestinationAsNumber, and bgpNextHopIPv4Address, etc., the Exporter has to hold the up-to-date BGP routing table and perform lookups in the table. The Exporter can obtain the BGP community information in the same procedure; thus, the additional load added by exporting BGP community information is minimal if the Exporter is already exporting the existing BGP-related IEs. It is RECOMMENDED that the BGP community information be exported by the Exporter directly using IPFIX.
基于BGP社区属性的流信息可由IPFIX中介（在[RFC6183]中定义）收集。IPFIX中介器负责流信息和BGP社区属性之间的关联。但是，[RFC6183]中没有定义用于在IPFIX中导出BGP社区信息的IEs。此外，为了将BGP社区属性与流信息关联起来，IPFIX中介需要了解BGP路由并在BGP路由表中执行查找，以获得特定流的匹配条目。BGP路由学习和路由表查找对于IPFIX中介来说并非微不足道。引入IPFIX中介器主要是为了降低导出器的性能要求[RFC5982]。事实上，要获取已定义的BGP相关IE的信息，如BGPSourceNumber、bgpDestinationAsNumber和bgpNextHopIPv4Address等，导出器必须持有最新的BGP路由表并在表中执行查找。出口商可以通过相同的程序获得BGP社区信息；因此，如果导出程序已经导出现有的BGP相关IEs，则导出BGP社区信息所增加的额外负载最小。建议导出者直接使用IPFIX导出BGP社区信息。
By running BGP [RFC4271] or the BGP Monitoring Protocol (BMP) [RFC7854] and performing lookups in the BGP routing table to correlate the matching entry for a specific flow, IPFIX Collectors and other applications, such as an SDN controller or PCE, can determine the network traffic at the BGP community granularity. However, running BGP or BMP and performing routing table lookup are not trivial for the IPFIX Collectors and other applications. Moreover, correlation between IPFIX flow information and the BGP RIB on the Exporter (such as a router) is more accurate compared to the correlation on a Collector, since the BGP routing table may be updated when the IPFIX Collectors and other applications receive the IPFIX flow information. As stated above, the Exporter can obtain the BGP community information during the same procedure when it obtains other BGP-related information. Therefore, exporting the BGP community information directly by the Exporter to the Collector is both efficient and accurate. If the IPFIX Collectors and other applications only want to determine the network traffic at the BGP community granularity, they do not need to run the full BGP or BMP protocols when the BGP community information can be obtained by IPFIX. However, BMP has its own application scenario, and the mechanism introduced in this document is not meant to replace it.
通过运行BGP[RFC4271]或BGP监控协议（BMP）[RFC7854]并在BGP路由表中执行查找以关联特定流的匹配项，IPFIX收集器和其他应用程序（如SDN控制器或PCE）可以确定BGP社区粒度的网络流量。但是，对于IPFIX收集器和其他应用程序来说，运行BGP或BMP并执行路由表查找并非易事。此外，与收集器上的相关性相比，导出器（例如路由器）上的IPFIX流信息和BGP RIB之间的相关性更准确，因为当IPFIX收集器和其他应用程序接收IPFIX流信息时，BGP路由表可能会更新。如上所述，出口商在获取其他BGP相关信息时，可以在相同的过程中获取BGP社区信息。因此，由导出器直接将BGP社区信息导出到收集器既高效又准确。如果IPFIX收集器和其他应用程序只想确定BGP社区粒度的网络流量，则当IPFIX可以获取BGP社区信息时，它们不需要运行完整的BGP或BMP协议。但是，BMP有自己的应用场景，本文档中介绍的机制并不是要取代它。
By introducing new IEs, this document extends the existing BGP-related IEs to enable IPFIX [RFC7011] to export BGP community information, including the BGP Standard Communities [RFC1997], BGP Extended Communities [RFC4360], and BGP Large Communities [RFC8092]. Flow information (including packetDeltaCount [RFC7011] [RFC7012],
通过引入新的IEs，本文档扩展了现有的BGP相关IEs，使IPFIX[RFC7011]能够导出BGP社区信息，包括BGP标准社区[RFC1997]、BGP扩展社区[RFC4360]和BGP大型社区[RFC8092]。流量信息（包括packetDeltaCount[RFC7011][RFC7012]，
octetDeltaCount [RFC7011] [RFC7012], etc.) can then be accumulated and analyzed by the Collector or other applications, such as an SDN controller or PCE [RFC4655], at the BGP community granularity. This is useful for measuring the traffic generated 1) by different kinds of customers or 2) from different geographical or topological regions according to the operator's BGP community plan. Flow information can then be used by the traffic engineering or traffic optimization applications, especially in the backbone network.
然后，收集器或其他应用程序（如SDN控制器或PCE[RFC4655]）可以在BGP社区粒度上累积和分析八进制数据量[RFC7011][RFC7012]等。根据运营商的BGP社区计划，这有助于测量1）由不同类型的客户或2）来自不同地理或拓扑区域的客户产生的流量。然后，流量工程或流量优化应用程序可以使用流量信息，特别是在主干网中。
The IEs introduced in this document are applicable to both IPv4 and IPv6 traffic. Both the Exporter and the IPFIX Mediator can use these IEs to export BGP community information in IPFIX. When needed, the IPFIX Mediator or Collector can use these IEs to report BGP community-related traffic flow information it gets either from Exporters or through local correlation to other IPFIX devices.
本文档中介绍的IEs适用于IPv4和IPv6流量。导出器和IPFIX中介器都可以使用这些IEs导出IPFIX中的BGP社区信息。需要时，IPFIX中介器或收集器可以使用这些IEs报告从导出器或通过与其他IPFIX设备的本地关联获得的BGP社区相关流量信息。
As stated above, the method introduced in this document is not the sole, definitive one for obtaining BGP community information related to a specific traffic flow, but it is possible, efficient, and accurate.
如上所述，本文件中介绍的方法不是获取特定交通流相关BGP社区信息的唯一、确定的方法，但它是可行、高效和准确的。
No new BGP community attributes are defined in this document.
本文档中未定义新的BGP社区属性。
Note that this document does not update the IPFIX specification [RFC7011] or information model [RFC7012]. Rather, the "IPFIX Information Elements" registry [IANA-IPFIX] contains the current complete reference for IPFIX Information Elements, per Section 1 of [RFC7012].
请注意，本文档不更新IPFIX规范[RFC7011]或信息模型[RFC7012]。相反，根据[RFC7012]第1节，“IPFIX信息元素”注册表[IANA-IPFIX]包含IPFIX信息元素的当前完整参考。
Please refer to the "IPFIX Information Elements" registry [IANA-IPFIX] for the complete list of BGP-related IEs.
有关BGP相关IE的完整列表，请参阅“IPFIX信息元素”注册表[IANA-IPFIX]。
Please refer to Appendix A of this document for the encoding example and Section 3 for a detailed use case.
编码示例请参见本文档附录A，详细用例请参见第3节。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
The IPFIX-specific terminology used in this document is defined in Section 2 of [RFC7011] and Section 2 of [RFC6183].
[RFC7011]第2节和[RFC6183]第2节定义了本文件中使用的IPFIX专用术语。
This document uses the term "BGP Standard Community" to refer to the BGP community attribute defined in [RFC1997] in order to distinguish it from BGP Extended Community [RFC4360] and Large Community [RFC8092].
本文档使用术语“BGP标准社区”来指代[RFC1997]中定义的BGP社区属性，以区别于BGP扩展社区[RFC4360]和大型社区[RFC8092]。
[RFC4384] introduces the mechanism of using BGP Standard Community and Extended Community to collect geographical and topological information in the BGP routing system. [RFC8195] gives some examples of the application of BGP Large Communities to represent the geographical regions. Since the network traffic at the BGP community granularity represents the traffic generated 1) by different kinds of customers or 2) from different geographical regions according to the network operator's BGP community plan, it is useful for network operators to analyze and optimize the network traffic among different customers and regions. This section gives a use case in which the network operator uses traffic information based on BGP community to adjust the network paths for different traffic flows.
[RFC4384]介绍了在BGP路由系统中使用BGP标准社区和扩展社区收集地理和拓扑信息的机制。[RFC8195]给出了应用BGP大型社区表示地理区域的一些示例。由于BGP社区粒度的网络流量表示1）由不同类型的客户或2）根据网络运营商的BGP社区计划从不同地理区域生成的流量，因此网络运营商分析和优化不同客户和区域之间的网络流量非常有用。本节给出了一个用例，其中网络运营商使用基于BGP社区的流量信息来调整不同流量的网络路径。
Consider the following scenario. Autonomous System (AS) C provides a transit connection between ASes A and B. By tagging different BGP communities, the routes of AS A and B are categorized into several groups in the operator's plan. For example, communities A:X and A:Y are used for routes that originated from different geographical regions in AS A, and communities B:M and B:N are used for routes representing the different kinds of customers in AS B (e.g., B:M is for mobile customers and B:N is for fixed line customers). By default, all traffic originating from AS A and destined for AS B (i.e., traffic A-B) goes through path C1-C2-C3 (i.e., Path-1) in AS C. When the link between C1 and C2 is congested, we cannot simply steer all the traffic A-B from Path-1 to Path C1-C4-C3 (i.e., Path-2) because it will cause congestion in Path-2.
考虑下面的场景。自治系统（AS）C在ASes a和B之间提供过境连接。通过标记不同的BGP社区，AS a和B的路线在运营商的计划中分为若干组。例如，社区A:X和A:Y用于来自AS A中不同地理区域的路由，社区B:M和B:N用于代表AS B中不同类型客户的路由（例如，B:M用于移动客户，B:N用于固定线路客户）。默认情况下，所有源自AS A且目的地为AS B的流量（即流量A-B）都通过AS C中的路径C1-C2-C3（即路径-1）。当C1和C2之间的链路拥塞时，我们不能简单地将所有流量A-B从路径-1转向路径C1-C4-C3（即路径-2），因为这将导致路径-2中的拥塞。
+----------+
| PCE/SDN |
+-------|Controller|-------+
| +----------+ |
| |
| AS C |
| | +----------+ | |
| | +---|Router C2 |---+ | |
| | | +----------+ | | |
AS A | | |100 50| | | AS B
+--------+ | +---------+ +---------+ | +--------+
|Router A|--|--|Router C1| |Router C3|--|--|Router B|
+--------+ | +---------+ +---------+ | +--------+
Community: | |100 100| | Community:
A:X | | +----------+ | | B:M
A:Y | +---|Router C4 |---+ | B:N
+----------+
+----------+
| PCE/SDN |
+-------|Controller|-------+
| +----------+ |
| |
| AS C |
| | +----------+ | |
| | +---|Router C2 |---+ | |
| | | +----------+ | | |
AS A | | |100 50| | | AS B
+--------+ | +---------+ +---------+ | +--------+
|Router A|--|--|Router C1| |Router C3|--|--|Router B|
+--------+ | +---------+ +---------+ | +--------+
Community: | |100 100| | Community:
A:X | | +----------+ | | B:M
A:Y | +---|Router C4 |---+ | B:N
+----------+
Figure 1: Traffic Collection Based on BGP Community
图1：基于BGP社区的流量收集
If the PCE/SDN controller in AS C can obtain network traffic information at the BGP community granularity, it can steer some traffic related to some BGP communities (when we consider only the source or destination of the traffic) or some BGP community pairs (when we consider both the source and the destination of the traffic) from Path-1 to Path-2 according to the utilization of different paths. For instance, it can steer the traffic generated by community A:X from Path-1 to Path-2 by deploying a route policy at Router C1 or steer the traffic from community A:Y to community B:M from Path-1 to Path-2. Using the IEs defined in this document, IPFIX can export the BGP community information related to a specific traffic flow together with other flow information. The traffic information can then be accumulated at the BGP community granularity and used by the PCE/SDN controller to steer the appropriate traffic from Path-1 to Path-2.
如果A/C中的PCE/SDN控制器可以在BGP社区粒度上获得网络流量信息，它可以引导一些与BGP社区相关的业务（当我们只考虑流量的源或目的地）或一些BGP社区对（当我们考虑流量的来源和目的地时）。根据不同路径的使用情况，从路径1到路径2。例如，它可以通过在路由器C1部署路由策略，将社区A:X生成的流量从路径1转向路径2，或者将社区A:Y的流量从路径1转向社区B:M的流量从路径1转向路径2。使用本文档中定义的IEs，IPFIX可以导出与特定流量相关的BGP社区信息以及其他流量信息。然后，可以在BGP社区粒度上累积流量信息，并由PCE/SDN控制器用于将适当的流量从路径1引导到路径2。
[RFC1997] defines the BGP community attribute (referred to as "BGP Standard Community" in this document), which describes a group of routes sharing some common properties. BGP Standard Community is treated as a 32-bit value, as stated in [RFC1997].
[RFC1997]定义了BGP社区属性（在本文档中称为“BGP标准社区”），它描述了一组共享一些公共属性的路由。BGP标准团体被视为32位值，如[RFC1997]所述。
In order to export BGP Standard Community information along with other flow information defined by IPFIX, this document introduces three new IEs:
为了导出BGP标准社区信息以及IPFIX定义的其他流信息，本文档引入了三个新的IEs：
o bgpCommunity - used to identify that the value in this IE is a BGP Standard Community.
o BGP社区-用于标识此IE中的值是BGP标准社区。
o bgpSourceCommunityList - a basicList [RFC6313] of bgpCommunity used to export BGP Standard Community information corresponding to a specific flow's source IP address.
o BGPSourceCommunity列表-BGP社区的基本列表[RFC6313]，用于导出对应于特定流的源IP地址的BGP标准社区信息。
o bgpDestinationCommunityList - a basicList [RFC6313] of bgpCommunity used to export BGP Standard Community information corresponding to a specific flow's destination IP address.
o bgpDestinationCommunity列表-bgpCommunity的基本列表[RFC6313]，用于导出对应于特定流的目标IP地址的BGP标准社区信息。
See Section 9 ("IANA Considerations") for detailed information about these three new IEs.
有关这三个新IEs的详细信息，请参见第9节（“IANA注意事项”）。
[RFC4360] defines the BGP Extended Communities attribute, which provides a mechanism for labeling the information carried in BGP. Each Extended Community is encoded as an 8-octet quantity with the format defined in [RFC4360].
[RFC4360]定义了BGP扩展社区属性，该属性提供了标记BGP中携带的信息的机制。每个扩展社区编码为8个八位字节，格式见[RFC4360]。
In order to export BGP Extended Community information together with other flow information by IPFIX, this document introduces three new IEs:
为了通过IPFIX将BGP扩展社区信息与其他流信息一起导出，本文档介绍了三种新的IEs：
o bgpExtendedCommunity - used to identify that the value in this IE is a BGP Extended Community.
o bgpExtendedCommunity-用于标识此IE中的值是BGP扩展社区。
o bgpSourceExtendedCommunityList - a basicList [RFC6313] of bgpExtendedCommunity used to export the BGP Extended Community information corresponding to a specific flow's source IP address.
o bgpSourceExtendedCommunityList—bgpExtendedCommunity的基本列表[RFC6313]，用于导出与特定流的源IP地址相对应的BGP扩展社区信息。
o bgpDestinationExtendedCommunityList - a basicList [RFC6313] of bgpExtendedCommunity used to export the BGP Extended Community information corresponding to a specific flow's destination IP address.
o bgpDestinationExtendedCommunityList—bgpExtendedCommunity的基本列表[RFC6313]，用于导出与特定流的目标IP地址相对应的BGP扩展社区信息。
See Section 9 ("IANA Considerations") for detailed information about these three new IEs.
有关这三个新IEs的详细信息，请参见第9节（“IANA注意事项”）。
[RFC8092] defines the BGP Large Communities attribute, which is suitable for use with all Autonomous System Numbers (ASNs), including 4-octet ASNs. Each BGP Large Community is encoded as a 12-octet quantity with the format defined in [RFC8092].
[RFC8092]定义BGP大型社区属性，该属性适用于所有自治系统编号（ASN），包括4个八位组ASN。每个BGP大型社区按照[RFC8092]中定义的格式编码为12个八位组。
In order to export BGP Large Community information together with other flow information by IPFIX, this document introduces three new IEs:
为了通过IPFIX将BGP大型社区信息与其他流量信息一起导出，本文档介绍了三种新的IEs：
o bgpLargeCommunity - used to identify that the value in this IE is a BGP Large Community.
o BGP大型社区-用于确定此IE中的值是BGP大型社区。
o bgpSourceLargeCommunityList - a basicList [RFC6313] of bgpLargeCommunity used to export the BGP Large Community information corresponding to a specific flow's source IP address.
o bgpSourceLargeCommunityList—bgpLargeCommunity的基本列表[RFC6313]，用于导出与特定流的源IP地址相对应的BGP大型社区信息。
o bgpDestinationLargeCommunityList - a basicList [RFC6313] of bgpLargeCommunity used to export the BGP Large Community information corresponding to a specific flow's destination IP address.
o bgpDestinationLargeCommunityList—bgpLargeCommunity的基本列表[RFC6313]，用于导出与特定流的目标IP地址相对应的BGP大型社区信息。
See Section 9 ("IANA Considerations") for detailed information about these three new IEs.
有关这三个新IEs的详细信息，请参见第9节（“IANA注意事项”）。
The maximum length of an IPFIX message is 65535 bytes as per [RFC7011], and the maximum length of a normal BGP message is 4096 bytes as per [RFC4271]. Since BGP communities, including Standard, Extended, and Large Communities, are BGP path attributes carried in BGP Update messages, the total length of these attributes cannot exceed the length of a BGP message, i.e., 4096 bytes. Therefore, one IPFIX message with a maximum length of 65535 bytes has enough space to fit all the communities relating to a specific flow's source and destination IP address.
根据[RFC7011]，IPFIX消息的最大长度为65535字节；根据[RFC4271]，正常BGP消息的最大长度为4096字节。由于BGP社区（包括标准社区、扩展社区和大型社区）是BGP更新消息中携带的BGP路径属性，因此这些属性的总长度不能超过BGP消息的长度，即4096字节。因此，一条最大长度为65535字节的IPFIX消息有足够的空间容纳与特定流的源和目标IP地址相关的所有社区。
[EXT-MSG] extends the maximum size of a BGP Update message to 65535 bytes. In that case, the BGP community information related to a specific flow could theoretically exceed the length of one IPFIX message. However, according to information regarding actual networks in the field, the number of BGP communities in one BGP route is usually no more than ten. Nevertheless, BGP speakers that support the extended message SHOULD only convey as many communities as possible without exceeding the 65535-byte limit of an IPFIX message. The Collector, which receives an IPFIX message with the maximum length and BGP communities contained in its data set, SHOULD generate a warning or log message to indicate that the BGP communities may be truncated due to limited message space. In this case, it is recommended that the export policy of BGP communities be configured to limit the BGP communities by including or excluding specific communities.
[EXT-MSG]将BGP更新消息的最大大小扩展到65535字节。在这种情况下，与特定流相关的BGP社区信息理论上可能超过一条IPFIX消息的长度。然而，根据有关现场实际网络的信息，一条BGP路由中的BGP社区数量通常不超过十个。尽管如此，支持扩展消息的BGP扬声器应只传送尽可能多的社区，而不超过IPFIX消息的65535字节限制。收集器接收的IPFIX消息具有其数据集中包含的最大长度和BGP社区，应生成警告或日志消息，以指示BGP社区可能因消息空间有限而被截断。在这种情况下，建议将BGP社区的导出策略配置为通过包括或排除特定社区来限制BGP社区。
If needed, the IPFIX message length can be extended from 16 bits to 32 bits to solve this problem completely. The details about increasing the IPFIX message length is out of scope of this document.
如果需要，IPFIX消息长度可以从16位扩展到32位，以完全解决此问题。有关增加IPFIX消息长度的详细信息超出了本文档的范围。
To align with the sizes of the BGP Extended Community and Large Community attributes, the sizes of bgpExtendedCommunity and bgpLargeCommunity are 8 octets and 12 octets, respectively. In the event that the bgpExtendedCommunity or bgpLargeCommunity IE is not the expected size, the IPFIX Collector SHOULD ignore it. This is intended to protect implementations using BGP logic from calling their parsing routines with invalid lengths.
为了与BGP扩展社区和大型社区属性的大小保持一致，bgpExtendedCommunity和BGPLARGEComunity的大小分别为8个八位字节和12个八位字节。如果bgpExtendedCommunity或bgpLargeCommunity不是预期的大小，IPFIX收集器应该忽略它。这是为了防止使用BGP逻辑的实现调用长度无效的解析例程。
To properly process the Exporter when it receives the template requesting to report the BGP community information (refer to Appendix A for an example), the Exporter SHOULD obtain the corresponding BGP community information through a BGP lookup using the corresponding source or destination IP address of the specific traffic flow. When exporting the IPFIX information to the Collector, the Exporter SHOULD include the corresponding BGP communities in the IPFIX message.
为了在收到请求报告BGP社区信息的模板时正确处理导出器（示例请参阅附录A），导出器应使用特定流量的相应源或目标IP地址，通过BGP查找获得相应的BGP社区信息。将IPFIX信息导出到收集器时，导出器应在IPFIX消息中包含相应的BGP社区。
This document defines new IEs for IPFIX. The same security considerations as for the IPFIX protocol specification [RFC7011] and information model [RFC7012] apply.
本文档定义了IPFIX的新IEs。IPFIX协议规范[RFC7011]和信息模型[RFC7012]的安全注意事项同样适用。
Systems processing BGP community information collected by IPFIX Collectors need to be aware of the use of communities as an attack vector [WEAPONIZING-BGP] and only include BGP community information in decisions where they are confident of its validity. Thus, we cannot assume that all BGP community information collected by IPFIX Collectors is credible and accurate. It is RECOMMENDED to use only the IPFIX-collected BGP community information that the processing system can trust, for example, the BGP communities generated by the consecutive neighboring ASes within the same trust domain as the processing system (i.e., the consecutive neighboring ASes and the processing system are operated by one carrier).
系统处理由IpFig收藏家收集的BGP社区信息需要知道社区作为攻击向量的使用[武器装备BGP]，并且只在决策者确信其有效性的情况下包括BGP社区信息。因此，我们不能假设IPFIX收集器收集的所有BGP社区信息都是可信和准确的。建议仅使用处理系统可以信任的IPFIX收集的BGP社区信息，例如，由与处理系统在同一信任域内的连续相邻ASE生成的BGP社区（即，连续相邻ASE和处理系统由一个运营商操作）。
[RFC7011] notes that the storage of the information collected by IPFIX must be protected and its visibility confined to authorized users via technical as well as policy means to ensure the privacy of the information collected. [RFC7011] also provides mechanisms to ensure the confidentiality and integrity of IPFIX data transferred from an Exporting Process to a Collecting Process. The mechanism to authenticate IPFIX Collecting and Exporting Processes is also provided in [RFC7011]. If sensitive information is contained in the
[RFC7011]注意到，必须通过技术和政策手段保护IPFIX收集的信息的存储，其可见性仅限于授权用户，以确保收集的信息的隐私。[RFC7011]还提供了确保从导出过程传输到收集过程的IPFIX数据的机密性和完整性的机制。[RFC7011]中还提供了对IPFIX收集和导出过程进行身份验证的机制。如果敏感信息包含在
community information, the above recommendations and mechanisms are recommended. No additional privacy risks are introduced by this document.
社区信息、上述建议和机制均为建议。本文件不涉及其他隐私风险。
This document specifies IPFIX IEs to enable export of BGP community information along with other flow information. IANA has assigned the following ElementIDs for these IEs in the "IPFIX Information Elements" registry [IANA-IPFIX]:
本文档指定了IPFIX IEs，以支持BGP社区信息和其他流信息的导出。IANA已在“IPFIX信息元素”注册表[IANA-IPFIX]中为这些IE分配了以下元素ID：
----------------------------------------------------------------------
|ElementID| Name |Abstract | Data Type |
| | |Data Type | Semantics |
|--------------------------------------------------------------------|
| 483 | bgpCommunity |unsigned32 | identifier |
|--------------------------------------------------------------------|
| 484 | bgpSourceCommunityList | basicList | list |
|--------------------------------------------------------------------|
| 485 |bgpDestinationCommunityList| basicList | list |
|--------------------------------------------------------------------|
| 486 | bgpExtendedCommunity |octetArray | default |
|--------------------------------------------------------------------|
| 487 | bgpSourceExtended | | |
| | CommunityList | basicList | list |
|--------------------------------------------------------------------|
| 488 | bgpDestinationExtended | | |
| | CommunityList | basicList | list |
|--------------------------------------------------------------------|
| 489 | bgpLargeCommunity |octetArray | default |
|--------------------------------------------------------------------|
| 490 |bgpSourceLargeCommunityList| basicList | list |
|--------------------------------------------------------------------|
| 491 | bgpDestinationLarge | | |
| | CommunityList | basicList | list |
|--------------------------------------------------------------------|
----------------------------------------------------------------------
|ElementID| Name |Abstract | Data Type |
| | |Data Type | Semantics |
|--------------------------------------------------------------------|
| 483 | bgpCommunity |unsigned32 | identifier |
|--------------------------------------------------------------------|
| 484 | bgpSourceCommunityList | basicList | list |
|--------------------------------------------------------------------|
| 485 |bgpDestinationCommunityList| basicList | list |
|--------------------------------------------------------------------|
| 486 | bgpExtendedCommunity |octetArray | default |
|--------------------------------------------------------------------|
| 487 | bgpSourceExtended | | |
| | CommunityList | basicList | list |
|--------------------------------------------------------------------|
| 488 | bgpDestinationExtended | | |
| | CommunityList | basicList | list |
|--------------------------------------------------------------------|
| 489 | bgpLargeCommunity |octetArray | default |
|--------------------------------------------------------------------|
| 490 |bgpSourceLargeCommunityList| basicList | list |
|--------------------------------------------------------------------|
| 491 | bgpDestinationLarge | | |
| | CommunityList | basicList | list |
|--------------------------------------------------------------------|
----------------------------------------------------------
|ElementID| Description |
|---------------------------------------------------------
| 483 | BGP community as defined in [RFC1997] |
|---------------------------------------------------------
| | basicList of zero or more bgpCommunity IEs, |
| 484 | containing the BGP communities corresponding|
| | with source IP address of a specific flow |
|---------------------------------------------------------
| | basicList of zero or more bgpCommunity IEs, |
| 485 |containing the BGP communities corresponding |
| |with destination IP address of a specific flow|
|---------------------------------------------------------
| 486 |BGP Extended Community as defined in RFC 4360;|
| |the size of this IE MUST be 8 octets |
|---------------------------------------------------------
| |basicList of zero or more bgpExtendedCommunity|
| 487 |IEs, containing the BGP Extended Communities |
| |corresponding with source IP address of |
| | a specific flow |
|---------------------------------------------------------
| |basicList of zero or more bgpExtendedCommunity|
| 488 |IEs, containing the BGP Extended Communities |
| | corresponding with destination IP address |
| | of a specific flow |
|---------------------------------------------------------
| 489 | BGP Large Community as defined in [RFC8092]; |
| | the size of this IE MUST be 12 octets |
|---------------------------------------------------------
| | basicList of zero or more bgpLargeCommunity |
| | IEs, containing the BGP Large Communities |
| 490 | corresponding with source IP address |
| | of a specific flow |
|---------------------------------------------------------
| | basicList of zero or more bgpLargeCommunity |
| | IEs, containing the BGP Large Communities |
| 491 | corresponding with destination IP address |
| | of a specific flow |
|---------------------------------------------------------
----------------------------------------------------------
|ElementID| Description |
|---------------------------------------------------------
| 483 | BGP community as defined in [RFC1997] |
|---------------------------------------------------------
| | basicList of zero or more bgpCommunity IEs, |
| 484 | containing the BGP communities corresponding|
| | with source IP address of a specific flow |
|---------------------------------------------------------
| | basicList of zero or more bgpCommunity IEs, |
| 485 |containing the BGP communities corresponding |
| |with destination IP address of a specific flow|
|---------------------------------------------------------
| 486 |BGP Extended Community as defined in RFC 4360;|
| |the size of this IE MUST be 8 octets |
|---------------------------------------------------------
| |basicList of zero or more bgpExtendedCommunity|
| 487 |IEs, containing the BGP Extended Communities |
| |corresponding with source IP address of |
| | a specific flow |
|---------------------------------------------------------
| |basicList of zero or more bgpExtendedCommunity|
| 488 |IEs, containing the BGP Extended Communities |
| | corresponding with destination IP address |
| | of a specific flow |
|---------------------------------------------------------
| 489 | BGP Large Community as defined in [RFC8092]; |
| | the size of this IE MUST be 12 octets |
|---------------------------------------------------------
| | basicList of zero or more bgpLargeCommunity |
| | IEs, containing the BGP Large Communities |
| 490 | corresponding with source IP address |
| | of a specific flow |
|---------------------------------------------------------
| | basicList of zero or more bgpLargeCommunity |
| | IEs, containing the BGP Large Communities |
| 491 | corresponding with destination IP address |
| | of a specific flow |
|---------------------------------------------------------
----------------------------------------------------------
|ElementID| References | Requester | Revision |
|---------------------------------------------------------
| 483 | RFC 1997 | RFC 8549 | 0 |
|---------------------------------------------------------
| 484 | RFC 6313, RFC 1997 | RFC 8549 | 0 |
|---------------------------------------------------------
| 485 | RFC 6313, RFC 1997 | RFC 8549 | 0 |
|---------------------------------------------------------
| 486 | RFC 4360 | RFC 8549 | 0 |
|---------------------------------------------------------
| 487 | RFC 6313, RFC 4360 | RFC 8549 | 0 |
|---------------------------------------------------------
| 488 | RFC 6313, RFC 4360 | RFC 8549 | 0 |
|---------------------------------------------------------
| 489 | RFC 8092 | RFC 8549 | 0 |
|---------------------------------------------------------
| 490 | RFC 6313, RFC 8092 | RFC 8549 | 0 |
|---------------------------------------------------------
| 491 | RFC 6313, RFC 8092 | RFC 8549 | 0 |
|---------------------------------------------------------
----------------------------------------------------------
|ElementID| References | Requester | Revision |
|---------------------------------------------------------
| 483 | RFC 1997 | RFC 8549 | 0 |
|---------------------------------------------------------
| 484 | RFC 6313, RFC 1997 | RFC 8549 | 0 |
|---------------------------------------------------------
| 485 | RFC 6313, RFC 1997 | RFC 8549 | 0 |
|---------------------------------------------------------
| 486 | RFC 4360 | RFC 8549 | 0 |
|---------------------------------------------------------
| 487 | RFC 6313, RFC 4360 | RFC 8549 | 0 |
|---------------------------------------------------------
| 488 | RFC 6313, RFC 4360 | RFC 8549 | 0 |
|---------------------------------------------------------
| 489 | RFC 8092 | RFC 8549 | 0 |
|---------------------------------------------------------
| 490 | RFC 6313, RFC 8092 | RFC 8549 | 0 |
|---------------------------------------------------------
| 491 | RFC 6313, RFC 8092 | RFC 8549 | 0 |
|---------------------------------------------------------
Figure 2: Updates to "IPFIX Information Elements" Registry
图2：“IPFIX信息元素”注册表的更新
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, "Export of Structured Data in IP Flow Information Export (IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011, <https://www.rfc-editor.org/info/rfc6313>.
[RFC6313]Claise，B.，Dhandapani，G.，Aitken，P.，和S.Yates，“IP流信息导出（IPFIX）中结构化数据的导出”，RFC 6313，DOI 10.17487/RFC6313，2011年7月<https://www.rfc-editor.org/info/rfc6313>.
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information", STD 77, RFC 7011, DOI 10.17487/RFC7011, September 2013, <https://www.rfc-editor.org/info/rfc7011>.
[RFC7011]Claise，B.，Ed.，Trammell，B.，Ed.，和P.Aitken，“流量信息交换的IP流量信息导出（IPFIX）协议规范”，STD 77，RFC 7011，DOI 10.17487/RFC7011，2013年9月<https://www.rfc-editor.org/info/rfc7011>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[COMMUNITY-TE] Shao, W., Devienne, F., Iannone, L., and J. Rougier, "On the use of BGP communities for fine-grained inbound traffic engineering", Computer Science: Networking and Internet Architecture, November 2015, <https://arxiv.org/abs/1511.08336>.
[COMMUNITY-TE]Shao，W.，Devienne，F.，Iannone，L.，和J.Rougier，“关于BGP社区用于细粒度入站流量工程”，计算机科学：网络和互联网架构，2015年11月<https://arxiv.org/abs/1511.08336>.
[EXT-MSG] Bush, R., Patel, K., and D. Ward, "Extended Message support for BGP", Work in Progress, draft-ietf-idr-bgp-extended-messages-30, March 2019.
[EXT-MSG]Bush，R.，Patel，K.，和D.Ward，“BGP的扩展消息支持”，正在进行的工作，草稿-ietf-idr-BGP-Extended-messages-3022019年3月。
[IANA-IPFIX] IANA, "IP Flow Information Export (IPFIX) Entities", <http://www.iana.org/assignments/ipfix/>.
[IANA-IPFIX]IANA，“IP流信息导出（IPFIX）实体”<http://www.iana.org/assignments/ipfix/>.
[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, <https://www.rfc-editor.org/info/rfc1997>.
[RFC1997]Chandra，R.，Traina，P.，和T.Li，“BGP社区属性”，RFC 1997，DOI 10.17487/RFC1997，1996年8月<https://www.rfc-editor.org/info/rfc1997>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, <https://www.rfc-editor.org/info/rfc4271>.
[RFC4271]Rekhter，Y.，Ed.，Li，T.，Ed.，和S.Hares，Ed.，“边境网关协议4（BGP-4）”，RFC 4271，DOI 10.17487/RFC4271，2006年1月<https://www.rfc-editor.org/info/rfc4271>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, February 2006, <https://www.rfc-editor.org/info/rfc4360>.
[RFC4360]Sangli，S.，Tappan，D.和Y.Rekhter，“BGP扩展社区属性”，RFC 4360，DOI 10.17487/RFC4360，2006年2月<https://www.rfc-editor.org/info/rfc4360>.
[RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, RFC 4384, DOI 10.17487/RFC4384, February 2006, <https://www.rfc-editor.org/info/rfc4384>.
[RFC4384]Meyer，D.，“BGP社区用于数据收集”，BCP 114，RFC 4384，DOI 10.17487/RFC4384，2006年2月<https://www.rfc-editor.org/info/rfc4384>.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation Element (PCE)-Based Architecture", RFC 4655, DOI 10.17487/RFC4655, August 2006, <https://www.rfc-editor.org/info/rfc4655>.
[RFC4655]Farrel，A.，Vasseur，J.，和J.Ash，“基于路径计算元素（PCE）的体系结构”，RFC 4655，DOI 10.17487/RFC4655，2006年8月<https://www.rfc-editor.org/info/rfc4655>.
[RFC5982] Kobayashi, A., Ed. and B. Claise, Ed., "IP Flow Information Export (IPFIX) Mediation: Problem Statement", RFC 5982, DOI 10.17487/RFC5982, August 2010, <https://www.rfc-editor.org/info/rfc5982>.
[RFC5982]Kobayashi，A.，Ed.和B.Claise，Ed.，“IP流信息导出（IPFIX）调解：问题陈述”，RFC 5982，DOI 10.17487/RFC5982，2010年8月<https://www.rfc-editor.org/info/rfc5982>.
[RFC6183] Kobayashi, A., Claise, B., Muenz, G., and K. Ishibashi, "IP Flow Information Export (IPFIX) Mediation: Framework", RFC 6183, DOI 10.17487/RFC6183, April 2011, <https://www.rfc-editor.org/info/rfc6183>.
[RFC6183]Kobayashi，A.，Claise，B.，Muenz，G.，和K.Ishibashi，“IP流信息导出（IPFIX）中介：框架”，RFC 6183，DOI 10.17487/RFC6183，2011年4月<https://www.rfc-editor.org/info/rfc6183>.
[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model for IP Flow Information Export (IPFIX)", RFC 7012, DOI 10.17487/RFC7012, September 2013, <https://www.rfc-editor.org/info/rfc7012>.
[RFC7012]Claise，B.，Ed.和B.Trammell，Ed.，“IP流信息导出（IPFIX）的信息模型”，RFC 7012，DOI 10.17487/RFC7012，2013年9月<https://www.rfc-editor.org/info/rfc7012>.
[RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP Monitoring Protocol (BMP)", RFC 7854, DOI 10.17487/RFC7854, June 2016, <https://www.rfc-editor.org/info/rfc7854>.
[RFC7854]Scudder，J.，Ed.，Fernando，R.，和S.Stuart，“BGP监测协议（BMP）”，RFC 7854，DOI 10.17487/RFC7854，2016年6月<https://www.rfc-editor.org/info/rfc7854>.
[RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas, I., and N. Hilliard, "BGP Large Communities Attribute", RFC 8092, DOI 10.17487/RFC8092, February 2017, <https://www.rfc-editor.org/info/rfc8092>.
[RFC8092]Heitz，J.，Ed.，Snijders，J.，Ed.，Patel，K.，Bagdonas，I.，和N.Hilliard，“BGP大社区属性”，RFC 8092，DOI 10.17487/RFC8092，2017年2月<https://www.rfc-editor.org/info/rfc8092>.
[RFC8195] Snijders, J., Heasley, J., and M. Schmidt, "Use of BGP Large Communities", RFC 8195, DOI 10.17487/RFC8195, June 2017, <https://www.rfc-editor.org/info/rfc8195>.
[RFC8195]Snijders，J.，Heasley，J.，和M.Schmidt，“BGP大型社区的使用”，RFC 8195，DOI 10.17487/RFC8195，2017年6月<https://www.rfc-editor.org/info/rfc8195>.
[WEAPONIZING-BGP] Streibelt, F., Lichtblau, F., Beverly, R., Pelsser, C., Smaragdakis, G., Bush, R., and A. Feldmann, "Weaponizing BGP Using Communities", November 2018, <https://datatracker.ietf.org/meeting/103/materials/ slides-103-grow-bgp-communities-spread-their-wings-01>.
[WEAPONIZING-BGP]Streibelt，F.，Lichtblau，F.，Beverly，R.，Pelsser，C.，Smaragdakis，G.，Bush，R.，和A.Feldmann，“使用社区对BGP进行武器化”，2018年11月<https://datatracker.ietf.org/meeting/103/materials/ 幻灯片-103-grow-bgp-communities-spread-thes-wings-01>。
In this section, we provide an example to show the encoding format for the newly introduced IEs.
在本节中，我们提供了一个示例来展示新引入的IEs的编码格式。
Flow information, including BGP communities, is shown in the following table. In this example, all the fields are reported by IPFIX.
流量信息，包括BGP社区，如下表所示。在本例中，所有字段都由IPFIX报告。
----------------------------------------------------------------------
| Source |Destination| BGP community | BGP community |
| IP | IP | corresponding with | corresponding with |
| | | Source IP | Destination IP |
----------------------------------------------------------------------
| 1.1.1.1 | 2.2.2.2 | 1:1001, 1:1002, 8:1001 | 2:1002, 8:1001 |
----------------------------------------------------------------------
| 3.3.3.3 | 4.4.4.4 | 3:1001, 3:1002, 8:1001 | 4:1001, 8:1001 |
----------------------------------------------------------------------
----------------------------------------------------------------------
| Source |Destination| BGP community | BGP community |
| IP | IP | corresponding with | corresponding with |
| | | Source IP | Destination IP |
----------------------------------------------------------------------
| 1.1.1.1 | 2.2.2.2 | 1:1001, 1:1002, 8:1001 | 2:1002, 8:1001 |
----------------------------------------------------------------------
| 3.3.3.3 | 4.4.4.4 | 3:1001, 3:1002, 8:1001 | 4:1001, 8:1001 |
----------------------------------------------------------------------
Figure 3: Flow Information Including BGP Communities
图3：流量信息，包括BGP社区
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SET ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 256 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| SourceIPv4Address = 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| DestinationIPv4Address = 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| bgpSourceCommunityList=484 | Field Length = 0xFFFF |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| bgpDestinationCommunityList | Field Length = 0xFFFF |
| | = 485 | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SET ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 256 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| SourceIPv4Address = 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| DestinationIPv4Address = 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| bgpSourceCommunityList=484 | Field Length = 0xFFFF |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| bgpDestinationCommunityList | Field Length = 0xFFFF |
| | = 485 | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Template Record Encoding Format
图4：模板记录编码格式
In this example, the Template ID is 256, which will be used in the Data Record. The field length for bgpSourceCommunityList and bgpDestinationCommunityList is 0xFFFF, which means the length of this IE is variable, and the actual length of this IE is indicated by the List Length field in the basicList format as per [RFC6313].
在本例中，模板ID为256，将在数据记录中使用。bgpSourceCommunityList和BGPDestinitionCommunityList的字段长度为0xFFFF，这意味着此IE的长度是可变的，此IE的实际长度由基本列表格式的列表长度字段表示，如[RFC6313]所示。
The data set is represented as follows:
数据集表示如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SET ID = 256 | Length = 92 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SourceIPv4Address = 1.1.1.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DestinationIPv4Address = 2.2.2.2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 17 |semantic=allof |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 1 = 1:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 2 = 1:1002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 3 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 13 |semantic=allof |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 1 = 2:1002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 2 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SourceIPv4Address = 3.3.3.3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DestinationIPv4Address = 4.4.4.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 17 | semantic=allof|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 1 = 3:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 2 = 3:1002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 3 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 13 | semantic=allof|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SET ID = 256 | Length = 92 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SourceIPv4Address = 1.1.1.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DestinationIPv4Address = 2.2.2.2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 17 |semantic=allof |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 1 = 1:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 2 = 1:1002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 3 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 13 |semantic=allof |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 1 = 2:1002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 2 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SourceIPv4Address = 3.3.3.3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DestinationIPv4Address = 4.4.4.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 17 | semantic=allof|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 1 = 3:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 2 = 3:1002 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Source Community Value 3 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List Length = 13 | semantic=allof|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 483 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 1 = 4:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 2 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 1 = 4:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 2 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Data Set Encoding Format
图5：数据集编码格式
Acknowledgements
致谢
The authors would like to thank Benoit Claise and Paul Aitken for their comments and suggestions to promote this document. The authors would also like thank Tianran Zhou, Warren Kumari, Jeffrey Haas, Ignas Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared Mauch, Rudiger Volk, and Andrew Malis for their discussion, comments, and suggestions for improving this document.
作者要感谢Benoit Claise和Paul Aitken为推广本文件提出的意见和建议。作者还要感谢周天然、沃伦·库马里、杰弗里·哈斯、伊格纳斯·巴格多纳斯、斯图尔特·布莱恩特、保罗·朗森特、乔布斯·斯奈德斯、贾里德·莫奇、鲁迪格·沃尔克和安德鲁·马利斯为改进本文件所作的讨论、评论和建议。
Authors' Addresses
作者地址
Zhenqiang Li China Mobile 32 Xuanwumen West Ave, Xicheng District Beijing 100053 China
中国移动北京市西城区宣武门西大街32号，邮编100053
Email: li_zhenqiang@hotmail.com
Email: li_zhenqiang@hotmail.com
Rong Gu China Mobile 32 Xuanwumen West Ave, Xicheng District Beijing 100053 China
中国移动北京市西城区宣武门西大街32号荣固100053
Email: gurong_cmcc@outlook.com
Email: gurong_cmcc@outlook.com
Jie Dong Huawei Technologies Huawei Campus, No. 156 Beiqing Rd. Beijing 100095 China
中国北京市北青路156号华为校园华为技术有限公司，邮编：100095
Email: jie.dong@huawei.com
Email: jie.dong@huawei.com