RFC 9916 on Updates to the Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)

rfc-editor@rfc-editor.org Tue, 14 July 2026 23:27 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from celery-78f7859f6-lcn9z (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id D9DA9116E0592; Tue, 14 Jul 2026 16:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784071677; bh=EKcelfBQSdaqmkPycJ1ItmQlbCC9RcCWwoFabUmoZC8=; h=Subject:From:To:Cc:Date; b=xlz7Au5WT3dsl14DhBitwLrLu5/OCUEsqVV6Kli7lJFI4esf34l8i/LXOmJj0rJpa QFx/HxxXSlEcrYspgOg7QD5jfG1bY4O4noIg5X8Y02whCnXWz87Vse8HUDdmlwsaHx 1HEQ0lJIqHP/hq0FYmHOBT3F9uz57tYwHAC91hR0=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9916 on Updates to the Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Tue, 14 Jul 2026 23:27:57 -0000
message-id: <178407167777.12.14070263535087782683@rfc-editor.org>
Message-ID-Hash: 3RLT5K6HQCY7OBRNAQNUGYAKEOZ3GGZN
X-Message-ID-Hash: 3RLT5K6HQCY7OBRNAQNUGYAKEOZ3GGZN
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nomCzW8mUy2XaQstBV_Sbs6c6o4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        RFC 9916

        Title:      Updates to the Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
        Author:     D. Dhody,
                    S. Turner,
                    R. Housley
        Status:     Proposed Standard
        Stream:     IETF
        Date:       July 2026
        Mailbox:    dd@dhruvdhody.com,
                    sean@sn3rd.com,
                    housley@vigilsec.com
        Pages:      5
        Updates:    RFC 8253


        I-D Tag:    draft-ietf-pce-pceps-tls13-04

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

        DOI:        10.17487/RFC9916

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.

This document is a product of the Path Computation Element Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

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