draft-ietf-opsawg-ipfix-bgp-community-01.txt   draft-ietf-opsawg-ipfix-bgp-community-02.txt 
opsawg Z. Li, Ed. opsawg Z. Li
Internet-Draft R. Gu, Ed. Internet-Draft R. Gu
Intended status: Standards Track China Mobile Intended status: Standards Track China Mobile
Expires: September 8, 2017 J. Dong Expires: December 22, 2017 J. Dong
Huawei Technologies Huawei Technologies
March 7, 2017 June 20, 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-01 draft-ietf-opsawg-ipfix-bgp-community-02
Abstract Abstract
This draft specifies an extension to the IPFIX information model This draft introduces several information elements in IPFIX
defined in [RFC7012] to export the BGP community [RFC1997] information model [RFC7012] to enable IPFIX [RFC7011] to export the
information. Three information elements, bgpCommunity, BGP community information, including standard community defined in
bgpSourceCommunityList and bgpDestinationCommunityList, are [RFC1997], extended community defined in [RFC4360], large community
introduced in this document to carry the BGP community information. defined in [RFC8092], community container defined in
bgpCommunity, containing exactly one BGP community value, is used to [I-D.ietf-idr-wide-bgp-communities].
consist the list in bgpSourceCommunityList and
bgpDestinationCommunityList, which are corresponding to a specific
flow's source IP and destination IP respectively.
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 http://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 8, 2017. This Internet-Draft will expire on December 22, 2017.
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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. BGP Community Information Elements . . . . . . . . . . . . . 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. Security Considerations . . . . . . . . . . . . . . . . . . . 5 4. IEs for BGP Extended Community . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4.1. bgpExtendedCommunity . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 4.2. bgpSourceExtendedCommunityList . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.3. bgpDestinationExtendedCommunityList . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 7 5. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 7 5.1. bgpLargeCommunity . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Application Example . . . . . . . . . . . . . . . . 8 5.2. bgpSourceLargeCommunityList . . . . . . . . . . . . . . . 8
A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 8 5.3. bgpDestinationLargeCommunityList . . . . . . . . . . . . 9
A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 9 6. IEs for BGP Community Container . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 7. Message Length Considerations . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
11.1. Normative References . . . . . . . . . . . . . . . . . . 12
11.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Application Example . . . . . . . . . . . . . . . . 14
A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 14
A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 15
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 steer some flows
from the congested links to the low utilized links. from the congested links to the low utilized links.
skipping to change at page 2, line 51 skipping to change at page 3, line 10
information exporting in different grain: sourceIPv4Address, information exporting in different grain: 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 used 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 is not suitable. Flow information based on IP address or IP
prefix is much more mediculous. On the contrary, flow information prefix is much more mediculous. On the contrary, flow information
based on AS number is too coarse. BGP community [RFC1997], which based on AS number is too coarse. BGP community [RFC1997], which
describes a group of routes sharing some common properties, is describes a group of routes sharing some common properties, is
preferablely used for fine granularity traffic engineering preferably used for fine granularity traffic engineering
[Community-TE] [RFC4384]. Unfortunately, [IANA-IPFIX] has no IE [Community-TE] [RFC4384]. Unfortunately, [IANA-IPFIX] has no IE
defined for BGP community information, yet. defined for BGP community information, yet.
Flow information based on BGP community can be collected by a Flow information based on BGP community can 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 lookup in the BGP
routing table to get the matching entry for the specific flow. routing table to get the matching entry for the specific flow.
skipping to change at page 3, line 28 skipping to change at page 3, line 34
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 look up in the BGP routing table. The exporter can
get the community information in the same procedure. So, getting BGP get the community information in the same procedure. So, getting BGP
community information adds no more requirement for exporter. Some community information adds no more requirement for exporter. Some
vendors have already implemented this feature in their exporters vendors have already implemented this feature in their exporters
using private IEs. So, exporter is RECOMMENDED to export the BGP using private IEs. So, exporter is RECOMMENDED to export the BGP
community information in IPFIX directly, other than the mediator. community information in IPFIX directly, other than the mediator.
This draft specifies an extension to the IPFIX information model This draft introduces new IEs to extend the IPFIX information model
defined in [RFC7012] to export the BGP community information. Three defined in [RFC7012] to export the BGP community information,
IEs, bgpCommunity, bgpSourceCommunityList and including standard community defined in [RFC1997], extended community
bgpDestinationCommunityList, are introduced to complete this task. defined in [RFC4360], large community defined in [RFC8092], and
bgpCommunity contains one BGP community value. community container defined in [I-D.ietf-idr-wide-bgp-communities].
BgpSourceCommunityList consists of a list of bgpCommunity Flow information, such as packetDeltaCount, octetDeltaCount [RFC7012]
corresponding with the source IP address of a specific flow, and etc, can then be accumulated and analysed by the collector or other
bgpDestinationCommunityList consists of a list of bgpCommunity applications based on BGP community.
corresponding with the destination IP address of a specific flow.
BgpCommunity, bgpSourceCommunityList and bgpDestinationCommunityList The IEs introduced in this document are applicable for both IPv4 and
IEs are applicable for both IPv4 and IPv6 traffic. Both exporter and IPv6 traffic. Both exporter and mediator can use these IEs to export
mediator can use these three IEs to export BGP community information BGP community information in IPFIX.
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. BGP Community Information Elements 3. IEs for BGP Standard Community
In order to export BGP community information along with other flow [RFC1997] defines the BGP Communities attribute, called BGP Standard
information defined by IPFIX, we need to introduce three new IEs. Community in this document, which describes a group of routes sharing
One is bgpCommunity, which is used to identify that the value in this some common properties. BGP Standard Communities are treated as 32
IE is BGP community [RFC1997]. The other two are bit values as stated in in [RFC1997].
bgpSourceCommunityList and bgpDestinationCommunityList. They both
are basicList [RFC6313] of bgpCommunity. bgpSourceCommunityList and
bgpDestinationCommunityList are used to export BGP community
information corresponding to a specific flow's source IP and
destination IP respectively. Flow information based on BGP community
can then be accumulated and analysed by the collector or other
applications.
The details of these three new introduced IEs are illustrated below, In order to export BGP standard community information along with
including name, ID, type, semantics, description and units. other flow information defined by IPFIX, three new IEs are
introduced. One is bgpCommunity, which is used to identify that the
value in this IE is a BGP standard community. The other two are
bgpSourceCommunityList and bgpDestinationCommunityList, which are
both basicList [RFC6313] of bgpCommunity, and are used to export BGP
standard community information corresponding to a specific flow's
source IP and destination IP respectively.
The detailed information of the three new IEs are shown in the
following sections.
3.1. bgpCommunity 3.1. bgpCommunity
---------------------------------------------------------------------- ----------------------------------------------------------------------
| ElementID | to be assigned by IANA, 458 is suggested | | ElementID | to be assigned by IANA |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Name | bgpCommunity | | Name | bgpCommunity |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| Data Type | unsigned32 | | Data Type | unsigned32 |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| Data Type Semantics | identifier | | Data Type Semantics | identifier |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Description | BGP community as defined in [RFC1997] | | Description | BGP community as defined in [RFC1997] |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Units | none | | Units | none |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
Figure 1: bgpCommunity Figure 1: bgpCommunity
3.2. bgpSourceCommunityList 3.2. bgpSourceCommunityList
---------------------------------------------------------------------- ----------------------------------------------------------------------
| ElementID | to be assigned by IANA, 459 is suggested | | ElementID | to be assigned by IANA |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Name | bgpSourceCommunityList | | Name | bgpSourceCommunityList |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| Data Type | basicList, as specified in [RFC6313] | | Data Type | basicList, as specified in [RFC6313] |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| Data Type Semantics | list | | Data Type Semantics | list |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Description | zero or more BGP communities corresponding | | Description | zero or more BGP communities corresponding |
| | with source IP address of a specific flow | | | with source IP address of a specific flow |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Units | none | | Units | none |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
Figure 2: bgpSourceCommunityList Figure 2: bgpSourceCommunityList
3.3. bgpDestinationCommunityList 3.3. bgpDestinationCommunityList
---------------------------------------------------------------------- ---------------------------------------------------------------------
| ElementID | to be assigned by IANA, 460 is suggested | | ElementID | to be assigned by IANA |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Name | bgpDestinationCommunityList | | Name | bgpDestinationCommunityList |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| Data Type | basicList, as specified in [RFC6313] | | Data Type | basicList, as specified in [RFC6313] |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| Data Type Semantics | list | | Data Type Semantics | list |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| Description | zero or more BGP communities corresponding | | Description | zero or more BGP communities corresponding |
| |with destination IP address of a specific flow| | |with destination IP address of a specific flow|
|--------------------------------------------------------------------|
| Units | none |
|--------------------------------------------------------------------|
Figure 3: bgpDestinationCommunityList
4. IEs for BGP Extended Community
[RFC4360] defines the BGP Extended Communities attribute, which
provides a mechanism for labeling information carried in BGP. Each
Extended Community is encoded as an 8-octet quantity with the format
defined in [RFC4360].
In order to export BGP Extended Community information together with
other flow information by IPFIX, three new IEs are introduced. 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
bgpSourceExtendedCommunityList and
bgpDestinationExtendedCommunityList, which are both basicList
[RFC6313] of bgpExtendedCommunity, and are used to export the BGP
Extended Community information corresponding to a specific flow's
source IP and destination IP respectively.
The detailed information of the three new IEs are shown in the
following sections.
4.1. bgpExtendedCommunity
----------------------------------------------------------------------
| ElementID | to be assigned by IANA |
|--------------------------------------------------------------------|
| Name | bgpExtendedCommunity |
|--------------------------------------------------------------------|
| Data Type | octetArray |
|--------------------------------------------------------------------|
| Data Type Semantics | default |
|--------------------------------------------------------------------|
| |BGP Extended Community as defined in [RFC4360]|
| Description |The size of this Information Element is 8 |
| |octets. |
|--------------------------------------------------------------------|
| Units | none |
|--------------------------------------------------------------------|
Figure 4: bgpExtendedCommunity
4.2. bgpSourceExtendedCommunityList
----------------------------------------------------------------------
| ElementID | to be assigned by IANA |
|--------------------------------------------------------------------|
| Name | bgpSourceExtendedCommunityList |
|--------------------------------------------------------------------|
| Data Type | basicList, as specified in [RFC6313] |
|--------------------------------------------------------------------|
| Data Type Semantics | list |
|--------------------------------------------------------------------|
| | zero or more BGP Extended Communities |
| Description | corresponding with source IP address |
| | of a specific flow |
|--------------------------------------------------------------------|
| Units | none |
|--------------------------------------------------------------------|
Figure 5: bgpSourceExtendedCommunityList
4.3. bgpDestinationExtendedCommunityList
----------------------------------------------------------------------
| ElementID | to be assigned by IANA |
|--------------------------------------------------------------------|
| Name | bgpDestinationExtendedCommunityList |
|--------------------------------------------------------------------|
| Data Type | basicList, as specified in [RFC6313] |
|--------------------------------------------------------------------|
| Data Type Semantics | list |
|--------------------------------------------------------------------|
| | zero or more BGP Extended communities |
| Description | corresponding with destination IP address |
| | of a specific flow |
|--------------------------------------------------------------------|
| Units | none |
|--------------------------------------------------------------------|
Figure 6: bgpDestinationExtendedCommunityList
5. IEs for BGP Large Community
[RFC8092] defines the BGP Large Communities attribute, which is
suitable for use with all Autonomous System Numbers (ASNs) including
four-octet ASNs. Each BGP Large Community is encoded as a 12-octet
quantity with the format defined in [RFC8092].
In order to export BGP Large Community information together with
other flow information by IPFIX, three new IEs are introduced. The
first one is bgpLargeCommunity, which is used to identify that the
value in this IE is a BGP Large Community. The other two are
bgpSourceLargeCommunityList and bgpDestinationLargeCommunityList,
which are both basicList [RFC6313] of bgpLargeCommunity, and are used
to export the BGP Large Community information corresponding to a
specific flow's source IP and destination IP respectively.
The detailed information of the three new IEs are shown in the
following sections.
5.1. bgpLargeCommunity
---------------------------------------------------------------------- ----------------------------------------------------------------------
| ElementID | to be assigned by IANA |
|--------------------------------------------------------------------|
| Name | bgpLargeCommunity |
|--------------------------------------------------------------------|
| Data Type | octetArray |
|--------------------------------------------------------------------|
| Data Type Semantics | default |
|--------------------------------------------------------------------|
| | BGP Large Community as defined in [RFC8092] |
| Description | The size of this Information Element is 12 |
| | octets. |
|--------------------------------------------------------------------|
| Units | none | | Units | none |
|--------------------------------------------------------------------- |---------------------------------------------------------------------
Figure 3: bgpDestinationCommunityList Figure 7: bgpLargeCommunity
4. Security Considerations 5.2. bgpSourceLargeCommunityList
----------------------------------------------------------------------
| ElementID | to be assigned by IANA |
|--------------------------------------------------------------------|
| Name | bgpSourceLargeCommunityList |
|--------------------------------------------------------------------|
| Data Type | basicList, as specified in [RFC6313] |
|--------------------------------------------------------------------|
| Data Type Semantics | list |
|--------------------------------------------------------------------|
| | zero or more BGP Large Communities |
| Description | corresponding with source IP address |
| | of a specific flow |
|--------------------------------------------------------------------|
| Units | none |
|--------------------------------------------------------------------|
Figure 8: bgpSourceLargeCommunityList
5.3. bgpDestinationLargeCommunityList
----------------------------------------------------------------------
| ElementID | to be assigned by IANA |
|--------------------------------------------------------------------|
| Name | bgpDestinationLargeCommunityList |
|--------------------------------------------------------------------|
| Data Type | basicList, as specified in [RFC6313] |
|--------------------------------------------------------------------|
| Data Type Semantics | list |
|--------------------------------------------------------------------|
| Description | zero or more BGP Large communities |
| | corresponding with destination IP address |
| | of a specific flow |
|--------------------------------------------------------------------|
| Units | none |
|--------------------------------------------------------------------|
Figure 9: bgpDestinationLargeCommunityList
6. IEs for BGP Community Container
TBD.
7. Message Length Considerations
The maximum length of one IPFIX message is 65535 bytes as per
[RFC7011] and 4096 bytes for one BGP message as per [RFC4271]. Since
BGP communities, including standard, extended, large and container,
are BGP path attributes distributed in update messages, the length of
them can not exceed the length of a BGP message, i.e. 4096. So one
IPFIX message with maximum length of 65535 has enough space to fit
all the communities related to a specific flow, both the source IP
and the destination IP related.
[I-D.ietf-idr-bgp-extended-messages], however, extends the maximum
update message size of BGP beyond 4096 bytes to 65535 bytes. BGP
speakers that support the extended message SHOULD take care to handle
the IPFIX message properly, such as only convey as many communities
as possible in the IPFIX message. The collector who receives an
IPFIX message with maximum length and BGP communities contained in
its data set SHOULD be aware of the BGP communities may be truncated
due to limited message space. In this case, it is RECOMMENDED to
configure export policy on the exporter to limit the BGP communities
to be exported, to export only some specific communities, for
example, or not to export some communities.
To solve this problem completely, a separate document will be
submitted to extend the message length of IPFIX [RFC7011] to 32 bits.
8. Security Considerations
This document only defines three new IEs for IPFIX. So, this This document only defines three new IEs for IPFIX. So, this
document itself does not directly introduce security issues. The document itself does not directly introduce security issues. The
same security considerations as for the IPFIX Protocol Specification same 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. are no increased privacy concerns, neither.
5. IANA Considerations 9. IANA Considerations
This draft specifies three new IPFIX IEs, bgpCommunity, This draft specifies the following IPFIX IEs to export BGP community
bgpSourceCommunityList and bgpDestinationCommunityList, to export BGP information along with other flow information.
community information along with other flow information.
The Element IDs for these three IEs are solicited to be assigned by The Element IDs for these IEs are solicited to be assigned by IANA.
IANA. The following table is for IANA's reference to put in each The following table is for IANA's reference to put in each field in
field in the registry. the registry.
---------------------------------------------------------------------- ----------------------------------------------------------------------
|ElementID| Name | Data Type|Data Type Semantics| |ElementID| Name | Data Type|Data Type Semantics|
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA1 | bgpCommunity |unsigned32| identifier | | TBA1 | bgpCommunity |unsigned32| identifier |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA2 | bgpSourceCommunityList | basicList| list | | TBA2 | bgpSourceCommunityList | basicList| list |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA3 |bgpDestinationCommunityList| basicList| list | | TBA3 |bgpDestinationCommunityList| basicList| list |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA4 | bgpExtendedCommunity |octetArray| default |
|--------------------------------------------------------------------|
| TBA5 | bgpSourceExtended | | |
| | CommunityList | basicList| list |
|--------------------------------------------------------------------|
| TBA6 | bgpDestinationExtended | | |
| | CommunityList | basicList| list |
|--------------------------------------------------------------------|
| TBA7 | bgpLargeCommunity |octetArray| default |
|--------------------------------------------------------------------|
| TBA8 |bgpSourceLargeCommunityList| basicList| list |
|--------------------------------------------------------------------|
| TBA9 | bgpDestinationLarge | | |
| | CommunityList | basicList| list |
|--------------------------------------------------------------------|
---------------------------------------------------------------------- ----------------------------------------------------------------------
|ElementID| Description | Units | |ElementID| Description | Units |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA1 | BGP community | | | TBA1 | BGP community as defined in [RFC1997] | |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA2 | zero or more BGP communities corresponding | | | TBA2 | zero or more BGP communities corresponding | |
| | with source IP address of a specific flow | | | | with source IP address of a specific flow | |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA3 | zero or more BGP communities corresponding | | | TBA3 | zero or more BGP communities corresponding | |
| |with destination IP address of a specific flow| | | |with destination IP address of a specific flow| |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA4 |BGP Extended Community as defined in [RFC4360]| |
| |The size of this IE is 8 octets | |
|--------------------------------------------------------------------|
| | zero or more BGP Extended Communities | |
| TBA5 | corresponding with source IP address of | |
| | a specific flow | |
|--------------------------------------------------------------------|
| | zero or more BGP Extended communities | |
| TBA6 | corresponding with destination IP address | |
| | of a specific flow | |
|--------------------------------------------------------------------|
| TBA7 | BGP Large Community as defined in [RFC8092] | |
| | The size of this IE is 12 octets. | |
|--------------------------------------------------------------------|
| | zero or more BGP Large Communities | |
| TBA8 | corresponding with source IP address | |
| | of a specific flow | |
|--------------------------------------------------------------------|
| | zero or more BGP Large communities | |
| TBA9 | corresponding with destination IP address | |
| | of a specific flow | |
|--------------------------------------------------------------------|
---------------------------------------------------------------------- ----------------------------------------------------------------------
|ElementID| Range | References | Requester | Revision | date | |ElementID| Range | References | Requester | Revision | date |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA1 | | RFC1997 |this draft | 0 | | | TBA1 | | RFC1997 |this draft | 0 | |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA2 | |RFC6313,RFC1997|this draft | 0 | | | TBA2 | |RFC6313,RFC1997|this draft | 0 | |
|--------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA3 | |RFC6313,RFC1997|this draft | 0 | | | TBA3 | |RFC6313,RFC1997|this draft | 0 | |
---------------------------------------------------------------------- |--------------------------------------------------------------------|
| TBA4 | | RFC4360 |this draft | 0 | |
|--------------------------------------------------------------------|
| TBA5 | |RFC6313,RFC4360|this draft | 0 | |
|--------------------------------------------------------------------|
| TBA6 | |RFC6313,RFC4360|this draft | 0 | |
|--------------------------------------------------------------------|
| TBA7 | | RFC8092 |this draft | 0 | |
|--------------------------------------------------------------------|
| TBA8 | |RFC6313,RFC8092|this draft | 0 | |
|--------------------------------------------------------------------|
| TBA9 | |RFC6313,RFC8092|this draft | 0 | |
|--------------------------------------------------------------------|
Figure 4 Figure 10: IANA Considerations
6. Acknowledgements 10. 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, Jeffrey Haas, Ignas
Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared Mauch, Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared Mauch,
etc, for their discussion in the mail list. etc, for their discussion in the mail list.
7. References 11. References
7.1. Normative References 11.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>. <http://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>. <http://www.rfc-editor.org/info/rfc6313>.
skipping to change at page 7, line 38 skipping to change at page 13, line 21
"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>. <http://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>. <http://www.rfc-editor.org/info/rfc7012>.
7.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]
Bush, R., Patel, K., and D. Ward, "Extended Message
support for BGP", draft-ietf-idr-bgp-extended-messages-21
(work in progress), March 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>. <http://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,
<http://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, <http://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>. <http://www.rfc-editor.org/info/rfc4384>.
[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>. <http://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>. <http://www.rfc-editor.org/info/rfc6183>.
[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,
<http://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| |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 | | 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 | | 3.3.3.3 | 4.4.4.4 |3:1001,3:1002,8:1001| 4:1001,8:1001 |
-------------------------------------------------------------------------- --------------------------------------------------------------------------
Figure 5: 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| SourceIPv4Address = 8 | Field length = 4 | |0| SourceIPv4Address = 8 | Field length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| DestinationIPv4Address = 12 | Field length = 4 | |0| DestinationIPv4Address = 12 | Field length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| bgpSourceCommunityList = 459| Field length = 0xFFFF | |0| bgpSourceCommunityList = 459| Field length = 0xFFFF |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| bgpDestinationCommunityList | Field length = 0xFFFF | |0| bgpDestinationCommunityList | Field length = 0xFFFF |
| | = 460 | | | | = 460 | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Template Record Encoding Format Figure 12: Template Record Encoding Format
In this example, the Template ID is 256, which will be used in the In this example, the Template ID is 256, which will be used in the
data record. The field length for bgpSourceCommunityList and data record. The field length for bgpSourceCommunityList and
bgpDestinationCommunityList is 0xFFFF, which means the length of this bgpDestinationCommunityList is 0xFFFF, which means the length of this
IE is variable, the actual length of this IE is indicated by the list IE is variable, the actual length of this IE is indicated by the list
length field in the basic list format as per [RFC6313]. length field in the basic list format as per [RFC6313].
A.2. Data Set A.2. Data Set
The data set is represented as follows: The data set is represented as follows:
skipping to change at page 10, line 35 skipping to change at page 16, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 255 | List length = 13 |semantic =allof| | 255 | List length = 13 |semantic =allof|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| bgpCommunity = 458 | Field Len = 4 | | bgpCommunity = 458 | Field Len = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 1 = 4:1001 | | BGP Destination Community Value 1 = 4:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Destination Community Value 2 = 8:1001 | | BGP Destination Community Value 2 = 8:1001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Data Set Encoding Format Figure 13: Data Set Encoding Format
Authors' Addresses Authors' Addresses
Zhenqiang Li (editor) Zhenqiang Li
China Mobile China Mobile
32 Xuanwumen West Ave, Xicheng District 32 Xuanwumen West Ave, Xicheng District
Beijing 100053 Beijing 100053
China China
Email: lizhenqiang@chinamobile.com Email: li_zhenqiang@hotmail.com
Rong Gu (editor) Rong Gu
China Mobile China Mobile
32 Xuanwumen West Ave, Xicheng District 32 Xuanwumen West Ave, Xicheng District
Beijing 100053 Beijing 100053
China China
Email: gurong_cmcc@outlook.com Email: gurong_cmcc@outlook.com
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
 End of changes. 62 change blocks. 
109 lines changed or deleted 375 lines changed or added

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