RFC 9963 on Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3
rfc-editor@rfc-editor.org Tue, 28 April 2026 23:29 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B4E95E5369B9; Tue, 28 Apr 2026 16:29:36 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 99FCD2D4106; Tue, 28 Apr 2026 16:29:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9963 on Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260428232936.99FCD2D4106@rfcpa.rfc-editor.org>
Date: Tue, 28 Apr 2026 16:29:36 -0700
Message-ID-Hash: CBOV5VUWOCCWNWWK3X44OISCP6X6VOEA
X-Message-ID-Hash: CBOV5VUWOCCWNWWK3X44OISCP6X6VOEA
X-MailFrom: wwwrun@rfcpa.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: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tls@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/OZGNetCgo0-5cmmiPZGsP-7h22c>
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 9963
Title: Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3
Author: D. Benjamin,
A. Popov
Status: Standards Track
Stream: IETF
Date: April 2026
Mailbox: davidben@google.com,
andreipo@microsoft.com
Pages: 6
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tls-tls13-pkcs1-07.txt
URL: https://www.rfc-editor.org/info/rfc9963
DOI: 10.17487/RFC9963
This document allocates code points for the use of RSASSA-PKCS1-v1_5
with client certificates in TLS 1.3. This removes an obstacle for
some deployments to migrate to TLS 1.3.
This document is a product of the Transport Layer Security 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