Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-04.txt
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Wed, 09 April 2014 14:28 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 847AE1A032F for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.823
X-Spam-Level:
X-Spam-Status: No, score=-1.823 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.272, 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 ot60hbbdgPNM for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:28:24 -0700 (PDT)
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 151651A032E for <rtcweb@ietf.org>; Wed, 9 Apr 2014 07:28:24 -0700 (PDT)
Received: from [192.168.1.103] (p508F0BDC.dip0.t-ipconnect.de [80.143.11.220]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 97C9B1C10464D; Wed, 9 Apr 2014 16:28:22 +0200 (CEST)
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: <CAN=GVAvy3qADK4NoJH8FKS5cJA8GQ7rxFLBhNFqkCZ8ZzwmEjw@mail.gmail.com>
Date: Wed, 09 Apr 2014 16:28:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E50492B5-8166-4A2E-A4E6-AE4F4D13C4BE@lurchi.franken.de>
References: <20140409100313.9526.70264.idtracker@ietfa.amsl.com> <CAN=GVAvy3qADK4NoJH8FKS5cJA8GQ7rxFLBhNFqkCZ8ZzwmEjw@mail.gmail.com>
To: Barry Dingle <btdingle@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/eGFlvriXNL9moq4pDan1b5uuxC8
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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:28:25 -0000
On 09 Apr 2014, at 14:17, Barry Dingle <btdingle@gmail.com> wrote: > Hi, > > The first sentence of the Abstract in the WebRTC Data Channel Establishment Protocol incorrectly refers to the "WebRTC working group. (The wording in the second line also needs editing.) > > I suggest copying the first sentence of the Abstract from WebRTC Data Channels (-08 version) so it reads - > > The Real-Time Communication in WEB-browsers working group is charged > to provide protocol support for direct interactive rich communication > using audio, video, and data between two peers' web-browsers. OK. Will be in the next revision. Best regards Michael > > > > 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 > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [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… Barry Dingle
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-p… Michael Tuexen
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-p… Michael Tuexen