draft-ietf-netmod-iana-timezones-01.txt		draft-ietf-netmod-iana-timezones-02.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 12, 2013		Intended status: Standards Track November 19, 2013
	Expires: May 16, 2014		Expires: May 23, 2014
	IANA Timezone Database YANG Module		IANA Timezone Database YANG Module
	draft-ietf-netmod-iana-timezones-01		draft-ietf-netmod-iana-timezones-02
	Abstract		Abstract
	This document defines the iana-timezones YANG module for timezone		This document defines the iana-timezones YANG module for timezone
	configuration.		configuration.
	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.
	skipping to change at page 1, line 31		skipping to change at page 1, line 31
	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 16, 2014.		This Internet-Draft will expire on May 23, 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 13		skipping to change at page 2, line 13
	described in the Simplified BSD License.		described in the Simplified BSD License.
	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
	6. Normative References . . . . . . . . . . . . . . . . . . . . 39		6. Normative References . . . . . . . . . . . . . . . . . . . . 39
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 39		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 39
	1. Introduction		1. Introduction
	This document defines the iana-timezones YANG module for timezone		This document defines the iana-timezones YANG module for timezone
	configuration.		configuration.
	The iana-timezones module reflects IANA's existing "timezone		The iana-timezones module reflects IANA's existing "timezone
	database". The latest revision of the module can be obtained from		database". The latest revision of the module can be obtained from
	the IANA web site (http://www.iana.org/time-zones).		the IANA web site (http://www.iana.org/time-zones).
	Whenever a new timezone name is added to the IANA "timezone		Whenever a new timezone name is added to the IANA "timezone
	database", the iana-timezones module is updated by IANA.		database", the iana-timezones module is updated by IANA.
	2. IANA Maintained Timezones YANG Module		2. IANA Maintained Timezones YANG Module
	<CODE BEGINS> file "iana-timezones@2013-11-12.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";
	contact		contact
	" Internet Assigned Numbers Authority		" Internet Assigned Numbers Authority
	Postal: ICANN		Postal: ICANN
	skipping to change at page 3, line 20		skipping to change at page 3, line 23
	Redistribution and use in source and binary forms, with or		Redistribution and use in source and binary forms, with or
	without modification, is permitted pursuant to, and subject		without modification, is permitted pursuant to, and subject
	to the license terms contained in, the Simplified BSD License		to the license terms contained in, the Simplified BSD License
	set forth in Section 4.c of the IETF Trust's Legal Provisions		set forth in Section 4.c of the IETF Trust's Legal Provisions
	Relating to IETF Documents		Relating to IETF Documents
	(http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX; see		This version of this YANG module is part of RFC XXXX; see
	the RFC itself for full legal notices.";		the RFC itself for full legal notices.";
	revision 2013-11-12 {		revision 2013-11-19 {
	description		description
	"Updated to use IANA Time Zone Data v. 2013h		"Initial revision using IANA Time Zone Data v. 2013h
	(Released 2013-10-25)";		(Released 2013-10-25)";
	reference "RFC XXXX: TITLE";		reference "RFC XXXX: TITLE";
	}		}
	revision 2012-07-09 {
	description
	"Initial revision. Using IANA Time Zone Data v. 2012c
	(Released 2012-03-27)";
	reference "RFC XXXX: TITLE";
	}
	typedef iana-timezone {		typedef iana-timezone {
	description		description
	"A timezone location as defined by the IANA timezone		"A timezone location as defined by the IANA timezone
	database (http://www.iana.org/time-zones)";		database (http://www.iana.org/time-zones)";
	type enumeration {		type enumeration {
	enum "Europe/Andorra" {		enum "Europe/Andorra" {
	value 0;		value 0;
	}		}
	enum "Asia/Dubai" {		enum "Asia/Dubai" {
	skipping to change at page 38, line 31		skipping to change at page 38, line 28
	database". When a timezone location is added to the database, the		database". When a timezone location is added to the database, the
	"iana-timezone" enumeration MUST be updated as defined in RFC 6020		"iana-timezone" enumeration MUST be updated as defined in RFC 6020
	Section 10 to add the newly created timezone location to the		Section 10 to add the newly created timezone location to the
	enumeration. The new "enum" statement MUST be added to the "iana-		enumeration. The new "enum" statement MUST be added to the "iana-
	timezone" typedef with the same name as the newly added timezone		timezone" typedef with the same name as the newly added timezone
	location. A new enum value MUST be allocated by IANA and applied to		location. A new enum value MUST be allocated by IANA and applied to
	the newly created enum entry. New entries MAY be placed in any order		the newly created enum entry. New entries MAY be placed in any order
	in the enumeration as long as the previously assigned enumeration		in the enumeration as long as the previously assigned enumeration
	values are not changed.		values are not changed.
			If a timezone location is removed from the IANA timezone database,
			the corresponding existing enum statement is kept and a status
			statement is added to mark the enum entry as 'obsolete'.
			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
			the enum representing the old timezone name is kept but marked with a
			status statement declaring the enum as 'obsolete'.
			The following is an example of an enum entry which has been marked as
			'obsolete':
			enum "America/New_York" {
			status obsolete;
			value 369;
			description "Eastern Time";
			}
	When the iana-timezones YANG module is updated, a new "revision"		When the iana-timezones YANG module is updated, a new "revision"
	statement must be added.		statement must be added.
	This document registers one URI in the IETF XML registry [RFC3688].		This document registers one URI in the IETF XML registry [RFC3688].
	Following the format in RFC 3688, the following registration is		Following the format in RFC 3688, the following registration is
	requested to be made.		requested to be made.
	URI: urn:ietf:params:xml:ns:yang:iana-timezones		URI: urn:ietf:params:xml:ns:yang:iana-timezones
	Registrant Contact: IANA.		Registrant Contact: IANA.
	skipping to change at page 39, line 22		skipping to change at page 39, line 36
	itself.		itself.
	5. Change Log		5. Change Log
	-- 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
			o Updated IANA considerations
			o Removed old yang revisions
	6. Normative References		6. Normative References
	[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.
	Author's Address		Author's Address
	Jeffrey Lange		Jeffrey Lange
	GE MDS LLC		GE MDS LLC
End of changes. 10 change blocks.
	13 lines changed or deleted		32 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/