RFC 9916: Updates to the Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
In plain English — editorial summary, not part of the RFC
Section 3.4 of RFC 8253 specifies TLS connection establishment restrictions for PCEPS; PCEPS refers to usage of TLS to provide a secure transport for the Path Computation Element Communication Protocol (PCEP). This document adds restrictions to specify what PCEPS implementations do if they support more than one version of the TLS protocol and to restrict the use of TLS 1.3's early data.
Document record
- Document ID
- RFC9916
- Published
- July 2026
- Authors
- D. Dhody; S. Turner; R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 8253
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9918Updates to Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 AuthenticationCurrent
July 2026
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 9862Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate PathsCurrent
October 2025
- RFC 9753Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) ObjectsCurrent
April 2025
- RFC 9603Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment RoutingUpdated
July 2024
- RFC 9357Label Switched Path (LSP) Object Flag Extension for Stateful PCEUpdated
February 2023
- RFC 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 8745Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCEUpdated
March 2020
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?