BGP Next-Hop Capabilities
draft-decraene-idr-next-hop-capability-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-03-09
Replaced by draft-ietf-idr-next-hop-capability
Stream (None)
Intended RFC status (None)
Formats plain text 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                                        B. Decraene
Internet-Draft                                                    Orange
Intended status: Standards Track                           March 9, 2015
Expires: September 10, 2015

                       BGP Next-Hop Capabilities
               draft-decraene-idr-next-hop-capability-00

Abstract

   RFC 5492 defines capabilities advertisement for the BGP peer.  In
   addition, it's useful to know the capabilities of the BGP Next-Hop,
   in particular for forwarding plane features.  RFC 5492 is not
   applicable because the BGP peer may be different from the BGP Next-
   Hop, in particular when BGP Route Reflection is used.  This document
   defines a mechanism to advertise such BGP Next Hop Capabilities.

   This document defines a new BGP non-transitive attribute to carry
   Next-Hop Capabilities.  This attribute is deleted when the BGP Next
   Hop is changed.

   This document also defines a Next-Hop capability to advertise the
   ability to handle the Entropy Label defined in RFC 6790.

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 RFC 2119 [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 September 10, 2015.

Decraene               Expires September 10, 2015               [Page 1]
Internet-Draft          BGP Next-Hop Capabilities             March 2015

Copyright Notice

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

1.  Introduction

   [RFC5492] defines capabilities advertisement for the BGP peer.  It's
   also useful to know the capabilities of the BGP Next-Hop, in
   particular for forwarding plane features.  RFC 5492 is not applicable
   because the BGP peer may be different from the BGP Next-Hop, in
   particular when BGP Route Reflection is used.  This document defines
   a mechanism to advertise such BGP Next Hop Capabilities.

   This document defines a new BGP non-transitive attribute to carry
   Next-Hop Capabilities.  This attribute is deleted when the BGP Next
   Hop is changed.

   This document also defines a first application to advertise the
   capability to handle the Entropy Label defined in [RFC6790].  Note
   that RFC 6790 had originally defined a BGP attribute for this but it
   has been latter deprecated in [RFC7447]

2.  BGP Next-Hop Capability Attribute

   The BGP Next-Hop Capabilities Attribute is an optional, non-
   transitive BGP Attribute, of value TBD1.  The attribute consists of a
   set of Next-Hop Capabilities.  Inclusion of a Next-Hop Capability "X"
   indicates that the BGP Next-Hop, encoded in either the NEXT_HOP
   attribute defined in [RFC4271] or the Network Address of Next Hop
   field of the MP_REACH_NLRI attribute defined in [RFC4760], supports
   the capability "X".  This document do not make distinction between
   these two Next-Hop fields and refer to them as BGP Next-Hop.

   A Next-Hop Capability is triple (Capability Code, Capability Length,
   Capability Value) aka a TLV:

Decraene               Expires September 10, 2015               [Page 2]
Internet-Draft          BGP Next-Hop Capabilities             March 2015

                           A Next-Hop Capability.

             +------------------------------+
             | Capability Code (1 octet)    |
             +------------------------------+
             | Capability Length (1 octet)  |
             +------------------------------+
             | Capability Value (variable)  |
             ~                              ~
             +------------------------------+

   Capability Code : a one-octet unsigned binary integer which indicates
Show full document text