RFC 9763 on Related Certificates for Use in Multiple Authentications within a Protocol

rfc-editor@rfc-editor.org Fri, 13 June 2025 23:32 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 DB21934CEF44; Fri, 13 Jun 2025 16:32:28 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A68482673AA; Fri, 13 Jun 2025 16:32:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9763 on Related Certificates for Use in Multiple Authentications within a Protocol
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250613233228.A68482673AA@rfcpa.rfc-editor.org>
Date: Fri, 13 Jun 2025 16:32:28 -0700
Message-ID-Hash: IMSDO2T4WWAKJOG23FJHKCSAEMDJTI5Q
X-Message-ID-Hash: IMSDO2T4WWAKJOG23FJHKCSAEMDJTI5Q
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, spasm@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/8neuM6eXUCVCtcOTfjc6s1Rur70>
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 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:    aebecke@uwe.nsa.gov,
                    rmguthr@uwe.nsa.gov,
                    mjjenki@cyber.nsa.gov
        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 rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team