Session Description Protocol (SDP) Offer/Answer Procedures For Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport.
draft-ietf-mmusic-sctp-sdp-26

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: ben@nostrum.com, mmusic@ietf.org, The IESG <iesg@ietf.org>, fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-sctp-sdp@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Session Description Protocol (SDP) Offer/Answer Procedures For Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport.' to Proposed Standard (draft-ietf-mmusic-sctp-sdp-25.txt)

The IESG has approved the following document:
- 'Session Description Protocol (SDP) Offer/Answer Procedures For Stream
   Control Transmission Protocol (SCTP) over Datagram Transport Layer
   Security (DTLS) Transport.'
  (draft-ietf-mmusic-sctp-sdp-25.txt) as Proposed Standard

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

The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa
Cooper.

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


Technical Summary

The Stream Control Transmission Protocol (SCTP) is a transport protocol used to establish associations between two endpoints. SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol, referred to as SCTP-over-DTLS.

This specification defines the following new Session Description Protocol (SDP) protocol identifiers (proto values): 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.  This specification also specifies how to use the new proto values with the SDP Offer/Answer mechanism for negotiating SCTP-over-DTLS associations.

Working Group Summary

Nothing in particular to note. The document has seen decent WG participation and no particular “roughness” in terms of consensus. 

Document Quality

There are existing implementations of earlier versions of the document and those implementations are expected to be updated. The specification is required in order to use SDP for negotiating WebRTC data channels and hence is expected to see significant vendor adoption.

MIB Doctor, etc. review is Not Applicable.  A TSV-ART review would be helpful.

Personnel

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

RFC Editor Note

Please make the following change in Section 12.2, paragraph 4, 2nd sentence:
 
OLD: “... including switching between UDP to TCP candidate pairs ... ”
 
NEW: “... including switching between UDP and TCP candidate pairs ...”