Generic Subtype for BGP Four-octet AS specific extended community
draft-ietf-idr-as4octet-extcomm-generic-subtype-10

Document Type Active Internet-Draft (idr WG)
Last updated 2016-12-02
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Dead 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)
Network Working Group                                             D. Rao
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                            P. Mohapatra
Expires: June 4, 2017                                   Sproute Networks
                                                                 J. Haas
                                                  Juniper Networks, Inc.
                                                        December 1, 2016

   Generic Subtype for BGP Four-octet AS specific extended community
           draft-ietf-idr-as4octet-extcomm-generic-subtype-10

Abstract

   Maintaining the current best practices with communities, ISPs and
   enterprises that are assigned a 4-octet AS number may want the BGP
   UPDATE messages they receive from their customers or peers to include
   a 4-octet AS specific BGP extended community.  This document defines
   a new sub-type within the four-octet AS specific extended community
   to facilitate this practice.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in [RFC2119] only when they appear in all
   upper case.  They may also appear in lower or mixed case as English
   words, without normative meaning.

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 June 4, 2017.

Rao, et al.               Expires June 4, 2017                  [Page 1]
Internet-Draft       4octet extcomm generic sub-type       December 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.  Generic Sub-type Definition . . . . . . . . . . . . . . . . .   3
   3.  Deployment Considerations . . . . . . . . . . . . . . . . . .   4
   4.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Document History . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Maintaining the current best practices with communities, ISPs and
   enterprises that are assigned a 4-octet AS number may want the BGP
   UPDATE messages they receive from their customers or peers to include
   a 4-octet AS specific extended community.  This document defines a
   new sub-type within the four-octet AS specific extended community to
   facilitate this practice.

   For example, [RFC1998] describes an application of BGP community
   attribute ([RFC1997]) to implement flexible routing policies for
   sites multi-homed to one or multiple providers.  In a two-octet AS
   environment, the advertised routes are usually associated with a
   community attribute that encodes the provider's AS number in the
   first two octets of the community and a LOCAL_PREF value in the
   second two octets of the community.  The community attribute signals
   the provider edge routers connected to the site to set the
Show full document text