idnits 2.17.1 draft-royer-timezone-registry-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 626. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 603. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 610. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 616. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. 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. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 19 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 15, 2005) is 7041 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1' is defined on line 524, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 531, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 535, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 540, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 543, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 546, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 549, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 553, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 557, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 567, but no explicit reference was found in the text == Unused Reference: '15' is defined on line 573, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 577, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 2445 (ref. '2') (Obsoleted by RFC 5545) -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Obsolete normative reference: RFC 822 (ref. '5') (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 1738 (ref. '6') (Obsoleted by RFC 4248, RFC 4266) ** Obsolete normative reference: RFC 1766 (ref. '7') (Obsoleted by RFC 3066, RFC 3282) ** Obsolete normative reference: RFC 2048 (ref. '10') (Obsoleted by RFC 4288, RFC 4289) ** Obsolete normative reference: RFC 2234 (ref. '12') (Obsoleted by RFC 4234) ** Obsolete normative reference: RFC 2279 (ref. '13') (Obsoleted by RFC 3629) ** Obsolete normative reference: RFC 2425 (ref. '14') (Obsoleted by RFC 6350) -- Possible downref: Non-RFC (?) normative reference: ref. '15' -- Possible downref: Non-RFC (?) normative reference: ref. '16' Summary: 16 errors (**), 0 flaws (~~), 16 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group D. Royer 2 Internet-Draft IntelliCal LLC 3 Expires: July 16, 2005 January 15, 2005 5 Time Zone Registry 6 draft-royer-timezone-registry-00 8 Status of this Memo 10 This document is an Internet-Draft and is subject to all provisions 11 of section 3 of RFC 3667. By submitting this Internet-Draft, each 12 author represents that any applicable patent or other IPR claims of 13 which he or she is aware have been or will be disclosed, and any of 14 which he or she become aware will be disclosed, in accordance with 15 RFC 3668. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on July 16, 2005. 35 Copyright Notice 37 Copyright (C) The Internet Society (2005). 39 Abstract 41 This is a submission for the creation of an new IANA Time Zones 42 registration process. This is a registry for iCalendar "VTIMEZONE" 43 calendar component information. Time zones and their definitions are 44 required in order to schedule and synchronize meetings and software. 45 The condition in which these time zones change are subject to civil 46 authority rulings are are not always determinable by software 47 algorithms. 49 This is intended to be a central repository for time zone 50 information. The registry does not presume to be the authority for 51 time zone information or rules. This register is simply a place 52 where time zone definitions may be registered for public access. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 5 58 2.1 Formatting Conventions . . . . . . . . . . . . . . . . . . 5 59 2.2 Related Memos . . . . . . . . . . . . . . . . . . . . . . 6 60 2.3 International Considerations . . . . . . . . . . . . . . . 6 61 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 62 4. Interoperability Considerations . . . . . . . . . . . . . . . 8 63 5. Registry TZID Value . . . . . . . . . . . . . . . . . . . . . 9 64 6. Registry TZURL Value . . . . . . . . . . . . . . . . . . . . . 11 65 7. iCalendar VTIMEZONE registry . . . . . . . . . . . . . . . . . 12 66 8. Initial Time Zone Name . . . . . . . . . . . . . . . . . . . . 13 67 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 18 69 Intellectual Property and Copyright Statements . . . . . . . . 19 71 1. Introduction 73 Many software vendors create time zone information for their 74 applications. This information can sometimes be inconsistent with 75 other applications or contain insufficient information when referring 76 to times far in the past. By creating an IANA registry, the same 77 information will be available to any vendor. In addition there is 78 revision control in the database so vendors will know if they have 79 the latest data. 81 Each time zone has a unique iCalendar time zone identifier (TZID). 82 This document uses the iCalendar "LAST-MODIFIED" property in the the 83 iCalendar "VTIMEZONE" calendar component to track revisions of the 84 data. 86 The "VTIMEZONE" calendar component is not defined in this 87 specification and all usage here are simply examples. At the time of 88 this writing RFC-2445 is the authority for the "VTIMEZONE" calendar 89 component. The initial information in the registry will be from the 90 "Olson" database. 92 When applications create information using a time zone is is critical 93 that the using applications have the same definitions of the time 94 zone in order for the instances in time to match. For that reason 95 the "TZID" property value will contain the revision information of 96 the time zone name and the "TZURL" value will point to the specific 97 revision of the time zone data. 99 The "TZID" property values are broken down into three parts; region, 100 city, and revision. And they are separated using the slash (/) 101 character. 103 This example is using the America/Bosie time zone that was registered 104 on January 15th, 2005 at 6:17:22 PM UTC: 106 BEGIN:VCALENDAR 107 PRODID:-//IANA.ORG//NONSGML OLSON VTIMEZONE DATABASE//EN 108 VERSION:2.0 109 METHOD:PUBLISH 110 BEGIN:VTIMEZONE 111 TZID:/IANA.ORG/America/Boise/20050115T181722Z 112 TZURL:ftp://iana.org/XXXXX/America/Boise/20050115T181722Z.ics 113 LAST-MODIFIED:20050115T181722Z 114 BEGIN:STANDARD 115 TZOFFSETFROM:-0600 116 TZOFFSETTO:-0700 117 TZNAME:MST 118 DTSTART:19701025T020000 119 RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU 120 END:STANDARD 121 BEGIN:DAYLIGHT 122 TZOFFSETFROM:-0700 123 TZOFFSETTO:-0600 124 TZNAME:MDT 125 DTSTART:19700405T020000 126 RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU 127 END:DAYLIGHT 128 END:VTIMEZONE 129 END:VCALENDAR 131 2. Basic Grammar and Conventions 133 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 134 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and 135 "OPTIONAL" in this document are to be interoperated as described in 136 [11]. 138 The notation used in this memo is the ABNF notation of [12]. Readers 139 intending on implementing this format defined in this memo should be 140 familiar with this notation in order to properly interpret the 141 specifications of this memo. 143 All numeric and hexadecimal values used in this memo are given in 144 decimal notation. 146 All names of properties, property parameters, enumerated property 147 values and property parameter values are case-insensitive. However, 148 all other property values are case-sensitive, unless otherwise 149 stated. 150 Note: All indented editorial notes, such as this one, are intended 151 to provide the reader with additional information. The 152 information is not essential to the building of an implementation 153 conformant with this memo. The information is provided to 154 highlight a particular feature or characteristic of the memo. 156 The format for the iCalendar object is based on the syntax of the 157 [14] content type. While the iCalendar object is not a profile of 158 the [14] content type, it does reuse a number of the elements from 159 the [14] specification. 161 2.1 Formatting Conventions 163 The mechanisms defined in this memo are defined in prose. Many of 164 the terms used to describe these have common usage that is different 165 than the standards usage of this memo. In order to reference within 166 this memo elements of the calendaring and scheduling model, core 167 object [2] some formatting conventions have been used. Calendaring 168 and scheduling roles are referred to in quoted-strings of text with 169 the first character of each word in upper case. For example, 170 "Organizer" refers to a role of a "Calendar User" within the protocol 171 defined by [2]. Calendar components defined by this memo are 172 referred to with capitalized, quoted-strings of text. All calendar 173 components start with the letter "V". For example, "VTIMEZONE" 174 refers to the time zone calendar component. 176 The properties defined by this memo are referred to with capitalized, 177 quoted-strings of text, followed by the word "property". For 178 example, "TZNAME" property refers to the iCalendar property used to 179 convey the display name of the time zone. Property parameters 180 defined by this memo are referred to with lowercase, quoted-strings 181 of text, followed by the word "parameter". For example, "value" 182 parameter refers to the iCalendar property parameter used to override 183 the default data type for a property value. 185 2.2 Related Memos 187 Implementers will need to be familiar with several other memos that, 188 along with this memo. Such as iCalendar [2] specifications. 190 [2] - Specifies the format for the "VTIMEZONE" calendar component. 192 This memo does not attempt to repeat the specification of concepts or 193 definitions from these other memos. Where possible, references are 194 made to the memo that provides for the specification of these 195 concepts or definitions. 197 2.3 International Considerations 199 In the rest of this document, descriptions of characters are of the 200 form "character name (codepoint)", where "codepoint" is from the US- 201 ASCII character set. The "character name" is the authoritative 202 description; (codepoint) is a reference to that character in US-ASCII 203 or US-ASCII compatible sets (for example the ISO-8859-x family, UTF- 204 8, ISO-2022-xx, KOI8-R). If a non-US-ASCII compatible character set 205 is used, appropriate code-point from that character set MUST be 206 chosen instead. Use of non-US-ASCII-compatible character sets is NOT 207 recommended. 209 3. Security Considerations 211 There are no known security issues with this proposal as this is a 212 repository of information and not an over the wire protocol. 214 4. Interoperability Considerations 216 This document is intended to be compliant with the [iCAL] "VTIMEZONE" 217 calendar component and will interoperate with any implementation that 218 follows that specification. 220 5. Registry TZID Value 222 Within the time zone registry, the "TZID" property will be used as 223 follows. This is compatible with the [iCAL] "TZID" property as here 224 we only define the format of the value of the property. 226 Property Name: TZID 228 Purpose: This property specifies the text value that uniquely 229 identifies the "VTIMEZONE" calendar component in the IANA registry. 231 Value Type: TEXT (in the format specified below) 233 Property Parameters: Non-standard property parameters can be 234 specified on this property. 236 Conformance: This property MUST be specified in a "VTIMEZONE" 237 calendar component. 239 Description: This is the label by which a time zone calendar 240 component is referenced by any iCalendar properties whose data type 241 is either DATE-TIME or TIME and not intended to specify a UTC or a 242 "floating" time. The presence of the SOLIDUS character (US-ASCII 243 decimal 47) as a prefix, indicates that this TZID represents an 244 unique ID in a globally defined IANA time zone registry (this 245 specification) 247 Format Definition: This property is defined by the following 248 notation: 250 tzid = "TZID" tzidpropparam ":" 251 ianatzidprefix 252 "/" tzregion 253 "/" tzcity 254 "/" tzrev CRLF 256 tzidpropparam = *(";" xparam) 258 ianatzidprefix = "/IANA.ORG" 260 tzregion = "Africa" / "America" / "Asia" / "Europe" 261 / "Indian" / "Pacific" 263 tzcity = 265 tzrev = date-time "Z" 267 date-time = 269 Example: The following are examples of globally unique time zone 270 identifiers as defined by this specification: 272 TZID:/IANA.ORG/Indian/Reunion/20050115T112522Z 274 TZID:/IANA.ORG/Pacific/Pago_Pago/20050114T162291Z 276 6. Registry TZURL Value 278 Within the time zone registry, the "TZURL" property will be used as 279 follows. This is compatible with the [iCAL] "TZURL" property as here 280 we only define the format of the value of the property. 282 Property Name: TZURL 284 a Purpose: The TZURL provides a means for a VTIMEZONE component to 285 point to a network location that can be used to retrieve an up-to- 286 date version of itself. 288 Value Type: URI 290 Property Parameters: Non-standard property parameters can be 291 specified on this property. 293 Conformance: This property can be specified in a "VTIMEZONE" calendar 294 component. 296 Description: The TZURL provides a means for a VTIMEZONE component to 297 point to a network location that can be used to retrieve an up-to- 298 date version of itself. This provides a hook to handle changes 299 government bodies impose upon time zone definitions. Retrieval of 300 this resource results in an iCalendar object containing a single 301 VTIMEZONE component and a METHOD property set to PUBLISH. 303 Format Definition: The property is defined by the following notation: 305 tzurl = "TZURL" tzurlparam ":" ianatzuri CRLF 307 tzurlparam = *(";" xparam) 309 ianatzuri = "ftp://iana.org/XXXXXX" 310 "/" tzregion "/" tzcity "/" rzrev ".ics" 312 Example: The following is an example of this property: 314 TZURL:ftp://iana.org/XXXXXX/Indian/Reunion/20050115T112522Z.ics 316 TZURL:ftp://iana.org/XXXXXX/Pacific/Pago_Pago/20050114T162291Z.ics 318 7. iCalendar VTIMEZONE registry 320 Each time zone is an [iCAL] "VTIMEZONE" calendar component. The 321 [iCAL] "TZID" property value will be unique in the IANA registry and 322 will be prefixed with "/IANA.ORG/" to identify them as being part of 323 the register. 325 The TZURL property will be URL that will point to the newest version 326 of the time zone ".ics" file in the IANA registry. 328 8. Initial Time Zone Name 330 Africa/Abidjan.ics Africa/Accra.ics 331 Africa/Addis_Ababa.ics Africa/Algiers.ics 332 Africa/Asmera.ics Africa/Bamako.ics 333 Africa/Bangui.ics Africa/Banjul.ics 334 Africa/Bissau.ics Africa/Blantyre.ics 335 Africa/Brazzaville.ics Africa/Bujumbura.ics 336 Africa/Cairo.ics Africa/Casablanca.ics 337 Africa/Ceuta.ics Africa/Conakry.ics 338 Africa/Dakar.ics Africa/Dar_es_Salaam.ics 339 Africa/Djibouti.ics Africa/Douala.ics 340 Africa/El_Aaiun.ics Africa/Freetown.ics 341 Africa/Gaborone.ics Africa/Harare.ics 342 Africa/Johannesburg.ics Africa/Kampala.ics 343 Africa/Khartoum.ics Africa/Kigali.ics 344 Africa/Kinshasa.ics Africa/Lagos.ics 345 Africa/Libreville.ics Africa/Lome.ics 346 Africa/Luanda.ics Africa/Lubumbashi.ics 347 Africa/Lusaka.ics Africa/Malabo.ics 348 Africa/Maputo.ics Africa/Maseru.ics 349 Africa/Mbabane.ics Africa/Mogadishu.ics 350 Africa/Monrovia.ics Africa/Nairobi.ics 351 Africa/Ndjamena.ics Africa/Niamey.ics 352 Africa/Nouakchott.ics Africa/Ouagadougou.ics 353 Africa/Porto-Novo.ics Africa/Sao_Tome.ics 354 Africa/Timbuktu.ics Africa/Tripoli.ics 355 Africa/Tunis.ics Africa/Windhoek.ics 356 America/Adak.ics America/Anchorage.ics 357 America/Anguilla.ics America/Antigua.ics 358 America/Araguaina.ics America/Aruba.ics 359 America/Asuncion.ics America/Bahia.ics 360 America/Barbados.ics America/Belem.ics 361 America/Belize.ics America/Boa_Vista.ics 362 America/Bogota.ics America/Boise.ics 363 America/Buenos_Aires.ics America/Cambridge_Bay.ics 364 America/Campo_Grande.ics America/Cancun.ics 365 America/Caracas.ics America/Catamarca.ics 366 America/Cayenne.ics America/Cayman.ics 367 America/Chicago.ics America/Chihuahua.ics 368 America/Cordoba.ics America/Costa_Rica.ics 369 America/Cuiaba.ics America/Curacao.ics 370 America/Danmarkshavn.ics America/Dawson_Creek.ics 371 America/Dawson.ics America/Denver.ics 372 America/Detroit.ics America/Dominica.ics 373 America/Edmonton.ics America/Eirunepe.ics 374 America/El_Salvador.ics America/Fortaleza.ics 375 America/Glace_Bay.ics America/Godthab.ics 376 America/Goose_Bay.ics America/Grand_Turk.ics 377 America/Grenada.ics America/Guadeloupe.ics 378 America/Guatemala.ics America/Guayaquil.ics 379 America/Guyana.ics America/Halifax.ics 380 America/Havana.ics America/Hermosillo.ics 381 America/Indiana/Indianapolis.ics America/Indiana/Knox.ics 382 America/Indiana/Marengo.ics America/Indianapolis.ics 383 America/Indiana/Vevay.ics America/Inuvik.ics 384 America/Iqaluit.ics America/Jamaica.ics 385 America/Jujuy.ics America/Juneau.ics 386 America/Kentucky/Louisville.ics America/Kentucky/Monticello.ics 387 America/La_Paz.ics America/Lima.ics 388 America/Los_Angeles.ics America/Louisville.ics 389 America/Maceio.ics America/Managua.ics 390 America/Manaus.ics America/Martinique.ics 391 America/Mazatlan.ics America/Mendoza.ics 392 America/Menominee.ics America/Merida.ics 393 America/Mexico_City.ics America/Miquelon.ics 394 America/Monterrey.ics America/Montevideo.ics 395 America/Montreal.ics America/Montserrat.ics 396 America/Nassau.ics America/New_York.ics 397 America/Nipigon.ics America/Nome.ics 398 America/Noronha.ics America/North_Dakota/Center.ics 399 America/Panama.ics America/Pangnirtung.ics 400 America/Paramaribo.ics America/Phoenix.ics 401 America/Port-au-Prince.ics America/Port_of_Spain.ics 402 America/Porto_Velho.ics America/Puerto_Rico.ics 403 America/Rainy_River.ics America/Rankin_Inlet.ics 404 America/Recife.ics America/Regina.ics 405 America/Rio_Branco.ics America/Santiago.ics 406 America/Santo_Domingo.ics America/Sao_Paulo.ics 407 America/Scoresbysund.ics America/Shiprock.ics 408 America/St_Johns.ics America/St_Kitts.ics 409 America/St_Lucia.ics America/St_Thomas.ics 410 America/St_Vincent.ics America/Swift_Current.ics 411 America/Tegucigalpa.ics America/Thule.ics 412 America/Thunder_Bay.ics America/Tijuana.ics 413 America/Toronto.ics America/Tortola.ics 414 America/Vancouver.ics America/Whitehorse.ics 415 America/Winnipeg.ics America/Yakutat.ics 416 America/Yellowknife.ics Antarctica/Casey.ics 417 Antarctica/Davis.ics Antarctica/DumontDUrville.ics 418 Antarctica/Mawson.ics Antarctica/McMurdo.ics 419 Antarctica/Palmer.ics Antarctica/Rothera.ics 420 Antarctica/South_Pole.ics Antarctica/Syowa.ics 421 Antarctica/Vostok.ics Arctic/Longyearbyen.ics 422 Asia/Aden.ics Asia/Almaty.ics 423 Asia/Amman.ics Asia/Anadyr.ics 424 Asia/Aqtau.ics Asia/Aqtobe.ics 425 Asia/Ashgabat.ics Asia/Baghdad.ics 426 Asia/Bahrain.ics Asia/Baku.ics 427 Asia/Bangkok.ics Asia/Beirut.ics 428 Asia/Bishkek.ics Asia/Brunei.ics 429 Asia/Calcutta.ics Asia/Choibalsan.ics 430 Asia/Chongqing.ics Asia/Colombo.ics 431 Asia/Damascus.ics Asia/Dhaka.ics 432 Asia/Dili.ics Asia/Dubai.ics 433 Asia/Dushanbe.ics Asia/Gaza.ics 434 Asia/Harbin.ics Asia/Hong_Kong.ics 435 Asia/Hovd.ics Asia/Irkutsk.ics 436 Asia/Istanbul.ics Asia/Jakarta.ics 437 Asia/Jayapura.ics Asia/Jerusalem.ics 438 Asia/Kabul.ics Asia/Kamchatka.ics 439 Asia/Karachi.ics Asia/Kashgar.ics 440 Asia/Katmandu.ics Asia/Krasnoyarsk.ics 441 Asia/Kuala_Lumpur.ics Asia/Kuching.ics 442 Asia/Kuwait.ics Asia/Macau.ics 443 Asia/Magadan.ics Asia/Makassar.ics 444 Asia/Manila.ics Asia/Muscat.ics 445 Asia/Nicosia.ics Asia/Novosibirsk.ics 446 Asia/Omsk.ics Asia/Oral.ics 447 Asia/Phnom_Penh.ics Asia/Pontianak.ics 448 Asia/Pyongyang.ics Asia/Qatar.ics 449 Asia/Qyzylorda.ics Asia/Rangoon.ics 450 Asia/Riyadh.ics Asia/Saigon.ics 451 Asia/Sakhalin.ics Asia/Samarkand.ics 452 Asia/Seoul.ics Asia/Shanghai.ics 453 Asia/Singapore.ics Asia/Taipei.ics 454 Asia/Tashkent.ics Asia/Tbilisi.ics 455 Asia/Tehran.ics Asia/Thimphu.ics 456 Asia/Tokyo.ics Asia/Ulaanbaatar.ics 457 Asia/Urumqi.ics Asia/Vientiane.ics 458 Asia/Vladivostok.ics Asia/Yakutsk.ics 459 Asia/Yekaterinburg.ics Asia/Yerevan.ics 460 Atlantic/Azores.ics Atlantic/Bermuda.ics 461 Atlantic/Canary.ics Atlantic/Cape_Verde.ics 462 Atlantic/Faeroe.ics Atlantic/Jan_Mayen.ics 463 Atlantic/Madeira.ics Atlantic/Reykjavik.ics 464 Atlantic/South_Georgia.ics Atlantic/Stanley.ics 465 Atlantic/St_Helena.ics Australia/Adelaide.ics 466 Australia/Brisbane.ics Australia/Broken_Hill.ics 467 Australia/Darwin.ics Australia/Hobart.ics 468 Australia/Lindeman.ics Australia/Lord_Howe.ics 469 Australia/Melbourne.ics Australia/Perth.ics 470 Australia/Sydney.ics Europe/Amsterdam.ics 471 Europe/Andorra.ics Europe/Athens.ics 472 Europe/Belfast.ics Europe/Belgrade.ics 473 Europe/Berlin.ics Europe/Bratislava.ics 474 Europe/Brussels.ics Europe/Bucharest.ics 475 Europe/Budapest.ics Europe/Chisinau.ics 476 Europe/Copenhagen.ics Europe/Dublin.ics 477 Europe/Gibraltar.ics Europe/Helsinki.ics 478 Europe/Istanbul.ics Europe/Kaliningrad.ics 479 Europe/Kiev.ics Europe/Lisbon.ics 480 Europe/Ljubljana.ics Europe/London.ics 481 Europe/Luxembourg.ics Europe/Madrid.ics 482 Europe/Malta.ics Europe/Minsk.ics 483 Europe/Monaco.ics Europe/Moscow.ics 484 Europe/Nicosia.ics Europe/Oslo.ics 485 Europe/Paris.ics Europe/Prague.ics 486 Europe/Riga.ics Europe/Rome.ics 487 Europe/Samara.ics Europe/San_Marino.ics 488 Europe/Sarajevo.ics Europe/Simferopol.ics 489 Europe/Skopje.ics Europe/Sofia.ics 490 Europe/Stockholm.ics Europe/Tallinn.ics 491 Europe/Tirane.ics Europe/Uzhgorod.ics 492 Europe/Vaduz.ics Europe/Vatican.ics 493 Europe/Vienna.ics Europe/Vilnius.ics 494 Europe/Warsaw.ics Europe/Zagreb.ics 495 Europe/Zaporozhye.ics Europe/Zurich.ics 496 Indian/Antananarivo.ics Indian/Chagos.ics 497 Indian/Christmas.ics Indian/Cocos.ics 498 Indian/Comoro.ics Indian/Kerguelen.ics 499 Indian/Mahe.ics Indian/Maldives.ics 500 Indian/Mauritius.ics Indian/Mayotte.ics 501 Indian/Reunion.ics Pacific/Apia.ics 502 Pacific/Auckland.ics Pacific/Chatham.ics 503 Pacific/Easter.ics Pacific/Efate.ics 504 Pacific/Enderbury.ics Pacific/Fakaofo.ics 505 Pacific/Fiji.ics Pacific/Funafuti.ics 506 Pacific/Galapagos.ics Pacific/Gambier.ics 507 Pacific/Guadalcanal.ics Pacific/Guam.ics 508 Pacific/Honolulu.ics Pacific/Johnston.ics 509 Pacific/Kiritimati.ics Pacific/Kosrae.ics 510 Pacific/Kwajalein.ics Pacific/Majuro.ics 511 Pacific/Marquesas.ics Pacific/Midway.ics 512 Pacific/Nauru.ics Pacific/Niue.ics 513 Pacific/Norfolk.ics Pacific/Noumea.ics 514 Pacific/Pago_Pago.ics Pacific/Palau.ics 515 Pacific/Pitcairn.ics Pacific/Ponape.ics 516 Pacific/Port_Moresby.ics Pacific/Rarotonga.ics 517 Pacific/Saipan.ics Pacific/Tahiti.ics 518 Pacific/Tarawa.ics Pacific/Tongatapu.ics 519 Pacific/Truk.ics Pacific/Wake.ics 520 Pacific/Wallis.ics Pacific/Yap.ics 522 9 References 524 [1] Royer, D., "Calendar Access Protocol (CAP)", RFC XXXX - TBD, 525 XXXXX 2005. 527 [2] Dawson, F. and D. Stenerson, "Internet Calendaring and 528 Scheduling Core Object specification (iCalendar)", RFC 2445, 529 November 1998. 531 [3] "ISO 8601, Data elements and interchange formats-Information 532 interchange--Representation of dates and times International 533 Organization for Standardization", June 1988. 535 [4] "ISO/IEC 9070, Information Technology_SGML Support 536 Facilities--Registration Procedures for Public Text Owner 537 Identifiers Second Edition, International Organization for 538 Standardization", April 1991. 540 [5] Crocker, D., "Standard for the Format of ARPA Internet Text 541 Messages", STD 11, RFC 822, August 1982. 543 [6] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform 544 Resource Locators (URL", RFC 1738, December 1994. 546 [7] Alvestrand, H., "Tags for the Identification of Languages", RFC 547 1766, March 1995. 549 [8] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 550 Extensions (MIME) - Part One: Format of Internet Message 551 Bodies", RFC 2045, November 1996. 553 [9] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 554 Extensions (MIME) - Part Two: Media Types", RFC 2046, November 555 1996. 557 [10] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet 558 Mail Extensions (MIME) - Part Four: Registration Procedures", 559 RFC 2048, January 1997. 561 [11] Bradner, S., "Key words for use in RFCs to Indicate Requirement 562 Levels", BCP 14, RFC 2119, March 1997. 564 [12] Crocker, D. and P. Overell, "Augmented BNF for Syntax 565 Specifications: ABNF", RFC 2234, November 1997. 567 [13] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 568 2279, January 1998. 570 [14] Howes, T., Smith, M. and F. Dawson, "A MIME Content-Type for 571 Directory Information", RFC 2425, September 1998. 573 [15] Olson, A., "Time zone code and data, 574 ftp://elsie.nci.nih.gov/pub/, updated periodically", 575 . 577 [16] "Internet Mail Consortium, vCalendar - The Electronic 578 Calendaring and Scheduling Exchange Format 579 http://www.imc.org/pdi/vcal-10.txt", September 1996, 580 . 582 Author's Address 584 Doug Royer 585 IntelliCal LLC 586 267 Kentlands Blvd., #3041 587 Gaithersburg, MD 20878 588 USA 590 Phone: +1-208-612-4638 591 EMail: Doug@IntelliCal.net 592 URI: http://Royer.com 594 Intellectual Property Statement 596 The IETF takes no position regarding the validity or scope of any 597 Intellectual Property Rights or other rights that might be claimed to 598 pertain to the implementation or use of the technology described in 599 this document or the extent to which any license under such rights 600 might or might not be available; nor does it represent that it has 601 made any independent effort to identify any such rights. Information 602 on the procedures with respect to rights in RFC documents can be 603 found in BCP 78 and BCP 79. 605 Copies of IPR disclosures made to the IETF Secretariat and any 606 assurances of licenses to be made available, or the result of an 607 attempt made to obtain a general license or permission for the use of 608 such proprietary rights by implementers or users of this 609 specification can be obtained from the IETF on-line IPR repository at 610 http://www.ietf.org/ipr. 612 The IETF invites any interested party to bring to its attention any 613 copyrights, patents or patent applications, or other proprietary 614 rights that may cover technology that may be required to implement 615 this standard. Please address the information to the IETF at 616 ietf-ipr@ietf.org. 618 Disclaimer of Validity 620 This document and the information contained herein are provided on an 621 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 622 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 623 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 624 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 625 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 626 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 628 Copyright Statement 630 Copyright (C) The Internet Society (2005). This document is subject 631 to the rights, licenses and restrictions contained in BCP 78, and 632 except as set forth therein, the authors retain all their rights. 634 Acknowledgment 636 Funding for the RFC Editor function is currently provided by the 637 Internet Society.