draft-ietf-pce-lsp-control-request-02.txt   draft-ietf-pce-lsp-control-request-03.txt 
PCE Working Group A. Raghuram PCE Working Group A. Raghuram
Internet-Draft A. Goddard Internet-Draft A. Goddard
Intended status: Standards Track C. Yadlapalli Intended status: Standards Track C. Yadlapalli
Expires: June 21, 2019 AT&T Expires: August 9, 2019 AT&T
J. Karthik J. Karthik
S. Sivabalan S. Sivabalan
J. Parker J. Parker
Cisco Systems, Inc. Cisco Systems, Inc.
D. Dhody M. Negi
Huawei Technologies Huawei Technologies
December 18, 2018 February 5, 2019
Ability for a stateful Path Computation Element (PCE) to request and Ability for a stateful Path Computation Element (PCE) to request and
obtain control of a LSP obtain control of a LSP
draft-ietf-pce-lsp-control-request-02 draft-ietf-pce-lsp-control-request-03
Abstract Abstract
The stateful Path Computation Element (PCE) communication Protocol The stateful Path Computation Element (PCE) communication Protocol
(PCEP) extensions provide stateful control of Multiprotocol Label (PCEP) extensions provide stateful control of Multiprotocol Label
Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP) Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP)
via PCEP, for a model where a Path Computation Client (PCC) delegates via PCEP, for a model where a Path Computation Client (PCC) delegates
control over one or more locally configured LSPs to a stateful PCE. control over one or more locally configured LSPs to a stateful PCE.
There are use-cases in which a stateful PCE may wish to request and There are use-cases in which a stateful PCE may wish to request and
obtain control of one or more LSPs from a PCC. This document obtain control of one or more LSPs from a PCC. This document
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 June 21, 2019. This Internet-Draft will expire on August 9, 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 47 skipping to change at page 2, line 47
7.1. Control of Function and Policy . . . . . . . . . . . . . 6 7.1. Control of Function and Policy . . . . . . . . . . . . . 6
7.2. Information and Data Models . . . . . . . . . . . . . . . 6 7.2. Information and Data Models . . . . . . . . . . . . . . . 6
7.3. Liveness Detection and Monitoring . . . . . . . . . . . . 6 7.3. Liveness Detection and Monitoring . . . . . . . . . . . . 6
7.4. Verify Correct Operations . . . . . . . . . . . . . . . . 6 7.4. Verify Correct Operations . . . . . . . . . . . . . . . . 6
7.5. Requirements On Other Protocols . . . . . . . . . . . . . 7 7.5. Requirements On Other Protocols . . . . . . . . . . . . . 7
7.6. Impact On Network Operations . . . . . . . . . . . . . . 7 7.6. Impact On Network Operations . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Stateful PCEP extensions [RFC8231] specifies a set of extensions to Stateful PCEP extensions [RFC8231] specifies a set of extensions to
PCEP [RFC5440] to enable stateful control of TE LSPs between and PCEP [RFC5440] to enable stateful control of TE LSPs between and
across PCEP sessions in compliance with [RFC4657]. It includes across PCEP sessions in compliance with [RFC4657]. It includes
mechanisms to effect LSP state synchronization between PCCs and PCEs, mechanisms to effect LSP state synchronization between PCCs and PCEs,
delegation of control of LSPs to PCEs, and PCE control of timing and delegation of control of LSPs to PCEs, and PCE control of timing and
sequence of path computations within and across PCEP sessions. The sequence of path computations within and across PCEP sessions. The
stateful PCEP defines the following two useful network operations: stateful PCEP defines the following two useful network operations:
skipping to change at page 8, line 7 skipping to change at page 8, line 7
<https://www.rfc-editor.org/info/rfc8231>. <https://www.rfc-editor.org/info/rfc8231>.
[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>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-pce-pcep-yang]
Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A
YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep-
yang-09 (work in progress), October 2018.
[RFC4657] Ash, J., Ed. and J. Le Roux, Ed., "Path Computation [RFC4657] Ash, J., Ed. and J. Le Roux, Ed., "Path Computation
Element (PCE) Communication Protocol Generic Element (PCE) Communication Protocol Generic
Requirements", RFC 4657, DOI 10.17487/RFC4657, September Requirements", RFC 4657, DOI 10.17487/RFC4657, September
2006, <https://www.rfc-editor.org/info/rfc4657>. 2006, <https://www.rfc-editor.org/info/rfc4657>.
[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,
<https://www.rfc-editor.org/info/rfc8051>. <https://www.rfc-editor.org/info/rfc8051>.
[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-pce-pcep-yang]
Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A
YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep-
yang-09 (work in 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
Aswatnarayan Raghuram Aswatnarayan Raghuram
AT&T AT&T
200 S Laurel Aevenue 200 S Laurel Aevenue
Middletown, NJ 07748 Middletown, NJ 07748
USA USA
Email: ar2521@att.com EMail: ar2521@att.com
Al Goddard Al Goddard
AT&T AT&T
200 S Laurel Aevenue 200 S Laurel Aevenue
Middletown, NJ 07748 Middletown, NJ 07748
USA USA
Email: ag6941@att.com EMail: ag6941@att.com
Chaitanya Yadlapalli Chaitanya Yadlapalli
AT&T AT&T
200 S Laurel Aevenue 200 S Laurel Aevenue
Middletown, NJ 07748 Middletown, NJ 07748
USA USA
Email: cy098d@att.com EMail: cy098d@att.com
Jay Karthik Jay Karthik
Cisco Systems, Inc. Cisco Systems, Inc.
125 High Street 125 High Street
Boston, Massachusetts 02110 Boston, Massachusetts 02110
USA USA
Email: jakarthi@cisco.com EMail: jakarthi@cisco.com
Siva Sivabalan Siva Sivabalan
Cisco Systems, Inc. Cisco Systems, Inc.
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario K2K 3E8 Kanata, Ontario K2K 3E8
Canada Canada
Email: msiva@cisco.com EMail: msiva@cisco.com
Jon Parker Jon Parker
Cisco Systems, Inc. Cisco Systems, Inc.
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario K2K 3E8 Kanata, Ontario K2K 3E8
Canada Canada
Email: jdparker@cisco.com EMail: jdparker@cisco.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. 17 change blocks. 
21 lines changed or deleted 32 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/