draft-ietf-netmod-iana-timezones-02.txt | draft-ietf-netmod-iana-timezones-03.txt | |||
---|---|---|---|---|
Network Working Group J. Lange | Network Working Group J. Lange | |||
Internet-Draft GE MDS LLC | Internet-Draft GE MDS LLC | |||
Intended status: Standards Track November 19, 2013 | Intended status: Standards Track December 3, 2013 | |||
Expires: May 23, 2014 | Expires: June 6, 2014 | |||
IANA Timezone Database YANG Module | IANA Timezone Database YANG Module | |||
draft-ietf-netmod-iana-timezones-02 | draft-ietf-netmod-iana-timezones-03 | |||
Abstract | Abstract | |||
This document defines the iana-timezones YANG module for timezone | This document defines the initial version of the iana-timezones YANG | |||
configuration. | module. The iana-timezones YANG module defines the iana-timezone | |||
type, which is a serialization of the existing IANA Time Zone | ||||
registry into YANG format. The document provides instructions to | ||||
IANA how to maintain the iana-timezones YANG module when the | ||||
underlying Time Zone registry is updated. | ||||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on May 23, 2014. | This Internet-Draft will expire on June 6, 2014. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2013 IETF Trust and the persons identified as the | Copyright (c) 2013 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 2, line 14 | skipping to change at page 2, line 24 | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
2. IANA Maintained Timezones YANG Module . . . . . . . . . . . . 2 | 2. IANA Maintained Timezones YANG Module . . . . . . . . . . . . 2 | |||
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 | 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 | |||
4. Security Considerations . . . . . . . . . . . . . . . . . . . 39 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 39 | |||
5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 39 | 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 39 | |||
5.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 39 | 5.1. 00-01 . . . . . . . . . . . . . . . . . . . . . . . . . . 39 | |||
5.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 39 | 5.2. 01-02 . . . . . . . . . . . . . . . . . . . . . . . . . . 39 | |||
6. Normative References . . . . . . . . . . . . . . . . . . . . 39 | 5.3. 02-03 . . . . . . . . . . . . . . . . . . . . . . . . . . 40 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 39 | 6. Normative References . . . . . . . . . . . . . . . . . . . . 40 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 40 | ||||
1. Introduction | 1. Introduction | |||
This document defines the iana-timezones YANG module for timezone | This document defines the initial version of the iana-timezones YANG | |||
configuration. | module [RFC6020]. The iana-timezones YANG module defines the iana- | |||
timezone type, which is a serialization of the existing IANA Time | ||||
The iana-timezones module reflects IANA's existing "timezone | Zone registry [RFC6557] into YANG format. Section 3 of this document | |||
database". The latest revision of the module can be obtained from | provides instructions to IANA how to maintain the iana-timezones YANG | |||
the IANA web site (http://www.iana.org/time-zones). | module when the underlying Time Zone registry is updated. | |||
Whenever a new timezone name is added to the IANA "timezone | The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
database", the iana-timezones module is updated by IANA. | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
"OPTIONAL" in this document are to be interpreted as described in BCP | ||||
14, [RFC2119]. | ||||
2. IANA Maintained Timezones YANG Module | 2. IANA Maintained Timezones YANG Module | |||
<CODE BEGINS> file "iana-timezones@2013-11-19.yang" | <CODE BEGINS> file "iana-timezones@2013-11-19.yang" | |||
module iana-timezones { | module iana-timezones { | |||
namespace "urn:ietf:params:xml:ns:yang:iana-timezones"; | namespace "urn:ietf:params:xml:ns:yang:iana-timezones"; | |||
prefix ianatz; | prefix ianatz; | |||
organization "IANA"; | organization "IANA"; | |||
skipping to change at page 38, line 18 | skipping to change at page 38, line 30 | |||
} | } | |||
<CODE ENDS> | <CODE ENDS> | |||
3. IANA Considerations | 3. IANA Considerations | |||
This document defines the initial version of the IANA-maintained | This document defines the initial version of the IANA-maintained | |||
iana-timezones YANG module. | iana-timezones YANG module. | |||
The iana-timezones module is intended to reflect the IANA "timezone | The iana-timezones module is intended to reflect the IANA "timezone | |||
database". When a timezone location is added to the database, the | database" [RFC6557]. When a timezone location is added to the | |||
"iana-timezone" enumeration MUST be updated as defined in RFC 6020 | database, the "iana-timezone" enumeration MUST be updated as defined | |||
Section 10 to add the newly created timezone location to the | in RFC 6020 Section 10 to add the newly created timezone location to | |||
enumeration. The new "enum" statement MUST be added to the "iana- | the enumeration. The new "enum" statement MUST be added to the | |||
timezone" typedef with the same name as the newly added timezone | "iana-timezone" typedef with the same name as the newly added | |||
location. A new enum value MUST be allocated by IANA and applied to | timezone location. A new enum value MUST be allocated by IANA and | |||
the newly created enum entry. New entries MAY be placed in any order | applied to the newly created enum entry. New entries MAY be placed | |||
in the enumeration as long as the previously assigned enumeration | in any order in the enumeration as long as the previously assigned | |||
values are not changed. | enumeration values are not changed. | |||
If a timezone location is removed from the IANA timezone database, | If a timezone location is removed from the IANA timezone database, | |||
the corresponding existing enum statement is kept and a status | the corresponding existing enum statement is kept and a status | |||
statement is added to mark the enum entry as 'obsolete'. | statement is added to mark the enum entry as 'obsolete'. | |||
If a timezone location is renamed in the IANA timezone database, a | If a timezone location is renamed in the IANA timezone database, a | |||
new enum is added with the new timezone name (as described above) and | new enum is added with the new timezone name (as described above) and | |||
the enum representing the old timezone name is kept but marked with a | the enum representing the old timezone name is kept but marked with a | |||
status statement declaring the enum as 'obsolete'. | status statement declaring the enum as 'obsolete'. | |||
skipping to change at page 39, line 39 | skipping to change at page 40, line 4 | |||
-- RFC Ed.: remove this section before publication. | -- RFC Ed.: remove this section before publication. | |||
5.1. 00-01 | 5.1. 00-01 | |||
o Updated timezone enumeration to match IANA timezone data v2013h | o Updated timezone enumeration to match IANA timezone data v2013h | |||
5.2. 01-02 | 5.2. 01-02 | |||
o Updated IANA considerations | o Updated IANA considerations | |||
o Removed old yang revisions | o Removed old yang revisions | |||
5.3. 02-03 | ||||
o Added additional normative references | ||||
o Updated Abstract and Introduction | ||||
6. Normative References | 6. Normative References | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | ||||
Requirement Levels", BCP 14, RFC 2119, March 1997. | ||||
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | |||
January 2004. | January 2004. | |||
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the | ||||
Network Configuration Protocol (NETCONF)", RFC 6020, | ||||
October 2010. | ||||
[RFC6557] Lear, E. and P. Eggert, "Procedures for Maintaining the | ||||
Time Zone Database", BCP 175, RFC 6557, February 2012. | ||||
Author's Address | Author's Address | |||
Jeffrey Lange | Jeffrey Lange | |||
GE MDS LLC | GE MDS LLC | |||
Email: jeffrey.k.lange@ge.com | Email: jeffrey.k.lange@ge.com | |||
End of changes. 12 change blocks. | ||||
26 lines changed or deleted | 48 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |