[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-lear-dhc-timezone-option) 00 01 02 03 04 05 RFC 4833

Network Working Group                                            E. Lear
Internet-Draft                                        Cisco Systems GmbH
Updates: 2132 (if approved)                                    P. Eggert
Expires: December 8, 2006                                           UCLA
                                                            June 6, 2006


                       A Timezone Option for DHCP
                 draft-ietf-dhc-timezone-option-01.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 8, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   DHCP defines an option for a server to deliver to a client offset
   from UTC.  This information in and of itself is not sufficient for
   devices to portray local time both accurately and consistently.  This
   memo specifies new options for both DHCPv4 and DHCPv6 to do so.






Lear & Eggert           Expires December 8, 2006                [Page 1]


Internet-Draft         A Timezone option for DHCP              June 2006


1.  Introduction

   Dynamic Host Configuration Protocol (DHCP) [2] provides a means for
   hosts to receive configuration information relating to their current
   location within an IP version 4 network. [4] similarly does so for IP
   version 6 networks.  RFC2132 [3] specifies an option to provide a
   client timezone information in the form of an offset in seconds from
   UTC.  The information provided in that option is insufficient for the
   client to determine whether it is in daylight saving time and when to
   change into and out of daylight saving time (DST).  In order for the
   client to properly represent local wall clock time in a consistent
   and accurate fashion the DHCP server would have to time lease
   expirations of affected clients to the beginning or end of DST, thus
   effecting a self stress test (to say the least) at the appointed
   hour.

   In addition, an offset is not sufficient to determine the actual
   timezone in which a client resides, and thus there is no means to
   derive a human readable display string such as "EST" or "EDT".

   This memo specifies a means to provide hosts with more accurate
   timezone information than was previously available.  There are
   currently three well known means to configure timezones:
   o  POSIX TZ strings
   o  Reference to the TZ Database
   o  Microsoft's timezone.xml

   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, 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
   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.

   The Microsoft TimeZone element conveys information similar to the
   POSIX string, but with an additional (presumably localized) display
   string.





Lear & Eggert           Expires December 8, 2006                [Page 2]


Internet-Draft         A Timezone option for DHCP              June 2006


1.1.  What about VTIMEZONE elements from iCalendar?

   VTIMEZONE elements are defined in the iCalendar specification.[8]
   Fully specified they provide a level of accuracy similar to the TZ
   database.  However, because there is currently no global registry of
   VTIMEZONE TZIDs (although one has been proposed; see [9]), complete
   accuracy requires that a full entry must be specified.  To achieve
   the same information would range from 300 octets upwards with no
   particular bound.  Furthermore, at the time of this writing the
   author is aware of no operating system that natively takes advantage
   of VTIMEZONE entries.  It might be possible to include an option for
   a TZURL.  However, in a cold start environment, it will be bad enough
   that devices are stressing the DHCP server, and perhaps unwise to
   similarly afflict other components.


2.  New Timezone Options for DHCPv4

   The following three options are defined for DHCPv4:


            PCode  Len   TZ-POSIX String
           +-----+-----+------------------------------+
           | TBD |  N  | IEEE 1003.1 String           |
           +-----+-----+------------------------------+

            TCode  Len   TZ-Database String
           +-----+-----+------------------------------+
           | TBD |  N  | Reference to the TZ Database |
           +-----+-----+------------------------------+

            MCode  Len   TZ-Microsoft Index
           +-----+-----+------------------------------+
           | TBD |  N  | Microsoft TZID               |
           +-----+-----+------------------------------+


   PCode, TCode, and MCode are TBD and will be allocated by IANA
   according to RFC-2939 [5].

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

   The string values that follow Len are described below.  Note that
   they are NOT terminated by an ASCII NULL.






Lear & Eggert           Expires December 8, 2006                [Page 3]


Internet-Draft         A Timezone option for DHCP              June 2006


3.  New Timezone Option for DHCPv6

   The semantics and content of the DHCPv6 encoding of this option are
   exactly the same as the encoding described for DHCPv4, other than
   necessary differences between the way options are encoded in DHCPv4
   and DHCPv6.

   Specifically, the DHCPv6 new timezone options are described below:


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  OPTION_NEW_POSIX_TIMEZONE    |         option-length         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                      TZ POSIX String                          |
      |                              ...                              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


   option-code: OPTION_NEW_POSIX_TIMEZONE(TBD)

   option-length: length of the TZ POSIX String described below.

   option-length: the number of octets of the TZ POSIX String Index
   described below.


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  OPTION_NEW_TZDB_TIMEZONE    |          option-length         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     TZ Database String                        |
      |                              ...                              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


   option-code: OPTION_NEW_TZDB_TIMEZONE(TBD)

   option-length: the number of octets of the TZ Database String Index
   described below.









Lear & Eggert           Expires December 8, 2006                [Page 4]


Internet-Draft         A Timezone option for DHCP              June 2006


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  OPTION_NEW_MS_TIMEZONE       |         option-length         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Microsoft TZID                         |
      |                              ...                              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


   option-code: OPTION_NEW_MS_TIMEZONE(TBD)

   option-length: the number of octets of the Microsoft TZ ID described
   below.


4.  The TZ POSIX String

   POSIX string is a string suitable for the TZ variable as specified by
   [1] in Section 8.3, with the exception that a string may not begin
   with a colon (":").  This string is NOT terminated by an ASCII NULL.
   An example might be as follows:

   "EST5EDT4,M3.2.0/02:00,M11.1.0/02:00"

   In this case, the string is interpreted as a timezone that is
   normally five hours behind UTC, and four hours behind UTC during DST,
   which runs from the second Sunday in March at 02:00 local time
   through the first Sunday in November at 02:00 local time.  Normally
   the timezone is abbreviated "EST" but during DST it is abbreviated
   "EDT".

   Clients and servers implementing other timezone options MUST support
   this suboption for basic compatability.


5.  The TZ Database String

   TZ Name is the name of a Zone entry in the database commonly referred
   to as the TZ database.  In order for this option to be useful, the
   client must already have a copy of the database.  This string is NOT
   terminated with an ASCII NULL.

   An example string would be "Europe/Zurich".

   A client that supports this option SHOULD prefer this option to POSIX
   string if it recognizes the TZ Name that was returned.  If it doesn't
   recognize the TZ Name the client MUST ignore this option.



Lear & Eggert           Expires December 8, 2006                [Page 5]


Internet-Draft         A Timezone option for DHCP              June 2006


6.  The Microsoft TZ ID

   TZ ID is a four-octet integer in network byte order that references
   the timezone ID as defined in the TimeZone element, as specified by
   Microsoft [7].

   A client that supports this option SHOULD prefer this option to the
   POSIX string if it recognizes the TZ ID that was returned by the
   server.  If it doesn't recognize the TZ ID the client MUST ignore
   this option.


7.  Use of the timezone string(s) returned from the server

   This specification presumes the DHCP server has some means of
   identifying which timezone the client is in.  One obvious approach
   would be to associate a subnet or group of subnets with a timezone,
   and respond with this option accordingly.

   As a matter of practicality the client will use this information at
   its discretion to configure the current timezone in which it resides.

   It will periodically be necessary for a DHCP server to update the
   timezone string, based on administrative changes made by local
   jurisdictions (say, for instance, counties in Indiana).  While the
   authors do not expect this to be a lower bound on a lease time in the
   vast majority of cases, there may be times when anticipation of a
   change dictates prudence, as certain governments give little if any
   notification.


8.  The New Timezone Option and Lease times

   When a lease has expired and new information is not forthcoming, the
   client MAY continue to use timezone information returned by the
   server.  This follows the principle of least astonishment.

8.1.  Deprecation of Time Offset Option

   Because this option provides a superset of functionality to the
   previous IPv4 time offset option (tag 2), and in order to maintain
   consistency between IPv4 and IPv6 implementation, the older option is
   deprecated.  Implementations of the time offset IPv4 option SHOULD
   implement this option as well.  Others SHOULD instead implement this
   option.






Lear & Eggert           Expires December 8, 2006                [Page 6]


Internet-Draft         A Timezone option for DHCP              June 2006


9.  Security Considerations

   An attacker could provide erroneous information to a client.  It is
   possible that someone might miss a meeting or otherwise show up
   early.  If clients have job processing tools such as cron that
   operate on wall clock time it is possible that certain jobs could be
   triggered either earlier or later, or even repeated or skipped
   entirely if scheduled during a DST transition.  In such cases, the
   client operating system might do well to confirm timezone changes
   with a human.

   Clients using the POSIX option should beware of any time zone setting
   specifying unusual characters (e.g., control characters) in the
   standard or daylight-saving abbreviations, as this might well trigger
   security-relevant bugs in applications.

   Clients using the POSIX option should also be suspicious of any time
   zone setting whose UTC offset exceeds 25 hours (the POSIX limit, if
   the default daylight-saving offset is used).  As of this writing, the
   maximum UTC offset is 14 hours in practice, but governments may
   extend this somewhat in the future.


10.  IANA Considerations

   The IANA is requested to allocate DHCPv4 and DHCPv6 option codes for
   this purpose and reference this document in those allocations for
   both DHCPv4 and DHCPv6.

   The IANA is requested to annotate the time offset IPv4 option (tag 2)
   as deprecated, with a reference to this memo.


11.  Acknowledgments

   This document specifies a means to exchange timezone information.
   The hard part is actually collecting changes to the various databases
   from scattered sources around the world.  The many volunteers on the
   mailing list tz@elsie.nci.nih.gov have done this nearly thankless
   task for many years.  Thanks also go to Ralph Droms, Bernie Volz, Ted
   Lemon, Lisa Dusseault,and Simon Vaillancourt for their attempts to
   improve this work.


12.  References






Lear & Eggert           Expires December 8, 2006                [Page 7]


Internet-Draft         A Timezone option for DHCP              June 2006


12.1.  Normative References

   [1]  "Standard for Information Technology - Portable Operating System
        Interface (POSIX) - Base Definitions", IEEE Std 1003.1-2004,
        December 2004.

   [2]  Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
        March 1997.

   [3]  Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
        Extensions", RFC 2132, March 1997.

   [4]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.
        Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
        RFC 3315, July 2003.

   [5]  Droms, R., "Procedures and IANA Guidelines for Definition of New
        DHCP Options and Message Types", BCP 43, RFC 2939,
        September 2000.

   [6]  Eggert, P. and A. Olson, "Sources for Time Zone and Daylight
        Saving Time Data", <http://www.twinsun.com/tz/tz-link.htm>.

   [7]  "The Microsoft TimeZone Element",
        <http://msdn.microsoft.com/library/>.

12.2.  Informational References

   [8]  Dawson, F. and Stenerson, D., "Internet Calendaring and
        Scheduling Core Object Specification (iCalendar)", RFC 2445,
        November 1998.

   [9]  Royer, D., "Time Zone Registry",
        draft-royer-timezone-registry-03 (work in progress),
        August 2005.


Appendix A.  Changes

   [The RFC Editor is requested to remove this section at publication.]
   o  -01: change from suboptions to options
   o  -00 (WG submission): add length field to Microsoft suboption,
      clarifying text about when to prefer which suboption, indicate
      that the POSIX string is NOT null terminated; add additional
      justification; add deprecation text; remove extraneous text that
      says that this document will not prescribe client behavior
      regarding multiple options (we just did).




Lear & Eggert           Expires December 8, 2006                [Page 8]


Internet-Draft         A Timezone option for DHCP              June 2006


   o  -02: fix references to the TZ database; add additional security
      considerations; clarify POSIX example; reference Doug Royer
      registry draft; add Paul Eggert as co-author(who did all the
      above)
   o  -01: clarify uses of each suboption; reset suboption sizes; add
      explanation for not using VTIMEZONEs; add acknowlegments.
   o  initial revision












































Lear & Eggert           Expires December 8, 2006                [Page 9]


Internet-Draft         A Timezone option for DHCP              June 2006


Authors' Addresses

   Eliot Lear
   Cisco Systems GmbH
   Glatt-com
   Glattzentrum, ZH  CH-8301
   Switzerland

   Phone: +41 1 878 9200
   Email: lear@cisco.com


   Paul Eggert
   UCLA
   Computer Science Department
   4532J Boelter Hall
   Los Angeles, CA  90095
   USA

   Phone: +1 310 825 3886
   Email: eggert@cs.ucla.edu






























Lear & Eggert           Expires December 8, 2006               [Page 10]


Internet-Draft         A Timezone option for DHCP              June 2006


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Lear & Eggert           Expires December 8, 2006               [Page 11]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/