RE: [dhcwg] Working Group Last Call: Location Configuration Info rmation for GEOPRIV

John Schnizlein <jschnizl@cisco.com> Wed, 02 July 2003 18:52 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06054; Wed, 2 Jul 2003 14:52:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xmi0-0004ad-OB; Wed, 02 Jul 2003 14:52:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xmhq-0004aQ-0v for dhcwg@optimus.ietf.org; Wed, 02 Jul 2003 14:51:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06023 for <dhcwg@ietf.org>; Wed, 2 Jul 2003 14:51:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xmhn-0005jH-00 for dhcwg@ietf.org; Wed, 02 Jul 2003 14:51:47 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19Xmhm-0005j5-00 for dhcwg@ietf.org; Wed, 02 Jul 2003 14:51:46 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h62IpDf0005190; Wed, 2 Jul 2003 11:51:14 -0700 (PDT)
Received: from jschnizl-w2k.cisco.com (rtp-vpn1-50.cisco.com [10.82.224.50]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA24545; Wed, 2 Jul 2003 11:51:12 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030702140724.020a14f0@wells.cisco.com>
X-Sender: jschnizl@wells.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 02 Jul 2003 14:51:11 -0400
To: "Abbott, Nadine B." <nabbott@telcordia.com>
From: John Schnizlein <jschnizl@cisco.com>
Subject: RE: [dhcwg] Working Group Last Call: Location Configuration Info rmation for GEOPRIV
Cc: 'Marc Linsner' <mlinsner@cisco.com>, dhcwg@ietf.org, geopriv@mail.apps.ietf.org, "Defazio, Carol" <cdefazio@telcordia.com>
In-Reply-To: <F0CB7F62D783BF40AD93882BB817F245129721@nvc-dts-exs01.cc.te lcordia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

At 01:42 PM 7/2/2003, Abbott, Nadine B. wrote:

>FYI and Question:
>
>For wireless 9-1-1 calls, the geodetic location is provided from the
>wireless carriers in a binary coded form over SS7 ...

For the same reasons that 2's complement binary is preferred
over binary-coded decimal in computing systems, I prefer it
for the DHCP option. It is worth remembering that the location
option is likely just one of many that have to fit in the
UDP-based DHC protocol. The efficiency of binary numbers fits
the principle of frugality with lightweight protocols.

Having the carrier provide location over its signaling system
is a little different from the model of connected computers.
In the wired-computer mechanism we envision, the edge network 
tells the computer where the wire it plugged into is so that 
it can decide who/what/when/where/how to share this information.

>For a 9-1-1 call, if IP devices are populated with coordinate information in
>a different format from that expected by PSAP mapping applications, then
>somewhere between caller and PSAP, the geodetic location information
>provided by the DHCP location object procedures will need to be put into a
>format that can be processed by PSAP applications.  If you assume that the
>location object information is routed via the E9-1-1 DBs, perhaps the
>conversion could be performed there.  

The host can use its location information for anything at all, including
emergency calls. We did not design the format to fit the model of SS7.

>If you envision that geodetic location is carried with 
>the call establishment signaling, where do you assume that
>the conversion between the DHCP-LO format and the formats 
>expected by PSAP applications will take place?  

Marc is taking a little time off before IETF, and will probably 
have more details, but we had not intended to constrain where 
format conversions would take place. I think James has some ideas 
about including location in SIP emergency call routing, but that 
also need  not follow an SS7 route. And Henning seems still 
interested in pursuing the civil location information also, 
which could be useful to the PSAP. Too soon to choose IMHO
among lots of alternatives.

John


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