Re: [sipcore] Questions on location conveyance and dereferencing

"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Mon, 16 August 2010 06:26 UTC

Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA3473A6819 for <sipcore@core3.amsl.com>; Sun, 15 Aug 2010 23:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level:
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2C8rfMIhT3b for <sipcore@core3.amsl.com>; Sun, 15 Aug 2010 23:26:28 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 37CB53A68B8 for <sipcore@ietf.org>; Sun, 15 Aug 2010 23:26:27 -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 o7G6QwJ2026377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 16 Aug 2010 08:26:58 +0200
Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o7G6QvHO000871; Mon, 16 Aug 2010 08:26:58 +0200
Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 16 Aug 2010 08:26:57 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 16 Aug 2010 09:26:57 +0300
Message-ID: <3D3C75174CB95F42AD6BCC56E5555B4502E9C319@FIESEXC015.nsn-intra.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA01C46B5792@MCHP058A.global-ad.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] Questions on location conveyance and dereferencing
Thread-Index: Acs591dqg6OyEIxSSSGOaw4Ja2Tz5gAALtKVADHnkYAAAE629wAAG7aQAADXHJAAAJUbYwAAUJuAAABop6EAAHVqQAAAoHrwAAE+BsAAAt1BgAAt+KYA
References: <A444A0F8084434499206E78C106220CA01C46B4FF1@MCHP058A.global-ad.net><5A55A45AE77F5941B18E5457ECAC81880120EB7D94A3@SISPE7MB1.commscope.com>, <A444A0F8084434499206E78C106220CA01C46B5547@MCHP058A.global-ad.net> <5A55A45AE77F5941B18E5457ECAC81880120EB7D94AA@SISPE7MB1.commscope.com> <3D3C75174CB95F42AD6BCC56E5555B4502E9BD6F@FIESEXC015.nsn-intra.net>, <A444A0F8084434499206E78C106220CA01C46B559B@MCHP058A.global-ad.net> <5A55A45AE77F5941B18E5457ECAC81880120EB7D94AB@SISPE7MB1.commscope.com>, <A444A0F8084434499206E78C106220CA01C46B55B5@MCHP058A.global-ad.net> <5A55A45AE77F5941B18E5457ECAC81880120EB7D94AC@SISPE7MB1.commscope.com> <3D3C75174CB95F42AD6BCC56E5555B4502E9BE56@FIESEXC015.nsn-intra.net> <A444A0F8084434499206E78C106220CA01C46B55F1@MCHP058A.global-ad.net> <3D3C75174CB95F42AD6BCC56E5555B4502E9BEBD@FIESEXC015.nsn-intra.net> <A444A0F8084434499206E78C106220CA01C46B5792@MCHP058A.global-ad.net>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Elwell, John" <john.elwell@siemens-enterprise.com>, "ext Winterbottom, James" <James.Winterbottom@andrew.com>, <sipcore@ietf.org>
X-OriginalArrivalTime: 16 Aug 2010 06:26:57.0743 (UTC) FILETIME=[070DADF0:01CB3D0C]
Subject: Re: [sipcore] Questions on location conveyance and dereferencing
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 16 Aug 2010 06:26:29 -0000

Hi John, 
 

> > In your enterprise LIS for emergency services you will most 
> > likely want
> > to figure out who is going to consume that reference. Quite 
> likely the
> > PSAP will consume the reference. If so, you better talk to the PSAP
> > responsible for that specific area. 
> [JRE] Quite so, except is it likely my VoIP service provider 
> might also want to inspect the location, to confirm correct 
> routing? Then depending on which SP I choose to route that 
> particular call through, they might support different URI 
> schemes? It seems to be a mess not having a MUST implement scheme.

I understand the theoretical concern. 
I have no objections against a mandatory to implement HTTP-based
dereferencing mechanism. 


> > XMPP does not provide equivalent functionality of SIP location
> > conveyance. 
> > So, another non-issue. 
> [JRE] That was not the point I was making. I was simply 
> saying that even applications that support presence might 
> support XMPP rather than SIMPLE, and therefore would not want 
> to implement RFC 3856. Instead they might prefer to use HTTP.
I am not quite sure which scenario you have in mind. 
If I have an end host that supports XMPP and then gets a location URI
then there is the question of who is going to dereference it. If it is
the end point then it would have to implement the protocol indicated by
the URI scheme. Now, if this happens to be SIP then this end point would
have to implement SIP. The end host could, however, request location by
value instead instead of going through the dance of utilizing a LbyR. 
If the end point does not dereference the LbyR but instead some other
entity then there is the question of how this reference then actually
gets there. 

Ciao
Hannes