Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-l o -profile-00

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 15 July 2005 01:28 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtF0M-0008Ny-3y; Thu, 14 Jul 2005 21:28:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtF0K-0008MT-VH for geopriv@megatron.ietf.org; Thu, 14 Jul 2005 21:28:41 -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 VAA27500 for <geopriv@ietf.org>; Thu, 14 Jul 2005 21:28:39 -0400 (EDT)
Received: from serrano.cc.columbia.edu ([128.59.29.6] ident=cu41754) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtFT2-000262-PQ for geopriv@ietf.org; Thu, 14 Jul 2005 21:58:22 -0400
Received: from [192.168.0.31] (pool-141-153-198-113.mad.east.verizon.net [141.153.198.113]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j6F1RYsg015750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 Jul 2005 21:27:35 -0400 (EDT)
Message-ID: <42D71101.6090606@cs.columbia.edu>
Date: Thu, 14 Jul 2005 21:27:29 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Winterbottom <winterb@nortel.com>
Subject: Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-l o -profile-00
References: <C0FA66CBDDF5D411B82E00508BE3A7221158AAE6@zctwc059.asiapac.nortel.com>
In-Reply-To: <C0FA66CBDDF5D411B82E00508BE3A7221158AAE6@zctwc059.asiapac.nortel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: 'GEOPRIV' <geopriv@ietf.org>, Marc Linsner <mlinsner@cisco.com>, "James M. Polk" <jmpolk@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>
Sender: geopriv-bounces@ietf.org
Errors-To: geopriv-bounces@ietf.org

James Winterbottom wrote:
> 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 

That's true in some sense, but doesn't much matter. Just like we have to 
assume that an operator includes a valid geo address, we have to assume 
that the civic address is a complete and preferably validated address, 
at least to the street level.

(Obviously, in either geo or civic case, things like building names or 
floor numbers may not be included.)

The notion that geo is always sufficient for routing is mistaken. If 
your geo resolution is such that it includes the whole North American 
continent, it is not particularly useful for routing. This is exactly 
the same problem as if somebody were to only include the country and 
state, say.

Henning

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv