draft-ietf-pce-local-protection-enforcement-00.txt   draft-ietf-pce-local-protection-enforcement-01.txt 
Network Working Group A. Stone Network Working Group A. Stone
Internet-Draft M. Aissaoui Internet-Draft M. Aissaoui
Updates: 5440 (if approved) Nokia Updates: 5440 (if approved) Nokia
Intended status: Standards Track S. Sidor Intended status: Standards Track S. Sidor
Expires: May 20, 2021 Cisco Systems, Inc. Expires: July 17, 2021 Cisco Systems, Inc.
S. Sivabalan S. Sivabalan
Ciena Coroporation Ciena Coroporation
November 16, 2020 January 13, 2021
Local Protection Enforcement in PCEP Local Protection Enforcement in PCEP
draft-ietf-pce-local-protection-enforcement-00 draft-ietf-pce-local-protection-enforcement-01
Abstract Abstract
This document updates [RFC5440] to clarify usage of the local This document updates [RFC5440] to clarify usage of the local
protection desired bit signalled in Path Computation Element Protocol protection desired bit signalled in Path Computation Element Protocol
(PCEP). This document also introduces a new flag for signalling (PCEP). This document also introduces a new flag for signalling
protection strictness in PCEP. protection strictness in PCEP.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 May 20, 2021. This Internet-Draft will expire on July 17, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 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 23 skipping to change at page 2, line 23
4. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Implementation differences . . . . . . . . . . . . . . . 4 4.1. Implementation differences . . . . . . . . . . . . . . . 4
4.2. SLA Enforcement . . . . . . . . . . . . . . . . . . . . . 4 4.2. SLA Enforcement . . . . . . . . . . . . . . . . . . . . . 4
5. Protection Enforcement Flag (E-Flag) . . . . . . . . . . . . 5 5. Protection Enforcement Flag (E-Flag) . . . . . . . . . . . . 5
5.1. Backwards Compatibility . . . . . . . . . . . . . . . . . 7 5.1. Backwards Compatibility . . . . . . . . . . . . . . . . . 7
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 7 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 7
6.1. Nokia Implementation . . . . . . . . . . . . . . . . . . 8 6.1. Nokia Implementation . . . . . . . . . . . . . . . . . . 8
6.2. Cisco Implementation . . . . . . . . . . . . . . . . . . 8 6.2. Cisco Implementation . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8.1. LSP Attributes Protection Enforcement Flag . . . . . . . 9 8.1. LSPA Object . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . 11
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Path Computation Element (PCE) Communication Protocol (PCEP) Path Computation Element (PCE) Communication Protocol (PCEP)
[RFC5440] enables the communication between a Path Computation Client [RFC5440] enables the communication between a Path Computation Client
(PCC) and a Path Control Element (PCE), or between two PCEs based on (PCC) and a Path Control Element (PCE), or between two PCEs based on
the PCE architecture [RFC4655]. the PCE architecture [RFC4655].
skipping to change at page 9, line 19 skipping to change at page 9, line 19
behaviour. The introduction of this new flag and behaviour behaviour. The introduction of this new flag and behaviour
clarification does not create any new sensitive information. No clarification does not create any new sensitive information. No
additional security measure is required. additional security measure is required.
Securing the PCEP session using Transport Layer Security (TLS) Securing the PCEP session using Transport Layer Security (TLS)
[RFC8253], as per the recommendations and best current practices in [RFC8253], as per the recommendations and best current practices in
[RFC7525] is RECOMMENDED. [RFC7525] is RECOMMENDED.
8. IANA Considerations 8. IANA Considerations
8.1. LSP Attributes Protection Enforcement Flag 8.1. LSPA Object
This document defines a new LSP Attribute Flag; IANA is requested to This document defines a new flag in the LSPA Object. IANA is
make the following bit allocation from the "LSPA Object" sub registry requested to allocate the following code point in the "LSPA Object
of the PCEP Numbers registry, as follows: Flag Field" subregistry in the "Path Computation Element Protocol
(PCEP) Numbers" registry.
Value Name Reference Value Name Reference
TBD PROTECTION-ENFORCEMENT This document TBD Protection Enforcement This document
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
 End of changes. 10 change blocks. 
12 lines changed or deleted 13 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/