Re: [rtcweb] data channel protocol comments and potential agenda topic
Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> Sat, 21 July 2012 12:02 UTC
Return-Path: <stefan.lk.hakansson@ericsson.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 AB88821F865C for <rtcweb@ietfa.amsl.com>; Sat, 21 Jul 2012 05:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.019
X-Spam-Level:
X-Spam-Status: No, score=-6.019 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 7HBCJWryvOIA for <rtcweb@ietfa.amsl.com>; Sat, 21 Jul 2012 05:02:11 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id C94FB21F864B for <rtcweb@ietf.org>; Sat, 21 Jul 2012 05:02:10 -0700 (PDT)
X-AuditID: c1b4fb25-b7fb66d000003bb6-51-500a9a7c81cd
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id DB.37.15286.C7A9A005; Sat, 21 Jul 2012 14:03:08 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.264.0; Sat, 21 Jul 2012 14:03:08 +0200
Message-ID: <500A9A7B.8050400@ericsson.com>
Date: Sat, 21 Jul 2012 14:03:07 +0200
From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <03FBA798AC24E3498B74F47FD082A92F1770A313@US70UWXCHMBA04.zam.alcatel-lucent.com>
In-Reply-To: <03FBA798AC24E3498B74F47FD082A92F1770A313@US70UWXCHMBA04.zam.alcatel-lucent.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJJMWRmVeSWpSXmKPExsUyM+JvrW7NLK4AgxPPlC3W/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxvo5a1kLFrJVnF5+jb2BsZu1i5GTQ0LAROLG9kssELaYxIV7 69m6GLk4hAROMUo827+KGcJZzihx48hONpAqXgFtifMH34J1swioSnzpv80IYrMJ2Eis7Z7C BGKLCoRIrPk2hRGiXlDi5MwnYBtEBIQltr7qBasRFgiU2H32GTOILSQQI/F67hOwek6BWIlX H9qBbA4OZgF7iQdby0DCzALyEs1bZ0OV60q8e32PdQKjwCwkG2YhdMxC0rGAkXkVo3BuYmZO ermRXmpRZnJxcX6eXnHqJkZg8B3c8lt1B+OdcyKHGKU5WJTEea237vEXEkhPLEnNTk0tSC2K LyrNSS0+xMjEwSnVwCjxabaI+fLkQ8vPPXENVBR4dITvq8HXFT5q+0WTBX7sSjtlV/BY2D/Z nG95/pZj+f8tkp69XfCqWXL3lMSzbFPVPkepyLYoVFVMOTa7y//Yfb0d5Y+sHr4O9n4Uw2b0 98bzAG0u79Pq09+bnk8QO7rthNSxTZrPp082uLOxbFvur5fiv9SWcm1QYinOSDTUYi4qTgQA LxanRAwCAAA=
Subject: Re: [rtcweb] data channel protocol comments and potential agenda topic
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: Sat, 21 Jul 2012 12:02:11 -0000
On 07/19/2012 06:26 PM, Ejzak, Richard P (Richard) wrote: ... > > Why don’t we instead specify the API to allow the application to select > the SCTP transmission characteristics (including stream id, ppid, > ordered, reliable, etc.) needed per data block to be transmitted. > Alternately, the API could specify and then allow changes to these > characteristics for a channel to influence the SCTP protocol options > selected without initiating a data channel protocol negotiation or > requiring release of the channel. The current API proposal is aligned to the WebSocket API. This API is state-of-art for web developers, is gaining momentum, and designing something very different would be a mistake IMO. Anyway, the API discussion and design belongs in the webrtc WG. Stefan
- [rtcweb] data channel protocol comments and poten… Ejzak, Richard P (Richard)
- Re: [rtcweb] data channel protocol comments and p… Harald Alvestrand
- Re: [rtcweb] data channel protocol comments and p… Ejzak, Richard P (Richard)
- Re: [rtcweb] data channel protocol comments and p… Stefan Hakansson LK
- Re: [rtcweb] data channel protocol comments and p… Ejzak, Richard P (Richard)
- Re: [rtcweb] data channel protocol comments and p… Stefan Hakansson LK
- Re: [rtcweb] data channel protocol comments and p… Michael Tuexen
- Re: [rtcweb] data channel protocol comments and p… Randell Jesup
- Re: [rtcweb] data channel protocol comments and p… Ejzak, Richard P (Richard)
- Re: [rtcweb] data channel protocol comments and p… Harald Alvestrand