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

Document Type Active Internet-Draft (idr WG)
Last updated 2017-01-11 (latest revision 2017-01-05)
Replaces draft-heitz-idr-large-community
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews GENART will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd John Scudder
Shepherd write-up Show (last changed 2016-11-22)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "John Scudder" <jgs@juniper.net>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
IDR                                                        J. Heitz, Ed.
Internet-Draft                                                     Cisco
Intended status: Standards Track                        J. Snijders, Ed.
Expires: July 9, 2017                                                NTT
                                                                K. Patel
                                                                  Arrcus
                                                             I. Bagdonas
                                                                 Equinix
                                                             N. Hilliard
                                                                    INEX
                                                         January 5, 2017

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

Abstract

   This document describes the BGP Large Communities attribute, an
   extension to BGP-4.  This attribute provides a mechanism to signal
   opaque information within separate namespaces to aid in routing
   management.  The attribute is suitable for use with all Autonomous
   System Numbers including four-octet Autonomous System Numbers.

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 July 9, 2017.

Heitz, et al.             Expires July 9, 2017                  [Page 1]
Internet-Draft            BGP Large Communities             January 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  BGP Large Communities Attribute . . . . . . . . . . . . . . .   3
   3.  Aggregation . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Canonical Representation  . . . . . . . . . . . . . . . . . .   4
   5.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
     11.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   BGP [RFC4271] implementations typically support a routing policy
   language to control the distribution of routing information.  Network
   operators attach BGP communities to routes to associate particular
   properties with these routes.  These properties may include
   information such as the route origin location, or specification of a
   routing policy action to be taken, or one that has been taken, and is
   applied to all routes contained in a BGP Update Message where the
   Communities Attribute is included.  Because BGP communities are
Show full document text