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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Mon, 03 March 2014 12:22 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 46E1F1A00AB for <rtcweb@ietfa.amsl.com>; Mon, 3 Mar 2014 04:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.547, SPF_HELO_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 3EmyyftPZNWL for <rtcweb@ietfa.amsl.com>; Mon, 3 Mar 2014 04:22:44 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCC01A00A8 for <rtcweb@ietf.org>; Mon, 3 Mar 2014 04:22:44 -0800 (PST)
Received: from dhcp-9fd9.meeting.ietf.org (dhcp-9fd9.meeting.ietf.org [31.133.159.217]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 1D3D21C0E97AE; Mon, 3 Mar 2014 13:22:41 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826DFDC6A1@US70UWXCHMBA02.zam.alcatel-lucent.com>
Date: Mon, 3 Mar 2014 12:22:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D616A97-C717-4EED-B7C7-9DBBE7D0B908@lurchi.franken.de>
References: <7594FB04B1934943A5C02806D1A2204B1D16D2BA@ESESSMB209.ericsson.se> <52FAF2A9.9070507@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D16E5F0@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826DFDC6A1@US70UWXCHMBA02.zam.alcatel-lucent.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Cnlz4JmzzEu1yOCSA3zfhKJOQ6Q
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Mon, 03 Mar 2014 12:22:46 -0000

On 12 Feb 2014, at 18:56, Makaraju, Maridi Raju (Raju) <Raju.Makaraju@alcatel-lucent.com> wrote:

>> 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...
> 
> [Raju] How about "Application Data Channel"?
What about:
"The Usage of SCTP for Data Channels"

Best regards
Michael
> 
>> (But it would still make sense for the JS API to have a WebRTC-specific name.)
> +1
> 
> -raju
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>