Usage of Large BGP Communities
draft-snijders-grow-large-communities-usage-00

Document Type Active Internet-Draft (grow WG)
Last updated 2016-12-07 (latest revision 2016-10-30)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
GROW                                                         J. Snijders
Internet-Draft                                                       NTT
Intended status: Informational                                M. Schmidt
Expires: May 3, 2017                                             i3D.net
                                                        October 30, 2016

                     Usage of Large BGP Communities
             draft-snijders-grow-large-communities-usage-00

Abstract

   Examples and inspiration for operators on how to use Large BGP
   Communities.

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 May 3, 2017.

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

Snijders & Schmidt         Expires May 3, 2017                  [Page 1]
Internet-Draft       Usage of Large BGP Communities         October 2016

   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.  The Generic Design Pattern  . . . . . . . . . . . . . . . . .   3
     2.1.  Informational Communities . . . . . . . . . . . . . . . .   3
     2.2.  Action Communities  . . . . . . . . . . . . . . . . . . .   4
   3.  Examples of Informational Communities . . . . . . . . . . . .   4
     3.1.  Location  . . . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  An ISO 3166-1 numeric function  . . . . . . . . . . .   4
       3.1.2.  An UNSD region function . . . . . . . . . . . . . . .   5
     3.2.  Relation  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Combining Informational Communities . . . . . . . . . . .   6
   4.  Examples of Action Communities  . . . . . . . . . . . . . . .   6
     4.1.  Selective NO_EXPORT . . . . . . . . . . . . . . . . . . .   6
       4.1.1.  Peer ASN Based Selective NO_EXPORT  . . . . . . . . .   6
       4.1.2.  Location Based Selective NO_EXPORT  . . . . . . . . .   7
     4.2.  Selective AS_PATH Prepending  . . . . . . . . . . . . . .   7
       4.2.1.  Peer ASN Based Selective AS_PATH Prepending . . . . .   7
       4.2.2.  Location Based Selective AS_PATH Prepending . . . . .   8
     4.3.  Region-Specific LOCAL_PREFERENCE  . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Large BGP Communities [I-D.ietf-idr-large-community] provide a
   mechanism to signal opaque information between Autonomous Systems.
   This document presents a set of examples on how Large BGP Communities
   could be implemented by an operator to achieve various goals.  This
   document draws from experience in Operational Communities such as
   NANOG [1] and NLNOG [2].

   The opaque nature of Large BGP Communities allows for rapid
   deployment of new features or changes to the product.  Operators are
Show full document text