Sivabalan et al 2020a - Revision history

Scipediacontent at 18:26, 5 March 2021

2021-03-05T18:26:38Z

Scipediacontent: Scipediacontent moved page Draft Content 642362363 to Sivabalan et al 2020a

2021-02-11T13:39:25Z

Scipediacontent moved page Draft Content 642362363 to Sivabalan et al 2020a

Scipediacontent: Created page with " == Abstract == Stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Pa..."

2021-02-11T13:39:22Z

Created page with " == Abstract == Stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Pa..."

New page

== Abstract ==

Stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs). When a PCE has stateful control over LSPs it may send indications to LSP head-ends to modify the attributes (especially the paths) of the LSPs. A Path Computation Client (PCC) that has set up LSPs under local configuration may delegate control of those LSPs to a stateful PCE. There are use-cases in which a stateful PCE may wish to obtain control of locally configured LSPs of which it is aware but that have not been delegated to the PCE. This document describes an extension to the Path Computation Element communication Protocol (PCEP) to enable a PCE to make requests for such control.

== Original document ==

The different versions of the original document can be found in:

* [http://dx.doi.org/10.17487/rfc8741 http://dx.doi.org/10.17487/rfc8741]

* [https://tools.ietf.org/html/rfc8741 https://tools.ietf.org/html/rfc8741],
: [https://www.rfc-editor.org/info/rfc8741 https://www.rfc-editor.org/info/rfc8741],
: [https://www.rfc-editor.org/rfc/rfc8741.txt https://www.rfc-editor.org/rfc/rfc8741.txt],
: [https://trac.tools.ietf.org/html/rfc8741 https://trac.tools.ietf.org/html/rfc8741],
: [https://www.levkowetz.com/html/rfc8741 https://www.levkowetz.com/html/rfc8741],
: [https://rfcs.web.fc2.com/draft-ietf-pce-lsp-control-request-06.html https://rfcs.web.fc2.com/draft-ietf-pce-lsp-control-request-06.html],
: [https://academic.microsoft.com/#/detail/2955367405 https://academic.microsoft.com/#/detail/2955367405]

@@ Line 2: / Line 2: @@
 == Abstract ==
- Stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs). When a PCE has stateful control over LSPs it may send indications to LSP head-ends to modify the attributes (especially the paths) of the LSPs. A Path Computation Client (PCC) that has set up LSPs under local configuration may delegate control of those LSPs to a stateful PCE. There are use-cases in which a stateful PCE may wish to obtain control of locally configured LSPs of which it is aware but that have not been delegated to the PCE. This document describes an extension to the Path Computation Element communication Protocol (PCEP) to enable a PCE to make requests for such control.
+Stateful Path Computation Element (PCE) retains information about the placement of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs). When a PCE has stateful control over LSPs it may send indications to LSP head-ends to modify the attributes (especially the paths) of the LSPs. A Path Computation Client (PCC) that has set up LSPs under local configuration may delegate control of those LSPs to a stateful PCE. There are use-cases in which a stateful PCE may wish to obtain control of locally configured LSPs of which it is aware but that have not been delegated to the PCE. This document describes an extension to the Path Computation Element communication Protocol (PCEP) to enable a PCE to make requests for such control.
-−
 == Original document ==

← Older revision	Revision as of 13:39, 11 February 2021
(No difference)