draft-ietf-opsawg-ipfix-bgp-community-00.txt   draft-ietf-opsawg-ipfix-bgp-community-01.txt 
opsawg Z. Li, Ed. opsawg Z. Li, Ed.
Internet-Draft R. Gu, Ed. Internet-Draft R. Gu, Ed.
Intended status: Standards Track China Mobile Intended status: Standards Track China Mobile
Expires: September 1, 2017 J. Dong Expires: September 8, 2017 J. Dong
Huawei Technologies Huawei Technologies
February 28, 2017 March 7, 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-00 draft-ietf-opsawg-ipfix-bgp-community-01
Abstract Abstract
This draft specifies an extension to the IPFIX information model This draft specifies an extension to the IPFIX information model
defined in [RFC7012] to export the BGP community [RFC1997] defined in [RFC7012] to export the BGP community [RFC1997]
information. Three information elements, bgpCommunity, information. Three information elements, bgpCommunity,
bgpSourceCommunityList and bgpDestinationCommunityList, are bgpSourceCommunityList and bgpDestinationCommunityList, are
introduced in this document to carry the BGP community information. introduced in this document to carry the BGP community information.
bgpCommunity, containing exactly one BGP community value, is used to bgpCommunity, containing exactly one BGP community value, is used to
consist the list in bgpSourceCommunityList and consist the list in bgpSourceCommunityList and
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 1, 2017. This Internet-Draft will expire on September 8, 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
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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. BGP Community Information Elements . . . . . . . . . . . . . 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. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Application Example . . . . . . . . . . . . . . . . 7 Appendix A. Application Example . . . . . . . . . . . . . . . . 8
A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 7 A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 8
A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 8 A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
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 5, line 4 skipping to change at page 5, line 4
| 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, 459 is suggested |
---------------------------------------------------------------------- ----------------------------------------------------------------------
| 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, 460 is suggested |
---------------------------------------------------------------------- ----------------------------------------------------------------------
| 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 | | Units | none |
|--------------------------------------------------------------------- |---------------------------------------------------------------------
Figure 3: bgpDestinationCommunityList Figure 3: bgpDestinationCommunityList
4. Security Considerations 4. 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
are no increased privacy concerns.
5. IANA Considerations 5. IANA Considerations
This draft specifies three new IPFIX IEs, bgpCommunity, This draft specifies three new IPFIX IEs, bgpCommunity,
bgpSourceCommunityList and bgpDestinationCommunityList, to export BGP bgpSourceCommunityList and bgpDestinationCommunityList, to export BGP
community 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 three IEs are solicited to be assigned by
IANA. Number 458, 459 and 460 are suggested for bgpCommunity, IANA. The following table is for IANA's reference to put in each
bgpSourceCommunityList and bgpDestinationCommunityList, respectively. field in the registry.
----------------------------------------------------------------------
|ElementID| Name | Data Type|Data Type Semantics|
----------------------------------------------------------------------
| TBA1 | bgpCommunity |unsigned32| identifier |
|---------------------------------------------------------------------
| TBA2 | bgpSourceCommunityList | basicList| list |
|---------------------------------------------------------------------
| TBA3 |bgpDestinationCommunityList| basicList| list |
----------------------------------------------------------------------
----------------------------------------------------------------------
|ElementID| Description | Units |
----------------------------------------------------------------------
| TBA1 | BGP community | |
|---------------------------------------------------------------------
| TBA2 | zero or more BGP communities corresponding | |
| | with source IP address of a specific flow | |
|---------------------------------------------------------------------
| TBA3 | zero or more BGP communities corresponding | |
| |with destination IP address of a specific flow| |
----------------------------------------------------------------------
----------------------------------------------------------------------
|ElementID| Range | References | Requester | Revision | date |
----------------------------------------------------------------------
| TBA1 | | RFC1997 |this draft | 0 | |
|---------------------------------------------------------------------
| TBA2 | |RFC6313,RFC1997|this draft | 0 | |
|---------------------------------------------------------------------
| TBA3 | |RFC6313,RFC1997|this draft | 0 | |
----------------------------------------------------------------------
Figure 4
6. Acknowledgements 6. 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
discussion and suggestions to promote this document. their comments and suggestions to promote this document.
Appreciations are given to Tianran Zhou, Jeffrey Haas, Ignas
Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared Mauch,
etc, for their discussion in the mail list.
7. References 7. References
7.1. Normative References 7.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>.
skipping to change at page 7, line 39 skipping to change at page 8, line 35
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 4: Flow information including BGP communities Figure 5: 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 5: Template Record Encoding Format Figure 6: 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 9, line 35 skipping to change at page 10, 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 6: Data Set Encoding Format Figure 7: Data Set Encoding Format
Authors' Addresses Authors' Addresses
Zhenqiang Li (editor) Zhenqiang Li (editor)
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: lizhenqiang@chinamobile.com
 End of changes. 13 change blocks. 
47 lines changed or deleted 87 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/