Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-02.txt

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Mon, 10 February 2014 10:11 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 462931A07D5 for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 02:11:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.548, 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 yLzQLstBLK7M for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 02:11:53 -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 5BA4B1A05DE for <rtcweb@ietf.org>; Mon, 10 Feb 2014 02:11:53 -0800 (PST)
Received: from [192.168.1.200] (p54819372.dip0.t-ipconnect.de [84.129.147.114]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 6C12A1C0B3FE4; Mon, 10 Feb 2014 11:11:52 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CAN=GVAsVnaRwnSYXDWkbr249LKyVzQ+YGmbZXOWZkYWdwXwViA@mail.gmail.com>
Date: Mon, 10 Feb 2014 11:11:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <122F40CC-C008-4C98-9705-DAD089D6A16C@lurchi.franken.de>
References: <20140209211659.26091.94840.idtracker@ietfa.amsl.com> <CAN=GVAsVnaRwnSYXDWkbr249LKyVzQ+YGmbZXOWZkYWdwXwViA@mail.gmail.com>
To: Barry Dingle <btdingle@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-02.txt
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, 10 Feb 2014 10:11:56 -0000

On Feb 10, 2014, at 11:07 AM, Barry Dingle <btdingle@gmail.com> wrote:

> Protocol looks good. 
> 
> One small point - the title of this protocol is "WebRTC Data Channel Protocol" but the Abstract says "This document specifies a simple protocol for establishing symmetric data channels between the peers."  This could cause confusion between what is a Data Channel Protocol and what is an Establishing protocol. 
> 
> It appears that the title of this protocol should be "WebRTC Data Channel Establishment Protocol" in order to avoid future confusion as to its purpose. 
You are right, the protocol is just for establishing data channels.
Other opinions regarding the name change?

Best regards
Michael
> 
> /Barry Dingle
> Australia
> 
> 
> On Mon, Feb 10, 2014 at 8:16 AM, <internet-drafts@ietf.org> wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.
> 
>         Title           : WebRTC Data Channel Protocol
>         Authors         : Randell Jesup
>                           Salvatore Loreto
>                           Michael Tuexen
>         Filename        : draft-ietf-rtcweb-data-protocol-02.txt
>         Pages           : 12
>         Date            : 2014-02-09
> 
> Abstract:
>    The Web Real-Time Communication (WebRTC) working group is charged to
>    provide protocols to support for direct interactive rich
>    communication using audio, video, and data between two peers' web-
>    browsers.  This document specifies a simple protocol for establishing
>    symmetric data channels between the peers.  It uses a two way
>    handshake and allows sending of user data without waiting for the
>    handshake to complete.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-data-protocol/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-data-protocol-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> 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