IETF Logo Mail Archive

Re: [sipcore] Questions on location conveyance and dereferencing

"Winterbottom, James" <James.Winterbottom@andrew.com> Thu, 12 August 2010 08:27 UTC

Return-Path: <James.Winterbottom@andrew.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 A4B9A3A69F0 for <sipcore@core3.amsl.com>; Thu, 12 Aug 2010 01:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level:
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=-0.856, BAYES_00=-2.599]
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 0ML0d494m2g8 for <sipcore@core3.amsl.com>; Thu, 12 Aug 2010 01:27:08 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id 0BE763A69C3 for <sipcore@ietf.org>; Thu, 12 Aug 2010 01:27:08 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:33291 "EHLO ACDCE7HC2.commscope.com") by csmailgw1.commscope.com with ESMTP id S30152371Ab0HLI1o convert rfc822-to-8bit (ORCPT <rfc822; sipcore@ietf.org>); Thu, 12 Aug 2010 03:27:44 -0500
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Thu, 12 Aug 2010 03:27:44 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Thu, 12 Aug 2010 16:27:40 +0800
From: "Winterbottom, James" <James.Winterbottom@andrew.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Thu, 12 Aug 2010 16:26:33 +0800
Thread-Topic: Questions on location conveyance and dereferencing
Thread-Index: Acs591dqg6OyEIxSSSGOaw4Ja2Tz5gAALtKV
Message-ID: <5A55A45AE77F5941B18E5457ECAC81880120EB7D94A3@SISPE7MB1.commscope.com>
References: <A444A0F8084434499206E78C106220CA01C46B4FF1@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA01C46B4FF1@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: James.Winterbottom@andrew.com
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: Thu, 12 Aug 2010 08:27:09 -0000

Hi John,

I think you could use this as a basic location subscription:
http://tools.ietf.org/html/draft-ietf-geopriv-loc-filters-11

There is already a lot of protest against point 2, and I believe that this is going to be fixed.

Cheers
James

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Elwell, John [john.elwell@siemens-enterprise.com]
Sent: Thursday, August 12, 2010 3:21 AM
To: sipcore@ietf.org
Subject: [sipcore] Questions on location conveyance and dereferencing

1. Draft-ietf-sipcore-location-conveyance-03 defines PRES, SIP and SIPS URI schemes for LbyR. For SIP and SIPS, there seems to be an absence of specification of what event package to use when submitting a SIP or SIPS SUBSCRIBE request for dereference purposes. If it is not defined in this specification, where is it defined?

2. Concerning PRES-URIs, we have the following text in 4.6:
"If a location URI is included in a SIP request, it MUST be a SIP-,
   SIPS- or PRES-URI.  When PRES: is used, as defined in [RFC3856], if
   the resulting resolution resolves to a SIP: or SIPS: URI, this
   section applies."

The words "this section applies" are rather strange, because there is little else in this section. Maybe in a previous iteration there was more information here (on how to use a SIP/SIPS URI for dereference purposes). As things stand, the absence of information on how to resolve a SIP- or SIPS-URI applies also to PRES-URIs.

3. Also there is nothing to say what to do if the PRES URI fails to resolve to a SIP or SIPS URI.

4. The "MUST be a SIP-, SIPS- or PRES-URI" text in cited above seems to preclude the addition of future URI schemes, which seems to be in conflict with 8.6 (registry establishment for location URIs).


John
_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email