draft-ietf-opsawg-ipfix-bgp-community-05.txt   draft-ietf-opsawg-ipfix-bgp-community-06.txt 
opsawg Z. Li opsawg Z. Li
Internet-Draft R. Gu Internet-Draft R. Gu
Updates: 7012 (if approved) China Mobile Intended status: Standards Track China Mobile
Intended status: Standards Track J. Dong Expires: September 23, 2018 J. Dong
Expires: September 6, 2018 Huawei Technologies Huawei Technologies
March 5, 2018 March 22, 2018
Export BGP community information in IP Flow Information Export (IPFIX) Export BGP community information in IP Flow Information Export (IPFIX)
draft-ietf-opsawg-ipfix-bgp-community-05 draft-ietf-opsawg-ipfix-bgp-community-06
Abstract Abstract
This draft updates RFC7012 IPFIX information model by introducing This draft introduces several information elements (IEs) to enable
several information elements (IEs) to enable IPFIX to export the BGP IPFIX [RFC7011] to export the BGP community information, including
community information, including BGP standard community defined in the information of BGP standard community [RFC1997], BGP extended
RFC1997, BGP extended community defined in RFC4360, and BGP large community [RFC4360], and BGP large community [RFC8092]. Network
community defined in RFC8092. Network traffic flow information can traffic information can then be accumulated and analysed at the BGP
then be accumulated and analysed at the granularity specified by the community granularity, which represents the traffic of different
BGP communities, which is suitable for and needed by some traffic kinds of customers, services, or geographical regions according to
optimization applications located in IPFIX collector, SDN controller the network operator's BGP community planning. Network traffic
or PCE (Path Computation Element). information at the BGP community granularity is useful for network
traffic analysis and engineering.
To clarify, no new BGP community attribute is defined in this To clarify, no new BGP community attribute is defined in this
document and this document has no purpose to replace BGP Monitoring document and this document has no purpose to replace BGP Monitoring
Protocol BMP defined in RFC7854. The IEs introduced in this document Protocol (BMP) defined in RFC7854. The IEs introduced in this
are used by IPFIX together with other IEs to facilitate the IPFIX document are used by IPFIX together with other IEs to facilitate the
collector analyzing the traffic in BGP community granularity without IPFIX collector analyzing the network traffic at the BGP community
running the heavy BGP protocol. granularity without running the heavy BGP protocol.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 6, 2018. This Internet-Draft will expire on September 23, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. BGP Community based Traffic Collection . . . . . . . . . . . 5 3. BGP Community based Traffic Collection . . . . . . . . . . . 5
4. IEs for BGP Standard Community . . . . . . . . . . . . . . . 6 4. IEs for BGP Standard Community . . . . . . . . . . . . . . . 6
4.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 7 4.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 7
4.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 7 4.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 7
4.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 7 4.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 8
5. IEs for BGP Extended Community . . . . . . . . . . . . . . . 8 5. IEs for BGP Extended Community . . . . . . . . . . . . . . . 8
5.1. bgpExtendedCommunity . . . . . . . . . . . . . . . . . . 8 5.1. bgpExtendedCommunity . . . . . . . . . . . . . . . . . . 8
5.2. bgpSourceExtendedCommunityList . . . . . . . . . . . . . 9 5.2. bgpSourceExtendedCommunityList . . . . . . . . . . . . . 9
5.3. bgpDestinationExtendedCommunityList . . . . . . . . . . . 9 5.3. bgpDestinationExtendedCommunityList . . . . . . . . . . . 9
6. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 10 6. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 10
6.1. bgpLargeCommunity . . . . . . . . . . . . . . . . . . . . 10 6.1. bgpLargeCommunity . . . . . . . . . . . . . . . . . . . . 10
6.2. bgpSourceLargeCommunityList . . . . . . . . . . . . . . . 11 6.2. bgpSourceLargeCommunityList . . . . . . . . . . . . . . . 11
6.3. bgpDestinationLargeCommunityList . . . . . . . . . . . . 11 6.3. bgpDestinationLargeCommunityList . . . . . . . . . . . . 11
7. Operational Considerations . . . . . . . . . . . . . . . . . 12 7. Operational Considerations . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
skipping to change at page 3, line 34 skipping to change at page 3, line 34
prefix may provide much too fine granularity for a large network. On prefix may provide much too fine granularity for a large network. On
the contrary, flow information based on AS number may be too coarse. the contrary, flow information based on AS number may be too coarse.
BGP community is a BGP path attribute defined in IDR (Inter Domain BGP community is a BGP path attribute defined in IDR (Inter Domain
Routing) working group. The already defined BGP community attribute Routing) working group. The already defined BGP community attribute
includes the standard community defined in [RFC1997], the extended includes the standard community defined in [RFC1997], the extended
community defined in [RFC4360], and the large community defined in community defined in [RFC4360], and the large community defined in
[RFC8092]. BGP community attribute has a variety of use cases, one [RFC8092]. BGP community attribute has a variety of use cases, one
common practice of which for the operators is to use BGP community common practice of which for the operators is to use BGP community
with planned specific values in their field networks to represent the with planned specific values in their field networks to represent the
groups of customers, peers, geographical and topological regions. groups of customers, services, geographical and topological regions.
Please refer to [RFC4384], [RFC8195] and Section 3 of this document Please refer to [RFC4384], [RFC8195] and Section 3 of this document
for the detailed examples. To know the traffic generated by differnt for the detailed examples. To know the traffic generated by differnt
kinds of customers, from differnt geographical or topological kinds of customers, from differnt geographical or topological
regions, by differnt kinds of customers in differnt regions, we need regions, by differnt kinds of customers in differnt regions, we need
the corresponding community information related to the traffic flow the corresponding community information related to the traffic flow
exported by IPFIX. Netwok traffic statistic in BGP community exported by IPFIX. Netwok traffic statistic at the BGP community
granularity is useful not only for the traffic analyzing, but also granularity is useful not only for the traffic analyzing, but also
can then be used by other applications, such as the traffic can then be used by other applications, such as the traffic
optimization applications located in IPFIX collector, SDN controller optimization applications located in IPFIX collector, SDN controller
or PCE. [Community-TE] also states analyzing network traffic or PCE. [Community-TE] also states analyzing network traffic
information at the granularity specified by BGP community is prefered information at the BGP community granularity is prefered for inbound
for inbound traffic engineering. However, there is no IE defined for traffic engineering. However, there is no IE defined for BGP
BGP community attribute in [IANA-IPFIX] yet. community attribute in [IANA-IPFIX] yet.
Flow information based on BGP community may be collected by a Flow information based on BGP community may be collected by a
mediator defined in [RFC6183]. Mediator is responsible for the mediator defined in [RFC6183]. Mediator is responsible for the
correlation between flow information and BGP community. However no correlation between flow information and BGP community. However no
IEs are defined in [RFC6183] for exporting BGP community information IEs are defined in [RFC6183] for exporting BGP community information
in IPFIX. Furthermore, to correlate the BGP community with the flow in IPFIX. Furthermore, to correlate the BGP community with the flow
information, mediator needs to learn BGP routes and perform lookup in information, mediator needs to learn BGP routes and perform lookup in
the BGP routing table to get the matching entry for a specific flow. the BGP routing table to get the matching entry for a specific flow.
Neither BGP route learning nor routing table lookup is trivial for a Neither BGP route learning nor routing table lookup is trivial for a
mediator. Mediator is mainly introduced to release the performance mediator. Mediator is mainly introduced to release the performance
skipping to change at page 4, line 23 skipping to change at page 4, line 23
routing table and perform lookup in the BGP routing table. The routing table and perform lookup in the BGP routing table. The
exporter can obtain the BGP community information in the same exporter can obtain the BGP community information in the same
procedure, thus exporting BGP community information adds no more procedure, thus exporting BGP community information adds no more
requirement for exporter. It is RECOMMENDED that the BGP community requirement for exporter. It is RECOMMENDED that the BGP community
information be exported by the exporter directly using IPFIX. information be exported by the exporter directly using IPFIX.
Through running BGP [RFC4271] or BMP [RFC7854] and performing lookup Through running BGP [RFC4271] or BMP [RFC7854] and performing lookup
in the BGP routing table to get the matching entry for a specific in the BGP routing table to get the matching entry for a specific
flow (we call it correlation), IPFIX collectors and other flow (we call it correlation), IPFIX collectors and other
applications, such as SDN controller or PCE, can figure up the applications, such as SDN controller or PCE, can figure up the
network traffic at BGP community granularity. However,neither network traffic at the BGP community granularity. However, neither
running BGP or BMP protocol nor routing table lookup is trivial for running BGP or BMP protocol nor routing table lookup is trivial for
the IPFIX collectors and other applications. Moreover correlation the IPFIX collectors and other applications. Moreover correlation
between IPFIX flow information and the BGP RIB on the exporter (such between IPFIX flow information and the BGP RIB on the exporter (such
as router) is more accurate, compared to the correlation on a as router) is more accurate, compared to the correlation on a
collector, since the BGP routing table may be updated when the IPFIX collector, since the BGP routing table may be updated when the IPFIX
collectors and other applications reveive the IPFIX flow information. collectors and other applications reveive the IPFIX flow information.
And as stated above, the exporter can obtain the BGP community And as stated above, the exporter can obtain the BGP community
information in the same procedure when it obtains other BGP related information in the same procedure when it obtains other BGP related
informaiton. So exporting the BGP community information directly by informaiton. So exporting the BGP community information directly by
the exporter to the collector is the efficient and accurate way. If the exporter to the collector is the efficient and accurate way. If
the IPFIX collectors and other applications only want to figure up the IPFIX collectors and other applications only want to figure up
the network traffic at BGP community granularity, they do not need to the network traffic at the BGP community granularity, they do not
run the heavy BGP or BMP protocol when the BGP community information need to run the heavy BGP or BMP protocol when the BGP community
can be obtained by IPFIX. However, we have to clarify, the BMP information can be obtained by IPFIX. However, we have to clarify,
protocol has its own application scenario, the mechanisum introduced the BMP protocol has its own application scenario, the mechanisum
in this document has no purpose to replace it. introduced in this document has no purpose to replace it.
This draft introduces new IEs to extend the IPFIX information model This draft introduces new IEs to enable IPFIX [RFC7011] to export the
defined in [RFC7012] to export the BGP community information, BGP community information, including BGP standard community defined
including BGP standard community defined in [RFC1997], BGP extended in [RFC1997], BGP extended community defined in [RFC4360], and BGP
community defined in [RFC4360], and BGP large community defined in large community defined in [RFC8092]. Flow information, including
[RFC8092]. Flow information, including packetDeltaCount, packetDeltaCount, octetDeltaCount [RFC7012] etc, can then be
octetDeltaCount [RFC7012] etc, can then be accumulated and analysed accumulated and analysed by the collector or other applications, such
by the collector or other applications, such as SDN controller or PCE as SDN controller or PCE [RFC4655], at the BGP community granularity,
[RFC4655], at the granularity specified by BGP community , which is which is useful for knowing the traffic generted by different kinds
useful for knowing the traffic generted by different kinds of of customers, from differnt geographical or topological regions
customers, from differnt geographical or topological regions
according to the operator's BGP community plan, and can then be used according to the operator's BGP community plan, and can then be used
by the traffic engineering or traffic optimization applications, by the traffic engineering or traffic optimization applications,
especially in the backbone network. To clarify, no new BGP community especially in the backbone network. To clarify, no new BGP community
attribute is defined in this document, IDR (Inter Domain Routing) attribute is defined in this document, IDR (Inter Domain Routing)
working group is the right place to define new community attributes working group is the right place to define new community attributes
for the BGP protocol. for the BGP protocol.
The IEs introduced in this document are applicable for both IPv4 and The IEs introduced in this document are applicable for both IPv4 and
IPv6 traffic. Both exporter and mediator can use these IEs to export IPv6 traffic. Both exporter and mediator can use these IEs to export
BGP community information in IPFIX. BGP community information in IPFIX.
Note that this document does not update the IPFIX specification
[RFC7011] and the Information Model [RFC7012] because IANA's IPFIX
registry [IANA-IPFIX] is the ultimate Information Element reference,
per Section 1 of [RFC7012].
Please refer Appendix A for the encoding example and Section 3 for a Please refer Appendix A for the encoding example and Section 3 for a
detailed use case. detailed use case.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. BGP Community based Traffic Collection 3. BGP Community based Traffic Collection
skipping to change at page 6, line 26 skipping to change at page 6, line 30
|Router A|--|--|Router C1| |Router C3|--|--|Router B| |Router A|--|--|Router C1| |Router C3|--|--|Router B|
+--------+ | +---------+ +---------+ | +--------+ +--------+ | +---------+ +---------+ | +--------+
Community: | |100 100| | Community: Community: | |100 100| | Community:
A:X | | +----------+ | | B:M A:X | | +----------+ | | B:M
A:Y | +---|Router C4 |---+ | B:N A:Y | +---|Router C4 |---+ | B:N
+----------+ +----------+
Figure 1: BGP Community based Traffic Collection Figure 1: BGP Community based Traffic Collection
If the PCE/SDN controller in AS C can obtain the network traffic If the PCE/SDN controller in AS C can obtain the network traffic
information at BGP community granularity, it can steer some traffic information at the BGP community granularity, it can steer some
related to some BGP communities (when we consider only the source or traffic related to some BGP communities (when we consider only the
destination of the traffic), or some BGP community pairs (when we source or destination of the traffic), or some BGP community pairs
consider both the source and the destination of the traffic) from (when we consider both the source and the destination of the traffic)
Path-1 to Path-2 according to the utilization of different paths. from Path-1 to Path-2 according to the utilization of different
For instance, steer the traffic generated by community A:X from paths. For instance, steer the traffic generated by community A:X
Path-1 to Path-2 by deploying route policy at Router C1, or steer the from Path-1 to Path-2 by deploying route policy at Router C1, or
traffic from community A:Y to community B:M from Path-1 to Path-2. steer the traffic from community A:Y to community B:M from Path-1 to
Using the IEs defined in this document, IPFIX can export the BGP Path-2. Using the IEs defined in this document, IPFIX can export the
community information related to a specific traffic flow togecher BGP community information related to a specific traffic flow togecher
with other flow information. The traffic information can then be with other flow information. The traffic information can then be
accumulated at BGP community granularity and used by the PCE/SDN accumulated at the BGP community granularity and used by the PCE/SDN
controller to steer the appropriate traffic from Path-1 to Path-2. controller to steer the appropriate traffic from Path-1 to Path-2.
4. IEs for BGP Standard Community 4. IEs for BGP Standard Community
[RFC1997] defines the BGP Communities attribute, called BGP Standard [RFC1997] defines the BGP Communities attribute, called BGP Standard
Community in this document, which describes a group of routes sharing Community in this document, which describes a group of routes sharing
some common properties. BGP Standard Communities are treated as 32 some common properties. BGP Standard Communities are treated as 32
bit values as stated in[RFC1997]. bit values as stated in[RFC1997].
In order to export BGP standard community information along with In order to export BGP standard community information along with
skipping to change at page 13, line 21 skipping to change at page 13, line 21
and 12 octets respectively. In the event that the and 12 octets respectively. In the event that the
bgpExtendedCommunity or bgpLargeCommunity Elements are not of their bgpExtendedCommunity or bgpLargeCommunity Elements are not of their
expected sizes (8 and 12 octets, respectively), the IPFIX collector expected sizes (8 and 12 octets, respectively), the IPFIX collector
SHOULD ignore them. This is intended to protect implementations SHOULD ignore them. This is intended to protect implementations
using BGP logic from calling their parsing routines with invalid using BGP logic from calling their parsing routines with invalid
lengths. lengths.
For the proper processing of the exporter, when it receives the For the proper processing of the exporter, when it receives the
template requesting to report the BGP community information (refer template requesting to report the BGP community information (refer
Appendix A for an example), the exporter SHOULD obtain the Appendix A for an example), the exporter SHOULD obtain the
coressponding BGP community information through BGP lookup using the corresponding BGP community information through BGP lookup using the
corresponding source or destination IP of the specific traffic flow. corresponding source or destination IP of the specific traffic flow.
When exporting the IPFIX information to the collector, the exporter When exporting the IPFIX information to the collector, the exporter
SHOULD include the corresponding BGP communities in the IPFIX SHOULD include the corresponding BGP communities in the IPFIX
message. message.
8. Security Considerations 8. Security Considerations
This document only defines three new IEs for IPFIX. This document This document only defines three new IEs for IPFIX. This document
itself does not directly introduce security issues. The same itself does not directly introduce security issues. The same
security considerations as for the IPFIX Protocol Specification security considerations as for the IPFIX Protocol Specification
skipping to change at page 16, line 16 skipping to change at page 16, line 16
"Export of Structured Data in IP Flow Information Export "Export of Structured Data in IP Flow Information Export
(IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011, (IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011,
<https://www.rfc-editor.org/info/rfc6313>. <https://www.rfc-editor.org/info/rfc6313>.
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,
"Specification of the IP Flow Information Export (IPFIX) "Specification of the IP Flow Information Export (IPFIX)
Protocol for the Exchange of Flow Information", STD 77, Protocol for the Exchange of Flow Information", STD 77,
RFC 7011, DOI 10.17487/RFC7011, September 2013, RFC 7011, DOI 10.17487/RFC7011, September 2013,
<https://www.rfc-editor.org/info/rfc7011>. <https://www.rfc-editor.org/info/rfc7011>.
[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>.
11.2. Informative References 11.2. Informative References
[Community-TE] [Community-TE]
Shao, W., Devienne, F., Iannone, L., and JL. Rougier, "On Shao, W., Devienne, F., Iannone, L., and JL. Rougier, "On
the use of BGP communities for fine-grained inbound the use of BGP communities for fine-grained inbound
traffic engineering", Computer Science 27392(1):476-487, traffic engineering", Computer Science 27392(1):476-487,
November 2015. November 2015.
[I-D.ietf-idr-bgp-extended-messages] [I-D.ietf-idr-bgp-extended-messages]
Bush, R., Patel, K., and D. Ward, "Extended Message Bush, R., Patel, K., and D. Ward, "Extended Message
skipping to change at page 17, line 24 skipping to change at page 17, line 20
[RFC5982] Kobayashi, A., Ed. and B. Claise, Ed., "IP Flow [RFC5982] Kobayashi, A., Ed. and B. Claise, Ed., "IP Flow
Information Export (IPFIX) Mediation: Problem Statement", Information Export (IPFIX) Mediation: Problem Statement",
RFC 5982, DOI 10.17487/RFC5982, August 2010, RFC 5982, DOI 10.17487/RFC5982, August 2010,
<https://www.rfc-editor.org/info/rfc5982>. <https://www.rfc-editor.org/info/rfc5982>.
[RFC6183] Kobayashi, A., Claise, B., Muenz, G., and K. Ishibashi, [RFC6183] Kobayashi, A., Claise, B., Muenz, G., and K. Ishibashi,
"IP Flow Information Export (IPFIX) Mediation: Framework", "IP Flow Information Export (IPFIX) Mediation: Framework",
RFC 6183, DOI 10.17487/RFC6183, April 2011, RFC 6183, DOI 10.17487/RFC6183, April 2011,
<https://www.rfc-editor.org/info/rfc6183>. <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>.
[RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP [RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP
Monitoring Protocol (BMP)", RFC 7854, Monitoring Protocol (BMP)", RFC 7854,
DOI 10.17487/RFC7854, June 2016, DOI 10.17487/RFC7854, June 2016,
<https://www.rfc-editor.org/info/rfc7854>. <https://www.rfc-editor.org/info/rfc7854>.
[RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas, [RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas,
I., and N. Hilliard, "BGP Large Communities Attribute", I., and N. Hilliard, "BGP Large Communities Attribute",
RFC 8092, DOI 10.17487/RFC8092, February 2017, RFC 8092, DOI 10.17487/RFC8092, February 2017,
<https://www.rfc-editor.org/info/rfc8092>. <https://www.rfc-editor.org/info/rfc8092>.
 End of changes. 18 change blocks. 
58 lines changed or deleted 63 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/