Datagram Transport Layer Security Version 1.2
RFC 6347
Document | Type |
RFC - Proposed Standard
(January 2012; Errata)
Obsoletes RFC 4347
|
|
---|---|---|---|
Authors | Eric Rescorla , Nagendra Modadugu | ||
Last updated | 2015-10-14 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6347 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Sean Turner | ||
IESG note | Joe Salowey (jsalowey@cisco.com) is the document Shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) E. Rescorla Request for Comments: 6347 RTFM, Inc. Obsoletes: 4347 N. Modadugu Category: Standards Track Google, Inc. ISSN: 2070-1721 January 2012 Datagram Transport Layer Security Version 1.2 Abstract 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6347. Rescorla & Modadugu Standards Track [Page 1] RFC 6347 DTLS January 2012 Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Rescorla & Modadugu Standards Track [Page 2] RFC 6347 DTLS January 2012 Table of Contents 1. Introduction ....................................................4 1.1. Requirements Terminology ...................................5 2. Usage Model .....................................................5 3. Overview of DTLS ................................................5 3.1. Loss-Insensitive Messaging .................................6 3.2. Providing Reliability for Handshake ........................6 3.2.1. Packet Loss .........................................6 3.2.2. Reordering ..........................................7 3.2.3. Message Size ........................................7 3.3. Replay Detection ...........................................7 4. Differences from TLS ............................................7 4.1. Record Layer ...............................................8 4.1.1. Transport Layer Mapping ............................10 4.1.1.1. PMTU Issues ...............................10 4.1.2. Record Payload Protection ..........................12 4.1.2.1. MAC .......................................12 4.1.2.2. Null or Standard Stream Cipher ............13 4.1.2.3. Block Cipher ..............................13 4.1.2.4. AEAD Ciphers ..............................13 4.1.2.5. New Cipher Suites .........................13 4.1.2.6. Anti-Replay ...............................13 4.1.2.7. Handling Invalid Records ..................14Show full document text