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

"Abbott, Nadine B." <nabbott@telcordia.com> Wed, 02 July 2003 17:48 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 NAA03913; Wed, 2 Jul 2003 13:48:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xli5-00021J-8z; Wed, 02 Jul 2003 13:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xle2-0001yh-Sf for dhcwg@optimus.ietf.org; Wed, 02 Jul 2003 13:43: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 NAA03805 for <dhcwg@ietf.org>; Wed, 2 Jul 2003 13:43:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xle0-0004tG-00 for dhcwg@ietf.org; Wed, 02 Jul 2003 13:43:48 -0400
Received: from dnsmx1rrc.telcordia.com ([128.96.20.41]) by ietf-mx with esmtp (Exim 4.12) id 19Xldz-0004sw-00 for dhcwg@ietf.org; Wed, 02 Jul 2003 13:43:47 -0400
Received: from rrc-its-ieg01.cc.telcordia.com (rrc-its-ieg01.cc.telcordia.com [128.96.109.78]) by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with SMTP id NAA14425 for <dhcwg@ietf.org>; Wed, 2 Jul 2003 13:42:43 -0400 (EDT)
Received: from rrc-its-exbh01.mail.saic.com ([128.96.109.61]) by rrc-its-ieg01.cc.telcordia.com (NAVGW 2.5.2.17) with SMTP id M2003070213424007596 ; Wed, 02 Jul 2003 13:42:42 -0400
Received: by rrc-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19) id <3BQY12LJ>; Wed, 2 Jul 2003 13:42:40 -0400
Message-ID: <F0CB7F62D783BF40AD93882BB817F245129721@nvc-dts-exs01.cc.telcordia.com>
From: "Abbott, Nadine B." <nabbott@telcordia.com>
To: 'Marc Linsner' <mlinsner@cisco.com>
Cc: dhcwg@ietf.org, geopriv@mail.apps.ietf.org, "Defazio, Carol" <cdefazio@telcordia.com>
Subject: RE: [dhcwg] Working Group Last Call: Location Configuration Info rmation for GEOPRIV
Date: Wed, 02 Jul 2003 13:42:39 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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>

Marc,

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 (ISUP or TCAP/E2, carried
in Calling Geodetic Location parameter; see ANSI T1.628-2000 for the coding
of the CGL--similar, but not the same as the DHCP-LO).  The location
information is processed by an E9-1-1 Database for delivery to Public Safety
Answering Points (PSAPs).
The geodetic location information that is provided to 9-1-1 Public Safety
Answering Points via queries to these E9-1-1 DBs uses the following NENA
formats:

Longitude:
11 bytes; Numeric; 
Longitude/X coordinate. Right Justified; pad field with zeros to left of
decimal degrees. +long: east of Greenwich; -long: west of Greenwich.  (Can
be used
for wireline as well as wireless) Sample: +000.######

Latitude 
10 bytes; Numeric; 
Latitude/Y coordinate. Right Justified; pad field with zeros to left of
decimal
degrees. +lat: north of equator; -lat: south of equator. (Can be used for
wireline as well as wireless) Sample: +00.######

Elevation 
5 bytes; Numeric;
Elevation/Altitude indicated as height above mean sea level, measured in
meters (Can be used for wireline) Sample: #####

Datum 
2 bytes; alphanumeric;
Specifies the map projection and coordinate system recommended for the
display of the Longitude and Latitude coordinates. Two systems are
commonly used for North America. The code 83 identifies North American
Datum for 1983 (NAD83). Code 84 identifies the World Geodetic System
for 1984 (WGS84). Other codes may be added as additional datum become
available through authorized entities.
Where x =
83 = NAD83
84 = WGS84

****************************************************************************
***********


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.  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?  

Thanks,
Nadine Abbott
Telcordia Technologies



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