--- 1/draft-ietf-opsawg-ipfix-bgp-community-09.txt 2018-10-19 06:13:07.727222524 -0700 +++ 2/draft-ietf-opsawg-ipfix-bgp-community-10.txt 2018-10-19 06:13:07.763223382 -0700 @@ -1,20 +1,20 @@ opsawg Z. Li Internet-Draft R. Gu Intended status: Standards Track China Mobile -Expires: March 29, 2019 J. Dong +Expires: April 22, 2019 J. Dong Huawei Technologies - September 25, 2018 + October 19, 2018 Export BGP community information in IP Flow Information Export (IPFIX) - draft-ietf-opsawg-ipfix-bgp-community-09 + draft-ietf-opsawg-ipfix-bgp-community-10 Abstract By introducing new Information Elements (IEs), this draft extends the existing BGP related IEs to enable IPFIX [RFC7011] to export the BGP community information, including the information of BGP standard community [RFC1997], BGP extended community [RFC4360], and BGP large community [RFC8092]. Network traffic information can then be accumulated and analysed at the BGP community granularity, which represents the traffic of different kinds of customers, services, or @@ -41,21 +41,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 https://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 March 29, 2019. + This Internet-Draft will expire on April 22, 2019. Copyright Notice Copyright (c) 2018 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -74,21 +74,21 @@ 5. IEs for BGP Extended Community . . . . . . . . . . . . . . . 7 6. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 7 7. Operational Considerations . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 11.1. Normative References . . . . . . . . . . . . . . . . . . 11 11.2. Informative References . . . . . . . . . . . . . . . . . 12 Appendix A. Encoding Example . . . . . . . . . . . . . . . . . . 13 - A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 13 + A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 14 A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 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 @@ -433,49 +433,54 @@ |--------------------------------------------------------------------| | TBA9 | bgpDestinationLarge | | | | | CommunityList | basicList| list | |--------------------------------------------------------------------| ---------------------------------------------------------------------- |ElementID| Description | Units | |--------------------------------------------------------------------| | TBA1 | BGP community as defined in [RFC1997] | | |--------------------------------------------------------------------| - | TBA2 | zero or more BGP communities corresponding | | + | | basicList of zero or more bgpCommunity IEs, | | + | TBA2 | containing the BGP communities corresponding| | | | with source IP address of a specific flow | | |--------------------------------------------------------------------| - | TBA3 | zero or more BGP communities corresponding | | + | | basicList of zero or more bgpCommunity IEs, | | + | TBA3 |containing the BGP communities corresponding | | | |with destination IP address of a specific flow| | |--------------------------------------------------------------------| | TBA4 |BGP Extended Community as defined in [RFC4360]| | | |The size of this IE MUST be 8 octets | | |--------------------------------------------------------------------| - | | zero or more BGP Extended Communities | | - | TBA5 | corresponding with source IP address of | | + | |basicList of zero or more bgpExtendedCommunity| | + | TBA5 |IEs, containing the BGP Extended Communities | | + | |corresponding with source IP address of | | | | a specific flow | | |--------------------------------------------------------------------| - | | zero or more BGP Extended communities | | - | TBA6 | corresponding with destination IP address | | + | |basicList of zero or more bgpExtendedCommunity| | + | TBA6 |IEs, containing the BGP Extended Communities | | + | | corresponding with destination IP address | | | | of a specific flow | | |--------------------------------------------------------------------| | TBA7 | BGP Large Community as defined in [RFC8092] | | | | The size of this IE MUST be 12 octets. | | |--------------------------------------------------------------------| - | | zero or more BGP Large Communities | | + | | basicList of zero or more bgpLargeCommunity | | + | | IEs, containing the BGP Large Communities | | | TBA8 | corresponding with source IP address | | | | of a specific flow | | |--------------------------------------------------------------------| - | | zero or more BGP Large communities | | + | | basicList of zero or more bgpLargeCommunity | | + | | IEs, containing the BGP Large Communities | | | TBA9 | 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 | | |--------------------------------------------------------------------| | TBA4 | | RFC4360 |this draft | 0 | |