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

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 25 February 2014 22:41 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8884A1A02F4 for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 14:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 ehrUI1P9F05l for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 14:41:29 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 4146C1A0338 for <rtcweb@ietf.org>; Tue, 25 Feb 2014 14:41:29 -0800 (PST)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by QMTA11.westchester.pa.mail.comcast.net with comcast id WbzW1n0051wpRvQ5BmhUBA; Tue, 25 Feb 2014 22:41:28 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta18.westchester.pa.mail.comcast.net with comcast id WmhT1n0193ZTu2S3emhUX3; Tue, 25 Feb 2014 22:41:28 +0000
Message-ID: <530D1C17.9020703@alum.mit.edu>
Date: Tue, 25 Feb 2014 17:41:27 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1B4DA3@ESESSMB209.ericsson.se> <CAJuyhsz4ZG_ReNEqmu+fTcSDfXxCnKWaVBhYvjf4XsWxSXB1mQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1B5097@ESESSMB209.ericsson.se> <CAJuyhsxz4X2aDNx2Y1Y2Gi9G0D12Ort95QFD=cQ6s-zM5GK9Uw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1B5305@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826DFF58DB@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1B59FA@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826DFF5D26@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1B839A@ESESSMB209.ericsson.se> <530CCB54.4000106@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D1B9882@ESESSMB209.ericsson.se> <530D17B8.1070105@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D1BA5A7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1BA5A7@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393368088; bh=/+FQS+qp86ZqoEtKMX8/cDC26jW5kdpVuI8E6mC2X6Q=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Jgb0Flf1OSkwVGxfMqKvKrF01S3P82/8N2ETif+jUvXhhOLpGG+i1AlmrL8ooIe2E mgSS0lJTcExh7r14FtZbcBLUEDo2x/7jj9Z8zr3jRi8tDVIqddlq9gA0qtpGYxAC+D +zD/an8wZKFJ4eS+DbTh6KiEMb/MUpvlT+2Q6cNh+hpXI+rUOUI4fdddcUJfgqQNIa Le3OzeUgLwpbGdmxOCMCu9VwAHEjgxX+nW93opti7sfpKThQQ2J/aNOdDBgTfIv2wA /nE2KXsiuIRUpzKvXTjMkeWZN3hnL8DTDlpqZLVrO/D6AtSw1LBtlAIw5rP42PJ1VC m3rPVyjtxbcWQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/3XZ2p0en12oEycTrmNzLvyWlscg
Subject: Re: [rtcweb] A few questions on draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 22:41:32 -0000

On 2/25/14 5:29 PM, Christer Holmberg wrote:
> Hi,
>
>>>> So these parameters are needed to properly initialize a channel when
>>>> the subprotocol is not specified.
>>>
>>> Why would someone NOT specify the subprotocol?
>>
>> Because there is no defined subprotocol for what they are doing?
>>
>> In the common webrtc use case with two browsers talking to the same web service, and the web
>> service feeding the needed javascript to the browsers, they just "know" the protocol they are using. > So they may just "make it up", and have nothing registered.
>>
>> It is when they need to interoperate with something else that it becomes important to name and
>> register the protocol.
>>
>>> Especially considering Richard's draft, I thought the whole idea was to be able to negotiate the
>>> subprotocol using SDP.
>>
>> That's for us, not them. :-)
>>
>> They will be using DCEP.
>
> Sure, but my question is about the usage of the attributes in SDP (Richard's draft).

Are you then suggesting that the subprotocol MUST be supplied in the SDP?

I think we need some careful consideration of what rules are common to 
all data channels, and which ones can be different when using SDP rather 
than DCEP. That should consider how something first built using DCEP can 
be migrated to using SDP when it is discovered that it needs to 
interoperate with a sip server.

Unclear if that discussion should take place on rtcweb or mmusic.

	Thanks,
	Paul