Re: [dhcwg] Geographic position option

[Ryan Scripps <[e-mail]>]

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.

I look forward to further discussion.

-Ryan Scripps

--- Sam Critchley <[e-mail]> 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
[e-mail]
https://www1.ietf.org/mailman/listinfo/dhcwg