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 <christer.holmberg@ericsson.com> Fri, 16 October 2015 09:50 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F011B34C8 for <mmusic@ietfa.amsl.com>; Fri, 16 Oct 2015 02:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZgDE87imqFu for <mmusic@ietfa.amsl.com>; Fri, 16 Oct 2015 02:50:55 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB99F1B34CE for <mmusic@ietf.org>; Fri, 16 Oct 2015 02:50:54 -0700 (PDT)
X-AuditID: c1b4fb3a-f79136d0000071e2-4d-5620c87ca13f
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6E.40.29154.C78C0265; Fri, 16 Oct 2015 11:50:52 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.226]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0248.002; Fri, 16 Oct 2015 11:50:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, Flemming Andreasen <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
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: AdEACzQi8oHkYmJfQK6mNtv7qVRYfQHfDqWAABciENcABMSN8AAARuCY
Date: Fri, 16 Oct 2015 09:50:51 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37B45FDB@ESESSMB209.ericsson.se>
References: <786615F3A85DF44AA2A76164A71FE1ACDF796695@FR711WXCHMBA01.zeu.alcatel-lucent.com>, <56202783.3010300@cisco.com> <7594FB04B1934943A5C02806D1A2204B37B45C83@ESESSMB209.ericsson.se>, <786615F3A85DF44AA2A76164A71FE1ACDF79D867@FR711WXCHMBA01.zeu.alcatel-lucent.com>
In-Reply-To: <786615F3A85DF44AA2A76164A71FE1ACDF79D867@FR711WXCHMBA01.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B45FDBESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM+JvjW7NCYUwg/YbNhZ/Wn8xWry/oGsx dfljFgdmj9Zne1k9pvzeyOqxZMlPpgDmKC6blNSczLLUIn27BK6MOdf+shcsn89YcWiOeAPj /y7GLkYODgkBE4l1T4O7GDmBTDGJC/fWs3UxcnEICRxllPi+/y0ThLOEUWLB2XYWkAY2AQuJ 7n/aIHERgRmMEq9/XmQEcYQFFjNKfGx4ywKRAeqYufo0O8hcEQE3iQtrbzKD2CwCqhJLjjxj BbF5BXwlvs24wgJiCwn0MUk86PEB2cApECtx+mMESJgR6KTvp9YwgdjMAuISTV9WskKcKiCx ZM95ZghbVOLl43+sIK3MAvkSe5Z5QkwXlDg58wnLBEbhWUi6ZyFUzUJSBVFiIHFu+0Z2CFtb YtnC18wQtr7E9tszWZHFFzCyr2IULU4tLs5NNzLSSy3KTC4uzs/Ty0st2cQIjKiDW35b7WA8 +NzxEKMAB6MSD69ClEKYEGtiWXFl7iFGaQ4WJXHeZqYHoUIC6YklqdmpqQWpRfFFpTmpxYcY mTg4pRoYixne3bEUCuO60Furksd8lePw7qC/r7/PiKrefMKLn61Q/H1XZdxtRcUKUfV5q9sF E95PZHQq8fB5GLbuerMBY21q/cuctRMdXBZYrb62/lil8qFjHa+cI07MeRW6OcL50WqDiyFr 5m6o85MxTlD9d77yWUCu7ecPHAu9RabO2cUqN/nR+e1KSizFGYmGWsxFxYkAnFnPOokCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/grlOI6ejlMuqRcIgEbRolchTekI>
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-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 09:50:58 -0000

Sorry - my mistake. But, my comment applies to BFCP too.

I see no reason why IETF should work on a T.140 draft however - unless there are lots of people who want to do it (which I doubt).

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Schwarz, Albrecht (Albrecht)<mailto:albrecht.schwarz@alcatel-lucent.com>
Sent: ‎16/‎10/‎2015 12:43
To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>; Flemming Andreasen<mailto:fandreas@cisco.com>; mmusic@ietf.org<mailto:mmusic@ietf.org>
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

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

This email thread is about T.140 and BFCP, not MSRP! The MSRP draft is already adopted by the WG.


From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Freitag, 16. Oktober 2015 09:26
To: Flemming Andreasen; Schwarz, Albrecht (Albrecht); mmusic@ietf.org
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,

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.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Flemming Andreasen<mailto:fandreas@cisco.com>
Sent: ‎16/‎10/‎2015 01:23
To: Schwarz, Albrecht (Albrecht)<mailto:albrecht.schwarz@alcatel-lucent.com>; mmusic@ietf.org<mailto:mmusic@ietf.org>
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).

Thanks

-- 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 <Juergen.Stoetzer-Bradler@alcatel-lucent.com<mailto:Juergen.Stoetzer-Bradler@alcatel-lucent.com>> 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,
> http://www.ietf.org/mail-archive/web/mmusic/current/msg14537.html,
> 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, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> 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:            https://www.ietf.org/internet-drafts/draft-ietf-mmusic-msrp-usage-data-channel-02.txt
>> Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-msrp-usage-data-channel/
>> Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-msrp-usage-data-channel-02
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-msrp-usage-data-channel-02
>>
>> 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 tools.ietf.org.
>>
>> The IETF Secretariat
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org<mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic