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.

[1]  Thomas Narten,et al.  Guidelines for Writing an IANA Considerations Section in RFCs , 1998, RFC.

[2]  Jean-Louis Le Roux,et al.  Path Computation Element (PCE) Communication Protocol (PCEP) , 2009, RFC.

[3]  Adrian Farrel,et al.  Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts , 2011, RFC.

[4]  Adrian Farrel,et al.  Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol , 2014, RFC.

[5]  Adrian Farrel,et al.  A Path Computation Element (PCE)-Based Architecture , 2006, RFC.

[6]  David Harrington Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions , 2009, RFC.

[7]  Jean-Louis Le Roux,et al.  Network Working Group Encoding of Objective Functions in the Path Computation Element Communication Protocol (pcep) , 2009 .

[8]  Daniel King,et al.  Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module , 2014, RFC.

[9]  Adrian Farrel,et al.  Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications , 2009, RFC.

[10]  Keyur Patel,et al.  Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide , 2013, RFC.

[11]  Jean-Louis Le Roux,et al.  OSPF Protocol Extensions for Path Computation Element (PCE) Discovery , 2008, RFC.

[12]  Scott O. Bradner,et al.  Key words for use in RFCs to Indicate Requirement Levels , 1997, RFC.

[13]  Tomonori Takeda,et al.  Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths , 2010, RFC.

[14]  Keith McCloghrie,et al.  Structure of Management Information Version 2 (SMIv2) , 1999, RFC.

[15]  Jean-Louis Le Roux,et al.  Path Computation Element (PCE) Communication Protocol Generic Requirements , 2006, RFC.

[16]  Dhruv Dhody,et al.  Management Information Base (MIB) for the PCE Communications Protocol (PCEP) for Path-Key based Confidentiality in Inter-Domain Path Computation. , 2014 .

[17]  Jean-Louis Le Roux,et al.  IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery , 2008, RFC.