IETF Logo Mail Archive

Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-07.txt - Comment on section 6 title

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 12 February 2014 10:23 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 BFEED1A092B for <rtcweb@ietfa.amsl.com>; Wed, 12 Feb 2014 02:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 NXYSjcDmDEWU for <rtcweb@ietfa.amsl.com>; Wed, 12 Feb 2014 02:23:47 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id CA7821A092A for <rtcweb@ietf.org>; Wed, 12 Feb 2014 02:23:46 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-bc-52fb4bb1d921
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 2C.21.04853.1BB4BF25; Wed, 12 Feb 2014 11:23:45 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.02.0387.000; Wed, 12 Feb 2014 11:23:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-07.txt - Comment on section 6 title
Thread-Index: Ac8nVPFNLUjUgV0jQBWV6hVVCkMWSAASh4uAAA9Dh5A=
Date: Wed, 12 Feb 2014 10:23:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D16E5F0@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D16D2BA@ESESSMB209.ericsson.se> <52FAF2A9.9070507@alum.mit.edu>
In-Reply-To: <52FAF2A9.9070507@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.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyM+Jvje5G799BBu17pS1WbDjAarH2Xzu7 A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJVx5cNy5oLfnBXLljawNzD+ZO9i5OSQEDCR aHl8kBnCFpO4cG89WxcjF4eQwAlGiVk7GpggnMWMEp3/L7N2MXJwsAlYSHT/0wZpEBHwlei9 fI4RxBYWSJN4cmUrK0Q8XaLh5Uoo20riz88jYDaLgKrEmXkrwGxeoN5Jl44ygdhCAvkSy3+c B4tzCuhIHNvXDHYcI9BB30+tAathFhCXuPVkPhPEoQISS/achzpaVOLl439gp0kIKEos75eD KNeRWLD7ExuErS2xbOFrZoi1ghInZz5hmcAoOgvJ1FlIWmYhaZmFpGUBI8sqRsni1OLi3HQj A73c9NwSvdSizOTi4vw8veLUTYzAaDm45bfRDsaTe+wPMUpzsCiJ815nrQkSEkhPLEnNTk0t SC2KLyrNSS0+xMjEwSnVwLj9WQhPjuf+9Q+urpJV+GOvKz6ha2Yhd8LyW4/WTz6rKStX1yJR 8nLJ7eDXSbOVyxgr9hjJnpZcmOMWJ2tZEf0qdofrjQ7/vuXVC7rZ2V94FizxELd7fyVze9v7 L5a/Sh8u/5e4km3aVPdmzs0sD2JmXWc7fdCvo8Nt5fH4E8HOE1K+NyU8eaDEUpyRaKjFXFSc CACQCOJZZAIAAA==
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-07.txt - Comment on section 6 title
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: Wed, 12 Feb 2014 10:23:50 -0000

Hi,

> I suggest that this just be called "Data Channel", not "WebRTC Data Channel". (Or pick some other neutral name - perhaps SCTP Data Channel.)

Agree. A more generic name would be useful.

"Simple Data Channel"
"Simple SCTP Data Channel"
Etc...

> This won't be used solely for WebRTC. (It seems weird for two sip-based implementations of CLUE to be using a *WebRTC* Data Channel to talk to one another.)
>
> (But it would still make sense for the JS API to have a WebRTC-specific name.)

Agree.

Regards

Christer


On 2/11/14 1:15 PM, Christer Holmberg wrote:
> Hi,
>
> Section 6 describes the characteristics of the data channel.
>
> However, the section name is "The Usage of SCTP in the WebRTC Context".
>
> I think we should rename that to something like "The Usage of SCTP for the WebRTC Data Channel".
>
> Because, the definition of the channel is the same no matter in which 
> context it is used :)
>
> Regards,
>
> Christer
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email