idnits 2.17.1 draft-ietf-dhc-timezone-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([2], [3], [4], [5], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 54: '... client MUST discard the value of th...' RFC 2119 keyword, line 55: '...Option. The DHCP client MAY notify the...' RFC 2119 keyword, line 60: '...misformatted, it SHOULD notify the the...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 1998) is 9597 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' Summary: 10 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. W. Carney 3 INTERNET-DRAFT Sun Microsystems, Inc. 4 draft-ietf-dhc-timezone-03.txt August 1997 5 Expires January 1998 7 DHCP Option for IEEE 1003.1 POSIX Timezone Specifications 8 10 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress''. 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 24 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 26 ftp.isi.edu (US West Coast). 28 Abstract 30 The Dynamic Host Configuration Protocol (DHCP) [1] provides a 31 framework for passing configuration information to hosts on a TCP/IP 32 network. This document defines a new option to extend the available 33 option codes [3]. 35 Introduction 37 DHCP includes an option for the specification of the Universal 38 Coordinated Time Offset [2], which is defined as a two's complement 39 32-bit integer representing the offset in seconds from UTC. 40 Unfortunately, the UTC offset option does not provide enough 41 information for an Internet client to determine such timezone-related 42 details as the timezone names, daylight savings time start and end 43 times in addition to the timezone UTC offsets. 45 This document defines a new option which addresses these 46 shortcomings by delivering timezone information in the form of a 47 1003.1 POSIX Timezone specifier [4]. Timely information regarding 48 timezones can be had at the U.S. Naval Observatory's web site [5]. 50 Timezone 0ption Precedence 52 If a DHCP client receives both the Time Offset (code 2) and the 53 POSIX Timezone (code 88) options in a DHCP reply message, the 54 client MUST discard the value of the Time Offset (code 2) option and 55 utilize the POSIX Timezone Option. The DHCP client MAY notify the 56 user that it is resolving the conflict by discarding the Time Offset 57 (code 2) option. 59 If a DHCP client finds that the POSIX Timezone option value is 60 misformatted, it SHOULD notify the the user of the problem and MUST 61 discard the entire option value. 63 Definition of option 88, IEEE 1003.1 POSIX Timezone 64 specifier 66 This NVT ASCII string represents the IEEE 1003.1 POSIX Timezone 67 specification that a client is to use to set its timezone. The 68 option code number is 88. 70 Code Len POSIX Timezone string 71 +-----+-----+-----+-----+-----+-----+--- 72 | 88 | n | a1 | a2 | a3 | a4 | ... 73 +-----+-----+-----+-----+-----+-----+--- 75 The format of the IEEE 1003.1 POSIX timezone specification is 76 defined as follows: 78 stdoffset[dst[offset],[start[/time],end[/time]]], where: 80 std, dst: three or more bytes for the standard timezone (std) and 81 daylight savings timezone (dst). If dst is missing, then 82 daylight savings time does not apply in this locale. Any 83 characters (or case) except a leading colon, digits, 84 comma, minus or plus sign are allowed. 86 offset: Indicates the value one must add to local time to arrive 87 at UTC, of the form: hh[:mm[:ss]]. offset following std 88 is required. If no offset follows dst, then dst is 89 assumed to be one hour ahead of standard time. Digits 90 always interpreted as decimal number. 92 hour: 0-23, minutes and seconds: 0-59. If preceded by a '-', 93 the timezone is east of the Prime Meridian, otherwise 94 it is west ('+' is optional) 96 start/time,end/time: Indicate when to change to and back from 97 daylight savings time. The 'time' field indicates when, 98 in local time, the change is made. 100 start, end: 102 Jn: The julian day n, (1 <= n <= 365). Leap days 103 not counted. 105 n: zero-based julian day, (0 <= n <= 365). Leap 106 days are counted so it is possible to refer to 107 Feb 29. 109 Mm.n.d: The 'd'th day, (0 <= d <= 6) of week 'n' of 110 month 'm' of the year (1 <= n <= 5, 1 <= m <= 12, 111 where week 5 means last 'd' day in month 'm' 112 which may occur in either the fourth or the fifth 113 week. Week '1' is the first week in which the 'd' 114 day occurs. 116 time: time has the same format as offset, except that 117 no leading '-' or '+' is permitted. The default 118 is 02:00:00. 120 An Example 121 Eastern USA time zone, 1986: 123 EST5EDT4,116/02:00:00,298/02:00:00 125 References 127 [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, 128 Bucknell University, March 1997. 130 [2] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 131 Extensions", RFC 2132, Lachman Associates, March 1997 133 [3] Droms, R., "Procedure for Defining New DHCP Options", Work in 134 progress, February, 1996. 136 [4] IEEE, "1003.1 POSIX Timezone Specification", 1988. 138 [5] http://tycho.usno.navy.mil, "U.S. Naval Observatory" 140 Security Considerations 142 DHCP currently provides no authentication or security mechanisms. 143 Potential exposures to attack are discussed in section 7 of the 144 DHCP protocol specification [1]. 146 Author's Address 148 Mike Carney 149 Sun Microsystems, Inc. 150 2 Elizabeth Drive 151 Chelmsford, MA 01824 153 Phone: (508) 442-0469 154 EMail: Mike.Carney@East.Sun.COM