BGP Next-Hop dependant capabilities
draft-decraene-idr-next-hop-capability-03

Document Type Active Internet-Draft (individual)
Last updated 2017-01-26
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                                        B. Decraene
Internet-Draft                                                    Orange
Updates: 6790 (if approved)                                  K. Kompella
Intended status: Standards Track                  Juniper Networks, Inc.
Expires: July 30, 2017                                     W. Henderickx
                                                                   Nokia
                                                        January 26, 2017

                  BGP Next-Hop dependant capabilities
               draft-decraene-idr-next-hop-capability-03

Abstract

   RFC 5492 defines capabilities advertisement for the BGP peer.  In
   addition, it is useful to be able to advertise BGP Next-Hop dependant
   capabilities, 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 dependant
   Capabilities.

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

   This document also defines a Next-Hop capability to advertise the
   ability to handle the MPLS Entropy Label defined in RFC 6790.  It
   updates RFC 6790 with regard to this BGP signaling.

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

Decraene, et al.          Expires July 30, 2017                 [Page 1]
Internet-Draft          BGP Next-Hop Capabilities           January 2017

   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 July 30, 2017.

Copyright Notice

   Copyright (c) 2017 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.  BGP Next-Hop dependant Capabilities Attribute . . . . . . . .   3
     2.1.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Attribute Operation . . . . . . . . . . . . . . . . . . .   4
     2.3.  Capability Code Operation . . . . . . . . . . . . . . . .   5
     2.4.  Attribute Error Handling  . . . . . . . . . . . . . . . .   5
   3.  Entropy Label Next-Hop dependant Capability . . . . . . . . .   6
     3.1.  Entropy Label Next-Hop Capability error handling  . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Next-Hop Capabilities Attribute . . . . . . . . . . . . .   7
     4.2.  Next-Hop Capability registry  . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   [RFC5492] defines capabilities advertisement for the BGP peer.  In
   addition, it is useful to be able to advertise BGP Next-Hop dependant
   capabilities, in particular for forwarding plane features.  RFC 5492
Show full document text