[Geopriv] Review of draft-winterbottom-geopriv-held-lis2lis-bcp-00.txt
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Sat, 24 November 2007 11:22 UTC
Return-path: <geopriv-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivt5O-0002mu-Lx; Sat, 24 Nov 2007 06:22:10 -0500
Received: from geopriv by megatron.ietf.org with local (Exim 4.43) id 1Ivt5I-0002mU-6c for geopriv-confirm+ok@megatron.ietf.org; Sat, 24 Nov 2007 06:22:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivt5H-0002m8-Pj for geopriv@ietf.org; Sat, 24 Nov 2007 06:22:03 -0500
Received: from mail.gmx.net ([213.165.64.20]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1Ivt5H-0000fl-0b for geopriv@ietf.org; Sat, 24 Nov 2007 06:22:03 -0500
Received: (qmail invoked by alias); 24 Nov 2007 11:22:01 -0000
Received: from p549857C6.dip.t-dialin.net (EHLO [192.168.1.5]) [84.152.87.198] by mail.gmx.net (mp051) with SMTP; 24 Nov 2007 12:22:01 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19FZLkFzB9FBFLfXBdd4OvmEoCAlEsMAELG+yNli2 uUHi7+kJbqGnUR
Message-ID: <47480955.5060707@gmx.net>
Date: Sat, 24 Nov 2007 12:21:57 +0100
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: GEOPRIV <geopriv@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: "Thomson, Martin" <Martin.Thomson@andrew.com>
Subject: [Geopriv] Review of draft-winterbottom-geopriv-held-lis2lis-bcp-00.txt
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
Errors-To: geopriv-bounces@ietf.org
Some comments for http://tools.ietf.org/wg/geopriv/draft-winterbottom-geopriv-held-lis2lis-bcp-00.txt The document looks good to me. Still, I would merge it with the requirements draft. I would appreciate more RFC 2119 language in Section 4: 4. Detailed Description In a typical environment using HELD, the Target discovers the LIS using one of the methods described in [I-D.thomson-geopriv-lis-discovery], and makes a request for location information. The ISP LIS receives the location request from the Target, adds additional information, and then sends the location request on to the regional access provider LIS. The regional access provider LIS uses the extra information provided in the ISP LIS to determine the location of the Device and provide the PIDF-LO [RFC4119] in the requested form. The ISP LIS will, in many cases creates the identity used in the ^^^^^^^ create "pres" field of the PIDF-LO. This value needs to be conveyed from the ISP LIS to the regional access provider LIS. HELD can convey this value using a URI identity extension as described in [I-D.winterbottom-geopriv-held-identity-extensions]. I don't think that it is necessary to send the identity to the regional access provider LIS The ISP LIS may need to provide Device network attachment ^^^ MAY information, in the form of measurements, to the regional access provider LIS to aid it in determing the Device's location. ^^^^^^^^^ determining A comprehensive set of measurements and how they are used is provided in [I-D.thomson-geopriv-held-measurements]. HELD supports the inclusion of these additional elements without modification. The ISP LIS should not send a request for a location URI to the ^^^^^^^^^^SHOULD NOT regional access provider LIS. This is because the regional access provider LIS is, in most cases, invisible to entities other than the ISP LIS. A location URI contains the hostname of the LIS that will service a location request, which is the ISP LIS and not the regional access provider LIS. Consequently only the ISP LIS should create ^^^^^^ SHOULD location URIs for the Device. A regional access provider LIS receiving a request for a location URI from an ISP LIS should respond ^^^^^^ SHOULD with a "cannotProvideLiType" error. ^^^ if it got a request for creating a location URI that it cannot fulfill. The ISP LIS should pass all elements included in the Device's location request to the regional access provider LIS, with the exception of a request for a location URI which was described in the previous paragraph. This behaviour ensures that any new options made available to the LIS through HELD can be supported without necessarily requiring changes to the ISP LIS. I cannot imagine a use case where this would really be helpful as the ISP LIS is not really a relay but rather the endpoint of the communication from the HELD Target-to-LIS point of view. The ISP LIS should provide usage in any returned location object that match the user's desired settings, or in the absence of these, the default settings for <retransmission-allowed> and <retension-expiry> as applied by the ISP LIS. This corresponds to the HELD default procedure and does not need to be repeated here. Basic HELD is provided with an HTTP binding, which is suitable for the application of a Device requesting its own location. Where a nailed up connection between two entities and continual transaction streaming is required, HTTP may be less appropriate. In this configuration an alternative transport, such as BEEP [I-D.thomson-geopriv-held-beep], may be used. ^^^^MAY I would say that it is useful to indicate that the regional access provider LIS and the ISP LIS have to implement HELD, HELD Identity extension and HELD measurements. I would make this clear in this section. The implementation of [I-D.thomson-geopriv-held-beep] is optional. * Examples. The examples are code fragments. Please add the <?xml version="1.0"?> header. * Security A strong trust relationship needs to exist between the ISP and the regional access provider in order for this type of access network to operate successfully. I would use something like "To provide proper privacy protection the regional access provider LIS would enforce access control on entities requesting location information to ensure that only ISP LISs that have a pre-established trust relationship (potentially based on a business contract) are granted authorization." _______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www1.ietf.org/mailman/listinfo/geopriv
- [Geopriv] Review of draft-winterbottom-geopriv-he… Hannes Tschofenig