<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE rfc SYSTEM "rfc2629.dtd" []><!-- !ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml' --><!-- ?xml-stylesheet type='text/xsl' href='http://xml.resource.org/authoring/rfc2629.xslt' ? --><?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?><?rfc toc="yes" ?><?rfc tocompact="no" ?><?rfc tocindent="no" ?><?rfc comments="yes" ?><?rfc inline="yes" ?><?rfc symrefs="yes" ?><?rfc sortrefs="yes"?><?rfc iprnotified="no" ?><?rfc strict="yes" ?><?rfc compact="yes"?><?rfc subcompact="no"?><rfc category="std"     ipr="full3978"     docName="draft-leiba-tzregistry-00">    <front>        <title abbrev="Timezone Name Registry Definition">Definition of IANA Registry for Timezone Names</title>        <author initials='B.' surname="Leiba" fullname="Barry Leiba">            <organization>Internet Messaging Technology</organization>            <address>              <phone>+1 646 827 0648</phone>              <email>barryleiba@computer.org</email>            </address>        </author>        <date year="2009"/>        <area>Applications</area>        <workgroup>VCardDav Working Group</workgroup>        <keyword>VCard</keyword>        <keyword>timezone</keyword>        <keyword>IANA</keyword>        <abstract>          <t>            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.          </t>        </abstract><note title="Initial version"><t>  <list style="symbols">    <t>      Define timezone registry.    </t>    <t>      Defer initial population with Olsen database until we like the basic document.    </t>  </list></t></note>            </front>    <middle>        <section anchor="intro" title="Introduction">          <t>            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.          </t>          <t>            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.          </t>          <t>            A timezone name has the following ABNF <xref target="ABNF"/> syntax:            <list style="hanging" hangIndent="9">              <t hangText="tzname = ALPHA *127(ALPHA / DIGIT)"><vspace/>                ; may have mixed case for readability<vspace/>                ; interpreted case-insensitively<vspace/>              </t>            </list>          </t>        </section>                  <section anchor="iana-considerations" title="IANA Considerations">          <section anchor="tz-registry-def" title="New registry for timezone names">            <t>              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 <xref target="IANA"/>.              <cref>It won't be "Specification Required".  What should it be?</cref>                          </t>            <t>              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.            </t>            <t>              To: iana@iana.org              <vspace/>              Subject: Registration of new timezone name              <vspace/>              Timezone name: [a short US-ASCII string with no internal meaning]              <vspace/>              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")]              <vspace/>              Information URI: [A URI that points to more information about this timezone.                     Specify "none" if there is no appropriate URI.]              <vspace/>            </t>          </section>                    <section anchor="tz-registry-init" title="Initial population of timezone-names registry">            <t>              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.            </t>            <t>              <cref>We'll be filling this in from the Olsen DB...</cref>                          </t>            <t>              Timezone name: ??              <vspace/>              Description: a time zone.              <vspace/>              Information URI: none              <vspace/>            </t>          </section>        </section>        <section anchor="security" title="Security Considerations">          <t>            This document defines an IANA registry.  There are no security considerations.          </t>                </section>    </middle>    <back>        <references title="Normative References">          <reference anchor="ABNF">            <front>              <title>Augmented BNF for Syntax Specifications: ABNF</title>              <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">                <organization>Internet Mail Consortium</organization>              </author>              <author initials="P." surname="Overell" fullname="Paul Overell">                <organization>Demon Internet Ltd.</organization>              </author>              <date month="October" year="2005" />            </front>            <seriesInfo name="RFC" value="4234" />          </reference>                </references>        <references title="Informative References"><reference anchor='IANA'><front><title abbrev='Guidelines for IANA Considerations'>Guidelines for Writing an IANA Considerations Section in RFCs</title><author initials='T.' surname='Narten' fullname='Thomas Narten'><organization>IBM Corporation</organization><address><postal><street>3039 Cornwallis Ave.</street><street>PO Box 12195 - BRQA/502</street><street>Research Triangle Park</street><street>NC 27709-2195</street></postal><phone>919-254-7798</phone><email>narten@raleigh.ibm.com</email></address></author><author initials='H.T.' surname='Alvestrand' fullname='Harald Tveit Alvestrand'><organization>Maxware</organization><address><postal><street>Pirsenteret</street><street>N-7005 Trondheim</street><country>Norway</country></postal><phone>+47 73 54 57 97</phone><email>Harald@Alvestrand.no</email></address></author><date year='1998' month='October' /><area>General</area><keyword>Internet Assigned Numbers Authority</keyword><keyword>IANA</keyword></front><seriesInfo name='BCP' value='26' /><seriesInfo name='RFC' value='2434' /><format type='TXT' octets='25092' target='ftp://ftp.isi.edu/in-notes/rfc2434.txt' /><format type='XML' octets='27060' target='http://xml.resource.org/public/rfc/xml/rfc2434.xml' /></reference>        </references>    </back></rfc>