Skip to main content

Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)
draft-ietf-mmusic-dtls-sdp-32

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: draft-ietf-mmusic-dtls-sdp@ietf.org, ben@nostrum.com, mmusic@ietf.org, The IESG <iesg@ietf.org>, fandreas@cisco.com, mmusic-chairs@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)' to Proposed Standard (draft-ietf-mmusic-dtls-sdp-32.txt)

The IESG has approved the following document:
- 'Session Description Protocol (SDP) Offer/Answer Considerations for
   Datagram Transport Layer Security (DTLS) and Transport Layer
   Security (TLS)'
  (draft-ietf-mmusic-dtls-sdp-32.txt) as Proposed Standard

This document is the product of the Multiparty Multimedia Session Control
Working Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-dtls-sdp/


Ballot Text

Technical Summary

The document defines the SDP offer/answer procedures for negotiating and establishing a DTLS association.  The document also defines the criteria for when a new DTLS association must be established.  The document updates RFC 5763 and RFC 7345, by replacing common SDP   offer/answer procedures with a reference to this specification. The document defines a new SDP media-level attribute, 'dtls-id'.

Working Group Summary

There was originally no controversy or anything else to note. Version 22 of this draft underwent 
IETF Last Call. Subsequently, the working group elected to add support for TLS, which was a 
material change. Therefore the IETF Last Call was repeated with version 26.

Document Quality

There are existing implementations of the protocol, and a number of vendors have indicated that they intend to implement it.

Personnel

Flemming Andreasen is the Document Shepherd. 
Ben Campbell is the Area Director

RFC Editor Note