IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 25 February 2014 22:29 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 5E6201A0187 for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 14:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znR3g6WosPRO for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 14:29:26 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 13D9F1A0790 for <rtcweb@ietf.org>; Tue, 25 Feb 2014 14:29:25 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-af-530d1944efa5
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 51.D1.23809.4491D035; Tue, 25 Feb 2014 23:29:24 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.02.0387.000; Tue, 25 Feb 2014 23:29:23 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: VS: [rtcweb] A few questions on draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00
Thread-Index: Ac8xYc5b69yuJmdXSPqgdx4f9mMa8P///zaA///uN6CAAB/0AP//6jzw//+a7YD//x16EP/+ONLQ//ubSND/9sNUAP/taKmw/9qUQQD/tRccgA==
Date: Tue, 25 Feb 2014 22:29:22 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1BA5A7@ESESSMB209.ericsson.se>
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>
In-Reply-To: <530D17B8.1070105@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+Jvja6LJG+wQftzcYsVGw6wWqz9187u wOTx9/0HJo8lS34yBTBFcdmkpOZklqUW6dslcGXMX/eYseAie8Xyo1+ZGhj/s3YxcnJICJhI NDzYzQhhi0lcuLeerYuRi0NI4BCjxMJvz1lAEkICSxglrp8U72Lk4GATsJDo/qcNEhYR8JXo vXwOrFdYIFHizvnpzBDxJIl9fSdZIew6ibNTZoDZLAKqErvvzmcDsXmBeqeeu8EKsWsmm8SD O8fBmjkFdCSmn9nEBGIzAh30/dQaMJtZQFzi1pP5TBCHCkgs2XOeGcIWlXj5+B/UM0oSi25/ hqrXkViw+xMbhK0tsWzha2aIxYISJ2c+YZnAKDoLydhZSFpmIWmZhaRlASPLKkb23MTMnPRy o02MwFg4uOW36g7GO+dEDjFKc7AoifN+eOscJCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoEx ZF2J+1ruvzrRoqrHLJtFTzhwx89yDWBuOXlX1KhXo7SuMqP9LyOTZ/IrEe53h3MXXr3cd9C5 7uaXv+JhiR1bEkRz6lJ97Eq0dk1MZXaTfxfTl7Ms/n7lwr3ChSbBrEFmlQcTisMDSu6F3Tnj 5v9hJweDWuuyB49v/+sp3dHwxWPhjklV0kosxRmJhlrMRcWJAKJvsxdTAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/T-pJz4TolhobEQxG5HvDFNIm39M
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:29:32 -0000

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).

Regards,

Christer

v2.31.3 | Report a Bug | By Email | System Status