Re: [MMUSIC] WG adoption of other WebRTC data channel usage drafts?; Re: New Version Notification for draft-ietf-mmusic-msrp-usage-data-channel-02.txt

Christer Holmberg <> Fri, 16 October 2015 07:26 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0FBC11B2FE7 for <>; Fri, 16 Oct 2015 00:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id M71ON-uo7C9b for <>; Fri, 16 Oct 2015 00:26:29 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B35971B2FE5 for <>; Fri, 16 Oct 2015 00:26:28 -0700 (PDT)
X-AuditID: c1b4fb25-f79a26d00000149a-94-5620a6a29215
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 74.AA.05274.2A6A0265; Fri, 16 Oct 2015 09:26:26 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Fri, 16 Oct 2015 09:26:26 +0200
From: Christer Holmberg <>
To: Flemming Andreasen <>, "Schwarz, Albrecht (Albrecht)" <>, "" <>
Thread-Topic: [MMUSIC] WG adoption of other WebRTC data channel usage drafts?; Re: New Version Notification for draft-ietf-mmusic-msrp-usage-data-channel-02.txt
Thread-Index: AdEACzQi8oHkYmJfQK6mNtv7qVRYfQHfDqWAABciENc=
Date: Fri, 16 Oct 2015 07:26:25 +0000
Message-ID: <>
References: <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-GB
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B45C83ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyM+Jvje6iZQphBls/Wlv8af3FaPH+gq7F 1OWPWRyYPVqf7WX1mPJ7I6vHkiU/mQKYo7hsUlJzMstSi/TtErgy2jffZS3oz6uY1M/WwDg9 vouRk0NCwESi/cIRJghbTOLCvfVsILaQwFFGif9/E7oYuYDsJYwSs2/uZu5i5OBgE7CQ6P6n DRIXEZjBKPFy1Rl2EEdYYDGjxMeGtywQGaCOmatPs4OMEhGwkrjx4xNYN4uAqkRfIzeIySvg K3F0egrEskqJzVtvg1VzCmhKnF90nRHEZgQ66PupNWDHMQuISzR9WckKcaiAxJI955khbFGJ l4//sULU5Esc3joDrJ5XQFDi5MwnLBMYhWchaZ+FpGwWkjKIuIHEl/e3oWxtiWULXzND2PoS 3e9PMyGLL2BkX8UoWpxanJSbbmSsl1qUmVxcnJ+nl5dasokRGE8Ht/xW3cF4+Y3jIUYBDkYl Hl6FKIUwIdbEsuLK3EOM0hwsSuK8zUwPQoUE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwtkjH cm0J9kpwdz16dpXY4YA1J9ZkfLO17H4ZsWxepPIlGbnf3yILJyiZ39+uKyXueEPlifzxI9fm xQY1ah53utb8xrdY4M2We/+qJ53cun92/bG+3c3HCu/FqFYWHvSWuxP2iqtsjpKaS2C5agnL LKHmHdcDFjb9W53SvyNjW/Xb03OkXmZ0KLEUZyQaajEXFScCAGOBSeGIAgAA
Archived-At: <>
Subject: Re: [MMUSIC] WG adoption of other WebRTC data channel usage drafts?; Re: New Version Notification for draft-ietf-mmusic-msrp-usage-data-channel-02.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 16 Oct 2015 07:26:32 -0000


Does a new data channel usage require an RFC???

If someone wants to specify a data channel protocol X, they should be able to do so without having to gather interest in IETF.

Now, in THIS specific case we are talking about MSRP, so maybe it makes sense to publish an RFC.



Sent from my Windows Phone
From: Flemming Andreasen<>
Sent: ‎16/‎10/‎2015 01:23
To: Schwarz, Albrecht (Albrecht)<>;<>
Subject: Re: [MMUSIC] WG adoption of other WebRTC data channel usage drafts?; Re: New Version Notification for draft-ietf-mmusic-msrp-usage-data-channel-02.txt

Hi Albrecht

In order for the WG to take on additional work and specific drafts, we
generally require an expressed interest and support from the WG. We
haven't seen a lot of that so far on these two drafts, so you may want
to try and garner some additional interest and demonstrate that on the
list and/or in the upcoming meeting (let us know if you would like
agenda time to discuss these).


-- Flemming (as MMUSIC chair)

On 10/6/15 3:47 AM, Schwarz, Albrecht (Albrecht) wrote:
> Dear All,
> like too remind that there are three first WebRTC data channel applications,
> 1) MSRP based instant messaging,
> 2) T.140 based text conversation and
> 3) BFCP based floor control within a WebRTC conference service.
> draft-ietf-mmusic-msrp-usage-data-channel was/is the precedent for getting a common understanding about application protocol specific SDP usage (on top of the generic control of a DC).
> The discussion and protocol design are fairly mature in the meanwhile, hence it is time to start the work on the two other applications.
> We've prepared initial drafts, derived from the "MSRP draft", see:
> T.140 Text Conversation over Data Channels
> draft-schwarz-mmusic-t140-usage-data-channel-02.txt
> BFCP floor control signalling over Data Channels
> draft-schwarz-mmusic-bfcp-usage-data-channel-01.txt
> We'd like to request MMUSIC for adoption of these drafts.
> Regards,
> Albrecht
> Re: [MMUSIC] New Version Notification for draft-ietf-mmusic-msrp-usage-data-channel-02.txt
> Juergen Stoetzer-Bradler <> Wed, 09 September 2015 14:45 UTCShow header
> Hello,
> Version 02 of draft-ietf-mmusic-msrp-usage-data-channel addresses Christian's comments to version 01,
> except for the "setup" attribute related one.
> We'll come back regarding the SDP setup attribute, which can be part of an MSRP over data channel
> related SDP media description as media level "a=setup" attribute and/or as MSRP sub-protocol specific
> attribute "a=dcsa:x setup".
> Thanks,
> Juergen
> On 09.09.2015 16:33, wrote:
>> A new version of I-D, draft-ietf-mmusic-msrp-usage-data-channel-02.txt
>> has been successfully submitted by Juergen Stoetzer-Bradler and posted to the
>> IETF repository.
>> Name:                draft-ietf-mmusic-msrp-usage-data-channel
>> Revision:    02
>> Title:               MSRP over Data Channels
>> Document date:       2015-09-09
>> Group:               mmusic
>> Pages:               15
>> URL:  
>> Status:
>> Htmlized:
>> Diff: 
>> Abstract:
>>      This document specifies how the Message Session Relay Protocol (MSRP)
>>      can be instantiated as a data channel sub-protocol, using the SDP
>>      offer/answer exchange-based generic data channel negotiation
>>      framework.  Two network configurations are documented: a WebRTC end-
>>      to-end configuration (connecting two MSRP over data channel
>>      endpoints), and a gateway configuration (connecting an MSRP over data
>>      channel endpoint with an MSRP over TCP endpoint).
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at
>> The IETF Secretariat
> _______________________________________________
> mmusic mailing list
> .

mmusic mailing list