Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Deprecation of BGP Entropy Label Capability Attribute (RFC7447)

IP.com Disclosure Number: IPCOM000240478D
Original Publication Date: 2015-Feb-01
Included in the Prior Art Database: 2015-Feb-04
Document File: 8 page(s) / 8K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Scudder: AUTHOR [+2]

Abstract

[RFC6790] defines the Entropy Label Capability attribute (ELCA), an optional, transitive BGP path attribute. For correct operation, an intermediate node modifying the next hop of a route must remove the ELCA unless the node doing so is able to process entropy labels. Sadly, this requirement cannot be fulfilled with the ELCA as specified, because it is an optional, transitive attribute. By definition, a node that does not support the ELCA will propagate the attribute (this is a general property of optional, transitive attributes; see [RFC4271]). But such an ELCA-oblivious node is likely to be incapable of processing entropy labels and is exactly the node that we desire to remove the attribute!

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 36% of the total text.

Internet Engineering Task Force (IETF)                        J. Scudder Request for Comments: 7447                                   K. Kompella Updates: 6790                                           Juniper Networks Category: Standards Track                                  February 2015 ISSN: 2070-1721

          Deprecation of BGP Entropy Label Capability Attribute

Abstract

   The BGP Entropy Label Capability attribute is defined in RFC 6790.    Regrettably, it has a bug: although RFC 6790 mandates that routers    incapable of processing Entropy Labels must remove the attribute,    fulfillment of this requirement cannot be guaranteed in practice.    This specification deprecates the attribute.  A forthcoming document    will propose a replacement.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7447.

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.

Scudder & Kompella           Standards Track                    [Page 1]
 RFC 7447                   Deprecation of ELCA             February 2015

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2      1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2    2.  Deprecation of ELCA . . . . . . . . . . . . . . . . . . . . .   2    3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3    4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3    5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3      5.1.  Normative References ...