IETF Logo Mail Archive

Re: [dhcwg] Second dhc wg last call on "Time Protocol Servers and Time Offset Options for IPv6 DHCP"

Ralph Droms <rdroms@cisco.com> Tue, 06 June 2006 12:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnanq-0006HG-PE; Tue, 06 Jun 2006 08:36:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnanp-0006Fd-Q0 for dhcwg@ietf.org; Tue, 06 Jun 2006 08:36:57 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnaL3-0008C4-8X for dhcwg@ietf.org; Tue, 06 Jun 2006 08:07:13 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fna7T-0001vr-Ar for dhcwg@ietf.org; Tue, 06 Jun 2006 07:53:14 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-4.cisco.com with ESMTP; 06 Jun 2006 04:53:10 -0700
X-IronPort-AV: i="4.05,214,1146466800"; d="scan'208"; a="1820081234:sNHT32880030"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id k56BrAi9005088; Tue, 6 Jun 2006 04:53:10 -0700
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 k56BrAku010544; Tue, 6 Jun 2006 07:53:10 -0400 (EDT)
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 6 Jun 2006 07:53:09 -0400
Received: from 10.86.242.139 ([10.86.242.139]) by xmb-rtp-211.amer.cisco.com ([64.102.31.118]) with Microsoft Exchange Server HTTP-DAV ; Tue, 6 Jun 2006 11:53:09 +0000
User-Agent: Microsoft-Entourage/11.2.3.060209
Date: Tue, 06 Jun 2006 07:53:10 -0400
Subject: Re: [dhcwg] Second dhc wg last call on "Time Protocol Servers and Time Offset Options for IPv6 DHCP"
From: Ralph Droms <rdroms@cisco.com>
To: Eliot Lear <lear@cisco.com>, Stig Venaas <stig.venaas@uninett.no>
Message-ID: <C0AAE4E6.195E0%rdroms@cisco.com>
Thread-Topic: [dhcwg] Second dhc wg last call on "Time Protocol Servers and Time Offset Options for IPv6 DHCP"
Thread-Index: AcaJX8guBuSr5PVTEdqLXgARJOT6eg==
In-Reply-To: <44856933.6060407@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 06 Jun 2006 11:53:09.0857 (UTC) FILETIME=[C8184510:01C6895F]
DKIM-Signature: a=rsa-sha1; q=dns; l=1415; t=1149594790; x=1150458790; c=relaxed/simple; s=sjdkim3001; 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]=20Second=20dhc=20wg=20last=20call=20on=20=22Time=20Proto col=20Servers=20and=0A=20Time=20Offset=20Options=20for=20IPv6=20DHCP=22; X=v=3Dcisco.com=3B=20h=3DUACqK+6e9GWtKTwO8tmWK7g0EcI=3D; b=ARS4R1hZAoXgZoIazK+ihA5gUm+QBeOpnn119OkeqXaQTIx8QexH+DmaOlCo5EAb04r/XX+N j9rCO+R+m9kJBDQpXM4hGiCdE7Nv6+uGolvZpc1+nuA2Iq8ENmhW+gi3;
Authentication-Results: sj-dkim-3.cisco.com; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: dhcwg@ietf.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>
Errors-To: dhcwg-bounces@ietf.org

Eliot - CableLabs DOCSIS 3.0 specification will use both the RFC 868 servers
option and the time offset option.  While
draft-ietf-dhc-timezone-option-00.txt is likely a better solution than the
time offset option (for that matter, NTP would likely be an improvement over
NTP), DOCSIS 3.0 will specify RFC 868 time service and the DHCPv6 equivalent
of the time offset option for consistency with previous DOCSIS specs.

Therefore, I think we should continue with the definition of the time offest
option.

- Ralph


On 6/6/06 7:38 AM, "Eliot Lear" <lear@cisco.com> wrote:

> Stig Venaas wrote:
>> This messages announces a new wg last call on "Time Protocol Servers
>> and Time Offset Options for IPv6
>> DHCP"<draft-ietf-dhc-dhcpv6-rfc868-servers-00.txt>. The last call will
>> conclude at 1700 ET on 2006-06-20.
> This group has accepted a working group document that contains a better
> alternative to the time offset option.  I would support the advancing of
> the above draft with only the 868 servers, and otherwise ask that we
> defer this last call until we have a more clear result as to the other
> timezone draft (draft-ietf-dhc-timezone-option-00.txt).  Of course, it
> seems only fair in return that I do my best to make that draft the best
> it can be, so I will put out a new version shortly that removes
> suboptions and uses multiple options.
> 
> Thanks,
> 
> Eliot

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

v2.23.0 | Report a Bug | By Email