Viewing source data: RFC9353 indexed from relaton-data-rfcs RFC 9353
docid.type IETF
docid.primary True 10.17487/RFC9353
docid#2.type DOI
docnumber RFC9353
language en
type standard
script Latn
date.value January 2023
date.type published
relation.type updates
relation.bibitem.formattedref.content RFC5088
relation.bibitem.formattedref.format text/plain RFC5088
relation.bibitem.docid.type IETF
relation.bibitem.docid.primary True RFC5088
relation#2.type updates
relation#2.bibitem.formattedref.content RFC5089
relation#2.bibitem.formattedref.format text/plain RFC5089
relation#2.bibitem.docid.type IETF
relation#2.bibitem.docid.primary True RFC5089
relation#3.type updates
relation#3.bibitem.formattedref.content RFC8231
relation#3.bibitem.formattedref.format text/plain RFC8231
relation#3.bibitem.docid.type IETF
relation#3.bibitem.docid.primary True RFC8231
relation#4.type updates
relation#4.bibitem.formattedref.content RFC8306
relation#4.bibitem.formattedref.format text/plain RFC8306
relation#4.bibitem.docid.type IETF
relation#4.bibitem.docid.primary True RFC8306
title.content IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
title.format text/plain
title.type main
abstract.content <p>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.</p><p>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.</p>
abstract.format text/html
abstract.script Latn
abstract.language en
revdate January 2023
contributor.role.type author Latn en D D. Latn en Lopez Latn en D. Lopez Latn en
contributor#2.role.type author Latn en Q Q. Latn en Wu Latn en Q. Wu Latn en
contributor#3.role.type author Latn en D D. Latn en Dhody Latn en D. Dhody Latn en
contributor#4.role.type author Latn en Q Q. Latn en Ma Latn en Q. Ma Latn en
contributor#5.role.type author Latn en D D. Latn en King Latn en D. King Latn en
contributor#6.role.type publisher RFC Publisher
contributor#7.role.type authorizer RFC Series
series.title.content RFC
series.title.format text/plain
series.number 9353
series.type main
keyword Path Computation Element
ext.schema-version v1.0.0 lsr
schema-version v1.2.1
id RFC9353