IETF Logo Mail Archive

[rtcweb] Data Channel Protocol: Data before DATA_CHANNEL_ACK

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 10 February 2014 10:20 UTC

Return-Path: <christer.holmberg@ericsson.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 4E0261A07E8 for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 02:20:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, 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 sXvFHvzVqNpl for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 02:20:03 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 275F01A07E7 for <rtcweb@ietf.org>; Mon, 10 Feb 2014 02:20:02 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-db-52f8a7d29068
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id FA.2C.04853.2D7A8F25; Mon, 10 Feb 2014 11:20:02 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0387.000; Mon, 10 Feb 2014 11:20:01 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Data Channel Protocol: Data before DATA_CHANNEL_ACK
Thread-Index: Ac8mSYxkYxWKLCWnTpOI4SR9Ce/EOg==
Date: Mon, 10 Feb 2014 10:20:02 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D166D41@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrALMWRmVeSWpSXmKPExsUyM+Jvje6l5T+CDG7+V7dY+6+d3YHRY8mS n0wBjFFcNimpOZllqUX6dglcGQ9XT2IpOMtSsbFnO3sD4w3mLkZODgkBE4k7329B2WISF+6t Z+ti5OIQEjjBKNH5q5cZwlnMKHHm4QqgDAcHm4CFRPc/bZAGEQF1icsPL7CD2MICNhInzh5n gog7SvS8OcwCYetJbN+1D6yGRUBV4lnTVbBlvAK+Etf+bAGrYQRa/P3UGrBeZgFxiVtP5jNB HCQgsWTPeajjRCVePv7HCmErSuw8284MUa8jsWD3JzYIW1ti2cLXUPMFJU7OfMIygVF4FpKx s5C0zELSMgtJywJGllWMksWpxcW56UYGernpuSV6qUWZycXF+Xl6xambGIGhfnDLb6MdjCf3 2B9ilOZgURLnvc5aEyQkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMZTv2KQvF8V+K/POnHB+ 0/dVsjyq5rPDIo8mZTbsP1+9QvHRz7U1m27tXqN9v51l8ToGzrP5lQqf32zeKaocW1km+e/K VAEPidfqIXPMPUQL1f89Xt42zX+jq9H+Fex73jxbHDQvfebM9srU9WLymROt3Kep1UiWJLA+ qrRvUeD6cMjObzHnNyWW4oxEQy3mouJEAMWLJT9DAgAA
Subject: [rtcweb] Data Channel Protocol: Data before DATA_CHANNEL_ACK
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: Mon, 10 Feb 2014 10:20:05 -0000

Hi,

As is defined in the data channel protocol, an entity can send data once DATA_CHANNEL_OPEN has been sent, before the associated DATA_CHANNEL_ACK is received.

What is the reason for allowing data to be sent before DATA_CHANNEL_ACK? The sender may not even know (depends on whatever external negotiation mechanisms are used) whether the remote peer supports the protocol to begin with.

It think it would be good to allow the remote peer to accept (DATA_CHANNEL_ACK) or reject (stream reset) the DATA_CHANNEL_OPEN before data is sent.

Regards,

Christer

v2.23.0 | Report a Bug | By Email