Hi, Since the constraints information is vendor specific, so the VENDOR-CONSTRAINT object can't be used in one domain which consists of different vendor's equipments. On the other side, if there are two domains, which consists of same vendor's equipments, the VENDOR-CONSTRAINT object should not be limited in only one domain. It can be exchanged between two PCEs where each PCE covers one domain.
Regards, Dan ----- Original Message ----- From: "Meral Shirazipour" <[EMAIL PROTECTED]> To: "Adrian Farrel" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Tuesday, April 08, 2008 6:02 AM Subject: Re: [Pce] Fw: I-D Action:draft-farrel-pce-vendor-constraints-00.txt Hi, In Section 5.6 raises an obvious issue : "the presence of additional vendor-specific information in PCEP messages may congest the operation of the protocol especially if the PCE does not support the constraints supplied by the PCC." Would it be safer to propose that the proposed feature should only be used for inter-area and inter-layer path computations (and not for inter-domain)?! I don't really see the prospect of using vendor specific constraints in an inter-domain environment... Regards, Meral Selon Adrian Farrel <[EMAIL PROTECTED]>: > 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 > _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
