RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
In plain English — editorial summary, not part of the RFC
This document specifies version 1.3 of the Datagram Transport Layer Security (DTLS) protocol. DTLS 1.3 allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. The DTLS 1.3 protocol is based on the Transport Layer Security (TLS) 1.3 protocol and provides equivalent security guarantees with the exception of order protection / non-replayability. Datagram semantics of the underlying transport are preserved by the DTLS protocol. This document obsoletes RFC 6347.
Document record
- Document ID
- RFC9147
- Published
- April 2022
- Authors
- E. Rescorla; H. Tschofenig; N. Modadugu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 61
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 4347 (2006)
- RFC 6347 (2012)
- RFC 9147 (2022)
Read the full history of The Datagram Transport Layer Security (DTLS) Protocol Version 1.3 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 8224Authenticated Identity Management in the Session Initiation Protocol (SIP)Updated
February 2018
- RFC 7375Secure Telephone Identity Threat ModelCurrent
October 2014
- RFC 7340Secure Telephone Identity Problem Statement and RequirementsCurrent
September 2014
- RFC 9148EST-coaps: Enrollment over Secure Transport with the Secure Constrained Application ProtocolUpdated
April 2022
- RFC 9146Connection Identifier for DTLS 1.2Updated
March 2022
- RFC 9149TLS Ticket RequestsCurrent
April 2022
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
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?