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

The brokenness of the time offset - lack of time to change offset 
information - can be fixed by adding options for NextOffset and 
nextChange, with advice that clients use the algorithm in 
http://www1.ietf.org/mail-archive/web/dhcwg/current/msg06029.html and 
get new options before the change after nextChange.

This approach was advocated, with compromise based on discussion at the 
last meeting and on the list, in 
http://www1.ietf.org/mail-archive/web/dhcwg/current/msg06114.html after 
being proposed in 
http://www1.ietf.org/mail-archive/web/dhcwg/current/msg05987.html.

John

On Jun 7, 2006, at 2:30 AM, Eliot Lear wrote:

> Ralph,
>
> To be clear...
>> 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.
>>
>
> draft-ietf-dhc-timezone-option-00.txt (and its soon to be released
> successor -01) both call for deprecation of time offset because it is
> broken.  To my knoweldge not a single general purpose computer
> implements it.  Is there anything we can do to get Cable Labs to
> reference the new work?  We should shortly be ready for WGLC.
>
> Eliot
>
> _______________________________________________
> 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