Datagram Transport Layer Security
Metadata
- Publisher
- IETF
- Doc Type
- Specification
- Pages
- 25
- Abstract
- This document specifies Version 1.0 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.
- Publication Date
- 2006-04-01
- Status Note
- Historic
- DOI
10.17487/RFC4347- Link
- https://doi.org/10.17487/RFC4347
- Author(s)
- Eric RescorlaNagendra Modadugu
- Keyword(s)
- DTLS
Latest version of IETF RFC 4347
Document Versions — IETF RFC 4347
-
▶ IETF RFC 4347 (2006-04-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 793 [Superseded*]
- IETF RFC 1191 [Active*]
- IETF RFC 1981 [Superseded*]
- IETF RFC 2401 [Superseded*]
- IETF RFC 2988 [Superseded*]
- IETF RFC 4346 [Superseded*]
Bibliographic Reference(s)
- Modadugu, N., Rescorla, E., "The Design and Implementation of Datagram TLS", Proceedings of ISOC NDSS 2004, February 2004. EXTERNAL
- Bernstein, D.J., "Cache-timing attacks on AES" http://cr.yp.to/antiforgery/cachetiming-20050414.pdf . EXTERNAL
- Kohler, E., Handley, M., Floyd, S., Padhye, J., "Datagram Congestion Control Protocol", Work in Progress, 10 March 2005. EXTERNAL
- Bellovin, S., "Guidelines for Mandating the Use of IPsec" , Work in Progress, October 2003. EXTERNAL
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 1939 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2246 [Superseded*]
- IETF RFC 2402 [Superseded*]
- IETF RFC 2406 [Superseded*]
- IETF RFC 2409 [Superseded*]
- IETF RFC 2521 [Active*]
- IETF RFC 2960 [Superseded*]
- IETF RFC 3261 [Active*]
- IETF RFC 3501 [Superseded*]
- IETF RFC 4306 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4347.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4347, Datagram Transport Layer Security. Available at https://doi.org/10.17487/RFC4347
Snippet:
IETF RFC 4347, Datagram Transport Layer Security. Available at https://doi.org/10.17487/RFC4347
HTML (ISO 690 compliant)
Preview:
IETF RFC 4347, Datagram Transport Layer Security. Available at https://doi.org/10.17487/RFC4347
Snippet:
<span class="citation"><cite>IETF RFC 4347</cite>, Datagram Transport Layer Security. Available at <a href="https://doi.org/10.17487/RFC4347" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4347</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4347, Datagram Transport Layer Security
doi: 10.17487/RFC4347
url: https://doi.org/10.17487/RFC4347
doi: 10.17487/RFC4347
url: https://doi.org/10.17487/RFC4347
Snippet:
<li> <cite id="bib-rfc4347">IETF RFC 4347</cite>, Datagram Transport Layer Security <span class="doi">10.17487/RFC4347</span> </li>
Referenced By
- IETF RFC 5101 [Superseded*]
- IETF RFC 5238 [Active*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 5415 [Active*]
- IETF RFC 5456 [Active*]
- IETF RFC 5595 [Active*]
- IETF RFC 5705 [Active*]
- IETF RFC 5746 [Active*]
- IETF RFC 5764 [Active*]
- IETF RFC 5953 [Superseded*]
- IETF RFC 6012 [Active*]
- IETF RFC 6083 [Active*]
- IETF RFC 6084 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6347 [Superseded*]
- IETF RFC 6353 [Active*]
- IETF RFC 6460 [Active*]
- IETF RFC 7457 [Active*]
- IETF RFC 7507 [Superseded*]
- IETF RFC 7525 [Superseded*]
- IETF RFC 8261 [Active*]
- IETF RFC 8996 [Active*]