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

Barry Dingle <btdingle@gmail.com> Wed, 09 April 2014 14:20 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 A56F91A0336 for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 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, MISSING_HEADERS=1.021, 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 XGRSHPy-3qaL for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:20:14 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 1A25C1A032F for <rtcweb@ietf.org>; Wed, 9 Apr 2014 07:20:13 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id bs8so9590920wib.1 for <rtcweb@ietf.org>; Wed, 09 Apr 2014 07:20:13 -0700 (PDT)
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:cc :content-type; bh=sKFCqCdCNIQBgYBAZ8NzGhCDhp8Yv9yMt5rgztx4cgo=; b=Y/kJIooosWyk+wLlBe5SbzW4OrLY+7evqOupx1OWyVfNnTFAQLqGO66k4gavohDXb9 leiJiZICsYm+I5X2huQ5JEuoVsAZH9DoYUZu4rCw/sWK+SnF35X0S4rJhlhYhxna0mhD zfVpro6b1fysoEoerUYiiSOKI11vjZY/KK6p4ex+nemvdr+X38auhW6TNtZ/jEcjvROE h3804f7NoE68igS/FkPHeQWXZdBZjOUQMGGSNFCrSOx3n0cPkd4M7dM0qF6lL9uW6C8H LoOs3rvycFEA5tWlQfpTkOVg8tnWPyIrUeIJrn0hEHXey5S0RrwE8Zlnmqi8WQL7m0WQ DocA==
X-Received: by 10.194.189.80 with SMTP id gg16mr1990015wjc.84.1397053212793; Wed, 09 Apr 2014 07:20:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.91.212 with HTTP; Wed, 9 Apr 2014 07:19:52 -0700 (PDT)
In-Reply-To: <20140409100313.9526.70264.idtracker@ietfa.amsl.com>
References: <20140409100313.9526.70264.idtracker@ietfa.amsl.com>
From: Barry Dingle <btdingle@gmail.com>
Date: Thu, 10 Apr 2014 00:19:52 +1000
Message-ID: <CAN=GVAvyRSUADutwaZsB7pPnTVmrjcrbXV0MfHVW7v4ufhCF_w@mail.gmail.com>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bb03f9c7b20a104f69ccca7
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/jHR9lQ1kct7JcEezUCAhJH-loms
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-04.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: Wed, 09 Apr 2014 14:20:15 -0000

Data Channel Establishment Protocol *Editorials* -

Section 4 - 2nd paragraph -

Change

"The set of consistent properties includes "   to the following

"The set of consistent properties includes : "


Section 4 - 3rd para (after the 6 dot points), 2nd sentence reads as
follows -

"The side wanting to open a data channel selects an SCTP stream
identifier for which the
   corresponding incoming and outgoing SCTP stream is unused and sends a
   DATA_CHANNEL_OPEN message on this outgoing SCTP stream. "

This is confusing. I suggest it be simplified to -

"The side wanting to open a data channel selects an unused SCTP stream
identifier   and sends a
   DATA_CHANNEL_OPEN message on this outgoing SCTP stream. "


Cheers,
/Barry Dingle
Australia


On Wed, Apr 9, 2014 at 8:03 PM, <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 Establishment Protocol
>         Authors         : Randell Jesup
>                           Salvatore Loreto
>                           Michael Tuexen
>         Filename        : draft-ietf-rtcweb-data-protocol-04.txt
>         Pages           : 12
>         Date            : 2014-04-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-04
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-data-protocol-04
>
>
> 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
>