Subject: [MMUSIC] FW: New Version Notification for draft-ietf-mmusic-data-channel-sdpneg-22.txt

From: "Roni Even (A)" <[email-masked]>
Date: Mon, 19 Nov 2018 10:04:57 +0000

Hi,
Updated the document to reference https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-30 in order to resolve the open issue discussed in IETF103
Roni

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Monday, November 19, 2018 12:02 PM
To: Maridi R. Makaraju (Raju); Jerome Marcon; Richard Ejzak; [email-masked]; Maridi Makaraju; Juergen Stoetzer-Bradler; Keith Drage; Roni Even (A); Juergen Stoetzer-Bradler
Subject: New Version Notification for draft-ietf-mmusic-data-channel-sdpneg-22.txt

A new version of I-D, draft-ietf-mmusic-data-channel-sdpneg-22.txt
has been successfully submitted by Roni Even and posted to the IETF repository.

Name:		draft-ietf-mmusic-data-channel-sdpneg
Revision:	22
Title:		SDP-based Data Channel Negotiation
Document date:	2018-11-19
Group:		mmusic
Pages:		39
URL:            https://www.ietf.org/internet-drafts/draft-ietf-mmusic-data-channel-sdpneg-22.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-data-channel-sdpneg/
Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-22
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-data-channel-sdpneg
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-data-channel-sdpneg-22

Abstract:
   The Real-Time Communication in WEB-browsers (RTCWeb) working group is
   charged to provide protocols to support direct interactive rich
   communications using audio, video, and data between two peers' web-
   browsers.  For the support of data communication, the RTCWeb working
   group has in particular defined the concept of bi-directional data
   channels over SCTP (Stream Control Transmission Protocol), where each
   data channel might be used to transport other protocols, called
   subprotocols.  Data channel setup can be done using either the in-
   band Data Channel Establishment Protocol (DCEP) or using some out-of-
   band non-DCEP protocol.  This document specifies how the SDP (Session
   Description Protocol) offer/answer exchange can be used to achieve
   such an out-of-band non-DCEP negotiation.  Even though data channels
   are designed for RTCWeb use initially, they may be used by other
   protocols like, but not limited to, the CLUE protocol (which is
   defined by the IETF "ControLling mUltiple streams for tElepresence"
   working group).  This document is intended to be used wherever data
   channels are used.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat