Fwd: [TLS] RFC 9147 on The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
ISTO-PWG Internet Printing Protocol workgroup discussion forum via ipp <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Hooray - DTLS/1.3 is finally published as an RFC! ---------- Forwarded message --------- From: <[email protected]> Date: Thu, Apr 21, 2022 at 6:34 PM Subject: [TLS] RFC 9147 on The Datagram Transport Layer Security (DTLS) Protocol Version 1.3 To: <[email protected]>, <[email protected]> Cc: <[email protected]>, <[email protected]>, <[email protected] > A new Request for Comments is now available in online RFC libraries. RFC 9147 Title: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3 Author: E. Rescorla, H. Tschofenig, N. Modadugu Status: Standards Track Stream: IETF Date: April 2022 Mailbox: [email protected], [email protected], [email protected] Pages: 61 Obsoletes: RFC 6347 I-D Tag: draft-ietf-tls-dtls13-43.txt URL: https://www.rfc-editor.org/info/rfc9147 DOI: 10.17487/RFC9147 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. This document is a product of the Transport Layer Security 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 Association Management Solutions, LLC _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp