IETF Logo Mail Archive

Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)

<Markus.Isomaki@nokia.com> Thu, 15 September 2011 19:22 UTC

Return-Path: <Markus.Isomaki@nokia.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 7DB6721F8BFE for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 12:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAz0PLals10T for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 12:22:49 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id C6B0921F8BF9 for <rtcweb@ietf.org>; Thu, 15 Sep 2011 12:22:48 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8FJOxEq008175; Thu, 15 Sep 2011 22:25:00 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 15 Sep 2011 22:24:55 +0300
Received: from 008-AM1MMR1-003.mgdnok.nokia.com (65.54.30.58) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 15 Sep 2011 21:24:54 +0200
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.204]) by 008-AM1MMR1-003.mgdnok.nokia.com ([65.54.30.58]) with mapi id 14.01.0323.007; Thu, 15 Sep 2011 21:24:53 +0200
From: Markus.Isomaki@nokia.com
To: randell-ietf@jesup.org, rtcweb@ietf.org
Thread-Topic: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
Thread-Index: AQHMclbXOUIKXflnkES/7qO+qcO8OJVOFtUAgAB+RoCAADJxMP//5MgAgAAEU4CAACIG8A==
Date: Thu, 15 Sep 2011 19:24:53 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620B3B02@008-AM1MPN1-043.mgdnok.nokia.com>
References: <CABw3bnO+85i-TtuqS+P4n+rYgyxyoASc8HXpADhy4QPTC0_szA@mail.gmail.com> <6F469757-6B5C-4DC9-BC34-026F34C7E508@phonefromhere.com> <CAD5OKxvCSJWS+F72P_WOFapmtffkLCSSe3A-rDEUOhNjWcoh4A@mail.gmail.com> <E44893DD4E290745BB608EB23FDDB7620B39D8@008-AM1MPN1-043.mgdnok.nokia.com> <CAD5OKxtt9phWr9Vrn5J1STxA9airR8g-tHMnddFP=QwrTHuPcA@mail.gmail.com> <4E724E25.1000204@jesup.org>
In-Reply-To: <4E724E25.1000204@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [88.114.26.217]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Sep 2011 19:24:55.0110 (UTC) FILETIME=[2619E660:01CC73DD]
X-Nokia-AV: Clean
Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
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, 15 Sep 2011 19:22:49 -0000

SIP over UDP is used by mobile operators themselves, as they are in control of the access infrastructure, and can make special provisions for their own services. But if you try to run SIP over UDP over mobile networks to any independent ("OTT") Internet service, it is likely to not work that well, due to battery consumption. Even with public addresses, in many mobile networks firewalls drop UDP flow state after 30 seconds.

TCP usually survives longer, in most networks actually more than 15 minutes. Unfortunately a small percentage of networks breaks even TCP in less than 5 minutes. (Several companies, including Nokia, have concrete stats from all over the globe.)

So all in all I'm not sure that HTTP or websockets are in a worse position than pure SIP. The main differences are that the Javascript app may not have access to some helpers the more native mobile platform may offer.

Markus


>-----Original Message-----
>From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf
>Of ext Randell Jesup
>Sent: 15 September, 2011 22:13
>To: rtcweb@ietf.org
>Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport
>for Session Initiation Protocol (SIP)
>
>On 9/15/2011 11:57 AM, Roman Shpount wrote:
>> Actually SIP over UDP is what is typically used for mobile apps now.
>> If you are doing SIP from the public IP, you do not need to maintain
>> the connection even if TCP/TLS is used.
>
>Markus had a point: SIP over UDP requires keepalives if it's behind a NAT as
>well.  So maybe it's not such a big difference, depending on the keepalive
>rates needed (and for UDP circa 30 sec is typical).
>
>--
>Randell Jesup
>randell-ietf@jesup.org
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email