Re: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt
Ralph Droms <rdroms@cisco.com> Sun, 13 August 2006 11:11 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCDrx-0006t7-NV; Sun, 13 Aug 2006 07:11:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCDrw-0006t1-18 for dhcwg@ietf.org; Sun, 13 Aug 2006 07:11:00 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GCDrt-0006TY-NI for dhcwg@ietf.org; Sun, 13 Aug 2006 07:11:00 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 13 Aug 2006 07:10:57 -0400
X-IronPort-AV: i="4.08,118,1154923200"; d="scan'208"; a="96553766:sNHT35315364"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k7DBAvlK001083 for <dhcwg@ietf.org>; Sun, 13 Aug 2006 07:10:57 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k7DBAvdp004942 for <dhcwg@ietf.org>; Sun, 13 Aug 2006 07:10:57 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 13 Aug 2006 07:10:57 -0400
Received: from [192.168.1.103] ([10.86.242.17]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 13 Aug 2006 07:10:56 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <23FE5FF5-6782-4764-A4C5-4D7253DC5C6D@cisco.com>
References: <23FE5FF5-6782-4764-A4C5-4D7253DC5C6D@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <79EE3382-C065-4430-8F57-936F7D0BE00F@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt
Date: Sun, 13 Aug 2006 07:11:05 -0400
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 13 Aug 2006 11:10:56.0669 (UTC) FILETIME=[264974D0:01C6BEC9]
DKIM-Signature: a=rsa-sha1; q=dns; l=2895; t=1155467457; x=1156331457; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:Ralph=20Droms=20<rdroms@cisco.com> |Subject:Re=3A=20[dhcwg]=20dhc=20WG=20last=20call=20on=20draft-ietf-dhc-timezone- option-02.txt |To:dhcwg@ietf.org; X=v=3Dcisco.com=3B=20h=3D9k2ewAbF9LPC5OdKr1MKjLyrNxw=3D; b=DRG+UZQg1TqIm2q41/1Li/Gw8aFAxrjEzCYzlCyrhWf8tbM7GisuBQFkmP02cKoHToJj5fgO L6mt6VG5Byip3Y45gLgn8iplG8HJwt2KEhBooxbnBP3llX5tXWXRJ49F;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
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>
Errors-To: dhcwg-bounces@ietf.org
Comments (with WG chair hat off) on draft-ietf-dhc-timezone- option-02.txt: I think the references to "prior art", including the existing DHCP offset option and VTIMEZONE, should be moved to a separate section at the end of the document. I also think text marketing this option as an improvement to the existing DHCP offset option in the body of the document are unnecessary. A simple sentence outlining the problems with the offset option in the "prior art" section should suffice. Here is some suggested text for the Abstract and Introduction: Abstract This document defines new options for DHCPv4 and DHCPv6 through which a DHCP server can indicate what timezone a DHCP client should use in determining its local time. The timezone information is used to determine the offset between UTC and local time for the client. 1. Introduction This defines new options for DHCPv4 and DHCPv6 through which DHCP hosts can be provided with accurate timezone information. There are currently two well known means to configure timezones: o POSIX TZ strings o Reference to the TZ Database Are these the only two well known means to configure timezones? What about the Microsoft option (which has been removed from this document)? POSIX [1] provides a standard for how to express timezone information in a character string. Use of such a string can provide accuracy for at least one transition into and out of daylight saving time (DST), and possibly for more transitions if the transitions are regular enough (e.g., "second Sunday in March at 02:00 local time"). However, for accuracy over longer periods, that involve daylight-saving rule changes or other irregular changes, a more detailed mechanism is necessary. The so-called "TZ Database" [6] that is used in many operating ^^^^^^^^^^^^^^^^^^^^^^^ Why use "so-called", which (to my mind, anyway) diminishes the credibility? systems provides backwards consistency and accuracy for almost all real-world locations since 1970. The TZ database also attempts to provide a stable set of human readable timezone identifiers. In addition, many systems already make use of the TZ database, and so the names used are a defacto standard. Sections 4 and 5: eliminate double quotes from example or specifically note that the double quotes are not included in the data on-the-wire. Section 7.1: I don't see any need or advantage to deprecate the previous time offset option. Section 10: missing space after "Dusseault," Mention that configuration of the TZ database is explicitly out-of- scope of this document, in conjunction with this sentence in section 5: In order for this option to be useful, the client must already have a copy of the database. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhc WG last call on draft-ietf-dhc-timezo… Ralph Droms
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… David W. Hankins
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Ted Lemon
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Shane Kerr
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Mark Stapp
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… H. Peter Anvin
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Eliot Lear
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Mark Stapp
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… John Schnizlein
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… John Schnizlein
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Ted Lemon
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Eliot Lear
- RE: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Bernie Volz (volz)
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Ralph Droms
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Eliot Lear
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Ralph Droms
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-ti… Eliot Lear