IETF Logo Mail Archive

Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 20 June 2013 15:57 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 496D421F9D2A for <sipcore@ietfa.amsl.com>; Thu, 20 Jun 2013 08:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.329
X-Spam-Level:
X-Spam-Status: No, score=-0.329 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.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 fXfGIeHCiK8E for <sipcore@ietfa.amsl.com>; Thu, 20 Jun 2013 08:57:51 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7BB21F9CC3 for <sipcore@ietf.org>; Thu, 20 Jun 2013 08:57:51 -0700 (PDT)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA11.westchester.pa.mail.comcast.net with comcast id qcpp1l0030cZkys5Bfxqm0; Thu, 20 Jun 2013 15:57:50 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta10.westchester.pa.mail.comcast.net with comcast id qfxq1l00g3ZTu2S3WfxqYT; Thu, 20 Jun 2013 15:57:50 +0000
Message-ID: <51C3267F.8040709@alum.mit.edu>
Date: Thu, 20 Jun 2013 11:57:51 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: sipcore@ietf.org
References: <CALiegfmtohM8Nnf34o2EqMr-jV-LaQBP7mOB5qq+7OcQO9FkSA@mail.gmail.com> <003f01ce6aaf$aabda760$0038f620$@co.in> <CALiegfn=KrEsOT+HGkCpfkS3C7Tc0Jko6kautCHk3sP8zHrzVw@mail.gmail.com> <011e01ce6c44$3c70e290$b552a7b0$@co.in> <CALiegfnPeFf751QHLoeT_jO0u1LROtvkqseE7QcAZvLgSiqVZQ@mail.gmail.com> <E54AEADE791D51469F45E7FBB964391505C964@SGSIMBX001.nsn-intra.net> <019a01ce6d24$8ee95670$acbc0350$@co.in> <CALiegfkFVJgNNLJat+3v4JqXz_=OwLPTDtR6J55dRLmiH8OgFg@mail.gmail.com>
In-Reply-To: <CALiegfkFVJgNNLJat+3v4JqXz_=OwLPTDtR6J55dRLmiH8OgFg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1371743870; bh=gYncWq5I1t7bjLbaRD4A40p6PCyUVl2F2ZbdCoHYyMw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=E/Jg0zSKty6cJqAfSXOegVG0m9dGi0ay3RQg9Dreh+0bjorhYpCMr5pjqtfwD+Tin UuE1D803TqNTEtzu0cA1wbkqUbQTTkfh0FDXm6ohwrI1KzqecK+y48kalU2+bUE6Q6 BdnGd+944IFWztIDZnjzFtqUjPd2B3ZB6KDpRTd5YXeitOpIJuZ3pqKKgCfi/O2CT9 e7Z0eP74QeGr9DNt+TzMI614wYkTNss7S6ffABOcQyuiho1BAylGilUd3fFUHXUYrL S1o2SMvuV/NENxhGtZb6aDphcV8ipYT/Gg5tOPTbrftUgTVVY2CaPfRSWD4JHh5BDs 5TivCQyCRsgYQ==
Subject: Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 15:57:57 -0000

On 6/19/13 6:05 PM, Iñaki Baz Castillo wrote:
> 2013/6/19 Parthasarathi R <partha@parthasarathi.co.in>:
>>
>> Just adding to Ranjit mentioned. The text similar to the following has to be added. "Record-route header MUST be added by SIP WebSocket Server in case WebSocket is the only supported SIP transport between SIP WebSocket client & server and SIP WebSocket server acts as SIP proxy"
>
> That is just true in case the client is a web browser (a SIP WS Client
> but not a SIP WS Server so it can not receive incoming WS
> connections). So the text would be:
>
> "Record-route header MUST be added by SIP WebSocket Server in case
> WebSocket is the only supported SIP transport between client and
> server, the server acts as SIP proxy, and the client is a SIP
> WebSocket Client (but not a SIP WebSocket Server so it can not accept
> incoming WebSocket connections)."

How will the server know that the client is not capable of being a 
WebSocket Server?

I guess in many cases it might be able to know that because the client 
is a browser being controlled by scripting from the server. But in other 
cases ISTM that it just won't know.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email