< draft-ietf-pce-stateful-path-protection-03.txt   draft-ietf-pce-stateful-path-protection-04.txt >
PCE Working Group H. Ananthakrishnan PCE Working Group H. Ananthakrishnan
Internet-Draft Netflix Internet-Draft Netflix
Intended status: Standards Track S. Sivabalan Intended status: Standards Track S. Sivabalan
Expires: April 25, 2019 Cisco Expires: August 7, 2019 Cisco
C. Barth C. Barth
R. Torvi R. Torvi
Juniper Networks Juniper Networks
I. Minei I. Minei
Google, Inc Google, Inc
E. Crabbe E. Crabbe
Individual Contributor Individual Contributor
D. Dhody M. Negi
Huawei Technologies Huawei Technologies
October 22, 2018 February 3, 2019
PCEP Extensions for Associating Working and Protection LSPs with PCEP Extensions for Associating Working and Protection LSPs with
Stateful PCE Stateful PCE
draft-ietf-pce-stateful-path-protection-03 draft-ietf-pce-stateful-path-protection-04
Abstract Abstract
A stateful Path Computation Element (PCE) is capable of computing as A stateful Path Computation Element (PCE) is capable of computing as
well as controlling via Path Computation Element Protocol (PCEP) well as controlling via Path Computation Element Protocol (PCEP)
Multiprotocol Label Switching Traffic Engineering Label Switched Multiprotocol Label Switching Traffic Engineering Label Switched
Paths (MPLS LSP). Furthermore, it is also possible for a stateful Paths (MPLS LSP). Furthermore, it is also possible for a stateful
PCE to create, maintain, and delete LSPs. This document describes PCE to create, maintain, and delete LSPs. This document describes
PCEP extension to associate two or more LSPs to provide end-to-end PCEP extension to associate two or more LSPs to provide end-to-end
path protection. path protection.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 April 25, 2019. This Internet-Draft will expire on August 7, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 50 skipping to change at page 2, line 50
8. Manageability Considerations . . . . . . . . . . . . . . . . 11 8. Manageability Considerations . . . . . . . . . . . . . . . . 11
8.1. Control of Function and Policy . . . . . . . . . . . . . 11 8.1. Control of Function and Policy . . . . . . . . . . . . . 11
8.2. Information and Data Models . . . . . . . . . . . . . . . 11 8.2. Information and Data Models . . . . . . . . . . . . . . . 11
8.3. Liveness Detection and Monitoring . . . . . . . . . . . . 11 8.3. Liveness Detection and Monitoring . . . . . . . . . . . . 11
8.4. Verify Correct Operations . . . . . . . . . . . . . . . . 11 8.4. Verify Correct Operations . . . . . . . . . . . . . . . . 11
8.5. Requirements On Other Protocols . . . . . . . . . . . . . 11 8.5. Requirements On Other Protocols . . . . . . . . . . . . . 11
8.6. Impact On Network Operations . . . . . . . . . . . . . . 12 8.6. Impact On Network Operations . . . . . . . . . . . . . . 12
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12
10.2. Information References . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
[RFC5440] describes PCEP for communication between a Path Computation [RFC5440] describes PCEP for communication between a Path Computation
Client (PCC) and a PCE or between one a pair of PCEs as per Client (PCC) and a PCE or between one a pair of PCEs as per
[RFC4655]. A PCE computes paths for MPLS-TE LSPs based on various [RFC4655]. A PCE computes paths for MPLS-TE LSPs based on various
constraints and optimization criteria. constraints and optimization criteria.
Stateful pce [RFC8231] specifies a set of extensions to PCEP to Stateful pce [RFC8231] specifies a set of extensions to PCEP to
enable stateful control of paths such as MPLS TE LSPs between and enable stateful control of paths such as MPLS TE LSPs between and
skipping to change at page 13, line 21 skipping to change at page 13, line 21
[RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for PCE-Initiated LSP Setup in a Stateful PCE Extensions for PCE-Initiated LSP Setup in a Stateful PCE
Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
<https://www.rfc-editor.org/info/rfc8281>. <https://www.rfc-editor.org/info/rfc8281>.
[I-D.ietf-pce-association-group] [I-D.ietf-pce-association-group]
Minei, I., Crabbe, E., Sivabalan, S., Ananthakrishnan, H., Minei, I., Crabbe, E., Sivabalan, S., Ananthakrishnan, H.,
Dhody, D., and Y. Tanaka, "PCEP Extensions for Dhody, D., and Y. Tanaka, "PCEP Extensions for
Establishing Relationships Between Sets of LSPs", draft- Establishing Relationships Between Sets of LSPs", draft-
ietf-pce-association-group-06 (work in progress), June ietf-pce-association-group-07 (work in progress), December
2018. 2018.
10.2. Information References 10.2. Informative References
[RFC4427] Mannie, E., Ed. and D. Papadimitriou, Ed., "Recovery [RFC4427] Mannie, E., Ed. and D. Papadimitriou, Ed., "Recovery
(Protection and Restoration) Terminology for Generalized (Protection and Restoration) Terminology for Generalized
Multi-Protocol Label Switching (GMPLS)", RFC 4427, Multi-Protocol Label Switching (GMPLS)", RFC 4427,
DOI 10.17487/RFC4427, March 2006, DOI 10.17487/RFC4427, March 2006,
<https://www.rfc-editor.org/info/rfc4427>. <https://www.rfc-editor.org/info/rfc4427>.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, Element (PCE)-Based Architecture", RFC 4655,
DOI 10.17487/RFC4655, August 2006, DOI 10.17487/RFC4655, August 2006,
skipping to change at page 14, line 24 skipping to change at page 14, line 24
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[I-D.ietf-pce-pcep-yang] [I-D.ietf-pce-pcep-yang]
Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A
YANG Data Model for Path Computation Element YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep- Communications Protocol (PCEP)", draft-ietf-pce-pcep-
yang-09 (work in progress), October 2018. yang-09 (work in progress), October 2018.
[I-D.ietf-pce-association-diversity] [I-D.ietf-pce-association-diversity]
Litkowski, S., Sivabalan, S., Barth, C., and D. Dhody, Litkowski, S., Sivabalan, S., Barth, C., and D. Dhody,
"Path Computation Element communication Protocol extension "Path Computation Element communication Protocol (PCEP)
for signaling LSP diversity constraint", draft-ietf-pce- extension for signaling LSP diversity constraint", draft-
association-diversity-04 (work in progress), June 2018. ietf-pce-association-diversity-05 (work in progress),
December 2018.
[I-D.ietf-pce-segment-routing] [I-D.ietf-pce-segment-routing]
Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,
and J. Hardwick, "PCEP Extensions for Segment Routing", and J. Hardwick, "PCEP Extensions for Segment Routing",
draft-ietf-pce-segment-routing-14 (work in progress), draft-ietf-pce-segment-routing-14 (work in progress),
October 2018. October 2018.
[I-D.litkowski-pce-state-sync] [I-D.litkowski-pce-state-sync]
Litkowski, S., Sivabalan, S., and D. Dhody, "Inter Litkowski, S., Sivabalan, S., and D. Dhody, "Inter
Stateful Path Computation Element communication Stateful Path Computation Element communication
procedures", draft-litkowski-pce-state-sync-03 (work in procedures", draft-litkowski-pce-state-sync-04 (work in
progress), April 2018. progress), October 2018.
Appendix A. Contributor Addresses
Dhruv Dhody
Huawei Technologies
Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066
India
EMail: dhruv.ietf@gmail.com
Authors' Addresses Authors' Addresses
Hariharan Ananthakrishnan Hariharan Ananthakrishnan
Netflix Netflix
USA USA
Email: hari@netflix.com Email: hari@netflix.com
Siva Sivabalan Siva Sivabalan
Cisco Cisco
2000 Innovation Drive 2000 Innovation Drive
Kananta, Ontaria K2K 3E8 Kananta, Ontaria K2K 3E8
Canada Canada
Email: msiva@cisco.com Email: msiva@cisco.com
Colby Barth Colby Barth
Juniper Networks Juniper Networks
skipping to change at page 15, line 35 skipping to change at page 16, line 4
Email: rtorvi@juniper.net Email: rtorvi@juniper.net
Ina Minei Ina Minei
Google, Inc Google, Inc
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA, 94043 Mountain View, CA, 94043
USA USA
Email: inaminei@google.com Email: inaminei@google.com
Edward Crabbe Edward Crabbe
Individual Contributor Individual Contributor
Email: edward.crabbe@gmail.com Email: edward.crabbe@gmail.com
Dhruv Dhody
Mahendra Singh Negi
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066 Bangalore, Karnataka 560066
India India
Email: dhruv.ietf@gmail.com Email: mahendrasingh@huawei.com
 End of changes. 15 change blocks. 
17 lines changed or deleted 30 lines changed or added

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