[rtcweb] Future requirement: RTC-Web apps must work through interface switching

<Markus.Isomaki@nokia.com> Mon, 03 October 2011 11:56 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 09A9D21F8753 for <rtcweb@ietfa.amsl.com>; Mon, 3 Oct 2011 04:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DiF5zpjYnsYR for <rtcweb@ietfa.amsl.com>; Mon, 3 Oct 2011 04:56:06 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com []) by ietfa.amsl.com (Postfix) with ESMTP id 37A3321F86A5 for <rtcweb@ietf.org>; Mon, 3 Oct 2011 04:56:05 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com []) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p93BwQh5022128 for <rtcweb@ietf.org>; Mon, 3 Oct 2011 14:59:06 +0300
Received: from smtp.mgd.nokia.com ([]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 3 Oct 2011 14:58:30 +0300
Received: from 008-AM1MMR1-001.mgdnok.nokia.com ( by NOK-am1MHUB-02.mgdnok.nokia.com ( with Microsoft SMTP Server (TLS) id; Mon, 3 Oct 2011 13:58:29 +0200
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([]) by 008-AM1MMR1-001.mgdnok.nokia.com ([]) with mapi id 14.01.0339.002; Mon, 3 Oct 2011 13:58:29 +0200
From: Markus.Isomaki@nokia.com
To: rtcweb@ietf.org
Thread-Topic: Future requirement: RTC-Web apps must work through interface switching
Thread-Index: AcyBw8LOCbj0Q27JT3eGKgpYq050bw==
Date: Mon, 03 Oct 2011 11:58:28 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620D3782@008-AM1MPN1-043.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Oct 2011 11:58:30.0330 (UTC) FILETIME=[C49051A0:01CC81C3]
X-Nokia-AV: Clean
Subject: [rtcweb] Future requirement: RTC-Web apps must work through interface switching
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, 03 Oct 2011 11:56:07 -0000

Hi all,

There is one important requirement, which may not be critical today, but will most likely be in the future.

We can assume RTC-Web to be supported in devices like tablets, pads or smartphones, that people carry around. We can also assume that when such devices are carried around, their point of attachement to the Internet will change, even so that the type of access network will change, typically between something like HSPA/LTE and Wi-Fi. Today this will always mean a change of IP address as well. In the future we may have technologies such as (Proxy)Mobile IP in use that will provide IP address preservation, but we can't really count on that.

How does this relate to RTC-Web? Interface switching usually happens at the discretion of the OS or some kind of connection manager. The browser or the web application environment has no control over it. At best it, or the JS application running within, can get some kind of signal of such event happening. For TCP-based client-server things (HTTP, Websocket) it is possible to react to this by re-establishing the lost TCP connections and state on top of them. This is indeed what many (native) apps are able to do today. There can be some smarter ways in the pipeline as well, such as multipath TCP, which would make the process of "transitioning" a TCP connection from one interface/IP to another potentially transparent to the application. But with peer-to-peer and interactive real-time, things get more complicated. It may of course be that the switching happens due to a sudden loss of coverage and is so slow, that voice or video calls are broken anyway. However, in many cases the old interface can be up while the new one is being established, and in principle the total loss of connectivity can be avoided. In such scenarios it would be realistically possible to update the ongoing real-time sessions to a new IP address and port, if there were some kind of end-to-end or server-assisted mechanism for it. Even a cut of 1-2 seconds would not be as bad as a total loss of the session.

What does this mean in terms of requirements?
- The first-order requirement is that the browser and/or the JS app, whoever needs to act, has to be able to get events of interface switching in the same way as native apps can. If it were only the browser who was required to get them, we could set standards aside, and declare that the browser does this as any other app. But if it is the JS app that needs to do something, then we may need something new as a JS API. I have no clue at the moment if the JS apps can learn about this kind of events. And this is clearly not a RTC-Web specific requirement, but a generic one. I do know that browsers or HTTP libraries can re-send requests etc. based on IP address change, but I don't know what a JS Websocket client can do, if anything.
- The second requirement is that the media related APIs and transport protocols (RTP) have to be flexible enough, that they can at least be extended to work so that they do not assume that the session is forever bound to a certain IP address/port in either end. How this affects the system depends on what is actually standardized, for instance if the SDP offer/answer model is included or not. But on the generic level it could be something like this:
	- If the browser/JS app receives signaling/offer from its peer that peer's RTP/UDP IP address/port has changed, it has to be able to set these through the media API and re-run STUN checks or whatever is required at that point. This has to be work so that the media session can be otherwise continued, after the process is completed.
	- If the browser/JS app receives an event that its own IP address/port has changed (or is about to change), it has to be able to re-initialize the RTP/UDP accordingly, re-establish its "signaling connection and state" with its webserver, notify the peer about the change, and re-run STUN checks etc. as needed.

This sounds quite complicated so it may be that we don't want to add this as a Day 1 requirement for RTC-Web. But I believe we should try to design the APIs and protocols in such a way that this kind of thing can be added later on. There could be other ways too, like MPRTP (http://datatracker.ietf.org/doc/draft-singh-avtcore-mprtp/), we could look at. 

I suppose the less we standardize about the signaling and offer/answer, the easier it might be to support these kinds of things as add-on. But whatever we standardize, please keep the interface and IP address change in mind. The outcome could be that we declare that transport (MPTCP, MPRTP) has to deal with it, but eventually I think this will have to work one way or the other.