Well-Known Community Policy Behavior
draft-ietf-grow-wkc-behavior-08

Document Type Active Internet-Draft (grow WG)
Last updated 2019-06-18 (latest revision 2019-06-13)
Replaces draft-ymbk-grow-wkc-behavior
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Job Snijders
Shepherd write-up Show (last changed 2019-04-17)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Job Snijders <job@ntt.net>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Network Working Group                                     J. Borkenhagen
Internet-Draft                                                      AT&T
Updates: 1997 (if approved)                                      R. Bush
Intended status: Standards Track                            IIJ & Arrcus
Expires: December 15, 2019                                     R. Bonica
                                                        Juniper Networks
                                                            S. Bayraktar
                                                           Cisco Systems
                                                           June 13, 2019

                  Well-Known Community Policy Behavior
                    draft-ietf-grow-wkc-behavior-08

Abstract

   Well-Known BGP Communities are manipulated differently across various
   current implementations; resulting in difficulties for operators.
   Network operators should deploy consistent community handling across
   their networks while taking the inconsistent behaviors from the
   various BGP implementations into consideration..  This document
   recommends specific actions to limit future inconsistency, namely BGP
   implementors must not create further inconsistencies from this point
   forward.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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

Borkenhagen, et al.     Expires December 15, 2019               [Page 1]
Internet-Draft    Well-Known Community Policy Behavior         June 2019

   This Internet-Draft will expire on December 15, 2019.

Copyright Notice

   Copyright (c) 2019 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Manipulation of Communities by Policy . . . . . . . . . . . .   3
   3.  Community Manipulation Policy Differences . . . . . . . . . .   3
   4.  Documentation of Vendor Implementations . . . . . . . . . . .   3
     4.1.  Note on an Inconsistency  . . . . . . . . . . . . . . . .   4
   5.  Note for Those Writing RFCs for New Community-Like Attributes   5
   6.  Action Items  . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The BGP Communities Attribute was specified in [RFC1997] which
   introduced the concept of Well-Known Communities.  In hindsight,
   [RFC1997] did not prescribe as fully as it should have how Well-Known
   Communities may be manipulated by policies applied by operators.
   Currently, implementations differ in this regard, and these
   differences can result in inconsistent behaviors that operators find
   difficult to identify and resolve.

   This document describes the current behavioral differences in order
   to assist operators in generating consistent community-manipulation
   policies in a multi-vendor environment, and to prevent the
   introduction of additional divergence in implementations.

Borkenhagen, et al.     Expires December 15, 2019               [Page 2]
Internet-Draft    Well-Known Community Policy Behavior         June 2019

   This document recommends specific actions to limit future
Show full document text