IETF Logo Mail Archive

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

Brian Rosen <br@brianrosen.net> Fri, 15 July 2005 16:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtTGt-0003ia-E4; Fri, 15 Jul 2005 12:42:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtTGs-0003iV-Il for geopriv@megatron.ietf.org; Fri, 15 Jul 2005 12:42:42 -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 MAA23749 for <geopriv@ietf.org>; Fri, 15 Jul 2005 12:42:39 -0400 (EDT)
Received: from mta2.prod1.dngr.net ([216.220.209.221] helo=mfe1.prod.danger.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtTji-0000CE-Fv for geopriv@ietf.org; Fri, 15 Jul 2005 13:12:31 -0400
Received: from [10.253.1.252] (HELO localhost.localdomain) by mfe1.prod.danger.com (CommuniGate Pro SMTP 4.1.6) with ESMTP id 338696134; Fri, 15 Jul 2005 09:42:23 -0700
Date: Fri, 15 Jul 2005 12:42:15 -0400
Subject: Re: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-l o -profile-00
X-Mailer: Danger Service
Content-Transfer-Encoding: 7bit
In-Reply-To: <911MAIL1wiZ9rWjAKYV0000270a@mail.911.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Marc Berryman <MBerryman@911.org>, "James M. Polk" <jmpolk@cisco.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Mime-Version: 1.0
References: <911MAIL1wiZ9rWjAKYV0000270a@mail.911.org>
From: Brian Rosen <br@brianrosen.net>
Message-Id: <1121445741.38CA5BC4@bc12.dngr.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
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>
Sender: geopriv-bounces@ietf.org
Errors-To: geopriv-bounces@ietf.org

Henning has given examples where routing is dependent on z.  One is 
where you have an enterprise, which could be a university, which has its 
own response capability.  The enterprise could occupy a portion of a 
high rise.

Sending both is aways fine with me, as long as you know what the data 
really means. Routing has to be fast and unambigous.  If you get 
multiple locations, however they are represented in the signaling, you 
need to choose one to route on.  To me, that would be the "orignal", 
civic or geo.  Of course we may have the problem of multiple locations 
because multiple entities have their own mechanisms.  We need ways of 
representing them so that we can decide which of them to use for 
routing.  This is a "truth in labeling" problem.

Brian

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

v2.23.0 | Report a Bug | By Email