Re: [rtcweb] A few questions on draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00

Christer Holmberg <> Tue, 25 February 2014 22:55 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 48AE91A07C8 for <>; Tue, 25 Feb 2014 14:55:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QUNdop0vifdG for <>; Tue, 25 Feb 2014 14:55:23 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 9700D1A079F for <>; Tue, 25 Feb 2014 14:55:18 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-c1-530d1f545527
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id D0.FB.10875.45F1D035; Tue, 25 Feb 2014 23:55:17 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Tue, 25 Feb 2014 23:55:16 +0100
From: Christer Holmberg <>
To: Randell Jesup <>, "" <>
Thread-Topic: [rtcweb] A few questions on draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00
Thread-Index: Ac8xYc5b69yuJmdXSPqgdx4f9mMa8P///zaA///uN6CAAB/0AP//6jzwgAIpVwD//+vjwA==
Date: Tue, 25 Feb 2014 22:55:16 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLLMWRmVeSWpSXmKPExsUyM+JvjW6oPG+wwbanjBZnt2VZrP3Xzu7A 5LFkyU8mjw/L17EFMEVx2aSk5mSWpRbp2yVwZXRP+Mlc0CVcsWaVQwPjTv4uRk4OCQETiT2n exkhbDGJC/fWs3UxcnEICRxilDg68w4TSEJIYAmjxKyz7l2MHBxsAhYS3f+0QcIiAoESR393 sYPYwgKxEu2PdzBBxOMkHj3Yxg5hh0ns/vIDLM4ioCrx8uxisF28Ar4SP8++YocY38QsMfeR AIjNKaAp0TKxhw3EZgS65/upNWC9zALiEreezGeCuFNAYsme88wQtqjEy8f/WCFsJYkV2y8x QtTrSCzY/YkNwtaWWLbwNTPEXkGJkzOfsExgFJ2FZOwsJC2zkLTMQtKygJFlFSN7bmJmTnq5 4SZGYBQc3PJbdwfjqXMihxilOViUxHk/vHUOEhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cDo w7nmkanui3fTKvXbrfivhZi6BOtw+J5YGLlc337VUT4NixvlG99//XLu4sv7anL8t1lni1Ub L/U78I+nbv8iKf7rWblFDklc4gZrt8ockZ2SYPnXi/+dws3URd8DDk6+tWRSiXv2+ieSX+/M meCU+qI7eG2e5JkMNR5zoWfVZ1LXHcgzmp+rxFKckWioxVxUnAgAtn8pmVACAAA=
Subject: Re: [rtcweb] A few questions on draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Feb 2014 22:55:26 -0000

Hi Randell,

I am not sure whether an WebRTC endpoint (e.g. a browser) would have to implement this. The JS Application can insert the information into the SDP before sending it out on the wire (in cases where SDP is used on the wire).



-----Original Message-----
From: rtcweb [] On Behalf Of Randell Jesup
Sent: 26 February 2014 00:41
Subject: Re: [rtcweb] A few questions on draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00

On 2/24/2014 10:21 AM, Christer Holmberg wrote:
> I still don't think the information belong to SDP - they define protocol characteristics. The protocol specification should define re-transmission timers etc.
> Anyway, we can argue about it later. At this moment I think the focus 
> should be on whether to move forward with the mechanism to begin with, 
> and the main feature of the mechanism - which is about negotiating 
> usage of channels :)

This (whether to move forward) is my concern (in addition to Mary's about this being the wrong group - MMUSIC is where the SDP should be and has been).

The apparent justification for this document is "This document defines SDP-based out-of-band negotiation procedures to establish WebRTC data channels for transport of well-defined sub- protocols." This seems a pretty sparse justification.

We very purposely avoided using SDP for channel setup (after MUCH discussion at Boston and elsewhere).  That isn't to say that for non-webrtc usage, one could define an SDP used to externally-negotiate the settings for DataChannels, which this appears to be.  But I think there should a clearer statement as to "why" we should invest the time to standardize this now, not just that we "can".  For example, if CLUE really wants to use this instead of in-band opens, then maybe there's a reason to do so - but don't expect webrtc endpoints to implement this.  
And if so, it should be done in CLUE by request to MMUSIC.

At this point I don't see need to move forward with this, and certainly not here.  And I certainly don't want this to delay finalizing the stuff needed in MMUSIC for WebRTC use of DataChannels

Randell Jesup -- rjesup a t mozilla d o t com

rtcweb mailing list