RFC 9353: IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
In plain English — editorial summary, not part of the RFC
When a Path Computation Element (PCE) is a Label Switching Router (LSR) or a server participating in the Interior Gateway Protocol (IGP), its presence and path computation capabilities can be advertised using IGP flooding. The IGP extensions for PCE Discovery (PCED) (RFCs 5088 and 5089) define a method to advertise path computation capabilities using IGP flooding for OSPF and IS-IS, respectively. However, these specifications lack a method to advertise Path Computation Element Communication Protocol (PCEP) security (e.g., Transport Layer Security (TLS) and TCP Authentication Option (TCP-AO)) support capability. This document defines capability flag bits for the PCE-CAP-FLAGS sub-TLV that can be announced as an attribute in the IGP advertisement to distribute PCEP security support information. In addition, this document updates RFCs 5088 and 5089 to allow advertisement of a Key ID or KEY-CHAIN-NAME sub-TLV to support TCP-AO security capability. This document also updates RFCs 8231 and 8306.
Document record
- Document ID
- RFC9353
- Published
- January 2023
- Authors
- D. Lopez; Q. Wu; D. Dhody; Q. Ma; D. King
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8934PCE Communication Protocol (PCEP) Extensions for Label Switched Path (LSP) Scheduling with Stateful PCEUpdated
October 2020
- RFC 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 5441A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched PathsCurrent
April 2009
- RFC 5376Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)Current
November 2008
- RFC 4927Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic EngineeringCurrent
June 2007
- RFC 5468Performance Analysis of Inter-Domain Path Computation MethodologiesCurrent
April 2009
- RFC 9352IS-IS Extensions to Support Segment Routing over the IPv6 Data PlaneCurrent
February 2023
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?