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

Saúl Ibarra Corretgé <> Fri, 16 September 2011 06:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4807921F8BBC for <>; Thu, 15 Sep 2011 23:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.628
X-Spam-Status: No, score=-1.628 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JMeSqcbg8zwb for <>; Thu, 15 Sep 2011 23:48:51 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B6E7A21F8BAA for <>; Thu, 15 Sep 2011 23:48:51 -0700 (PDT)
Received: by (Postfix, from userid 5001) id 96C0DB01B8; Fri, 16 Sep 2011 08:51:04 +0200 (CEST)
Received: from [] ( []) by (Postfix) with ESMTPSA id 01ABFB019A; Fri, 16 Sep 2011 08:51:03 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <>
In-Reply-To: <>
Date: Fri, 16 Sep 2011 08:51:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <>
To: Roman Shpount <>
X-Mailer: Apple Mail (2.1084)
Cc: Randell Jesup <>,
Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 16 Sep 2011 06:48:52 -0000


On Sep 15, 2011, at 7:52 PM, Roman Shpount wrote:

> I don't think this is a problem for RTC web to resolve. This is the same problem that someone building an IM or email client for a web browser will need to deal with. Some type of push notification framework is needed to implement this and it might be something for W3C to standardize as a solution for this problem. 

I fully agree here. AFAIK this group is not about getting applications to run smoothly on mobile platforms, it's about realtime communications within a browser. Having a JS SIP client on a browser might be OK for a desktop, but mobiles will always need native apps because they can be optimized for specific hardware and give a better user experience IMHO. That being said, I don't think mobile battery consumption is important in any way when discussing SIP over WebSocket.


Saúl Ibarra Corretgé
AG Projects