Extension for Stateful PCE to allow Optional Processing of PCEP Objects
draft-dhody-pce-stateful-pce-optional-06
PCE Working Group C. Li
Internet-Draft H. Zheng
Updates: 8231 (if approved) Huawei Technologies
Intended status: Standards Track S. Litkowski
Expires: January 10, 2021 Cisco
July 09, 2020
Extension for Stateful PCE to allow Optional Processing of PCEP Objects
draft-dhody-pce-stateful-pce-optional-06
Abstract
This document introduces a mechanism to mark some of the Path
Computation Element (PCE) Communication Protocol (PCEP) objects as
optional during PCEP messages exchange for the Stateful PCE model to
allow relaxing some constraints. This document introduces this
relaxation and updates the RFC 8231.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 10, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Li, et al. Expires January 10, 2021 [Page 1]
Internet-Draft STATEFUL-OPT July 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Usage Example . . . . . . . . . . . . . . . . . . . . . . 4
3. PCEP Extension . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. STATEFUL-PCE-CAPABILITY TLV . . . . . . . . . . . . . . . 4
3.2. Handling of P flag . . . . . . . . . . . . . . . . . . . 5
3.2.1. The PCRpt message . . . . . . . . . . . . . . . . . . 5
3.2.2. The PCUpd message and the PCInitiate message . . . . 5
3.3. Handling of I flag . . . . . . . . . . . . . . . . . . . 5
3.3.1. The PCUpd message . . . . . . . . . . . . . . . . . . 5
3.3.2. The PCRpt message . . . . . . . . . . . . . . . . . . 6
3.3.3. The PCInitiate message . . . . . . . . . . . . . . . 6
3.4. Delegation . . . . . . . . . . . . . . . . . . . . . . . 6
3.5. Unknown Object Handling . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5.1. STATEFUL-PCE-CAPABILITY TLV . . . . . . . . . . . . . . . 7
6. Manageability Considerations . . . . . . . . . . . . . . . . 7
6.1. Control of Function and Policy . . . . . . . . . . . . . 7
6.2. Information and Data Models . . . . . . . . . . . . . . . 7
6.3. Liveness Detection and Monitoring . . . . . . . . . . . . 8
6.4. Verify Correct Operations . . . . . . . . . . . . . . . . 8
6.5. Requirements On Other Protocols . . . . . . . . . . . . . 8
6.6. Impact On Network Operations . . . . . . . . . . . . . . 8
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
[RFC5440] describes the Path Computation Element communication
Protocol (PCEP) which enables the communication between a Path
Computation Client (PCC) and a Path Control Element (PCE), or between
two PCEs based on the PCE architecture [RFC4655].
Show full document text