A new Request for Comments is now available in online RFC libraries.
RFC 9763
Title: Related Certificates for Use in
Multiple Authentications within a Protocol
Author: A. Becker,
R. Guthrie,
M. Jenkins
Status: Standards Track
Stream: IETF
Date: June 2025
Mailbox: [email protected],
[email protected],
[email protected]
Pages: 13
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lamps-cert-binding-for-multi-auth-06.txt
URL: https://www.rfc-editor.org/info/rfc9763
DOI: 10.17487/RFC9763
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.
This document is a product of the Limited Additional Mechanisms for PKIX and
SMIME 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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
