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

From: "MARCON, JEROME (JEROME)" <[email-masked]>
Date: Fri, 2 Aug 2013 12:59:48 +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 : [email-masked] [[email-masked]] de la part de [email-masked] [[email-masked]]
Date d'envoi : lundi 15 juillet 2013 21:23
À : [email-masked]
Cc: [email-masked]
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
[email-masked]
https://www.ietf.org/mailman/listinfo/rtcweb