Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-option-02.txt
Eliot Lear <lear@cisco.com> Wed, 19 July 2006 07:40 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G36f6-0004AP-P6; Wed, 19 Jul 2006 03:40:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G36f5-0004AJ-E5 for dhcwg@ietf.org; Wed, 19 Jul 2006 03:40:03 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G36f4-0006GD-4f for dhcwg@ietf.org; Wed, 19 Jul 2006 03:40:03 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 19 Jul 2006 00:40:02 -0700
X-IronPort-AV: i="4.06,257,1149490800"; d="scan'208"; a="1839780064:sNHT25185858"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6J7e1lF010065; Wed, 19 Jul 2006 00:40:01 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k6J7e179025027; Wed, 19 Jul 2006 00:40:01 -0700 (PDT)
Received: from [212.254.247.5] (ams3-vpn-dhcp4206.cisco.com [10.61.80.109]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k6J7XcNl029880; Wed, 19 Jul 2006 00:33:39 -0700
Message-ID: <44BDE1CF.4090506@cisco.com>
Date: Wed, 19 Jul 2006 09:39:59 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-option-02.txt
References: <E1G2vZx-0000jw-Sn@stiedprstage1.ietf.org> <23d03dbc02d24f0df7afd775bffe0f43@cisco.com>
In-Reply-To: <23d03dbc02d24f0df7afd775bffe0f43@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Authentication-Results: sj-dkim-5.cisco.com; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com verified; );
DKIM-Signature: a=rsa-sha1; q=dns; l=1899; t=1153294801; x=1154158801; c=relaxed/simple; s=sjdkim5002; 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]=20I-D=20ACTION=3Adraft-ietf-dhc-timezone-option-02.txt; X=v=3Dcisco.com=3B=20h=3DQgNJbeSoH0NpXaAbYxqhOnP16GA=3D; b=kHrWleEuo0F0rDyIMIBhGu/uR5gSj3pxVycDFvPbOI4pcefMZLn85AsQ5ke8cS43CUPmeYpo g7pXXOStrQJnKMzI8sdoqGqYTAnJ1PB9YRGFwP1GNQHhFRRUxbwI6FrV;
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: DHCP discussion list <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
John, Thanks for your contributions to this discussion. > Unfortunately, it still contains the following unnecessary text, which > conflicts with existing practice and section 4 of > draft-ietf-dhc-dhcpv6-rfc868-servers-00.txt, which was the subject of > a WG last call from June 6 to June 20. It does no harm to continue > the existing practice, although operational use of the existing offset > option could be improved by providing options for when to change the > offset and to what to change it. What is the benefit of deprecating > what is in use? My sense is that you are correct that there is not yet consensus for the existing text. Perhaps now is a good time to try and come to consensus, and I would ask the chairs for their assistance. I have two concerns: * First, the existing mechanism is broken and cannot handle DST transitions nor can it easily integrate with such general purpose platforms as Microsoft Windows, UNIX, and some Java stacks. This is the reason Paul and I wrote the draft in the first place. * Second, once one arrives at the first conclusion as a matter of best practice - and I do believe there is consensus on that point, if one has developed a better alternative, that is the alternative that should be recommended, and not a menu of approaches. A menu has the nasty habit of only working sometimes in the best of circumstances, and having bad interactions in the worst. I am of course well aware that there will be a long slow transition in some cases from the existing option. And so I believe deprecation of the time offset option is appropriate. Shane has graciously offered some alternative wording to make the text a bit less confusing. I am happy to see further improvements if you believe we could better convey the above points. Eliot _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-option… Internet-Drafts
- Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-op… John Schnizlein
- Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-op… Shane Kerr
- Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-op… Eliot Lear
- Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-op… Ted Lemon
- Re: [dhcwg] I-D ACTION:draft-ietf-dhc-timezone-op… David W. Hankins