Re: [dhcwg] Geographic position option

Sam Critchley <Sam.Critchley@wcom.com> Mon, 19 August 2002 10:37 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 GAA27346 for <dhcwg-archive@odin.ietf.org>; Mon, 19 Aug 2002 06:37:45 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA11518 for dhcwg-archive@odin.ietf.org; Mon, 19 Aug 2002 06:39:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11472; Mon, 19 Aug 2002 06:35:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11445 for <dhcwg@optimus.ietf.org>; Mon, 19 Aug 2002 06:35:45 -0400 (EDT)
Received: from ams2eusosrv15.ams.ops.eu.uu.net (ams2eusosrv15.ams.ops.eu.uu.net [146.188.99.70]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27293 for <dhcwg@ietf.org>; Mon, 19 Aug 2002 06:34:21 -0400 (EDT)
Received: from ams2eusosrv20.ams.ops.eu.uu.net by ams2eusosrv15.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: ams2eusosrv20.ams.ops.eu.uu.net [146.188.99.75]) id QQncoo01541; Mon, 19 Aug 2002 10:35:41 GMT
Received: from ams2eusosrv20.ams.ops.eu.uu.net by ams2eusosrv20.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: localhost [127.0.0.1]) id QQncoo27672; Mon, 19 Aug 2002 10:35:34 GMT
Received: from anocserve1.ams.ops.eu.uu.net by ams2eusosrv20.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: anocserve1.ams.ops.eu.uu.net [146.188.99.69]) id QQncoo27668; Mon, 19 Aug 2002 10:35:34 GMT
Date: Mon, 19 Aug 2002 12:35:34 +0200
From: Sam Critchley <Sam.Critchley@wcom.com>
X-X-Sender: <samc@anocserve1.ams.ops.eu.uu.net>
To: RyanScripps@alumni.utexas.net
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Geographic position option
In-Reply-To: <20020816154942.26115.qmail@web13907.mail.yahoo.com>
Message-ID: <Pine.SOL.4.33.0208191220450.3159-100000@anocserve1.ams.ops.eu.uu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

Hi Ryan,

Thanks for the comments as well, please see mine inline:

On Fri, 16 Aug 2002, Ryan Scripps wrote:

> This is an interesting option, but I don't understand
> it's relevance.  A DHCP client only talks to a DHCP
> server when negotiating a lease.  Physical location is
> unimportant in this transaction since physical
> closeness does not necessarily imply "network
> closeness".  Furthermore, as stated in the draft,
> other mechanisms exist to query the physical location
> of a client.

Well, in the case of growth in mobile access in the future, there
currently seem to be two main areas:

1. Mobile telephony-based systems, such as 2.5/3G solutions (GPRS, CDMA
1x, CDMA2000, UMTS etc). Content based a lot on i-Mode, WAP 2.0 etc. For
example, i-Mode here in the Netherlands seems to work pretty well and
there are a lot of services being developed.

2. 802.11-based access, with roaming across national/international
networks in many locations. Roaming agreements are in place, vendors are
shipping equipment with 802.11 devices built in, and apparently sales of
802.11b cards for laptops/PDAs etc are running around 1 million per month.

There are also combinations of the above, where with one subscription you
can have mobile telephony in most places, but switch to higher speed
802.11 when in range.

A lot of work is going in LBS mechanisms for the first option (and in
South Korea, for example, there are already over a million GPS-enabled
mobile phones which use them), but (as far as I can see) little is
happening for the second one, and I don't yet see a mechanism in place
which will tell me or an LBS server my location adequately, certainly not
with the security level I would require. To have a DHCP-based system which
would give you your position to, in many cases, a few metres accuracy,
would seem to at least be adequate to use many of the LBS services being
put together, in the absence of a host being able to acquire its exact
location.

>
> I look forward to further discussion.

Me too. :-)

Thanks,


Sam


>
> -Ryan Scripps
>
> --- Sam Critchley <Sam.Critchley@wcom.com> wrote:
> >
> > Hi,
> >
> > Included below is a draft proposing an option to
> > allow a DHCP server to
> > pass its geographic location to a DHCP client.
> >
> > From RFC 2489:
> >
> > "Preferably, the author will submit the Internet
> > Draft to the DHC Working
> > Group,..."
> >
> > and
> >
> > "The specification is reviewed by the DHC WG (if it
> > exists) or by the
> > IETF."
> >
> > So, I'd be interested in people's comments on this
> > document. What should I
> > do with the document now?
> >
> > Many thanks,
> >
> >
> > Sam
> >
> >
> > Here is the draft:
> >
> >
> ************************************************************************
> >
> > Network Working Group
> >       Sam Critchley
> > Internet Draft
> >       Worldcom, Inc
> >
> >
> >        August, 2002
> >
> > Expires January, 2003
> >
> >
> > 	     The Geographic Position Option for DHCP
> >
> > <draft-critchley-dhc-location-option-00.txt>
> >
> > Status of this Memo
> >
> >    This document is an Internet-Draft and is subject
> > to all provisions
> >    of Section 10 of RFC2026.
> >
> >    Internet-Drafts are working documents of the
> > Internet Engineering
> >    Task Force (IETF), its areas, and its working
> > groups.  Note that
> >    other groups may also distribute working
> > documents as
> >    Internet-Drafts.
> >
> >    Internet-Drafts are draft documents valid for a
> > maximum of six
> >    months and may be updated, replaced, or obsoleted
> > by other
> >    documents at any time.  It is inappropriate to
> > use Internet-
> >    Drafts as reference material or to cite them
> > other than as
> >    "work in progress."
> >
> >    The list of current Internet-Drafts can be
> > accessed at
> >    http://www.ietf.org/1id-abstracts.html
> >
> >    The list of Internet-Draft Shadow Directories can
> > be accessed at
> >    http://www.ietf.org/shadow.html
> >
> > Abstract
> >
> >    This document describes a DHCP option in which
> > the geographic
> >    position of the DHCP server is passed to the DHCP
> > client in order
> >    to allow the client to make use of Location-Based
> > Services.
> >
> > 1. 	Introduction
> >
> >    Mobile telephony networks are able to make use of
> > certain
> >    technologies which supply the geographic location
> > of a mobile
> >    suscriber's handset to a Location-Based Services
> > (LBS) provider. The
> >    mobile subscriber is then able to take advantage
> > of such services
> >    as point-of-interest (POI) location, mapping,
> > route-determination,
> >    traffic services and location-aware mobile
> > instant messaging.
> >
> >    There is currently no standardised mechanism in
> > place to supply
> >    a geographic location to Internet hosts not
> > connected to mobile
> >    telephony network, including, but not limited to,
> > hosts connecting
> >    using IEEE 802.11x wireless protocols, and those
> > connected to
> >    wire-based networks but configured with
> > non-static IP addresses.
> >    Consequently, these hosts are more limited in
> > their ability to
> >    take advantage of LBS, including having to
> > manually enter a
> >    geographic position or street address in many
> > cases.
> >
> >    This document defines a DHCP option by which a
> > DHCP server can pass
> >    its geographical location, in the form of a
> > latitude, longitude and
> >    altitude position, to its clients.
> >
> >    This document does not seek to define a method to
> > allow a host to
> >    pass its location to a LBS server, as there are
> > already in place
> >    several standards which propose these mechanisms,
> > such as the Mobile
> >    Location Protocol (MLP) developed by the Location
> > Interoperability
> >    Forum (LIF), although it does make one security
> > recommendation in
> >    this area.
> >
> >    Furthermore, this document does not attempt to
> > propose a mechanism
> >    which would perform in the same manner as
> > critical emergency location
> >    services such as the Enhanced 911 (E-911) service
> > being implemented
> >    in US mobile telephony networks, nor does it
> > propose a mechanism
> >    to be used for highly accurate positioning
> > applications, such as that   provided by the Global
> > Positioning System (GPS).
> >
> >    However, the Geographic Position Option for DHCP
> > does propose a
> >    mechanism which, in many cases, will provide a
> > position to the same
> >    degree of accuracy as that provided by mobile
> > telephony networks'
> >    geographic location mechanisms.
> >
> > 2. 	The Geographic Position Option for DHCP
> >
> > 2.1	DHCP Option field definitions.
> >
> >    This option contains the following fields:
> >
> >    a) Option Code - TBD
> >    b) Option length in bytes
> >    c) DHCP Server Geographic Position Sentence
> >
> >     0                   1                   2
> >            3
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
> > 4 5 6 7 8 9 0 1
> >
> >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |   Code = TBD  |    Length     |  Geographic
> > Position Sentence |
> >
> >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                 Geographic Position Sentence
> >               |
> >
> >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                            . . . .
> >               |
> >
> >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                            . . . .
> >               |
> >
> >
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > 2.2 	DHCP Server Geographic Position Sentence
> >
> >    The DHCP Server Geographic Position Sentence
> > takes the form of a
> >    comma-separated ASCII string of position terms.
> > This is in some ways
> >    similar to the format used in the National Marine
> > Electronics
> >    Association's NMEA 0183 and NMEA 2000 standards,
> > commonly
> === message truncated ===
>
>
> __________________________________________________
> Do You Yahoo!?
> HotJobs - Search Thousands of New Jobs
> http://www.hotjobs.com
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>


******************************************************
Sam Critchley           Technology Integration Manager
                        Network Services EMEA
Sam.Critchley@wcom.com  Worldcom
                       	Joan Muyskenweg 22
Tel: +31 20 711 6082    1096 CJ Amsterdam
                        The Netherlands
******************************************************


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