RFC 9353 on IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
rfc-editor@rfc-editor.org Sat, 14 January 2023 01:23 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9490DC16FE5F; Fri, 13 Jan 2023 17:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7naaggAO2Web; Fri, 13 Jan 2023 17:23:24 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8296C16ECA3; Fri, 13 Jan 2023 17:23:24 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D69324C292; Fri, 13 Jan 2023 17:23:24 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9353 on IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lsr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230114012324.D69324C292@rfcpa.amsl.com>
Date: Fri, 13 Jan 2023 17:23:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GWvIaSln4dur6oGSN8SQwn5_5TA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2023 01:23:28 -0000
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: diego.r.lopez@telefonica.com,
bill.wu@huawei.com,
dhruv.ietf@gmail.com,
maqiufang1@huawei.com,
daniel@olddog.co.uk
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC