IETF Logo Mail Archive

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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Thu, 18 July 2013 09: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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF5F621E80AA for <rtcweb@ietfa.amsl.com>; Thu, 18 Jul 2013 02:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3UqSnXRrEHw for <rtcweb@ietfa.amsl.com>; Thu, 18 Jul 2013 02:11:55 -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 589AF21E809B for <rtcweb@ietf.org>; Thu, 18 Jul 2013 02:11:55 -0700 (PDT)
Received: from [192.168.1.200] (p508F0EA8.dip0.t-ipconnect.de [80.143.14.168]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 557071C0C0692; Thu, 18 Jul 2013 11:11:54 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CAJrXDUFGM9+bw7KcYxwK9s_MbzW2L_1xjshTocgTKxpur345Nw@mail.gmail.com>
Date: Thu, 18 Jul 2013 11:11:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD542B20-8EA3-45F8-B9F1-7991F207F2A1@lurchi.franken.de>
References: <20130715203130.5677.31855.idtracker@ietfa.amsl.com> <CAJrXDUFGM9+bw7KcYxwK9s_MbzW2L_1xjshTocgTKxpur345Nw@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
X-Mailer: Apple Mail (2.1508)
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 18 Jul 2013 09:11:56 -0000

On Jul 16, 2013, at 2:43 AM, Peter Thatcher <pthatcher@google.com> wrote:

> Hey Randell, can you give a short summary of the changes, if any, that I would or other implementors would need to know about?
Hi Peter,

using
http://tools.ietf.org/rfcdiff?url1=http://tools.ietf.org/id/draft-jesup-rtcweb-data-protocol-04.txt&url2=http://tools.ietf.org/id/draft-ietf-rtcweb-data-protocol-00.txt
you see that in addition to clarifications and cleanups
* external negotiation of data channels is described
* the packet format of the DATA_CHANNEL_OPEN message as been changed
Both of these changes require code changes.

Best regards
Michael
> 
> 
> On Mon, Jul 15, 2013 at 1:31 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 Protocol
>         Author(s)       : Randell Jesup
>                           Salvatore Loreto
>                           Michael Tuexen
>         Filename        : draft-ietf-rtcweb-data-protocol-00.txt
>         Pages           : 11
>         Date            : 2013-07-15
> 
> 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 an actual (minor) protocol for how
>    the JS-layer DataChannel objects provide the data channels between
>    the peers.
> 
> 
> 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-00
> 
> 
> 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

v2.23.0 | Report a Bug | By Email