draft-ietf-opsawg-ipfix-bgp-community-02.txt   draft-ietf-opsawg-ipfix-bgp-community-03.txt 
opsawg Z. Li opsawg Z. Li
Internet-Draft R. Gu Internet-Draft R. Gu
Intended status: Standards Track China Mobile Updates: 7012 (if approved) China Mobile
Expires: December 22, 2017 J. Dong Intended status: Standards Track J. Dong
Huawei Technologies Expires: April 20, 2018 Huawei Technologies
June 20, 2017 October 17, 2017
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-02 draft-ietf-opsawg-ipfix-bgp-community-03
Abstract Abstract
This draft introduces several information elements in IPFIX This draft updates RFC7012 IPFIX information model by introducing
information model [RFC7012] to enable IPFIX [RFC7011] to export the several information elements to enable IPFIX to export the BGP
BGP community information, including standard community defined in community information, including BGP standard community defined in
[RFC1997], extended community defined in [RFC4360], large community RFC1997, BGP extended community defined in RFC4360, and BGP large
defined in [RFC8092], community container defined in community defined in RFC8092. Network traffic flow information can
[I-D.ietf-idr-wide-bgp-communities]. then be accumulated and analysed at the granularity specified by the
BGP communities, which is suitable for and needed by some traffic
optimization applications located in IPFIX collector, SDN controller
or PCE (Path Computation Element).
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 http://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 December 22, 2017. This Internet-Draft will expire on April 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. IEs for BGP Standard Community . . . . . . . . . . . . . . . 4 3. IEs for BGP Standard Community . . . . . . . . . . . . . . . 4
3.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 4 3.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 4
3.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 4 3.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 4
3.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 5 3.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 5
4. IEs for BGP Extended Community . . . . . . . . . . . . . . . 5 4. IEs for BGP Extended Community . . . . . . . . . . . . . . . 5
4.1. bgpExtendedCommunity . . . . . . . . . . . . . . . . . . 6 4.1. bgpExtendedCommunity . . . . . . . . . . . . . . . . . . 6
4.2. bgpSourceExtendedCommunityList . . . . . . . . . . . . . 6 4.2. bgpSourceExtendedCommunityList . . . . . . . . . . . . . 6
4.3. bgpDestinationExtendedCommunityList . . . . . . . . . . . 7 4.3. bgpDestinationExtendedCommunityList . . . . . . . . . . . 7
5. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 7 5. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 7
5.1. bgpLargeCommunity . . . . . . . . . . . . . . . . . . . . 8 5.1. bgpLargeCommunity . . . . . . . . . . . . . . . . . . . . 8
5.2. bgpSourceLargeCommunityList . . . . . . . . . . . . . . . 8 5.2. bgpSourceLargeCommunityList . . . . . . . . . . . . . . . 8
5.3. bgpDestinationLargeCommunityList . . . . . . . . . . . . 9 5.3. bgpDestinationLargeCommunityList . . . . . . . . . . . . 9
6. IEs for BGP Community Container . . . . . . . . . . . . . . . 9 6. Operational Considerations . . . . . . . . . . . . . . . . . 9
7. Message Length Considerations . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12
11.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.2. Informative References . . . . . . . . . . . . . . . . . 13
11.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Application Example . . . . . . . . . . . . . . . . 14 Appendix A. Application Example . . . . . . . . . . . . . . . . 14
A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 14 A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 14
A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 15 A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
IP Flow Information Export (IPFIX) [RFC7011] provides network IP Flow Information Export (IPFIX) [RFC7011] provides network
administrators with traffic flow information using the information administrators with traffic flow information using the information
elements (IEs) defined in [IANA-IPFIX] registries. Based on the elements (IEs) defined in [IANA-IPFIX] registries. Based on the
traffic flow information, network administrators know the amount and traffic flow information, network administrators know the amount and
direction of the traffic in their network, then they can optimize direction of the traffic in their network, then they can optimize
their network when needed. For example, they can steer some flows their network when needed. For example, they can shift some flows
from the congested links to the low utilized links. from the congested links to the low utilized links through a SDN
controller or PCE [RFC4655].
[IANA-IPFIX] has already defined the following IEs for traffic flow [IANA-IPFIX] has already defined the following IEs for traffic flow
information exporting in different grain: sourceIPv4Address, information exporting in different granularities: sourceIPv4Address,
sourceIPv4Prefix, destinationIPv4Address, destinationIPv4Prefix, sourceIPv4Prefix, destinationIPv4Address, destinationIPv4Prefix,
bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address, bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address,
etc. In some circumstances, however, especially when traffic etc. In some circumstances, however, especially when traffic
engineering and optimization are used in the Tier 1 or Tier 2 engineering and optimization are executed in the Tier 1 or Tier 2
operators' backbone networks, traffic flow information based on these operators' backbone networks, traffic flow information based on these
IEs is not suitable. Flow information based on IP address or IP IEs may not be suitable. Flow information based on IP address or IP
prefix is much more mediculous. On the contrary, flow information prefix may provide much too fine granularity for a large network. On
based on AS number is too coarse. BGP community [RFC1997], which the contrary, flow information based on AS number may be too coarse.
describes a group of routes sharing some common properties, is BGP community [RFC1997], which describes a group of routes sharing
preferably used for fine granularity traffic engineering some common properties, is preferably used for traffic engineering at
[Community-TE] [RFC4384]. Unfortunately, [IANA-IPFIX] has no IE the proper granularity [Community-TE] [RFC4384]. There is no IE
defined for BGP community information, yet. defined for BGP community information in [IANA-IPFIX] yet.
Flow information based on BGP community can 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 lookup in the BGP information, mediator needs to learn BGP routes and perform lookup in
routing table to get the matching entry for the specific flow. the BGP routing table to get the matching entry for 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
requirement for the exporter [RFC5982]. In fact, to obtain the requirement for the exporter [RFC5982]. In fact, to obtain the
information for BGP related IEs that have already been defined, such information for BGP related IEs that have already been defined, such
as bgpSourceAsNumber, bgpDestinationAsNumber, and as bgpSourceAsNumber, bgpDestinationAsNumber, and
bgpNextHopIPv4Address, etc, exporter has to hold the up-to-date BGP bgpNextHopIPv4Address, etc, exporter has to hold the up-to-date BGP
routing table and look up in the BGP routing table. The exporter can routing table and perform lookup in the BGP routing table. The
get the community information in the same procedure. So, getting BGP exporter can obtain the BGP community information in the same
community information adds no more requirement for exporter. Some procedure, thus exporting BGP community information adds no more
vendors have already implemented this feature in their exporters requirement for exporter. It is RECOMMENDED that the BGP community
using private IEs. So, exporter is RECOMMENDED to export the BGP information be exported by the exporter directly using IPFIX.
community information in IPFIX directly, other than the mediator.
This draft introduces new IEs to extend the IPFIX information model This draft introduces new IEs to extend the IPFIX information model
defined in [RFC7012] to export the BGP community information, defined in [RFC7012] to export the BGP community information,
including standard community defined in [RFC1997], extended community including BGP standard community defined in [RFC1997], BGP extended
defined in [RFC4360], large community defined in [RFC8092], and community defined in [RFC4360], and BGP large community defined in
community container defined in [I-D.ietf-idr-wide-bgp-communities]. [RFC8092]. Flow information, including packetDeltaCount,
Flow information, such as packetDeltaCount, octetDeltaCount [RFC7012] octetDeltaCount [RFC7012] etc, can then be accumulated and analysed
etc, can then be accumulated and analysed by the collector or other by the collector or other applications, such as SDN controller or PCE
applications based on BGP community. [RFC4655], at the granularity specified by BGP community , which is
useful for traffic engineering or traffic optimization applications,
especially in the backbone network.
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.
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. IEs for BGP Standard Community 3. 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 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
other flow information defined by IPFIX, three new IEs are other flow information defined by IPFIX, three new IEs are
introduced. One is bgpCommunity, which is used to identify that the introduced. One is bgpCommunity, which is used to identify that the
value in this IE is a BGP standard community. The other two are value in this IE is a BGP standard community. The other two are
bgpSourceCommunityList and bgpDestinationCommunityList, which are bgpSourceCommunityList and bgpDestinationCommunityList, which are
both basicList [RFC6313] of bgpCommunity, and are used to export BGP both basicList [RFC6313] of bgpCommunity, and are used to export BGP
standard community information corresponding to a specific flow's standard community information corresponding to a specific flow's
source IP and destination IP respectively. source IP and destination IP respectively.
skipping to change at page 5, line 43 skipping to change at page 5, line 43
| |with destination IP address of a specific flow| | |with destination IP address of a specific flow|
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
| Units | none | | Units | none |
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
Figure 3: bgpDestinationCommunityList Figure 3: bgpDestinationCommunityList
4. IEs for BGP Extended Community 4. IEs for BGP Extended Community
[RFC4360] defines the BGP Extended Communities attribute, which [RFC4360] defines the BGP Extended Communities attribute, which
provides a mechanism for labeling information carried in BGP. Each provides a mechanism for labeling the information carried in BGP.
Extended Community is encoded as an 8-octet quantity with the format Each Extended Community is encoded as an 8-octet quantity with the
defined in [RFC4360]. format defined in [RFC4360].
In order to export BGP Extended Community information together with In order to export BGP Extended Community information together with
other flow information by IPFIX, three new IEs are introduced. The other flow information by IPFIX, three new IEs are introduced. The
first one is bgpExtendedCommunity, which is used to identify that the first one is bgpExtendedCommunity, which is used to identify that the
value in this IE is a BGP Extended Community. The other two are value in this IE is a BGP Extended Community. The other two are
bgpSourceExtendedCommunityList and bgpSourceExtendedCommunityList and
bgpDestinationExtendedCommunityList, which are both basicList bgpDestinationExtendedCommunityList, which are both basicList
[RFC6313] of bgpExtendedCommunity, and are used to export the BGP [RFC6313] of bgpExtendedCommunity, and are used to export the BGP
Extended Community information corresponding to a specific flow's Extended Community information corresponding to a specific flow's
source IP and destination IP respectively. source IP and destination IP respectively.
skipping to change at page 9, line 42 skipping to change at page 9, line 42
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
| Description | zero or more BGP Large communities | | Description | zero or more BGP Large communities |
| | corresponding with destination IP address | | | corresponding with destination IP address |
| | of a specific flow | | | of a specific flow |
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
| Units | none | | Units | none |
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
Figure 9: bgpDestinationLargeCommunityList Figure 9: bgpDestinationLargeCommunityList
6. IEs for BGP Community Container 6. Operational Considerations
TBD.
7. Message Length Considerations
The maximum length of one IPFIX message is 65535 bytes as per The maximum length of an IPFIX message is 65535 bytes as per
[RFC7011] and 4096 bytes for one BGP message as per [RFC4271]. Since [RFC7011] , and the maximum length of a normal BGP message is 4096
BGP communities, including standard, extended, large and container, bytes as per [RFC4271]. Since BGP communities, including standard,
are BGP path attributes distributed in update messages, the length of extended, and large communities , are BGP path attributes carried in
them can not exceed the length of a BGP message, i.e. 4096. So one BGP Update messages, the total length of these attributes can not
IPFIX message with maximum length of 65535 has enough space to fit exceed the length of a BGP message, i.e. 4096 bytes. So one IPFIX
message with maximum length of 65535 bytes has enough space to fit
all the communities related to a specific flow, both the source IP all the communities related to a specific flow, both the source IP
and the destination IP related. and the destination IP related.
[I-D.ietf-idr-bgp-extended-messages], however, extends the maximum [I-D.ietf-idr-bgp-extended-messages] extends the maximum size of a
update message size of BGP beyond 4096 bytes to 65535 bytes. BGP BGP Update message to 65535 bytes. Then theoretically the BGP
speakers that support the extended message SHOULD take care to handle community information related to a specific flow may exceed the
the IPFIX message properly, such as only convey as many communities length one IPFIX message. However, according to the information
as possible in the IPFIX message. The collector who receives an about the networks in the field, the number of BGP communities in one
IPFIX message with maximum length and BGP communities contained in BGP route is usually no more than 10. Nevertheless, BGP speakers
its data set SHOULD be aware of the BGP communities may be truncated that support the extended message SHOULD be careful to export the BGP
due to limited message space. In this case, it is RECOMMENDED to communities in the IPFIX message properly, such as only convey as
configure export policy on the exporter to limit the BGP communities many communities as possible in the IPFIX message. The collector
to be exported, to export only some specific communities, for which receives an IPFIX message with maximum length and BGP
example, or not to export some communities. communities contained in its data set SHOULD be aware that the BGP
communities may be truncated due to limited message space. In this
case, it is RECOMMENDED to configure export policy of BGP communities
on the exporter to limit the BGP communities to be exported, so as to
only export some specific communities,or not to export some specific
communities.
To solve this problem completely, a separate document will be If needed, we may consider to extend the message length of IPFIX
submitted to extend the message length of IPFIX [RFC7011] to 32 bits. [RFC7011] from 16 bits to 32 bits to solve this problem completely.
The detailed mechanism is out of the scope of this document.
8. Security Considerations 7. Security Considerations
This document only defines three new IEs for IPFIX. So, this This document only defines three new IEs for IPFIX. This document
document itself does not directly introduce security issues. The itself does not directly introduce security issues. The same
same security considerations as for the IPFIX Protocol Specification security considerations as for the IPFIX Protocol Specification
[RFC7011] and Information Model [RFC7012] apply. [RFC7011] and Information Model [RFC7012] apply.
As the BGP community information is deducible by other means, there As the BGP community information is deducible by other means, there
are no increased privacy concerns, neither. are no increased privacy concerns, neither.
9. IANA Considerations 8. IANA Considerations
This draft specifies the following IPFIX IEs to export BGP community This draft specifies the following IPFIX IEs to export BGP community
information along with other flow information. information along with other flow information.
The Element IDs for these IEs are solicited to be assigned by IANA. The Element IDs for these IEs are solicited to be assigned by IANA.
The following table is for IANA's reference to put in each field in The following table is for IANA's reference to put in each field in
the registry. the registry.
---------------------------------------------------------------------- ----------------------------------------------------------------------
|ElementID| Name | Data Type|Data Type Semantics| |ElementID| Name | Data Type|Data Type Semantics|
skipping to change at page 12, line 36 skipping to change at page 12, line 35
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
| TBA7 | | RFC8092 |this draft | 0 | | | TBA7 | | RFC8092 |this draft | 0 | |
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
| TBA8 | |RFC6313,RFC8092|this draft | 0 | | | TBA8 | |RFC6313,RFC8092|this draft | 0 | |
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
| TBA9 | |RFC6313,RFC8092|this draft | 0 | | | TBA9 | |RFC6313,RFC8092|this draft | 0 | |
|--------------------------------------------------------------------| |--------------------------------------------------------------------|
Figure 10: IANA Considerations Figure 10: IANA Considerations
10. Acknowledgements 9. Acknowledgements
The authors would like to thank Benoit Claise and Paul Aitken for The authors would like to thank Benoit Claise and Paul Aitken for
their comments and suggestions to promote this document. their comments and suggestions to promote this document.
Appreciations are given to Tianran Zhou, Jeffrey Haas, Ignas Appreciations are given to Tianran Zhou, Warren Kumari, Jeffrey Haas,
Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared Mauch, Ignas Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared
etc, for their discussion in the mail list. Mauch, Rudiger Volk, etc, for their discussion, comments and
suggestions in the face to face meetings and in the mail list.
11. References 10. References
11.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates,
"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,
<http://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,
<http://www.rfc-editor.org/info/rfc7011>. <https://www.rfc-editor.org/info/rfc7011>.
[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012, for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013, DOI 10.17487/RFC7012, September 2013,
<http://www.rfc-editor.org/info/rfc7012>. <https://www.rfc-editor.org/info/rfc7012>.
11.2. Informative References 10.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
support for BGP", draft-ietf-idr-bgp-extended-messages-21 support for BGP", draft-ietf-idr-bgp-extended-messages-22
(work in progress), March 2017. (work in progress), August 2017.
[I-D.ietf-idr-wide-bgp-communities]
Raszuk, R., Haas, J., Lange, A., Decraene, B., Amante, S.,
and P. Jakma, "BGP Community Container Attribute", draft-
ietf-idr-wide-bgp-communities-04 (work in progress), March
2017.
[IANA-IPFIX] [IANA-IPFIX]
"IP Flow Information Export (IPFIX) Entities", "IP Flow Information Export (IPFIX) Entities",
<http://www.iana.org/assignments/ipfix/>. <http://www.iana.org/assignments/ipfix/>.
[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,
<http://www.rfc-editor.org/info/rfc1997>. <https://www.rfc-editor.org/info/rfc1997>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<http://www.rfc-editor.org/info/rfc4271>. <https://www.rfc-editor.org/info/rfc4271>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
February 2006, <http://www.rfc-editor.org/info/rfc4360>. February 2006, <https://www.rfc-editor.org/info/rfc4360>.
[RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114,
RFC 4384, DOI 10.17487/RFC4384, February 2006, RFC 4384, DOI 10.17487/RFC4384, February 2006,
<http://www.rfc-editor.org/info/rfc4384>. <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>.
[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,
<http://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,
<http://www.rfc-editor.org/info/rfc6183>. <https://www.rfc-editor.org/info/rfc6183>.
[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,
<http://www.rfc-editor.org/info/rfc8092>. <https://www.rfc-editor.org/info/rfc8092>.
Appendix A. Application Example Appendix A. Application Example
In this section, we give an example to show the encoding format for In this section, we give an example to show the encoding format for
the three new introduced IEs. the three new introduced IEs.
Flow information including BGP communities is shown in the below Flow information including BGP communities is shown in the below
table. Suppose we want all the fields to be reported by IPFIX. table. Suppose we want all the fields to be reported by IPFIX.
|Source ip|Destination ip |Source BGP community|Destination BGP community| -----------------------------------------------------------------------
| 1.1.1.1 | 2.2.2.2 |1:1001,1:1002,8:1001| 2:1002,8:1001 | |Source ip|Destination ip |Source BGP community| Destination BGP |
| 3.3.3.3 | 4.4.4.4 |3:1001,3:1002,8:1001| 4:1001,8:1001 | | | | | community |
-----------------------------------------------------------------------
| 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 11: Flow information including BGP communities Figure 11: Flow information including BGP communities
A.1. Template Record A.1. Template Record
0 1 2 3 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 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 | | SET ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 256 | Field Count = 4 | | Template ID = 256 | Field Count = 4 |
 End of changes. 43 change blocks. 
111 lines changed or deleted 123 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/