Hello, Nice to see some bandwidth being used.
"PCE Architecture" -- an architecture that includes a PCE. "PCE" -- something that performs path computation. "PCC" -- something that requests path computation. In the Abstract... This document specifies the architecture for a Path Computation Element (PCE)-based model. Is it really necessary to then state... "We will term this architecture the PCE Architecture" ? I believe that at no other point in the architecture document is there a reference to "PCE" that means "PCE architecture" except it says explicitly "PCE architecture". I would be happy for you to point out places where this is a problem. In other documents (such as draft-ietf-pce-comm-protocol-gen-reqs-02.txt) appear to make exactly the same distinction. Thus, there is no use of the term "PCE" to mean an architecture. It is always used to mean a network element. There is no need to (re-)introduce the term "PCS" because it is isomorphic to "PCE" as currently defined. Thanks, Adrian ----- Original Message ----- From: "Lou Berger" <[EMAIL PROTECTED]> To: "Gray, Eric" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, October 15, 2005 3:57 PM Subject: RE: [Pce] WG Last Call ended on draft-ietf-pce-architecture-02.txt > > At 06:06 PM 10/14/2005, Gray, Eric wrote: > >Lou, > > > > What would be the point? Then it is merely a traffic > >engineer application. > > > >-- > >Eric > > Eric, > The PCE Architecture doesn't limit PCE to multi-domain > networks. to quote: > "... Path computation in large, multi-domain, multi-region or > multi-layer networks is complex and may require special > computational components and cooperation between the different > network domains." > > Lou > > > _______________________________________________ > Pce mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/pce > > _______________________________________________ Pce mailing list [email protected] https://www1.ietf.org/mailman/listinfo/pce
