History of tzdist protocol development
<h2>Crib sheet for Time Zone Data Distribution Service (tzdist) development</h2>
<p><a href="http://datatracker.ietf.org/wg/tzdist/charter/">Working Group Charter</a></p>
<h3>Initial draft documents</h3>
<p><a href="https://datatracker.ietf.org/doc/draft-douglass-timezone-service/?include_text=1">draft-douglass-timezone-service</a></p>
<p><a href="https://datatracker.ietf.org/doc/draft-daboo-caldav-timezone-ref/?include_text=1">draft-daboo-caldav-timezone-ref</a></p>
<h3>Resources</h3>
<p><a href="http://trac.tools.ietf.org/wg/tzdist/trac/report">Ticket Tracker </a></p>
<p><a href="http://www.ietf.org/mail-archive/web/tzdist/current/maillist.html">Mail List Archive</a></p>
<h3>Third part elements out of scope of discussions</h3>
<p>- Any changes to the Time Zone Database process or infrastructure, as documented in <a href="http://tools.ietf.org/html/rfc6557">RFC 6557</a>.<br />
Backwards data now supported in tz database, so historic material can be defined and updated - <a href="http://hg.lsces.org.uk/hg/tz/file/8f7d54b585c3/CONTRIBUTING">see CONTRIBUTING</a> in tz repository</p>
<p>- The naming process for time zone identifiers. The working group can consider adding a mechanism, such as a "namespace" prefix, to differentiate different time zone sources, but the nature of the time zone identifiers used will be controlled by the sources themselves.<br />
Time zone abbreviations section of the <a href="http://hg.lsces.org.uk/hg/tz/file/8f7d54b585c3/Theory">Theory file</a> in tz repository</p>
<p>- Lookup protocols or APIs to map a location to a time zone.<br />
Sourced from <a href="http://download.geonames.org/export/dump/">geonames database</a> which uses the tz 'zone' table as it's cross reference rather than zone1970.<br />
((Importing geonames data into Firebird))</p>
<p><a href="http://datatracker.ietf.org/wg/tzdist/charter/">Working Group Charter</a></p>
<h3>Initial draft documents</h3>
<p><a href="https://datatracker.ietf.org/doc/draft-douglass-timezone-service/?include_text=1">draft-douglass-timezone-service</a></p>
<p><a href="https://datatracker.ietf.org/doc/draft-daboo-caldav-timezone-ref/?include_text=1">draft-daboo-caldav-timezone-ref</a></p>
<h3>Resources</h3>
<p><a href="http://trac.tools.ietf.org/wg/tzdist/trac/report">Ticket Tracker </a></p>
<p><a href="http://www.ietf.org/mail-archive/web/tzdist/current/maillist.html">Mail List Archive</a></p>
<h3>Third part elements out of scope of discussions</h3>
<p>- Any changes to the Time Zone Database process or infrastructure, as documented in <a href="http://tools.ietf.org/html/rfc6557">RFC 6557</a>.<br />
Backwards data now supported in tz database, so historic material can be defined and updated - <a href="http://hg.lsces.org.uk/hg/tz/file/8f7d54b585c3/CONTRIBUTING">see CONTRIBUTING</a> in tz repository</p>
<p>- The naming process for time zone identifiers. The working group can consider adding a mechanism, such as a "namespace" prefix, to differentiate different time zone sources, but the nature of the time zone identifiers used will be controlled by the sources themselves.<br />
Time zone abbreviations section of the <a href="http://hg.lsces.org.uk/hg/tz/file/8f7d54b585c3/Theory">Theory file</a> in tz repository</p>
<p>- Lookup protocols or APIs to map a location to a time zone.<br />
Sourced from <a href="http://download.geonames.org/export/dump/">geonames database</a> which uses the tz 'zone' table as it's cross reference rather than zone1970.<br />
((Importing geonames data into Firebird))</p>