RFC 9345: Delegated Credentials for TLS and DTLS
In plain English — editorial summary, not part of the RFC
The organizational separation between operators of TLS and DTLS endpoints and the certification authority can create limitations. For example, the lifetime of certificates, how they may be used, and the algorithms they support are ultimately determined by the Certification Authority (CA). This document describes a mechanism to overcome some of these limitations by enabling operators to delegate their own credentials for use in TLS and DTLS without breaking compatibility with peers that do not support this specification.
Document record
- Document ID
- RFC9345
- Published
- July 2023
- Authors
- R. Barnes; S. Iyengar; N. Sullivan; E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 9763Related Certificates for Use in Multiple Authentications within a ProtocolCurrent
June 2025
- RFC 9367GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.3Current
February 2023
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
- RFC 9635Grant Negotiation and Authorization Protocol (GNAP)Current
October 2024
- RFC 9045Algorithm Requirements Update to the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Current
June 2021
- RFC 9044Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)Current
June 2021
- RFC 9734X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIsCurrent
February 2025
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?