Re: [rtcweb] Data Channel Protocol: Data before DATA_CHANNEL_ACK
Christer Holmberg <christer.holmberg@ericsson.com> Mon, 10 February 2014 20:18 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 EBC401A06AF for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 12:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_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 cRk5QR4PuVJ4 for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 12:18:07 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 52E801A06F3 for <rtcweb@ietf.org>; Mon, 10 Feb 2014 12:18:07 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-8d-52f933fea56e
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 4E.1B.04249.EF339F25; Mon, 10 Feb 2014 21:18:06 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0387.000; Mon, 10 Feb 2014 21:18:06 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Peter Thatcher <pthatcher@google.com>
Thread-Topic: [rtcweb] Data Channel Protocol: Data before DATA_CHANNEL_ACK
Thread-Index: Ac8mSYxkYxWKLCWnTpOI4SR9Ce/EOgAOuZcAAAUfzMD///P/AP//7Pxw
Date: Mon, 10 Feb 2014 20:18:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D167D92@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D166D41@ESESSMB209.ericsson.se> <CAJrXDUHBBt6L7tp4Ck426xQEkAQEmOnscmu2mBFUGR8YVHqoaw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D167CCE@ESESSMB209.ericsson.se> <CAJrXDUHVkcKWwmYmpZSyfaikq2shQwWUmOiBDPN=NPQJigDAnw@mail.gmail.com>
In-Reply-To: <CAJrXDUHVkcKWwmYmpZSyfaikq2shQwWUmOiBDPN=NPQJigDAnw@mail.gmail.com>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvje4/459BBre+aVpcW/6a1WLtv3Z2 ByaPBZtKPZYs+ckUwBTFZZOSmpNZllqkb5fAlTFro1jBB9aKwz+VGhjvsHYxcnJICJhIdD6e yQ5hi0lcuLeerYuRi0NI4AijxKxzC6GcxYwS///cY+li5OBgE7CQ6P6nDdIgIqApMXlyM9gg ZgF1iTuLz4ENEhbwlNjRPpUdosZL4tj7dkYI203izeUHLCA2i4CqxMMLC8FqeAV8Jea1H2eC 2DWfSWL1h81sIAlOgUCJwy+WMYPYjEDXfT+1hglimbjEh4PXmSGuFpBYsuc8lC0q8fLxP6jP lCTWHt4OdjMz0KHrd+lDtCpKTOl+CLVXUOLkzCcsExjFZiGZOguhYxaSjllIOhYwsqxi5ChO LU7KTTcy2MQIjI6DW35b7GC8/NfmEKM0B4uSOO/Ht85BQgLpiSWp2ampBalF8UWlOanFhxiZ ODilGhgz3vz5svZCUdrHZGHbuSfu+hlf3uh74W+q/qHZE+5qlqfnz3dq4z9nt36msM3cM+VZ h+922pTKthwSSShP6MratN9915I3a/VzknwWL7i94oTawT9sYtxC9mVdx5+f2PejW/uTlrgB t2dxf0e/fbz0SvuIbzNl7rqlthXJcvLk35wQeH3RdRklluKMREMt5qLiRACucUOuXAIAAA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [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 20:18:09 -0000
>I think what is already in the standard is sufficient for your use case. You just need to add a little application-specific signalling. I don't think the in-band signalling is the right place to put things like this. If it is sufficient to use in-band signalling to say ”I would like to send you this data”, I think it is equally sufficient to use in-band signaling to reply “No, I don’t want that data”... Anyway, if people don't think it's needed, then I guess one can simply reset the stream. Regards, Christer
- [rtcweb] Data Channel Protocol: Data before DATA_… Christer Holmberg
- Re: [rtcweb] Data Channel Protocol: Data before D… Peter Thatcher
- Re: [rtcweb] Data Channel Protocol: Data before D… Christer Holmberg
- Re: [rtcweb] Data Channel Protocol: Data before D… Peter Thatcher
- Re: [rtcweb] Data Channel Protocol: Data before D… Christer Holmberg
- Re: [rtcweb] Data Channel Protocol: Data before D… Michael Tuexen
- Re: [rtcweb] Data Channel Protocol: Data before D… Randell Jesup