RFC 9963: Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9963
- Published
- April 2026
- Authors
- D. Benjamin; A. Popov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9964ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
May 2026
- RFC 9965The eap.arpa. Domain and Extensible Authentication Protocol (EAP) ProvisioningCurrent
May 2026
- RFC 9966Bootstrapped TLS Authentication with Proof of KnowledgeCurrent
May 2026
- RFC 9967System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)Current
May 2026
- RFC 9958Post-Quantum Cryptography for EngineersCurrent
June 2026
- RFC 9955Hybrid Signature SpectrumsCurrent
July 2026
- RFC 9954Hybrid Key Exchange in TLS 1.3Current
July 2026
- RFC 9973TLS 1.3 Extension for Using Certificates with an External Pre-Shared KeyCurrent
July 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?