[rtcweb] TR : I-D Action: draft-ietf-rtcweb-data-channel-05.txt

"MARCON, JEROME (JEROME)" <jerome.marcon@alcatel-lucent.com> Fri, 02 August 2013 13:00 UTC

Return-Path: <jerome.marcon@alcatel-lucent.com>
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 4FE3311E8342 for <rtcweb@ietfa.amsl.com>; Fri, 2 Aug 2013 06:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 4kzfVEKdSZwh for <rtcweb@ietfa.amsl.com>; Fri, 2 Aug 2013 06:00:25 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF3F11E8317 for <rtcweb@ietf.org>; Fri, 2 Aug 2013 05:59:57 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r72CxnEv013864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 2 Aug 2013 07:59:51 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r72Cxmxr024847 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Aug 2013 14:59:49 +0200
Received: from FR711WXCHMBA02.zeu.alcatel-lucent.com ([169.254.2.36]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 2 Aug 2013 14:59:48 +0200
From: "MARCON, JEROME (JEROME)" <jerome.marcon@alcatel-lucent.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "randell-ietf@jesup.org" <randell-ietf@jesup.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-05.txt
Thread-Index: AQHOgZEM4YD2XdHBEUicFlTuBgZVUZmB+L1I
Date: Fri, 2 Aug 2013 12:59:48 +0000
Message-ID: <39821B4C400EC14DAD4DB25330A9271A0816BB0A@FR711WXCHMBA02.zeu.alcatel-lucent.com>
References: <20130715192354.17142.94001.idtracker@ietfa.amsl.com>
In-Reply-To: <20130715192354.17142.94001.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_39821B4C400EC14DAD4DB25330A9271A0816BB0AFR711WXCHMBA02z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: [rtcweb] TR : I-D Action: draft-ietf-rtcweb-data-channel-05.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: Fri, 02 Aug 2013 13:00:44 -0000

Hi,

Section 6.4 reads "The simple protocol specified in [I-D.jesup-rtcweb-data-protocol] MUST be used to set up and manage the bidirectional data channels."



And section 4 of  'draft-ietf-rtcweb-data-protocol' reads: "Alternatively, both sides make externally agree to a set of parameters for a Channel, in which case no DATA_CHANNEL_OPEN message is required."

I guess the reference should now point to 'draft-ietf-rtcweb-data-protocol'.

Also, shouldn't it be clarified (in either 'draft-ietf-rtcweb-data-channel' or 'draft-ietf-rtcweb-data-protocol') that the optionality of this protocol is about the app invoking it (through in-band negotiation) or not (external negotiation), not about the browser implementing or not. Currently a reader could wonder whether DATA CHANNEL OPEN is always implemented by WebRTC browsers.

Jerome

________________________________________
De : rtcweb-bounces@ietf.org [rtcweb-bounces@ietf.org] de la part de internet-drafts@ietf.org [internet-drafts@ietf.org]
Date d'envoi : lundi 15 juillet 2013 21:23
À : i-d-announce@ietf.org
Cc: rtcweb@ietf.org
Objet : [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-05.txt

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           : RTCWeb Data Channels
        Author(s)       : Randell Jesup
                          Salvatore Loreto
                          Michael Tuexen
        Filename        : draft-ietf-rtcweb-data-channel-05.txt
        Pages           : 13
        Date            : 2013-07-15

Abstract:
   The Web Real-Time Communication (WebRTC) working group is charged to
   provide protocol support for direct interactive rich communication
   using audio, video, and data between two peers' web-browsers.  This
   document specifies the non-media data transport aspects of the WebRTC
   framework.  It provides an architectural overview of how the Stream
   Control Transmission Protocol (SCTP) is used in the WebRTC context as
   a generic transport service allowing Web Browser to exchange generic
   data from peer to peer.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-data-channel

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-data-channel-05


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