Re: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt
Eliot Lear <lear@cisco.com> Mon, 14 August 2006 06:40 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCW7Q-0002yK-Ke; Mon, 14 Aug 2006 02:40:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCW7O-0002yF-TW for dhcwg@ietf.org; Mon, 14 Aug 2006 02:40:10 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GCW7N-0001kY-Fl for dhcwg@ietf.org; Mon, 14 Aug 2006 02:40:10 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-4.cisco.com with ESMTP; 13 Aug 2006 23:40:09 -0700
X-IronPort-AV: i="4.08,119,1154934000"; d="scan'208"; a="1846682614:sNHT32775144"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k7E6e8Nh010929; Sun, 13 Aug 2006 23:40:08 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k7E6e8UJ016989; Sun, 13 Aug 2006 23:40:08 -0700 (PDT)
Received: from [212.254.247.4] (ams3-vpn-dhcp4137.cisco.com [10.61.80.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k7E6W8Z3020620; Sun, 13 Aug 2006 23:32:09 -0700
Message-ID: <44E01AC9.6080601@cisco.com>
Date: Mon, 14 Aug 2006 08:40:09 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719)
MIME-Version: 1.0
To: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt
References: <23FE5FF5-6782-4764-A4C5-4D7253DC5C6D@cisco.com> <79EE3382-C065-4430-8F57-936F7D0BE00F@cisco.com>
In-Reply-To: <79EE3382-C065-4430-8F57-936F7D0BE00F@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Authentication-Results: sj-dkim-3.cisco.com; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com verified; );
DKIM-Signature: a=rsa-sha1; q=dns; l=4009; t=1155537608; x=1156401608; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:Eliot=20Lear=20<lear@cisco.com> |Subject:Re=3A=20[dhcwg]=20dhc=20WG=20last=20call=20on=20draft-ietf-dhc-timezone- option-02.txt; X=v=3Dcisco.com=3B=20h=3DNmywc0lSNMM/2u5LYmbtnRA/3CE=3D; b=bP0l9Vaut5xhprTnK+IHNMg7oHVmVmM1orqySkejgOoT1wz+UWKYPTBN1LC8j0uL433heBHX o5BmQWxUqC+/a68LGBJWQ0AnCVBvvfhln59QiZjpIJa0Euq2ZCTPVD6H;
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: dhcwg@ietf.org, Paul Eggert <eggert@CS.UCLA.EDU>
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
Hi Ralph, First, thanks for your comments. Please see below. Ralph Droms wrote: > 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. I propose to do this using the classic "related work" heading at the bottom of the introduction. > > Here is some suggested text for the Abstract and Introduction: Thank you for the suggested text. The RFC Editor strongly objects to text in the abstract that is simply copied from the introduction. As such I would prefer to leave the abstract unchanged, or I would accept other alternate text. > > 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)? Microsoft also has a database, but one can vary from it without grief because POSIX provides sufficient information to populate the registry. > > 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? Fixed. > > 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. Fixed. > > Section 7.1: I don't see any need or advantage to deprecate the > previous time offset option. My argument remains as follows: * the offset is broken for the reasons described in the introduction; * the reason I'm writing this in the first place is to provide a correct approach; * having fewer ways to accomplish a task is better. On that last point, it is quite possible to derive offset information from the POSIX option without *too much* effort. > > Section 10: missing space after "Dusseault," Fixed. > > 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. > Added. Thanks again, Eliot _______________________________________________ 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