IETF Logo Mail Archive

RE: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt

"Bernie Volz \(volz\)" <volz@cisco.com> Sat, 12 August 2006 20:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GC067-0007PJ-N8; Sat, 12 Aug 2006 16:28:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GC066-0007PE-Vi for dhcwg@ietf.org; Sat, 12 Aug 2006 16:28:42 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GC065-00068C-MP for dhcwg@ietf.org; Sat, 12 Aug 2006 16:28:42 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 12 Aug 2006 13:28:41 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.08,117,1154934000"; d="scan'208"; a="35827772:sNHT32278072"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k7CKSfEn012236 for <dhcwg@ietf.org>; Sat, 12 Aug 2006 16:28:41 -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 k7CKSedp023894 for <dhcwg@ietf.org>; Sat, 12 Aug 2006 16:28:40 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 12 Aug 2006 16:28:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt
Date: Sat, 12 Aug 2006 16:28:40 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21020312B4@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] dhc WG last call on draft-ietf-dhc-timezone-option-02.txt
Thread-Index: Aca7zi/Avy+545d9ReaQ8GK5bzESQgCfnyLQ
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, dhcwg@ietf.org
X-OriginalArrivalTime: 12 Aug 2006 20:28:41.0006 (UTC) FILETIME=[E62C4CE0:01C6BE4D]
DKIM-Signature: a=rsa-sha1; q=dns; l=2093; t=1155414521; x=1156278521; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com> |Subject:RE=3A=20[dhcwg]=20dhc=20WG=20last=20call=20on=20draft-ietf-dhc-timezone- option-02.txt |To:=22Ralph=20Droms=20\(rdroms\)=22=20<rdroms@cisco.com>, =20<dhcwg@ietf.org >; X=v=3Dcisco.com=3B=20h=3DJbc7ndhja6iQyl6pIRHq8wQnUMw=3D; b=FI13ugfDVWAJpJQm5BKr9g6JM3sLZeAJ9vW5+H/HUX54Ai3iu+uFe5j6FQdXVOzxxKM+/nW0 nRxfsj0CMBbFMqAj1WNMv7hnrOOdmNlvyrcm10ybPC6RMTFSWt1IzoQS;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc:
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

With the previously mentioned edits (critical ones below), I AM in FAVOR
of advancing this draft.


In Section 2, New Timezone Options for DHCPv4:

OLD:

  The following three options are defined for DHCPv4:

NEW:

  The following two options are defined for DHCPv4:
                ^^^
---

OLD:

   Len is the two-octet value of the length of the succeeding string for
   each option.

NEW:

   Len is the one-octet value of the length of the succeeding string for
              ^^^
   each option.

---

Optionally, you may want to reference RFC 3396, but I don't think there
is a need.

---

And, there is the discussion Shane/Eliot/Mark had regrading the DHCPv4
client transition issues (old vs new timezone options). However they
decide regarding that is fine by me.

- Bernie

-----Original Message-----
From: Ralph Droms (rdroms) 
Sent: Wednesday, August 09, 2006 12:09 PM
To: dhcwg@ietf.org
Subject: [dhcwg] dhc WG last call on
draft-ietf-dhc-timezone-option-02.txt

This message announces a WG last call on "A Timezone Option for DHCP"
<draft-ietf-dhc-timezone-option-02.txt>.  The last call will conclude
at 1700EDT on Wed, 2006-08-16.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.  If there is no expression of support for
acceptance during the WG last call, the document will not be advanced
to the IESG.

draft-ietf-dhc-timezone-option-02.txt specifies new options for both
DHCPv4 and DHCPv6 to provide hosts with accurate timezone
information, using the following two means to configure timezones:
    o  POSIX TZ strings
    o  Reference to the TZ Database.
This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-timezone- 
option-02.txt

- Ralph Droms

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email