BGP Community Container Attribute
draft-ietf-idr-wide-bgp-communities-04

Document Type Active Internet-Draft (idr WG)
Last updated 2017-03-02
Replaces draft-raszuk-wide-bgp-communities
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document Apr 2016
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IDR Working Group                                         R. Raszuk, Ed.
Internet-Draft                                              Bloomberg LP
Intended status: Standards Track                            J. Haas, Ed.
Expires: September 3, 2017                              Juniper Networks
                                                           A. Lange, Ed.
                                                                   Nokia
                                                        B. Decraene, Ed.
                                                                  Orange
                                                               S. Amante
                                                             Apple, Inc.
                                                                P. Jakma
                                              Hewlett Packard Enterprise
                                                           March 2, 2017

                   BGP Community Container Attribute
                 draft-ietf-idr-wide-bgp-communities-04

Abstract

   Route tagging plays an important role in external BGP [RFC4271]
   relations, in communicating various routing policies between peers.
   It is also a very common best practice among operators to propagate
   various additional information about routes intra-domain.  The most
   common tool used today to attach various information about routes is
   through the use of BGP communities [RFC1997].

   This document defines a new encoding which will enhance and simplify
   what can be accomplished today with the use of BGP communities.  The
   most important addition this specification makes over currently
   defined BGP communities is the ability to specify, carry as well as
   use for execution an operator's defined set of parameters.  It also
   provides an extensible platform for any new community encoding needs
   in the future.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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

Raszuk, et al.          Expires September 3, 2017               [Page 1]
Internet-Draft           BGP Community Container              March 2017

   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 3, 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Summary  . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  BGP Community Container Common Header . . . . . . . . . .   4
     2.2.  Community Containers  . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Type 1: BGP Wide Community  . . . . . . . . . . . . .   5
     2.3.  BGP Community Container Atoms . . . . . . . . . . . . . .   5
   3.  BGP Community Container Attribute . . . . . . . . . . . . . .   5
     3.1.  BGP Community Container Attribute Common Header . . . . .   6
   4.  BGP Community Container, Type 1: BGP Wide Community . . . . .   7
     4.1.  Community Value . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Source AS Number  . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Context AS Number . . . . . . . . . . . . . . . . . . . .   8
     4.4.  BGP Wide Community TLVs . . . . . . . . . . . . . . . . .   8
       4.4.1.  Sub-Type 1, BGP Wide Community Target(s) TLV  . . . .   9
Show full document text