RFC 6083: Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)
In plain English — editorial summary, not part of the RFC
This document describes the usage of the Datagram Transport Layer Security (DTLS) protocol over the Stream Control Transmission Protocol (SCTP). DTLS over SCTP provides communications privacy for applications that use SCTP as their transport protocol and allows client/server applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. Applications using DTLS over SCTP can use almost all transport features provided by SCTP and its extensions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6083
- Published
- January 2011
- Authors
- M. Tuexen; R. Seggelmann; E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
- Updated by:
- RFC 8996
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 6093On the Implementation of the TCP Urgent MechanismObsoleted
January 2011
- RFC 6096Stream Control Transmission Protocol (SCTP) Chunk Flags RegistrationObsoleted
January 2011
- RFC 6069Making TCP More Robust to Long Connectivity Disruptions (TCP-LCD)Current
December 2010
- RFC 6056Recommendations for Transport-Protocol Port RandomizationCurrent
January 2011
- RFC 6040Tunnelling of Explicit Congestion NotificationUpdated
November 2010
- RFC 6016Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNsCurrent
October 2010
- RFC 6191Reducing the TIME-WAIT State Using TCP TimestampsCurrent
April 2011
- RFC 5961Improving TCP's Robustness to Blind In-Window AttacksUpdated
August 2010
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?