IANA Registries for BGP Extended Communities
draft-ietf-idr-extcomm-iana-01

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2013-11-29 (latest revision 2013-09-30)
Replaces draft-rosen-idr-extcomm-iana
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2013-09-27)
IESG IESG state Waiting for Writeup::Revised I-D Needed
Telechat date
Responsible AD Stewart Bryant
Send notices to idr-chairs@tools.ietf.org, draft-ietf-idr-extcomm-iana@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
IDR Working Group                                          Eric C. Rosen
Internet Draft                                       Cisco Systems, Inc.
Intended Status: Standards Track
Updates: 4360,5701                                         Yakov Rekhter
Expires: March 30, 2014                           Juniper Networks, Inc.

                                                      September 30, 2013

              IANA Registries for BGP Extended Communities

                   draft-ietf-idr-extcomm-iana-01.txt

Abstract

   This document reorganizes the IANA Registries for the type values and
   sub-type values of BGP Extended Communities attribute and the BGP
   IPv6-Address-Specific Extended Communities attribute.  This is done
   in order to remove inter-dependencies among the registries, thus
   making it easier for IANA to determine which codepoints are available
   for assignment in which registries.  This document also clarifies the
   information that must be provided to IANA when requesting an
   allocation from one or more of these registries.  These changes are
   compatible with the existing allocations, and thus do not affect
   protocol implementations.  The changes will however impact the "IANA
   Considerations" sections of future protocol specifications.  This
   document updates RFCs 4360 and 5701.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

Rosen & Rekhter                                                 [Page 1]



Internet Draft     draft-ietf-idr-extcomm-iana-01.txt     September 2013

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Copyright and License Notice

   Copyright (c) 2013 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.

Rosen & Rekhter                                                 [Page 2]



Internet Draft     draft-ietf-idr-extcomm-iana-01.txt     September 2013

Table of Contents

 1          Introduction  ..........................................   4
 2          Types, Sub-Types, and Registries  ......................   4
 3          Applicability to IPv6 Address Specific EC Attribute  ...   5
 4          How to Request EC Type and/or Sub-Type Codepoints  .....   5
 5          IANA Considerations  ...................................   7
 5.1        Registries for the TYPE Field  .........................   7
 5.1.1      Transitive Types  ......................................   7
 5.1.2      Non-Transitive Types  ..................................   9
 5.2        Registries for the Sub-Type Field  .....................  10
 5.2.1      EVPN Sub-Types  ........................................  10
 5.2.2      Transitive Two-Octet AS-Specific Sub-Types  ............  10
 5.2.3      Non-Transitive Two-Octet AS-Specific Sub-Types  ........  11
 5.2.4      Transitive Four-Octet AS-Specific Sub-Types  ...........  12
 5.2.5      Non-Transitive Four-Octet AS-Specific Sub-Types  .......  12
 5.2.6      Transitive IPv4-Address-Specific Sub-Types  ............  13
 5.2.7      Non-Transitive IPv4-Address-Specific Sub-Types  ........  13
 5.2.8      Transitive Opaque Extended Community Sub-Types  ........  14
 5.2.9      Non-Transitive Opaque Extended Community Sub-Types  ....  14
 5.2.10     Generic Transitive Experimental Use Sub-Types  .........  15
 5.2.11     Registries for the Value Field  ........................  15
 5.2.11.1   Traffic Action Field  ..................................  15
 5.3        Registries for IPv6-Address-Specific ECs  ..............  15
 5.3.1      Transitive Types  ......................................  15
Show full document text