idnits 2.17.1 draft-ietf-calext-eventpub-extensions-18.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 (January 13, 2021) is 1199 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 1290 ** 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) January 13, 2021 5 Intended status: Standards Track 6 Expires: July 17, 2021 8 Event Publishing Extensions to iCalendar 9 draft-ietf-calext-eventpub-extensions-18 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 July 17, 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 . . . . . . . . . . . . . . . . . . . . . . . 18 77 7.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 18 78 7.1.1. Schedulable Participant . . . . . . . . . . . . . . . 22 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 . . . . . . . . . . . . . . . . . . . 27 85 9.1. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 27 86 9.2. Malicious Content . . . . . . . . . . . . . . . . . . . . 28 87 9.3. HTML Content . . . . . . . . . . . . . . . . . . . . . . 28 88 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 28 89 10.1. Tracking . . . . . . . . . . . . . . . . . . . . . . . . 28 90 10.2. Revealing Locations . . . . . . . . . . . . . . . . . . 28 91 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 92 11.1. Additional iCalendar Registrations . . . . . . . . . . . 29 93 11.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 29 94 11.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 29 95 11.1.3. Components . . . . . . . . . . . . . . . . . . . . . 30 96 11.2. New Registration Tables . . . . . . . . . . . . . . . . 30 97 11.2.1. Participant Types . . . . . . . . . . . . . . . . . 30 98 11.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 31 99 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 100 13. Normative References . . . . . . . . . . . . . . . . . . . . 31 101 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 33 102 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 33 103 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 36 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 = ; the elements herein may appear in any order, 678 ; and the order is not significant. 680 (";" "VALUE" "=" ("URI" / "TEXT")) 682 [";" altrepparam] 683 [";" languageparam] 684 [";" fmttypeparam] 685 [";" derivedparam] 687 *(";" other-param) 689 styleddescval = ( uri / text ) 690 ;Value MUST match value type 692 Example: 694 The following is an example of this property. It points to an html 695 description. 697 STYLED-DESCRIPTION;VALUE=URI:http://example.org/desc001.html 699 6.6. Structured-Data 701 Property Name: STRUCTURED-DATA 703 Purpose: This property specifies ancillary data associated with the 704 calendar component. 706 Value Type: There is no default value type for this property. The 707 value type can be set to TEXT, BINARY or URI 709 Property Parameters: IANA-registered, non-standard, inline encoding 710 and value data type property parameters can be specified on this 711 property. The format type and schema parameters can be specified 712 on this property and MUST be present for text or inline binary 713 encoded content information. 715 Conformance: This property can be specified multiple times in an 716 iCalendar object. Typically it would be used in "VEVENT", "VTODO" 717 or "VJOURNAL" calendar components. 719 Description: The existing properties in iCalendar cover key elements 720 of events and tasks such as start time, end time, location, 721 summary, etc. However, different types of events often have other 722 specific "fields" that it is useful to include in the calendar 723 data. For example, an event representing an airline flight could 724 include the airline, flight number, departure and arrival airport 725 codes, check-in and gate-closing times etc. As another example, a 726 sporting event might contain information about the type of sport, 727 the home and away teams, the league the teams are in, information 728 about nearby parking, etc. 730 This property is used to specify ancillary data in some structured 731 format either directly (inline) as a "TEXT" or "BINARY" value or 732 as a link via a "URI" value. 734 Rather than define new iCalendar properties for the variety of 735 event types that might occur, it would be better to leverage 736 existing schemas for such data. For example, schemas available at 737 https://schema.org include different event types. By using 738 standard schemas, interoperability can be improved between 739 calendar clients and non-calendaring systems that wish to generate 740 or process the data. 742 This property allows the direct inclusion of ancillary data whose 743 schema is defined elsewhere. This property also includes 744 parameters to clearly identify the type of the schema being used 745 so that clients can quickly and easily spot what is relevant 746 within the calendar data and present that to users or process it 747 within the calendaring system. 749 iCalendar does support an "ATTACH" property which can be used to 750 include documents or links to documents within the calendar data. 751 However, that property does not allow data to be included as a 752 "TEXT" value (a feature that "STRUCTURED-DATA" does allow), plus 753 attachments are often treated as "opaque" data to be processed by 754 some other system rather than the calendar client. Thus the 755 existing "ATTACH" property is not sufficient to cover the specific 756 needs of inclusion of schema data. Extending the "ATTACH" 757 property to support a new value type would likely cause 758 interoperability problems. Additionally some implementations 759 manage attachments by stripping them out and replacing with a link 760 to the resource. Thus a new property to support inclusion of 761 schema data is warranted. 763 Format Definition: 765 This property is defined by the following notation: 767 sdataprop = "STRUCTURED-DATA" sdataparam ":" 768 sdataval CRLF 770 sdataparam = ; all parameter elements may appear in any order, 771 ; and the order is not significant. 772 (sdataparamtext / sdataparambin / sdataparamuri) 773 *(";" other-param) 775 sdataparamtext = ";VALUE=TEXT" 776 ";" fmttypeparam 777 ";" schemaparam 779 sdataparambin = ";VALUE=BINARY" 780 ";ENCODING=BASE64" 781 ";" fmttypeparam 782 ";" schemaparam 784 sdataparamuri = ";VALUE=URI" 785 [";" fmttypeparam] 786 [";" schemaparam] 788 sdataval = ( binary / text /uri ) 789 ; value MUST match value type 791 Example: The following is an example of this property: 793 STRUCTURED-DATA;FMTTYPE=application/ld+json; 794 SCHEMA="https://schema.org/SportsEvent"; 795 VALUE=TEXT:{\n 796 "@context": "http://schema.org"\,\n 797 "@type": "SportsEvent"\,\n 798 "homeTeam": "Pittsburgh Pirates"\,\n 799 "awayTeam": "San Francisco Giants"\n 800 }\n 802 7. New Components 804 7.1. Participant 806 Component name: PARTICIPANT 808 Purpose: This component provides information about a participant in 809 an event or task. 811 Conformance: This component can be specified multiple times in a 812 "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar component. 814 Description: This component provides information about a participant 815 in a calendar component. A participant may be an attendee in a 816 scheduling sense and the ATTENDEE property may be specified in 817 addition. Participants can be individuals or organizations, for 818 example a soccer team, the spectators or the musicians. 820 STRUCTURED-DATA properties if present may refer to definitions of 821 the participant - such as a vCard. 823 The CALENDAR-ADDRESS property if present will provide a cal- 824 address. If an ATTENDEE property has the same value the 825 participant is considered schedulable. The PARTICIPANT component 826 can be used to contain additional meta-data related to the 827 attendee. 829 Format Definition: 831 This component is defined by the following notation: 833 participantc = "BEGIN" ":" "PARTICIPANT" CRLF 834 partprop *locationc *resourcec 835 "END" ":" "PARTICIPANT" CRLF 837 partprop = ; the elements herein may appear in any order, 838 ; and the order is not significant. 840 uid 841 participanttype 843 [calendaraddress] 844 [created] 845 [description] 846 [dtstamp] 847 [geo] 848 [last-mod] 849 [priority] 850 [seq] 851 [status] 852 [summary] 853 [url] 855 *attach 856 *categories 857 *comment 858 *contact 859 *location 860 *rstatus 861 *related 862 *resources 863 *strucloc 864 *strucres 865 *styleddescription 866 *sdataprop 867 *iana-prop 869 Note: When the PRIORITY is supplied it defines the ordering of 870 PARTICIPANT components with the same value for the PARTICIPANT- 871 TYPE property. 873 Privacy Issues: When a LOCATION is supplied it provides information 874 about the location of a participant at a given time or times. 875 This may represent an unacceptable privacy risk for some 876 participants. User agents MUST NOT broadcast this information 877 without the participant's express permission. For further 878 comments see Section 10 880 Example: 882 The following is an example of this component. It contains a 883 STRUCTURED-DATA property which points to a vCard providing 884 information about the event participant. 886 BEGIN:PARTICIPANT 887 UID: em9lQGZvb2GFtcGxlLmNvbQ 888 PARTICIPANT-TYPE:PERFORMER 889 STRUCTURED-DATA;VALUE=URI: 890 http://dir.example.com/vcard/aviolinist.vcf 891 END:PARTICIPANT 893 Example: 895 The following is an example for the primary contact. 897 BEGIN:PARTICIPANT 898 UID: em9lQGZvb2GFtcGxlLmNvbQ 899 STRUCTURED-DATA;VALUE=URI; 900 http://dir.example.com/vcard/contacts/contact1.vcf 901 PARTICIPANT-TYPE:CONTACT 902 DESCRIPTION:A contact 903 END:PARTICIPANT 905 Example: 907 The following is an example for a participant with contact and 908 location. 910 BEGIN:PARTICIPANT 911 UID: em9lQGZvb2GFtcGxlLmNdrt 912 STRUCTURED-DATA;VALUE=URI; 913 http://dir.example.com/vcard/contacts/my-card.vcf 914 PARTICIPANT-TYPE:SPEAKER 915 DESCRIPTION:A participant 916 BEGIN:VLOCATION 917 UID:123456-abcdef-98765432 918 NAME:My home location 919 STRUCTURED-DATA;VALUE=URI: 920 http://dir.example.com/addresses/my-home.vcf 921 END:VLOCATION 922 END:PARTICIPANT 924 7.1.1. Schedulable Participant 926 A PARTICIPANT component may represent someone or something that needs 927 to be scheduled as defined for ATTENDEE in [RFC5545] and [RFC5546]. 928 The PARTICIPANT component may also represent someone or something 929 that is NOT to receive scheduling messages. 931 For backwards compatibility wuth existing clients and servers when 932 used to schedule events and tasks the ATTENDEE property MUST be used 933 to specify the sheduling parameters as defined for that property. 935 For other, future uses the CALENDAR-ADDRESS property MUST be used to 936 specify those parameters. 938 A PARTICIPANT component is defined to be schedulable if 940 o It contains a CALENDAR-ADDRESS property 942 o That property value is the same as the value for an ATTENDEE 943 property. 945 If both of these conditions apply then the participant defined by the 946 value of the URL property will take part in scheduling operations as 947 defined in [RFC5546]. 949 An appropriate use for the PARTICIPANT component in scheduling would 950 be to store SEQUENCE and DTSTAMP properties associated with replies 951 from each ATTENDEE. A LOCATION property within the PARTICIPANT 952 component might allow better selection of meeting times when 953 participants are in different timezones. 955 7.2. Location 957 Component name: VLOCATION 959 Purpose: This component provides rich information about the location 960 of an event using the structured data property or optionally a 961 plain text typed value. 963 Conformance: This component can be specified multiple times in a 964 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY" or "PARTICIPANT" 965 calendar component. 967 Description: There may be a number of locations associated with an 968 event. This component provides detailed information about a 969 location. 971 When used in a component the value of this property provides 972 information about the event venue or of related services such as 973 parking, dining, stations etc.. 975 STRUCTURED-DATA properties if present may refer to representations 976 of the location - such as a vCard. 978 Format Definition: 980 This component is defined by the following notation: 982 locationc = "BEGIN" ":" "VLOCATION" CRLF 983 locprop 984 "END" ":" "VLOCATION" CRLF 986 locprop = ; the elements herein may appear in any order, 987 ; and the order is not significant. 989 uid 991 [name] 992 [description] 993 [geo] 994 [loctype] 996 *sdataprop 997 *iana-prop 999 The NAME property is defined in [RFC7986] 1001 Example: 1003 The following is an example of this component. It points to a venue. 1005 BEGIN:VLOCATION 1006 UID:123456-abcdef-98765432 1007 NAME:The venue 1008 STRUCTURED-DATA;VALUE=URI: 1009 http://dir.example.com/venues/big-hall.vcf 1010 END:VLOCATION 1012 7.3. Resource 1014 Component name: VRESOURCE 1016 Purpose: This component provides a typed reference to external 1017 information about a resource or optionally a plain text typed 1018 value. Typically a resource is anything that might be required or 1019 used by a calendar entity and possibly has a directory entry. 1021 Conformance: This component can be specified multiple times in a 1022 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY" or "PARTICIPANT" 1023 calendar component. 1025 Description: When used in a component this component provides 1026 information about resources used for the event such as rooms, 1027 projectors, conferencing capabilities. 1029 The RESOURCE-TYPE value registry provides a place in which 1030 resource types may be registered. 1032 STRUCTURED-DATA properties if present may refer to representations 1033 of the resource - such as a vCard. 1035 Format Definition: 1037 This component is defined by the following notation: 1039 resourcec = "BEGIN" ":" "VRESOURCE" CRLF 1040 resprop 1041 "END" ":" "VRESOURCE" CRLF 1043 resprop = ; the elements herein may appear in any order, 1044 ; and the order is not significant. 1046 uid 1048 [name] 1049 [description] 1050 [geo] 1051 [restype] 1053 *sdataprop 1054 *iana-prop 1056 The NAME property is defined in [RFC7986] 1058 Example: 1060 The following is an example of this component. It refers to a 1061 projector. 1063 BEGIN:VRESOURCE 1064 UID:456789-abcdef-98765432 1065 NAME:The projector 1066 RESOURCE-TYPE:projector 1067 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/projectors/3d.vcf 1068 END:VRESOURCE 1070 8. Extended examples 1072 The following are some examples of the use of the properties defined 1073 in this specification. They include additional properties defined in 1074 [RFC7986] which includes IMAGE. 1076 8.1. Example 1 1077 The following is an example of a VEVENT describing a concert. It 1078 includes location information for the venue itself as well as 1079 references to parking and restaurants. 1081 BEGIN:VEVENT 1082 CREATED:20200215T145739Z 1083 DESCRIPTION: Piano Sonata No 3\n 1084 Piano Sonata No 30 1085 DTSTAMP:20200215T145739Z 1086 DTSTART;TZID=America/New_York:20200315T150000Z 1087 DTEND;TZID=America/New_York:20200315T163000Z 1088 LAST-MODIFIED:20200216T145739Z 1089 SUMMARY:Beethoven Piano Sonatas 1090 UID:123456 1091 IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:h 1092 ttp://example.com/images/concert.png 1093 BEGIN:PARTICIPANT 1094 PARTICIPANT-TYPE:SPONSOR 1095 UID:dG9tQGZvb2Jhci5xlLmNvbQ 1096 STRUCTURED-DATA;VALUE=URI:http://example.com/sponsor.vcf 1097 END:PARTICIPANT 1098 BEGIN:PARTICIPANT 1099 PARTICIPANT-TYPE:PERFORMER: 1100 UID:em9lQGZvb2GFtcGxlLmNvbQ 1101 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/johndoe.vcf 1102 END:PARTICIPANT 1103 BEGIN:VLOCATION 1104 UID:123456-abcdef-98765432 1105 NAME:The venue 1106 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/venues/big-hall.vcf 1107 END:VLOCATION 1108 BEGIN:VLOCATION 1109 UID:123456-abcdef-87654321 1110 NAME:Parking for the venue 1111 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/venues/parking.vcf 1112 END:VLOCATION 1113 END:VEVENT 1115 8.2. Example 2 1116 The following is an example of a VEVENT describing a meeting. One of 1117 the attendees is a remote participant. 1119 BEGIN:VEVENT 1120 CREATED:20200215T145739Z 1121 DTSTAMP:20200215T145739Z 1122 DTSTART;TZID=America/New_York:20200315T150000Z 1123 DTEND;TZID=America/New_York:20200315T163000Z 1124 LAST-MODIFIED:20200216T145739Z 1125 SUMMARY:Conference planning 1126 UID:123456 1127 ORGANIZER:mailto:a@example.com 1128 ATTENDEE;PARTSTAT=ACCEPTED;CN=A:mailto:a@example.com 1129 ATTENDEE;RSVP=TRUE;CN=B:mailto:b@example.com 1130 BEGIN:PARTICIPANT 1131 PARTICIPANT-TYPE:ACTIVE: 1132 UID:v39lQGZvb2GFtcGxlLmNvbQ 1133 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/b.vcf 1134 LOCATION:At home 1135 END:PARTICIPANT 1136 END:VEVENT 1138 9. Security Considerations 1140 This specification extends [RFC5545] and makes further use of 1141 possibly linked data. While calendar data is not unique in this 1142 regard it is worth reminding implementors of some of the dangers and 1143 safeguards. 1145 9.1. URIs 1147 See [RFC3986] for a discussion of the security considerations 1148 relating to URIs. Because of the issues discussed there and below, 1149 clients SHOULD NOT follow URIs and fetch content automatically, and 1150 should only do so at the explicit request of the user. 1152 Fetching remote resources carries inherent risks. Connections must 1153 only be allowed on well known ports, using allowed protocols 1154 (generally just HTTP/HTTPS on their default ports). The URL must be 1155 resolved externally and not allowed to access internal resources. 1156 Connecting to an external source reveals IP (and therefore generally 1157 location) information. 1159 A maliciously constructed iCalendar object may contain a very large 1160 number of URIs. In the case of published calendars with a large 1161 number of subscribers, such objects could be widely distributed. 1162 Implementations should be careful to limit the automatic fetching of 1163 linked resources to reduce the risk of this being an amplification 1164 vector for a denial-of-service attack. 1166 9.2. Malicious Content 1168 For the "STRUCTURED-DATA" property, agents need to be aware that a 1169 client could attack underlying storage by sending extremely large 1170 values and could attack processing time by uploading a recurring 1171 event with a large number of overrides and then repeatedly adding, 1172 updating and deleting structured data. 1174 Agents should set reasonable limits on storage size and number of 1175 instances and apply those constraints. Calendar protocols should 1176 ensure there is a way to report on such limits being exceeded. 1178 Malicious content could be introduced into the calendar server by way 1179 of the "STRUCTURED-DATA" property and propagated to many end users 1180 via scheduling. Servers SHOULD check this property for malicious or 1181 inappropriate content. Upon detecting such content, servers SHOULD 1182 remove the property, 1184 9.3. HTML Content 1186 When processing HTML content, applications need to be aware of the 1187 many security and privacy issues, as described in the IANA 1188 considerations section of [W3C.REC-html51-20171003] 1190 10. Privacy Considerations 1192 10.1. Tracking 1194 Properties with a "URI" value type can expose their users to privacy 1195 leaks as any network access of the URI data can be tracked both by a 1196 network observer and by the entity hosting the remote resource. 1197 Clients SHOULD NOT automatically download data referenced by the URI 1198 without explicit instruction from users. 1200 To help alleviate some of the concerns protocols and services could 1201 provide proxy services for downloading referenced data. 1203 10.2. Revealing Locations 1205 The addition of location information to the new participant component 1206 provides information about the location of participants at a given 1207 time. This information MUST NOT be distributed to other participants 1208 without those participant's express permission. Note that there may 1209 be a number of participants who may be unaware of their inclusion in 1210 the data. 1212 Agents processing and distributing calendar data must be aware that 1213 it has the property of providing information about a future time when 1214 a given individual may be at a particular location, which could 1215 enable targeted attacks against that individual. 1217 The same may be true of other information contained in the 1218 participant component. In general, revealing only as much as is 1219 absolutely necessary should be the approach taken. 1221 For example, there may be some privacy considerations relating to the 1222 ORDER parameter, as it provides an indication of the organizer's 1223 perception of the relative importance of other participants. 1225 11. IANA Considerations 1227 11.1. Additional iCalendar Registrations 1229 11.1.1. Properties 1231 This document defines the following new iCalendar properties to be 1232 added to the registry defined in Section 8.2.3 of [RFC5545]: 1234 +--------------------+---------+----------------------+ 1235 | Property | Status | Reference | 1236 +--------------------+---------+----------------------+ 1237 | CALENDAR-ADDRESS | Current | RFCXXXX, Section 6.4 | 1238 | LOCATION-TYPE | Current | RFCXXXX, Section 6.1 | 1239 | PARTICIPANT-TYPE | Current | RFCXXXX, Section 6.2 | 1240 | RESOURCE-TYPE | Current | RFCXXXX, Section 6.3 | 1241 | STRUCTURED-DATA | Current | RFCXXXX, Section 6.6 | 1242 | STYLED-DESCRIPTION | Current | RFCXXXX, Section 6.5 | 1243 +--------------------+---------+----------------------+ 1245 11.1.2. Parameters 1247 This document defines the following new iCalendar property parameters 1248 to be added to the registry defined in Section 8.2.4 of [RFC5545]: 1250 +--------------------+---------+----------------------+ 1251 | Property Parameter | Status | Reference | 1252 +--------------------+---------+----------------------+ 1253 | ORDER | Current | RFCXXXX, Section 5.1 | 1254 | SCHEMA | Current | RFCXXXX, Section 5.2 | 1255 +--------------------+---------+----------------------+ 1257 11.1.3. Components 1259 This document defines the following new iCalendar components to be 1260 added to the registry defined in Section 8.3.1 of [RFC5545]: 1262 +-------------+---------+----------------------+ 1263 | Component | Status | Reference | 1264 +-------------+---------+----------------------+ 1265 | PARTICIPANT | Current | RFCXXXX, Section 7.1 | 1266 | VLOCATION | Current | RFCXXXX, Section 7.2 | 1267 | VRESOURCE | Current | RFCXXXX, Section 7.3 | 1268 +-------------+---------+----------------------+ 1270 11.2. New Registration Tables 1272 This section defines new registration tables for PARTICIPANT-TYPE and 1273 RESOURCE-TYPE values. These tables are updated using the same 1274 approaches laid down in Section 8.2.1 of [RFC5545] 1276 This document creates new IANA registries for participant and 1277 resource types. IANA will maintain these registries and, following 1278 the policies outlined in [RFC8126], new tokens are assigned after 1279 Expert Review. The Expert Reviewer will generally consult the IETF 1280 GeoPRIV working group mailing list or its designated successor. 1281 Updates or deletions of tokens from the registration follow the same 1282 procedures. The expert review should be guided by a few common sense 1283 considerations. For example, tokens should not be specific to a 1284 country, region, organization, or company; they should be well- 1285 defined and widely recognized. The expert's support of IANA will 1286 include providing IANA with the new token(s) when the update is 1287 provided only in the form of a schema, and providing IANA with the 1288 new schema element(s) when the update is provided only in the form of 1289 a token. To ensure widespread usability across protocols, tokens 1290 MUST follow the character set restrictions for XML Names [3]. Each 1291 registration must include the name of the token and a brief 1292 description similar to the ones offered herein for the initial 1293 registrations contained this document: 1295 11.2.1. Participant Types 1297 The following table has been used to initialize the participant types 1298 registry. 1300 +-------------------+---------+----------------------+ 1301 | Participant Type | Status | Reference | 1302 +-------------------+---------+----------------------+ 1303 | ACTIVE | Current | RFCXXXX, Section 6.2 | 1304 | INACTIVE | Current | RFCXXXX, Section 6.2 | 1305 | SPONSOR | Current | RFCXXXX, Section 6.2 | 1306 | CONTACT | Current | RFCXXXX, Section 6.2 | 1307 | BOOKING-CONTACT | Current | RFCXXXX, Section 6.2 | 1308 | EMERGENCY-CONTACT | Current | RFCXXXX, Section 6.2 | 1309 | PUBLICITY-CONTACT | Current | RFCXXXX, Section 6.2 | 1310 | PLANNER-CONTACT | Current | RFCXXXX, Section 6.2 | 1311 | PERFORMER | Current | RFCXXXX, Section 6.2 | 1312 | SPEAKER | Current | RFCXXXX, Section 6.2 | 1313 +-------------------+---------+----------------------+ 1315 11.2.2. Resource Types 1317 The following table has been used to initialize the resource types 1318 registry. 1320 +-------------------------+---------+----------------------+ 1321 | Resource Type | Status | Reference | 1322 +-------------------------+---------+----------------------+ 1323 | PROJECTOR | Current | RFCXXXX, Section 6.3 | 1324 | ROOM | Current | RFCXXXX, Section 6.3 | 1325 | REMOTE-CONFERENCE-AUDIO | Current | RFCXXXX, Section 6.3 | 1326 | REMOTE-CONFERENCE-VIDEO | Current | RFCXXXX, Section 6.3 | 1327 +-------------------------+---------+----------------------+ 1329 12. Acknowledgements 1331 The author would like to thank Chuck Norris of eventful.com for his 1332 work which led to the development of this RFC. 1334 The author would also like to thank the members of CalConnect, The 1335 Calendaring and Scheduling Consortium, the Event Publication 1336 technical committee and the following individuals for contributing 1337 their ideas and support: 1339 Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis. 1341 13. Normative References 1343 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1344 Requirement Levels", BCP 14, RFC 2119, 1345 DOI 10.17487/RFC2119, March 1997, 1346 . 1348 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 1349 RFC 2426, DOI 10.17487/RFC2426, September 1998, 1350 . 1352 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1353 Resource Identifier (URI): Generic Syntax", STD 66, 1354 RFC 3986, DOI 10.17487/RFC3986, January 2005, 1355 . 1357 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types 1358 Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, 1359 . 1361 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 1362 Scheduling Core Object Specification (iCalendar)", 1363 RFC 5545, DOI 10.17487/RFC5545, September 2009, 1364 . 1366 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 1367 Interoperability Protocol (iTIP)", RFC 5546, 1368 DOI 10.17487/RFC5546, December 2009, 1369 . 1371 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 1372 DOI 10.17487/RFC7986, October 2016, 1373 . 1375 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1376 Writing an IANA Considerations Section in RFCs", BCP 26, 1377 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1378 . 1380 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1381 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1382 May 2017, . 1384 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1385 Interchange Format", STD 90, RFC 8259, 1386 DOI 10.17487/RFC8259, December 2017, 1387 . 1389 [W3C.REC-html51-20171003] 1390 Faulkner, S., Eicholz, A., Leithead, T., and A. Danilo, 1391 "HTML 5.1 2nd Edition", World Wide Web Consortium 1392 Recommendation REC-html51-20171003, October 2017, 1393 . 1395 [W3C.REC-xml-20081126] 1396 Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and 1397 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 1398 Edition)", World Wide Web Consortium Recommendation REC- 1399 xml-20081126, November 2008, 1400 . 1402 Appendix A. Open issues 1404 None at the moment 1406 Appendix B. Change log 1408 To be deleted on publication 1410 calext-v18 2021-??-?? MD 1412 o Fix incorrect participant type property name in PARTICIPANT. 1414 o Allow parameters on LOCATION-TYPE. 1416 calext-v17 2021-01-03 MD 1418 o Remove STRUCTURED-LOCATION property, add VLOCATION component. 1420 o Remove STRUCTURED-RESOURCE property, add VRESOURCE component. 1422 o Make LOCATION-TYPE multi-valued property for location. 1424 o Make RESOURCE-TYPE multi-valued property for resource. 1426 o Tidy up abnf. 1428 calext-v16 2019-10-09 MD 1430 o Make LOCTYPE multi-valued. 1432 o Add all ATTENDEE scheduling parameters to CALENDAR-ADDRESS. 1434 calext-v15 2019-10-08 MD 1436 o Address various DICUSS points. 1438 calext-v14 2019-06-11 MD 1440 o Definition of event and social calendaring. 1442 o Remove redefinition of SOURCE - use STRUCTURED-DATA. 1444 calext-v13 2019-05-26 MD 1446 o Respond to various issues. 1448 calext-v12 2019-02-28 MD 1450 o Fix styled-description example. Respond to various AD issues. 1451 Some typos. 1453 calext-v11 2019-02-27 MD 1455 o Add DERIVED parameter for styled-description, RELATED parameter 1456 for structured-location 1458 calext-v09 2018-08-30 MD 1460 o Sorted out inconsistencies in refs to 5546 1462 calext-v08 2018-07-06 MD 1464 o Add some text for equal ORDER values 1466 o Switched scheduleaddress to calendaraddress in participant abnf. 1467 Also added more properties 1469 o Fixed PARTICIPANT abnf 1471 calext-v04 2017-10-11 MD 1473 o Change SCHEDULE-ADDRESS to CALENDAR-ADDRESS 1475 o Explicitly broaden scope of SOURCE 1477 o Add initial registry for RESTYPE and move new tables into separate 1478 section. 1480 o Fix PARTTYPE/PARTICIPANT-TYPE inconsistency 1482 calext-v03 2017-10-09 MD 1484 o Mostly typographical and other minor changes 1486 calext-v02 2017-04-20 MD 1488 o Add SCHEDULE-ADDRESS property 1490 o PARTICIPANT becomes a component rather than a property. Turn many 1491 of the former parameters into properties. 1493 o Use existing ATTENDEE property for scheduling. 1495 calext-v01 2017-02-18 MD 1497 o Change ASSOCIATE back to PARTICIPANT 1499 o PARTICIPANT becomes a component rather than a property. Turn many 1500 of the former parameters into properties. 1502 calext-v00 2016-08-?? MD 1504 o Name changed - taken up by calext working group 1506 v06 2016-06-26 MD 1508 o Fix up abnf 1510 o change ref to ietf from daboo 1512 o take out label spec - use Cyrus spec 1514 v05 2016-06-14 MD 1516 o Remove GROUP and HASH. they can be dealt with elsewhere if desired 1518 o Change ORDER to integer >= 1. 1520 o Incorporate Structured-Data into this specification. 1522 v04 2014-02-01 MD 1524 o Added updates attribute. 1526 o Minor typos. 1528 o Resubmitted mostly to refresh the draft. 1530 v03 2013-03-06 MD 1532 o Replace PARTICIPANT with ASSOCIATE plus related changes. 1534 o Added section showing modifications to components. 1536 o Replace ID with GROUP and modify HASH. 1538 o Replace TITLE param with LABEL. 1540 o Fixed STYLED-DESCRIPTION in various ways, correct example. 1542 v02 2012-11-02 MD 1544 o Collapse sections with description of properties and the use cases 1545 into a section with sub-sections. 1547 o New section to describe relating properties. 1549 o Remove idref and upgrade hash to have the reference 1551 o No default value types on properties.. 1553 v01 2012-10-18 MD Many changes. 1555 o SPONSOR and STRUCTURED-CONTACT are now in PARTICIPANT 1557 o Add a STRUCTURED-RESOURCE property 1559 o STYLED-DESCRIPTION to handle rich text 1561 o Much more... 1563 2011-01-07 1565 o Remove MEDIA - it's going in the Cyrus RFC 1567 o Rename EXTENDED-... to STRUCTURED-... 1569 o Add TYPE parameter to SPONSOR 1571 v00 2007-10-19 MD Initial version 1573 Author's Address 1575 Michael Douglass 1576 Bedework 1577 226 3rd Street 1578 Troy, NY 12180 1579 USA 1581 Email: mdouglass@bedework.com 1582 URI: http://bedework.com