Wide BGP Communities Attribute
draft-ietf-idr-wide-bgp-communities-00

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2015-08-04 (latest revision 2015-06-25)
Replaces draft-raszuk-wide-bgp-communities
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
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                                             Mirantis Inc.
Intended status: Standards Track                            J. Haas, Ed.
Expires: December 27, 2015                              Juniper Networks
                                                           A. Lange, Ed.
                                                          Alcatel-Lucent
                                                               S. Amante
                                                             Apple, Inc.
                                                             B. Decraene
                                                                  Orange
                                                                P. Jakma
                                                         Uni. of Glasgow
                                                          R. Steenbergen
                                             nLayer Communications, Inc.
                                                           June 25, 2015

                     Wide BGP Communities Attribute
                 draft-ietf-idr-wide-bgp-communities-00

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

   Such information is important to allow BGP speakers to perform some
   mutually agreed actions without the need to maintain a separate
   offline database for each tuple of prefix and associated set of
   action entries.

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

Raszuk, et al.          Expires December 27, 2015               [Page 1]
Internet-Draft            wide-bgp-communities                 June 2015

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 December 27, 2015.

Copyright Notice

   Copyright (c) 2015 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
     1.1.  Protocol Summary  . . . . . . . . . . . . . . . . . . . .   4
   2.  Wide Community Atoms  . . . . . . . . . . . . . . . . . . . .   5
     2.1.  The Autonomous System number list atom  . . . . . . . . .   6
     2.2.  The IPv4 and IPv6 prefix list atoms . . . . . . . . . . .   6
     2.3.  The Integer list atom . . . . . . . . . . . . . . . . . .   6
     2.4.  The IEEE Floating Point Number list atom  . . . . . . . .   7
     2.5.  The Neighbor Class list atom  . . . . . . . . . . . . . .   7
     2.6.  The User-defined Class list atom  . . . . . . . . . . . .   7
     2.7.  The UTF-8 String atom . . . . . . . . . . . . . . . . . .   8
   3.  Wide BGP Community Attribute  . . . . . . . . . . . . . . . .   8
     3.1.  Wide BGP Community Attribute Container Header . . . . . .   8
   4.  Container Type 1: Wide Community  . . . . . . . . . . . . . .  10
Show full document text