Extended Experimental Path Attributes for BGP
draft-haas-idr-extended-experimental-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-01
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)
Network Working Group                                            J. Haas
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                           March 1, 2017
Expires: September 2, 2017

             Extended Experimental Path Attributes for BGP
                draft-haas-idr-extended-experimental-01

Abstract

   BGP's primary feature extension mechanism, Optional-Transitive Path
   Attributes, has proven to be a successful mechanism to permit BGP to
   be extended.  In order to ease various issues during the development
   of new BGP features, this document proposes an extended experimental
   Path Attribute to carry prototype features.

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 September 2, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Haas                    Expires September 2, 2017               [Page 1]
Internet-DraftExtended Experimental Path Attributes for BGP   March 2017

   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.  Extended Experimental Path Attribute  . . . . . . . . . . . .   3
   3.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Moving to an Allocated Code Point . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Comparisons to Other Features  . . . . . . . . . . .   6
   Appendix B.  Discussion to this Date  . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   BGP's [RFC4271] primary feature extension mechanism, Optional-
   Transitive Path Attributes, has proven to be a successful mechanism
   to permit BGP to be extended.  It permits implementations to
   propagate unknown Path Attributes without understanding their
   contents, so long as they are syntactically valid.

   Path Attributes are encoded in BGP UPDATE messages using a single
   octet code-point.  While this code-point space is relatively small,
   the rate at which new BGP features are introduced has proven to be
   slow enough that the potential for exhaustion has not been a
   significant concern more than twenty years into the deployment of
   BGP-4.  This code point space is managed by IANA under the Standards
   Action policy [RFC5226], one of the more restrictive policies in
   IETF's repertoire.  Early allocation [RFC7120] provides some latitude
   for allocation of these code points compared to the original RFC 5226
   policy, but is reserved for features that are considered
   appropriately stable.

   Development work on the BGP protocol often requires a code point be
Show full document text