RFC 9763: Related Certificates for Use in Multiple Authentications within a Protocol
In plain English — editorial summary, not part of the RFC
This document defines a new Certificate Signing Request (CSR) attribute, relatedCertRequest, and a new X.509 certificate extension, RelatedCertificate. The use of the relatedCertRequest attribute in a CSR and the inclusion of the RelatedCertificate extension in the resulting certificate together provide additional assurance that two certificates each belong to the same end entity. This mechanism is particularly useful in the context of non-composite hybrid authentication, which enables users to employ the same certificates in hybrid authentication as in authentication done with only traditional or post-quantum algorithms.
Document record
- Document ID
- RFC9763
- Published
- June 2025
- Authors
- A. Becker; R. Guthrie; M. Jenkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9734X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIsCurrent
February 2025
- RFC 9802Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key InfrastructureCurrent
June 2025
- RFC 9881Internet X.509 Public Key Infrastructure -- Algorithm Identifiers for the Module-Lattice-Based Digital Signature Algorithm (ML-DSA)Current
October 2025
- RFC 9935Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)Current
March 2026
- RFC 9980Post-Quantum Cryptography in OpenPGPCurrent
June 2026
- RFC 10024Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3Current
August 2026
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
- RFC 9370Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2023
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?