A new Request for Comments is now available in online RFC libraries.

        
        RFC 9353

        Title:      IGP Extension for Path Computation 
                    Element Communication Protocol (PCEP) 
                    Security Capability Support in
                    PCE Discovery (PCED) 
        Author:     D. Lopez,
                    Q. Wu,
                    D. Dhody,
                    Q. Ma,
                    D. King
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2023
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      13
        Updates:    RFC 5088, RFC 5089, RFC 8231, RFC 8306

        I-D Tag:    draft-ietf-lsr-pce-discovery-security-support-13.txt

        URL:        https://www.rfc-editor.org/info/rfc9353

        DOI:        10.17487/RFC9353

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.

This document is a product of the Link State Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to