Re: [Geopriv] Another Update to draft-ietf-geopriv-loc-filters-05.txt
"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Fri, 17 July 2009 10:04 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 5DA8A3A6E11 for <geopriv@core3.amsl.com>; Fri, 17 Jul 2009 03:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.168
X-Spam-Level:
X-Spam-Status: No, score=-2.168 tagged_above=-999 required=5 tests=[AWL=0.431, 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 3oFygiW5Curz for <geopriv@core3.amsl.com>; Fri, 17 Jul 2009 03:04:46 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 79C903A6D31 for <geopriv@ietf.org>; Fri, 17 Jul 2009 03:04:44 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jul 2009 10:05:17 -0000
Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp021) with SMTP; 17 Jul 2009 12:05:17 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX191yaUlIMx1/fgnP9uQdPB7z1lw2w5IG4c3sizid3 TkXXZQxLMUVnZm
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: "'Thomson, Martin'" <Martin.Thomson@andrew.com>, geopriv@ietf.org
References: <017d01ca0525$c2102fd0$1116a20a@nsnintra.net> <E51D5B15BFDEFD448F90BDD17D41CFF10608AEB6@AHQEX1.andrew.com>
Date: Fri, 17 Jul 2009 13:07:39 +0300
Message-ID: <02f901ca06c6$6ab2bb70$0301a8c0@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <E51D5B15BFDEFD448F90BDD17D41CFF10608AEB6@AHQEX1.andrew.com>
thread-index: AcoFJbwHFm0tlC4TTB+b2vZivz31tgAe9MxwAEjQEiA=
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.52
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: Fri, 17 Jul 2009 10:04:47 -0000
Hi Martin, >Thanks Hannes, > >responseTime is a bit of a concern. > >At a minimum, responseTime is a separate item from >locationType. That will simplify your description a little. Since there is no top level XML element I could only define it as a separate XML element. That's fine but I believe it does not change a lot. >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-protocol-03.txt Or http://www.ietf.org/internet-drafts/draft-ietf-geopriv-loc-filters-04.txt For http://tools.ietf.org/id/draft-winterbottom-geopriv-deref-protocol-03.txt he could use the 'responseTime' attribute set to "emergencyRouting". When a 'responseTime' attribute is used with http://www.ietf.org/internet-drafts/draft-ietf-geopriv-loc-filters-04.txt then hopefully the semantic would be the same. Instead of returning location information that is good for dispatch location information usable for routing would be returned. Ciao Hannes >--Martin > >> -----Original Message----- >> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On >> Behalf Of Hannes Tschofenig >> Sent: Wednesday, 15 July 2009 6:25 PM >> To: geopriv@ietf.org >> Subject: [Geopriv] Another Update to draft-ietf-geopriv-loc-filters- >> 05.txt >> >> Hi all, >> >> Here is another update to >draft-ietf-geopriv-loc-filters-05.txt based >> on the feedback from Martin. The changes are: >> >> * added the <locationType> element (including the 'exact' and >> 'responseTime' >> attribute). I re-used the text from the HELD specification and >> modified as appropriately. >> * fixed the civic prefix in the example (again) >> * modified the schema to pick up the suggestion regarding >the <moved> >> and the <enterOrExit> element. >> >> The new document is here: >> http://www.tschofenig.priv.at/svn/Filters/draft-ietf-geopriv-loc- >> filters-05. >> txt >> >> Ciao >> Hannes >> >> PS: When including the text about <locationType> element two issues >> that might need to get discussed, namely the ability to >carry multiple >> PIDF- Los (or to include multiple representations of the location in >> the same >> PIDF-LO) >> in a NOTIFY and the need to define some error messages >(e.g., to tell >> the Notifier that the requested locationType is actually not >> available). >> >> _______________________________________________ >> Geopriv mailing list >> Geopriv@ietf.org >> https://www.ietf.org/mailman/listinfo/geopriv > >--------------------------------------------------------------- >--------------------------------- >This message is for the designated recipient only and may >contain privileged, proprietary, or otherwise private information. >If you have received it in error, please notify the sender >immediately and delete the original. Any unauthorized use of >this email is prohibited. >--------------------------------------------------------------- >--------------------------------- >[mf2] >
- [Geopriv] Another Update to draft-ietf-geopriv-lo… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… Thomson, Martin
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… Thomson, Martin
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… Thomson, Martin
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… Thomson, Martin
- Re: [Geopriv] Another Update to draft-ietf-geopri… Thomson, Martin
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… James M. Polk
- Re: [Geopriv] Another Update to draft-ietf-geopri… Thomson, Martin
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig
- Re: [Geopriv] Another Update to draft-ietf-geopri… Hannes Tschofenig