< draft-ietf-tzdist-service-10.txt		draft-ietf-tzdist-service-11.txt >
	Network Working Group M. Douglass		Network Working Group M. Douglass
	Internet-Draft Spherical Cow Group		Internet-Draft Spherical Cow Group
	Intended status: Standards Track C. Daboo		Intended status: Standards Track C. Daboo
	Expires: January 23, 2016 Apple		Expires: January 24, 2016 Apple
	July 22, 2015		July 23, 2015
	Time Zone Data Distribution Service		Time Zone Data Distribution Service
	draft-ietf-tzdist-service-10		draft-ietf-tzdist-service-11
	Abstract		Abstract
	This document defines a time zone data distribution service that		This document defines a time zone data distribution service that
	allows reliable, secure and fast delivery of time zone data and leap		allows reliable, secure and fast delivery of time zone data and leap
	second rules to client systems such as calendaring and scheduling		second rules to client systems such as calendaring and scheduling
	applications or operating systems.		applications or operating systems.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 January 23, 2016.		This Internet-Draft will expire on January 24, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 47, line 38 ¶		skipping to change at page 47, line 38 ¶
	IANA is asked to create a new top-level category called "Time Zone		IANA is asked to create a new top-level category called "Time Zone
	Data Distribution Service (TZDIST) Parameters", and to put all the		Data Distribution Service (TZDIST) Parameters", and to put all the
	registries created herein into that category.		registries created herein into that category.
	IANA is asked to create a new registry called "TZDIST Service		IANA is asked to create a new registry called "TZDIST Service
	Actions", as defined below.		Actions", as defined below.
	10.1.1. Service Actions Registration Procedure		10.1.1. Service Actions Registration Procedure
	This registry uses the "Specification Required" policy defined in		This registry uses the "Specification Required" policy defined in
	[I-D.leiba-cotton-iana-5226bis], which makes use of a designated		[RFC5226], which makes use of a designated expert to review potential
	expert to review potential registrations.		registrations.
	The IETF will create a mailing list, tzdist-service@ietf.org, which		The IETF will create a mailing list, tzdist-service@ietf.org, which
	can be used for public discussion of time zone data distribution		can be used for public discussion of time zone data distribution
	service actions proposals prior to registration. The IESG will		service actions proposals prior to registration. The IESG will
	appoint a designated expert who will monitor the tzdist-		appoint a designated expert who will monitor the tzdist-
	service@ietf.org mailing list and review registrations.		service@ietf.org mailing list and review registrations.
	A Standards Track RFC is REQUIRED for changes to actions previously		A Standards Track RFC is REQUIRED for changes to actions previously
	documented in a Standards Track RFC, otherwise any public		documented in a Standards Track RFC, otherwise any public
	specification that satisfies the requirements of		specification that satisfies the requirements of [RFC5226] is
	[I-D.leiba-cotton-iana-5226bis] is acceptable.		acceptable.
	The registration procedure begins when a completed registration		The registration procedure begins when a completed registration
	template, as defined below, is sent to tzdist-service@ietf.org and		template, as defined below, is sent to tzdist-service@ietf.org and
	iana@iana.org. The designated expert is expected to tell IANA and		iana@iana.org. The designated expert is expected to tell IANA and
	the submitter of the registration whether the registration is		the submitter of the registration whether the registration is
	approved, approved with minor changes, or rejected with cause, within		approved, approved with minor changes, or rejected with cause, within
	two weeks. When a registration is rejected with cause, it can be re-		two weeks. When a registration is rejected with cause, it can be re-
	submitted if the concerns listed in the cause are addressed.		submitted if the concerns listed in the cause are addressed.
	Decisions made by the designated expert can be appealed as per		Decisions made by the designated expert can be appealed as per
	Section 10 of [I-D.leiba-cotton-iana-5226bis].		Section 7 of [RFC5226].
	The designated expert MUST take the following requirements into		The designated expert MUST take the following requirements into
	account when reviewing the registration:		account when reviewing the registration:
	1. A valid registration template MUST be provided by the submitter,		1. A valid registration template MUST be provided by the submitter,
	with a clear description of what the action does.		with a clear description of what the action does.
	2. A proposed new action name MUST NOT conflict with any existing		2. A proposed new action name MUST NOT conflict with any existing
	registered action name. A conflict includes a name that		registered action name. A conflict includes a name that
	duplicates an existing one, or that appears to be very similar to		duplicates an existing one, or that appears to be very similar to
	skipping to change at page 50, line 45 ¶		skipping to change at page 50, line 45 ¶
	Assignment Note: This is an extension of the https service. Defined		Assignment Note: This is an extension of the https service. Defined
	TXT keys: path=<context path> (as per Section 6 of [RFC6763]).		TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
	10.4. tzdist Identifiers Registry		10.4. tzdist Identifiers Registry
	IANA is requested to register a new URN sub-namespace within the IETF		IANA is requested to register a new URN sub-namespace within the IETF
	URN Sub-namespace for Registered Protocol Parameter Identifiers		URN Sub-namespace for Registered Protocol Parameter Identifiers
	defined in [RFC3553].		defined in [RFC3553].
	Registrations in this registry follow the "IETF Review"		Registrations in this registry follow the "IETF Review" [RFC5226]
	[I-D.leiba-cotton-iana-5226bis] policy.		policy.
	Registry name: tzdist Identifiers		Registry name: tzdist Identifiers
	URN prefix: urn:ietf:params:tzdist		URN prefix: urn:ietf:params:tzdist
	Specification: RFCXXXX		Specification: RFCXXXX
	Repository: http://www.iana.org/assignments/tzdist-identifiers.		Repository: http://www.iana.org/assignments/tzdist-identifiers.
	Index value:: Values in this registry are URNs or URN prefixes that		Index value:: Values in this registry are URNs or URN prefixes that
	start with the prefix "urn:ietf:params:tzdist:". Each is		start with the prefix "urn:ietf:params:tzdist:". Each is
	skipping to change at page 54, line 30 ¶		skipping to change at page 54, line 30 ¶
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[I-D.ietf-appsawg-http-problem]		[I-D.ietf-appsawg-http-problem]
	Nottingham, M. and E. Wilde, "Problem Details for HTTP		Nottingham, M. and E. Wilde, "Problem Details for HTTP
	APIs", draft-ietf-appsawg-http-problem-00 (work in		APIs", draft-ietf-appsawg-http-problem-00 (work in
	progress), September 2014.		progress), September 2014.
	[I-D.leiba-cotton-iana-5226bis]
	Cotton, M., Leiba, B., and T. Narten, "Guidelines for
	Writing an IANA Considerations Section in RFCs", draft-
	leiba-cotton-iana-5226bis-11 (work in progress), November
	2014.
	[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail		[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
	Extensions (MIME) Part Two: Media Types", RFC 2046,		Extensions (MIME) Part Two: Media Types", RFC 2046,
	November 1996.		November 1996.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for		[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
	specifying the location of services (DNS SRV)", RFC 2782,		specifying the location of services (DNS SRV)", RFC 2782,
	February 2000.		February 2000.
	skipping to change at page 55, line 16 ¶		skipping to change at page 55, line 9 ¶
	IETF URN Sub-namespace for Registered Protocol		IETF URN Sub-namespace for Registered Protocol
	Parameters", BCP 73, RFC 3553, June 2003.		Parameters", BCP 73, RFC 3553, June 2003.
	[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO		[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
	10646", STD 63, RFC 3629, November 2003.		10646", STD 63, RFC 3629, November 2003.
	[RFC4985] Santesson, S., "Internet X.509 Public Key Infrastructure		[RFC4985] Santesson, S., "Internet X.509 Public Key Infrastructure
	Subject Alternative Name for Expression of Service Name",		Subject Alternative Name for Expression of Service Name",
	RFC 4985, August 2007.		RFC 4985, August 2007.
			[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 5226,
			DOI 10.17487/RFC5226, May 2008,
			<http://www.rfc-editor.org/info/rfc5226>.
	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security		[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
	(TLS) Protocol Version 1.2", RFC 5246, August 2008.		(TLS) Protocol Version 1.2", RFC 5246, August 2008.
	[RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling		[RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling
	Core Object Specification (iCalendar)", RFC 5545,		Core Object Specification (iCalendar)", RFC 5545,
	September 2009.		September 2009.
	[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known		[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
	Uniform Resource Identifiers (URIs)", RFC 5785, April		Uniform Resource Identifiers (URIs)", RFC 5785, April
	2010.		2010.
	skipping to change at page 56, line 50 ¶		skipping to change at page 56, line 46 ¶
	12.2. Informative References		12.2. Informative References
	[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC		[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC
	2131, March 1997.		2131, March 1997.
	Appendix A. Change History (to be removed prior to publication as an		Appendix A. Change History (to be removed prior to publication as an
	RFC)		RFC)
	Changes for -10		Changes for -10
			1. AD: switch 5226bis back to 5226.
			Changes for -10
	1. OPSDIR: minor editorial tweaks.		1. OPSDIR: minor editorial tweaks.
	2. OPSDIR: Add RFC6763 reference into IANA registration templates.		2. OPSDIR: Add RFC6763 reference into IANA registration templates.
	3. IESG: add reference to security section for well-known redirects.		3. IESG: add reference to security section for well-known redirects.
	4. IESG: Add sentence describing current size of an initial JSON		4. IESG: Add sentence describing current size of an initial JSON
	response for IANA data.		response for IANA data.
	5. IESG: don't mention per-user context paths - just refer to		5. IESG: don't mention per-user context paths - just refer to
End of changes. 10 change blocks.
	17 lines changed or deleted		20 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/