Datagram Transport Layer Security Version 1.2
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: RFC Editor <email@example.com>, tls mailing list <firstname.lastname@example.org>, tls chair <email@example.com> Subject: Protocol Action: 'Datagram Transport Layer Security version 1.2' to Proposed Standard (draft-ietf-tls-rfc4347-bis-06.txt) The IESG has approved the following document: - 'Datagram Transport Layer Security version 1.2' (draft-ietf-tls-rfc4347-bis-06.txt) as a Proposed Standard This document is the product of the Transport Layer Security Working Group. The IESG contact persons are Sean Turner and Stephen Farrell. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-tls-rfc4347-bis/
Technical Summary This document specifies Version 1.2 of the Datagram Transport Layer Security (DTLS) protocol. The DTLS protocol provides communications privacy for datagram protocols. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the Transport Layer Security (TLS) protocol and provides equivalent security guarantees. Datagram semantics of the underlying transport are preserved by the DTLS protocol. This document updates DTLS 1.0 to work with TLS version 1.2. Working Group Summary This document has been extensively reviewed int he working group. There is strong consensus to move the document forward. The document completed working group last call last year, but was delayed during the discussion of other higher priority documents. Document Quality There are several vendors who implement DTLS 1.1. Vendors have indicated they would support DTLS 1.2 to take advantage of AEAD cipher suites. The document has ve reviewed by security and transport experts. The document has been reviewed by implementers. Personnel Joe Salowey <firstname.lastname@example.org> is the Document Shepherd. Sean Turner <email@example.com> is the Responsible Area Director.