Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6

"David W. Hankins" <David_Hankins@isc.org> Mon, 19 November 2007 22:10 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuEoh-0000zK-Nm; Mon, 19 Nov 2007 17:10:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuEoh-0000zF-5V for dhcwg@ietf.org; Mon, 19 Nov 2007 17:10:07 -0500
Received: from [2001:4f8:3:bb::1:ee8b] (helo=goliath.isc.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuEod-0006BR-HK for dhcwg@ietf.org; Mon, 19 Nov 2007 17:10:07 -0500
Received: by goliath.isc.org (Postfix, from userid 10200) id A380E5A6ED; Mon, 19 Nov 2007 14:09:58 -0800 (PST)
Date: Mon, 19 Nov 2007 14:09:58 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6
Message-ID: <20071119220958.GH14750@isc.org>
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <4733482A.7020302@sun.com> <A05118C6DF9320488C77F3D5459B17B70634E4E5@xmb-ams-333.emea.cisco.com> <4735A243.6090905@sun.com> <47368636.3070007@udel.edu> <47410A17.8090503@ntp.org> <47411C6D.1010808@udel.edu>
Mime-Version: 1.0
In-Reply-To: <47411C6D.1010808@udel.edu>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ntpwg@lists.ntp.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1362810539=="
Errors-To: dhcwg-bounces@ietf.org

On Mon, Nov 19, 2007 at 05:17:33AM +0000, David L. Mills wrote:
> server and receives a response. There is an opportunity for the DHCP 
> client to measure the delay, should it be so instrumented. In no way did 

I'm not aware of any DHCP message exchanges that are suitable for
RTT measurements in any meaningful way.

Many DHCP message exchanges require physical flushes to disc or other
similar recoverable storage before replying, and in other messages
servers may engage in additional behaviours that rely on additional
RTTs (such as Dynamic DNS updates), or timeouts (such as with ICMP
echoes).

I can go into detail if you wish, but I personally would not use
even the informational messages for any kind of meaningful time
derivation (since even with informational messages, the server may
perform recursive DNS resolution of names in its configuration in
order to deliver IP addresses over DHCP).

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg