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

Document Type Active Internet-Draft (opsawg WG)
Last updated 2017-03-10
Replaces draft-li-opsawg-ipfix-bgp-community
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
On Agenda opsawg at IETF-98
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
opsawg                                                        Z. Li, Ed.
Internet-Draft                                                R. Gu, Ed.
Intended status: Standards Track                            China Mobile
Expires: September 8, 2017                                       J. Dong
                                                     Huawei Technologies
                                                           March 7, 2017

 Export BGP community information in IP Flow Information Export (IPFIX)
                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
   bgpDestinationCommunityList, which are corresponding to a specific
   flow's source IP and destination IP respectively.

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 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 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

Li, et al.              Expires September 8, 2017               [Page 1]
Internet-Draft        Export BGP Community in IPFIX           March 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   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 . . . . . . . . . . . . . . . . . . . . .   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.

   [IANA-IPFIX] has already defined the following IEs for traffic flow
   information exporting in different grain: sourceIPv4Address,
   sourceIPv4Prefix, destinationIPv4Address, destinationIPv4Prefix,
   bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address,
   etc.  In some circumstances, however, especially when traffic
   engineering and optimization are used in the Tier 1 or Tier 2
   operators' backbone networks, traffic flow information based on these
Show full document text