Export BGP community information in IP Flow Information Export (IPFIX)
draft-ietf-opsawg-ipfix-bgp-community-11

Document Type Active Internet-Draft (opsawg WG)
Last updated 2018-12-06 (latest revision 2018-11-25)
Replaces draft-li-opsawg-ipfix-bgp-community
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews SECDIR, OPSDIR will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Tianran Zhou
Shepherd write-up Show (last changed 2018-08-13)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Ignas Bagdonas
Send notices to Tianran Zhou <zhoutianran@huawei.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state None
opsawg                                                             Z. Li
Internet-Draft                                                     R. Gu
Intended status: Standards Track                            China Mobile
Expires: May 29, 2019                                            J. Dong
                                                     Huawei Technologies
                                                       November 25, 2018

 Export BGP community information in IP Flow Information Export (IPFIX)
                draft-ietf-opsawg-ipfix-bgp-community-11

Abstract

   By introducing new Information Elements (IEs), this draft extends the
   existing BGP-related IEs to enable IPFIX [RFC7011] to export BGP
   community information, including BGP standard communities [RFC1997],
   BGP extended communities [RFC4360], and BGP large communities
   [RFC8092].  Network traffic information can then be accumulated and
   analyzed at the BGP community granularity, which represents the
   traffic of different kinds of customers, services, or geographical
   regions according to the network operator's BGP community planning.
   Network traffic information at the BGP community granularity is
   useful for network traffic analysis and engineering.

   To clarify, no new BGP community attribute is defined in this
   document and this document does not replace BGP Monitoring Protocol
   (BMP) defined in RFC7854.  The IEs introduced in this document are
   used by IPFIX, together with other IEs, to facilitate the IPFIX
   Collector analyzing network traffic at the BGP community granularity
   without needing to run the heavy BGP itself.  When needed, the IPFIX
   Mediator or Collector can use the IEs introduced in this document to
   report the BGP community-related traffic flow information it gets
   either from Exporters or through local correlation to other IPFIX
   devices.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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

Li, et al.                Expires May 29, 2019                  [Page 1]
Internet-Draft        Export BGP Community in IPFIX        November 2018

   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 May 29, 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  BGP Community-based Traffic Collection  . . . . . . . . . . .   5
   4.  IEs for BGP Standard Community  . . . . . . . . . . . . . . .   7
   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 . . . . . . . . . . . . . . . . . . . . .  14
     A.2.  Data Set  . . . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

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
Show full document text