Re: [sipcore] location-conveyance-03 just submitted

"Winterbottom, James" <James.Winterbottom@andrew.com> Tue, 13 July 2010 06:51 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 780293A690E for <sipcore@core3.amsl.com>; Mon, 12 Jul 2010 23:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 xNvM7WxIb1RK for <sipcore@core3.amsl.com>; Mon, 12 Jul 2010 23:51:11 -0700 (PDT)
Received: from csmailgw2.commscope.com (csmailgw2.commscope.com [198.135.207.242]) by core3.amsl.com (Postfix) with ESMTP id A1E353A6851 for <sipcore@ietf.org>; Mon, 12 Jul 2010 23:51:11 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:58073 "EHLO ACDCE7HC2.commscope.com") by csmailgw2.commscope.com with ESMTP id S331734Ab0GMGvU convert rfc822-to-8bit (ORCPT <rfc822; sipcore@ietf.org>); Tue, 13 Jul 2010 01:51:20 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Tue, 13 Jul 2010 01:51:20 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Tue, 13 Jul 2010 14:51:18 +0800
From: "Winterbottom, James" <James.Winterbottom@andrew.com>
To: "James M. Polk" <jmpolk@cisco.com>, "Thomson, Martin" <Martin.Thomson@andrew.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Tue, 13 Jul 2010 14:51:16 +0800
Thread-Topic: [sipcore] location-conveyance-03 just submitted
Thread-Index: AcsiVM7hB/XehKtcRIGsLtrH5/QNRQAAb/hQ
Message-ID: <5A55A45AE77F5941B18E5457ECAC81880120E7BC023C@SISPE7MB1.commscope.com>
References: <201007122355.o6CNt6us024310@sj-core-3.cisco.com> <8B0A9FCBB9832F43971E38010638454F03E9DCCFFC@SISPE7MB1.commscope.com> <201007130629.o6D6Tk7F028645@sj-core-2.cisco.com>
In-Reply-To: <201007130629.o6D6Tk7F028645@sj-core-2.cisco.com>
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 csmailgw2.commscope.com
X-BCN-Sender: James.Winterbottom@andrew.com
Subject: Re: [sipcore] location-conveyance-03 just submitted
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: Tue, 13 Jul 2010 06:51:12 -0000

Hi James,

I have similar sentiments to Martin, this is a greatly improved document.


> >Section 4.6 should reference draft-ietf-geopriv-deref-protocol.
> 
> how so?
> 
> It is already covered by the geopriv-filters
> reference. I do not believe anything more is necessary.
> 

I don't think that your response here answers the question.
Section 4.6 as is written now is saying that only a SIP, SIPS or PRES URI scheme can be carried in the Sip header.

" 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.  These schemes MUST be implemented according to
  this document.

   absoluteURI is not mandatory-to-implement, but allowed.

   See [ID-GEO-FILTERS] for more details on dereferencing location."

LOC Filters is all about subscribing for location information using SIP, and makes no reference to the HELD deref draft that Martin has requested reference to. Since we now have a working group item in Geopriv describing how an HTTP URI can be used as a location URI, it is being requested that the SIP conveyance document allow this in its prose, rather than excluding everything but a SIP-related method. I think that this is a reasonable request.

Cheers
James