RFC 7345: UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)
In plain English — editorial summary, not part of the RFC
This document specifies how the UDP Transport Layer (UDPTL) protocol, the predominant transport protocol for T.38 fax, can be transported over the Datagram Transport Layer Security (DTLS) protocol, how the usage of UDPTL over DTLS is indicated in the Session Description Protocol (SDP), and how UDPTL over DTLS is negotiated in a session established using the Session Initiation Protocol (SIP).
Document record
- Document ID
- RFC7345
- Published
- August 2014
- Authors
- C. Holmberg; I. Sedlacek; G. Salgueiro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 23
- Also known as
- —
- Updated by:
- RFC 8842
Topics
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 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8373Negotiating Human Language in Real-Time CommunicationsUpdated
May 2018
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 8841Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) TransportCurrent
January 2021
- RFC 6337Session Initiation Protocol (SIP) Usage of the Offer/Answer ModelCurrent
August 2011
- RFC 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
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?