Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-02.txt
Barry Dingle <btdingle@gmail.com> Mon, 10 February 2014 10:08 UTC
Return-Path: <btdingle@gmail.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 432AB1A06BF for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 02:08:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 zqkf_yEwhIRs for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 02:08:16 -0800 (PST)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 786BE1A05DE for <rtcweb@ietf.org>; Mon, 10 Feb 2014 02:08:16 -0800 (PST)
Received: by mail-wi0-f181.google.com with SMTP id hi5so2607435wib.8 for <rtcweb@ietf.org>; Mon, 10 Feb 2014 02:08:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4t+gjQB4LZFftUhM5xt8yorpZk5FmfBnTg43vc2A9CI=; b=q3pmIVgfdxKed5FsVc1px1GQ9DO1WQWMuqOMdXFsKrJlG9XGfdt3/DfbbplEpXkODp JmJAHOD7YOS7fWS8im2a0cpPbuZThzjEfwPatYjYWaADQUitQ3pqh6V2+pdNZ4N361AR JYX0webR0jFNOEcQycWuw2hE2IAEN/UOwKd3FmZteYHSFo/1s5dwpvkmAs6daCXL3Wjb MOF3Hi/xO2PWCwBSuhFaASpBy4y6xlUa/jFBjbsKcwrqyOgDPbWfCE9ZCTxS1Ss61wwc VLUNFRnjAyJMcD680U5BwshURXnCsoLWYc5IQwXALx+BbGiHsglQtOsS6Ss37LbthqSG osbA==
X-Received: by 10.180.19.69 with SMTP id c5mr9642680wie.7.1392026895964; Mon, 10 Feb 2014 02:08:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.118.226 with HTTP; Mon, 10 Feb 2014 02:07:55 -0800 (PST)
In-Reply-To: <20140209211659.26091.94840.idtracker@ietfa.amsl.com>
References: <20140209211659.26091.94840.idtracker@ietfa.amsl.com>
From: Barry Dingle <btdingle@gmail.com>
Date: Mon, 10 Feb 2014 21:07:55 +1100
Message-ID: <CAN=GVAsVnaRwnSYXDWkbr249LKyVzQ+YGmbZXOWZkYWdwXwViA@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="bcaec53d5a8ba6e2b104f20a849e"
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:08:22 -0000
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. /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 >
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-p… Michael Tuexen
- [rtcweb] I-D Action: draft-ietf-rtcweb-data-proto… internet-drafts
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-p… Barry Dingle
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-p… Salvatore Loreto