IETF Logo Mail Archive

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

"Avasarala, Ranjit (NSN - IN/Bangalore)" <ranjit.avasarala@nsn.com> Wed, 19 June 2013 05:54 UTC

Return-Path: <ranjit.avasarala@nsn.com>
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 2926921F9D86 for <sipcore@ietfa.amsl.com>; Tue, 18 Jun 2013 22:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 81SAzspl0gb6 for <sipcore@ietfa.amsl.com>; Tue, 18 Jun 2013 22:54:39 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 9154521F9D7D for <sipcore@ietf.org>; Tue, 18 Jun 2013 22:54:39 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r5J5sbKs017500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Jun 2013 07:54:37 +0200
Received: from SGSIHTC002.nsn-intra.net ([10.159.225.19]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r5J5qKl8000812 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Jun 2013 07:54:33 +0200
Received: from SGSIHTC003.nsn-intra.net (10.159.225.20) by SGSIHTC002.nsn-intra.net (10.159.225.19) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 19 Jun 2013 13:53:41 +0800
Received: from SGSIMBX001.nsn-intra.net ([169.254.1.71]) by SGSIHTC003.nsn-intra.net ([10.159.225.20]) with mapi id 14.03.0123.003; Wed, 19 Jun 2013 13:53:41 +0800
From: "Avasarala, Ranjit (NSN - IN/Bangalore)" <ranjit.avasarala@nsn.com>
To: ext Iñaki Baz Castillo <ibc@aliax.net>, Parthasarathi R <partha@parthasarathi.co.in>
Thread-Topic: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09
Thread-Index: AQHObHcliKGMQna3kEGI3rQZiy9t15k8h92w
Date: Wed, 19 Jun 2013 05:53:41 +0000
Message-ID: <E54AEADE791D51469F45E7FBB964391505C964@SGSIMBX001.nsn-intra.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>
In-Reply-To: <CALiegfnPeFf751QHLoeT_jO0u1LROtvkqseE7QcAZvLgSiqVZQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.225.114]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1856
X-purgate-ID: 151667::1371621277-00002EAE-826247ED/0-0/0-0
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 05:54:44 -0000

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

v2.23.0 | Report a Bug | By Email