PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
RFC 8253
| Document | Type |
RFC - Proposed Standard
(October 2017; Errata)
Updates RFC 5440
Was draft-ietf-pce-pceps (pce WG)
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Replaces | draft-lopez-pce-pceps | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Cyril Margaria | ||
| Shepherd write-up | Show (last changed 2017-04-24) | ||
| IESG | IESG state | RFC 8253 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Deborah Brungard | ||
| Send notices to | Cyril Margaria <cmargaria@juniper.net> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) D. Lopez
Request for Comments: 8253 O. Gonzalez de Dios
Updates: 5440 Telefonica I+D
Category: Standards Track Q. Wu
ISSN: 2070-1721 D. Dhody
Huawei
October 2017
PCEPS: Usage of TLS to Provide a Secure Transport for the
Path Computation Element Communication Protocol (PCEP)
Abstract
The Path Computation Element Communication Protocol (PCEP) defines
the mechanisms for the communication between a Path Computation
Client (PCC) and a Path Computation Element (PCE), or among PCEs.
This document describes PCEPS -- the usage of Transport Layer
Security (TLS) to provide a secure transport for PCEP. The
additional security mechanisms are provided by the transport protocol
supporting PCEP; therefore, they do not affect the flexibility and
extensibility of PCEP.
This document updates RFC 5440 in regards to the PCEP initialization
phase procedures.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8253.
Lopez, et al. Standards Track [Page 1]
RFC 8253 PCEPS October 2017
Copyright Notice
Copyright (c) 2017 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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Lopez, et al. Standards Track [Page 2]
RFC 8253 PCEPS October 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 5
3. Applying PCEPS . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Initiating TLS Procedures . . . . . . . . . . . . . . . . 5
3.3. The StartTLS Message . . . . . . . . . . . . . . . . . . 8
3.4. TLS Connection Establishment . . . . . . . . . . . . . . 13
3.5. Peer Identity . . . . . . . . . . . . . . . . . . . . . . 15
3.6. Connection Establishment Failure . . . . . . . . . . . . 16
4. Discovery Mechanisms . . . . . . . . . . . . . . . . . . . . 16
4.1. DANE Applicability . . . . . . . . . . . . . . . . . . . 17
5. Backward Compatibility . . . . . . . . . . . . . . . . . . . 17
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
6.1. New PCEP Message . . . . . . . . . . . . . . . . . . . . 18
6.2. New Error-Values . . . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. Manageability Considerations . . . . . . . . . . . . . . . . 20
8.1. Control of Function and Policy . . . . . . . . . . . . . 20
8.2. Information and Data Models . . . . . . . . . . . . . . . 21
8.3. Liveness Detection and Monitoring . . . . . . . . . . . . 21
Show full document text