DTLS as Subtransport protocol

Document Type Expired Internet-Draft (individual)
Authors Christian Huitema  , Eric Rescorla  , Jana Iyengar 
Last updated 2015-09-06 (latest revision 2015-03-05)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The developers of "user level" transports will benefit from a standard implementation of authentication and encryption. This can be achieved using DTLS as a sub-transport. Using DTLS enables developers to benefit from the investment in TLS, and removes the burden and the risks of re-creating similar technology. There are several requirements to ensure that DTLS is a suitable sub- transport: zero RTT setup, low overhead, and DOS prevention. The IAB SEMI workshop outlined other potential requirements: start/stop indication, and ability to accept indications from the network. The draft presents guidelines for meeting these requirements in a new version of DTLS.


Christian Huitema (huitema@microsoft.com)
Eric Rescorla (ekr@rtfm.com)
Jana Iyengar (jri@google.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)