draft-ietf-pce-stateful-pce-auto-bandwidth-07.txt   draft-ietf-pce-stateful-pce-auto-bandwidth-08.txt 
PCE Working Group D. Dhody PCE Working Group D. Dhody
Internet-Draft U. Palle Internet-Draft U. Palle
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: November 22, 2018 R. Singh Expires: May 23, 2019 R. Singh
Juniper Networks Juniper Networks
R. Gandhi R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
L. Fang L. Fang
Expedia, Inc. Expedia, Inc.
May 21, 2018 November 19, 2018
PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with
Stateful PCE Stateful PCE
draft-ietf-pce-stateful-pce-auto-bandwidth-07 draft-ietf-pce-stateful-pce-auto-bandwidth-08
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
computations in response to Path Computation Clients (PCCs) requests. computations in response to Path Computation Clients (PCCs) requests.
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 Label Switched Paths (TE Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE
LSPs) using PCEP. LSPs) using PCEP.
skipping to change at page 27, line 32 skipping to change at page 27, line 32
Error-Type Meaning & error values Reference Error-Type Meaning & error values Reference
----------------------------------------------------------------- -----------------------------------------------------------------
19 Invalid Operations 19 Invalid Operations
Error-Value = TBD4: [This document] Error-Value = TBD4: [This document]
Auto-Bandwidth Capability Auto-Bandwidth Capability
was not Advertised was not Advertised
8.5. Notification Object 8.5. Notification Object
IANA is requested to allocate new Notification Types and Notification IANA is requested to allocate new Notification Type and Notification
Values within the "Notification Object" sub-registry of the PCEP Values within the "Notification Object" sub-registry of the PCEP
Numbers registry, as follows: Numbers registry, as follows:
Type Meaning Reference Type Meaning Reference
----------------------------------------------------------------- -----------------------------------------------------------------
TBD3 Auto-Bandwidth Overwhelm State [This document] TBD3 Auto-Bandwidth Overwhelm State [This document]
Notification-value=1: Entering Auto-Bandwidth Notification-value=1: Entering Auto-Bandwidth
overwhelm state overwhelm state
Notification-value=2: Clearing Auto-Bandwidth Notification-value=2: Clearing Auto-Bandwidth
skipping to change at page 28, line 28 skipping to change at page 28, line 28
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Pah [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Pah
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for Stateful PCE", RFC 8231, DOI Extensions for Stateful PCE", RFC 8231, DOI
10.17487/RFC8231, September 2017, <https://www.rfc- 10.17487/RFC8231, September 2017,
editor.org/infor/rfc8231>. <https://www.rfc-editor.org/infor/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
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP
skipping to change at page 29, line 8 skipping to change at page 29, line 8
Hardwick, "Path Computation Element Communication Protocol Hardwick, "Path Computation Element Communication Protocol
(PCEP) Management Information Base (MIB) Module", RFC (PCEP) Management Information Base (MIB) Module", RFC
7420, December 2014. 7420, December 2014.
[RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path [RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path
Computation Element (PCE)", RFC 8051, January 2017. Computation Element (PCE)", RFC 8051, January 2017.
[RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage [RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage
of TLS to Provide a Secure Transport for the Path of TLS to Provide a Secure Transport for the Path
Computation Element Communication Protocol (PCEP)", RFC Computation Element Communication Protocol (PCEP)", RFC
8253, October 2017, <https://www.rfc- 8253, October 2017,
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. [I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and J.
Tantsura, "A YANG Data Model for Path Computation Element Tantsura, "A YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep-yang Communications Protocol (PCEP)", draft-ietf-pce-pcep-yang
(work in progress). (work in progress).
[IEEE.754.1985] Institute of Electrical and Electronics Engineers, [IEEE.754.1985] Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", IEEE "Standard for Binary Floating-Point Arithmetic", IEEE
Standard 754, August 1985. Standard 754, August 1985.
skipping to change at page 31, line 33 skipping to change at page 31, line 33
Ravi Singh Ravi Singh
Juniper Networks Juniper Networks
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
Email: ravis@juniper.net Email: ravis@juniper.net
Rakesh Gandhi Rakesh Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
Canada
Email: rgandhi@cisco.com Email: rgandhi@cisco.com
Luyuan Fang Luyuan Fang
Expedia, Inc. Expedia, Inc.
USA USA
Email: luyuanf@gmail.com Email: luyuanf@gmail.com
 End of changes. 8 change blocks. 
9 lines changed or deleted 10 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/