idnits 2.17.1 draft-ietf-calsch-csp-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-19) 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 62 longer pages, the longest (page 1) being 62 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.) ** The abstract seems to contain references ([MIME-CAL]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 386 has weird spacing: '...atus to mess...' == Line 443 has weird spacing: '...atus to mess...' -- 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 9805 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'MIME-CAL' on line 3017 looks like a reference -- Missing reference section? 'RFC1521' on line 3012 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 4 warnings (==), 4 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 Profile 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 18 by other documents at any time. It is not appropriate to use 19 Internet-Drafts as reference material or to cite them other than as a 20 "working 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 The use of mail enabled applications such as calendaring and 33 scheduling has grown considerably in the last decade. Enterprise and 34 inter-enterprise business has become dependent on rapid scheduling of 35 events and actions using this information technology. The store-and- 36 forward characteristic of electronic messaging technologies has been 37 shown to be complementary to the asynchronous nature of group 38 communications. However, the longer term growth of mail enabled 39 applications, such as calendaring and scheduling, is currently 40 limited by the lack of Internet standards for the message content 41 types that these groupware applications are based on. This 42 specification is intended to progress the level of interoperability 43 possible between dissimilar calendaring and scheduling applications 44 that communicate using an SMTP or MIME transport. 46 This specification defines a usage profile for the MIME Calendaring 47 and Scheduling Content Type [MIME-CAL]. Any MIME based calendaring 48 and scheduling application that supports this MIME Calendaring and 49 Scheduling Content Type profile will be able to interoperate with 50 other MIME based calendaring and scheduling applications using a 51 broad range of scheduling functions. 53 Table of Contents 55 1. Introduction........................................................2 56 1.1 Content Type Profile Summary .....................................3 57 1.2 Message Protocol Summary .........................................4 58 2. Intended Use........................................................5 59 2.1 Request and reply to an event ....................................5 60 2.2 Request and reply to a todo ......................................6 61 2.3 Request and reply to free/busy time ..............................7 62 2.4 Negotiate an event ...............................................8 63 2.5 Delegate an event ...............................................10 64 2.6 Cancel an event .................................................11 65 3. Profile Specification..............................................12 66 3.1 EVENT/REQUEST Profile ...........................................14 67 3.2 EVENT/REPLY Profile .............................................16 68 3.3 EVENT/COUNTER Profile ...........................................18 69 3.4 EVENT/DECLINE-COUNTER Profile ...................................20 70 3.5 EVENT/MODIFY Profile ............................................22 71 3.6 EVENT/REPLACE Profile ...........................................24 72 3.7 EVENT/CANCEL Profile ............................................26 73 3.8 EVENT/DELEGATE Profile ..........................................28 74 3.9 EVENT/RESEND Profile ............................................30 75 3.10 FREE-BUSY/REQUEST Profile ......................................32 76 3.11 FREE-BUSY/REPLY Profile ........................................33 77 3.12 TODO/REQUEST Profile ...........................................35 78 3.13 TODO/REPLY Profile .............................................37 79 3.14 TODO/COUNTER Profile ...........................................39 80 3.15 TODO/DECLINE-COUNTER Profile ...................................41 81 3.16 TODO/MODIFY Profile ............................................43 82 3.17 TODO/REPLACE Profile ...........................................45 83 3.18 TODO/CANCEL Profile ............................................47 84 3.19 TODO/DELEGATE Profile ..........................................49 85 3.20 TODO/RESEND Profile ............................................51 86 4. MIME registrations.................................................53 87 4.1 Security Considerations .........................................53 88 5. Example MIME Message Segments......................................53 89 5.1 Simple event/request message ....................................53 90 5.2 Negotiated Event Request and Reply ..............................54 91 5.3 Event/request based on free-busy time search results ............58 92 6. Acknowledgments....................................................62 93 7. Bibliography.......................................................62 94 8. Author's Address...................................................62 96 1. Introduction 98 This specification defines a usage profile for the MIME Calendaring 99 and Scheduling Content Type [MIME-CAL]. [MIME-CAL] provides for the 100 capture and exchange of information normally stored within a 101 calendaring and scheduling application; such as a Personal 102 Information Manager or a Group Scheduling product. The usage profile 103 defines a set of MIME messages that form the basis for a message 104 based protocol that supports a wide range of group scheduling 105 capabilities. These capabilities include the ability to negotiate, 106 schedule, modify, delegate and cancel calendar events or todos; as 107 well as, request and reply with free/busy time data. 109 1.1 Content Type Profile Summary 111 The [MIME-CAL] usage profile takes the form of a registration request 112 for a series of [MIME-CAL] content type profiles. Specifically, these 113 content type profiles include: 115 Content-Type Profile Description 116 Type/Subtype Name 118 EVENT/REQUEST Make a request for an 119 event 121 EVENT/REPLY Reply to an event 122 request 124 EVENT/COUNTER Make a counter proposal 125 to the event request 127 EVENT/DECLINE- Decline the counter 128 COUNTER proposal to the event 129 request 131 EVENT/MODIFY Modify a subset of the 132 details of an existing 133 event request 135 EVENT/REPLACE Replace the current 136 event request with a 137 complete set of 138 information 140 EVENT/CANCEL Cancel an existing 141 event request 143 EVENT/DELEGATE Delegate an existing 144 event request 146 EVENT/RESEND Request a duplicate of 147 the current event 148 request information 149 TODO/REQUEST Assign a todo 151 TODO/REPLY Reply to a todo 152 assignment 154 TODO/COUNTER Make a counter proposal 155 for the todo request 157 TODO/DECLINE-COUNTER Decline a counter 158 proposal for the todo 159 request 161 TODO/MODIFY Modify a subset of the 162 details of an existing 163 todo assignment 165 TODO/REPLACE Replace the current 166 todo request with a 167 complete set of 168 information 170 TODO/CANCEL Cancel an existing todo 172 TODO/DELEGATE Delegate an existing 173 todo 175 TODO/RESEND Request a duplicate of 176 the current todo 177 request information 179 FREE-BUSY/REQUEST Free/busy time request 181 FREE-BUSY/REPLY Reply to an existing 182 free/busy time request 183 with free/busy time 184 data 186 1.2 Message Protocol Summary 188 This usage profile provides for calendaring and scheduling operations 189 including: requesting, replying to, modifying, canceling and 190 delegating either an event or todo calendar component. In addition, 191 the profiles provide for the request for and reply of free/busy time 192 data. These functions are supported through the use of a simple 193 message based protocol, as defined by this profile. 195 The calendaring and scheduling capabilities are implemented by a 196 request-and-reply form of message exchange. For example, an 197 appointment type of event would be created between two individual by 198 one individual, acting as the event _owner_, sending an 199 EVENT/REQUEST message to the other individual. The recipient of the 200 event request message would confirm or decline the proposed 201 appointment with an EVENT/REPLY message. A todo or action item could 202 similarly be assigned with a TODO/REQUEST and TODO/REPLY message 203 sequence. And, a free/busy time data representation of an interval of 204 an individual's calendar can be retrieved by a FREE-BUSY/REQUEST and 205 FREE-BUSY/REPLY message sequence. More sophisticated scheduling 206 operations such as negotiating an appointment request is also 207 supported with request-and-reply using the EVENT/COUNTER and 208 EVENT/REPLACE or EVENT/DECLINE-COUNTER message sequences between a 209 recipient of an EVENT/REQUEST and the _owner_ and/or _organizer_ of 210 the event. Similarly, a todo can be negotiated between two 211 individuals using the analogous todo component message types. 213 The recipient of an event or a todo request can also request an 214 updated or duplicate copy of the calendar component description with 215 the EVENT/RESEND or TODO/RESENT message types. These messages are 216 sent from the recipient of a existing event or todo request to the 217 _owner_ and/or _organizer_ of the corresponding event or todo. The 218 _owner_ and/or _organizer_ of the calendar component would reply with 219 the EVENT/REPLACE or the TODO/REPLACE message type. 221 A number of the calendaring and scheduling capabilities defined by 222 this usage profile are based a single message exchange, rather than a 223 request-and-reply message sequence. For example, an _owner_ or 224 _organizer_ of an event or todo can modify a subset of the details of 225 the calendar component with the EVENT/MODIFY or TODO/MODIFY message 226 types. The complete set of calendar component details can be replaced 227 with the EVENT/REPLACE or TODO/REPLACE message types. An event or an 228 assigned todo can be canceled by the _owner_ and/or _organizer_ of 229 the calendar component with the EVENT/CANCEL or the TODO/CANCEL 230 message types. 232 2. Intended Use 234 This usage profile defines a sequence of MIME message types that 235 provide for a broad set of scheduling operations. The following 236 scenarios provide a limited summary of some of the intended use of 237 these messages. Refer to the MIME message segments in section 5 for a 238 more detailed set of examples. 240 2.1 Request and reply to an event 242 Individual _A_ requests a meeting between individuals _A_, _B_ and 243 _C_. Individual _B_ confirms attendance to the meeting. Individual 244 _C_ declines attendance. The following table illustrates the sequence 245 of messages that would be exchanged between these individuals. 247 Action Originator Recipient 249 Initiate a meeting _A_ sends EVENT/REQUEST 250 request message to _B_ and _C_ 252 Accept the meeting _B_ sends EVENT/REPLY 253 request message to _A_ with 254 it's ATTENDEE/STATUS 255 property parameter set 256 to _CONFIRMED_ 258 Decline the meeting _C_ sends EVENT/REPLY 259 request message to _A_ with 260 it's ATTENDEE/STATUS 261 property parameter set 262 to _DECLINED_ 264 Confirm meeting status _A_ sends EVENT/REPLACE 265 with attendees message to _B_ and _C_ 266 with current 267 information for event. 268 SEQUENC property is 269 _1_. 271 2.2 Request and reply to a todo 273 Individual _A_ assigns a todo to individual _B_. Individual _B_ 274 accepts the todo. The following table illustrates the sequence of 275 messages that would be exchanged between these individuals. 277 Action Originator Recipient 279 Assign a todo _A_ sends TODO/REQUEST 280 message to _B_. 282 Accept the todo _B_ sends TODO/REPLY 283 message to _A_ with 284 it's ATTENDEE/STATUS 285 property parameter set 286 to _ACCEPTED_ 288 Confirm todo status _A_ sends TODO/REPLACE 289 with attendee message to _B_ with 290 current information for 291 todo. SEQUENCE property 292 is _1_. 294 A similar set of messages could have been exchanged to assign a todo 295 to a group of individuals. 297 2.3 Request and reply to free/busy time 299 Individual _A_ requests free/busy time of individuals _B_ and _C_. 300 Individual _B_ and _C_ reply to the free/busy time request. The 301 following table illustrates the sequence of messages that would be 302 exchanged between these individuals. 304 Action Originator Recipient 306 Request free time _A_ sends FREE-BUSY/ 307 REQUEST message to _B_ 308 and _C_. The interval 309 for the free/busy time 310 is specified with the 311 DTSTART and DTEND 312 properties. The desired 313 duration of time is 314 specified with the 315 DURATION property.. 317 Reply with free/busy _B_ sends FREE- 318 time data BUSY/REPLY message to 319 _A_ with an event MIME 320 calendar component for 321 each free/busy time 322 interval. UID 323 corresponds to original 324 request. 326 _C_ sends FREE- 327 BUSY/REPLY message to 328 _A_ with an event MIME 329 calendar component for 330 each free/busy time 331 interval. UID 332 corresponds to original 333 request. 335 2.4 Negotiate an event 337 Individual _A_ requests a meeting between individuals _A_, _B_ and 338 _C_. Individual _B_ confirms attendance to the meeting. Individual 339 _C_ counter proposes. Individual _A_ accepts the counter proposal. 340 Individual _C_ confirms attendance to the meeting. Individual _B_ 341 accepts the modified meeting request. Individual _A_ distributes the 342 revised meeting details and attendee status. The following table 343 illustrates the sequence of messages that would be exchanged between 344 these individuals. 346 Action Originator Recipient 347 Initiate a meeting _A_ sends EVENT/REQUEST 348 request message to _B_ and _C_ 350 Accept the meeting _B_ sends EVENT/REPLY 351 request message to _A_ with 352 it's ATTENDEE/STATUS 353 property parameter set 354 to _CONFIRMED_ 356 Counter proposal for _C_ sends EVENT/COUNTER 357 the meeting request message to _A_ 358 signaling a request to 359 revise some detail 360 about the request 362 Accept the counter _A_ sends EVENT/MODIFY 363 proposal message to _B_ and _C_. 364 SEQUENCE parameter is 365 _1_. 367 Confirm revised meeting _C_ sends EVENT/REPLY 368 request message to _A_ with 369 it's ATTENDEE/STATUS 370 property parameter set 371 to _CONFIRMED_. 372 RESPONSE-SEQUENCE and 373 SEQUENCE parameters are 374 both _1_. 376 _B_ sends EVENT/REPLY 377 message to _A_ with 378 it's ATTENDEE/STATUS 379 property parameter set 380 to _CONFIRMED_. 381 RESPONSE-SEQUENCE and 382 SEQUENCE parameters are 383 both _1_. 385 Redistribute meeting _A_ sends EVENT/REPLACE 386 details and status to message to _B_ and _C_ 387 attendees with current 388 information for event. 389 SEQUENCE property is 390 _2_. 392 Individual _A_ could have declined the counter proposal for the 393 meeting request with the EVENT/DECLINE-COUNTER message. Individual 394 _B_ could have declined the original meeting request with the 395 EVENT/REPLY message or delegated the original meeting request with a 396 combination of the EVENT/REPLY to the originator and the 397 EVENT/DELEGATE to the delegated individual (e.g., Individual _D_). 399 An analogous exchange of todo component messages could have been used 400 to negotiate a todo. 402 2.5 Delegate an event 404 Individual _A_ requests a meeting between individuals _A_ and _B_. 405 Individual _B_ delegates attendance to the meeting to individual _C_. 406 Individual _C_ confirms attendance to the meeting. Individual _A_ 407 distributes the revised meeting details and attendee status. The 408 following table illustrates the sequence of messages that would be 409 exchanged between these individuals. 411 Action Originator Recipient 413 Initiate a meeting _A_ sends EVENT/REQUEST 414 request message to _B_ and _C_ 416 Delegate the meeting _B_ sends EVENT/REPLY 417 request message to _A_ with 418 it's ATTENDEE/STATUS 419 property parameter set 420 to _DELEGATED_ and an 421 ATTENDEE property has 422 been added for _C_. 424 _B_ sends 425 EVENT/DELEGATE message 426 to _C_ with the 427 original meeting 428 request information. 429 The ATTENDEE/STATUS 430 property parameter for 431 _B_ has been set to 432 _DELEGATED_. An 433 ATTENDEE property has 434 been added for _C_. 436 Confirm meeting _C_ sends EVENT/REPLY 437 attendance message to _A_ with 438 it's ATTENDEE/STATUS 439 property parameter set 440 to _CONFIRMED_ 442 Redistribute meeting _A_ sends EVENT/REPLACE 443 details and status to message to _B_ and _C_ 444 attendees with current 445 information for event. 446 SEQUENCE property is 447 _1_ 449 Individual _C_ could have declined the delegated proposal for the 450 meeting request with the EVENT/REPLY message being sent to both _A_ 451 and _B_. 453 An analogous exchange of todo component messages could have been used 454 to delegate a todo. 456 2.6 Cancel an event 458 Individual _A_ requests a meeting between individuals _A_ and _B_. 459 Individual _B_ declines attendance to the meeting. Individual _A_ 460 decides to cancel the meeting. The following table illustrates the 461 sequence of messages that would be exchanged between these 462 individuals. 464 Action Originator Recipient 466 Initiate a meeting _A_ sends EVENT/REQUEST 467 request message to _B_ and _C_ 469 Decline the meeting _B_ sends EVENT/REPLY 470 request message to _A_ with 471 it's ATTENDEE/STATUS 472 property parameter set 473 to _DECLINED_ 475 Cancel the meeting _A_ sends EVENT/CANCEL 476 message to _B_ to 477 cancel the meeting. 478 SEQUENCE parameter is 479 _1_. 481 3. Profile Specification 483 The following sections define each of the profiles included in this 484 specification. If a MIME Calendaring and Scheduling Content Type 485 property is not specified in the profile definition, then it is not 486 allowed in a MIME entity conforming to the profile. 488 The following usage profiles are defined by this document. Each 489 profile type/subtype provides support for a particular scheduling 490 operation. Taken as a whole, these profiles provide support for a 491 robust level of calendaring and scheduling functionality. 493 Content-Type Profile Description 494 Type/Subtype Name 496 EVENT/REQUEST Make a request for an 497 event 499 EVENT/REPLY Reply to an event 500 request 502 EVENT/COUNTER Make a counter proposal 503 to the event request 505 EVENT/DECLINE- Decline the counter 506 COUNTER proposal to the event 507 request 509 EVENT/MODIFY Modify a subset of the 510 details of an existing 511 event request 513 EVENT/REPLACE Replace the current 514 event request with a 515 complete set of 516 information 518 EVENT/CANCEL Cancel an existing 519 event request 521 EVENT/DELEGATE Delegate an existing 522 event request 524 EVENT/RESEND Request a duplicate of 525 the current event 526 request information 528 TODO/REQUEST Assign a todo 530 TODO/REPLY Reply to a todo 531 assignment 533 TODO/COUNTER Make a counter proposal 534 for the todo request 536 TODO/DECLINE-COUNTER Decline a counter 537 proposal for the todo 538 request 540 TODO/MODIFY Modify a subset of the 541 details of an existing 542 todo assignment 544 TODO/REPLACE Replace the current 545 todo request with a 546 complete set of 547 information 549 TODO/CANCEL Cancel an existing todo 551 TODO/DELEGATE Delegate an existing 552 todo 554 TODO/RESEND Request a duplicate of 555 the current todo 556 request information 558 FREE-BUSY/REQUEST Free/busy time request 560 FREE-BUSY/REPLY Reply to an existing 561 free/busy time request 562 with free/busy time 563 data 565 3.1 EVENT/REQUEST Profile 566 To: ietf-calendar@imc.org 567 Subject: Registration of text/calendar MIME profile EVENT/REQUEST 568 Profile name: Event request 569 Profile purpose: Define a MIME Calendaring and Scheduling usage 570 profile that allows for the message based request for 571 scheduling a calendar event such as a meeting or an 572 appointment. The message is sent from an originator (i.e., 573 OWNER or ORGANIZER) of an event request to one or more 574 intended recipients. By default, the originator is the OWNER 575 of the event. The OWNER is a ROLE parameter value for the 576 ATTENDEE property. 577 Profile type/subtype: EVENT/REQUEST 578 Required header fields: 580 Header Field Name Value, Parameter Usage Constraints 582 CONTENT-TYPE Value must be _text/calendar_. Profile 583 parameter must be specified with the value 584 _event/request_. 586 CONTENT-ID Required on secondary body part/MIME 587 entities. Value must be globally unique 588 value. Recipient must maintain this value in 589 order to assure association for REPLY, 590 MODIFY, CANCEL, and DELEGATE operations. 592 MESSAGE-ID Required on the primary body part/MIME 593 entity. Value must be a globally unique 594 value. Recipient must maintain this value in 595 order to assure association for REPLY, 596 MODIFY, CANCEL, and DELEGATE operations. 598 Optional header fields: 599 CONTENT-LANGUAGE 600 TRANSFER-ENCODING 601 Any non-standard header field 602 Calendar component: EVENT 603 Required calendar properties: 605 Property Name Value / Usage Constraints 607 PROFILE Value must be _event/request_. 609 DAYLIGHT Property is required if the date/time values 610 in the component properties are specified in 611 local time. Value must reflect DST 612 observance at originator's location. 614 PRODID Value must be a unique identification of the 615 application that generated the calendar 616 object. 618 TZ Property is required if the date/time values 619 in the component properties are specified in 620 local time. Value must reflect the time zone 621 of the originator's location. Optional if 622 the date/time values are specified in UTC. 624 VERSION Value must be _1.0_. 626 Optional calendar properties: 627 DAYLIGHT (If date/time values in component properties are UTC). 628 GEO 629 TZ (If date/time values in component properties are UTC). 630 Any non-standard calendar property. 631 Required component properties: 633 Property Name Value / Usage Constraints 635 ATTENDEE A property instance must be specified for 636 each invited attendee. 638 DESCRIPTION None. 640 DTEND Must be equal to or later than DTSTART. 642 DTSTART Must be before DTEND. 644 SEQUENCE Required if not zero. 646 UID Value must be a globally unique value. 647 Property must be used by the recipient in 648 all responses to this request. 650 Optional component properties: 651 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE, 652 EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM, 653 RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP, 654 URL 655 Any non-standard properties 656 Profile special notes: A MIME entity with this profile type is used 657 to request a new event with a group of people. Either the 658 EVENT/MODIFY, EVENT/REPLACE, or a sequence of the EVENT/CANCEL 659 followed by the EVENT/REQUEST profile types should be used by the 660 originator to change this event. 661 Intended usage: COMMON 663 3.2 EVENT/REPLY Profile 664 To: ietf-calendar@imc.org 665 Subject: Registration of text/calendar MIME profile EVENT/REPLY 666 Profile name: Event reply 667 Profile purpose: Define a MIME Calendaring and Scheduling usage 668 profile that allows for the message based reply to an event 669 request such as a meeting or appointment; in order to update 670 the status of an attendee. The message is sent from a 671 recipient of an event request back to the event OWNER and/or 672 ORGANIZER. 673 Profile type/subtype: EVENT/REPLY 674 Required header fields: 676 Header Field Name Value / Usage Constraints 678 CONTENT-TYPE Value must be _text/calendar_. Profile 679 parameter must be specified with the value 680 _event/reply_. 682 CONTENT-ID Required on secondary body part/MIME 683 entities. Value must be globally unique 684 value. Recipient must maintain this value in 685 order to assure association for REPLY, 686 MODIFY, CANCEL, and DELEGATE operations. 688 MESSAGE-ID Required on the primary body part/MIME 689 entity. Value must be a globally unique 690 value. Recipient must maintain this value in 691 order to assure association for REPLY, 692 MODIFY, CANCEL, and DELEGATE operations. 694 Optional header fields: 695 CONTENT-LANGUAGE 696 TRANSFER-ENCODING 697 Any non-standard header field 698 Calendar component: EVENT 699 Required calendar properties: 701 Property Name Value / Usage Constraints 703 PROFILE Value must be _event/reply_. 705 DAYLIGHT Property is required if the date/time values 706 in the component properties are specified in 707 local time. Value must reflect DST 708 observance at originator's location. 710 PRODID Value must be a unique identification of the 711 application that generated the calendar 712 object. 714 TZ Property is required if the date/time values 715 in the component properties are specified in 716 local time. Value must reflect the time zone 717 of the originator's location. Optional if 718 the date/time values are specified in UTC. 720 VERSION Value must be _1.0_. 722 Optional calendar properties: 723 DAYLIGHT (If date/time values in component properties are UTC). 724 GEO 725 TZ (If date/time values in component properties are UTC). 726 Any non-standard calendar property. 727 Required component properties: 729 Property Name Value / Usage Constraints 731 ATTENDEE Required if STATUS for recipient is not 732 specified. An instance corresponding to the 733 attendee replying to the original request. 734 If the attendee is delegating the request, 735 then an additional ATTENDEE property must 736 also be included for the individual being 737 delegated to. 739 DESCRIPTION Value may be used as a secondary matching 740 field. 742 DTEND Value may be used as a secondary matching 743 field. 745 DTSTART Value may be used as a secondary matching 746 field 748 RESPONSE-SEQUENCE Required if not zero. Value used to properly 749 sequence receipt of various replies. 751 SEQUENCE Required if not zero. Value used to properly 752 sequence replies to various versions of the 753 event request. 755 STATUS Required if ATTENDEE not specified. 757 UID Value used as a primary matching field. 758 Value is equal to the globally unique value 759 specified in the original request. 761 Optional component properties: 762 LAST-MODIFIED, SUMMARY, URL 763 Any non-standard properties 764 Profile special notes: A MIME entity with this profile type is used 765 to reply to an event request. Note: This profile is not used 766 to make a counter proposal to various event request details. 767 This would be accomplished by sending an EVENT/COUNTER 768 message to the OWNER and/or ORGANIZER of the original event 769 request. This profile is ONLY USED to reply to an event 770 request such as a meeting or appointment; in order to update 771 the status of an attendee. An EVENT/REPLY to a recurring 772 event, may contain the EXRULE or EXDATE property in order to 773 indicate that the ATTENDEE is only replying to a subset of 774 the occurrences in the original EVENT/REQUEST. 775 Intended usage: COMMON 777 3.3 EVENT/COUNTER Profile 778 To: ietf-calendar@imc.org 779 Subject: Registration of text/calendar MIME profile EVENT/COUNTER 780 Profile name: Counter an existing event request 781 Profile purpose: Define a MIME Calendaring and Scheduling usage 782 profile that allows for the message based counter to an event 783 request. The message is sent from an a recipient of an 784 existing event request to the OWNER and/or ORGANIZER of the 785 original event request. The OWNER and ORGANIZER are ROLE 786 parameter values for the ATTENDEE property. 787 Profile type/subtype: EVENT/COUNTER 788 Required header fields: 790 Header Field Name Value / Usage Constraints 792 CONTENT-TYPE Value must be _text/calendar_. Profile 793 parameter must be specified with the value 794 _event/counter_. 796 CONTENT-ID Required on secondary body part/MIME 797 entities. Value must be globally unique 798 value. Recipient must maintain this value in 799 order to assure association for REPLY, 800 MODIFY, CANCEL, and DELEGATE operations. 802 MESSAGE-ID Required on the primary body part/MIME 803 entity. Value must be a globally unique 804 value. Recipient must maintain this value in 805 order to assure association for REPLY, 806 MODIFY, CANCEL, and DELEGATE operations. 808 Optional header fields: 809 CONTENT-LANGUAGE 810 TRANSFER-ENCODING 811 Any non-standard header field 812 Calendar component: EVENT 813 Required calendar properties: 815 Property Name Value / Usage Constraints 817 PROFILE Value must be _event/counter_. 819 DAYLIGHT Property is required if the date/time values 820 in the component properties are specified in 821 local time. Value must reflect DST 822 observance at originator's location. 824 PRODID Value must be a unique identification of the 825 application that generated the calendar 826 object. 828 TZ Property is required if the date/time values 829 in the component properties are specified in 830 local time. Value must reflect the time zone 831 of the originator's location. Optional if 832 the date/time values are specified in UTC. 834 VERSION Value must be _1.0_. 836 Optional calendar properties: 837 DAYLIGHT (If date/time values in component properties are UTC). 838 GEO 839 TZ (If date/time values in component properties are UTC). 840 Any non-standard calendar property. 841 Required component properties: 843 Property Name Value / Usage Constraints 845 ATTENDEE A property instance must be specified for 846 each invited attendee. 848 DESCRIPTION None. 850 DTEND Must be equal to or later than DTSTART. 852 DTSTART Must be before DTEND. 854 RESPONSE-SEQUENCE Required if not zero. 856 SEQUENCE Required if not zero. 858 UID Value must be a globally unique value. 859 Property must be used by the recipient in 860 all responses to this request. 862 Optional component properties: 863 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE, 864 EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM, 865 RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP, 866 URL 867 Any non-standard properties 868 Profile special notes: A MIME entity with this profile type is used 869 to counter a request for a new event. The message is sent from a 870 recipient of an existing event request to the originator of the event 871 request. 872 Intended usage: COMMON 874 3.4 EVENT/DECLINE-COUNTER Profile 875 To: ietf-calendar@imc.org 876 Subject: Registration of text/calendar MIME profile EVENT/DECLINE- 877 COUNTER 878 Profile name: Decline event request counter proposal. 879 Profile purpose: Define a MIME Calendaring and Scheduling usage 880 profile that allows for the message based decline of an 881 existing event request counter proposal. The message is sent 882 by the OWNER and/or ORGANIZER of the original, existing event 883 request to the originator of the event request counter 884 proposal. The OWNER and ORGANIZER are ROLE parameter values 885 for the ATTENDEE property. 886 Profile type/subtype: EVENT/DECLINE-COUNTER 887 Required header fields: 889 Header Field Name Value / Usage Constraints 891 CONTENT-TYPE Value must be _text/calendar_. Profile 892 parameter must be specified with the value 893 _event/decline-counter_. 895 CONTENT-ID Required on secondary body part/MIME 896 entities. Value must be globally unique 897 value. Recipient must maintain this value in 898 order to assure association for REPLY, 899 MODIFY, CANCEL, and DELEGATE operations. 901 MESSAGE-ID Required on the primary body part/MIME 902 entity. Value must be a globally unique 903 value. Recipient must maintain this value in 904 order to assure association for REPLY, 905 MODIFY, CANCEL, and DELEGATE operations. 907 Optional header fields: 908 CONTENT-LANGUAGE 909 TRANSFER-ENCODING 910 Any non-standard header field 911 Calendar component: EVENT 912 Required calendar properties: 914 Property Name Value / Usage Constraints 916 PROFILE Value must be _event/decline-counter_. 918 DAYLIGHT Property is required if the date/time values 919 in the component properties are specified in 920 local time. Value must reflect DST 921 observance at originator's location. 923 PRODID Value must be a unique identification of the 924 application that generated the calendar 925 object. 927 TZ Property is required if the date/time values 928 in the component properties are specified in 929 local time. Value must reflect the time zone 930 of the originator's location. Optional if 931 the date/time values are specified in UTC. 933 VERSION Value must be _1.0_. 935 Optional calendar properties: 936 DAYLIGHT (If date/time values in component properties are UTC). 937 GEO 938 TZ (If date/time values in component properties are UTC). 939 Any non-standard calendar property. 940 Required component properties: 942 Property Name Value / Usage Constraints 944 ATTENDEE Value represents the originator of the 945 counter proposal. 947 RESPONSE-SEQUENCE Required if not zero. 949 SEQUENCE Required if not zero. 951 UID Value used as the primary matching field. 952 Value is equal to the globally unique value 953 specified in the original request or any 954 subsequent modification request. 956 Optional component properties: 957 If specified: DESCRIPTION, DTEND, EXDATE, EXRULE, LOCATION, 958 RNUM, RDATE, RRULE, RESOURCES, DTSTART, SUMMARY, indicate that 959 the event counter was declined because based on the value of 960 these properties. 961 Any non-standard properties 962 Profile special notes: A MIME entity with this profile type is used 963 to decline a counter proposal for an existing event request. 965 A MIME entity corresponding to this profile can only be sent 966 by one of the recipients of an existing event request. It is 967 sent to the OWNER and/or ORGANIZER of the original, existing 968 event request. The optional properties in the message are 969 specified to indicate the basis for declining the event 970 counter proposal. The OWNER and ORGANIZER are ROLE parameter 971 values for the ATTENDEE property. 972 Intended usage: COMMON 974 3.5 EVENT/MODIFY Profile 975 To: ietf-calendar@imc.org 976 Subject: Registration of text/calendar MIME profile EVENT/MODIFY 977 Profile name: Event modify 978 Profile purpose: Define a MIME Calendaring and Scheduling usage 979 profile that allows for the message based modification of a 980 subset of the description of an existing calendar event 981 request. The message is sent from the originator of the 982 original event request to one or more of the original 983 recipients. 984 Profile type/subtype: EVENT/MODIFY 985 Required header fields: 987 Header Field Name Value / Usage Constraints 989 CONTENT-TYPE Value must be _text/calendar_. Profile 990 parameter must be specified with the value 991 _event/modify_. 993 CONTENT-ID Required on secondary body part/MIME 994 entities. Value must be globally unique 995 value. Recipient must maintain this value in 996 order to assure association for REPLY, 997 MODIFY, CANCEL, and DELEGATE operations. 999 MESSAGE-ID Required on the primary body part/MIME 1000 entity. Value must be a globally unique 1001 value. Recipient must maintain this value in 1002 order to assure association for REPLY, 1003 MODIFY, CANCEL, and DELEGATE operations. 1005 Optional header fields: 1006 CONTENT-LANGUAGE 1007 TRANSFER-ENCODING 1008 Any non-standard header field 1009 Calendar component: EVENT 1010 Required calendar properties: 1012 Property Name Value / Usage Constraints 1014 PROFILE Value must be _event/modify_. 1016 DAYLIGHT Property is required if the date/time values 1017 in the component properties are specified in 1018 local time. Value must reflect DST 1019 observance at originator's location. 1021 PRODID Value must be a unique identification of the 1022 application that generated the calendar 1023 object. 1025 TZ Property is required if the date/time values 1026 in the component properties are specified in 1027 local time. Value must reflect the time zone 1028 of the originator's location. Optional if 1029 the date/time values are specified in UTC. 1031 VERSION Value must be _1.0_. 1033 Optional calendar properties: 1034 DAYLIGHT (If date/time values in component properties are UTC). 1035 GEO 1036 TZ (If date/time values in component properties are UTC). 1037 Any non-standard calendar property. 1038 Required component properties: 1040 Property Name Value / Usage Constraints 1042 DESCRIPTION Value may be used as a secondary matching 1043 field. 1045 DTEND Value may be used as a secondary matching 1046 field. 1048 DTSTART Value may be used as a secondary matching 1049 field. 1051 SEQUENCE Value must be the ordinal of the revision 1052 (i.e., 1st revision value would be _1_). 1054 UID Value must be a globally unique value. 1055 Property must be maintained by the 1056 recipient. 1058 Any of the Value corresponds to a modified property 1059 optional value. If a property is specified with the 1060 properties. unchanged, original value, it will still be 1061 assumed to be a modified property value. 1063 Optional component properties: 1064 ATTACH, ATTENDEE, AALARM, CATEGORIES, CLASS, CREATED, DALARM, 1065 EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, 1066 PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, 1067 TRANSP, URL 1068 Any non-standard properties 1069 Profile special notes: A MIME entity with this profile type is used 1070 by the originator of an event request to send modifications 1071 to an existing event. The MIME entity with this profile can 1072 only be sent by the OWNER and/or ORGANIZER of the original 1073 event request. The OWNER and ORGANIZER are ROLE parameter 1074 values for the ATTENDEE property. This message is intended to 1075 be used to change a subset of the event details. The 1076 preferred method of effecting a wholesale change for an event 1077 is to send an EVENT/REPLACE message or to send an 1078 EVENT/CANCEL message for the original event request followed 1079 by an EVENT/REQUEST message the details for the new event. 1080 Intended usage: COMMON 1082 3.6 EVENT/REPLACE Profile 1083 To: ietf-calendar@imc.org 1084 Subject: Registration of text/calendar MIME profile EVENT/REPLACE 1085 Profile name: Replace an event request. 1086 Profile purpose: Define a MIME Calendaring and Scheduling usage 1087 profile that allows for the message based update of the 1088 complete description for a calendar event such as a meeting 1089 or an appointment. The message is sent from an originator 1090 (i.e., OWNER or ORGANIZER) of an event request to one or more 1091 intended recipients. By default, the originator is the OWNER 1092 of the event. The OWNER is a ROLE parameter value for the 1093 ATTENDEE property. 1094 Profile type/subtype: EVENT/REPLACE 1095 Required header fields: 1097 Header Field Name Value / Usage Constraints 1099 CONTENT-TYPE Value must be _text/calendar_. Profile 1100 parameter must be specified with the value 1101 _event/replace_. 1103 CONTENT-ID Required on secondary body part/MIME 1104 entities. Value must be globally unique 1105 value. Recipient must maintain this value in 1106 order to assure association for REPLY, 1107 MODIFY, CANCEL, and DELEGATE operations. 1109 MESSAGE-ID Required on the primary body part/MIME 1110 entity. Value must be a globally unique 1111 value. Recipient must maintain this value in 1112 order to assure association for REPLY, 1113 MODIFY, CANCEL, and DELEGATE operations. 1115 Optional header fields: 1116 CONTENT-LANGUAGE 1117 TRANSFER-ENCODING 1118 Any non-standard header field 1119 Calendar component: EVENT 1120 Required calendar properties: 1122 Property Name Value / Usage Constraints 1124 PROFILE Value must be _event/replace_. 1126 DAYLIGHT Property is required if the date/time values 1127 in the component properties are specified in 1128 local time. Value must reflect DST 1129 observance at originator's location. 1131 PRODID Value must be a unique identification of the 1132 application that generated the calendar 1133 object. 1135 TZ Property is required if the date/time values 1136 in the component properties are specified in 1137 local time. Value must reflect the time zone 1138 of the originator's location. Optional if 1139 the date/time values are specified in UTC. 1141 VERSION Value must be _1.0_. 1143 Optional calendar properties: 1144 DAYLIGHT (If date/time values in component properties are UTC). 1145 GEO 1146 TZ (If date/time values in component properties are UTC). 1147 Any non-standard calendar property. 1148 Required component properties: 1150 Property Name Value / Usage Constraints 1152 ATTENDEE A property instance must be specified for 1153 each invited attendee. 1155 DESCRIPTION None. 1157 DTEND Must be equal to or later than DTSTART. 1159 DTSTART Must be before DTEND. 1161 SEQUENCE Required if not zero. 1163 UID Value must be a globally unique value. 1164 Property must be used by the recipient in 1165 all responses to this request. 1167 Optional component properties: 1169 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE, 1170 EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM, 1171 RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP, 1172 URL 1173 Any non-standard properties 1174 Profile special notes: A MIME entity with this profile type is used 1175 to replace the description of an event with the recipients of an 1176 existing event request. 1177 Intended usage: COMMON 1179 3.7 EVENT/CANCEL Profile 1180 To: ietf-calendar@imc.org 1181 Subject: Registration of text/calendar MIME profile EVENT/CANCEL 1182 Profile name: Event cancellation 1183 Profile purpose: Define a MIME Calendaring and Scheduling usage 1184 profile that allows for the message based cancellation of an 1185 existing event request such as a meeting or an appointment. 1186 The message is sent by the OWNER and/or ORGANIZER of the 1187 original, existing event request to the recipients of the 1188 original event request. The OWNER and ORGANIZER are ROLE 1189 parameter values for the ATTENDEE property. 1190 Profile type/subtype: EVENT/CANCEL 1191 Required header fields: 1193 Header Field Name Value / Usage Constraints 1195 CONTENT-TYPE Value must be _text/calendar_. Profile 1196 parameter must be specified with the value 1197 _event/cancel_. 1199 CONTENT-ID Required on secondary body part/MIME 1200 entities. Value must be globally unique 1201 value. Recipient must maintain this value in 1202 order to assure association for REPLY, 1203 MODIFY, CANCEL, and DELEGATE operations. 1205 MESSAGE-ID Required on the primary body part/MIME 1206 entity. Value must be a globally unique 1207 value. Recipient must maintain this value in 1208 order to assure association for REPLY, 1209 MODIFY, CANCEL, and DELEGATE operations. 1211 Optional header fields: 1212 CONTENT-LANGUAGE 1213 TRANSFER-ENCODING 1214 Any non-standard header field 1215 Calendar component: EVENT 1216 Required calendar properties: 1218 Property Name Value / Usage Constraints 1219 PROFILE Value must be _event/cancel_. 1221 DAYLIGHT Property is required if the date/time values 1222 in the component properties are specified in 1223 local time. Value must reflect DST 1224 observance at originator's location. 1226 PRODID Value must be a unique identification of the 1227 application that generated the calendar 1228 object. 1230 TZ Property is required if the date/time values 1231 in the component properties are specified in 1232 local time. Value must reflect the time zone 1233 of the originator's location. Optional if 1234 the date/time values are specified in UTC. 1236 VERSION Value must be _1.0_. 1238 Optional calendar properties: 1239 DAYLIGHT (If date/time values in component properties are UTC). 1240 GEO 1241 TZ (If date/time values in component properties are UTC). 1242 Any non-standard calendar property. 1243 Required component properties: 1245 Property Name Value / Usage Constraints 1247 DESCRIPTION Value used as a tertiary matching field 1249 DTEND Value used as a secondary matching field. 1251 DTSTART Value used as a secondary matching field 1253 SEQUENCE Required if not zero. 1255 UID Value used as the primary matching field. 1256 Value is equal to the globally unique value 1257 specified in the original request or any 1258 subsequent modification request. 1260 Optional component properties: 1261 LAST-MODIFIED, RELATED-TO (can be used to find linked events), 1262 SUMMARY, URL 1263 Any non-standard properties 1264 Profile special notes: A MIME entity with this profile type is used 1265 to cancel an existing event request. A MIME entity 1266 corresponding to this profile can only be sent by the OWNER 1267 and/or ORGANIZER of the original, existing event request. In 1268 the event that the recipient application does not have the 1269 persistent UID property for the calendar component, the 1270 optional properties can be used to select the calendar entry 1271 corresponding to this request. The OWNER and ORGANIZER are 1272 ROLE parameter values for the ATTENDEE property. 1273 Intended usage: COMMON 1275 3.8 EVENT/DELEGATE Profile 1276 To: ietf-calendar@imc.org 1277 Subject: Registration of text/calendar MIME profile EVENT/DELEGATE 1278 Profile name: Event delegation 1279 Profile purpose: Define a MIME Calendaring and Scheduling usage 1280 profile that allows for the message based delegation of an 1281 existing event request such as a meeting or appointment to an 1282 alternate individual. The message is sent by any of the 1283 attendees of an existing event request to another delegated 1284 attendee and possibly the originator, OWNER, or ORGANIZER of 1285 the event request. The OWNER and ORGANIZER are ROLE parameter 1286 values for the ATTENDEE property. 1287 Profile type/subtype: EVENT/DELEGATE 1288 Required header fields: 1290 Header Field Name Value / Usage Constraints 1292 CONTENT-TYPE Value must be _text/calendar_. Profile 1293 parameter must be specified with the value 1294 _event/delegate_. 1296 CONTENT-ID Required on secondary body part/MIME 1297 entities. Value must be globally unique 1298 value. Recipient must maintain this value in 1299 order to assure association for REPLY, 1300 MODIFY, CANCEL, and DELEGATE operations. 1302 MESSAGE-ID Required on the primary body part/MIME 1303 entity. Value must be a globally unique 1304 value. Recipient must maintain this value in 1305 order to assure association for REPLY, 1306 MODIFY, CANCEL, and DELEGATE operations. 1308 Optional header fields: 1309 CONTENT-LANGUAGE 1310 TRANSFER-ENCODING 1311 Any non-standard header field 1312 Calendar component: EVENT 1313 Required calendar properties: 1315 Property Name Value / Usage Constraints 1317 PROFILE Value must be _event/delegate_. 1319 DAYLIGHT Value must reflect DST observance at 1320 originator's location. 1322 PRODID Value must be a unique identification of the 1323 application that generated the calendar 1324 object. 1326 TZ Property is required if the date/time values 1327 in the component properties are specified in 1328 local time. Value must reflect the time zone 1329 of the originator's location. Optional if 1330 the date/time values are specified in UTC. 1332 VERSION Value must be _1.0_. 1334 Optional calendar properties: 1335 GEO 1336 TZ (If date/time values in component properties are UTC). 1337 Any non-standard calendar property. 1338 Required component properties: 1340 Property Name Value / Usage Constraints 1342 ATTENDEE A property instance must be specified for 1343 each delegated attendee. In addition, an 1344 ATTENDEE instance must be specified for the 1345 individual being delegated to. 1347 DESCRIPTION None 1349 DTEND Must be equal to or later than DTSTART 1351 DTSTART Must be before DTEND. 1353 RESPONSE-SEQUENCE Required if not zero. 1355 SEQUENCE Required if not zero 1357 UID Value must be a globally unique value. 1358 Property must be maintained by the 1359 recipient. 1361 Optional component properties: 1362 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE, 1363 EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM, 1364 RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP, 1365 URL 1366 Any non-standard properties 1367 Profile special notes: A MIME entity with this profile type is used 1368 to delegate an existing event request to another person. A MIME 1369 entity corresponding to this profile may be sent by any of the 1370 attendees of an existing event request. The properties from the 1371 original event request must be included in the calendar component to 1372 assure that the delegated attendee has a complete specification of 1373 the delegated event. This may include a description that reflects 1374 numerous revisions of the original request. The message must also 1375 contain an ATTENDEE property corresponding to the individual being 1376 delegated to. 1377 Intended usage: COMMON 1379 3.9 EVENT/RESEND Profile 1380 To: ietf-calendar@imc.org 1381 Subject: Registration of text/calendar MIME profile EVENT/RESEND 1382 Profile name: Request an update or duplicate or an existing event 1383 request. 1384 Profile purpose: Define a MIME Calendaring and Scheduling usage 1385 profile that allows for the message based request for an 1386 update or duplicate of the specification for an existing 1387 event request such as a meeting or an appointment. The 1388 message is sent by the recipient of an existing event request 1389 to the OWNER and/or ORGANIZER of the original, existing event 1390 request. The OWNER and ORGANIZER are ROLE parameter values 1391 for the ATTENDEE property. 1392 Profile type/subtype: EVENT/RESEND 1393 Required header fields: 1395 Header Field Name Value / Usage Constraints 1397 CONTENT-TYPE Value must be _text/calendar_. Profile 1398 parameter must be specified with the value 1399 _event/resend_. 1401 CONTENT-ID Required on secondary body part/MIME 1402 entities. Value must be globally unique 1403 value. Recipient must maintain this value in 1404 order to assure association for REPLY, 1405 MODIFY, CANCEL, and DELEGATE operations. 1407 MESSAGE-ID Required on the primary body part/MIME 1408 entity. Value must be a globally unique 1409 value. Recipient must maintain this value in 1410 order to assure association for REPLY, 1411 MODIFY, CANCEL, and DELEGATE operations. 1413 Optional header fields: 1414 CONTENT-LANGUAGE 1415 TRANSFER-ENCODING 1416 Any non-standard header field 1417 Calendar component: EVENT 1418 Required calendar properties: 1420 Property Name Value / Usage Constraints 1421 PROFILE Value must be _event/resend_. 1423 DAYLIGHT Property is required if the date/time values 1424 in the component properties are specified in 1425 local time. Value must reflect DST 1426 observance at originator's location. 1428 PRODID Value must be a unique identification of the 1429 application that generated the calendar 1430 object. 1432 TZ Property is required if the date/time values 1433 in the component properties are specified in 1434 local time. Value must reflect the time zone 1435 of the originator's location. Optional if 1436 the date/time values are specified in UTC. 1438 VERSION Value must be _1.0_. 1440 Optional calendar properties: 1441 DAYLIGHT (If date/time values in component properties are UTC). 1442 GEO 1443 TZ (If date/time values in component properties are UTC). 1444 Any non-standard calendar property. 1445 Required component properties: 1447 Property Name Value / Usage Constraints 1449 RESPONSE-SEQUENCE Required if not zero. 1451 SEQUENCE Required if not zero. 1453 UID Value used as the primary matching field. 1454 Value is equal to the globally unique value 1455 specified in the original request or any 1456 subsequent modification request. 1458 Optional component properties: 1459 DESCRIPTION, DTEND, DTSTART, LAST-MODIFIED, RELATED-TO, SUMMARY, 1460 URL can be used as secondary matching fields for the event. 1461 Any non-standard properties 1462 Profile special notes: A MIME entity with this profile type is used 1463 to request an update or duplicate of the specification of an 1464 existing event request. A MIME entity corresponding to this 1465 profile can only be sent by the recipient of an existing 1466 event request. It is sent to the OWNER and/or ORGANIZER of 1467 the original, existing event request. In the event that the 1468 recipient application does not have the persistent UID 1469 property for the calendar component, the optional properties 1470 can be used to select the calendar entry corresponding to 1471 this request. The OWNER and ORGANIZER are ROLE parameter 1472 values for the ATTENDEE property. 1473 Intended usage: COMMON 1475 3.10 FREE-BUSY/REQUEST Profile 1476 To: ietf-calendar@imc.org 1477 Subject: Registration of text/calendar MIME profile FREE-BUSY/REQUEST 1478 Profile name: Free/busy request 1479 Profile purpose: Define a MIME Calendaring and Scheduling usage 1480 profile that allows for the message based request of 1481 free/busy time data from a group of people. The message is 1482 sent by the originator of the free/busy time request to 1483 individual recipients of the request. 1484 Profile type/subtype: FREE-BUSY/REQUEST 1485 Required header fields: 1487 Header Field Name Value / Usage Constraints 1489 CONTENT-TYPE Value must be _text/calendar_. Profile 1490 parameter must be specified with the value 1491 _free-busy/request_. 1493 CONTENT-ID Required on secondary body part/MIME 1494 entities. Value must be globally unique 1495 value. Recipient must maintain this value in 1496 order to assure association for REPLY 1497 operations. 1499 MESSAGE-ID Required on the primary body part/MIME 1500 entity. Value must be a globally unique 1501 value. Recipient must maintain this value in 1502 order to assure association for REPLY 1503 operations. 1505 Optional header fields: 1506 CONTENT-LANGUAGE 1507 TRANSFER-ENCODING 1508 Any non-standard header field 1509 Calendar component: EVENT 1510 Required calendar properties: 1512 Property Name Value / Usage Constraints 1514 PROFILE Value must be _free-busy/request_. 1516 DAYLIGHT Property is required if the date/time values 1517 in the component properties are specified in 1518 local time. Value must reflect DST 1519 observance at originator's location. 1521 PRODID Value must be a unique identification of the 1522 application that generated the calendar 1523 object. 1525 TZ Property is required if the date/time values 1526 in the component properties are specified in 1527 local time. Value must reflect the time zone 1528 of the originator's location. Optional if 1529 the date/time values are specified in UTC. 1531 VERSION Value must be _1.0_. 1533 Optional calendar properties: 1534 DAYLIGH (If date/time values in component properties are UTC). 1535 GEO 1536 TZ (If date/time values in component properties are UTC). 1537 Any non-standard calendar property. 1538 Required component properties: 1540 Property Name Value / Usage Constraints 1542 ATTENDEE A property instance must be specified for 1543 each attendee for which free/busy time data 1544 is being requested 1546 DTEND Must be equal to or later than DTSTART. 1547 Represents the end of the free/busy time 1548 search interval 1550 DTSTART Must be before or the same as DTEND. 1551 Represents the start of the free/busy time 1552 search interval 1554 DURATION Represents the length of free time being 1555 requested. 1557 UID Value must be a globally unique value. 1558 Property must be maintained by the 1559 recipient. 1561 Optional component properties: 1562 Any non-standard properties 1563 Profile special notes: A MIME entity with this profile type is used 1564 to request free/busy time data from another person. 1565 Intended usage: COMMON 1567 3.11 FREE-BUSY/REPLY Profile 1568 To: ietf-calendar@imc.org 1569 Subject: Registration of text/calendar MIME profile FREE-BUSY/REPLY 1570 Profile name: Free/busy reply 1571 Profile purpose: Define a MIME Calendaring and Scheduling usage 1572 profile that allows for the message based reply of free/busy 1573 time data. The message is sent by the recipient of the 1574 free/busy time request to the originator of the request. 1575 Profile type/subtype: FREE-BUSY/REPLY 1576 Required header fields: 1578 Header Field Name Value / Usage Constraints 1580 CONTENT-TYPE Value must be _text/calendar_. Profile 1581 parameter must be specified with the value 1582 _free-busy/reply_. 1584 CONTENT-ID Required on secondary body part/MIME 1585 entities. Value must be globally unique 1586 value. Recipient must maintain this value in 1587 order to assure association for REPLY 1588 operations. 1590 MESSAGE-ID Required on the primary body part/MIME 1591 entity. Value must be a globally unique 1592 value. Recipient must maintain this value in 1593 order to assure association for REPLY 1594 operations. 1596 Optional header fields: 1597 CONTENT-LANGUAGE 1598 TRANSFER-ENCODING 1599 Any non-standard header field 1600 Calendar component: EVENT 1601 Required calendar properties: 1603 Property Name Value / Usage Constraints 1605 PROFILE Value must be _free-busy/reply_. 1607 DAYLIGHT Property is required if the date/time values 1608 in the component properties are specified in 1609 local time. Value must reflect DST 1610 observance at originator's location. 1612 PRODID Value must be a unique identification of the 1613 application that generated the calendar 1614 object. 1616 TZ Property is required if the date/time values 1617 in the component properties are specified in 1618 local time. Value must reflect the time zone 1619 of the originator's location. Optional if 1620 the date/time values are specified in UTC. 1622 VERSION Value must be _1.0_. 1624 Optional calendar properties: 1625 DAYLIGHT (If date/time values in component properties are UTC). 1626 GEO 1627 TZ (If date/time values in component properties are UTC). 1628 Any non-standard calendar property. 1629 Required component properties: 1631 Property Name Value / Usage Constraints 1633 ATTENDEE The recipient that is replying to the 1634 free/busy time request. 1636 DTEND Must be equal to or later than DTSTART. 1638 DTSTART This is the start date/time of the free/busy 1639 time interval. The date must be before or 1640 the same as DTEND. 1642 TRANSP This indicates whether the date/time 1643 sequence represents a busy (a value of _0_) 1644 or free (a value of _1_) time interval. 1646 UID Value must be a globally unique value. This 1647 value corresponds to the UID in the original 1648 free/busy time request. 1650 Optional component properties: 1651 STATUS, CATEGORIES 1652 Any non-standard properties 1653 Profile special notes: A MIME entity with this profile type is used 1654 to reply to a free/busy time request. Numerous intervals of free/busy 1655 time data are represented as separate MIME event components. 1656 Intended usage: COMMON 1658 3.12 TODO/REQUEST Profile 1659 To: ietf-calendar@imc.org 1660 Subject: Registration of text/calendar MIME profile TODO/REQUEST 1661 Profile name: Todo request 1662 Profile purpose: Define a MIME Calendaring and Scheduling usage 1663 profile that allows for the message based assignment of a 1664 todo or action item. The message is sent from an originator 1665 (i.e., OWNER or ORGANIZER) of an todo request to one or more 1666 intended recipients. By default, the originator is the OWNER 1667 of the todo. The OWNER is a ROLE parameter value for the 1668 ATTENDEE property. 1669 Profile type/subtype: TODO/REQUEST 1670 Required header fields: 1672 Header Field Name Value / Usage Constraints 1674 CONTENT-TYPE Value must be _text/calendar_. Profile 1675 parameter must be specified with the value 1676 _todo/request_. 1678 CONTENT-ID Required on secondary body part/MIME 1679 entities. Value must be globally unique 1680 value. Recipient must maintain this value in 1681 order to assure association for REPLY, 1682 MODIFY, CANCEL, and DELEGATE operations. 1684 MESSAGE-ID Required on the primary body part/MIME 1685 entity. Value must be a globally unique 1686 value. Recipient must maintain this value in 1687 order to assure association for REPLY, 1688 MODIFY, CANCEL, and DELEGATE operations. 1690 Optional header fields: 1691 CONTENT-LANGUAGE 1692 TRANSFER-ENCODING 1693 Any non-standard header field 1694 Calendar component: TODO 1695 Required calendar properties: 1697 Property Name Value / Usage Constraints 1699 PROFILE Value must be _todo/request_. 1701 DAYLIGHT Property is required if the date/time values 1702 in the component properties are specified in 1703 local time. Value must reflect DST 1704 observance at originator's location. 1706 PRODID Value must be a unique identification of the 1707 application that generated the calendar 1708 object. 1710 TZ Property is required if the date/time values 1711 in the component properties are specified in 1712 local time. Value must reflect the time zone 1713 of the originator's location. Optional if 1714 the date/time values are specified in UTC. 1716 VERSION Value must be _1.0_. 1718 Optional calendar properties: 1719 DAYLIGHT (If date/time values in component properties are UTC). 1720 GEO 1721 TZ (If date/time values in component properties are UTC). 1723 Any non-standard calendar property. 1724 Required component properties: 1726 Property Name Value / Usage Constraints 1728 ATTENDEE A property instance must be specified for 1729 each invited attendee. 1731 DESCRIPTION None. 1733 DUE Must be equal to or later than DTSTART. 1735 SEQUENCE Required if not zero. 1737 UID Value must be a globally unique value. 1738 Property must be used by the recipient in 1739 all responses to this request. 1741 Optional component properties: 1742 DTSTART - Default is the same as DUE value. Indicates the 1743 date/time that the todo is to first appear on the calendar. 1744 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE, 1745 EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM, 1746 RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP, 1747 URL 1748 Any non-standard properties 1749 Profile special notes: A MIME entity with this profile type is used 1750 to assign a new todo to a group of people. Either the TODO/MODIFY, 1751 TODO/REPLACE, or a sequence of the TODO/CANCEL followed by the 1752 TODO/REQUEST profile types should be used by the originator to change 1753 this todo. 1754 Intended usage: COMMON 1756 3.13 TODO/REPLY Profile 1757 To: ietf-calendar@imc.org 1758 Subject: Registration of text/calendar MIME profile TODO/REPLY 1759 Profile name: Todo reply 1760 Profile purpose: Define a MIME Calendaring and Scheduling usage 1761 profile that allows for the message based reply to an todo 1762 assignment; in order to update the status and possibly the 1763 completion date of the todo assignee. The message is sent 1764 from a recipient of an todo request back to the todo OWNER 1765 and/or ORGANIZER. 1766 Profile type/subtype: TODO/REPLY 1767 Required header fields: 1769 Header Field Name Value / Usage Constraints 1771 CONTENT-TYPE Value must be _text/calendar_. Profile 1772 parameter must be specified with the value 1773 _todo/reply_. 1775 CONTENT-ID Required on secondary body part/MIME 1776 entities. Value must be globally unique 1777 value. Recipient must maintain this value in 1778 order to assure association for REPLY, 1779 MODIFY, CANCEL, and DELEGATE operations. 1781 MESSAGE-ID Required on the primary body part/MIME 1782 entity. Value must be a globally unique 1783 value. Recipient must maintain this value in 1784 order to assure association for REPLY, 1785 MODIFY, CANCEL, and DELEGATE operations. 1787 Optional header fields: 1788 CONTENT-LANGUAGE 1789 TRANSFER-ENCODING 1790 Any non-standard header field 1791 Calendar component: TODO 1792 Required calendar properties: 1794 Property Name Value / Usage Constraints 1796 PROFILE Value must be _todo/reply_. 1798 DAYLIGHT Property is required if the date/time values 1799 in the component properties are specified in 1800 local time. Value must reflect DST 1801 observance at originator's location. 1803 PRODID Value must be a unique identification of the 1804 application that generated the calendar 1805 object. 1807 TZ Property is required if the date/time values 1808 in the component properties are specified in 1809 local time. Value must reflect the time zone 1810 of the originator's location. Optional if 1811 the date/time values are specified in UTC. 1813 VERSION Value must be _1.0_. 1815 Optional calendar properties: 1816 DAYLIGHT (If date/time values in component properties are UTC). 1817 GEO 1818 TZ (If date/time values in component properties are UTC). 1820 Any non-standard calendar property. 1821 Required component properties: 1823 Property Name Value / Usage Constraints 1825 ATTENDEE Required if STATUS for recipient is not 1826 specified. An instance corresponding to the 1827 attendee replying to the original request. 1828 If the attendee is delegating the request, 1829 then an additional ATTENDEE property must 1830 also be included for the individual being 1831 delegated to. 1833 COMPLETED Required if todo has been completed. 1835 DESCRIPTION Value may be used as a secondary matching 1836 field. 1838 DUE Value may be used as a secondary matching 1839 field. 1841 RESPONSE-SEQUENCE Required if not zero. Value used to properly 1842 sequence receipt of various replies. 1844 SEQUENCE Required if not zero. Value used to properly 1845 sequence replies to various versions of the 1846 todo request. 1848 STATUS Required if ATTENDEE not specified. 1850 UID Value used as a primary matching field. 1851 Value is equal to the globally unique value 1852 specified in the original request. 1854 Optional component properties: 1855 DTSTART, EXDATE, EXRULE, LAST-MODIFIED, SUMMARY, URL 1856 Any non-standard properties 1857 Profile special notes: A MIME entity with this profile type is used 1858 to reply to an todo assignment. Note: This profile is not 1859 used to make a counter proposal to various todo request 1860 details. This would be accomplished by sending a TODO/COUNTER 1861 message to the OWNER and/or ORGANIZER of the original todo 1862 request. This profile is ONLY USED to reply to an todo 1863 request; in order to update the status of a todo assignee. A 1864 TODO/REPLY to a recurring todo, may contain the EXRULE or 1865 EXDATE property in order to indicate that the ATTENDEE is 1866 only replying to a subset of the occurrences in the original 1867 TODO/REQUEST. 1868 Intended usage: COMMON 1870 3.14 TODO/COUNTER Profile 1871 To: ietf-calendar@imc.org 1872 Subject: Registration of text/calendar MIME profile TODO/COUNTER 1873 Profile name: Counter an existing todo request 1874 Profile purpose: Define a MIME Calendaring and Scheduling usage 1875 profile that allows for the message based counter to an todo 1876 request. The message is sent from an a recipient of an 1877 existing todo request to the OWNER and/or ORGANIZER of the 1878 original todo request. The OWNER and ORGANIZER are ROLE 1879 parameter values for the ATTENDEE property. 1880 Profile type/subtype: TODO/COUNTER 1881 Required header fields: 1883 Header Field Name Value / Usage Constraints 1885 CONTENT-TYPE Value must be _text/calendar_. Profile 1886 parameter must be specified with the value 1887 _todo/counter_. 1889 CONTENT-ID Required on secondary body part/MIME 1890 entities. Value must be globally unique 1891 value. Recipient must maintain this value in 1892 order to assure association for REPLY, 1893 MODIFY, CANCEL, and DELEGATE operations. 1895 MESSAGE-ID Required on the primary body part/MIME 1896 entity. Value must be a globally unique 1897 value. Recipient must maintain this value in 1898 order to assure association for REPLY, 1899 MODIFY, CANCEL, and DELEGATE operations. 1901 Optional header fields: 1902 CONTENT-LANGUAGE 1903 TRANSFER-ENCODING 1904 Any non-standard header field 1905 Calendar component: TODO 1906 Required calendar properties: 1908 Property Name Value / Usage Constraints 1910 PROFILE Value must be _todo/counter_. 1912 DAYLIGHT Property is required if the date/time values 1913 in the component properties are specified in 1914 local time. Value must reflect DST 1915 observance at originator's location. 1917 PRODID Value must be a unique identification of the 1918 application that generated the calendar 1919 object. 1921 TZ Property is required if the date/time values 1922 in the component properties are specified in 1923 local time. Value must reflect the time zone 1924 of the originator's location. Optional if 1925 the date/time values are specified in UTC. 1927 VERSION Value must be _1.0_. 1929 Optional calendar properties: 1930 DAYLIGHT (If date/time values in component properties are UTC). 1931 GEO 1932 TZ (If date/time values in component properties are UTC). 1933 Any non-standard calendar property. 1934 Required component properties: 1936 Property Name Value / Usage Constraints 1938 ATTENDEE A property instance must be specified for 1939 each invited attendee. 1941 DESCRIPTION None. 1943 DUE Must be equal to or later than DTSTART. 1945 RESPONSE-SEQUENCE Required if not zero. 1947 SEQUENCE Required if not zero. 1949 UID Value must be a globally unique value. 1950 Property must be used by the recipient in 1951 all responses to this request. 1953 Optional component properties: 1954 DTSTART, ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, 1955 EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, 1956 PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, 1957 TRANSP, URL 1958 Any non-standard properties 1959 Profile special notes: A MIME entity with this profile type is used 1960 to counter a request for a new todo. The message is sent from a 1961 recipient of an existing todo request to the originator of the todo 1962 request. 1963 Intended usage: COMMON 1965 3.15 TODO/DECLINE-COUNTER Profile 1966 To: ietf-calendar@imc.org 1967 Subject: Registration of text/calendar MIME profile TODO/DECLINE- 1968 COUNTER 1969 Profile name: Decline todo request counter proposal. 1970 Profile purpose: Define a MIME Calendaring and Scheduling usage 1971 profile that allows for the message based decline of an 1972 existing todo request counter proposal. The message is sent 1973 by the OWNER and/or ORGANIZER of the original, existing todo 1974 request to the originator of the todo request counter 1975 proposal. The OWNER and ORGANIZER are ROLE parameter values 1976 for the ATTENDEE property. 1977 Profile type/subtype: TODO/DECLINE-COUNTER 1978 Required header fields: 1980 Header Field Name Value / Usage Constraints 1982 CONTENT-TYPE Value must be _text/calendar_. Profile 1983 parameter must be specified with the value 1984 _todo/decline-counter_. 1986 CONTENT-ID Required on secondary body part/MIME 1987 entities. Value must be globally unique 1988 value. Recipient must maintain this value in 1989 order to assure association for REPLY, 1990 MODIFY, CANCEL, and DELEGATE operations. 1992 MESSAGE-ID Required on the primary body part/MIME 1993 entity. Value must be a globally unique 1994 value. Recipient must maintain this value in 1995 order to assure association for REPLY, 1996 MODIFY, CANCEL, and DELEGATE operations. 1998 Optional header fields: 1999 CONTENT-LANGUAGE 2000 TRANSFER-ENCODING 2001 Any non-standard header field 2002 Calendar component: TODO 2003 Required calendar properties: 2005 Property Name Value / Usage Constraints 2007 PROFILE Value must be _todo/decline-counter_. 2009 DAYLIGHT Property is required if the date/time values 2010 in the component properties are specified in 2011 local time. Value must reflect DST 2012 observance at originator's location. 2014 PRODID Value must be a unique identification of the 2015 application that generated the calendar 2016 object. 2018 TZ Property is required if the date/time values 2019 in the component properties are specified in 2020 local time. Value must reflect the time zone 2021 of the originator's location. Optional if 2022 the date/time values are specified in UTC. 2024 VERSION Value must be _1.0_. 2026 Optional calendar properties: 2027 DAYLIGHT (If date/time values in component properties are UTC). 2028 GEO 2029 TZ (If date/time values in component properties are UTC). 2030 Any non-standard calendar property. 2031 Required component properties: 2033 Property Name Value / Usage Constraints 2035 ATTENDEE Value represents the originator of the 2036 counter proposal. 2038 RESPONSE-SEQUENCE Required if not zero. 2040 SEQUENCE Required if not zero. 2042 UID Value used as the primary matching field. 2043 Value is equal to the globally unique value 2044 specified in the original request or any 2045 subsequent modification request. 2047 Optional component properties: 2048 If specified: DESCRIPTION, DUE, EXDATE, EXRULE, LOCATION, 2049 PRIORITY, RNUM, RDATE, RRULE, RESOURCES, DTSTART, SUMMARY, 2050 indicate that the todo counter was declined because based on the 2051 value of these properties. 2052 Any non-standard properties 2053 Profile special notes: A MIME entity with this profile type is used 2054 to decline a counter proposal for an existing todo request. A 2055 MIME entity corresponding to this profile can only be sent by 2056 one of the recipients of an existing todo request. It is sent 2057 to the OWNER and/or ORGANIZER of the original, existing todo 2058 request. The optional properties in the message are specified 2059 to indicate the basis for declining the todo counter 2060 proposal. The OWNER and ORGANIZER are ROLE parameter values 2061 for the ATTENDEE property. 2062 Intended usage: COMMON 2064 3.16 TODO/MODIFY Profile 2065 To: ietf-calendar@imc.org 2066 Subject: Registration of text/calendar MIME profile TODO/MODIFY 2067 Profile name: Todo modify 2068 Profile purpose: Define a MIME Calendaring and Scheduling usage 2069 profile that allows for the message based modification of a 2070 subset of the description of an existing calendar todo 2071 request. The message is sent from the originator of the 2072 original todo request to one or more of the original 2073 recipients. 2074 Profile type/subtype: TODO/MODIFY 2075 Required header fields: 2077 Header Field Name Value / Usage Constraints 2079 CONTENT-TYPE Value must be _text/calendar_. Profile 2080 parameter must be specified with the value 2081 _todo/modify_. 2083 CONTENT-ID Required on secondary body part/MIME 2084 entities. Value must be globally unique 2085 value. Recipient must maintain this value in 2086 order to assure association for REPLY, 2087 MODIFY, CANCEL, and DELEGATE operations. 2089 MESSAGE-ID Required on the primary body part/MIME 2090 entity. Value must be a globally unique 2091 value. Recipient must maintain this value in 2092 order to assure association for REPLY, 2093 MODIFY, CANCEL, and DELEGATE operations. 2095 Optional header fields: 2096 CONTENT-LANGUAGE 2097 TRANSFER-ENCODING 2098 Any non-standard header field 2099 Calendar component: TODO 2100 Required calendar properties: 2102 Property Name Value / Usage Constraints 2104 PROFILE Value must be _todo/modify_. 2106 DAYLIGHT Property is required if the date/time values 2107 in the component properties are specified in 2108 local time. Value must reflect DST 2109 observance at originator's location. 2111 PRODID Value must be a unique identification of the 2112 application that generated the calendar 2113 object. 2115 TZ Property is required if the date/time values 2116 in the component properties are specified in 2117 local time. Value must reflect the time zone 2118 of the originator's location. Optional if 2119 the date/time values are specified in UTC. 2121 VERSION Value must be _1.0_. 2123 Optional calendar properties: 2124 DAYLIGHT (If date/time values in component properties are UTC). 2125 GEO 2126 TZ (If date/time values in component properties are UTC). 2127 Any non-standard calendar property. 2128 Required component properties: 2130 Property Name Value / Usage Constraints 2132 DESCRIPTION Value may be used as a secondary matching 2133 field. 2135 DUE Value may be used as a secondary matching 2136 field. 2138 SEQUENCE Value must be the ordinal of the revision 2139 (i.e., 1st revision value would be _1_). 2141 UID Value must be a globally unique value. 2142 Property must be maintained by the 2143 recipient. 2145 Any of the Value corresponds to a modified property 2146 optional value. If a property is specified with the 2147 properties. unchanged, original value, it will still be 2148 assumed to be a modified property value. 2150 Optional component properties: 2151 ATTACH, ATTENDEE, AALARM, CATEGORIES, CLASS, CREATED, DALARM, 2152 EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, 2153 PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, DTSTART, STATUS, 2154 SUMMARY, URL 2155 Any non-standard properties 2156 Profile special notes: A MIME entity with this profile type is used 2157 by the originator of an todo request to send modifications to 2158 an existing todo. The MIME entity with this profile can only 2159 be sent by the OWNER and/or ORGANIZER of the original todo 2160 request. The OWNER and ORGANIZER are ROLE parameter values 2161 for the ATTENDEE property. This message is intended to be 2162 used to change a subset of the todo details. The preferred 2163 method of effecting a wholesale change for an todo is to send 2164 an TODO/REPLACE message or to send an TODO/CANCEL message for 2165 the original todo request followed by an TODO/REQUEST message 2166 the details for the new todo. 2167 Intended usage: COMMON 2169 3.17 TODO/REPLACE Profile 2170 To: ietf-calendar@imc.org 2171 Subject: Registration of text/calendar MIME profile TODO/REPLACE 2172 Profile name: Replace an todo request. 2174 Profile purpose: Define a MIME Calendaring and Scheduling usage 2175 profile that allows for the message based update of the 2176 complete description for a calendar todo such as a meeting or 2177 an appointment. The message is sent from an originator (i.e., 2178 OWNER or ORGANIZER) of an todo request to one or more 2179 intended recipients. By default, the originator is the OWNER 2180 of the todo. The OWNER is a ROLE parameter value for the 2181 ATTENDEE property. 2182 Profile type/subtype: TODO/REPLACE 2183 Required header fields: 2185 Header Field Name Value / Usage Constraints 2187 CONTENT-TYPE Value must be _text/calendar_. Profile 2188 parameter must be specified with the value 2189 _todo/replace_. 2191 CONTENT-ID Required on secondary body part/MIME 2192 entities. Value must be globally unique 2193 value. Recipient must maintain this value in 2194 order to assure association for REPLY, 2195 MODIFY, CANCEL, and DELEGATE operations. 2197 MESSAGE-ID Required on the primary body part/MIME 2198 entity. Value must be a globally unique 2199 value. Recipient must maintain this value in 2200 order to assure association for REPLY, 2201 MODIFY, CANCEL, and DELEGATE operations. 2203 Optional header fields: 2204 CONTENT-LANGUAGE 2205 TRANSFER-ENCODING 2206 Any non-standard header field 2207 Calendar component: TODO 2208 Required calendar properties: 2210 Property Name Value / Usage Constraints 2212 PROFILE Value must be _todo/replace_. 2214 DAYLIGHT Property is required if the date/time values 2215 in the component properties are specified in 2216 local time. Value must reflect DST 2217 observance at originator's location. 2219 PRODID Value must be a unique identification of the 2220 application that generated the calendar 2221 object. 2223 TZ Property is required if the date/time values 2224 in the component properties are specified in 2225 local time. Value must reflect the time zone 2226 of the originator's location. Optional if 2227 the date/time values are specified in UTC. 2229 VERSION Value must be _1.0_. 2231 Optional calendar properties: 2232 DAYLIGHT (If date/time values in component properties are UTC). 2233 GEO 2234 TZ (If date/time values in component properties are UTC). 2235 Any non-standard calendar property. 2236 Required component properties: 2238 Property Name Value / Usage Constraints 2240 ATTENDEE A property instance must be specified for 2241 each invited attendee. 2243 DESCRIPTION None. 2245 DUE Must be equal to or later than DTSTART. 2247 SEQUENCE Required if not zero. 2249 UID Value must be a globally unique value. 2250 Property must be used by the recipient in 2251 all responses to this request. 2253 Optional component properties: 2254 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, DTSTART, 2255 EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, 2256 PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, 2257 URL 2258 Any non-standard properties 2259 Profile special notes: A MIME entity with this profile type is used 2260 to replace the description of an todo with the recipients of an 2261 existing todo request. 2262 Intended usage: COMMON 2264 3.18 TODO/CANCEL Profile 2265 To: ietf-calendar@imc.org 2266 Subject: Registration of text/calendar MIME profile TODO/CANCEL 2267 Profile name: Todo cancellation 2268 Profile purpose: Define a MIME Calendaring and Scheduling usage 2269 profile that allows for the message based cancellation of an 2270 existing todo request. The message is sent by the OWNER 2271 and/or ORGANIZER of the original, existing todo request to 2272 the recipients of the original todo request. The OWNER and 2273 ORGANIZER are ROLE parameter values for the ATTENDEE 2274 property. 2275 Profile type/subtype: TODO/CANCEL 2276 Required header fields: 2278 Header Field Name Value / Usage Constraints 2280 CONTENT-TYPE Value must be _text/calendar_. Profile 2281 parameter must be specified with the value 2282 _todo/cancel_. 2284 CONTENT-ID Required on secondary body part/MIME 2285 entities. Value must be globally unique 2286 value. Recipient must maintain this value in 2287 order to assure association for REPLY, 2288 MODIFY, CANCEL, and DELEGATE operations. 2290 MESSAGE-ID Required on the primary body part/MIME 2291 entity. Value must be a globally unique 2292 value. Recipient must maintain this value in 2293 order to assure association for REPLY, 2294 MODIFY, CANCEL, and DELEGATE operations. 2296 Optional header fields: 2297 CONTENT-LANGUAGE 2298 TRANSFER-ENCODING 2299 Any non-standard header field 2300 Calendar component: TODO 2301 Required calendar properties: 2303 Property Name Value / Usage Constraints 2305 PROFILE Value must be _todo/cancel_. 2307 DAYLIGHT Property is required if the date/time values 2308 in the component properties are specified in 2309 local time. Value must reflect DST 2310 observance at originator's location. 2312 PRODID Value must be a unique identification of the 2313 application that generated the calendar 2314 object. 2316 TZ Property is required if the date/time values 2317 in the component properties are specified in 2318 local time. Value must reflect the time zone 2319 of the originator's location. Optional if 2320 the date/time values are specified in UTC. 2322 VERSION Value must be _1.0_. 2324 Optional calendar properties: 2325 DAYLIGHT (If date/time values in component properties are UTC). 2326 GEO 2327 TZ (If date/time values in component properties are UTC). 2328 Any non-standard calendar property. 2329 Required component properties: 2331 Property Name Value / Usage Constraints 2333 DESCRIPTION Value used as a tertiary matching field 2335 DUE Value used as a secondary matching field. 2337 SEQUENCE Required if not zero. 2339 UID Value used as the primary matching field. 2340 Value is equal to the globally unique value 2341 specified in the original request or any 2342 subsequent modification request. 2344 Optional component properties: 2345 DTSTART, LAST-MODIFIED, PRIORITY, RELATED-TO (can be used to 2346 find linked todos), SUMMARY, URL 2347 Any non-standard properties 2348 Profile special notes: A MIME entity with this profile type is used 2349 to cancel an existing todo request. A MIME entity 2350 corresponding to this profile can only be sent by the OWNER 2351 and/or ORGANIZER of the original, existing todo request. In 2352 the event that the recipient application does not have the 2353 persistent UID property for the calendar component, the 2354 optional properties can be used to select the calendar entry 2355 corresponding to this request. The OWNER and ORGANIZER are 2356 ROLE parameter values for the ATTENDEE property. 2357 Intended usage: COMMON 2359 3.19 TODO/DELEGATE Profile 2360 To: ietf-calendar@imc.org 2361 Subject: Registration of text/calendar MIME profile TODO/DELEGATE 2362 Profile name: Todo delegation 2363 Profile purpose: Define a MIME Calendaring and Scheduling usage 2364 profile that allows for the message based delegation of an 2365 existing todo request such as a meeting or appointment to an 2366 alternate individual. The message is sent by any of the 2367 attendees of an existing todo request to another delegated 2368 attendee and possibly the originator, OWNER, or ORGANIZER of 2369 the todo request. The OWNER and ORGANIZER are ROLE parameter 2370 values for the ATTENDEE property. 2371 Profile type/subtype: TODO/DELEGATE 2372 Required header fields: 2374 Header Field Name Value / Usage Constraints 2376 CONTENT-TYPE Value must be _text/calendar_. Profile 2377 parameter must be specified with the value 2378 _todo/delegate_. 2380 CONTENT-ID Required on secondary body part/MIME 2381 entities. Value must be globally unique 2382 value. Recipient must maintain this value in 2383 order to assure association for REPLY, 2384 MODIFY, CANCEL, and DELEGATE operations. 2386 MESSAGE-ID Required on the primary body part/MIME 2387 entity. Value must be a globally unique 2388 value. Recipient must maintain this value in 2389 order to assure association for REPLY, 2390 MODIFY, CANCEL, and DELEGATE operations. 2392 Optional header fields: 2393 CONTENT-LANGUAGE 2394 TRANSFER-ENCODING 2395 Any non-standard header field 2396 Calendar component: TODO 2397 Required calendar properties: 2399 Property Name Value / Usage Constraints 2401 PROFILE Value must be _todo/delegate_. 2403 DAYLIGHT Value must reflect DST observance at 2404 originator's location. 2406 PRODID Value must be a unique identification of the 2407 application that generated the calendar 2408 object. 2410 TZ Property is required if the date/time values 2411 in the component properties are specified in 2412 local time. Value must reflect the time zone 2413 of the originator's location. Optional if 2414 the date/time values are specified in UTC. 2416 VERSION Value must be _1.0_. 2418 Optional calendar properties: 2419 GEO 2420 TZ (If date/time values in component properties are UTC). 2421 Any non-standard calendar property. 2422 Required component properties: 2424 Property Name Value / Usage Constraints 2426 ATTENDEE A property instance must be specified for 2427 each delegated attendee. In addition, an 2428 ATTENDEE instance must be specified for the 2429 individual being delegated to. 2431 DESCRIPTION None 2433 DUE Must be equal to or later than DTSTART 2435 RESPONSE-SEQUENCE Required if not zero. 2437 SEQUENCE Required if not zero 2439 UID Value must be a globally unique value. 2440 Property must be maintained by the 2441 recipient. 2443 Optional component properties: 2444 ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, DTSTART, 2445 EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, 2446 PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, 2447 URL 2448 Any non-standard properties 2449 Profile special notes: A MIME entity with this profile type is used 2450 to delegate an existing todo request to another person. A MIME entity 2451 corresponding to this profile may be sent by any of the attendees of 2452 an existing todo request. The properties from the original todo 2453 request must be included in the calendar component to assure that the 2454 delegated attendee has a complete specification of the delegated 2455 todo. This may include a description that reflects numerous revisions 2456 of the original request. The message must also contain an ATTENDEE 2457 property corresponding to the individual being delegated to. 2458 Intended usage: COMMON 2460 3.20 TODO/RESEND Profile 2461 To: ietf-calendar@imc.org 2462 Subject: Registration of text/calendar MIME profile TODO/RESEND 2463 Profile name: Request an update or duplicate or an existing todo 2464 request. 2465 Profile purpose: Define a MIME Calendaring and Scheduling usage 2466 profile that allows for the message based request for an 2467 update or duplicate of the specification for an existing todo 2468 request. The message is sent by the recipient of an existing 2469 todo request to the OWNER and/or ORGANIZER of the original, 2470 existing todo request. The OWNER and ORGANIZER are ROLE 2471 parameter values for the ATTENDEE property. 2472 Profile type/subtype: TODO/RESEND 2473 Required header fields: 2475 Header Field Name Value / Usage Constraints 2477 CONTENT-TYPE Value must be _text/calendar_. Profile 2478 parameter must be specified with the value 2479 _todo/resend_. 2481 CONTENT-ID Required on secondary body part/MIME 2482 entities. Value must be globally unique 2483 value. Recipient must maintain this value in 2484 order to assure association for REPLY, 2485 MODIFY, CANCEL, and DELEGATE operations. 2487 MESSAGE-ID Required on the primary body part/MIME 2488 entity. Value must be a globally unique 2489 value. Recipient must maintain this value in 2490 order to assure association for REPLY, 2491 MODIFY, CANCEL, and DELEGATE operations. 2493 Optional header fields: 2494 CONTENT-LANGUAGE 2495 TRANSFER-ENCODING 2496 Any non-standard header field 2497 Calendar component: TODO 2498 Required calendar properties: 2500 Property Name Value / Usage Constraints 2502 PROFILE Value must be _todo/resend_. 2504 DAYLIGHT Property is required if the date/time values 2505 in the component properties are specified in 2506 local time. Value must reflect DST 2507 observance at originator's location. 2509 PRODID Value must be a unique identification of the 2510 application that generated the calendar 2511 object. 2513 TZ Property is required if the date/time values 2514 in the component properties are specified in 2515 local time. Value must reflect the time zone 2516 of the originator's location. Optional if 2517 the date/time values are specified in UTC. 2519 VERSION Value must be _1.0_. 2521 Optional calendar properties: 2522 DAYLIGHT (If date/time values in component properties are UTC). 2523 GEO 2524 TZ (If date/time values in component properties are UTC). 2526 Any non-standard calendar property. 2527 Required component properties: 2529 Property Name Value / Usage Constraints 2531 RESPONSE-SEQUENCE Required if not zero. 2533 SEQUENCE Required if not zero. 2535 UID Value used as the primary matching field. 2536 Value is equal to the globally unique value 2537 specified in the original request or any 2538 subsequent modification request. 2540 Optional component properties: 2541 DESCRIPTION, DUE, DTSTART, LAST-MODIFIED, PRIORITY, RELATED-TO, 2542 SUMMARY, URL can be used as secondary matching fields for the 2543 todo. 2544 Any non-standard properties 2545 Profile special notes: A MIME entity with this profile type is used 2546 to request an update or duplicate of the specification of an 2547 existing todo request. A MIME entity corresponding to this 2548 profile can only be sent by the recipient of an existing todo 2549 request. It is sent to the OWNER and/or ORGANIZER of the 2550 original, existing todo request. In the todo that the 2551 recipient application does not have the persistent UID 2552 property for the calendar component, the optional properties 2553 can be used to select the calendar entry corresponding to 2554 this request. The OWNER and ORGANIZER are ROLE parameter 2555 values for the ATTENDEE property. 2556 Intended usage: COMMON 2558 4. MIME registrations 2560 This memo is meant to serve as the basis for registration of a MIME 2561 Calendaring and Scheduling Content Type usage profile per [MIME-CAL]. 2563 4.1 Security Considerations 2565 Security issues are not discussed in this memo. 2567 5. Example MIME Message Segments 2569 The following provides some example MIME message segments that 2570 demonstrate the usage of the message types defined by this [MIME-CAL] 2571 usage profile. 2573 5.1 Simple event/request message 2575 The following example message segment issues an event/request that 2576 does not require any reply. The message is sent as a singular 2577 _text/calendar_ content type, body part. 2579 From: jsmith@host1.com 2580 To: ietf-calendar@imc.org 2581 Subject: First IETF-Calendar Working Group Meeting 2582 MIME-Version: 1.0 2583 Message-ID: 2584 Content-Type: text/calendar;Profile=event/request 2586 BEGIN:VCALENDAR 2587 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2588 PRODID:-//RDU Software//NONSGML HandCal//EN 2589 TZ:-05:00 2590 VERSION:1.0 2591 BEGIN:VEVENT 2592 ATTENDEE;EXPECT=REQUEST:ietf-calendar@imc.org 2593 DESCRIPTION:First IETF-Calendaring and Scheduling Working Group 2594 Meeting 2595 CATEGORIES:MEETING 2596 CLASS:PUBLIC 2597 DCREATED:19961022T083000 2598 SUMMARY:IETF Calendaring Working Group Meeting 2599 DTSTART:19961210T210000Z 2600 DTEND:19961210T220000Z 2601 LOCATION:San Jose, CA - Fairmont Hotel 2602 UID:guid-1.host1.com 2603 END:VEVENT 2604 END:VCALENDAR 2606 5.2 Negotiated Event Request and Reply 2608 The following message segments provide an example of a message 2609 exchange that would involve negotiating a event request between two 2610 parties and the subsequent confirmation of the recipient of the 2611 request. In the example, dboss@host1.com is the OWNER of the request 2612 and nmploye@host2.com is the recipient of the request. 2614 The following message is an event request. 2616 From: dboss@host1.com 2617 To: nmploye@host2.com 2618 Subject: Your Annual Review 2619 MIME-Version: 1.0 2620 Message-ID: 2621 Content-Type: text/calendar;Profile=event/request 2623 BEGIN:VCALENDAR 2624 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2625 PRODID:-//RDU Software//NONSGML HandCal//EN 2626 TZ:-05:00 2627 VERSION:1.0 2628 BEGIN:VEVENT 2629 ATTENDEE;EXPECT=REQUIRE;RSVP=YES:nmploye@host2.com 2630 DESCRIPTION:Employee: N. Mploye's 360 Review 2631 CATEGORIES:MEETING 2632 CLASS:CONFIDENTIAL 2633 DCREATED:19960401T083000 2634 SUMMARY:Your Annual Review 2635 DTSTART:19960415T130000 2636 DTEND:19960415T131500 2637 LOCATION:Bldg. 01/Room 07-1A 2638 UID:guid-2.host1.com 2639 END:VEVENT 2640 END:VCALENDAR 2642 The following message is a counter proposal message. 2644 From: nmploye@host2.com 2645 To: dboss@host1.com 2646 Subject: Let's Reschedule The 360 Review 2647 Content-Type: multipart/mixed;boundary=example2 2648 MIME-Version: 1.0 2649 Message-ID: 2651 --example2 2652 Content-Type: text/plain 2653 Content-Id: 2655 D: 2656 I can't make the scheduled 360 review. Remember 2657 it is tax-day! Besides, 15 minutes is not adequate. 2658 - M. 2660 --example2-- 2662 --example2 2663 Content-Type: text/calendar;Profile=event/counter 2664 Content-Id: 2666 BEGIN:VCALENDAR 2667 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2668 PRODID:-//RDU Software//NONSGML HandCal//EN 2669 TZ:-05:00 2670 VERSION:1.0 2671 BEGIN:VEVENT 2672 ATTENDEE;EXPECT=REQUIRE;RSVP=YES:nmploye@host2.com 2673 DESCRIPTION:Employee: N. Mploye's 360 Review 2674 CATEGORIES:MEETING 2675 CLASS:CONFIDENTIAL 2676 SUMMARY:Your Annual Review 2677 DTSTART:19960416T130000 2678 DTEND:19960416T140000 2679 LOCATION:Bldg. 02/Room 00-99Z 2680 UID:guid-1.host2.com 2681 END:VEVENT 2682 END:VCALENDAR 2683 --example2-- 2685 The decline of the counter proposal and revised event request message 2686 follows: 2688 From: dboss@host1.com 2689 To: nmploye@host2.com 2690 Subject: Can't Do Your Reschedule 2691 Content-Type: multipart/mixed;boundary=example2 2692 Message-Id: 2693 MIME-Version: 1.0 2695 --example2 2696 Content-Type: text/plain 2697 Content-Id: 2699 M: 2700 I understand that 4/15 is tax-day. Somehow, I am not 2701 surprised that you are doing your taxes at the last minute! 2703 The 4/16 reschedule date is okay, but we will have to do this 2704 in my office, not yours. We can also complete this in one half 2705 hour or less. 2706 - D. 2708 --example2-- 2710 --example2 2711 Content-Type: text/calendar;Profile=event/decline 2712 Content-Id: 2714 BEGIN:VCALENDAR 2715 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2716 PRODID:-//RDU Software//NONSGML HandCal//EN 2717 TZ:-05:00 2718 VERSION:1.0 2719 BEGIN:VEVENT 2720 ATTENDEE:nmeploye@host2.com 2721 LOCATION:Bldg. 02/Room 00-99Z 2722 UID:guid-1.host2.com 2723 END:VEVENT 2724 END:VCALENDAR 2726 --example2-- 2728 --example2 2729 Content-Type: text/calendar;Profile=event/request 2730 Content-Id: 2732 BEGIN:VCALENDAR 2733 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2734 PRODID:-//RDU Software//NONSGML HandCal//EN 2735 TZ:-05:00 2736 VERSION:1.0 2737 BEGIN:VEVENT 2738 ATTENDEE;EXPECT=REQUIRE;RSVP=YES:nmploye@host2.com 2739 DESCRIPTION:Employee: N. Mploye's 360 Review 2740 CATEGORIES:MEETING 2741 CLASS:CONFIDENTIAL 2742 SUMMARY:Your Annual Review 2743 DTSTART:19960416T130000 2744 DTEND:19960416T133000 2745 LOCATION:Bldg. 01/Room 07-1A 2746 UID:guid-1.host1.com 2747 SEQUENCE:1 2748 END:VEVENT 2749 END:VCALENDAR 2751 --example2-- 2753 The event reply message confirming attendance follows: 2755 From: nmploye@host2.com 2756 To: dboss@host1.com 2757 Subject: Let's Reschedule The 360 Review 2758 Content-Type: multipart/mixed;boundary=example2 2759 Message-Id: 2760 MIME-Version: 1.0 2762 --example2 2763 Content-Type: text/plain 2764 Content-Id: 2766 D: 2767 Well, I guess we can do this review quickly! 2768 - M. 2770 --example2-- 2772 --example2 2773 Content-Type: text/calendar;Profile=event/reply 2774 Content-Id: 2776 BEGIN:VCALENDAR 2777 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2778 PRODID:-//RDU Software//NONSGML HandCal//EN 2779 TZ:-05:00 2780 VERSION:1.0 2781 BEGIN:VEVENT 2782 ATTENDEE;STATUS=CONFIRMED:nmploye@host2.com 2783 UID:guid-1.host2.com 2784 SEQUENCE:1 2785 END:VEVENT 2786 END:VCALENDAR 2788 --example2-- 2789 5.3 Event/request based on free-busy time search results 2791 The following example illustrates using free-busy time results to 2792 schedule an event with a group of individuals. The message sequence 2793 involves a free-busy/request from the orginator to a group of 2794 potential group of meeting attendees. The recipients return free/busy 2795 time results with the free-busy/reply message. The originator uses 2796 this information to generate an event/request. The messages are sent 2797 as singular _text/calendar_ content type, body parts. 2799 The following message segment is a free/busy time request to a group 2800 of potential meeting attendees. 2802 From: jsmith@host1.com 2803 To: jdoe@host2.com, imquik@host3.com 2804 Subject: Free/Busy Time Request 2805 MIME-Version: 1.0 2806 Message-ID: 2807 Content-Type: text/calendar;Profile=free-busy/request 2809 BEGIN:VCALENDAR 2810 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2811 PRODID:-//RDU Software//NONSGML HandCal//EN 2812 TZ:-05:00 2813 VERSION:1.0 2814 BEGIN:VEVENT 2815 ATTENDEE:jdoe@host2.com 2816 ATTENDEE:imquik@host3.com 2817 DURATION:P1H30M 2818 DTSTART:19961112T083000 2819 DTEND:19961112T170000 2820 UID:guid-3.host1.com 2821 END:VEVENT 2822 END:VCALENDAR 2824 The following two message segment are the resultant free/busy time 2825 data replies from the two potential meeting attendees. The two reply 2826 messages assume that the originator had access privileges within the 2827 recipient calendaring and scheduling applications to get the returned 2828 information. The first message segment is the free-busy/reply from 2829 the first recipient. Notice that the first recipient's calendaring 2830 and scheduling application only returns free time data. 2832 From: jdoe@host2.com 2833 To: jsmith@host1.com 2834 Subject: Free/Busy Time Request 2835 MIME-Version: 1.0 2836 Message-ID: 2837 Content-Type: text/calendar;Profile=free-busy/reply 2839 BEGIN:VCALENDAR 2840 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2841 PRODID:-//RDU Software//NONSGML HandCal//EN 2842 TZ:-05:00 2843 VERSION:1.0 2844 BEGIN:VEVENT 2845 ATTENDEE:jdoe@host2.com 2846 DTSTART:19961112T090000 2847 DTEND:19961112T110000 2848 TRANSP:1 2849 UID:guid-3.host1.com 2850 END:VEVENT 2851 BEGIN:VEVENT 2852 ATTENDEE:jdoe@host2.com 2853 DTSTART:19961112T130000 2854 DTEND:19961112T133000 2855 TRANSP:1 2856 UID:guid-3.host1.com 2857 END:VEVENT 2858 BEGIN:VEVENT 2859 ATTENDEE:jdoe@host2.com 2860 DTSTART:19961112T141500 2861 DTEND:19961112T143000 2862 TRANSP:1 2863 UID:guid-3.host1.com 2864 END:VEVENT 2865 BEGIN:VEVENT 2866 ATTENDEE:jdoe@host2.com 2867 DTSTART:19961112T150000 2868 DTEND:19961112T170000 2869 TRANSP:1 2870 UID:guid-3.host1.com 2871 END:VEVENT 2872 END:VCALENDAR 2874 This is the free-busy/reply from the second recipient. Notice that 2875 the second recipient's calendaring and scheduling application returns 2876 both free and busy time data. In addition, more information is 2877 returned than the first recipient's application. 2879 From: imquik@host3.com 2880 To: jsmith@host1.com 2881 Subject: Free/Busy Time Request 2882 MIME-Version: 1.0 2883 Message-ID: 2884 Content-Type: text/calendar;Profile=free-busy/reply 2886 BEGIN:VCALENDAR 2887 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2888 PRODID:-//ABC Software//NONSGML VaporCal//EN 2889 TZ:-05:00 2890 VERSION:1.0 2891 BEGIN:VEVENT 2892 ATTENDEE:imquik@host3.com 2893 DTSTART:19961112T083000 2894 DTEND:19961112T110000 2895 TRANSP:1 2896 UID:guid-3.host1.com 2897 END:VEVENT 2898 BEGIN:VEVENT 2899 ATTENDEE:imquik@host3.com 2900 CATEGORIES:MISCELLANEOUS 2901 CLASS:PUBLIC 2902 DESCRIPTION:Lunch With The Boss 2903 DTSTART:19961112T110000 2904 DTEND:19961112T130000 2905 TRANSP:0 2906 UID:guid-3.host1.com 2907 END:VEVENT 2908 BEGIN:VEVENT 2909 ATTENDEE:imquik@host3.com 2910 CLASS:CONFIDENTIAL 2911 DTSTART:19961112T130000 2912 DTEND:19961112T133000 2913 TRANSP:0 2914 UID:guid-3.host1.com 2915 END:VEVENT 2916 BEGIN:VEVENT 2917 ATTENDEE:imquik@host3.com 2918 DTSTART:19961112T133000 2919 DTEND:19961112T141500 2920 TRANSP:1 2921 UID:guid-3.host1.com 2922 END:VEVENT 2923 BEGIN:VEVENT 2924 ATTENDEE:imquik@host3.com 2925 CATEGORIES:PHONE CALL;PROJECT 2926 CLASS:PUBLIC 2927 DESCRIPTION:Weekly Project Status Call 2928 DTSTART:19961112T141500 2929 DTEND:19961112T143000 2930 TRANSP:0 2931 UID:guid-3.host1.com 2932 END:VEVENT 2933 BEGIN:VEVENT 2934 ATTENDEE:imquik@host3.com 2935 DTSTART:19961112T143000 2936 DTEND:19961112T170000 2937 TRANSP:1 2938 UID:guid-3.host1.com 2939 END:VEVENT 2940 END:VCALENDAR 2942 The following message is the event/request message that uses the free 2943 time results from the previous messages. 2945 From: jsmith@host1.com 2946 To: jdoe@host2.com, imquik@host3.com 2947 Subject: New Project Discussion 2948 MIME-Version: 1.0 2949 Message-ID: 2950 Content-Type: multipart/mixed;boundary=example3 2951 MIME-Version: 1.0 2953 --example3 2954 Content-Type: text/plain 2955 Content-Id: 2957 Folks: 2959 We have to more quickly on this new Internet C&S standard. I want 2960 meet with you all and draft a project plan that (a) will result in 2961 a product in the channels by year-end and (b) we can take to the 2962 Board after COMDEX in November. 2964 - John. 2966 --example2-- 2968 --example2 2970 Content-Type: text/calendar;Profile=event/request 2971 Content-Id: 2973 BEGIN:VCALENDAR 2974 DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT 2975 PRODID:-//RDU Software//NONSGML HandCal//EN 2976 TZ:-05:00 2977 VERSION:1.0 2978 BEGIN:VEVENT 2979 ATTENDEE;EXPECT=REQUIRE;RSVP=YES:jdoe@host2.com 2980 ATTENDEE;EXPECT=REQUIRE;RSVP=YES:imquik@host3.com 2981 SUMMARY:New Project Discussion 2982 DESCRIPTION:New Project D 2983 CATEGORIES:MEETING;PROJECT 2984 CLASS:PRIVATE 2985 DCREATED:19961104T083000 2986 DTSTART:199611125T153000 2987 DTEND:19961112T170000 2988 LOCATION:Big Conf. Room 2989 UID:guid-4.host1.com 2990 END:VEVENT 2991 END:VCALENDAR 2993 --example2-- 2994 6. Acknowledgments 2996 A hearty thanks to the IETF Calendaring and Scheduling Working Group 2997 and also the following individuals who have participated in the 2998 drafting, review and discussion of this memo: 3000 Roland Alden, Harald T. Alvestrand, Denis Bigorgne, John Binici, Bill 3001 Bliss, Andre Courtemanche, Dave Crocker, Alec Dun, Ross Finlayson, 3002 Randell Flink, Ned Freed, Patrik Falstrom, Anik Ganguly, Chuck 3003 Grandgent, Mark Handley, Steve Hanna, Paul B. Hill, Mark Horton, 3004 Bruce Kahn, C. Harald Koch, Theodore Lorek, Keith Moore, Cecil 3005 Rhodes, Chris Newman, Ralph Patterson, Pete Resnick, Keith Rhodes, 3006 Robert Ripberger, Andras Salamar, Vinod Seraphin, Ken Shan, Andrew 3007 Shuman, William P. Spencer, Mark Towfiq, Robert Visnov, James L. 3008 Weiner, Mike Weston, William Wyatt. 3010 7. Bibliography 3012 [RFC1521] N. Borenstein and N. Freed, "MIME (Multipurpose Internet 3013 Mail Extensions) Part One: Mechanisms for Internet Draft UTF-825 3014 July 1996 Specifying and Describing the Format of Internet Message 3015 Bodies", RFC 1521, Bellcore, Innosoft, September 1993. 3017 [MIME-CAL] F. Dawson, _MIME Calendaring and Scheduling Content 3018 Type_, Internet Draft, draft-dawson-csct-00.txt, IBM Corporation, 3019 October 1996. 3021 8. Author's Address 3023 The following address information is provided in a MIME-VCARD, 3024 Electronic Business Card, format. 3026 BEGIN:VCARD 3027 FN:Frank Dawson 3028 ORG:IBM Corporation 3029 ADR;WORK;POSTAL;PARCEL:;APNA/CC-303/Bldg. 002;3039 Cornwallis Rd; 3030 Research Triangle Park;NC;27709;USA 3031 TEL;WORK;MSG:+1-919-254-5861 3032 TEL;WORK;FAX:+1-919-543-6822 3033 EMAIL;INTERNET:fdawson@us1.ibm.com 3034 EMAIL;HOME;INTERNET:fdawson@earthlink.net 3035 URL;HOME:http://home.earthlink.net/~fdawson 3036 END:VCARD