[dhcwg] Re: dhcwg digest, Vol 1 #410 - 2 msgs
Eric Scanner Luce <Eric.Luce@nominum.com> Tue, 26 November 2002 18:47 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 NAA15163 for <dhcwg-archive@odin.ietf.org>; Tue, 26 Nov 2002 13:47:34 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAQInoU16237 for dhcwg-archive@odin.ietf.org; Tue, 26 Nov 2002 13:49:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQInov16234 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 13:49:50 -0500
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 NAA15152 for <dhcwg-web-archive@ietf.org>; Tue, 26 Nov 2002 13:47:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQIlLv16088; Tue, 26 Nov 2002 13:47:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQIa0v14897 for <dhcwg@optimus.ietf.org>; Tue, 26 Nov 2002 13:36:00 -0500
Received: from shell.nominum.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14519 for <dhcwg@ietf.org>; Tue, 26 Nov 2002 13:33:12 -0500 (EST)
Received: from yomiko.engr.nominum.com (dhcp-132.engr.nominum.com [128.177.194.132]) by shell.nominum.com (Postfix) with ESMTP id 28247137F11 for <dhcwg@ietf.org>; Tue, 26 Nov 2002 10:35:55 -0800 (PST)
Received: from yomiko.engr.nominum.com (localhost [127.0.0.1]) by yomiko.engr.nominum.com (8.12.6/8.9.3) with ESMTP id gAQIZsR6047943 for <dhcwg@ietf.org>; Tue, 26 Nov 2002 10:35:54 -0800 (PST)
Message-Id: <200211261835.gAQIZsR6047943@yomiko.engr.nominum.com>
To: dhcwg@ietf.org
In-reply-to: Your message of "Tue, 26 Nov 2002 12:00:02 EST." <20021126170002.8366.97332.Mailman@www1.ietf.org>
X-URI: http://www.nominum.com/
X-Face: 6K2.ZvQgQ.NDQLIx.1pW(xRu*">:}&PX-Ad_!!?wU7H4L"wF"0xEwYu=8Or0V+=5?-eO1XL 7-0Hom/|]B2C7Uznyol-NVnvEk:+sod^MyB4v4qVpPDemr; b@pZdRSXu.'Gm^t0?2l,j[&t.kbc[UW x6Lz^e$K$W
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset="US-ASCII"
Date: Tue, 26 Nov 2002 10:35:54 -0800
From: Eric Scanner Luce <Eric.Luce@nominum.com>
Subject: [dhcwg] Re: dhcwg digest, Vol 1 #410 - 2 msgs
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>
>>>>> "bh" == dhcwg-request <dhcwg-request@ietf.org> >>>>> wrote the following on Tue, 26 Nov 2002 12:00:02 -0500 bh> 5. altitude should be able to be specified to near-orbital bh> precision in 30 bits, but I wonder if latitude, longitude and bh> altitude is the best measure if devices are much above bh> passenger aviation levels? Again, I'm not sufficiently bh> conversant in the technology of location to know even what bh> system is used for, say, the lunar lander or a mars probe, let bh> alone what is sufficient precision, but it seems appropriate bh> to ask. While I do not think this is reasonable for a lunar lander or things that far out the amateur sattelite organization has shown that you can get GPS lock out beyond geo-sync orbit. We should at least include such altitudes -- although at this time a dhcp client on a satellite seems a bit far fetched we have seen stranger things come to pass. -- Scanner (scanner@nominum.com) Nominum, Inc. | www.nominum.com | +1.650.779.6035 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Re: dhcwg digest, Vol 1 #410 - 2 msgs Eric Scanner Luce