Re: Past LC comments on draft-ietf-geopriv-http-location-delivery-08
Richard Barnes <rbarnes@bbn.com> Mon, 11 August 2008 13:52 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66E533A6C38; Mon, 11 Aug 2008 06:52:06 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F11673A6824 for <ietf@core3.amsl.com>; Mon, 11 Aug 2008 06:52:04 -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 feNpG7tP1ipj for <ietf@core3.amsl.com>; Mon, 11 Aug 2008 06:52:04 -0700 (PDT)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 7B01D3A6B5F for <ietf@ietf.org>; Mon, 11 Aug 2008 06:51:39 -0700 (PDT)
Received: from col-dhcp33-244-152.bbn.com ([128.33.244.152] helo=Lab-Macbook-Pro.local) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <rbarnes@bbn.com>) id 1KSXoa-0007OT-9z; Mon, 11 Aug 2008 09:52:04 -0400
Message-ID: <48A043E6.7070607@bbn.com>
Date: Mon, 11 Aug 2008 09:51:34 -0400
From: Richard Barnes <rbarnes@bbn.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Past LC comments on draft-ietf-geopriv-http-location-delivery-08
References: <4895D549.9060807@gmx.de> <C41BFCED3C088E40A8510B57B165C1624162FA@FIESEXC007.nsn-intra.net> <4896A57D.30005@gmx.de> <C41BFCED3C088E40A8510B57B165C16241632A@FIESEXC007.nsn-intra.net> <4896AF32.7040900@gmx.de> <E51D5B15BFDEFD448F90BDD17D41CFF104A8E1A9@AHQEX1.andrew.com> <88124B07-C837-4F36-8F70-99E2A63CB7C7@osafoundation.org> <4899F4AA.80003@gmx.de> <8D7BE6AA-F0E3-4127-8650-076E369F2FD3@osafoundation.org> <4899FA6E.60004@gmx.de> <20080806202648.GB4194@iCoaster.does-not-exist.org> <489A0BAC.5040403@gmx.de>
In-Reply-To: <489A0BAC.5040403@gmx.de>
Cc: Lisa Dusseault <lisa@osafoundation.org>, IETF Discussion <ietf@ietf.org>, "Thomson, Martin" <Martin.Thomson@andrew.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Hi Julian, I'd like to try to answer one of your questions: > As far as I understand, HELD is used to query for location information. > Right now, the details of the query are encoded in a POST body as > defined by the XML Schema in > <http://tools.ietf.org/html/draft-ietf-geopriv-http-location-delivery-08#section-7>. > A GET works the same way as an empty POST request (as shown in 11.1). > > This really smells like over-engineering. > > Why aren't these things simple query parameters in a GET request? The short answer is that the WG (and the HELD authors in particular) perceive a need for this protocol to have an extensible request syntax. This document (-http-location-delivery) defines a very basic request-response container for location-request and -response messages. In this basic form, it supports the simple case where the HELD server can determine the client's location based only on the client's IP address. Often, however, the HELD server requires additional information to determine the client's location. The most basic example of this is when the HELD server computes the client's position based measurements of the network, such as 802.11 signal strength measurements. These measurements could be embedded into a HELD request using the extensions to the XML request syntax defined in the following draft: <http://tools.ietf.org/html/draft-thomson-geopriv-held-measurements> <http://tools.ietf.org/html/draft-thomson-geopriv-wimax-measurements> It's fair to note that the WG has not adopted any HELD extensions as WG documents. However, GEOPRIV is currently considering whether to adopt them, so it seems to make sense to provide a simple way to extend the request syntax. Cheers, --Richard _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Past LC comments on draft-ietf-geopriv-http-locat… Julian Reschke
- RE: Past LC comments on draft-ietf-geopriv-http-l… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- RE: Past LC comments on draft-ietf-geopriv-http-l… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: Past LC comments on draft-ietf-geopriv-http-l… Frank Ellermann
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- RE: Past LC comments on draft-ietf-geopriv-http-l… Thomson, Martin
- Re: Past LC comments on draft-ietf-geopriv-http-l… Lisa Dusseault
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- Re: Past LC comments on draft-ietf-geopriv-http-l… Lisa Dusseault
- Re: Past LC comments on draft-ietf-geopriv-http-l… Frank Ellermann
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- Re: Past LC comments on draft-ietf-geopriv-http-l… Thomas Roessler
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- New schemes vs recycling "http:" (Re: Past LC com… Harald Alvestrand
- Re: New schemes vs recycling "http:" (Re: Past LC… Patrik Fältström
- Re: New schemes vs recycling "http:" (Re: Past LC… Julian Reschke
- Re: New schemes vs recycling "http:" (Re: Past LC… Julian Reschke
- Re: New schemes vs recycling "http:" (Re: Past LC… Harald Alvestrand
- Re: New schemes vs recycling "http:" (Re: Past LC… Julian Reschke
- RE: New schemes vs recycling "http:" (Re: Past LC… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: New schemes vs recycling "http:" (Re: Past LC… Julian Reschke
- Re: New schemes vs recycling "http:" (Re: Past LC… Tim Bray
- Re: New schemes vs recycling "http:" (Re: Past LC… Lisa Dusseault
- Re: New schemes vs recycling "http:" (Re: Past LC… Julian Reschke
- Re: Past LC comments on draft-ietf-geopriv-http-l… Tony Finch
- Re: Past LC comments on draft-ietf-geopriv-http-l… Julian Reschke
- Re: New schemes vs recycling "http:" (Re: Past LC… Keith Moore
- Re: New schemes vs recycling "http:" (Re: Past LC… Tim Bray
- Re: New schemes vs recycling "http:" (Re: Past LC… Keith Moore
- Re: New schemes vs recycling "http:" (Re: Past LC… Lisa Dusseault
- Re: New schemes vs recycling "http:" (Re: Past LC… Tim Bray
- Re: New schemes vs recycling "http:" (Re: Past LC… Keith Moore
- Re: New schemes vs recycling "http:" (Re: Past LC… Tim Bray
- Re: New schemes vs recycling "http:" (Re: Past LC… Ted Hardie
- Re: New schemes vs recycling "http:" (Re: Past LC… Keith Moore
- Re: New schemes vs recycling "http:" (Re: Past LC… Julian Reschke
- Re: Past LC comments on draft-ietf-geopriv-http-l… Richard Barnes