Re: [dhcwg] Re: Fwd: I-D ACTION:draft-polk-dhcp-geo-loc-option-00.txt

Ted Lemon <Ted.Lemon@nominum.com> Fri, 25 October 2002 20:58 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11752 for <dhcwg-archive@odin.ietf.org>; Fri, 25 Oct 2002 16:58:50 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9PL0hs31593 for dhcwg-archive@odin.ietf.org; Fri, 25 Oct 2002 17:00:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PL0hv31590 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 25 Oct 2002 17:00:43 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11740 for <dhcwg-web-archive@ietf.org>; Fri, 25 Oct 2002 16:58:19 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PKw9v31196; Fri, 25 Oct 2002 16:58:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PKvZv31182 for <dhcwg@optimus.ietf.org>; Fri, 25 Oct 2002 16:57:35 -0400
Received: from toccata.fugue.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11509 for <dhcwg@ietf.org>; Fri, 25 Oct 2002 16:55:11 -0400 (EDT)
Received: from nominum.com (a35.pm3-67.theriver.com [206.25.48.227]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id g9PKtN211855; Fri, 25 Oct 2002 15:55:23 -0500 (CDT)
Date: Fri, 25 Oct 2002 13:57:21 -0700
Subject: Re: [dhcwg] Re: Fwd: I-D ACTION:draft-polk-dhcp-geo-loc-option-00.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "Marc Linsner" <mlinsner@cisco.com>, "James M. Polk" <jmpolk@cisco.com>, dhcwg@ietf.org
To: John Schnizlein <jschnizl@cisco.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <4.3.2.7.2.20021023142936.01d98d88@wells.cisco.com>
Message-Id: <5AE3D9D6-E85C-11D6-B81E-003065D63CF6@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

It looks fine, superficially, but all those fiddly 4-bit, 34-bit, and 
30-bit values are going to be a real pain for implementation.   I don't 
know if this is going to be implemented on servers that are not 
embedded in devices that can do location calculations, but if it is, it 
would be better to use a less complex numbering scheme.   It's normally 
considered bad form to have a DHCP option that requires special 
modifications to the server in order to implement.

I'm also a bit skeptical that DHCP is even the right way to do this, 
because the DHCP server's physical location, and even the relay agent's 
physical location, is not the same as the device's physical location.   
For wired devices, you can figure out the devices location through a 
database lookup, but for wireless devices you need to triangulate, and 
I have trouble figuring out how you're going to cram that functionality 
into a DHCP server.

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