PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol
RFC 8253, “PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol”, is a Proposed Standard document published in October 2017 by D. Lopez, O. Gonzalez de Dios, Q. Wu, D. Dhody. It updates RFC 5440. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8253 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8252 OAuth 2.0 for Native Apps
- RFC 8254 Uniform Resource Name Namespace Registration Transition
- RFC 8251 Updates to the Opus Audio Codec
- RFC 8255 Multiple Language Content Type
- RFC 8250 IPv6 Performance and Diagnostic Metrics Destination Option
- RFC 8256 Requirements for Hitless MPLS Path Segment Monitoring
- RFC 8249 Transparent Interconnection of Lots of Links : MTU Negotiation
- RFC 8257 Data Center TCP : TCP Congestion Control for Data Centers