draft-ietf-pce-stateful-hpce-03.txt   draft-ietf-pce-stateful-hpce-04.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
Ericsson Ericsson
J. Shin J. Shin
SK Telecom SK Telecom
D. King D. King
Lancaster University Lancaster University
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica I+D Telefonica I+D
March 5, 2018 March 5, 2018
Hierarchical Stateful Path Computation Element (PCE). Hierarchical Stateful Path Computation Element (PCE).
draft-ietf-pce-stateful-hpce-03 draft-ietf-pce-stateful-hpce-04
Abstract Abstract
A Stateful Path Computation Element (PCE) maintains information on A Stateful Path Computation Element (PCE) maintains information on
the current network state, including: computed Label Switched Path the current network state, including: computed Label Switched Path
(LSPs), reserved resources within the network, and pending path (LSPs), reserved resources within the network, and pending path
computation requests. This information may then be considered when computation requests. This information may then be considered when
computing new traffic engineered LSPs, and for associated computing new traffic engineered LSPs, and for associated
and dependent LSPs, received from Path Computation Clients (PCCs). and dependent LSPs, received from Path Computation Clients (PCCs).
skipping to change at page 6, line 13 skipping to change at page 6, line 13
this C-PCE passes the path on to the PCC that issued the original this C-PCE passes the path on to the PCC that issued the original
request. request.
As per [RFC8231], PCC sends an LSP State Report carried on a PCRpt As per [RFC8231], PCC sends an LSP State Report carried on a PCRpt
message to the C-PCE, indicating the LSP's status. The C-PCE MAY message to the C-PCE, indicating the LSP's status. The C-PCE MAY
further propagate the State Report to the P-PCE. A local policy at further propagate the State Report to the P-PCE. A local policy at
C-PCE MAY dictate which LSPs to be reported to the P-PCE. The PCRpt C-PCE MAY dictate which LSPs to be reported to the P-PCE. The PCRpt
message is sent from C-PCE to P-PCE. message is sent from C-PCE to P-PCE.
State synchronization mechanism as described in [RFC8231] and State synchronization mechanism as described in [RFC8231] and
[RFC8233] are applicable to PCEP session between C-PCE and P-PCE as [RFC8232] are applicable to PCEP session between C-PCE and P-PCE as
well. well.
Taking the sample hierarchical domain topology example from [RFC6805] Taking the sample hierarchical domain topology example from [RFC6805]
as the reference topology for the entirety of this document. as the reference topology for the entirety of this document.
----------------------------------------------------------------- -----------------------------------------------------------------
| Domain 5 | | Domain 5 |
| ----- | | ----- |
| |PCE 5| | | |PCE 5| |
| ----- | | ----- |
skipping to change at page 17, line 5 skipping to change at page 17, line 5
[RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP
Authentication Option", RFC 5925, DOI 10.17487/RFC5925, Authentication Option", RFC 5925, DOI 10.17487/RFC5925,
June 2010, <http://www.rfc-editor.org/info/rfc5925>. June 2010, <http://www.rfc-editor.org/info/rfc5925>.
[RFC8051] Zhang, X., Ed. and I. Minei, Ed., "Applicability of a [RFC8051] Zhang, X., Ed. and I. Minei, Ed., "Applicability of a
Stateful Path Computation Element (PCE)", RFC 8051, Stateful Path Computation Element (PCE)", RFC 8051,
DOI 10.17487/RFC8051, January 2017, DOI 10.17487/RFC8051, January 2017,
<http://www.rfc-editor.org/info/rfc8051>. <http://www.rfc-editor.org/info/rfc8051>.
[RFC8233] Dhody, D., Wu, Q., Manral, V., Ali, Z., and K. Kumaki, [RFC8232] Crabbe, E., Minei, I., Medved, J., Varga, R., Zhang, X.,
"Extensions to the Path Computation Element Communication and D. Dhody, "Optimizations of Label Switched Path State
Protocol (PCEP) to Compute Service-Aware Label Switched Synchronization Procedures for a Stateful PCE", RFC 8232,
Paths (LSPs)", RFC 8233, DOI 10.17487/RFC8233, September DOI 10.17487/RFC8232, September 2017,
2017, <https://www.rfc-editor.org/info/rfc8233>. <https://www.rfc-editor.org/info/rfc8232>.
[RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody, [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody,
"PCEPS: Usage of TLS to Provide a Secure Transport for the "PCEPS: Usage of TLS to Provide a Secure Transport for the
Path Computation Element Communication Protocol (PCEP)", Path Computation Element Communication Protocol (PCEP)",
RFC 8253, DOI 10.17487/RFC8253, October 2017, RFC 8253, DOI 10.17487/RFC8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[I-D.ietf-teas-actn-framework] [I-D.ietf-teas-actn-framework]
Ceccarelli D. and Y. Lee, "Framework for Abstraction and Ceccarelli D. and Y. Lee, "Framework for Abstraction and
Control of Transport Networks", draft-ietf-teas- Control of Transport Networks", draft-ietf-teas-
 End of changes. 3 change blocks. 
7 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/