Re: [rtcweb] Data channel comments and questions

Salvatore Loreto <salvatore.loreto@ericsson.com> Mon, 02 April 2012 18:33 UTC

Return-Path: <salvatore.loreto@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 4948B21F85CE for <rtcweb@ietfa.amsl.com>; Mon, 2 Apr 2012 11:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.749
X-Spam-Level:
X-Spam-Status: No, score=-105.749 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_BACKHAIR_24=1, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 DOCR4O2n7WCZ for <rtcweb@ietfa.amsl.com>; Mon, 2 Apr 2012 11:33:33 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 420C821F85CC for <rtcweb@ietf.org>; Mon, 2 Apr 2012 11:33:33 -0700 (PDT)
X-AuditID: c1b4fb2d-b7b76ae0000063d8-e6-4f79f0fb5153
Authentication-Results: mailgw1.ericsson.se x-tls.subject="/CN=esessmw0184"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0184", Issuer "esessmw0184" (not verified)) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 9F.08.25560.BF0F97F4; Mon, 2 Apr 2012 20:33:32 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.213.0; Mon, 2 Apr 2012 20:33:31 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 4476D2323 for <rtcweb@ietf.org>; Mon, 2 Apr 2012 21:33:31 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 5A61B52679 for <rtcweb@ietf.org>; Mon, 2 Apr 2012 21:33:31 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 0F913517DB for <rtcweb@ietf.org>; Mon, 2 Apr 2012 21:33:31 +0300 (EEST)
Message-ID: <4F79F0FA.80604@ericsson.com>
Date: Mon, 02 Apr 2012 21:33:30 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <E44893DD4E290745BB608EB23FDDB7621B12D4@008-AM1MPN1-042.mgdnok.nokia.com> <4F760634.207@ericsson.com> <4F761AFC.5090503@jesup.org>
In-Reply-To: <4F761AFC.5090503@jesup.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [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: Mon, 02 Apr 2012 18:33:34 -0000

On 3/30/12 11:43 PM, Randell Jesup wrote:
>>> >>  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.
>> >  that is exact the proposal in the data-channel draft.
>> >  Anyway you can not use multihoming because of the fact that SCTP runs on
>> >  top of DTLS
> Correct, though there was some in-room discussion of running it over
> multiple DTLS connections to support smooth handoff across interfaces
> (think mobile and 4g<->WiFi switchover).
definitely, that is also something else worth to investigate more deeply


-- 
Salvatore Loreto, PhD
www.sloreto.com