RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-l o -profile-00
"James Winterbottom" <winterb@nortel.com> Fri, 15 July 2005 01:19 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtErp-0004cj-RL; Thu, 14 Jul 2005 21:19:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtEro-0004cb-Ht for geopriv@megatron.ietf.org; Thu, 14 Jul 2005 21:19:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26919 for <geopriv@ietf.org>; Thu, 14 Jul 2005 21:19:50 -0400 (EDT)
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtFKW-0001qZ-TC for geopriv@ietf.org; Thu, 14 Jul 2005 21:49:33 -0400
Received: from zctwc060.asiapac.nortel.com (zctwc060.asiapac.nortel.com [47.153.200.67]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j6F1HrJ26188; Thu, 14 Jul 2005 20:17:54 -0500 (CDT)
Received: by zctwc060.asiapac.nortel.com with Internet Mail Service (5.5.2653.19) id <N6XR4W5K>; Fri, 15 Jul 2005 11:17:22 +1000
Message-ID: <C0FA66CBDDF5D411B82E00508BE3A7221158AAE6@zctwc059.asiapac.nortel.com>
From: James Winterbottom <winterb@nortel.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>, "James M. Polk" <jmpolk@cisco.com>
Subject: RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-l o -profile-00
Date: Fri, 15 Jul 2005 11:17:20 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: 'GEOPRIV' <geopriv@ietf.org>, Marc Linsner <mlinsner@cisco.com>
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>
Content-Type: multipart/mixed; boundary="===============0245813334=="
Sender: geopriv-bounces@ietf.org
Errors-To: geopriv-bounces@ietf.org
I think that the problem is more complex than this. The Geo with floor does provide a relatively precise location. Certainly it can be precise enough to enable routing decisions to be made. Civic, as is defined in the PIDF-LO document I am afraid does not. All elements are defined as 0-1 occurrences, which means that an operator can pick and choose what ever elements they want to include. We need to provide recommendations on a minimum set of civic elements that are required to be entered I think. Anyway, given this limitation I am going to propose the following: 1) If you request AT THE SAME TIME, Geo and Civic, and you get both, you: a) Create a Single tuple, status, GeoPriv and Location-info element. b) You fill in everything you can with the Geo information first, so Geo will be the first entry in the location-info element. If floor was provided then you create a civic element and fill in the floor. c) You take everything except for floor from the returned civic information and populate that into the same civic element that was created to put the floor info into. RATIONALE:- Civic data returned may not be sufficient to provide routing information, but may be extremely useful to people that need to look at the location. 2) If you request different location types at different times then the locations must be populated into different tuples. -----Original Message----- From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] Sent: Friday, 15 July 2005 10:47 AM To: James M. Polk Cc: Winterbottom, James [WOLL:5500:EXCH]; Marc Linsner; 'GEOPRIV' Subject: Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-lo -profile-00 Since I'm not sure I understand the question and since partial answers may confuse more than help, let me try to explain what I see as the process and issues systematically. The DHCP client wants to get location information and then PUBLISH this information via PIDF-LO. I assume that the DHCP client has no out-of-band knowledge what location information, if any, is available locally. Let's assume that the DHCP client hasn't participated in the 35 geo vs. civic discussions on this list and just wants to get all the location information it can lay its virtual hands on. I know it's bad form these days to be an agnostic, but maybe we can tolerate it in protocols. The most expedient way is to request both civic and geo options in one DHCP request, requesting them by their respective DHCP option numbers. Let's assume both are available and are returned. (If just one, there's no problem except that you'll possibly generate an incomplete civic record.) The question at hand is what the PIDF should look like, with its 1, 2 or 3 location objects. (One: combined civic+geo, Two: one each, Three: one civic from the geo object, plus the full civic plus the geo object). It sure would be nice if we can give an answer which is something other than "maybe 1, maybe 2, maybe 3, depending on the weather". Henning
_______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www1.ietf.org/mailman/listinfo/geopriv
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James Winterbottom
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Henning Schulzrinne
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James M. Polk
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James Winterbottom
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James M. Polk
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Henning Schulzrinne
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Andrew Newton
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James M. Polk
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James M. Polk
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Henning Schulzrinne
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Brian Rosen
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Marc Linsner
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Marc Linsner
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Tom Taylor
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Brian Rosen
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Marc Berryman
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Marc Linsner
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Brian Rosen
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Marc Berryman
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James M. Polk
- RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf… James M. Polk
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Henning Schulzrinne
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Henning Schulzrinne
- Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf… Tim Dunn
- RE: AW:[Geopriv] Quickrandomcommentsondraft-ietf-… Brian Rosen
- RE: AW:[Geopriv] Quickrandomcommentsondraft-ietf-… James M. Polk