idnits 2.17.1 draft-ietf-calsch-csct-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 70 longer pages, the longest (page 40) being 108 lines 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.) ** There is 1 instance of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([RFC1521]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1024: '... this property MUST be the same as t...' RFC 2119 keyword, line 2295: '...alendar property MUST appear in the MI...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (June 1997) is 9804 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC1521' on line 281 looks like a reference -- Missing reference section? 'RFC 1521' on line 3105 looks like a reference -- Missing reference section? 'VCAL' on line 3126 looks like a reference -- Missing reference section? 'MIME-REG' on line 3101 looks like a reference -- Missing reference section? 'RFC 822' on line 504 looks like a reference -- Missing reference section? 'RFC 1766' on line 3116 looks like a reference -- Missing reference section? 'XAPIA' on line 3236 looks like a reference -- Missing reference section? 'ISO 630' on line 3077 looks like a reference -- Missing reference section? 'ISO 3166' on line 3080 looks like a reference -- Missing reference section? 'ISO 8601' on line 3084 looks like a reference -- Missing reference section? 'ISO 8859-1' on line 3092 looks like a reference -- Missing reference section? 'ISO 9070' on line 3096 looks like a reference -- Missing reference section? 'RFC 1738' on line 3112 looks like a reference -- Missing reference section? 'UNICODE' on line 3119 looks like a reference -- Missing reference section? 'US-ASCII' on line 3123 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Frank Dawson 3 Internet Draft IBM Corporation 4 November 26, 1996 5 Expires June 1997 7 MIME Calendaring and Scheduling Content Type 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months. Internet-Drafts may be updated, replaced, or made obsolete by 18 other documents at any time. It is not appropriate to use Internet- 19 Drafts as reference material or to cite them other than as a "working 20 draft" or "work in progress". 22 To learn the current status of any Internet-Draft, please check the 23 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 24 Directories on ds.internic.net (US East Coast), nic.nordu.net 25 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 26 Rim). 28 Distribution of this document is unlimited. 30 Abstract 32 There is a clear need to provide and deploy interoperable calendaring 33 and scheduling services for the Internet. Current group scheduling 34 and Personal Information Management (PIM) products are being extended 35 for use across the Internet, today, in proprietary ways. This 36 document has been defined to provide the a definition of a MIME 37 message format for openly exchanging calendaring and scheduling 38 information across the Internet. 40 This memo is meant to serve as the basis for registration of such a 41 MIME media type per [RFC1521]. The proposed media type value is 42 "TEXT/CALENDAR". This string would label a media type containing 43 calendaring and scheduling information encoded as text characters 44 formatted in a manner outlined below. 46 This MIME media type provides a standard content type for capturing 47 calendar event and todo information. It also can be used to convey 48 free/busy time information. The content type is suitable as a MIME 49 message entity that can be transferred over MIME based email systems 50 or using HTTP. In addition, the content type is useful as an object 51 for interactions between desktop applications using the operating 52 system clipboard, drag/drop or file systems capabilities. 54 It is expected that additional documents will be created for this 55 content type that define usage profiles for specific sets of 57 Dawson 1 Expires June 1997 58 calendaring and scheduling capabilities. The format for these profile 59 documents is also defined by this document. 61 The document is also intended to serve as a standard for message 62 profiles that will provide an interoperability method for exchanging 63 over the Internet event-requests, reply to event-requests, 64 modification notices for event requests, cancellation notices for 65 event-requests, todo-requests, reply to todo-requests, modification 66 notices for todo requests, cancellation notices for todo-requests, 67 requesting free/busy time and replying to free/busy time requests 68 between different calendaring and scheduling products. This is the 69 subject of another Internet Draft. 71 Table of Contents 73 1. Introduction........................................................4 74 2. TEXT/CALENDAR Registration Information..............................5 75 3. Intended Use........................................................6 76 3.1 Published specification ..........................................6 77 3.1.1 Existing Message Header Fields ................................6 78 3.1.1.1 Content-Type Header Field .................................6 79 3.1.1.1.1 CHARSET Header Field Parameter .........................6 80 3.1.1.2 Content-ID Header Field ...................................7 81 3.1.1.3 Content-Language ..........................................7 82 3.1.1.4 Message-ID Header Field ...................................7 83 3.1.1.5 Transfer-Encoding Header Field ............................7 84 3.1.2 Additional Content Type Parameter .............................7 85 3.1.2.1 Profile ...................................................7 86 3.1.3 Content Syntax Considerations .................................8 87 3.1.3.1 Property ..................................................8 88 3.1.3.2 Delimiters ................................................9 89 3.1.3.3 Property Value Transfer Encoding .........................10 90 3.1.3.4 Property Value Character Set .............................10 91 3.1.3.5 Property Value Language ..................................11 92 3.1.3.6 Property Value Data Type .................................11 93 3.1.3.7 Date and Time ............................................14 94 3.1.3.8 Time Duration ............................................15 95 3.1.3.9 Value Location ...........................................16 96 3.1.3.10 Binary Property Values ..................................17 97 3.1.3.11 Recurrence Rule Grammar .................................17 98 3.1.4 Body Delimiter Properties ....................................17 99 3.1.4.1 Calendar Object ..........................................17 100 3.1.4.2 Event Component ..........................................18 101 3.1.4.3 Todo Component ...........................................18 102 3.1.5 Calendar Object Properties ...................................19 103 3.1.5.1 Calendar Content Profile .................................19 104 3.1.5.2 Daylight Savings Rule ....................................21 105 3.1.5.3 Geographic Position ......................................22 106 3.1.5.4 Product Identifier .......................................22 107 3.1.5.5 Time Zone ................................................23 108 3.1.5.6 Version ..................................................23 109 3.1.6 Event and Todo Component Properties ..........................23 110 3.1.6.1 Attachment ...............................................23 111 3.1.6.2 Attendee .................................................24 113 Dawson 2 Expires June 1997 114 3.1.6.3 Audio Reminder ...........................................28 115 3.1.6.4 Categories ...............................................30 116 3.1.6.5 Classification ...........................................31 117 3.1.6.6 Date/Time Created ........................................32 118 3.1.6.7 Date/Time Completed ......................................32 119 3.1.6.8 Description ..............................................32 120 3.1.6.9 Display Reminder .........................................33 121 3.1.6.10 Due Date/Time ...........................................33 122 3.1.6.11 Duration ................................................33 123 3.1.6.12 End Date/Time ...........................................34 124 3.1.6.13 Exception Date/Times ....................................34 125 3.1.6.14 Exception Rule ..........................................34 126 3.1.6.15 Last Modified ...........................................35 127 3.1.6.16 Location ................................................35 128 3.1.6.17 Mail Reminder ...........................................35 129 3.1.6.18 Number Recurrences ......................................36 130 3.1.6.19 Priority ................................................36 131 3.1.6.20 Procedure Reminder ......................................36 132 3.1.6.21 Related To ..............................................37 133 3.1.6.22 Recurrence Date/Times ...................................38 134 3.1.6.23 Recurrence Rule .........................................38 135 3.1.6.24 Resources ...............................................38 136 3.1.6.25 Response Sequence Number ................................39 137 3.1.6.26 Sequence Number .........................................40 138 3.1.6.27 Start Date/Time .........................................40 139 3.1.6.28 Status ..................................................40 140 3.1.6.29 Summary .................................................42 141 3.1.6.30 Time Transparency .......................................42 142 3.1.6.31 Uniform Resource Locator ................................42 143 3.1.6.32 Unique Identifier .......................................42 144 3.1.6.33 Non-standard Properties .................................43 145 3.2 Formal Definition ...............................................43 146 3.3 Basic Recurrence Rule Grammar ...................................49 147 3.3.1 Daily Rule ...................................................49 148 3.3.2 Weekly Rule ..................................................50 149 3.3.3 Monthly Rule .................................................50 150 3.3.4 Yearly Rule ..................................................51 151 3.3.5 Grammar ......................................................52 152 3.3.6 Grammar Glossary .............................................53 153 3.3.7 Policies .....................................................54 154 4. Registration of Content Type Profiles..............................55 155 4.1 Define the profile ..............................................55 156 4.2 Post the profile definition .....................................56 157 4.3 Allow a comment period ..........................................56 158 4.4 Submit the profile for approval .................................56 159 4.5 Profile Change Control ..........................................56 160 4.6 Registration of New Content Type Properties .....................57 161 4.6.1 Define the property ..........................................57 162 4.6.2 Post the Property definition .................................58 163 4.6.3 Allow a comment period .......................................58 164 4.6.4 Submit the property for approval .............................58 165 4.7 Content Type Property Change Control ............................58 166 5. File extension.....................................................59 167 6. Macintosh File Type Code...........................................59 169 Dawson 3 Expires June 1997 170 7. Bibliography.......................................................59 171 8. Acknowledgments....................................................60 172 9. Author's Address...................................................60 173 10. Examples..........................................................61 174 11. Extended Recurrence Grammar.......................................62 175 11.1 Rule Introduction ..............................................62 176 11.2 Grammar ........................................................64 177 11.3 Glossary .......................................................65 178 11.4 Policies .......................................................66 179 11.5 Examples .......................................................68 181 1. Introduction 183 The use of mail enabled applications such as calendaring and 184 scheduling has grown considerably in the last decade. Enterprise and 185 inter-enterprise business has become dependent on rapid scheduling of 186 events and actions using this information technology. The store-and- 187 forward characteristic of electronic messaging technologies has been 188 shown to be complementary to the asynchronous nature of group 189 communications. However, the longer term growth of mail enabled 190 applications, such as calendaring and scheduling, is currently 191 limited by the lack of Internet standards for the message content 192 types that are central to these groupware applications. This 193 specification is intended to progress the level of interoperability 194 possible between dissimilar calendaring and scheduling applications 195 that communicate using an SMTP or MIME transport. 197 This specification defines a MIME content type for exchanging 198 electronic calendaring and scheduling information. The MIME 199 Calendaring and Scheduling Content Type allows for the capture and 200 exchange of information normally stored within a calendaring and 201 scheduling application; such as a Personal Information Manager or a 202 Group Scheduling product. 204 The format is suitable as an exchange format between applications or 205 systems. The format is defined in terms of a MIME content type. The 206 primary transport for this exchange is expected to be a MIME 207 electronic messaging system. However, other transports such as HTTP, 208 a file system, desktop interactive protocols such as the use of a 209 memory-based clipboard or drag/drop interactions, point-to-point 210 asynchronous communication, wired-network transport, or some form of 211 unwired transport such as infrared might also be used. 213 The specification also provides for the definition of usage profiles 214 that will map this content type to a set of messages for supporting 215 calendaring and scheduling operations such as requesting, replying 216 to, modifying, and canceling meetings or appointments and todos. The 217 usage profiles can be used to define other calendaring and scheduling 218 operations such a requesting for and replying with free/busy time 219 data. 221 Dawson 4 Expires June 1997 222 The specification also includes a formal grammar for the content type 223 to aid in the implementation of parsers and to serve as the 224 definitive reference when ambiguities or questions arise in 225 interpreting the descriptive prose definition of the specification. 227 2. TEXT/CALENDAR Registration Information 229 To: ietf-types@uninett.no 231 Subject: Registration of MIME content type text/calendar. 233 MIME media type name: text 235 MIME subtype name: calendar 237 Required parameters: PROFILE 239 Optional parameters: CHARSET 241 Additional required content header fields: CONTENT-ID, MESSAGE-ID 243 Optional content header fields: CONTENT-LANGUAGE, TRANSFER-ENCODING 245 Encoding considerations: This MIME content type does not introduce 246 any new encoding considerations beyond those defined in [RFC 1521]. 248 Security considerations: The calendaring and scheduling information 249 based on this MIME content type may include references to Uniform 250 Resource Locators that may be programmed resources. In addition, 251 this information may contain direct references to executable 252 programs intended to be used as program-based alarms for an event 253 or todo. Implementers and users of this specification should be 254 aware of the network security implications of accepting and parsing 255 such information. 257 Interoperability considerations: This MIME content type is intended 258 to provide interoperability between calendaring and scheduling 259 products. It is heavily based on the prior [VCAL] specification in 260 order to assure interoperability with implementations conforming to 261 this industry specification. 263 Intended Usage: COMMON 265 Published specification: This document. 267 Person & email address to contact for further information: 269 Frank Dawson 270 IBM Corporation 271 3039 Cornwallis Road 272 RTP, NC 27709 273 919-254-5861 (Telephone) 274 919-543-6822 (Facsimile) 275 fdawson@raleigh.ibm.com (Internet Mail) 277 Dawson 5 Expires June 1997 278 3. Intended Use 280 This memo is meant to serve as the basis for registration of a MIME 281 content type per [RFC1521]. It is defined using the MIME content type 282 registration from [MIME-REG]. The proposed content type value is 283 "TEXT/CALENDAR". This string would label a media type containing 284 calendaring and scheduling information encoded primarily as text 285 characters formatted in a manner outlined below. 287 A subtype of the standard MIME _TEXT_ media type was chosen as the 288 form for this content type because it provides a known and reasonable 289 fallback for legacy systems that are required in an enterprise that 290 also includes MIME based user agents that support this content type. 291 Legacy systems that do not understand the _TEXT/CALENDAR_ content 292 type will render these MIME entities as they would _TEXT/PLAIN_ 293 content type. This will provide a minimal level of support for 294 calendaring and scheduling information in legacy systems (i.e., the 295 ability to display the text tagged calendaring and scheduling content 296 information). This is a vital requirement for any mail enabled, 297 enterprise application; as there are still over 7 million existing 298 legacy electronic mail user agents at this time. 300 The calendaring and scheduling media type is specified as an 301 independent content type in order that it can be conveyed as a single 302 MIME message entity or as one MIME entity in a multi-part MIME 303 message. Additionally, the calendaring and scheduling information may 304 be defined in a multi-part message containing references to other 305 MIME body parts holding additional data related to the event, todo, 306 or free/busy time information. 308 3.1 Published specification 310 The following characteristics are specific to this MIME content type. 312 3.1.1 Existing Message Header Fields 314 The MIME Calendar Content Type may utilize any of the message header 315 fields defined by [RFC 822], [RFC 1521], and [RFC 1766]. A number of 316 these message header fields are especially useful to the MIME 317 Calendaring and Scheduling Content Type. These include the following 318 header fields defined in either [RFC 822], [RFC 1521], and [RFC 319 1766]. 321 3.1.1.1 Content-Type Header Field 323 The [RFC 1521] Content-Type header field is used to identify the MIME 324 Calendaring and Scheduling Content Type. The value of this property 325 must be _text/calendar_ in order to correspond to the media type 326 defined by this document. This header field is required for MIME 327 entities conforming to this content type. 329 3.1.1.1.1 CHARSET Header Field Parameter 331 Dawson 6 Expires June 1997 332 The [RFC 1521] CHARSET Content-Type header field parameter is used to 333 identify an alternate character set to the default US-ASCII used by 334 the MIME Calendaring and Scheduling Content Type. This header field 335 parameter is optional for MIME entities conforming to this content 336 type. 338 3.1.1.2 Content-ID Header Field 340 The [RFC 1521] Content-ID header field is used to provide a 341 persistent, globally unique identifier for a MIME Calendar Object 342 within a MIME message entity. This header field is required for MIME 343 entities conforming to this content type. 345 3.1.1.3 Content-Language 347 The [RFC 1766] Content-Language header field is used to provide an 348 alternate default language for the MIME Calendar Object. The default 349 language is _en-US_. This header field is optional for MIME entities 350 conforming to this content type. 352 3.1.1.4 Message-ID Header Field 354 The [RFC 1521] Message-ID header field is used to provide a 355 persistent, globally unique identifier for a MIME message containing 356 a single body part consisting of a MIME Calendaring and Scheduling 357 Content Type. This header field is required for a single body part 358 MIME message conforming to this content type. 360 3.1.1.5 Transfer-Encoding Header Field 362 The [RFC 1521] Transfer-Encoding header filed is used to provide an 363 alternate transfer encoding for the MIME Calendaring and Scheduling 364 Content Type. The default transfer encoding is _7BIT_. This header 365 field is optional for a MIME entity conforming to this content type. 367 3.1.2 Additional Content Type Parameter 369 In addition to the existing content type parameters defined by [RFC 370 1521] and [RFC 1766], this document defines an additional content 371 type parameter to be used by the MIME Calendaring and Scheduling 372 Content Type. 374 3.1.2.1 Profile 376 The MIME Calendar Object defines the Profile content type parameter. 377 This parameter is used to specify a usage profile for the MIME 378 Calendaring and Scheduling Content Type. The value of this parameter 379 consists of a type and a subtype value pair. The type value is used 380 to specify either a EVENT, TODO, or FREE-BUSY type of MIME Calendar 381 Object profile. The subtype value is used to specify the scheduling 382 operation being conveyed by the profile type. The EVENT and TODO type 383 values may have a subtype value of REQUEST, to convey an event or 384 todo request message, REPLY, to convey an event or todo reply 385 message, MODIFY, to convey an event or todo modification message, 387 Dawson 7 Expires June 1997 388 CANCEL, to convey an event or todo cancellation message, DELEGATE, to 389 convey an event or todo delegation message. The BUSY-FREE type value 390 may have a subtype value of REQUEST, to convey a free-busy time 391 request message , or REPLY, to convey a free-busy time data message. 392 The parameter value is defined by the following BNF: 394 profile := ((_EVENT / 395 _ _ _ 396 TODO ) _/_ type1) / (_FREE-BUSY_ _/_ type2) 398 type1 := _REQUEST_ / _REPLY_ / _MODIFY_ / _CANCEL_ / _DELEGATE_ 400 type2 := _REQUEST_ / _REPLY_ 402 The following is an example of this content type parameter for 403 specifying an event request message, such as in a request for a 404 meeting or appointment: 406 CONTENT-TYPE:TEXT/CALENDAR;PROFILE=EVENT/REQUEST 408 The following is an example of this content type parameter for 409 specifying a todo delegation message, such as delegating a task to 410 another individual: 412 CONTENT-TYPE:TEXT/CALENDAR;TODO/DELEGATE 414 The following is an example of this content type parameter for 415 specifying a free-busy time request, such as when searching for a 416 free time for a meeting: 418 CONTENT-TYPE:TEXT/CALENDAR;PROFILE=FREE-BUSY/REQUEST 420 This content type parameter is required for MIME entities conforming 421 to this content type. 423 3.1.3 Content Syntax Considerations 425 The following general considerations are specific to the syntax used 426 to format the text of the body information for this content type. 428 3.1.3.1 Property 430 A property is the definition of an individual attribute describing an 431 event or a todo associated with the MIME Calendar Object. A property 432 takes the following form: 434 property := propname *(_;_ propparm) _:_ propvalue 436 as shown in the following example: 438 DTSTART:19960415T083000 440 A property takes the form of one or more lines of text. The 441 specification of property names and property parameters is case 442 insensitive. The property name can be one of a set of pre-defined or 443 non-standard strings. The property name must appear as the first 445 Dawson 8 Expires June 1997 446 characters on a line. In the previous example, _DTSTART_ is the name 447 of the Start Date/Time property. Property values are specified as 448 strings. In the previous example, _19960415T083000_ is the ISO 8601 449 formatted value for the Start Date/Time property. 451 The property parameter expressions are specified as either a 452 name=value or a value string. The parameter value string can be 453 specified alone in those cases where the value is unambiguous. For 454 example a complete property parameter specification might be: 456 DESCRIPTION;ENCODING=QUOTED-PRINTABLE:Don't forget to order Girl= 457 Scout cookies from Stacey today! 459 A valid short version of the same property parameter specification 460 might be: 462 DESCRIPTION;QUOTED-PRINTABLE:Don't forget to order Girl= 463 Scout cookies from Stacey today! 465 3.1.3.2 Delimiters 467 Individual lines within the MIME Calendaring and Scheduling Content 468 Type body are delimited by the [RFC 822] line break, which is a CRLF 469 sequence (ASCII decimal 13, followed by ASCII decimal 10). Long lines 470 of text can be split into a multiple-line representation using the 471 RFC 822 _folding_ technique. That is, wherever there may be linear 472 white space (NOT simply LWSP-chars), a CRLF immediately followed by 473 at least one LWSP-char may instead be inserted. For example the line: 475 DESCRIPTION:This is a long description that exists on a long line. 477 Can be represented as: 479 DESCRIPTION:This is a long description 480 that exists on a long line. 482 The process of moving from this folded multiple-line representation 483 of a property definition to its single line representation is called 484 _unfolding_. Unfolding is accomplished by regarding CRLF immediately 485 followed by a LWSP-char as equivalent to the LWSP-char. 487 It is recommended that folding be limited to higher-level syntactic 488 breaks in structured components of the property definition. 490 A formatted text line break in a property value, must also be 491 specified by a (RFC 822) line break, which is a CRLF sequence. 492 However, since the CRLF sequence is used to delimit a line, property 493 values with formatted line breaks (i.e., multiple lines) must be 494 encoded using an alternate encoding of either Quoted-Printable or 495 Base64, as defined in [RFC 1521]. 497 For example, in the Quoted-Printable encoding the multiple lines of 498 formatted text are separated with a Quoted-Printable CRLF sequence of 499 _=0D_ followed by _=0A_ followed by a Quoted-Printable soft line 501 Dawson 9 Expires June 1997 502 break sequence of _=_. Quoted-Printable lines of text must also be 503 limited to less than 76 characters. The 76 characters does not 504 include the CRLF [RFC 822] line break sequence. For example a 505 multiple line DESCRIPTION value of: 507 Project XYZ Final Review 508 Conference Room - 3B 509 Come Prepared. 511 Would be represented in a Quoted-Printable encoding as: 513 DESCRIPTION; QUOTED-PRINTABLE:Project XYZ Final Review=0D=0A= 514 Conference Room - 3B=0D=0A= 515 Come Prepared. 517 Property parameter sub-strings are delimited by a field delimiter, 518 specified by the Semi-colon character (ASCII decimal 59). A Semi- 519 colon character in a property parameter value must be escaped with a 520 Backslash character (ASCII decimal 92). 522 Compound property values are delimited by a field delimiter, 523 specified by the Semi-colon character (ASCII decimal 59). A Semi- 524 colon character in a component of a compound property value must be 525 escaped with a Backslash character (ASCII decimal 92). 527 3.1.3.3 Property Value Transfer Encoding 529 The default transfer encoding for the MIME Calendaring and Scheduling 530 Content Type is _7BIT_. The default transfer encoding can be 531 overridden for an individual property value by using the _ENCODING_ 532 property parameter. This parameter value can be either _7BIT_, 533 _BASE64_, _QUOTED-PRINTABLE_, or _8BIT_. This parameter may be used 534 on any property. 536 The MIME TRANSFER-ENCODING header field can be used to specify a 537 default transfer encoding other than 7BIT (e.g., 8BIT). 539 3.1.3.4 Property Value Character Set 541 The default character set for a MIME Calendaring and Scheduling 542 Content Type is ASCII. The default character set can be overridden 543 for an individual property value by using the _CHARSET_ property 544 parameter. This property parameter may be used on any property. 545 However, the use of this parameter on some properties may not make 546 sense. 548 Any character set registered with the Internet Assigned Numbers 549 Authority (IANA) can be specified by this property parameter. For 550 example, ISO 8859-8 or the Latin/Hebrew character set is specified 551 by: 553 DESCRIPTION;CHARSET=ISO-8859-8:... 555 Dawson 10 Expires June 1997 556 The MIME CHARSET parameter on the CONTENT-TYPE header field can be 557 used to specify a default character set other than ASCII (e.g., UTF- 558 8). 560 3.1.3.5 Property Value Language 562 The default language for a MIME Calendaring and Scheduling Content 563 Type is _en-US_ (US English). The default language can be overridden 564 for an individual property value by using the _LANGUAGE_ property 565 parameter. The values for this property are a string consistent with 566 RFC 1766, Tags for the Identification of Languages. This property 567 parameter may be used on any property. However, the use of this 568 parameter on some properties, such as PHOTO, LOGO, SOUND, TEL, may 569 not make sense. Canadian French would be specified by this property 570 parameter by the following: 572 SUMMARY;LANGUAGE=fr-CA:... 574 The MIME LANGUAGE parameter on the CONTENT-TYPE header field can be 575 used to specify a default language other than US English (e.g., fr- 576 CA). 578 3.1.3.6 Property Value Data Type 580 In order to more fully specify the semantics of this content type and 581 to facilitate its automated processing, the specification of each 582 property defined by the MIME Calendaring and Scheduling Content Type 583 identifies the valid data types and the default data type for the 584 property value. In addition, within an instance of this content type 585 a property may explicitly convey the data type information through 586 the DATATYPE property parameter. The STRING data type for the 587 DESCRIPTION property would be specified by the following: 589 DESCRIPTION;DATATYPE=STRING:Weekly Staff Meeting 591 If the DATATYPE property parameter is not specified on a property, 592 then the default data type for that property is assumed. Usage 593 profiles for this content type that introduce new properties must 594 specify the default data type for each newly defined property. The 595 data types used within this content type definition include the 596 following: 598 Description Property Data 599 Type 601 Indicates an AALARM 602 audio alarm 603 value, as 604 specified by 605 this document. 607 Dawson 11 Expires June 1997 608 Indicates a BOOLEAN 609 Boolean value 610 string of 611 either TRUE or 612 FALSE. 614 Indicates a 615 string 616 identifier 617 value for the 618 content 619 identifier of 620 another MIME 621 entity within 622 the current 623 CID 624 message. 626 Indicates a DALARM 627 display alarm 628 value, as 629 specified by 630 this document. 632 Indicates an 633 ISO 8601 634 formatted 635 date/time 636 DATE-TIME 637 string value. 639 Indicates a DST-RULE 640 daylight saving 641 time rule value 642 as specified in 643 this document. 645 Indicates a D-T-LIST 646 list of ISO 647 8601 formatted 648 date/time 649 string values. 651 Indicates an DURATION 652 ISO 8601 653 formatted 654 duration or 655 period of time 656 value. 658 Indicates a FLOAT 659 string 660 representation 661 of a floating 662 point value. 664 Dawson 12 Expires June 1997 665 Indicates a FLOAT-LIST 666 list of string 667 representations 668 of floating 669 point values. 671 Indicates a INTEGER 672 numeric string 673 representation 674 of an integer 675 value. 677 Indicates a INTEGER-LIST 678 list of numeric 679 string 680 representations 681 of an integer 682 value. 684 Indicates a MALARM 685 mail alarm 686 value, as 687 specified by 688 this document. 690 Indicates a MID 691 string 692 identifier 693 value for an 694 external 695 message. 697 Indicates a PALARM 698 procedure alarm 699 value, as 700 specified by 701 this document. 703 Indicates a RFC RFC822- 704 822 formatted ADDRESS 705 address 706 specification 707 string value. 709 Indicates a RRULE 710 recurrence rule 711 grammar string 712 value as 713 specified in 714 this document. 716 Indicates a STRING 717 text string 719 Dawson 13 Expires June 1997 720 value in the 721 current 722 character set. 724 Indicates a 725 list of text 726 string values 727 in the current 728 STRING-LIST 729 character set. 731 Indicates an TIME-OFFSET 732 ISO 8601 733 formatted time 734 offset value 736 Indicates a RFC URL 737 1738 formatted 738 Uniform 739 Resource 740 Locator string. 742 The property values consisting of lists of a particular data type 743 (i.e., STRING-LIST) are semi-colon separated string of list items. 745 3.1.3.7 Date and Time 747 The date and time values for all MIME Calendaring and Scheduling 748 Content Type properties are formatted as a string consistent with the 749 ISO 8601 representation for combinations of dates and times. Either 750 the basic or extended format is allowed. The use of UTC, rather than 751 local time, should be used when ever possible in order to avoid time 752 zone ambiguities. Where local time is specified, the inclusion of the 753 UTC offset should also be included to avoid time zone ambiguities. 754 The format for the complete, representation of a date and time value 755 is represented by the following ABNF: 757 date-time = 1*(date / time / (date time)) 759 date = year month day 760 year = 761 month = [_-_] 762 day = [_-_] 764 time = hour minute second [fraction] (utc-sign / utc-offset) 765 hour = 766 minute = [_:] 768 second = [_:_] 771 fraction = _,_ 773 Dawson 14 Expires June 1997 774 utc-sign = _Z_ 775 utc-offset = [_+_ / _-_] hour [_:_] minute 776 ;_+_ if offset is after UTC and _-_ if offset is before UTC 778 The basic complete representation does not include the _-_ date 779 separator nor the _:_ time separator. The extended complete 780 representation does include the separators. 782 For example, 8:30 AM on April 15, 1996 local time EST would be 783 written as: 785 19960415T083000-05:00 787 And the same time in UTC based time would be written as: 789 19960415T133000Z 791 The same date and time represented in the extended completed 792 representation would be written as: 794 1996-04-15T08:30:00-05:00 796 And the same time in UTC based time would be written as: 798 1996-04-15T13:30:00Z 800 Where a value needs to specify a sequence of date and time values, 801 then the property value is a string made up of a list of date and 802 time values, separated by the field separator, a Semi-Colon (ASCII 803 decimal 59). For example: 805 19960101T090000Z;19960201T090000Z;19960301T090000Z;... 807 3.1.3.8 Time Duration 809 The values for time duration or periods of time for all MIME 810 Calendaring and Scheduling Content Type properties are formatted as a 811 string consistent with the ISO 8601 representation for duration of 812 time. A given duration of a period of time is represented by a 813 character string consisting of the designator _P_, optionally 814 including the number of years followed by the designator _Y_, 815 optionally including the number of months followed by the designator 816 _M_, optionally including the number of weeks followed by the 817 designator _W_, optionally including the number of days followed by 818 the designator _D_. The sequence can also contain a time component 819 preceded by the designator _T_, optionally including the number of 820 hours followed by the designator _H_, optionally including the number 821 of minutes followed by the designator _M_, optionally including the 822 number of seconds followed by the designator _S_. The following ABNF 823 describes the representation of ISO 8601 periods of time: 825 duration = _P_ (yr-period / tm-period / (yr-period tm-period)) 826 ;Duration needs to include at least one component of year or 827 ;time periods 829 Dawson 15 Expires June 1997 830 yr-period = [yr-parm] [mo-parm] / wk-parm 831 yr-parm = _Y_ 832 mo-parm = _M_ 833 wk-parm = _W_ 835 tm-period = _T_ [hr-parm] [mn-parm] [sc-parm] 836 hr-parm = _H_ 837 mn-parm = _M_ 838 sc-parm = _S_ 840 For example: 842 P6W 844 represents a period of six weeks; 846 PT15M 848 represents a period of 15 minutes; 850 PT1H30M 852 represents a period of 1 hour and thirty minutes; or 854 P2Y10M15DT10H30M20S 856 represents a period of 2 years, 10 months, 15 days, 10 hours, 30 857 minutes, and 20 seconds. 859 3.1.3.9 Value Location 861 The default location of the property values is inline with the 862 property. However, for some properties, such as those that specify 863 multimedia values, it is more efficient in a MIME message to organize 864 the property value as a separate MIME entity. The property parameter 865 _VALUE_ can be specified to override the _INLINE_ location of the 866 property value. In the case of the MIME Calendaring and Scheduling 867 Content Type being transported within a MIME email message, the 868 property value can be specified as being located in a separate MIME 869 entity with the _CONTENT-ID_ value; or _CID_ for shorthand. In this 870 case, the property value is the Content-ID for the MIME entity within 871 the multi-part message that contains the property value. The value 872 can also be specified as being contained within an another, external 873 message using the _MESSAGE-ID_ value, or _MID_ for shorthand. In 874 addition, the property value can be specified as being located out on 875 the Internet using the _URL_ value. In this case, the property value 876 is the Uniform Resource Locator for the Internet resource containing 877 the property value. This property parameter may be used on any 878 property. However, the use of this parameter on some properties may 879 not make sense; for example the Version, Time Zone, Status, Priority, 880 Mail Reminder, etc. properties. 882 The following specifies a value located out on the Internet: 884 Dawson 16 Expires June 1997 885 ATTACH;VALUE=URL:http://www.abc.com/dir_photos/my_photo.gif 887 The following specifies a value located out in the content of another 888 message: 890 ATTACH;VALUE=MID:<960120.aaCB@host1.com> 892 3.1.3.10 Binary Property Values 894 The MIME Calendaring and Scheduling Content Type supports inclusion 895 of binary information, such as computer graphic images (e.g., 896 IMAGE/JPEG), digital audio (e.g., AUDIO/BASIC), or video graphic 897 images (e.g., VIDEO/MPEG). As specified above the binary information 898 can be referenced with a Uniform Reference Locator (URL), referenced 899 within an external MIME message, referenced within a particular MIME 900 message body part, or placed. Inline binary information is included 901 as a property value after being binary encoded using Base 64 902 (default) or Quoted-Printable transfer encoding. 904 3.1.3.11 Recurrence Rule Grammar 906 Recurring events within the MIME Calendaring and Scheduling Content 907 Type may be specified as either a list of discrete date and time 908 values or as a recurrence rule using a grammar. The basic recurrence 909 rule grammar used by this specification is defined in a separate 910 section of this specification. The grammar defines a recurrence rule 911 that that is based on the prior work of the X.400 API Association's 912 Calendaring and Scheduling Subcommittee. It is also based on prior 913 work of the IETF Chronos Working Group. Refer to section 3.3. 915 3.1.4 Body Delimiter Properties 917 The body information of a MIME Calendaring and Scheduling Content 918 Type is defined by a series of body fields or properties. This 919 section defines the properties that can be used in MIME entities 920 conforming to this content type. 922 3.1.4.1 Calendar Object 924 The body of the MIME Calendaring and Scheduling Content Type is 925 identified within the body of a MIME entity by the appearance of the 926 Begin Calendar Object Delimiter: 928 BEGIN:VCALENDAR 930 The sentinel string must appear as the first characters in the body 931 of the MIME entity and as the first characters on a line. 933 The body information of the MIME Calendaring and Scheduling Content 934 Type is terminated by the appearance of the End Calendar Object 935 Delimiter as the first characters on a line: 937 END:VCALENDAR 939 Dawson 17 Expires June 1997 940 The MIME Calendaring and Scheduling Content Type is a container for 941 calendar components. These can include either event or todo 942 components. The body of a MIME Calendaring and Scheduling Content 943 Type will generally contain a single calendar event or todo 944 component. However, the body may include multiple event or todo 945 components. This is the case for free-busy time reply messages that 946 contain multiple free time intervals in individual calendar 947 components. 949 The Begin and End Calendar Object Delimiter properties are required 950 in a MIME entity conforming to this content type. The default data 951 type for these properties is a STRING. 953 3.1.4.2 Event Component 955 An Event Component is a grouping of calendaring and scheduling 956 properties that defines a component that represents a scheduled 957 amount of time on a calendar. For example, it may be an activity; 958 such as a one-hour, department meeting from 8 AM to 9 AM, tomorrow or 959 a free/busy time interval. 961 An individual Event Component is identified within a MIME Calendaring 962 and Scheduling Content Type by the appearance of the delimiter: 964 BEGIN:VEVENT 966 The sentinel string must appear as the first characters on a line. 968 The Event Component is terminated with the appearance of the 969 following delimiter string as the first characters on a line 971 END:VEVENT 973 The Event Component can not be nested within another Event or Todo 974 Component. If Event components need to be related to each other or to 975 a Todo Component, they can specify a relationship with the RELATED-TO 976 property. 978 The Begin and End Event Component Delimiter properties are required 979 for a MIME entity containing an event component and conforming to 980 this content type. The default data type for these properties is a 981 STRING. 983 3.1.4.3 Todo Component 985 A Todo Component is a grouping of calendaring and scheduling 986 properties that define a component that represents an action-item or 987 assignment. For example, it may be an item of work assigned to an 988 individual; such as _turn in travel expense today_. 990 An individual Todo Component is identified within a MIME Calendaring 991 and Scheduling Content Type by the appearance of the delimiter: 993 BEGIN:VTODO 995 Dawson 18 Expires June 1997 996 The sentinel string must appear as the first characters on a line. 998 The Todo Component is terminated with the appearance of the following 999 delimiter string as the first characters on a line 1001 END:VTODO 1003 The Todo Component can not be nested within another Todo or Event 1004 Component. If Todo components need to be related to each other or to 1005 an Event Component, they can specify a relationship with the RELATED- 1006 TO property. 1008 The Begin and End Todo Component Delimiter properties are required 1009 for a MIME entity containing a todo component and conforming to this 1010 content type. The default data type for these properties is a STRING. 1012 3.1.5 Calendar Object Properties 1014 The following properties may appear between the Begin Calendar Object 1015 Delimiter and either the Begin Event Component Delimiter or the Begin 1016 Todo Component Delimiter. These properties define body field values 1017 that apply to the complete calendar object. 1019 3.1.5.1 Calendar Content Profile 1021 This property is identified by the property name PROFILE. This 1022 property defines the usage profile associated with the calendar 1023 object. When used included in a MIME message entity, the value of 1024 this property MUST be the same as the Content-Type profile parameter 1025 value. 1027 The calendar property value may include the following usage profile 1028 values: 1030 Profile Parameter Description 1031 Type/Subtype Value 1033 EVENT/REQUEST Make a request for an 1034 event 1036 EVENT/REPLY Reply to an event 1037 request 1039 EVENT/COUNTER Make a counter proposal 1040 to the event request 1042 EVENT/DECLINE- Decline the counter 1043 COUNTER proposal to the event 1045 Dawson 19 Expires June 1997 1046 request 1048 EVENT/MODIFY Modify a subset of the 1049 details of an existing 1050 event request 1052 EVENT/REPLACE Replace the current 1053 event request with a 1054 complete set of 1055 information 1057 EVENT/CANCEL Cancel an existing 1058 event request 1060 EVENT/DELEGATE Delegate an existing 1061 event request 1063 EVENT/RESEND Request a duplicate of 1064 the current event 1065 request information 1067 TODO/REQUEST Assign a todo 1069 TODO/REPLY Reply to a todo 1070 assignment 1072 TODO/COUNTER Make a counter proposal 1073 for the todo request 1075 TODO/DECLINE-COUNTER Decline a counter 1076 proposal for the todo 1077 request 1079 TODO/MODIFY Modify a subset of the 1080 details of an existing 1081 todo assignment 1083 TODO/REPLACE Replace the current 1084 todo request with a 1085 complete set of 1086 information 1088 Dawson 20 Expires June 1997 1089 TODO/CANCEL Cancel an existing todo 1091 TODO/DELEGATE Delegate an existing 1092 todo 1094 TODO/RESEND Request a duplicate of 1095 the current todo 1096 request information 1098 FREE-BUSY/REQUEST Free/busy time request 1100 FREE-BUSY/REPLY Reply to an existing 1101 free/busy time request 1102 with free/busy time 1103 data 1105 Other values may be defined by other usage profiles of this content 1106 type. 1108 This property is optional for MIME entities conforming to this 1109 content type. In the event that this property is not specified, the 1110 recipient of a MIME Calendaring and Scheduling Content Type should 1111 assume the calendar object is for an _event/request_. The default 1112 data type for this property is STRING. 1114 3.1.5.2 Daylight Savings Rule 1116 This property is identified by the property name DAYLIGHT. This 1117 property defines the daylight savings time rule observed by the 1118 _home_ calendar system that created the MIME calendar object. 1120 Many locations adjust their standard time forward or backward by one 1121 hour, in order to accommodate seasonal changes in number of daylight 1122 hours. Some locations adjust their time by a fraction of an hour. 1123 Standard time is also known as Winter Time. Daylight savings time is 1124 also known as Advanced Time, Summer Time, or Legal Time in certain 1125 countries. 1127 The property value consists of a sequence of components that define a 1128 rule for the observance of daylight savings time. The value consists 1129 of the daylight savings time flag, followed by the daylight savings 1130 time offset, followed by the date and time that the daylight savings 1131 time begins, followed by the date and time that the daylight savings 1132 time ends, followed by the standard time designation, followed by the 1133 daylight savings time designation. The daylight savings time flag is 1135 Dawson 21 Expires June 1997 1136 TRUE if daylight savings time is observed, otherwise it is FALSE and 1137 no other components are specified. The daylight savings time offset 1138 value is specified in a manner consistent with ISO 8601. The property 1139 value is a signed numeric indicating the number of hours and possibly 1140 minutes from UTC. The date and time that the daylight savings time 1141 begins and ends is specified in a manner consistent with ISO 8601 1142 date and time format. The standard time and daylight savings time 1143 designations correspond to the customary character designations. 1145 The following are examples of this property: 1147 DAYLIGHT:TRUE;-06;19960407T025959;19961027T010000;EST;EDT 1149 DAYLIGHT:FALSE 1151 DAYLIGHT:TRUE;-09;19960407T115959;19961027T100000;PST;PDT 1153 This property is optional for MIME entities conforming to this 1154 content type. In the event that this property is not specified, the 1155 recipient of a MIME Calendaring and Scheduling Content Type should 1156 assume the same daylight savings time rule as the recipient location. 1157 The default data type for this property is DST-RULE. 1159 3.1.5.3 Geographic Position 1161 This property is identified by the property name GEO. This property 1162 specifies information related to the global position of the _home_ 1163 system that created the MIME calendar object. The property value 1164 specifies longitude and latitude. The longitude represents the 1165 location east and west of the prime meridian as a positive or 1166 negative real number, respectively. The latitude represents the 1167 location north and south of the equator as a positive or negative 1168 real number, respectively. The following is an example of this 1169 property: 1171 GEO:37.24,-17.87 1173 This property is optional for MIME entities conforming to this 1174 content type. The default data type for this property is FLOAT-LIST. 1176 3.1.5.4 Product Identifier 1178 This property is identified by the property name PRODID. This 1179 property specifies the identifier for the product that created the 1180 MIME calendar object. The vendor of the implementation should assure 1181 that this is a globally unique identifier; using some technique such 1182 as an ISO 9070 FPI value. The following is an example of this 1183 property: 1185 PRODID:-//ABC Corporation//NONSGML My Product//EN 1187 This property is required for MIME entities conforming to this 1188 content type. The default data type for this property is STRING. 1190 Dawson 22 Expires June 1997 1191 3.1.5.5 Time Zone 1193 This property is identified by the property name TZ. This property 1194 specifies the standard time zone of the _home_ system that created 1195 the MIME calendar object. The property value is specified in a manner 1196 consistent with ISO 8601. The property value is a signed numeric 1197 indicating the number of hours and possibly minutes from UTC. Time 1198 zones east of UTC are positive numbers. Time zones west of UTC are 1199 negative numbers. The following are examples of this property: 1201 TZ:-0500 1203 TZ:+05:30 1205 This property is optional for MIME entities conforming to this 1206 content type. If this property is missing, the recipient should 1207 assume all local times are relative to the recipients time zone. The 1208 default data type for this property is TIME-OFFSET. 1210 3.1.5.6 Version 1212 This property specifies the identifier corresponding to the highest 1213 version number of the MIME Calendaring and Scheduling Content Type 1214 specification supported by the implementation that created the MIME 1215 calendar object. The value of this property must be 1.0 to correspond 1216 to this specification.. 1218 This property is identified by the property name VERSION. The 1219 following is an example of this property: 1221 VERSION:1.0 1223 This property is required for MIME entities conforming to this 1224 content type. This property must appear within the MIME calendar 1225 object. The default data type for this property is FLOAT. 1227 3.1.6 Event and Todo Component Properties 1229 The following properties apply to either an event or todo calendar 1230 object component. 1232 3.1.6.1 Attachment 1234 This property is identified by the property name ATTACH. The property 1235 defines an attached object to the MIME calendar object. For example, 1236 a document to be reviewed at a scheduled event or the process steps 1237 for a todo. The property value can be a text string, a reference to 1238 another message body part or a reference to a URL corresponding to a 1239 document. 1241 Multiple attachments may be specified by including multiple ATTACH 1242 properties within the MIME calendaring entity. 1244 The following are examples of this property: 1246 Dawson 23 Expires June 1997 1247 ATTACH;VALUE=CONTENT-ID: 1250 ATTACH;VALUE=URL:file://xyzCorp.com/pub/reports/r-960812.ps 1252 This property is optional for MIME entities conforming to this 1253 content type. The default data type for this property is MID. The 1254 data type may alternatively be specified to be CID, URL, or STRING 1255 value. 1257 3.1.6.2 Attendee 1259 This property is identified by the property name ATTENDEE. The 1260 property defines an attendee to a group event or todo. The default 1261 property value is an (RFC 822) address. The property may include 1262 property parameters TYPE, for the type of attendee, ROLE, for the 1263 role of the attendee in the event or todo; STATUS, for the status of 1264 the attendee's participation in the event or todo, RSVP, for 1265 indicating whether the favor of a reply is requested, EXPECT, to 1266 indicate the expectation of the attendee's participation by the 1267 originator, and MEMBER, to indicate the group that the attendee 1268 belongs to.. 1270 Multiple attendees may be specified by including multiple ATTENDEE 1271 properties within the MIME calendaring entity. 1273 The property value may reference a vCard object. This provides a 1274 useful mechanism to allow more than just the address of the attendee 1275 to be referenced. 1277 The TYPE property parameter for each attendee can have the following 1278 values: 1280 Dawson 24 Expires June 1997 1281 Description Property 1282 Value 1284 Indicates INDIVIDUAL 1285 attendee is an 1286 individual. 1288 Indicates GROUP 1289 attendee is a 1290 group of 1291 individuals. 1293 Indicates RESOURCE 1294 attendee is a 1295 resource. 1297 Indicates UNKNOWN 1298 attendee type 1299 is unknown. 1301 The ROLE property parameter for each attendee can have the following 1302 values: 1304 Description Property 1305 Value 1307 Indicates an ATTENDEE 1308 attendee at the 1309 event or todo 1311 Indicates ORGANIZER 1312 organizer of 1313 the event, but 1314 not owner 1316 Indicates owner OWNER 1317 of the event or 1318 todo. 1320 Indicates a DELEGATE 1321 delegate of 1322 another 1323 attendee. 1325 Dawson 25 Expires June 1997 1326 The default value for this property parameter is ATTENDEE. 1328 The STATUS property parameter for each attendee can have the 1329 following values: 1331 Description Property 1332 Value 1334 Indicates todo ACCEPTED 1335 was accepted by 1336 attendee 1338 Indicates event NEEDS ACTION 1339 or todo 1340 requires action 1341 by attendee 1343 Indicates event SENT 1344 or todo was 1345 sent out to 1346 attendee 1348 Indicates event TENTATIVE 1349 is tentatively 1350 accepted by 1351 attendee 1353 Indicates CONFIRMED 1354 attendee has 1355 confirmed their 1356 attendance at 1357 the event 1359 Indicates event DECLINED 1360 or todo has 1361 been rejected 1362 by attendee 1364 Indicates todo COMPLETED 1365 has been 1366 completed by 1367 attendee 1369 Indicates event DELEGATED 1370 or todo has 1371 been delegated 1372 by the attendee 1373 to another 1375 Dawson 26 Expires June 1997 1376 Indicates the CANCELED 1377 event or todo 1378 has been 1379 canceled and/or 1380 this attendee 1381 has been 1382 removed from 1383 the list of 1384 attendees. 1386 The default value for this property parameter is NEEDS ACTION. 1388 The RSVP property parameter for each attendee can have the following 1389 values: 1391 Description Property 1392 Value 1394 Indicates a YES 1395 reply is 1396 requested 1398 Indicates a NO 1399 reply is not 1400 requested. 1402 The default value for this property parameter is NO. 1404 The EXPECT property parameter for each attendee can have the 1405 following values: 1407 Description Property 1408 Value 1410 Indicates FYI 1411 request is for 1412 your 1413 information. 1415 Dawson 27 Expires June 1997 1416 Indicates REQUIRE 1417 presence is 1418 definitely 1419 required. 1421 Indicates 1422 presence is 1423 REQUEST 1424 being requested 1426 Indicates an IMMEDIATE 1427 immediate 1428 response 1429 needed. 1431 The default value for this property parameter is FYI. 1433 The MEMBER property parameter value is an (RFC 822) address that 1434 represents the group or distribution list. 1436 The following is an example of this property's use for a todo: 1438 ATTENDEE;ROLE=OWNER;STATUS=COMPLETED:jsmith@host1.com 1440 The following is an example of this property used for specifying 1441 multiple attendees to an event: 1443 ATTENDEE;ROLE=OWNER;STATUS=CONFIRMED:John Smith 1444 ATTENDEE;ROLE=ATTENDEE;STATUS=TENTATIVE:Henry Cabot 1445 1446 ATTENDEE;ROLE=DELEGATE;STATUS=CONFIRMED:Jane Doe 1448 The following is an example of this property with the value specified 1449 as an URL reference to a vCard that contains the information about 1450 the attendee: 1452 ATTENDEE;ROLE=ATTENDEE;STATUS=CONFIRMED;VALUE=URL: 1453 http://www.xyz.com/~myvcard.vcf 1455 This property is optional for MIME entities conforming to this 1456 content type. The default data type for this property is RFC822- 1457 ADDRESS. 1459 3.1.6.3 Audio Reminder 1461 This property is identified by the property name AALARM. The property 1462 defines an audio reminder for the MIME calendar object. An audio 1463 reminder is an alarm that is sounded for a calendar component.. 1465 The value for the audio reminder consists of the Run Time, or the 1466 date and time that the reminder is to be executed; Snooze Time, or 1468 Dawson 28 Expires June 1997 1469 the duration of time after the Run Time that the reminder is to be 1470 dormant prior to being repeated; Repeat Count, or the number of times 1471 that the reminder is to be repeated; and the Audio Content, or the 1472 digital sound to be played when the reminder is executed. 1474 The following are some examples of this property: 1476 AALARM;TYPE=WAVE;VALUE=URL:19960415T235959; ; ; 1477 file:///mmedia/taps.wav 1479 AALARM;TYPE=WAVE;VALUE=CONTENT- 1480 ID:19960903T060000;PT15M;4; 1483 The property has the following additional property parameters: 1485 Description Property 1486 Parameter 1487 Values 1489 TYPE 1491 Indicates the BASIC 1492 MIME basic 1493 audio content 1494 type. 1496 Indicates the WAVE 1497 WAVE format for 1498 audio content. 1500 Indicates the AIFF 1501 AIFF format for 1502 audio content. 1504 The Reminder properties are primarily provided as a means for 1505 allowing the capture of alarm information when accessing a calendar 1506 system. It may not be an appropriate property to send in an event or 1507 todo request. 1509 This property is optional for MIME entities conforming to this 1510 content type. The default data type for this property is AALARM. The 1511 data type may alternatively be specified to be CID, MID, or URL. 1513 Dawson 29 Expires June 1997 1514 3.1.6.4 Categories 1516 This property is identified by the property name CATEGORIES. This 1517 property defines the categories for the MIME calendar component. More 1518 than one category may be specified as a list of categories separated 1519 by the Semi-Colon character (ASCII decimal 59). 1521 The following are some examples of this property: 1523 CATEGORIES:APPOINTMENT;EDUCATION 1525 CATEGORIES:MEETING 1527 Some of the possible values for this property might include the 1528 following: 1530 Some Possible 1532 Property Values 1534 APPOINTMENT 1536 BUSINESS 1538 EDUCATION 1540 HOLIDAY 1542 MEETING 1544 MISCELLANEOUS 1546 NON-WORKING-HOURS 1548 NOT-IN-OFFICE 1550 PERSONAL 1552 PHONE CALL 1554 SICK DAY 1556 SPECIAL OCCASION 1558 TRAVEL 1560 VACATION 1562 Dawson 30 Expires June 1997 1563 This property is optional for MIME entities conforming to this 1564 content type. The default data type for this property is STRING-LIST. 1566 3.1.6.5 Classification 1568 This property is identified by the property name CLASS. This property 1569 defines the access classification for the MIME calendar component. 1571 A calendar event/todo access classification is only one component of 1572 the general security system within a calendar application. It 1573 provides a method of capturing the scope of the access the calendar 1574 owner intends for information within an individual calendar entry. 1575 The access classification of an individual MIME calendaring entity is 1576 useful when measured along with the other security components of a 1577 calendar system (e.g., user authorization, access rights, access 1578 role, etc.). Hence, the semantics of the individual access 1579 classifications can not be completely defined by this specification. 1580 Additionally, due to the _blind_ nature of most exchange processes 1581 using this specification, these entity classifications can not serve 1582 as an enforcement statement for a system receiving a MIME calendar 1583 object . Rather, they provide a method for capturing the intention of 1584 the calendar owner for the access to the MIME calendar object 1585 component. 1587 The following is an example of this property: 1589 CLASS:PUBLIC 1591 The property can have the following values: 1593 Description Property 1594 Value 1596 Indicates PUBLIC 1597 general, public 1598 access. 1600 Indicates PRIVATE 1601 restricted, 1602 private access. 1604 Indicates very CONFIDENTIAL 1605 restricted, 1606 confidential 1607 access. 1609 The default value for this property is PUBLIC. 1611 Dawson 31 Expires June 1997 1612 This property is optional for MIME entities conforming to this 1613 content type. The default data type for this property is STRING. 1615 3.1.6.6 Date/Time Created 1617 This property is identified by the property name DCREATED. This 1618 property specifies the date and time that the MIME calendar component 1619 was created within the originating calendar system. This is not 1620 necessarily the same date and time that the MIME calendar object was 1621 created. The date and time value is the local or UTC based time 1622 expressed in the complete representation, basic or extended format as 1623 specified in ISO 8601. The following is an example of this property: 1625 DCREATED:19960329T083000-0500 1627 This property is optional for MIME entities conforming to this 1628 content type. The default data type for this property is DATE-TIME. 1630 3.1.6.7 Date/Time Completed 1632 This property is identified by the property name COMPLETED. This 1633 property defines the date and time that the todo was actually 1634 completed. The date and time value is expressed in the complete 1635 representation, basic or extended format as specified in ISO 8601. 1636 The time can either be in local or UTC based time. The following is 1637 an example of this property: 1639 COMPLETED:19960401T235959Z 1641 This property is optional for MIME entities conforming to this 1642 content type. The default data type for this property is DATE-TIME. 1644 3.1.6.8 Description 1646 This property is identified by the property name DESCRIPTION. This 1647 property provides a more complete description of the MIME calendar 1648 component, than that provided by the SUMMARY property. The following 1649 is an examples of the property with formatted line breaks in the 1650 property value: 1652 DESCRIPTION;ENCODING=QUOTED-PRINTABLE:Meeting to provide technical= 1653 review for _Phoenix_ design.=0D=0A= 1654 Happy Face Conference Room. Phoenix design team= 1655 must attend this meeting. RSVP to team leader. 1657 The following is an examples of the property with folding of long 1658 lines: 1660 DESCRIPTION:Last draft of the new novel is to be completed 1661 for the editor's proof today. 1663 This property is required for MIME entities conforming to this 1664 content type. The default data type for this property is STRING. 1666 Dawson 32 Expires June 1997 1667 3.1.6.9 Display Reminder 1669 This property is identified by the property name DALARM. The property 1670 defines a display reminder for the MIME calendar component. A display 1671 reminder is an alarm that is popped up into the user interface or 1672 otherwise visually displayed for a calendar component. 1674 The value for the display reminder consists of the Run Time, or the 1675 date and time that the reminder is to be executed; Snooze Time, or 1676 the duration of time after the Run Time that the reminder is to be 1677 dormant prior to being repeated; Repeat Count, or the number of times 1678 that the reminder is to be repeated; and the Display String, or the 1679 text to be displayed when the reminder is executed. 1681 The following is an example of this property: 1683 DALARM:19960415T235000-0800;PT5M;2;Your Taxes Are Due !!! 1685 The Reminder properties are primarily provided as a means for 1686 allowing the capture of alarm information when accessing a calendar 1687 system. It may not be an appropriate property to send in an event or 1688 todo request. 1690 This property is optional for MIME entities conforming to this 1691 content type. The default data type for this property is DALARM. The 1692 data type may alternatively be specified to be CID, MID, or URL. 1694 3.1.6.10 Due Date/Time 1696 This property is identified by the property name DUE. This property 1697 defines the date and time that the todo is due to be completed. The 1698 date and time value is expressed in the complete representation, 1699 basic or extended format as specified in ISO 8601. The time can 1700 either be in local or UTC based time. Alternatively, the value may be 1701 a duration of time, expressed in the ISO 8601 format as specified in 1702 section 3.1.3.8. In this case, the end is relative to the start of 1703 the MIME calendar component. The following is an example of this 1704 property: 1706 DUE:19960401T235959Z 1708 This property is required for MIME entities consisting of a todo 1709 calendar component that conforms to this content type. The default 1710 data type for this property is DATE-TIME. The data type may 1711 alternatively be specified as a DURATION. 1713 3.1.6.11 Duration 1715 This property is identified by the property name DURATION. The 1716 property specifies an interval or duration of time. The following is 1717 an example of this property that specifies an interval of time of 1 1718 hour and zero minutes and zero seconds: 1720 DURATION:P1H0M0S 1722 Dawson 33 Expires June 1997 1723 The following is an example of this property that specifies an 1724 interval of time of 24 hours. 1726 DURATION:P24H 1728 This property is optional for MIME entities conforming to this 1729 content type. The default data type for this property is DURATION. 1731 3.1.6.12 End Date/Time 1733 This property is identified by the property name DTEND. This property 1734 defines the date and time that the event component will end. The date 1735 and time value is expressed in the complete representation, basic or 1736 extended format as specified in ISO 8601. The time can either be in 1737 local or UTC based time. Alternatively, the value may be a duration 1738 of time, expressed in the ISO 8601 format as specified in section 1739 3.1.3.8. In this case, the end is relative to the start of the MIME 1740 calendar component. Events may have an end date/time but no start 1741 date/time. In that case, the event does not take up any time. The 1742 following is an example of this property: 1744 DTEND:19960401T235959Z 1746 This property is required for MIME entities conforming to this 1747 content type. The default data type for this property is DATE-TIME. 1748 The data type may alternatively be specified as a DURATION. 1750 3.1.6.13 Exception Date/Times 1752 This property is identified by the property name EXDATE. This 1753 property defines the list of date/time exceptions for a recurring 1754 MIME calendar component. The date and time values is expressed in the 1755 complete representation, basic format as specified in ISO 8601. The 1756 times can either be in local or UTC based time. The following is an 1757 example of this property: 1759 EXDATE:19960402T010000Z;19960403T010000Z;19960404T010000Z 1761 This property is optional for MIME entities conforming to this 1762 content type. The default data type for this property is D-T-LIST. 1764 3.1.6.14 Exception Rule 1766 This property is identified by the property name EXRULE. This 1767 property defines a rule or repeating pattern for an exception to a 1768 recurring MIME calendaring entity, based on the Basic Recurrence Rule 1769 Grammar of the [XAPIA]. The value for the property is a pattern 1770 specification for the recurrence exception. The following are some 1771 examples of this property: 1773 EXRULE:W2 TU TH #2 // Except every other week, on Tuesday 1774 // and Thursday for 4 occurrences 1776 EXRULE:D1 #10 // Except daily for 10 occurrences 1778 Dawson 34 Expires June 1997 1779 EXRULE:YM1 6 7 #8 // Except yearly in June and July for 8 1780 // occurrences 1782 This property is optional for MIME entities conforming to this 1783 content type. The default data type for this property is RRULE. 1785 3.1.6.15 Last Modified 1787 This property is identified by the property name LAST-MODIFIED. The 1788 property specifies the date and time that the MIME calendar component 1789 was last revised. The following is an example of this property: 1791 LAST-MODIFIED:19960817T133000Z 1793 This property is optional for MIME entities conforming to this 1794 content type. The default data type for this property is DATE-TIME. 1796 3.1.6.16 Location 1798 This property is identified by the property name LOCATION. The 1799 property defines the intended location for the MIME calendar 1800 component. 1802 The property value may reference a vCard object. This provides a 1803 useful mechanism to specify a location in terms of its electronic 1804 business card. 1806 The following are some examples of this property: 1808 LOCATION:Conference Room - F123, Bldg. 002 // or 1810 LOCATION;VALUE=URL:http://www.xyzcorp.com/~jsmith.vcf 1812 This property is optional for MIME entities conforming to this 1813 content type. The default data type for this property is STRING. The 1814 data type may alternatively be specified to be CID, MID, or URL. 1816 3.1.6.17 Mail Reminder 1818 This property is identified by the property name MALARM. The property 1819 defines an email address that is to be sent a reminder for the MIME 1820 calendar component. A mail reminder is an electronic mail address 1821 that will be sent a display string as an alarm for a calendar 1822 component. 1824 The value for the procedure reminder consists of the Run Time, or the 1825 date and time that the reminder is to be executed; Snooze Time, or 1826 the duration of time after the Run Time that the reminder is to be 1827 dormant prior to being repeated; Repeat Count, or the number of times 1828 that the reminder is to be repeated; Email Address, or the (RFC 822) 1829 email address that is to be sent the reminder, Subject, or the 1830 textual subject of the note, and the Note, or the textual reminder 1831 string that is to be sent to the email address. 1833 Dawson 35 Expires June 1997 1834 The following is an example of this property: 1836 MALARM:19960416T000000-0500;PT1H;24;IRS@us.gov;My Payment; 1837 The Check Is In The Mail! 1839 The Reminder properties are primarily provided as a means for 1840 allowing the capture of alarm information when accessing a calendar 1841 system. It may not be an appropriate property to send in an event or 1842 todo request. 1844 This property is optional for MIME entities conforming to this 1845 content type. The default data type for this property is MALARM. The 1846 data type may alternatively be specified to be CID, MID, or URL. 1848 3.1.6.18 Number Recurrences 1850 This property is identified by the property name RNUM. The property 1851 defines the number of times the calendar entry will reoccur. The 1852 value is equal to the number of recurrences that are specified by the 1853 union of the Recurrence Dates, Recurrence Rule, Exception Dates, and 1854 Exception Rule property values. The following is an example of this 1855 property: 1857 RNUM:3 1859 In the event that this value does not match the computed number of 1860 recurrences, it will be ignored and the computer number of 1861 recurrences will be used. 1863 This property is optional for MIME entities conforming to this 1864 content type. The default data type for this property is INTEGER. 1866 3.1.6.19 Priority 1868 This property is identified by the property name PRIORITY. The 1869 property defines the priority for the MIME calendar component. The 1870 value is an alphanumeric. A value of zero (ASCII decimal 48) 1871 specifies an undefined priority. A value of one (ASCII decimal 49) is 1872 the highest priority. A value of two (ASCII decimal 50) is the second 1873 highest priority. Subsequent numbers specify a decreasing ordinal 1874 priority. The following is an example of this property: 1876 PRIORITY:2 1878 This property is optional for MIME entities conforming to this 1879 content type. The default data type for this property is STRING. The 1880 data type may alternatively be specified to be INTEGER. 1882 3.1.6.20 Procedure Reminder 1884 This property is identified by the property name PALARM. The property 1885 defines a procedure reminder for the MIME calendar component. A 1886 procedure reminder is a procedure, or application executable that 1887 will be run as an alarm for a calendar component. 1889 Dawson 36 Expires June 1997 1890 While this property has many useful purposes, implementers should be 1891 aware of the security implications of sending a MIME calendaring 1892 entity containing this property. The security implications are 1893 similar to those associated with active messages within electronic 1894 mail. 1896 The value for the procedure reminder consists of the Run Time, or the 1897 date and time that the reminder is to be executed; Snooze Time, or 1898 the duration of time after the Run Time that the reminder is to be 1899 dormant prior to being repeated; Repeat Count, or the number of times 1900 that the reminder is to be repeated; and the Procedure Name, or the 1901 path to the procedure to be run when the reminder is executed. 1902 Parameters are passed to the procedure by concatenating to the 1903 Procedure Name value a Question-Mark (ASCII decimal 63) followed by a 1904 string representation of the parameters. 1906 The following is an example of this property: 1908 PALARM;VALUE=URL:19960415T235000-0500;PT5M;2;file:///myapps/ 1909 shockme.exe?HARD 1911 The Reminder properties are primarily provided as a means for 1912 allowing the capture of alarm information when accessing a calendar 1913 system. It may not be an appropriate property to send in an event or 1914 todo request. 1916 This property is optional for MIME entities conforming to this 1917 content type. The default data type for this property is PALARM. The 1918 data type may alternatively be specified to be CID, MID, or URL. 1920 3.1.6.21 Related To 1922 This property is identified by the property name RELATED-TO. The 1923 property is used to represent relationships or references between 1924 this MIME calendar component and another. The property value consists 1925 of the persistent, globally unique identifier of another MIME 1926 calendar component. This value would be represented in a MIME 1927 calendar component by the UID property. 1929 A linked relationship can be specified by a series of components that 1930 each, in turn, refer to their parent component. A group relationship 1931 can be specified by a number of components that all refer to one 1932 common parent component. 1934 Changes to a calendar component referenced by this property may 1935 impact the related calendar component. For example, if a group event 1936 changes its start or end date or time, then the related, dependent 1937 events will need to have their start and end dates changed in a 1938 corresponding way. This property is intended only to provide 1939 information on the relationship of calendar components. It is up to 1940 the target calendar system to maintain this relationship. 1942 The following is an example of this property: 1944 Dawson 37 Expires June 1997 1945 RELATED-TO: 1947 RELATED-TO:19960401-080045-4000F192713-0052 1949 This property is optional for MIME entities conforming to this 1950 content type. The default data type for this property is STRING. The 1951 data type may alternatively be specified to be CID, MID, or URL. 1953 3.1.6.22 Recurrence Date/Times 1955 This property is identified by the property name RDATE. This property 1956 defines the list of date/times for a recurring MIME calendar 1957 component. The date and time values is expressed in the complete 1958 representation, basic format as specified in ISO 8601. The times can 1959 either be in local or UTC based time. The number of recurring 1960 date/times is specified by the Number Recurrences property. The 1961 following is an example of this property: 1963 RDATE:19960402T010000Z;19960403T010000Z;19960404T010000Z 1965 This property is optional for MIME entities conforming to this 1966 content type. The default data type for this property is D-T-LIST. 1968 3.1.6.23 Recurrence Rule 1970 This property is identified by the property name RRULE. This property 1971 defines a rule or repeating pattern for a recurring MIME calendar 1972 component, based on the Basic Recurrence Rule Grammar of [XAPIA]. The 1973 value for the property is a pattern specification for the recurrence. 1974 The following is an example of this property: 1976 RRULE:W2 TU TH // Every other week, on Tuesday 1977 // and Thursday 1979 RRULE:D1 #10 // Daily for 10 occurrences 1981 RRULE:YM1 6 7 #8 // Yearly in June and July for 8 1982 // occurrences 1984 This property is optional for MIME entities conforming to this 1985 content type. The default data type for this property is RRULE. 1987 3.1.6.24 Resources 1989 This property is identified by the property name RESOURCES. This 1990 property defines the equipment or resources needed in the MIME 1991 calendar component. 1993 Some of the values that the property may have include the following: 1995 Dawson 38 Expires June 1997 1996 Some Possible 1998 Property Values 2000 CATERING 2002 CHAIRS 2004 COMPUTER PROJECTOR 2006 EASEL 2008 OVERHEAD PROJECTOR 2010 SPEAKER PHONE 2012 TABLE 2014 TV 2016 VCR 2018 VIDEO PHONE 2020 VEHICLE 2022 The following is an example of this property: 2024 RESOURCES:EASEL;PROJECTOR;VCR 2026 This property is optional for MIME entities conforming to this 2027 content type. The default data type for this property is STRING-LIST. 2028 The data type may alternatively be specified to be STRING. 2030 3.1.6.25 Response Sequence Number 2032 This property is identified by the property name RESPONSE-SEQUENCE. 2033 This property defines the instance of the MIME calendar component in 2034 a revision sequence of responses. This property is needed to properly 2035 handle the receipt and processing of a sequence of MIME calendar 2036 components that have been delivered out of order. Such is the case 2037 for store-and-forward based transports. When a response to an 2038 original MIME calendaring entity is created its sequence number is 2039 zero (ASCII decimal 48). It is incremented each time it is revised. 2040 The following is an example of this property: 2042 RESPONSE-SEQUENCE:1 2044 Dawson 39 Expires June 1997 2045 This property is optional for MIME entities conforming to this 2046 content type. The default data type for this property is INTEGER. 2048 3.1.6.26 Sequence Number 2050 This property is identified by the property name SEQUENCE. This 2051 property defines the instance of the MIME calendar component in a 2052 sequence of revisions. This property is needed to properly handle the 2053 receipt and processing of a sequence of MIME calendar components that 2054 have been delivered out of order. Such is the case for store-and- 2055 forward based transports. When a MIME calendaring entity is created 2056 its sequence number is zero (ASCII decimal 48). It is incremented 2057 each time it is revised by the OWNER and/or ORGANIZER. The following 2058 is an example of this property: 2060 SEQUENCE:1 2062 This property is optional for MIME entities conforming to this 2063 content type. The default data type for this property is INTEGER. 2065 3.1.6.27 Start Date/Time 2067 This property is identified by the property name DTSTART. This 2068 property defines the date and time that the calendar component will 2069 start. The date and time value is expressed in the complete 2070 representation, basic format as specified in ISO 8601. The time can 2071 either be in local or UTC based time. Alternatively, the value may be 2072 a duration of time, expressed in the ISO 8601 format as specified in 2073 section 3.1.3.8. In this case, the start is relative to another MIME 2074 calendar component specified by the RELATED-TO property. Events may 2075 have a start date/time but no end date/time. In that case, the event 2076 does not take up any time. The following is an example of this 2077 property: 2079 DTSTART:19960401T235959-0600 2081 This property is optional for MIME entities conforming to this 2082 content type. The default data type for this property is DATE-TIME. 2083 The data type may alternatively be specified to be DURATION. 2085 3.1.6.28 Status 2087 This property is identified by the property name STATUS. This 2088 property defines the status associated with the MIME calendar 2089 component. This property can also be used when the ATTENDEE property 2090 is either not supported or not needed. The following is an example of 2091 this property: 2093 STATUS:TENTATIVE 2095 The property can have the following values: 2097 Dawson 40 Expires June rming to this 2098 content type. The default data type for this property is STRING. 2100 3.1.6.30 Time Transparency 2102 This property is identified by the property name TRANSP. This 2103 property defines whether the event is transparent to free time 2104 searches. The value of this property is a number. A value of zero 2105 (ASCII decimal 48) guarantees that the entry will blocks time and 2106 will be factored into a free time search. A value of one (ASCII 2107 decimal 49) specifies that the entry will not block time and will not 2108 be factored into a free time search. Any values greater than _1_ will 2109 provide implementation specific transparency semantics. Some 2110 implementations may treat values greater than one as non-blocking or 2111 transparent events. Other implementations may use the numeric value 2112 to provide a layering of levels of transparency. The default value is 2113 zero (ASCII decimal 48), the event is not transparent and will block 2114 free time searches. The following is an example of this property: 2116 TRANSP:0 2118 This property is optional for MIME entities conforming to this 2119 content type. The default data type for this property is INTEGER. 2121 3.1.6.31 Uniform Resource Locator 2123 This property is identified by the property name URL. This property 2124 defines a Uniform Resource Locator for an Internet location that can 2125 be used to obtain real-time information associated with the MIME 2126 calendar component. Valid values for this property are a string 2127 conforming to [IETF RFC 1738]. The following is an example of this 2128 property: 2130 URL:http://abc.com/pub/calendars/jsmith/mytime.or3 2132 This property is optional for MIME entities conforming to this 2133 content type. The default data type for this property is URL. 2135 3.1.6.32 Unique Identifier 2137 This property is identified by the property name UID. This property 2138 defines a persistent, globally unique identifier associated with the 2139 MIME calendar component. Some examples of forms of unique identifiers 2141 Dawson 42 Expires June 1997 2142 would include ISO 9070 formal public identifiers (FPI), X.500 2143 distinguished names, machine-generated _random_ numbers with a 2144 statistically high likelihood of being globally unique and Uniform 2145 Resource Locators (URL). If an URL is specified, it is suggested that 2146 the URL reference a service which can provide an updated version of 2147 the MIME calendar component. The following is an example of this 2148 property: 2150 UID:19960401-080045-4000F192713-0052 2152 This property is an important method for group scheduling 2153 applications to match calendar entities with later modification or 2154 deletion requests. Calendaring and scheduling applications that do 2155 not generate this property in MIME calendar components may be 2156 limiting their interoperability with other group scheduling 2157 applications. 2159 This property is optional for MIME entities conforming to this 2160 content type. The default data type for this property is STRING. The 2161 data type may alternatively be specified to be CID, MID, or URL. 2163 3.1.6.33 Non-standard Properties 2165 The MIME Calendaring and Scheduling Content Type provides a _standard 2166 mechanism for doing non-standard things_. This extension support is 2167 provided for implementers to _push the envelope_ on the existing 2168 version of the specification. Extension properties are specified by 2169 property and/or property parameter names that have the initial sub- 2170 string of X- (the two character sequence: Capital X character 2171 followed by the Dash character). It is recommended that vendors 2172 concatenate onto this sentinel an added short sub-string to identify 2173 the vendor. This will facilitate readability of the extensions and 2174 minimize possible collision of names between different vendors. User 2175 agents that support this content type are expected to be able to 2176 parse the extension properties and property parameters but may ignore 2177 them. The following might be the ABC vendor's extension for an audio- 2178 clip form of subject property: 2180 X-ABC-MMSUBJ;TYPE=WAVE; VALUE=URL: http://load.noise.org/mysubj.wav 2182 At present, there is no registration authority for names of extension 2183 properties and property parameters. The default data type for this 2184 property is STRING. 2186 3.2 Formal Definition 2188 The following modified Backus-Naur Notation (BNF) is provided to 2189 assist developers in building parsers for the properties of this MIME 2190 content type.. 2192 This syntax is written according to the form described in RFC 2193 822,but it references just this small subset of RFC 822 literals: 2195 CR = ; ( 15, 13.) 2197 Dawson 43 Expires June 1997 2198 LF = ; ( 12, 10.) 2200 CRLF = CR LF 2202 SPACE = ; ( 40, 32.) 2204 HTAB = ; ( 11, 9.) 2206 All literal property names are valid as upper, lower, or mixed 2207 case. 2209 ws = 1*(SPACE / HTAB) 2211 ; _whitespace,_ one or more spaces or tabs 2213 wsls = 1*(SPACE / HTAB / CRLF) 2215 ; whitespace with line separators 2217 value = 7bit / 8bit / quoted-printable / base64 2219 ; The value must be in the encoding type specified for the 2220 ; property value. 2222 7bit = <7bit us-ascii printable chars, excluding CR LF> 2224 8bit = 2226 quoted-printable = 2228 base64 = 2230 ; the end of the text is marked with two CRLF sequences 2232 ; this results in one blank line before the start of the next 2234 ; property 2236 word = 2238 vcal_file = [wsls] vcal [wsls] 2240 vcal = _BEGIN_ [ws] _:_ [ws] _VCALENDAR_ [ws] 2241 1*CRLF 2243 calprop calentities [ws] *CRLF 2245 _END_ [ws] _:_ [ws] _VCALENDAR_ [ws] 1*CRLF 2247 calentities = calentities *CRLF calentity 2249 / calentity 2251 calentity = evententity 2253 Dawson 44 Expires June 1997 2254 / todoentity 2256 evententity = _BEGIN_ [ws] _:_ [ws] _VEVENT_ [ws] 1*CRLF 2258 entprops [ws] *CRLF 2260 _END_ [ws] _:_ [ws] _VEVENT_ [ws] 1*CRLF 2262 todoentity = _ _ 2263 BEGIN [ws] _:_ [ws] _VTODO_ [ws] 1*CRLF 2265 entprops [ws] *CRLF 2267 _END_ [ws] _:_ [ws] _VTODO_ [ws] 1*CRLF 2269 calprops = calprops *CRLF calprop 2271 / calprop 2273 calprop = _PROFILE_ 2275 [parms] _:_ value CRLF 2277 / _DAYLIGHT_ 2279 [params] _:_ value CRLF 2281 / _GEO_ 2283 [params] _:_ value CRLF 2285 / _PRODID_ 2287 [params] _:_ value CRLF 2289 / _TZ_ 2291 [params] _:_ value CRLF 2293 / _VERSION_ _:_ _1.0_ CRLF 2295 ; The VERSION calendar property MUST appear in the MIME Calendar 2296 ; Object. 2298 entprops = entprops *CRLF entprop 2300 / entprop 2302 entprop = [ws] simprop 2304 [params] _:_ value CRLF 2306 / [ws] _AALARM_ 2308 [params] _:_ aalarmparts CRLF 2310 Dawson 45 Expires June 1997 2311 / [ws] _CATEGORIES_ 2313 [params] _:_ 1*catvals CRLF 2315 / [ws] _CLASS_ 2317 [params] _:_ classvals CRLF 2319 / [ws] _DALARM_ 2321 [params] _:_ dalarmparts CRLF 2323 / [ws] _EXDATE_ 2325 [params] _:_ xdatevals CRLF 2327 / [ws] _MALARM_ 2329 [params] _:_ malarmparts CRLF 2331 / [ws] _PALARM_ 2333 [params] _:_ palarmparts CRLF 2335 / [ws] _RDATE_ 2337 [params] _:_ rdatevals CRLF 2339 / [ws] _RESOURCES_ 2341 [params] _:_ 1*resvals CRLF 2343 / [ws] _STATUS_ 2345 [params] _:_ statvals CRLF 2347 simprop = _ATTACH_ / _ATTENDEE_ / _DCREATED_ / _COMPLETED_ 2349 / _DESCRIPTION_ / _DTSTART_ / _DUE_ / _DTEND_ / _EXRULE_ 2351 / _LAST-MODIFIED_ / _LOCATION_ / _RNUM_ / _PRIORITY_ 2353 / _RELATED-TO_ / _RESPONSE-SEQUENCE_ / _RRULE_ 2355 / _SEQUENCE_ / _SUMMARY_ / _TRANSP_ / _URL_ / _UID_ 2357 / _X-_ word 2359 aalarmparts = 0*3(strnosemi _;_) strnosemi 2361 ; runTime, snoozeTime, repeatCount, audioContent 2363 catvals = _APPOINTMENT_ / _ _ / 2364 BUSINESS _EDUCATION_ / _HOLIDAY_ 2366 Dawson 46 Expires June 1997 2367 / _MEETING_ / _MISCELLANEOUS_ / _NOT-IN-OFFICE_ 2369 / _NON-WORKING-HOURS_ / _PERSONAL_ / _PHONE CALL_ 2371 / _SICK DAY_ / _SPECIAL OCCASION_ / _TRAVEL_ 2373 / _VACATION_ / _X-_ word / value 2375 classvals = _PUBLIC_ / _PRIVATE_ / _CONFIDENTIAL_ / _X-_ word 2377 / value 2379 dalarmparts = 0*3(strnosemi _;_) strnosemi 2381 ; runTime, snoozeTime, repeatCount, displayString 2383 malarmparts = 0*5(strnosemi _;_) strnosemi 2385 ; runTime, snoozeTime, repeatCount, addressString, 2386 ; subjectstring, noteString 2388 palarmparts = 0*3(strnosemi _;_) strnosemi 2390 ; runTime, snoozeTime, repeatCount, procedureName 2392 rdatevals = 1*value 2394 ; One or more date/time values 2396 resvals = _CATERING_ / _CHAIRS_ / _EASEL_ / _PROJECTOR_ / _VCR_ 2398 / _VEHICLE_ / _X-_ word / value 2400 statvals = _ACCEPTED_ / _NEEDS ACTION_ / _SENT_ / _TENTATIVE_ 2402 / _CONFIRMED_ _ 2403 / DECLINED_ / _COMPLETED_ / _DELEGATED_ 2405 / _X-_ word / value 2407 params = _;_ [ws] paramlist 2409 paramlist = paramlist [ws] _;_ [ws] param 2411 / param 2413 param = _TYPE_ [ws] _=_ [ws] ptypeval 2415 / [_VALUE_ [ws] _=_ [ws]] pvalueval 2417 / [_ENCODING_ [ws] _=_ [ws]] pencodingval 2419 / _CHARSET_ [ws] _=_ [ws] charsetval 2421 / _DATATYPE_ [ws] _=_ [ws] dtypeval 2423 Dawson 47 Expires June 1997 2424 / _LANGUAGE_ [ws] _=_ [ws] langval 2426 / _MEMBER_ [ws] _=_ [ws] 2428 / _ROLE_ [ws] _=_ [ws] roleval 2430 / _STATUS_ [ws] _=_ [ws] statuval 2432 / _X-_ word [ws] _=_ [ws] word 2434 / knowntype 2436 ptypeval = knowntype / attendtype / _X-_ word 2438 knowntype = _BASIC_ / _WAVE_ / _X-_ word / value 2440 attendtype = _INDIVIDUAL_ / _GROUP_ / _RESOURCE_ / _UNKNOWN_ 2442 pvalueval = _INLINE_ / _URL_ / _CONTENT-ID_ / _CID_ / 2444 / _MESSAGE-ID_ / _MID_ / _X-_ word 2446 pencodingval = _7BIT_ / _8BIT_ / _QUOTED-PRINTABLE_ / _BASE64_ 2448 / _X-_ word 2450 charsetval = 2453 dtypeval = _AALARM_ / _BOOLEAN_ / _CID_ / _DALARM_ / _DATE-TIME_ 2455 / _DST-RULE / 2456 _ _D-T-LIST_ / _DURATION_ / _FLOAT_ 2458 / _FLOAT-LIST_ / INTEGER 2459 _ _ / _INTEGER-LIST_ / _MALARM_ 2461 / _MID_ _ 2462 / PALARM_ / _RFC822-ADDRESS_ / _RRULE_ 2464 / _STRING_ / _STRING-LIST_ / _TIME-OFFSET_ / _URL_ 2466 / _X-_ word 2468 langval = 2470 roleval = _ATTENDEE_ / _ORGANIZER_ / _OWNER_ / _X-_ word 2472 statusval = _ _ 2473 ACCEPTED / _NEEDS ACTION_ / _SENT_ / _TENTATIVE_ 2475 / _CONFIRMED_ / _DECLINED_ / _COMPLETED_ / _DELEGATED_ 2477 / _X-_ word 2479 strnosemi = *(*nonsemi (_\;_ / _\_ CRLF)) *nonsemi 2481 ; To include a semicolon in this string, it must be escaped 2483 Dawson 48 Expires June 1997 2484 ; with a _\_ character. 2486 nonsemi = 2488 3.3 Basic Recurrence Rule Grammar 2490 The specification of recurring events can be simplified by the use of 2491 a grammar or rule notation. This specification makes use of the Base 2492 Recurrence Rule Grammar from the [XAPIA]. 2494 A recurrence rule is a string or clear-text encoding of a recurrence 2495 specification. A recurrence rule is composed of several components. A 2496 rule begins with a frequency which describes the type of repeating 2497 event (e.g., daily, weekly, etc.). This is followed by an interval 2498 which indicates how often the frequency repeats (i.e., daily, every 2499 third day, etc.). This can be followed by optional frequency modifier 2500 information and either an end date or a duration. 2502 Below is the form of a typical rule. This example causes events to be 2503 generated every other week on Tuesday and Thursday, for 8 2504 occurrences: 2506 W2 TU TH #4 2508 Where, W is the Frequency, 2 is the Interval, TU and TH are the 2509 optional Frequency Modifiers, and #4 is the Duration. 2511 The basic recurrence rule grammar supports six types of repetition. 2512 The six types follow the same form with only the frequency name and 2513 optional modifier information changing from one type of frequency to 2514 the next. 2516 3.3.1 Daily Rule 2518 The daily rule is used for specifying repeating events based on an 2519 interval of a day or more. These can range from every day to every 2520 200th day and beyond. The daily rule begins with the letter D 2521 followed by an interval (representing days) and an optional duration 2522 or end date. 2524 Some examples follow: 2526 Daily for 10 occurrences: 2527 D1 #10 2529 Daily until 12/24/94: 2530 D1 19941224T000000Z 2532 Every other day - forever: 2533 D2 #0 2535 Every 10 days, 5 occurrences: 2536 D10 #5 2538 Dawson 49 Expires June 1997 2539 3.3.2 Weekly Rule 2541 The weekly rule is used for specifying repeating events based on an 2542 interval of a week or more. The basic weekly rule has the same form 2543 as the daily rule except that the rule begins with a W and can 2544 contain an optional list of weekdays the events are generated on. For 2545 weekly rules, the interval represents weeks. Some examples follow: 2547 Weekly for 10 occurrences: 2548 W1 #10 2550 Weekly until 12/24/94: 2551 W1 19941224T000000Z 2553 Every other week - forever: 2554 W2 #0 2556 Weekly on Tuesday and 2557 Thursday for 5 weeks: 2558 W1 TU TH #5 2560 Every other week on Monday Wednesday and Friday until 12/24/94: 2561 W2 MO WE FR 19941224T000000Z 2563 3.3.3 Monthly Rule 2565 The monthly rule is used for specifying repeating events base on an 2566 interval of a month or more. There are two types of monthly 2567 recurrence rules. One for by-position and one for by-day. The by- 2568 position rule allows weekdays in the month to be specified in 2569 relation to their occurrence in the month. An example would be to 2570 specify the third Sunday of the month or the last Friday of the 2571 month. An occurrence specifier may be used in monthly by-position 2572 rules. The occurrence specifiers control which occurrence of a 2573 weekday in a month an event occurs on: 2575 1+, 2+, ... 5+ for the first occurrence, second, ...fifth 2576 occurrence of the month. 2578 1-, 2-, ... 5- for the last occurrence, second to last occurrence, 2579 etc. 2581 A 2+ FR SA would indicate the second occurrence of Friday and 2582 Saturday in the month. A 1- MO would indicate the first occurrence of 2583 Monday working from the end of the month backwards (i.e., the last 2584 occurrence). A 2- MO would be the second to the last Monday of the 2585 month. 2587 A by-day rule allows actual day numbers to be specified such as the 2588 12th day or 29th day. 2590 The by-position rule begins with a MP and the by-day rule begins with 2591 a MD. The interval in monthly rules represents months. Some examples 2592 follow: 2594 Dawson 50 Expires June 1997 2595 Monthly on the 1st Friday for ten occurrences: 2596 MP1 1+ FR #10 2598 Monthly on the 1st Friday until 12/24/94: 2599 MP1 1+ FR 19941224T000000Z 2601 Every other month on the 1st and last 2602 Sunday of the month for 10 occurrences: 2603 MP2 1+ SU 1- SU #10 2605 Every six months on the 2nd Monday 2606 thru Friday for 10 occurrences: 2607 MP6 2+ MO TU WE TH FR #10 2609 Monthly on the second last Monday of the month for 6 months: 2611 MP1 2- MO #6 2613 Monthly on the third to the last day of the month, forever: 2615 MD1 3- #0 2617 Monthly on the 2nd and 15th of the month for 10 occurrences: 2618 MD1 2 15 #10 2620 In the next example LD refers to _LastDay_ in a monthly recurrence 2621 rule. Monthly on the 1st and last day of the month for 10 2622 occurrences: 2623 MD1 1 LD #10 or MD1 1 1- #10 2625 Every 18 months on the 10th thru 15th of the month for 10 2626 occurrences: 2627 MD18 10 11 12 13 14 15 #10 2629 Monthly on the second to the last day for 5 months. So, if the 2630 start date is August 1996, the event would repeat on 8/30/96, 2631 9/29/96, 10/30/96, 11/29/96, and 12/30/96: 2632 MD1 2- #5 2634 3.3.4 Yearly Rule 2636 The yearly rule is used for specifying repeating events based on an 2637 interval of a year or more. There are two types of yearly recurrence 2638 rules. One for by-month and one for by-day. The by-month rule allows 2639 specific months out of the year to be specified. The by-day allows 2640 specific days to be specified. In the by-month rule, the day in the 2641 month the rule is to occur on is determined from the initial 2642 appointment. 2644 The by-month rule begins with a YM and the by-day rule begins with a 2645 YD. The interval in yearly rules represents years. Some examples 2646 follow: 2648 Dawson 51 Expires June 1997 2649 Yearly in June and July for 10 occurrences: 2650 YM1 6 7 #10 2652 Every other year on January, Feb, and March for 10 occurrences: 2653 YM2 1 2 3 #10 2655 Every 3rd year on the 1st, 100th and 200th day for 10 occurrences: 2656 YD3 1 100 200 #10 2658 3.3.5 Grammar 2660 {} 0 or more 2662 [] 0 or 1 2664 start ::= [] | 2666 [] | 2668 [] | 2670 [] | 2672 [] | 2674 [] 2676 digit ::= <0|1|2|3|4|5|6|7|8|9> 2678 digits ::= {} 2680 enddate ::= ISO 8601_date_time value(e.g., 19940712T101530Z) 2682 interval ::= 2684 duration ::= # 2686 lastday ::= LD 2688 plus ::= + 2690 minus ::= - 2692 daynumber ::= <1-31> [|]| 2694 daynumberlist ::= daynumber {} 2696 month ::= <1-12> 2698 monthlist ::= {} 2700 day ::= <1-366> 2702 daylist ::= {} 2704 Dawson 52 Expires June 1997 2705 occurrence ::= <1-5> | <1-5> 2707 occurrencelist ::= {} 2709 weekday ::= 2711 weekdaylist ::= {} 2713 daily ::= D [] 2715 weekly ::= W [] [] 2717 monthlybypos ::= MP [ 2718 ] [] 2720 monthlybyday ::= MD [] [] 2722 yearlybymonth ::= YM [] [] 2724 yearlybyday ::= YD [] [] 2726 3.3.6 Grammar Glossary 2728 enddate Controls when a repeating event terminates. The enddate 2729 is the last time an event can occur. 2731 Interval Defines the frequency in which a rule repeats. 2733 duration Controls the number of events a rule generates. 2735 Lastday Can be used as a replacement to daynumber to indicate 2736 the last day of the month. 2738 daynumber A number representing a day of the month. 2740 month A number representing a month of the year. 2742 day A number representing a day of the year. 2744 occurrence Controls which week of the month a particular weekday 2745 event occurs. 2747 weekday A symbol representing a day of the week. 2749 daily Defines a rule that repeats on a daily basis. 2751 weekly Defines a rule that repeats on a weekly basis. 2753 monthlybypos Defines a rule that repeats on a monthly basis on a 2754 relative day and week. 2756 monthlybyday Defines a rule that repeats on a monthly basis on an 2757 absolute day. 2759 Dawson 53 Expires June 1997 2760 yearlybymonth Defines a rule that repeats on specific months 2761 of the year. 2763 yearlybyday Defines a rule that repeats on specific days of the 2764 year. 2766 3.3.7 Policies 2768 1. 2769 The duration portion of a rule defines the total number of events 2770 the rule generates, including the first event. 2772 2. 2773 Information, not contained in the rule, necessary to determine the 2774 next event time and date is derived from the Start Time entry 2775 attribute. 2777 3. 2778 If an end date and a duration is specified in the rule, the 2779 recurring event ceases when the end date is reached or the number 2780 of events indicated in the duration occur; whichever comes first. 2782 4. 2783 If the duration or an end date is not established in the rule 2784 (e.g., D4) the event occurs twice. That is D4 is equivalent to D4 2785 #2. 2787 5. 2788 A duration of #0 means repeat this event forever. 2790 6. 2791 Using the occurrence specifier 5+ (e.g. 5th Friday) or 5- (e.g. 2792 5th from last Friday) in a month that does not contain 5 weeks 2793 does not generate an event and thus does not count against the 2794 duration. The same applies to providing a day of the month that 2795 does not occur in the month. For example the 30th or 31st . 2797 7. 2798 The start time and date of an entry must be synchronized with one 2799 of the repeating events defined by its recurrence rule. The 2800 following is not allowed: 2802 Initial Appt Date: 7/1/94 (Friday) 2803 Recurrence Rule: W1 MO TH #5 2805 The following is acceptable: 2807 Initial Appt Date: 7/1/94 (Friday) 2808 Recurrence Rule: W1 MO FR #5 or W1 #5 2810 8. 2811 If the optional and information is 2812 missing from a occurrence the information is 2813 derived from the entry attributes. The used in the 2814 recurring event is a count from the beginning of the month to the 2815 entry date and the used is the day of the week the entry 2816 is scheduled to occur on. 2818 9. 2819 If the occurrence or occurrence does 2820 not list a week day (e.g., SU or day 10) in the rule, the week day 2821 is established from the entry attribute information. As an example 2822 the rule MP1 #3 used in an entry with a start date of 7/20/94 2824 Dawson 54 Expires June 1997 2825 (which is the third Wednesday of the month) repeats on 8/17/94 2826 which is the third Wednesday of the month. 2828 4. Registration of Content Type Profiles 2830 This section defines procedures by which usage profiles for the MIME 2831 Calendaring and Scheduling Content Type are registered with the IANA 2832 and made available to the Internet community. Note that non-IANA 2833 profiles may be used by bilateral agreement, provided the associated 2834 profile names follow the "X-" convention defined above in Section 2835 3.1.6.33. 2837 The procedures defined here are designed to allow public comment and 2838 review of new profiles, while posing only a small impediment to the 2839 definition of new profiles. 2841 Registration of a new profile is accomplished by the following steps. 2843 4.1 Define the profile 2845 A profile is defined by completing the following template. 2847 To: ietf-calendar@imc.org 2849 Subject: Registration of text/calendar MIME profile XXX 2851 Profile name: 2853 Profile purpose: 2855 Profile type/subtype: 2857 Profile special notes (optional): 2859 Intended usage: (one of COMMON, LIMITED USE or OBSOLETE) 2861 The explanation of what goes in each field in the template follows. 2863 Profile name: The name of the profile as it will be generally 2864 referred to in public. This name is required in the profile. 2866 Profile purpose: The purpose of the profile (e.g., to schedule 2867 document management updates, etc.). Give a short but clear 2868 description. This description is required in the profile. 2870 Profile type/subtype: The type/subtypes of the profile as they will 2871 appear in the text/calendar MIME Content-Type Profile parameter. This 2872 list of type/subtype values is required in the profile. 2874 Profile properties: The list of MIME Calendaring and Scheduling 2875 Content Type properties associated with the profile. This list of 2876 properties that are included in the profile. If a property is 2877 required by the profile, it should noted in this section. Other types 2878 not mentioned in the profile definition may also be present. Note 2880 Dawson 55 Expires June 1997 2881 that any new properties referenced by the profile must be defined 2882 separately as described in Section 4.6. 2884 Profile special notes: Any special notes about the profile, how it is 2885 to be used, etc. This section is not required in the profile. 2887 4.2 Post the profile definition 2889 The profile description must be posted to the IETF Calendaring and 2890 Scheduling Working Group discussion list, ietf-calendar@imc.org. 2892 4.3 Allow a comment period 2894 Discussion on the new profile must be allowed to take place on the 2895 list for a minimum of two weeks. Consensus must be reached on the 2896 profile before submitting the profile for approval. 2898 4.4 Submit the profile for approval 2900 Once the two-week comment period has elapsed, and the proposer is 2901 convinced consensus has been reached on the profile, the registration 2902 application should be submitted to the Profile Reviewer for approval. 2904 The Profile Reviewer is appointed to the Application Area Directors 2905 and may either accept or reject the profile registration. An accepted 2906 registration should be passed on by the Profile Reviewer to the IANA 2907 for inclusion in the official IANA profile registry. The registration 2908 may be rejected for any of the following reasons. 1) Insufficient 2909 comment period; 2) Consensus not reached; 3) Technical deficiencies 2910 raised on the list or elsewhere have not been addressed. The Profile 2911 Reviewer's decision to reject a profile may be appealed by the 2912 proposer to the IESG, or the objections raised can be addressed by 2913 the proposer and the profile resubmitted. 2915 4.5 Profile Change Control 2917 Existing profiles may be changed using the same process by which they 2918 were registered. 2920 1. 2921 Define the change 2923 2. 2924 Post the change 2926 3. 2927 Allow a comment period 2929 4. 2930 Submit the profile for approval 2932 Note that the original author or any other interested party may 2933 propose a change to an existing profile, but that such changes should 2934 only be proposed when there are serious omissions or errors in the 2935 published specification. The Profile Reviewer may object to a change 2936 if it is not backwards compatible, but is not required to do so. 2938 Dawson 56 Expires June 1997 2939 Profile definitions can never be deleted from the IANA registry, but 2940 profiles which are no longer believed to be useful can be declared 2941 OBSOLETE by a change to their "intended use" field. 2943 4.6 Registration of New Content Type Properties 2945 This section defines procedures by which new properties for the MIME 2946 Calendaring and Scheduling Content Type are registered with the IANA. 2947 Note that non-IANA properties may be used by bilateral agreement, 2948 provided the associated properties names follow the "X-" convention 2949 defined above in Section 3.1.6.33. 2951 The procedures defined here are designed to allow public comment and 2952 review of new properties, while posing only a small impediment to the 2953 definition of new properties. 2955 Registration of a new property is accomplished by the following 2956 steps. 2958 4.6.1 Define the property 2960 A property is defined by completing the following template. 2962 To: ietf-calendar@imc.org 2964 Subject: Registration of text/calendar MIME property XXX 2966 Property name: 2968 Property purpose: 2970 Property data type(s): 2972 Property encoding: 2974 Property special notes (optional): 2976 Intended usage: (one of COMMON, LIMITED USE or OBSOLETE) 2978 The meaning of each field in the template is as follows. 2980 Property name: The name of the property, as it will appear in the 2981 body of an text/calendar MIME Content-Type "property: value" line to 2982 the left of the colon ":". 2984 Property purpose: The purpose of the property (e.g., to indicate a 2985 delegate for the event or todo, etc.). Give a short but clear 2986 description. 2988 Property data type(s): Any of the valid data types for the property 2989 value needs to be specified. The default data type also needs to be 2990 specified. If a new data type is specified, it needs to be declared 2991 in this section. 2993 Dawson 57 Expires June 1997 2994 Property encoding: The encodings permitted for the property value. 2995 This description must be precise and must not violate the general 2996 encoding rules defined in section 3.1.3.3of this document. 2998 Property special notes: Any special notes about the property, how it 2999 is to be used, etc. 3001 4.6.2 Post the Property definition 3003 The property description must be posted to the new property 3004 discussion list, ietf-calendar@imc.org. 3006 4.6.3 Allow a comment period 3008 Discussion on the new property must be allowed to take place on the 3009 list for a minimum of two weeks. Consensus must be reached on the 3010 property before proceeding to step 4. 3012 4.6.4 Submit the property for approval 3014 Once the two-week comment period has elapsed, and the proposer is 3015 convinced consensus has been reached on the property, the 3016 registration application should be submitted to the Profile Reviewer 3017 for approval. The Profile Reviewer is appointed to the Application 3018 Area Directors and may either accept or reject the property 3019 registration. An accepted registration should be passed on by the 3020 Profile Reviewer to the IANA for inclusion in the official IANA 3021 profile registry. The registration may be rejected for any of the 3022 following reasons. 1) Insufficient comment period; 2) Consensus not 3023 reached; 3) Technical deficiencies raised on the list or elsewhere 3024 have not been addressed. The Profile Reviewer's decision to 3026 reject a property may be appealed by the proposer to the IESG, or the 3027 objections raised can be addressed by the proposer and the property 3028 resubmitted. 3030 4.7 Content Type Property Change Control 3032 Existing properties may be changed using the same process by which 3033 they were registered. 3035 1. 3036 Define the change 3038 2. 3039 Post the change 3041 3. 3042 Allow a comment period 3044 4. 3045 Submit the property for approval 3047 Note that the original author or any other interested party may 3048 propose a change to an existing property, but that such changes 3049 should only be proposed when there are serious omissions or errors in 3050 the published specification. The Profile Reviewer may object to a 3052 Dawson 58 Expires June 1997 3053 change if it is not backwards compatible, but is not required to do 3054 so. 3056 Property definitions can never be deleted from the IANA registry, but 3057 properties which are no longer believed to be useful can be declared 3058 OBSOLETE by a change to their "intended use" field. 3060 5. File extension 3062 The file extension of _vcs_ is to be used to designate a file 3063 containing calendaring and scheduling information consistent with 3064 this MIME content type. 3066 6. Macintosh File Type Code 3068 The file type code of _vcal_ is to be used in Apple MacIntosh 3069 operating system environments to designate a file containing 3070 calendaring and scheduling information consistent with this MIME 3071 media type. 3073 7. Bibliography 3075 The following document are referred to within this document. 3077 [ISO 630] ISO 639, Code for The Representation of names of languages, 3078 International Organization for Standardization, April, 1988. 3080 [ISO 3166] ISO 3166, Codes for The Representation of names of 3081 countries, International Organization for Standardization, December, 3082 1993. 3084 [ISO 8601] ISO 8601, Data elements and interchange formats_ 3085 Information interchange_Representation of dates and times, 3086 International Organization for Standardization, June, 1988. 3088 [ISO 8601 CORR] ISO 8601, Technical Corrigendum 1, Data elements and 3089 interchange formats_Information interchange_Representation of dates 3090 and times, International Organization for Standardization, May, 1991. 3092 [ISO 8859-1] ISO 8859-1, Information Processing_8-Bit single-byte 3093 coded graphic character sets_Part 1: Latin Alphabet No. 1, 3094 International Organization for Standardization, February, 1987. 3096 [ISO 9070] ISO/IEC 9070, Information Technology_SGML Support 3097 Facilities_Registration Procedures for Public Text Owner Identifiers, 3098 Second Edition, International Organization for Standardization, 3099 April, 1991. 3101 [MIME-REG] Freed, N., Postel, J., "Multipurpose Internet Mail 3102 Extensions (MIME) - Part Four: Registration Procedures", Internet- 3103 Draft draft-ietf-822ext-mime-reg-02.txt, December 1995. 3105 [RFC 1521] N. Borenstein and N. Freed, "MIME (Multipurpose Internet 3106 Mail Extensions) Part One: Mechanisms for Internet Draft UTF-825 July 3108 Dawson 59 Expires June 1997 3109 1996 Specifying and Describing the Format of Internet Message 3110 Bodies", RFC 1521, Bellcore, Innosoft, September 1993. 3112 [RFC 1738] T. Berners-Lee and L. Masinter , _Universal Resource 3113 Locator_, RFC 1738, Xerox Corporation, University of Minnesota, 3114 December 1994. 3116 [RFC 1766] H. Alvestrand, _Tags for the Identification of Languages_, 3117 UNINETT, RFC 1766, March 1995. 3119 [UNICODE] The Unicode Consortium, "The Unicode Standard --Worldwide 3120 Character Encoding -- Version 1.0", Addison-Wesley, Volume 1, 1991, 3121 Volume 2, 1992. UTF-8 is described in Unicode Technical Report #4. 3123 [US-ASCII] Coded Character Set--7-bit American Standard Code for 3124 Information Interchange, ANSI X3.4-1986. 3126 [VCAL] MIME calendaring entity - Calendaring and Scheduling Exchange 3127 Format, Versit Consortium, September 18, 1996. 3129 [XAPIA] XAPIA CSA, Calendaring and Scheduling Application 3130 Programming Interface (CSA) Version 1.0, X.400 API Association, 3131 November 15, 1994. 3133 8. Acknowledgments 3135 A hearty thanks to the IETF Calendaring and Scheduling Working Group 3136 and also the following individuals who have participated in the 3137 drafting, review and discussion of this memo: 3139 Roland Alden, Harald T. Alvestrand, Denis Bigorgne, John Binici, Bill 3140 Bliss, Andre Courtemanche, Dave Crocker, Alec Dun, Ross Finlayson, 3141 Randell Flink, Ned Freed, Patrik Falstrom, Anik Ganguly, Chuck 3142 Grandgent, Mark Handley, Steve Hanna, Paul B. Hill, Mark Horton, 3143 Bruce Kahn, C. Harald Koch, Theodore Lorek, Keith Moore, Cecil 3144 Rhodes, Chris Newman, Ralph Patterson, Pete Resnick, Keith Rhodes, 3145 Robert Ripberger, Andras Salamar, Vinod Seraphin, Ken Shan, Andrew 3146 Shuman, William P. Spencer, Mark Towfiq, Robert Visnov, James L. 3147 Weiner, Mike Weston, William Wyatt. 3149 9. Author's Address 3151 The following address information is provided in a MIME-VCARD, 3152 Electronic Business Card, format. 3154 BEGIN:VCARD 3155 FN:Frank Dawson 3156 ORG:IBM Corporation 3157 ADR;WORK;POSTAL;PARCEL:;APNA/CC-303/Bldg. 002;3039 Cornwallis Rd; 3158 Research Triangle Park;NC;27709;USA 3159 TEL;WORK;MSG:+1-919-254-5861 3160 TEL;WORK;FAX:+1-919-543-6822 3161 EMAIL;INTERNET,PREF:fdawson@raleigh.ibm.com 3162 EMAIL;INTERNET:fdawson@earthlink.net 3164 Dawson 60 Expires June 1997 3165 URL:http://home.earthlink.net/~fdawson 3166 END:VCARD 3168 10. Examples 3170 The following examples are provided as an informational source of 3171 illustrative MIME entities containing data consistent with this MIME 3172 content type. 3174 The following is an example of a MIME message with a single entity 3175 consisting of a text/calendar content type. 3177 TO:jsmith@host1.com 3178 FROM:jdoe@host1.com 3179 MIME-VERSION:1.0 3180 MESSAGE-ID:<19960704 08:30:00 EDT xyz@host1.com> 3181 CONTENT-TYPE:text/calendar;PROFILE=request/event 3183 BEGIN:VCALENDAR 3184 PROFILE:event/request 3185 VERSION:1.0 3186 BEGIN:VEVENT 3187 DTSTART:19960918T143000Z 3188 DTEND:19960920T220000Z 3189 CATEGORIES:CONFERENCE;PROJECT 3190 SUMMARY:Networld+Interop Conference 3191 DESCRIPTION;ENCODING=QUOTED-PRINTABLE:Networld+Interop Conference= 3192 and Exhibit=0D=0A= 3193 Atlanta World Congress Center=0D=0A= 3194 Atlanta, Georgia 3195 END:VEVENT 3196 END:VCALENDAR 3198 The following example message segment issues an event/request that 3199 does not require any reply. The message is sent as a singular 3200 _text/calendar_ content type, body part. 3202 From: jsmith@host1.com 3203 To: ietf-calendar@imc.org 3204 Subject: First IETF-Calendar Working Group Meeting 3205 MIME-Version: 1.0 3206 Message-ID: 3207 Content-Type: text/calendar;Profile=event/request 3209 BEGIN:VCALENDAR 3210 PROFILE:event/request 3211 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 3212 PRODID:-//RDU Software//NONSGML HandCal//EN 3213 TZ:-05:00 3214 VERSION:1.0 3215 BEGIN:VEVENT 3216 ATTENDEE;EXPECT=REQUEST:ietf-calendar@imc.org 3217 DESCRIPTION:First IETF-Calendaring and Scheduling Working Group 3218 Meeting 3220 Dawson 61 Expires June 1997 3221 CATEGORIES:MEETING 3222 CLASS:PUBLIC 3223 DCREATED:19961022T083000 3224 SUMMARY:IETF Calendaring Working Group Meeting 3225 DTSTART:19961210T210000Z 3226 DTEND:19961210T220000Z 3227 LOCATION:San Jose, CA - Fairmont Hotel 3228 UID:guid-1.host1.com 3229 END:VEVENT 3230 END:VCALENDAR 3232 11. Extended Recurrence Grammar 3234 The material in this section is provided as an informational 3235 reference. It is copied, with permission of the XAPIA, from the 3236 [XAPIA]. This section defines an extended recurrence rule grammar 3237 that may be useful to implementations wishing to extend the 3238 capability of the basic recurrence rule grammar defined by this 3239 specification. The material is equally applicable to extended support 3240 of the exception rules for repeating events. 3242 11.1 Rule Introduction 3244 A recurrence rule is made up of one or more recurrence frequencies. 3245 The frequencies express the granularity of the repeating event. The 3246 smallest granularity is based on minutes, the largest is based on 3247 years. Each frequency is immediately followed by an interval. The 3248 interval helps to define how often the frequency repeats (daily, 3249 every third day, etc.): 3251 D2 3253 Where, where D is the Frequency and 2 is the Interval. 3255 M5 Repeat every five minutes 3257 D1 Repeat daily 3259 D2 Repeat every other day 3261 D3 Repeat every third day 3263 W1 Repeat weekly 3265 W2 Repeat every other week 3267 W3 Repeat every third week 3269 The meaning of the interval depends on the frequency. As an example, 3270 the 5 in M5 is in minutes while the 3 in D3 is in days. 3272 A rule can end with the duration symbol, #, followed by a number. 3273 This defines the number of times the repetition occurs (including the 3274 first time). 3276 Dawson 62 Expires June 1997 3277 D2 #5 3279 Where, #5 is the Duration. In this example, the event occurs every 3280 other day and the duration indicates it occur 5 times. 3282 There may be other information between the frequency and the duration 3283 that supplements the meaning of the rule: 3285 D2 1200 1600 #5 3287 In this example, the event occurs every other day at 1200 and 1600 3288 for a total of 10 occurrences. The duration controls the number of 3289 times the rule occurs. In this case the rule defines two occurrences 3290 (1200 and 1600) so a total of 10 (2 x 5) occurrences are generated. 3292 A rule can be made up of several recurrence rules: 3294 MP6 1+ MO #5 D2 1200 1600 #5 M5 #3 3296 This recurrence rule is made up of three recurrence rules. Every time 3297 the first rule executes (every 6 months) it executes the next rule to 3298 the right. If there is not a rule to the right an event is generated. 3299 In this case there is a daily frequency rule to the right of the 3300 monthly frequency rule. It executes twice a day; starting on the 3301 first Monday of the month. The daily frequency rule executes a total 3302 of ten times. Since there is a rule following the daily rule it 3303 executes it each time the daily frequency rule executes. The minute 3304 frequency rule is executed three times, every time the daily 3305 frequency rule executes, for a total of six times a day. The above 3306 rules generate a total of 150 (5 * (2 * 5) * 3) occurrences. An 3307 occurrence specifier may be used in some rules. The occurrence 3308 specifier controls which occurrence of a weekday in a month an event 3309 occurs on: 3311 1+, 2+, ... 5+ for the first occurrence, second, ...fifth 3312 occurrence of the month. 3314 1-, 2-...5- for the last occurrence, second to last occurrence, etc. 3316 MP2 1+ 2- FR #3 3318 Where, 1+ and 2- are Occurrence Specifiers. 3320 This rule defines an event which happens every other month on the 3321 first Friday and second to the last Friday of the month. It generates 3322 a total of six occurrences. The end marker symbol $ can be used to 3323 terminate a rule early: 3325 W1 0100$ 0200 0300 #4 3327 The above rule generates occurrences weekly for 4 weeks at 0100, 0200 3328 and 0300. On the last (fourth week) an event is generated at 0100 3329 only. 3331 Dawson 63 Expires June 1997 3332 Recurrence rules are written from largest granularity to smallest. 3334 11.2 Grammar 3336 The following grammar defines the extended recurrence rule syntax. 3338 {} 0 or more 3340 [] 0 or 1 3342 start ::= [] | 3344 [] | 3346 [] | 3348 [] | 3350 [] | 3352 [] | 3354 [] 3356 digit ::= <0|1|2|3|4|5|6|7|8|9> 3358 digits ::= {} 3360 endmarker ::= $ 3362 enddate ::= ISO 8601 (clause 5.4.1) string(e.g. 3363 19940712T101530Z) in UTC 3365 interval ::= 3367 duration ::= # 3369 lastday ::= LD 3371 plus ::= + 3373 minus ::= - 3375 daynumber ::= <1-31>[|][] | 3377 daynumberlist ::= daynumber {} 3379 month ::= <1-12>[] 3381 monthlist ::= {} 3383 day ::= <1-366>[] 3385 daylist ::= {} 3387 Dawson 64 Expires June 1997 3388 occurrence ::= <1-5>[] | <1-5>[] 3390 occurrencelist ::= {} 3392 weekday ::= [] 3394 weekdaylist ::= {} 3396 time ::= [] 3398 timelist ::=