Re: [Geopriv] Another Update to draft-ietf-geopriv-loc-filters-05.txt

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Mon, 27 July 2009 16:52 UTC

Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6C3528C238 for <geopriv@core3.amsl.com>; Mon, 27 Jul 2009 09:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, 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 jDYBQuawuiQR for <geopriv@core3.amsl.com>; Mon, 27 Jul 2009 09:52:08 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 590E728C31B for <geopriv@ietf.org>; Mon, 27 Jul 2009 09:52:06 -0700 (PDT)
Received: (qmail invoked by alias); 27 Jul 2009 16:51:58 -0000
Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp071) with SMTP; 27 Jul 2009 18:51:59 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+ZDYpuGqSZeVlQn+FjeKNBweUicNv2qGhB/fi3NE 9/gOVLvxngrFeI
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: "'James M. Polk'" <jmpolk@cisco.com>, "'Thomson, Martin'" <Martin.Thomson@andrew.com>, geopriv@ietf.org
References: <017d01ca0525$c2102fd0$1116a20a@nsnintra.net> <E51D5B15BFDEFD448F90BDD17D41CFF10608AEB6@AHQEX1.andrew.com> <02f901ca06c6$6ab2bb70$0301a8c0@nsnintra.net> <XFE-SJC-212LFQG101s00009d83@xfe-sjc-212.amer.cisco.com>
Date: Mon, 27 Jul 2009 19:54:23 +0300
Message-ID: <027f01ca0eda$e6900ce0$0301a8c0@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcoOO4y0opIlObNDQWKeU5PuUsVVxwAnlUnw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <XFE-SJC-212LFQG101s00009d83@xfe-sjc-212.amer.cisco.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.59
Subject: Re: [Geopriv] Another Update to draft-ietf-geopriv-loc-filters-05.txt
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 16:52:08 -0000

Hi James, 
 
>> >More seriously: I'm not entirely sure how to interpret responseTime 
>> >in the context of a SIP PA.  This might work as you have described, 
>> >but I would suggest that it complicates things 
>considerably.  There's 
>> >discussion on this point in my draft here:
>> >
>> ><http://tools.ietf.org/html/draft-thomson-simple-cont-presence->val
>> -req-02#section-4.6.1.1>
>> >
>> >I don't know how to solve this problem yet.
>> >
>>
>>I am not sure I see the problems.
>>
>>Imagine a SIP proxy receives a SIP message with an LbyR and wants to 
>>retrieve location information for routing. Depending on the 
>URI scheme 
>>(HTTP vs. SIP) he would either use 
>>http://tools.ietf.org/id/draft-winterbottom-geopriv-deref-prot
>ocol-03.t
>>xt
>>Or
>>http://www.ietf.org/internet-drafts/draft-ietf-geopriv-loc-fil
>ters-04.t
>>xt
>
>I'm confused.
>
>For SIP, why would the filters doc be used when Conveyance 
>already has how a server dereferences a location URI for routing?
>
>This isn't a soliciting action requiring filters.

How does SIP Location Conveyance dereference location URIs?
My reading of draft-ietf-sip-location-conveyance was that it conveys
location by value and/or by reference. 

What "indication" is used in a SIP SUBSCRIBE to indicate "Please give me
location information suitable for routing."? 

Ciao
Hannes