Large BGP Communities
draft-ietf-idr-large-community-00

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2016-09-23
Replaces draft-heitz-idr-large-community
Stream IETF
Intended RFC status (None)
Formats plain text pdf html 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                                                             J. Heitz
Internet-Draft                                                     Cisco
Intended status: Standards Track                                K. Patel
Expires: March 27, 2017                                           Arrcus
                                                             J. Snijders
                                                                     NTT
                                                             I. Bagdonas
                                                                 Equinix
                                                              A. Simpson
                                                                   Nokia
                                                      September 23, 2016

                         Large BGP Communities
                   draft-ietf-idr-large-community-00

Abstract

   The BGP Communities Attribute [RFC1997] is heavily used by operators,
   but is inadequate to represent large enough values, particularly
   Four-octet Autonomous System numbers [RFC6793] plus additional
   values.  This document describes an extension to BGP [RFC4271] to
   address this need with a new extended form of the BGP community
   Attribute.

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 [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
   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 March 27, 2017.

Heitz, et al.            Expires March 27, 2017                 [Page 1]
Internet-Draft            Large BGP Communities           September 2016

Copyright Notice

   Copyright (c) 2016 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Large BGP Community Attribute . . . . . . . . . . . . . . . .   3
   3.  Textual Representation  . . . . . . . . . . . . . . . . . . .   4
   4.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
     9.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   BGP implementations typically support a routing policy language (RPL)
   to control the distribution of routing information.  Network
   operators add BGP communities to routes via the RPL to identify
   intrinsic differentia of a route such as its origin country or
   specify a RPL action to be taken, or one that has been taken, on an
   individual route or group of routes.  Because BGP communities are
   optional transitive BGP attributes, these differentia and actions
   identified by the communities may be acted upon or otherwise utilized
   by the RPL in any Autonomous System (AS) in the Internet, often are
   and often the goal of adding a community is to signal an AS one or
   more AS-hops away.

   BGP Communities Attributes are 4-octet values split into two 2-octet
   values where the most significant word is an Autonomous System number
   (ASN) and the least significant word is a value whose meaning is

Heitz, et al.            Expires March 27, 2017                 [Page 2]
Show full document text