< draft-ietf-pce-state-sync-01.txt   draft-ietf-pce-state-sync-02.txt >
PCE Working Group S. Litkowski PCE Working Group S. Litkowski
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track S. Sivabalan Intended status: Standards Track S. Sivabalan
Expires: 23 April 2022 Ciena Corporation Expires: 23 October 2022 Ciena Corporation
C. Li C. Li
H. Zheng H. Zheng
Huawei Technologies Huawei Technologies
20 October 2021 21 April 2022
Inter Stateful Path Computation Element (PCE) Communication Procedures. Inter Stateful Path Computation Element (PCE) Communication Procedures.
draft-ietf-pce-state-sync-01 draft-ietf-pce-state-sync-02
Abstract Abstract
The Path Computation Element Communication Protocol (PCEP) provides The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path mechanisms for Path Computation Elements (PCEs) to perform path
computation in response to a Path Computation Client (PCC) request. computation in response to a Path Computation Client (PCC) request.
The Stateful PCE extensions allow stateful control of Multi-Protocol The Stateful PCE extensions allow stateful control of Multi-Protocol
Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
(LSPs) using PCEP. (LSPs) using PCEP.
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 23 April 2022. This Internet-Draft will expire on 23 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction and Problem Statement . . . . . . . . . . . . . 3 1. Introduction and Problem Statement . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.2. Reporting LSP Changes . . . . . . . . . . . . . . . . . . 4 1.2. Reporting LSP Changes . . . . . . . . . . . . . . . . . . 4
1.3. Split-Brain . . . . . . . . . . . . . . . . . . . . . . . 5 1.3. Split-Brain . . . . . . . . . . . . . . . . . . . . . . . 5
1.4. Applicability to H-PCE . . . . . . . . . . . . . . . . . 12 1.4. Applicability to H-PCE . . . . . . . . . . . . . . . . . 12
2. Proposed solution . . . . . . . . . . . . . . . . . . . . . . 12 2. Proposed solution . . . . . . . . . . . . . . . . . . . . . . 12
2.1. State-sync session . . . . . . . . . . . . . . . . . . . 12 2.1. State-sync session . . . . . . . . . . . . . . . . . . . 12
skipping to change at page 30, line 42 skipping to change at page 30, line 42
"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>.
10.2. Informative References 10.2. Informative References
[I-D.knodel-terminology] [I-D.knodel-terminology]
Knodel, M. and N. T. Oever, "Terminology, Power, and Knodel, M. and N. T. Oever, "Terminology, Power, and
Exclusionary Language in Internet-Drafts and RFCs", Work Exclusionary Language in Internet-Drafts and RFCs", Work
in Progress, Internet-Draft, draft-knodel-terminology-06, in Progress, Internet-Draft, draft-knodel-terminology-09,
23 August 2021, <https://datatracker.ietf.org/doc/html/ 9 February 2022, <https://datatracker.ietf.org/doc/html/
draft-knodel-terminology-06>. draft-knodel-terminology-09>.
[RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path [RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path
Computation Element (PCE)-Based Architecture", RFC 4655, Computation Element (PCE)-Based Architecture", RFC 4655,
DOI 10.17487/RFC4655, August 2006, DOI 10.17487/RFC4655, August 2006,
<https://www.rfc-editor.org/info/rfc4655>. <https://www.rfc-editor.org/info/rfc4655>.
[RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the [RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the
Path Computation Element Architecture to the Determination Path Computation Element Architecture to the Determination
of a Sequence of Domains in MPLS and GMPLS", RFC 6805, of a Sequence of Domains in MPLS and GMPLS", RFC 6805,
DOI 10.17487/RFC6805, November 2012, DOI 10.17487/RFC6805, November 2012,
 End of changes. 7 change blocks. 
11 lines changed or deleted 11 lines changed or added

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