Browse Prior Art Database

Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol (RFC7470) Disclosure Number: IPCOM000240798D
Original Publication Date: 2015-Mar-01
Included in the Prior Art Database: 2015-Mar-04
Document File: 28 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Zhang: AUTHOR [+2]


A Path Computation Element (PCE) is an entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints. An architecture for the use of PCEs is defined in [RFC4655].

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

Internet Engineering Task Force (IETF)                          F. Zhang Request for Comments: 7470                                        Huawei Obsoletes: 7150                                                A. Farrel Category: Standards Track                               Juniper Networks ISSN: 2070-1721                                               March 2015

                  Conveying Vendor-Specific Constraints          in the Path Computation Element Communication Protocol


   The Path Computation Element Communication Protocol (PCEP) is used to    convey path computation requests and responses both between Path    Computation Clients (PCCs) and Path Computation Elements (PCEs) and    between cooperating PCEs.  In PCEP, the path computation requests    carry details of the constraints and objective functions that the PCC    wishes the PCE to apply in its computation.

   This document defines a facility to carry vendor-specific information    in PCEP using a dedicated object and a new Type-Length-Value (TLV)    that can be carried in any PCEP object that supports TLVs.

   This document obsoletes RFC 7150.  The only changes from that    document are a clarification of the use of the new Type-Length-Value    and the allocation of a different code point for the VENDOR-    INFORMATION object.

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

 Zhang & Farrel               Standards Track                    [Page 1]
 RFC 7470           Vendor-Specific Constraints in PCE         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    ( 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  ...