Hi all, We just submitted a new revision of this draft to address some comments in the list by introducing VENDOR-CONSTRAINT TLV.
The authors think that this draft is ready for WG LC. Thanks Fatai -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: 2011年12月2日 11:44 To: Zhangfatai Cc: [email protected]; Zhangfatai; [email protected] Subject: New Version Notification for draft-ietf-pce-vendor-constraints-05.txt A new version of I-D, draft-ietf-pce-vendor-constraints-05.txt has been successfully submitted by Fatai Zhang and posted to the IETF repository. Filename: draft-ietf-pce-vendor-constraints Revision: 05 Title: Conveying Vendor-Specific Constraints in the Path Computation Element Protocol Creation date: 2011-12-02 WG ID: pce Number of pages: 13 Abstract: The Path Computation Element Protocol (PCEP) is used to convey path computation requests and responses between Path Computation Clients (PCCs) and Path Computation Elements (PCEs), and also 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. The mechanisms defined for indicating objective functions include the capability to convey vendor-specific objective functions. This document defines a facility to carry vendor-specific constraints in PCEP. The IETF Secretariat _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
