RFC 9932: Mutually Authenticating TLS in the Context of Federations
In plain English — editorial summary, not part of the RFC
This Informational Independent Submission to the RFC Series describes a means to use TLS 1.3 to perform machine-to-machine mutual authentication within federations. This memo is not a standard. It does not modify the TLS protocol in any way, nor does it require changes to common TLS libraries. TLS is specified and standardized by the IETF's TLS Working Group. The framework enables interoperable trust management for federated machine-to-machine communication. It introduces a centrally managed trust anchor and a controlled metadata publication process, ensuring that only authorized members are identifiable within the federation. These mechanisms support unambiguous entity identification and reduce the risk of impersonation, promoting secure and policy-aligned interaction across organizational boundaries.
Document record
- Document ID
- RFC9932
- Published
- April 2026
- Authors
- S. Halén; J. Schlyter
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
- RFC 8576Internet of Things (IoT) Security: State of the Art and ChallengesCurrent
April 2019
- RFC 7712Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)Current
November 2015
- RFC 7711PKIX over Secure HTTP (POSH)Current
November 2015
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 5716Requirements for Federated File SystemsCurrent
January 2010
- RFC 2693SPKI Certificate TheoryCurrent
September 1999
- RFC 2692SPKI RequirementsCurrent
September 1999
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?