Re: [rtcweb] Open data channel issues
Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 26 February 2014 07:50 UTC
Return-Path: <magnus.westerlund@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 1DA4C1A0045 for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 23:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 dmpYorbHVkco for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 23:50:32 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 4948C1A0041 for <rtcweb@ietf.org>; Tue, 25 Feb 2014 23:50:31 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-6a-530d9cc5b2a3
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id A9.73.10875.5CC9D035; Wed, 26 Feb 2014 08:50:29 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.23) with Microsoft SMTP Server id 14.2.347.0; Wed, 26 Feb 2014 08:50:29 +0100
Message-ID: <530D9CC5.5080508@ericsson.com>
Date: Wed, 26 Feb 2014 08:50:29 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <31B9253D-E826-4D07-A8A1-1B062B50F163@lurchi.franken.de>
In-Reply-To: <31B9253D-E826-4D07-A8A1-1B062B50F163@lurchi.franken.de>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphluLIzCtJLcpLzFFi42KZGfG3RvfoHN5gg/4HNhYXm5YwWqz9187u wOSxZMlPJo8NLTuYApiiuGxSUnMyy1KL9O0SuDJm/FjAWLBVqGJ+7we2BsYTfF2MnBwSAiYS L17MZIOwxSQu3FsPZHNxCAkcYpTY//AVI4SznFHi4MVbjCBVvALaEvdOHgbrYBFQlfj+YAYr iM0mYCFx80cjWFxUIFhi54HfUPWCEidnPmEBsUUEYiQOXHoOVi8soCfxsWU7O4gtJOAi0Xew F8zmFHCVWDl/DlANB9BF4hI9jUEgYWag8ilXWxghbHmJ5q2zmSFatSUamjpYJzAKzkKybRaS lllIWhYwMq9iZM9NzMxJLzfcxAgMyYNbfuvuYDx1TuQQozQHi5I474e3zkFCAumJJanZqakF qUXxRaU5qcWHGJk4OKUaGGdukNtoX9rTqyZx+MhUldAldbuOPCu59efXV6OlKiq3bh/csO0D r5eI/heDiTPfr2jYyqHPqOL4xuDWTZ76i3cmvXjR+Ijl+p7G/BWz/k3u0e44kxLQ9O3F5aaQ i8e4PhXo3zhm1P7oyUljjvBre3LvL1nicbth6s9G5uS9ssprfwcFfThzTeuJEktxRqKhFnNR cSIAqvjFmxcCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/V5fxBZ7OUhsJTPk-1xHsRbUtS-s
Subject: Re: [rtcweb] Open data channel issues
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: Wed, 26 Feb 2014 07:50:37 -0000
Thanks Michael, WG, please consider these open issues and try to form your own position on them. They are intended to be discussed at the meeting. If you have proposals on how to resolve them or other input you are very welcome to provide that on the list. Thanks Magnus On 2014-02-26 00:44, Michael Tuexen wrote: > Dear all, > > Magnus asked me to send a list of open issues regarding data channels > to the list. Here is my current list: > > > * Priority > The W3C hasn't defined it yet. Neither for the (S)RTP media nor for the > data channels. We agreed on using a non strict policy for the data channels > (some sort of wighted fair queueing). That is all. > > * Protocol > It seems not to be clear what needs to be provided when registering a > (sub)-protocol at IANA. And the name of the registry is unclear... > > * SCTP parameters. > There was discussed the issue how to set SCTP parameters, especially path.max.retrans > and association.max.retrans. Also HB.Interval might be of interest. > RFC 4060 recommends path.max.retrans=5, association.max.retrans=10, but has multihoming > in mind. To avoid the dormant state, path.max.retrans = association.max.retrans should be used. > I would suggest 10 for this value. Should HEARTBEATs be disabled? > > * U-C 7: Proxy browsing > > * Alternate CC for SCTP > Currently there is only the standard CC. However, in some places negotiation of CC is > mentioned. > > I'm currently going through the backlog of comments regarding the data channels > ID and I'll try to address the issues. If I find other issues, I send an update > to the above list. > > Best regards > Michael > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > > -- Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Magnus Westerlund
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Paul Kyzivat
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Paul Kyzivat
- Re: [rtcweb] Open data channel issues Christer Holmberg
- Re: [rtcweb] Open data channel issues Paul Kyzivat
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Stefan Håkansson LK
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Karl Stahl
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] Open data channel issues Makaraju, Maridi Raju (Raju)