Content deleted Content added
Add some detail about architecture and protocol. Point to the PACE project. |
m Fix x-ref to TCP |
||
Line 12:
Since the early days, the PCE architecture has evolved considerably to encompass more sophisticated concepts and allow application to more complicated network scenarios. This evolution includes Hierarchical PCE (H-PCE)<ref name=H-PCE>RFC 6805 [http://www.rfc-editor.org/rfc/rfc6805.txt] "Hierarchical PCE"</ref> and both Stateful and Active PCE.<ref name=Stateful>draft-ietf-pce-questions[http://datatracker.ietf.org/doc/draft-ietf-pce-questions/] "Unanswered Questions in the Path Computation Element Architecture"</ref>
A potential deployment of PCE separates the computation element from the client (the PCC) that request computation services. communications between the PCE and PCC are achieved using the Path Computation Element Communication Protocol (PCEP)<ref name=PCEP>RFC 5440 [http://www.rfc-editor.org/rfc/rfc5440.txt] "Path Computation Element Communications Protocol"</ref> which runs over the [[
As the architecture has evolved, new protocol extensions have been developed to add functionality to support new applications and the new architectural elements. These developments are tracked by the PACE project<ref name=PACE>PACE [http://www.ict-pace.net/] "PACE: Next Steps in PAth Computation Element (PCE) Architectures"</ref> which is funded by the [[European Union]]'s Seventh Framework Programme for research, technological development and demonstration under grant agreement no. 619712.
| |||