Content deleted Content added
Rescuing 3 sources and tagging 2 as dead. #IABot (v1.6.5) |
m clean up ref newlines, spacing, zero-width |
||
Line 10:
PCE represents a vision of networks that separates route computations from the signaling of end-to-end connections and from actual [[packet forwarding]]. There is a basic tutorial on PCE as presented at ISOCORE's MPLS2008 conference<ref name=tutorial>Basic PCE tutorial [http://www.olddog.co.uk/Farrel_PCE_Tutorial.pdf "PCE Tutorial"]</ref> and a tutorial on advanced PCE as presented at ISOCORE's SDN/MPLS 2014 conference.<ref name=AdvTutorial>Advanced PCE tutorial [http://www.olddog.co.uk/AdvancedPCE.pdf "Advanced PCE Tutorial"]</ref>
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>RFC 7399 [http://www.rfc-editor.org/rfc/rfc7399.txt "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 [[Transmission Control Protocol]] (TCP).
Line 22:
* Interdomain PCE discovering extensions<ref>{{cite web
}}{{dead link|date=March 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</ref><ref>{{cite web
}}</ref><ref>{{cite web
}}{{dead link|date=March 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>
|