--- 1/draft-ietf-opsawg-ipfix-bgp-community-00.txt 2017-03-10 04:13:23.139813531 -0800 +++ 2/draft-ietf-opsawg-ipfix-bgp-community-01.txt 2017-03-10 04:13:23.171814285 -0800 @@ -1,20 +1,20 @@ opsawg Z. Li, Ed. Internet-Draft R. Gu, Ed. Intended status: Standards Track China Mobile -Expires: September 1, 2017 J. Dong +Expires: September 8, 2017 J. Dong Huawei Technologies - February 28, 2017 + March 7, 2017 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 This draft specifies an extension to the IPFIX information model defined in [RFC7012] to export the BGP community [RFC1997] information. Three information elements, bgpCommunity, bgpSourceCommunityList and bgpDestinationCommunityList, are introduced in this document to carry the BGP community information. bgpCommunity, containing exactly one BGP community value, is used to consist the list in bgpSourceCommunityList and @@ -29,21 +29,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -55,29 +55,29 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. BGP Community Information Elements . . . . . . . . . . . . . 4 3.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 4 3.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 4 3.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 - 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 - 7.2. Informative References . . . . . . . . . . . . . . . . . 6 - Appendix A. Application Example . . . . . . . . . . . . . . . . 7 - A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 7 - A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 8 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 + 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 + 7.2. Informative References . . . . . . . . . . . . . . . . . 7 + Appendix A. Application Example . . . . . . . . . . . . . . . . 8 + A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 8 + A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 9 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 1. Introduction IP Flow Information Export (IPFIX) [RFC7011] provides network administrators with traffic flow information using the information elements (IEs) defined in [IANA-IPFIX] registries. Based on the traffic flow information, network administrators know the amount and direction of the traffic in their network, then they can optimize their network when needed. For example, they can steer some flows from the congested links to the low utilized links. @@ -211,34 +211,74 @@ Figure 3: bgpDestinationCommunityList 4. Security Considerations This document only defines three new IEs for IPFIX. So, this document itself does not directly introduce security issues. The same security considerations as for the IPFIX Protocol Specification [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 This draft specifies three new IPFIX IEs, bgpCommunity, bgpSourceCommunityList and bgpDestinationCommunityList, to export BGP community information along with other flow information. The Element IDs for these three IEs are solicited to be assigned by - IANA. Number 458, 459 and 460 are suggested for bgpCommunity, - bgpSourceCommunityList and bgpDestinationCommunityList, respectively. + IANA. The following table is for IANA's reference to put in each + 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 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.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . @@ -297,41 +337,41 @@ 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 | -------------------------------------------------------------------------- | 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 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SET ID = 2 | Length = 24 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Template ID = 256 | Field Count = 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| SourceIPv4Address = 8 | Field length = 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| DestinationIPv4Address = 12 | Field length = 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| bgpSourceCommunityList = 459| Field length = 0xFFFF | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0| bgpDestinationCommunityList | Field length = 0xFFFF | | | = 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 data record. The field length for bgpSourceCommunityList and bgpDestinationCommunityList is 0xFFFF, which means the length of this IE is variable, the actual length of this IE is indicated by the list length field in the basic list format as per [RFC6313]. A.2. Data Set The data set is represented as follows: @@ -379,21 +419,21 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 255 | List length = 13 |semantic =allof| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | bgpCommunity = 458 | Field Len = 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BGP Destination Community Value 1 = 4:1001 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BGP Destination Community Value 2 = 8:1001 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Figure 6: Data Set Encoding Format + Figure 7: Data Set Encoding Format Authors' Addresses Zhenqiang Li (editor) China Mobile 32 Xuanwumen West Ave, Xicheng District Beijing 100053 China Email: lizhenqiang@chinamobile.com