idnits 2.17.1 draft-ietf-calext-eventpub-extensions-19.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). (Using the creation date from RFC5545, updated by this document, for RFC5378 checks: 2005-10-26) -- 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 (March 26, 2021) is 1127 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) -- Looks like a reference, but probably isn't: '3' on line 1307 ** Obsolete normative reference: RFC 2426 (Obsoleted by RFC 6350) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Douglass 3 Internet-Draft Bedework 4 Updates: 5545 (if approved) March 26, 2021 5 Intended status: Standards Track 6 Expires: September 27, 2021 8 Event Publishing Extensions to iCalendar 9 draft-ietf-calext-eventpub-extensions-19 11 Abstract 13 This specification updates RFC5545 by introducing a number of new 14 iCalendar properties and components which are of particular use for 15 event publishers and in social networking. 17 This specification also defines a new STRUCTURED-DATA property for 18 iCalendar RFC5545 to allow for data that is directly pertinent to an 19 event or task to be included with the calendar data. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 27, 2021. 38 Copyright Notice 40 Copyright (c) 2021 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 57 1.2. Terms Used in This Document . . . . . . . . . . . . . . . 3 58 2. Components and properties . . . . . . . . . . . . . . . . . . 4 59 3. Typed References . . . . . . . . . . . . . . . . . . . . . . 4 60 3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5 61 3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5 62 3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 5 63 3.1.2.1. Reserving facilities . . . . . . . . . . . . . . 6 64 4. Modifications to Calendar Components . . . . . . . . . . . . 6 65 5. New Property Parameters . . . . . . . . . . . . . . . . . . . 7 66 5.1. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 7 67 5.2. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 8 68 5.3. Derived . . . . . . . . . . . . . . . . . . . . . . . . . 9 69 6. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10 70 6.1. Location Type . . . . . . . . . . . . . . . . . . . . . . 10 71 6.2. Participant Type . . . . . . . . . . . . . . . . . . . . 11 72 6.3. Resource Type . . . . . . . . . . . . . . . . . . . . . . 13 73 6.4. Calendar Address . . . . . . . . . . . . . . . . . . . . 14 74 6.5. Styled-Description . . . . . . . . . . . . . . . . . . . 14 75 6.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 16 76 7. New Components . . . . . . . . . . . . . . . . . . . . . . . 19 77 7.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 19 78 7.1.1. Schedulable Participant . . . . . . . . . . . . . . . 21 79 7.2. Location . . . . . . . . . . . . . . . . . . . . . . . . 22 80 7.3. Resource . . . . . . . . . . . . . . . . . . . . . . . . 23 81 8. Extended examples . . . . . . . . . . . . . . . . . . . . . . 25 82 8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 25 83 8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 26 84 9. Security Considerations . . . . . . . . . . . . . . . . . . . 26 85 9.1. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 26 86 9.2. Malicious Content . . . . . . . . . . . . . . . . . . . . 27 87 9.3. HTML Content . . . . . . . . . . . . . . . . . . . . . . 27 88 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 89 10.1. Tracking . . . . . . . . . . . . . . . . . . . . . . . . 27 90 10.2. Revealing Locations . . . . . . . . . . . . . . . . . . 27 91 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 92 11.1. Additional iCalendar Registrations . . . . . . . . . . . 28 93 11.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 28 94 11.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 28 95 11.1.3. Components . . . . . . . . . . . . . . . . . . . . . 29 96 11.2. New Registration Tables . . . . . . . . . . . . . . . . 29 97 11.2.1. Participant Types . . . . . . . . . . . . . . . . . 29 98 11.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 30 99 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 100 13. Normative References . . . . . . . . . . . . . . . . . . . . 30 101 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 32 102 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 32 103 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 35 105 1. Introduction 107 The currently existing iCalendar standard [RFC5545] lacks useful 108 methods for referencing additional, external information relating to 109 calendar components. Additionally there is no standard way to 110 provide rich text descriptions or meta-data associated with the 111 event. 113 Current practice is to embed this information as links in the 114 description or to add non-standard properties as defined in [RFC5545] 115 section 3.8.8.2. 117 This document updates [RFC5545] to define a number of properties and 118 components referencing such external information that can provide 119 additional information about an iCalendar component. The intent is 120 to allow interchange of such information between applications or 121 systems (e.g., between clients, between client and server, and 122 between servers). Formats such as vCard [RFC2426] are likely to be 123 most useful to the receivers of such events as they may be used in 124 other applications - such as address books. 126 1.1. Conventions Used in This Document 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and 130 "OPTIONAL" in this document are to be interpreted as described in BCP 131 14 [RFC2119] [RFC8174] when, and only when, they appear in all 132 capitals, as shown here. 134 1.2. Terms Used in This Document 136 Event: When the (perhaps with a capitalised 'E') word 'event' is 137 used we are referring to gatherings, formal or informal. For 138 example a sports event, a party or a concert. 140 Social Calendaring: Historically, calendar data and scheduling has 141 been heavily biased towards meetings in a corporate environment. 142 Some of the features defined in this document are to support a 143 more informal, i.e. social, model. For example, we may want to 144 record who is participating in a public event. 146 2. Components and properties 148 Previous extensions to the calendaring standards have been largely 149 restricted to the addition of properties or parameters. This is 150 partly because iCalendar libraries had trouble handling components 151 nested deeper than those defined in [RFC5545]. 153 In a break with this 'tradition' this specification defines a number 154 of components rather than properties. This is a better match for the 155 way [W3C.REC-xml-20081126] and JSON [RFC8259] handle such structures 156 and allows richer definitions. 158 It also allows for the addition of extra properties inside the 159 components and resolves some of the problems of trying to add 160 detailed information as a parameter. 162 3. Typed References 164 The properties and components defined here can all reference external 165 meta-data which may be used by applications to provide further 166 information to users. By providing type information, clients and 167 servers are able to discover interesting references and make use of 168 them, perhaps for indexing or the presenting of additional related 169 information for the user. 171 As always, clients should exercise caution in following references to 172 external data. 174 The [RFC5545] LOCATION property provides only an unstructured single 175 text value for specifying the location where an event (or task) will 176 occur. This is inadequate for use cases where structured location 177 information (e.g. address, region, country, postal code) is required 178 or preferred, and limits widespread adoption of iCalendar in those 179 settings. 181 Using the VLOCATION component, rich information about multiple 182 locations can be communicated in a STRUCTURED-DATA property, for 183 example, address, region, country, postal code as well as other 184 information such as parking availability, nearby restaurants and the 185 venue. Servers and clients can retrieve the objects when storing the 186 event and use them to index by geographic location. 188 When a calendar client receives a calendar component it can search 189 the set of locations looking for those of particular interest. The 190 LOCATION-TYPE property and STRUCTURED-DATA FMTTYPE parameter, if 191 supplied, can be used to help the selection. 193 The PARTICIPANT component is designed to handle common use cases in 194 event publication. It is generally important to provide information 195 about the organizers of such events. Sponsors wish to be referenced 196 in a prominent manner. In social calendaring it is often important 197 to identify the active participants in the event, for example a 198 school sports team, and the inactive participants, for example the 199 parents. 201 The PARTICIPANT component can be used to provide useful extra data 202 about an attendee. For example a location inside the PARTICIPANT 203 gives the actual location of a remote attendee. (But see the note 204 about privacy.) 206 Alternatively the PARTICIPANT component can be used to provide a 207 reference - perhaps the address for mailing lists. 209 3.1. Use Cases 211 The main motivation for these changes has been event publication but 212 there are opportunities for use elsewhere. The following use cases 213 will describe some possible scenarios. 215 3.1.1. Piano Concert Performance 217 In putting together a concert there are many participants: piano 218 tuner, performer, stage hands etc. In addition there are sponsors 219 and various contacts to be provided. There will also be a number of 220 related locations. A number of events can be created, all of which 221 relate to the performance in different ways. 223 There may be an iTIP [RFC5546] meeting request for the piano tuner 224 who will arrive before the performance. Other members of staff may 225 also receive meeting requests. 227 An event can also be created for publication which will have a 228 PARTICIPANT component for the pianist providing a reference to vCard 229 [RFC2426] information about the performer. This event would also 230 hold information about parking, local subway stations and the venue 231 itself. In addition, there may be sponsorship information for 232 sponsors of the event and perhaps paid sponsorship properties 233 essentially advertising local establishments. 235 3.1.2. Itineraries 237 These additions also provide opportunities for the travel industry. 238 When booking a flight the PARTICIPANT component can be used to 239 provide references to businesses at the airports and to car hire 240 businesses at the destination. 242 The embedded location information can guide the traveler at the 243 airport or to their final destination. The contact information can 244 provide detailed information about the booking agent, the airlines, 245 car hire companies and the hotel. 247 3.1.2.1. Reserving facilities 249 For a meeting, the size of a room and the equipment needed depends to 250 some extent on the number of attendees actually in the room. 252 A meeting may have many attendees none of which are co-located. The 253 current ATTENDEE property does not allow for the addition of such 254 meta-data. The PARTICIPANT component allows attendees to specify 255 their location. 257 4. Modifications to Calendar Components 259 The following changes to the syntax defined in iCalendar [RFC5545] 260 are made here. New elements are defined in subsequent sections. 262 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 263 ; as valid components 264 eventc = "BEGIN" ":" "VEVENT" CRLF 265 eventprop *alarmc *participantc *locationc *resourcec 266 "END" ":" "VEVENT" CRLF 268 ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA 269 eventprop =/ *styleddescription 270 *sdataprop 272 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 273 ; as valid components 274 todoc = "BEGIN" ":" "VTODO" CRLF 275 todoprop *alarmc *participantc *locationc *resourcec 276 "END" ":" "VTODO" CRLF 278 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA 279 todoprop =/ *styleddescription 280 *sdataprop 282 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 283 ; as valid components 284 journalc = "BEGIN" ":" "VJOURNAL" CRLF 285 jourprop *participantc *locationc *resourcec 286 "END" ":" "VJOURNAL" CRLF 288 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA 289 jourprop =/ *styleddescription 290 *sdataprop 292 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 293 ; as valid components 294 freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF 295 fbprop *participantc *locationc *resourcec 296 "END" ":" "VFREEBUSY" CRLF 298 ; Addition of property STYLED-DESCRIPTION 299 fbprop =/ *styleddescription 301 5. New Property Parameters 303 5.1. Order 305 Parameter name: ORDER 307 Purpose: To define ordering for the associated property. 309 Format Definition: 311 This parameter is defined by the following notation: 313 orderparam = "ORDER" "=" integer 314 ; Must be greater than or equal to 1 316 Description: The ORDER parameter is OPTIONAL and is used to indicate 317 the relative ordering of the corresponding instance of a property. 318 Its value MUST be an integer greater than or equal to 1 that 319 specifies the order with 1 being the first in the ordering. 321 When the parameter is absent, the default MUST be to interpret the 322 property instance as being ordered last, that is, the property 323 will appear after any other instances of the same property with 324 any value of ORDER. 326 When any ORDER parameters have the same value all the associated 327 properties appear as a group within which there is no defined 328 order. 330 Note that the value of this parameter is to be interpreted only in 331 relation to values assigned to other corresponding instances of 332 the same property in the same entity. 334 This parameter MUST NOT be applied to a property that does not 335 allow multiple instances. 337 Example uses: The ORDER may be applied to the PARTICIPANT-TYPE 338 property to indicate the relative importance of the participant, 339 for example as a sponsor or a performer. For example, ORDER=1 340 could define the principal performer or soloist. 342 5.2. Schema 344 Parameter Name: SCHEMA 346 Purpose: To specify the schema used for the content of a 347 "STRUCTURED-DATA" property value. 349 Format Definition: 351 This parameter is defined by the following notation: 353 schemaparam = "SCHEMA" "=" DQUOTE uri DQUOTE 355 Description: This property parameter SHOULD be specified on 356 "STRUCTURED-DATA" properties. When present it provides 357 identifying information about the nature of the content of the 358 corresponding "STRUCTURED-DATA" property value. This can be used 359 to supplement the media type information provided by the "FMTTYPE" 360 parameter on the corresponding property. 362 Example: 364 STRUCTURED-DATA;FMTTYPE=application/ld+json; 365 SCHEMA="https://schema.org/FlightReservation"; 366 ENCODING=BASE64;VALUE=BINARY:ICAgIDxzY3JpcHQgdHlwZT0iYXBwb 367 GljYXRpb24vbGQranNvbiI+CiAgICB7CiAgICAgICJAY29 368 udGV4dCI6ICJodHRwOi8vc2NoZW1hLm9yZyIsCiAgICAgICJAdHlwZSI 369 6ICJGbGlnaHRSZXNlcnZhdGlvbiIsCiAgICAgICJyZXNlcnZhdGlvbkl 370 kIjogIlJYSjM0UCIsCiAgICAgICJyZXNlcnZhdGlvblN0YXR1cyI6ICJ 371 odHRwOi8vc2NoZW1hLm9yZy9SZXNlcnZhdGlvbkNvbmZpcm1lZCIsCiA 372 gICAgICJwYXNzZW5nZXJQcmlvcml0eVN0YXR1cyI6ICJGYXN0IFRyYWN 373 rIiwKICAgICAgInBhc3NlbmdlclNlcXVlbmNlTnVtYmVyIjogIkFCQzE 374 yMyIsCiAgICAgICJzZWN1cml0eVNjcmVlbmluZyI6ICJUU0EgUHJlQ2h 375 lY2siLAogICAgICAidW5kZXJOYW1lIjogewogICAgICAgICJAdHlwZSI 376 6ICJQZXJzb24iLAogICAgICAgICJuYW1lIjogIkV2YSBHcmVlbiIKICA 377 gICAgfSwKICAgICAgInJlc2VydmF0aW9uRm9yIjogewogICAgICAgICJ 378 AdHlwZSI6ICJGbGlnaHQiLAogICAgICAgICJmbGlnaHROdW1iZXIiOiA 379 iVUExMTAiLAogICAgICAgICJwcm92aWRlciI6IHsKICAgICAgICAgICJ 380 AdHlwZSI6ICJBaXJsaW5lIiwKICAgICAgICAgICJuYW1lIjogIkNvbnR 381 pbmVudGFsIiwKICAgICAgICAgICJpYXRhQ29kZSI6ICJDTyIsCiAgICA 382 gICAgICAiYm9hcmRpbmdQb2xpY3kiOiAiaHR0cDovL3NjaGVtYS5vcmc 383 vWm9uZUJvYXJkaW5nUG9saWN5IgogICAgICAgIH0sCiAgICAgICAgInN 384 lbGxlciI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJsaW5lIiwKICA 385 gICAgICAgICJuYW1lIjogIlVuaXRlZCIsCiAgICAgICAgICAiaWF0YUN 386 vZGUiOiAiVUEiCiAgICAgICAgfSwKICAgICAgICAiZGVwYXJ0dXJlQWl 387 ycG9ydCI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJwb3J0IiwKICA 388 gICAgICAgICJuYW1lIjogIlNhbiBGcmFuY2lzY28gQWlycG9ydCIsCiA 389 gICAgICAgICAiaWF0YUNvZGUiOiAiU0ZPIgogICAgICAgIH0sCiAgICA 390 gICAgImRlcGFydHVyZVRpbWUiOiAiMjAxNy0wMy0wNFQyMDoxNTowMC0 391 wODowMCIsCiAgICAgICAgImFycml2YWxBaXJwb3J0IjogewogICAgICA 392 gICAgIkB0eXBlIjogIkFpcnBvcnQiLAogICAgICAgICAgIm5hbWUiOiA 393 iSm9obiBGLiBLZW5uZWR5IEludGVybmF0aW9uYWwgQWlycG9ydCIsCiA 394 gICAgICAgICAiaWF0YUNvZGUiOiAiSkZLIgogICAgICAgIH0sCiAgICA 395 gICAgImFycml2YWxUaW1lIjogIjIwMTctMDMtMDVUMDY6MzA6MDAtMDU 396 6MDAiCiAgICAgIH0KICAgIH0KICAgIDwvc2NyaXB0Pg== 398 5.3. Derived 400 Parameter Name: DERIVED 402 Purpose: To specify that the value of the associated property is 403 derived from some other property value or values. 405 Format Definition: 407 This parameter is defined by the following notation: 409 derivedparam = "DERIVED" "=" ("TRUE" / "FALSE") 410 ; Default is FALSE 412 Description: This property parameter MAY be specified on any 413 property when the value is derived from some other property or 414 properties. When present with a value of TRUE clients MUST NOT 415 update the property. 417 As an example, if a STYLED-DESCRIPTION property is present with 418 FMTTYPE="application/rtf" then there may be an additional STYLED- 419 DESCRIPTION property with FMTTYPE="text/html" and DERIVED=TRUE and 420 a value created from the rtf value. 422 Example: 424 STYLED-DESCRIPTION;FMTTYPE=text/html; 425 DERIVED=TRUE:... 427 6. New Properties 429 This specification makes use of the NAME property which is defined in 430 [RFC7986] 432 6.1. Location Type 434 Property name: LOCATION-TYPE 436 Purpose: To specify the type(s) of a location. 438 Value type: The value type for this property is TEXT. The allowable 439 values are defined below. 441 Description: This property MAY be specified in VLOCATION components 442 and provides a way to differentiate multiple locations. For 443 example, it allows event producers to provide location information 444 for the venue and the parking. 446 Format Definition: 448 This property is defined by the following notation: 450 loctype = "LOCATION-TYPE" loctypeparam ":" 451 text *("," text) 452 CRLF 454 loctypeparam = *(";" other-param) 456 Multiple values may be used if the location has multiple purposes, 457 for example a hotel and a restaurant. 459 Values for this parameter are taken from the values defined in 460 [RFC4589] section 3. New location types SHOULD be registered in 461 the manner laid down in section 5 of that specification. 463 6.2. Participant Type 465 Property name: PARTICIPANT-TYPE 467 Purpose: To specify the type of participant. 469 Value type: The value type for this property is TEXT. The allowable 470 values are defined below. 472 Property Parameters: Non-standard parameters can be specified on 473 this property. 475 Conformance: This property MUST be specified once within a 476 PARTICIPANT component. 478 Description: This property defines the type of participation in 479 events or tasks. Participants can be individuals or 480 organizations, for example a soccer team, the spectators, or the 481 musicians. 483 Format Definition: 485 This property is defined by the following notation: 487 participanttype = "PARTICIPANT-TYPE" partvalueparam ":" 488 partvalue CRLF 490 partvalue = ("ACTIVE" 491 / "INACTIVE" 492 / "SPONSOR" 493 / "CONTACT" 494 / "BOOKING-CONTACT" 495 / "EMERGENCY-CONTACT" 496 / "PUBLICITY-CONTACT" 497 / "PLANNER-CONTACT" 498 / "PERFORMER" 499 / "SPEAKER" 500 / iana-token) ; Other IANA-registered 501 ; values 503 partvalueparam = *(";" other-param) 505 Example: 507 The following is an example of this property: 509 PARTICIPANT-TYPE:SPEAKER 511 The registered values for the PARTICIPANT-TYPE property have the 512 meanings described here: 514 ACTIVE: A participant taking an active role - for example a team 515 member. 517 INACTIVE: A participant taking an inactive role - for example an 518 audience member. 520 SPONSOR: A sponsor of the event. The ORDER parameter may be used 521 with this participant type to define the relative order of 522 multiple sponsors. 524 CONTACT: Contact information for the event. The ORDER parameter may 525 be used with this participant type to define the relative order of 526 multiple contacts. 528 BOOKING-CONTACT: Contact information for reservations or payment 530 EMERGENCY-CONTACT: Contact in case of emergency 532 PUBLICITY-CONTACT: Contact for publicity 533 PLANNER-CONTACT: Contact for the event planner or organizer 535 PERFORMER: A performer - for example the soloist or the accompanist. 536 The ORDER parameter may be used with this participant type to 537 define the relative order of multiple performers. For example, 538 ORDER=1 could define the principal performer or soloist. 540 SPEAKER: Speaker at an event 542 6.3. Resource Type 544 Property name: RESOURCE-TYPE 546 Purpose: To specify the type of resource. 548 Value type: The value type for this property is TEXT. The allowable 549 values are defined below. 551 Format Definition: 553 This property is defined by the following notation: 555 restypeprop = "RESOURCE-TYPE" restypeparam ":" 556 restypevalue CRLF 558 restypevalue = ("ROOM" 559 / "PROJECTOR" 560 / "REMOTE-CONFERENCE-AUDIO" 561 / "REMOTE-CONFERENCE-VIDEO" 562 / iana-token) ; Other IANA-registered 563 ; values 565 restypeparam = *(";" other-param) 567 Description: This property MAY be specified in VRESOURCE components 568 and provides a way to differentiate multiple resources. 570 The registered values are described below. New resource types 571 SHOULD be registered in the manner laid down in this 572 specification. 574 ROOM: A room for the event/meeting. 576 PROJECTOR: Projection equipment. 578 REMOTE-CONFERENCE-AUDIO: Audio remote conferencing facilities. 580 REMOTE-CONFERENCE-VIDEO: Video remote conferencing facilities. 582 6.4. Calendar Address 584 Property name: CALENDAR-ADDRESS 586 Purpose: To specify the calendar address for a participant. 588 Value type: CAL-ADDRESS 590 Property Parameters: IANA-registered, or non-standard property 591 parameters can be specified on this property. 593 Conformance: This property MAY be specified once within a 594 PARTICIPANT component. 596 Description: This property provides a calendar user address for the 597 participant. If there is an ATTENDEE property with the same value 598 then the participant is schedulable. 600 Format Definition: 602 This property is defined by the following notation: 604 calendaraddress = "CALENDAR-ADDRESS" caladdressparam ":" 605 cal-address CRLF 607 caladdressparam = *(";" other-param) 609 6.5. Styled-Description 611 Property name: STYLED-DESCRIPTION 613 Purpose: This property provides for one or more rich-text 614 descriptions to replace that provided by the DESCRIPTION property. 616 Value type: There is no default value type for this property. The 617 value type can be set to URI or TEXT. Other text-based value 618 types can be used when defined in the future. Clients MUST ignore 619 any properties with value types they do not understand. 621 Property Parameters: IANA-registered, non-standard, id, alternate 622 text representation, format type, derived and language property 623 parameters can be specified on this property. 625 Conformance: The property can be specified multiple times in the 626 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY", "PARTICIPANT", or 627 "VALARM" calendar components. 629 If it does appear more than once there MUST be exactly one 630 instance of the property with no DERIVED parameter or 631 DERIVED=FALSE. All others MUST have DERIVED=TRUE. 633 Additionally, if there is one or more STYLED-DESCRIPTION property 634 then the DESCRIPTION property should be either absent or have the 635 parameter DERIVED=TRUE. 637 Description: This property supports rich-text descriptions, for 638 example HTML. Event publishers typically wish to provide more and 639 better formatted information about the event. 641 This property is used in the "VEVENT" and "VTODO" to capture 642 lengthy textual descriptions associated with the activity. This 643 property is used in the "VJOURNAL" calendar component to capture 644 one or more textual journal entries. This property is used in the 645 "VALARM" calendar component to capture the display text for a 646 DISPLAY category of alarm, and to capture the body text for an 647 EMAIL category of alarm. In the PARTICIPANT component it provides 648 a detailed description of the participant. 650 VALUE=TEXT is used to provide rich-text inline as the property 651 value. 653 VALUE=URI is used to provide a link to rich-text content which is 654 expected to be displayed inline as part of the event. 656 In either case the DESCRIPTION property should be absent or 657 contain a plain text rendering of the styled text. 659 Applications MAY attempt to guess the media type of the resource 660 via inspection of its content if and only if the media type of the 661 resource is not given by the "FMTTYPE" parameter. If the media 662 type remains unknown, calendar applications SHOULD treat it as 663 type "text/html" and process the content as defined in 664 [W3C.REC-html51-20171003] 666 Multiple STYLED-DESCRIPTION properties may be used to provide 667 different formats or different language variants. However all but 668 one MUST have DERIVED=TRUE. 670 Format Definition: 672 This property is defined by the following notation: 674 styleddescription = "STYLED-DESCRIPTION" styleddescparam ":" 675 styleddescval CRLF 677 styleddescparam = *( 678 ; The following is REQUIRED, 679 ; but MUST NOT occur more than once. 680 ; 681 (";" "VALUE" "=" ("URI" / "TEXT")) / 682 ; 683 ; The following are OPTIONAL, 684 ; but MUST NOT occur more than once. 685 ; 686 (";" altrepparam) / (";" languageparam) / 687 (";" fmttypeparam) / (";" derivedparam) / 688 ; 689 ; the following is OPTIONAL 690 ; and MAY occur more than once 691 ; 692 (";" other-param) 693 ) 695 styleddescval = ( uri / text ) 696 ;Value MUST match value type 698 Example: 700 The following is an example of this property. It points to an html 701 description. 703 STYLED-DESCRIPTION;VALUE=URI:http://example.org/desc001.html 705 6.6. Structured-Data 707 Property Name: STRUCTURED-DATA 709 Purpose: This property specifies ancillary data associated with the 710 calendar component. 712 Value Type: There is no default value type for this property. The 713 value type can be set to TEXT, BINARY or URI 715 Property Parameters: IANA-registered, non-standard, inline encoding 716 and value data type property parameters can be specified on this 717 property. The format type and schema parameters can be specified 718 on this property and MUST be present for text or inline binary 719 encoded content information. 721 Conformance: This property can be specified multiple times in an 722 iCalendar object. Typically it would be used in "VEVENT", "VTODO" 723 or "VJOURNAL" calendar components. 725 Description: The existing properties in iCalendar cover key elements 726 of events and tasks such as start time, end time, location, 727 summary, etc. However, different types of events often have other 728 specific "fields" that it is useful to include in the calendar 729 data. For example, an event representing an airline flight could 730 include the airline, flight number, departure and arrival airport 731 codes, check-in and gate-closing times etc. As another example, a 732 sporting event might contain information about the type of sport, 733 the home and away teams, the league the teams are in, information 734 about nearby parking, etc. 736 This property is used to specify ancillary data in some structured 737 format either directly (inline) as a "TEXT" or "BINARY" value or 738 as a link via a "URI" value. 740 Rather than define new iCalendar properties for the variety of 741 event types that might occur, it would be better to leverage 742 existing schemas for such data. For example, schemas available at 743 https://schema.org include different event types. By using 744 standard schemas, interoperability can be improved between 745 calendar clients and non-calendaring systems that wish to generate 746 or process the data. 748 This property allows the direct inclusion of ancillary data whose 749 schema is defined elsewhere. This property also includes 750 parameters to clearly identify the type of the schema being used 751 so that clients can quickly and easily spot what is relevant 752 within the calendar data and present that to users or process it 753 within the calendaring system. 755 iCalendar does support an "ATTACH" property which can be used to 756 include documents or links to documents within the calendar data. 757 However, that property does not allow data to be included as a 758 "TEXT" value (a feature that "STRUCTURED-DATA" does allow), plus 759 attachments are often treated as "opaque" data to be processed by 760 some other system rather than the calendar client. Thus the 761 existing "ATTACH" property is not sufficient to cover the specific 762 needs of inclusion of schema data. Extending the "ATTACH" 763 property to support a new value type would likely cause 764 interoperability problems. Additionally some implementations 765 manage attachments by stripping them out and replacing with a link 766 to the resource. Thus a new property to support inclusion of 767 schema data is warranted. 769 Format Definition: 771 This property is defined by the following notation: 773 sdataprop = "STRUCTURED-DATA" sdataparam 774 ( 775 ";" "VALUE" "=" "TEXT" 776 ":" text 777 ) / 778 ( 779 ";" "ENCODING" "=" "BASE64" 780 ";" "VALUE" "=" "BINARY" 781 ":" binary 782 ) / 783 ( 784 ";" "VALUE" "=" "URI" 785 ":" uri 786 ) 787 CRLF 789 sdataparam = *( 790 ; 791 ; The following is OPTIONAL for a URI value, 792 ; REQUIRED for a TEXT or BINARY value, 793 ; and MUST NOT occur more than once. 794 ; 795 (";" fmttypeparam) / 796 (";" schemaparam) / 797 ; 798 ; The following is OPTIONAL, 799 ; and MAY occur more than once. 800 ; 801 (";" other-param) 802 ; 803 ) 805 Example: The following is an example of this property: 807 STRUCTURED-DATA;FMTTYPE=application/ld+json; 808 SCHEMA="https://schema.org/SportsEvent"; 809 VALUE=TEXT:{\n 810 "@context": "http://schema.org"\,\n 811 "@type": "SportsEvent"\,\n 812 "homeTeam": "Pittsburgh Pirates"\,\n 813 "awayTeam": "San Francisco Giants"\n 814 }\n 816 7. New Components 818 7.1. Participant 820 Component name: PARTICIPANT 822 Purpose: This component provides information about a participant in 823 an event or task. 825 Conformance: This component can be specified multiple times in a 826 "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar component. 828 Description: This component provides information about a participant 829 in a calendar component. A participant may be an attendee in a 830 scheduling sense and the ATTENDEE property may be specified in 831 addition. Participants can be individuals or organizations, for 832 example a soccer team, the spectators or the musicians. 834 STRUCTURED-DATA properties if present may refer to definitions of 835 the participant - such as a vCard. 837 The CALENDAR-ADDRESS property if present will provide a cal- 838 address. If an ATTENDEE property has the same value the 839 participant is considered schedulable. The PARTICIPANT component 840 can be used to contain additional meta-data related to the 841 attendee. 843 Format Definition: 845 This component is defined by the following notation: 847 participantc = "BEGIN" ":" "PARTICIPANT" CRLF 848 partprop *locationc *resourcec 849 "END" ":" "PARTICIPANT" CRLF 851 partprop = *( 852 ; 853 ; The following are REQUIRED, 854 ; but MUST NOT occur more than once. 855 ; 856 participanttype / uid / 857 ; 858 ; The following are OPTIONAL, 859 ; but MUST NOT occur more than once. 860 ; 861 calendaraddress / created / description / dtstamp / 862 geo / last-mod / priority / seq / 863 status / summary / url / 864 ; 865 ; The following are OPTIONAL, 866 ; and MAY occur more than once. 867 ; 868 attach / categories / comment / 869 contact / location / rstatus / related / 870 resources / strucloc / strucres / styleddescription / 871 sdataprop / iana-prop 872 ; 873 ) 875 Note: When the PRIORITY is supplied it defines the ordering of 876 PARTICIPANT components with the same value for the PARTICIPANT- 877 TYPE property. 879 Privacy Issues: When a LOCATION is supplied it provides information 880 about the location of a participant at a given time or times. 881 This may represent an unacceptable privacy risk for some 882 participants. User agents MUST NOT broadcast this information 883 without the express permission of the participants whose location 884 would be exposed. For further comments see Section 10 886 Example: 888 The following is an example of this component. It contains a 889 STRUCTURED-DATA property which points to a vCard providing 890 information about the event participant. 892 BEGIN:PARTICIPANT 893 UID: em9lQGZvb2GFtcGxlLmNvbQ 894 PARTICIPANT-TYPE:PERFORMER 895 STRUCTURED-DATA;VALUE=URI: 896 http://dir.example.com/vcard/aviolinist.vcf 897 END:PARTICIPANT 899 Example: 901 The following is an example for the primary contact. 903 BEGIN:PARTICIPANT 904 UID: em9lQGZvb2GFtcGxlLmNvbQ 905 STRUCTURED-DATA;VALUE=URI; 906 http://dir.example.com/vcard/contacts/contact1.vcf 907 PARTICIPANT-TYPE:CONTACT 908 DESCRIPTION:A contact 909 END:PARTICIPANT 911 Example: 913 The following is an example for a participant with contact and 914 location. 916 BEGIN:PARTICIPANT 917 UID: em9lQGZvb2GFtcGxlLmNdrt 918 STRUCTURED-DATA;VALUE=URI; 919 http://dir.example.com/vcard/contacts/my-card.vcf 920 PARTICIPANT-TYPE:SPEAKER 921 DESCRIPTION:A participant 922 BEGIN:VLOCATION 923 UID:123456-abcdef-98765432 924 NAME:My home location 925 STRUCTURED-DATA;VALUE=URI: 926 http://dir.example.com/addresses/my-home.vcf 927 END:VLOCATION 928 END:PARTICIPANT 930 7.1.1. Schedulable Participant 932 A PARTICIPANT component may represent someone or something that needs 933 to be scheduled as defined for ATTENDEE in [RFC5545] and [RFC5546]. 934 The PARTICIPANT component may also represent someone or something 935 that is NOT to receive scheduling messages. 937 For backwards compatibility with existing clients and servers when 938 used to schedule events and tasks the ATTENDEE property MUST be used 939 to specify the sheduling parameters as defined for that property. 941 For other, future uses the CALENDAR-ADDRESS property MUST be used to 942 specify those parameters. 944 A PARTICIPANT component is defined to be schedulable if 946 o It contains a CALENDAR-ADDRESS property 948 o That property value is the same as the value for an ATTENDEE 949 property. 951 If both of these conditions apply then the participant defined by the 952 value of the URL property will take part in scheduling operations as 953 defined in [RFC5546]. 955 An appropriate use for the PARTICIPANT component in scheduling would 956 be to store SEQUENCE and DTSTAMP properties associated with replies 957 from each ATTENDEE. A LOCATION property within the PARTICIPANT 958 component might allow better selection of meeting times when 959 participants are in different timezones. 961 7.2. Location 963 Component name: VLOCATION 965 Purpose: This component provides rich information about the location 966 of an event using the structured data property or optionally a 967 plain text typed value. 969 Conformance: This component can be specified multiple times in a 970 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY" or "PARTICIPANT" 971 calendar component. 973 Description: There may be a number of locations associated with an 974 event. This component provides detailed information about a 975 location. 977 When used in a component the value of this property provides 978 information about the event venue or of related services such as 979 parking, dining, stations etc.. 981 STRUCTURED-DATA properties if present may refer to representations 982 of the location - such as a vCard. 984 Format Definition: 986 This component is defined by the following notation: 988 locationc = "BEGIN" ":" "VLOCATION" CRLF 989 locprop 990 "END" ":" "VLOCATION" CRLF 992 locprop = *( 993 ; 994 ; The following are REQUIRED, 995 ; but MUST NOT occur more than once. 996 ; 997 uid / 998 ; 999 ; The following are OPTIONAL, 1000 ; but MUST NOT occur more than once. 1001 ; 1002 description / geo / loctype / name / 1003 ; 1004 ; The following are OPTIONAL, 1005 ; and MAY occur more than once. 1006 ; 1007 sdataprop / iana-prop 1009 The NAME property is defined in [RFC7986] 1011 Example: 1013 The following is an example of this component. It points to a venue. 1015 BEGIN:VLOCATION 1016 UID:123456-abcdef-98765432 1017 NAME:The venue 1018 STRUCTURED-DATA;VALUE=URI: 1019 http://dir.example.com/venues/big-hall.vcf 1020 END:VLOCATION 1022 7.3. Resource 1024 Component name: VRESOURCE 1026 Purpose: This component provides a typed reference to external 1027 information about a resource or optionally a plain text typed 1028 value. Typically a resource is anything that might be required or 1029 used by a calendar entity and possibly has a directory entry. 1031 Conformance: This component can be specified multiple times in a 1032 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY" or "PARTICIPANT" 1033 calendar component. 1035 Description: When used in a component this component provides 1036 information about resources used for the event such as rooms, 1037 projectors, conferencing capabilities. 1039 The RESOURCE-TYPE value registry provides a place in which 1040 resource types may be registered. 1042 STRUCTURED-DATA properties if present may refer to representations 1043 of the resource - such as a vCard. 1045 Format Definition: 1047 This component is defined by the following notation: 1049 resourcec = "BEGIN" ":" "VRESOURCE" CRLF 1050 resprop 1051 "END" ":" "VRESOURCE" CRLF 1053 resprop = *( 1054 ; 1055 ; The following are REQUIRED, 1056 ; but MUST NOT occur more than once. 1057 ; 1058 uid / 1059 ; 1060 ; The following are OPTIONAL, 1061 ; but MUST NOT occur more than once. 1062 ; 1063 description / geo / name / restype / 1064 ; 1065 ; The following are OPTIONAL, 1066 ; and MAY occur more than once. 1067 ; 1068 sdataprop / iana-prop 1070 The NAME property is defined in [RFC7986] 1072 Example: 1074 The following is an example of this component. It refers to a 1075 projector. 1077 BEGIN:VRESOURCE 1078 UID:456789-abcdef-98765432 1079 NAME:The projector 1080 RESOURCE-TYPE:projector 1081 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/projectors/3d.vcf 1082 END:VRESOURCE 1084 8. Extended examples 1086 The following are some examples of the use of the properties defined 1087 in this specification. They include additional properties defined in 1088 [RFC7986] which includes IMAGE. 1090 8.1. Example 1 1092 The following is an example of a VEVENT describing a concert. It 1093 includes location information for the venue itself as well as 1094 references to parking and restaurants. 1096 BEGIN:VEVENT 1097 CREATED:20200215T145739Z 1098 DESCRIPTION: Piano Sonata No 3\n 1099 Piano Sonata No 30 1100 DTSTAMP:20200215T145739Z 1101 DTSTART;TZID=America/New_York:20200315T150000Z 1102 DTEND;TZID=America/New_York:20200315T163000Z 1103 LAST-MODIFIED:20200216T145739Z 1104 SUMMARY:Beethoven Piano Sonatas 1105 UID:123456 1106 IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:h 1107 ttp://example.com/images/concert.png 1108 BEGIN:PARTICIPANT 1109 PARTICIPANT-TYPE:SPONSOR 1110 UID:dG9tQGZvb2Jhci5xlLmNvbQ 1111 STRUCTURED-DATA;VALUE=URI:http://example.com/sponsor.vcf 1112 END:PARTICIPANT 1113 BEGIN:PARTICIPANT 1114 PARTICIPANT-TYPE:PERFORMER: 1115 UID:em9lQGZvb2GFtcGxlLmNvbQ 1116 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/johndoe.vcf 1117 END:PARTICIPANT 1118 BEGIN:VLOCATION 1119 UID:123456-abcdef-98765432 1120 NAME:The venue 1121 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/venues/big-hall.vcf 1122 END:VLOCATION 1123 BEGIN:VLOCATION 1124 UID:123456-abcdef-87654321 1125 NAME:Parking for the venue 1126 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/venues/parking.vcf 1127 END:VLOCATION 1128 END:VEVENT 1130 8.2. Example 2 1132 The following is an example of a VEVENT describing a meeting. One of 1133 the attendees is a remote participant. 1135 BEGIN:VEVENT 1136 CREATED:20200215T145739Z 1137 DTSTAMP:20200215T145739Z 1138 DTSTART;TZID=America/New_York:20200315T150000Z 1139 DTEND;TZID=America/New_York:20200315T163000Z 1140 LAST-MODIFIED:20200216T145739Z 1141 SUMMARY:Conference planning 1142 UID:123456 1143 ORGANIZER:mailto:a@example.com 1144 ATTENDEE;PARTSTAT=ACCEPTED;CN=A:mailto:a@example.com 1145 ATTENDEE;RSVP=TRUE;CN=B:mailto:b@example.com 1146 BEGIN:PARTICIPANT 1147 PARTICIPANT-TYPE:ACTIVE: 1148 UID:v39lQGZvb2GFtcGxlLmNvbQ 1149 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/b.vcf 1150 LOCATION:At home 1151 END:PARTICIPANT 1152 END:VEVENT 1154 9. Security Considerations 1156 This specification extends [RFC5545] and makes further use of 1157 possibly linked data. While calendar data is not unique in this 1158 regard it is worth reminding implementors of some of the dangers and 1159 safeguards. 1161 9.1. URIs 1163 See [RFC3986] for a discussion of the security considerations 1164 relating to URIs. Because of the issues discussed there and below, 1165 clients SHOULD NOT follow URIs and fetch content automatically, and 1166 should only do so at the explicit request of the user. 1168 Fetching remote resources carries inherent risks. Connections must 1169 only be allowed on well known ports, using allowed protocols 1170 (generally just HTTP/HTTPS on their default ports). The URL must be 1171 resolved externally and not allowed to access internal resources. 1172 Connecting to an external source reveals IP (and therefore generally 1173 location) information. 1175 A maliciously constructed iCalendar object may contain a very large 1176 number of URIs. In the case of published calendars with a large 1177 number of subscribers, such objects could be widely distributed. 1178 Implementations should be careful to limit the automatic fetching of 1179 linked resources to reduce the risk of this being an amplification 1180 vector for a denial-of-service attack. 1182 9.2. Malicious Content 1184 For the "STRUCTURED-DATA" property, agents need to be aware that a 1185 client could attack underlying storage by sending extremely large 1186 values and could attack processing time by uploading a recurring 1187 event with a large number of overrides and then repeatedly adding, 1188 updating and deleting structured data. 1190 Agents should set reasonable limits on storage size and number of 1191 instances and apply those constraints. Calendar protocols should 1192 ensure there is a way to report on such limits being exceeded. 1194 Malicious content could be introduced into the calendar server by way 1195 of the "STRUCTURED-DATA" property and propagated to many end users 1196 via scheduling. Servers SHOULD check this property for malicious or 1197 inappropriate content. Upon detecting such content, servers SHOULD 1198 remove the property, 1200 9.3. HTML Content 1202 When processing HTML content, applications need to be aware of the 1203 many security and privacy issues, as described in the IANA 1204 considerations section of [W3C.REC-html51-20171003] 1206 10. Privacy Considerations 1208 10.1. Tracking 1210 Properties with a "URI" value type can expose their users to privacy 1211 leaks as any network access of the URI data can be tracked both by a 1212 network observer and by the entity hosting the remote resource. 1213 Clients SHOULD NOT automatically download data referenced by the URI 1214 without explicit instruction from users. 1216 To help alleviate some of the concerns protocols and services could 1217 provide proxy services for downloading referenced data. 1219 10.2. Revealing Locations 1221 The addition of location information to the new participant component 1222 provides information about the location of participants at a given 1223 time. This information MUST NOT be distributed to other participants 1224 without those participant's express permission. Note that there may 1225 be a number of participants who may be unaware of their inclusion in 1226 the data. 1228 Agents processing and distributing calendar data must be aware that 1229 it has the property of providing information about a future time when 1230 a given individual may be at a particular location, which could 1231 enable targeted attacks against that individual. 1233 The same may be true of other information contained in the 1234 participant component. In general, revealing only as much as is 1235 absolutely necessary should be the approach taken. 1237 For example, there may be some privacy considerations relating to the 1238 ORDER parameter, as it provides an indication of the organizer's 1239 perception of the relative importance of other participants. 1241 11. IANA Considerations 1243 11.1. Additional iCalendar Registrations 1245 11.1.1. Properties 1247 This document defines the following new iCalendar properties to be 1248 added to the registry defined in Section 8.2.3 of [RFC5545]: 1250 +--------------------+---------+----------------------+ 1251 | Property | Status | Reference | 1252 +--------------------+---------+----------------------+ 1253 | CALENDAR-ADDRESS | Current | RFCXXXX, Section 6.4 | 1254 | LOCATION-TYPE | Current | RFCXXXX, Section 6.1 | 1255 | PARTICIPANT-TYPE | Current | RFCXXXX, Section 6.2 | 1256 | RESOURCE-TYPE | Current | RFCXXXX, Section 6.3 | 1257 | STRUCTURED-DATA | Current | RFCXXXX, Section 6.6 | 1258 | STYLED-DESCRIPTION | Current | RFCXXXX, Section 6.5 | 1259 +--------------------+---------+----------------------+ 1261 11.1.2. Parameters 1263 This document defines the following new iCalendar property parameters 1264 to be added to the registry defined in Section 8.2.4 of [RFC5545]: 1266 +--------------------+---------+----------------------+ 1267 | Property Parameter | Status | Reference | 1268 +--------------------+---------+----------------------+ 1269 | ORDER | Current | RFCXXXX, Section 5.1 | 1270 | SCHEMA | Current | RFCXXXX, Section 5.2 | 1271 | DERIVED | Current | RFCXXXX, Section 5.3 | 1272 +--------------------+---------+----------------------+ 1274 11.1.3. Components 1276 This document defines the following new iCalendar components to be 1277 added to the registry defined in Section 8.3.1 of [RFC5545]: 1279 +-------------+---------+----------------------+ 1280 | Component | Status | Reference | 1281 +-------------+---------+----------------------+ 1282 | PARTICIPANT | Current | RFCXXXX, Section 7.1 | 1283 | VLOCATION | Current | RFCXXXX, Section 7.2 | 1284 | VRESOURCE | Current | RFCXXXX, Section 7.3 | 1285 +-------------+---------+----------------------+ 1287 11.2. New Registration Tables 1289 This section defines new registration tables for PARTICIPANT-TYPE and 1290 RESOURCE-TYPE values. These tables are updated using the same 1291 approaches laid down in Section 8.2.1 of [RFC5545] 1293 This document creates new IANA registries for participant and 1294 resource types. IANA will maintain these registries and, following 1295 the policies outlined in [RFC8126], new tokens are assigned after 1296 Expert Review. The Expert Reviewer will generally consult the IETF 1297 GeoPRIV working group mailing list or its designated successor. 1298 Updates or deletions of tokens from the registration follow the same 1299 procedures. The expert review should be guided by a few common sense 1300 considerations. For example, tokens should not be specific to a 1301 country, region, organization, or company; they should be well- 1302 defined and widely recognized. The expert's support of IANA will 1303 include providing IANA with the new token(s) when the update is 1304 provided only in the form of a schema, and providing IANA with the 1305 new schema element(s) when the update is provided only in the form of 1306 a token. To ensure widespread usability across protocols, tokens 1307 MUST follow the character set restrictions for XML Names [3]. Each 1308 registration must include the name of the token and a brief 1309 description similar to the ones offered herein for the initial 1310 registrations contained this document: 1312 11.2.1. Participant Types 1314 The following table has been used to initialize the participant types 1315 registry. 1317 +-------------------+---------+----------------------+ 1318 | Participant Type | Status | Reference | 1319 +-------------------+---------+----------------------+ 1320 | ACTIVE | Current | RFCXXXX, Section 6.2 | 1321 | INACTIVE | Current | RFCXXXX, Section 6.2 | 1322 | SPONSOR | Current | RFCXXXX, Section 6.2 | 1323 | CONTACT | Current | RFCXXXX, Section 6.2 | 1324 | BOOKING-CONTACT | Current | RFCXXXX, Section 6.2 | 1325 | EMERGENCY-CONTACT | Current | RFCXXXX, Section 6.2 | 1326 | PUBLICITY-CONTACT | Current | RFCXXXX, Section 6.2 | 1327 | PLANNER-CONTACT | Current | RFCXXXX, Section 6.2 | 1328 | PERFORMER | Current | RFCXXXX, Section 6.2 | 1329 | SPEAKER | Current | RFCXXXX, Section 6.2 | 1330 +-------------------+---------+----------------------+ 1332 11.2.2. Resource Types 1334 The following table has been used to initialize the resource types 1335 registry. 1337 +-------------------------+---------+----------------------+ 1338 | Resource Type | Status | Reference | 1339 +-------------------------+---------+----------------------+ 1340 | PROJECTOR | Current | RFCXXXX, Section 6.3 | 1341 | ROOM | Current | RFCXXXX, Section 6.3 | 1342 | REMOTE-CONFERENCE-AUDIO | Current | RFCXXXX, Section 6.3 | 1343 | REMOTE-CONFERENCE-VIDEO | Current | RFCXXXX, Section 6.3 | 1344 +-------------------------+---------+----------------------+ 1346 12. Acknowledgements 1348 The author would like to thank Chuck Norris of eventful.com for his 1349 work which led to the development of this RFC. 1351 The author would also like to thank the members of CalConnect, The 1352 Calendaring and Scheduling Consortium, the Event Publication 1353 technical committee and the following individuals for contributing 1354 their ideas and support: 1356 Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis. 1358 13. Normative References 1360 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1361 Requirement Levels", BCP 14, RFC 2119, 1362 DOI 10.17487/RFC2119, March 1997, 1363 . 1365 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 1366 RFC 2426, DOI 10.17487/RFC2426, September 1998, 1367 . 1369 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1370 Resource Identifier (URI): Generic Syntax", STD 66, 1371 RFC 3986, DOI 10.17487/RFC3986, January 2005, 1372 . 1374 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types 1375 Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, 1376 . 1378 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 1379 Scheduling Core Object Specification (iCalendar)", 1380 RFC 5545, DOI 10.17487/RFC5545, September 2009, 1381 . 1383 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 1384 Interoperability Protocol (iTIP)", RFC 5546, 1385 DOI 10.17487/RFC5546, December 2009, 1386 . 1388 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 1389 DOI 10.17487/RFC7986, October 2016, 1390 . 1392 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1393 Writing an IANA Considerations Section in RFCs", BCP 26, 1394 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1395 . 1397 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1398 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1399 May 2017, . 1401 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1402 Interchange Format", STD 90, RFC 8259, 1403 DOI 10.17487/RFC8259, December 2017, 1404 . 1406 [W3C.REC-html51-20171003] 1407 Faulkner, S., Eicholz, A., Leithead, T., and A. Danilo, 1408 "HTML 5.1 2nd Edition", World Wide Web Consortium 1409 Recommendation REC-html51-20171003, October 2017, 1410 . 1412 [W3C.REC-xml-20081126] 1413 Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and 1414 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 1415 Edition)", World Wide Web Consortium Recommendation REC- 1416 xml-20081126, November 2008, 1417 . 1419 Appendix A. Open issues 1421 None at the moment 1423 Appendix B. Change log 1425 To be deleted on publication 1427 calext-v19 2021-03-25 MD 1429 o Revert ABNF to RFC5545 format. 1431 o Add missing DERIVED parameter registration. 1433 o Fix small error in an example (missing space at start). 1435 calext-v18 2021-??-?? MD 1437 o Fix incorrect participant type property name in PARTICIPANT. 1439 o Allow parameters on LOCATION-TYPE. 1441 calext-v17 2021-01-03 MD 1443 o Remove STRUCTURED-LOCATION property, add VLOCATION component. 1445 o Remove STRUCTURED-RESOURCE property, add VRESOURCE component. 1447 o Make LOCATION-TYPE multi-valued property for location. 1449 o Make RESOURCE-TYPE multi-valued property for resource. 1451 o Tidy up abnf. 1453 calext-v16 2019-10-09 MD 1455 o Make LOCTYPE multi-valued. 1457 o Add all ATTENDEE scheduling parameters to CALENDAR-ADDRESS. 1459 calext-v15 2019-10-08 MD 1460 o Address various DICUSS points. 1462 calext-v14 2019-06-11 MD 1464 o Definition of event and social calendaring. 1466 o Remove redefinition of SOURCE - use STRUCTURED-DATA. 1468 calext-v13 2019-05-26 MD 1470 o Respond to various issues. 1472 calext-v12 2019-02-28 MD 1474 o Fix styled-description example. Respond to various AD issues. 1475 Some typos. 1477 calext-v11 2019-02-27 MD 1479 o Add DERIVED parameter for styled-description, RELATED parameter 1480 for structured-location 1482 calext-v09 2018-08-30 MD 1484 o Sorted out inconsistencies in refs to 5546 1486 calext-v08 2018-07-06 MD 1488 o Add some text for equal ORDER values 1490 o Switched scheduleaddress to calendaraddress in participant abnf. 1491 Also added more properties 1493 o Fixed PARTICIPANT abnf 1495 calext-v04 2017-10-11 MD 1497 o Change SCHEDULE-ADDRESS to CALENDAR-ADDRESS 1499 o Explicitly broaden scope of SOURCE 1501 o Add initial registry for RESTYPE and move new tables into separate 1502 section. 1504 o Fix PARTTYPE/PARTICIPANT-TYPE inconsistency 1506 calext-v03 2017-10-09 MD 1507 o Mostly typographical and other minor changes 1509 calext-v02 2017-04-20 MD 1511 o Add SCHEDULE-ADDRESS property 1513 o PARTICIPANT becomes a component rather than a property. Turn many 1514 of the former parameters into properties. 1516 o Use existing ATTENDEE property for scheduling. 1518 calext-v01 2017-02-18 MD 1520 o Change ASSOCIATE back to PARTICIPANT 1522 o PARTICIPANT becomes a component rather than a property. Turn many 1523 of the former parameters into properties. 1525 calext-v00 2016-08-?? MD 1527 o Name changed - taken up by calext working group 1529 v06 2016-06-26 MD 1531 o Fix up abnf 1533 o change ref to ietf from daboo 1535 o take out label spec - use Cyrus spec 1537 v05 2016-06-14 MD 1539 o Remove GROUP and HASH. they can be dealt with elsewhere if desired 1541 o Change ORDER to integer >= 1. 1543 o Incorporate Structured-Data into this specification. 1545 v04 2014-02-01 MD 1547 o Added updates attribute. 1549 o Minor typos. 1551 o Resubmitted mostly to refresh the draft. 1553 v03 2013-03-06 MD 1554 o Replace PARTICIPANT with ASSOCIATE plus related changes. 1556 o Added section showing modifications to components. 1558 o Replace ID with GROUP and modify HASH. 1560 o Replace TITLE param with LABEL. 1562 o Fixed STYLED-DESCRIPTION in various ways, correct example. 1564 v02 2012-11-02 MD 1566 o Collapse sections with description of properties and the use cases 1567 into a section with sub-sections. 1569 o New section to describe relating properties. 1571 o Remove idref and upgrade hash to have the reference 1573 o No default value types on properties.. 1575 v01 2012-10-18 MD Many changes. 1577 o SPONSOR and STRUCTURED-CONTACT are now in PARTICIPANT 1579 o Add a STRUCTURED-RESOURCE property 1581 o STYLED-DESCRIPTION to handle rich text 1583 o Much more... 1585 2011-01-07 1587 o Remove MEDIA - it's going in the Cyrus RFC 1589 o Rename EXTENDED-... to STRUCTURED-... 1591 o Add TYPE parameter to SPONSOR 1593 v00 2007-10-19 MD Initial version 1595 Author's Address 1596 Michael Douglass 1597 Bedework 1598 226 3rd Street 1599 Troy, NY 12180 1600 USA 1602 Email: mdouglass@bedework.com 1603 URI: http://bedework.com