Hi, This I-D is intended to allow PCE implementations to support specific additional constraints information that is not intoned for standardisation but which might be published for wider use or that is kept private for PCC-PCE communications.
As usual, comments to the list, please. Thanks, Adrian ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 07, 2008 5:45 PM Subject: I-D Action:draft-farrel-pce-vendor-constraints-00.txt >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > > Title : Conveying Vendor-Specific Constraints in the Path > Computation Element Protocol > Author(s) : A. Farrel, G. Bernstein > Filename : draft-farrel-pce-vendor-constraints-00.txt > Pages : 8 > Date : 2008-04-07 > > 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. _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
