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

"Parthasarathi R" <partha@parthasarathi.co.in> Wed, 19 June 2013 19:38 UTC

Return-Path: <partha@parthasarathi.co.in>
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 3ED1321F9B85 for <sipcore@ietfa.amsl.com>; Wed, 19 Jun 2013 12:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level:
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 fD-rpgH4HUGm for <sipcore@ietfa.amsl.com>; Wed, 19 Jun 2013 12:38:36 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us1.mailhostbox.com [70.87.28.138]) by ietfa.amsl.com (Postfix) with ESMTP id 6E61221F9DEF for <sipcore@ietf.org>; Wed, 19 Jun 2013 12:38:32 -0700 (PDT)
Received: from userPC (unknown [122.179.32.11]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id BCEE0190830A; Wed, 19 Jun 2013 19:38:21 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1371670705; bh=i0vASyQqTY/CxB/Gr4egaSQIN5Nqsd6/OVRW9t91sNs=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=IIVs/ZSlkSxcnBILO6JgJ6HjtpWLD2YqDhMB0JL6+l6FMrNQBSWDrH4qMixz8lpZn bSGXJl2oxNwzcJZCEul5TdN4XH/CY0qGj12ICIw3knMZjrIxQhUOG9YYMqzMd4UKZV UxSJe1av472+Gpal9eMWzpPRLsICZzCjiUf0wbRA=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: "'Avasarala, Ranjit (NSN - IN/Bangalore)'" <ranjit.avasarala@nsn.com>, 'ext Iñaki Baz Castillo' <ibc@aliax.net>
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>
In-Reply-To: <E54AEADE791D51469F45E7FBB964391505C964@SGSIMBX001.nsn-intra.net>
Date: Thu, 20 Jun 2013 01:08:15 +0530
Message-ID: <019a01ce6d24$8ee95670$acbc0350$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHObHcliKGMQna3kEGI3rQZiy9t15k8h92wgADmUWA=
Content-Language: en-us
X-CTCH-RefID: str=0001.0A0C0206.51C208B1.00AF, ss=2, re=0.000, recu=0.000, reip=0.000, cl=2, cld=1, fgs=64
X-CTCH-VOD: Unknown
X-CTCH-Spam: Suspect
X-CTCH-Score: 0.000
X-CTCH-Rules:
X-CTCH-Flags: 64
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.138
Cc: "'SIPCORE (Session Initiation Protocol Core) WG'" <sipcore@ietf.org>
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: Wed, 19 Jun 2013 19:38:40 -0000

Hi Inaki,

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" 

Thanks
Partha


> -----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On
> Behalf Of Avasarala, Ranjit (NSN - IN/Bangalore)
> Sent: Wednesday, June 19, 2013 11:24 AM
> To: ext Iñaki Baz Castillo; Parthasarathi R
> Cc: SIPCORE (Session Initiation Protocol Core) WG
> Subject: Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-
> 09
> 
> Hi Inaki
> 
> Usually contact header contains the address on which the callee can
> reach caller. But when a SIP message is sent in websocket, what is the
> use of putting contact header?
> 
> Should Contact header contain browser's address, since SIP UA is anyway
> part of browser and the callee cannot anyway reach SIP UA directly.
> 
> So I think there needs to be text in the draft explaining this
> behavior.
> 
> Regards
> Ranjit
> 
> 
> 
> 
> -----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On
> Behalf Of ext Iñaki Baz Castillo
> Sent: Wednesday, June 19, 2013 4:26 AM
> To: Parthasarathi R
> Cc: SIPCORE (Session Initiation Protocol Core) WG
> Subject: Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-
> 09
> 
> 2013/6/18 Parthasarathi R <partha@parthasarathi.co.in>:
> > I think that it is required for SIP over WebSocket to explain the
> usage of contact header field with example and normative statement.
> 
> Honestly I have no idea of what you mean.
> draft-ietf-sipcore-sip-websocket must explain how to use the SIP
> Contact header?
> 
> Sorry but I don't understand your concern. Could you please describe it
> again?
> 
> Thanks a lot.
> 
> 
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore