[rtcweb] Data channel comments and questions

<Markus.Isomaki@nokia.com> Thu, 29 March 2012 20:23 UTC

Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6B9EE21E80BE for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 13:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.099
X-Spam-Status: No, score=-8.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id k2f+AIz7QpvK for <rtcweb@ietfa.amsl.com>; Thu, 29 Mar 2012 13:23:38 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com []) by ietfa.amsl.com (Postfix) with ESMTP id C7DE121E805F for <rtcweb@ietf.org>; Thu, 29 Mar 2012 13:23:36 -0700 (PDT)
Received: from vaebh102.NOE.Nokia.com (vaebh102.europe.nokia.com []) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2TKNU55023358 for <rtcweb@ietf.org>; Thu, 29 Mar 2012 23:23:31 +0300
Received: from smtp.mgd.nokia.com ([]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 29 Mar 2012 23:23:29 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([]) by 008-AM1MMR1-011.mgdnok.nokia.com ([]) with mapi id 14.01.0355.003; Thu, 29 Mar 2012 22:23:29 +0200
From: Markus.Isomaki@nokia.com
To: rtcweb@ietf.org
Thread-Topic: Data channel comments and questions
Thread-Index: Ac0N59ezjOXJpyb5S8y3N1bZlLMXyA==
Date: Thu, 29 Mar 2012 20:23:28 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7621B12D4@008-AM1MPN1-042.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 29 Mar 2012 20:23:29.0863 (UTC) FILETIME=[CE05A570:01CD0DE9]
X-Nokia-AV: Clean
Subject: [rtcweb] Data channel comments and questions
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: Thu, 29 Mar 2012 20:23:38 -0000


Some comments on the data channel proposal:

1. Congestion control: If no real-time sessions are on, TCP-style loss-driven congestion control is fine. However, if voice/video session is up, such congestion control would be disasterous to the real-time traffic quality if sendind or receiving more than a slight amount of data. Especially in mobile access networks the user would bloat his/her own buffers very easily. In that case, some less-than-best-effort congestion control algorithm รก la LEDBAT would be required. It would be best to make this a MUST requirement on implementations, otherwise we will get a lot of crappy video even if the codec was better than H.261 :-)

2. Multihoming and interface switching: I don't suggest going for the multipath support on the SCTP level. I think it would be best to deal with this through ICE in the same way as for RTP, i.e. adding and removing candidates as interfaces become available or go. Or let the application handle it by creating a new data channel and continue from the breakpoint. The most important requirement is that the application gets notified about these changes downstrairs so it can act. 

3. HTTP tunneling: In practice we are going to need HTTP tunneling last-resort option for the data channel as well. If doing so, what will the protocol stack look like? Is it SCTP/DTLS/UDP/HTTP/TLS/TCP? Or can we collapse some of these layers. I think we'd better.