BGP Extra Extended Community
draft-heitz-idr-extra-extended-community-01

Document Type Active Internet-Draft (individual)
Last updated 2018-07-17
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IDR                                                             J. Heitz
Internet-Draft                                                A. Sajassi
Updates: 4684 (if approved)                                        Cisco
Intended status: Standards Track                             I. Bagdonas
Expires: January 18, 2019                                        Equinix
                                                           July 17, 2018

                      BGP Extra Extended Community
              draft-heitz-idr-extra-extended-community-01

Abstract

   Auto-derived identifiers are used by applications to enable zero
   configuration features.  Such identifiers are often a combination of
   primitive identifiers and are thus longer.  In addition, existing
   identifiers have grown longer.  IP addresses have grown from 4 octets
   to 16.  AS numbers have grown from 2 octets to 4.  In order to
   accommodate such longer identifiers in BGP extended communities, this
   document defines a new BGP path attribute, the Extra Extended
   Communities attribute.  It is similar to the Extended Community, but
   is 24 octets long.  Communities are mostly used within ASes under a
   single administration or between neighboring ASes.  Limiting the
   spread of communities beyond their intended reach and polluting the
   internet at large is complex and error prone.  To simplify this,
   enhanced transitivity options are provided.

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 https://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."

Heitz, et al.           Expires January 18, 2019                [Page 1]
Internet-Draft        BGP Extra Extended Community             July 2018

   This Internet-Draft will expire on January 18, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.  BGP Extra Extended Community Attribute  . . . . . . . . . . .   3
   3.  Transitivity  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Capability  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Constrained Route Distribution  . . . . . . . . . . . . . . .   5
   6.  IPv6-Address-Specific Extra Extended Community type . . . . .   7
   7.  IPv4-Address-Specific Extra Extended Community type . . . . .   7
   8.  AS-Specific Extra Extended Community type . . . . . . . . . .   8
   9.  Route Target Extra Extended Community Sub-Type  . . . . . . .   9
   10. EVPN Extra Extended Community type  . . . . . . . . . . . . .  10
   11. EVPN Route Target Extra Extended Community sub-types  . . . .  10
   12. EVPN ES-Import Route Target Extra Extended Community sub-type  11
   13. EVPN ESI-EVI Route Target Extra Extended Community sub-type .  11
   14. EVPN Overlay Route Target Extra Extended Community sub-type .  12
   15. Duplicate XXC . . . . . . . . . . . . . . . . . . . . . . . .  14
   16. Error Handling  . . . . . . . . . . . . . . . . . . . . . . .  14
   17. Security Considerations . . . . . . . . . . . . . . . . . . .  15
   18. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
     18.1.  Registry: BGP Extra Extended Community Types . . . . . .  15
     18.2.  Registry: IPv6-Address-Specific Extra Extended Community
            Sub-Types  . . . . . . . . . . . . . . . . . . . . . . .  15
     18.3.  Registry: IPv4-Address-Specific Extra Extended Community
            Sub-Types  . . . . . . . . . . . . . . . . . . . . . . .  16
     18.4.  Registry: AS-Specific Extra Extended Community Sub-Types  16
Show full document text