metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8253: PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)

Still current, but amended. Parts of this document are changed or extended by RFC 9916. Read both.

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8253
Published
October 2017
Authors
D. Lopez; O. Gonzalez de Dios; Q. Wu; D. Dhody
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
26
Also known as
—
Updates:
RFC 5440
Updated by:
RFC 9916

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8253-pceps-usage-of-tls-to-provide-a-secure-transport-for-the-path-computation-elemen