TOC 
VCardDav Working GroupB. Leiba
Internet-DraftInternet Messaging Technology
Intended status: Standards TrackMarch 26, 2009
Expires: September 27, 2009 


Definition of IANA Registry for Timezone Names
draft-leiba-tzregistry-00

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 September 27, 2009.

Abstract

VCards need a stable, well defined list of timezone names, so that users can create VCards that refer to timezones. There is no common list of such names, and other standards need timezone names also. This document creates an IANA registry of timezone names, and initially populates the list.

Initial version



Table of Contents

1.  Introduction

2.  IANA Considerations
2.1.  New registry for timezone names
2.2.  Initial population of timezone-names registry

3.  Security Considerations

4.  References
4.1.  Normative References
4.2.  Informative References

§  Author's Address
§  Intellectual Property and Copyright Statements




 TOC 

1.  Introduction

VCards need a stable, well defined list of timezone names, so that users can create VCards that refer to timezones. There is no common list of such names, and other standards need timezone names also. This document creates an IANA registry of timezone names, and initially populates the list.

This document defines only the names, leaving the definition of the timezone rules ("normal offset is UTC+2", "switch to summer time on the third Sunday in March", etc) out of scope. The registry contains an optional URI for each defined timezone, and it's possible for that URI to point to a place where such rule definitions can be obtained.

A timezone name has the following ABNF [ABNF] (Crocker, D., Ed. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” October 2005.) syntax:

tzname = ALPHA *127(ALPHA / DIGIT)
; may have mixed case for readability
; interpreted case-insensitively



 TOC 

2.  IANA Considerations



 TOC 

2.1.  New registry for timezone names

IANA is asked to create a new registry for timezone names. This registry contains only IETF-controlled timezone names. New names are registered using the "Specification Required" policy [IANA] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” October 1998.). [anchor1] (It won't be "Specification Required". What should it be?)

This defines the template for a new registry for timezone names, to be created as http://www.iana.org/assignments/timezone-names. There are no initial entries for this registry.

To: iana@iana.org
Subject: Registration of new timezone name
Timezone name: [a short US-ASCII string with no internal meaning]
Description: [a human-readable US-ASCII string, in English, that describes the meaning of this timezone (such as, "the time zone in New York City")]
Information URI: [A URI that points to more information about this timezone. Specify "none" if there is no appropriate URI.]



 TOC 

2.2.  Initial population of timezone-names registry

The following are the initial names to be registered in the timezone-names registry, to be entered in http://www.iana.org/assignments/timezone-names.

[anchor2] (We'll be filling this in from the Olsen DB...)

Timezone name: ??
Description: a time zone.
Information URI: none



 TOC 

3.  Security Considerations

This document defines an IANA registry. There are no security considerations.



 TOC 

4.  References



 TOC 

4.1. Normative References

[ABNF] Crocker, D., Ed. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” RFC 4234, October 2005.


 TOC 

4.2. Informative References

[IANA] Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” BCP 26, RFC 2434, October 1998 (TXT, XML).


 TOC 

Author's Address

  Barry Leiba
  Internet Messaging Technology
Phone:  +1 646 827 0648
Email:  barryleiba@computer.org


 TOC 

Full Copyright Statement

Intellectual Property