<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-rfc7150bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-rfc7150bis-00">
   <front>
      <title>Conveying Vendor-Specific Constraints in the Path Computation Element communication Protocol</title>
      <author initials="F." surname="Zhang" fullname="Fatai Zhang">
         </author>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         </author>
      <date month="July" day="22" year="2014" />
      <abstract>
	 <t>   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-Variable that
   can be carried in any existing PCEP object.

   This document obsoletes RFC 7150.  The only change from that document
   is the allocation of a different code point for the
   VENDOR-INFORMATION object.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-rfc7150bis-00" />
   
</reference>
