idnits 2.17.1 draft-daboo-icalendar-extensions-02.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 date (October 24, 2010) is 4933 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) -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Daboo 3 Internet-Draft Apple Inc. 4 Intended status: Standards Track October 24, 2010 5 Expires: April 27, 2011 7 New Properties for iCalendar 8 draft-daboo-icalendar-extensions-02 10 Abstract 12 This document defines a set of new properties for iCalendar data. 14 Status of this Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on April 27, 2011. 31 Copyright Notice 33 Copyright (c) 2010 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 50 3. Modifications to Calendar Components . . . . . . . . . . . . . 3 51 4. Calendar Properties . . . . . . . . . . . . . . . . . . . . . 4 52 4.1. CALENDAR-NAME Property . . . . . . . . . . . . . . . . . . 5 53 4.2. CALENDAR-DESCRIPTION Property . . . . . . . . . . . . . . 6 54 4.3. CALENDAR-UID Property . . . . . . . . . . . . . . . . . . 7 55 4.4. CALENDAR-URL Property . . . . . . . . . . . . . . . . . . 7 56 4.5. CALENDAR-TZID Property . . . . . . . . . . . . . . . . . . 8 57 4.6. CALENDAR-REFRESH-INTERVAL Property . . . . . . . . . . . . 9 58 4.7. CALENDAR-COLOR Property . . . . . . . . . . . . . . . . . 10 59 4.8. CALENDAR-IMAGE Property . . . . . . . . . . . . . . . . . 10 60 5. Component Properties . . . . . . . . . . . . . . . . . . . . . 12 61 5.1. IMAGE Property . . . . . . . . . . . . . . . . . . . . . . 12 62 5.2. CONFERENCE Property . . . . . . . . . . . . . . . . . . . 14 63 6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16 64 6.1. DISPLAY Property Parameter . . . . . . . . . . . . . . . . 16 65 6.2. INFO Property Parameter . . . . . . . . . . . . . . . . . 16 66 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 67 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 68 8.1. Property Registrations . . . . . . . . . . . . . . . . . . 17 69 8.2. Parameter Registrations . . . . . . . . . . . . . . . . . 18 70 8.3. Display Types Registry . . . . . . . . . . . . . . . . . . 18 71 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 72 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 73 10.1. Normative References . . . . . . . . . . . . . . . . . . . 18 74 10.2. Informative References . . . . . . . . . . . . . . . . . . 19 75 Appendix A. Change History (To be removed by RFC Editor 76 before publication) . . . . . . . . . . . . . . . . . 19 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 79 1. Introduction 81 The iCalendar [RFC5545] data format is used to represent calendar 82 data and is used with iTIP [RFC5546] to handle scheduling operations 83 between calendar users. iCalendar is in widespread use, and in 84 accordance with provisions in that specification, extension elements 85 have been added by various vendors to the data format in order to 86 support and enhance capabilities. This specification collects a 87 number of these ad-hoc extensions and uses the new IANA registry 88 capability defined in [RFC5545] to register standard variants with 89 clearly defined definitions and semantics. In addition, some new 90 elements are introduced for features that vendors have recently been 91 requesting. 93 2. Conventions Used in This Document 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 97 "OPTIONAL" in this document are to be interpreted as described in 98 [RFC2119]. 100 The notation used in this memo is the ABNF notation of [RFC5234] as 101 used by iCalendar [RFC5545]. Any syntax elements shown below that 102 are not explicitly defined in this specification come from iCalendar 103 [RFC5545]. 105 3. Modifications to Calendar Components 107 The following changes to the syntax defined in iCalendar [RFC5545] 108 are made here. New elements are defined in subsequent sections. 110 calprops /= *( 111 ; 112 ; The following are OPTIONAL, 113 ; but MUST NOT occur more than once. 114 ; 115 caluid / calurl / caltzid / 116 calrefresh / calcolor / 117 ; 118 ; The following are OPTIONAL, 119 ; and MAY occur more than once. 120 ; 121 calname / caldescription / calimg 122 ; 123 ) 125 eventprop /= *( 126 ; 127 ; The following are OPTIONAL, 128 ; and MAY occur more than once. 129 ; 130 image, conference 131 ; 132 ) 134 todoprop /= *( 135 ; 136 ; The following are OPTIONAL, 137 ; and MAY occur more than once. 138 ; 139 image, conference 140 ; 141 ) 143 jourprop /= *( 144 ; 145 ; The following are OPTIONAL, 146 ; and MAY occur more than once. 147 ; 148 image 149 ; 150 ) 152 4. Calendar Properties 153 4.1. CALENDAR-NAME Property 155 Property Name: CALENDAR-NAME 157 Purpose: This property specifies the name of the calendar. 159 Value Type: TEXT 161 Property Parameters: IANA, non-standard, alternate text 162 representation, and language property parameters can be specified 163 on this property. 165 Conformance: This property can be specified multiple times in an 166 iCalendar object. However, each property MUST represent the name 167 of the calendar in a different language. 169 Description: This property is used to specify a name (a short, one- 170 line description) of the iCalendar object that can be used by 171 calendar user agents when presenting the calendar data to a user. 172 Whilst a calendar only has a single name, multiple language 173 variants can be specified by including this property multiple 174 times with different "LANGUAGE" parameter values on each. 176 Format Definition: This property is defined by the following 177 notation: 179 calname = "CALENDAR-NAME" calnameparam ":" text CRLF 181 calnameparam = *( 182 ; 183 ; The following are OPTIONAL, 184 ; but MUST NOT occur more than once. 185 ; 186 (";" altrepparam) / (";" languageparam) / 187 ; 188 ; The following is OPTIONAL, 189 ; and MAY occur more than once. 190 ; 191 (";" other-param) 192 ; 193 ) 195 Example: The following is an example of this property: 197 CALENDAR-NAME:Company Vacation Days 199 4.2. CALENDAR-DESCRIPTION Property 201 Property Name: CALENDAR-DESCRIPTION 203 Purpose: This property specifies the description of the calendar. 205 Value Type: TEXT 207 Property Parameters: IANA, non-standard, alternate text 208 representation, and language property parameters can be specified 209 on this property. 211 Conformance: This property can be specified multiple times in an 212 iCalendar object. However, each property MUST represent the 213 description of the calendar in a different language. 215 Description: This property is used to specify a lengthy textual 216 description of the iCalendar object that can be used by calendar 217 user agents when describing the nature of the calendar data to a 218 user. Whilst a calendar only has a single description, multiple 219 language variants can be specified by including this property 220 multiple times with different "LANGUAGE" parameter values on each. 222 Format Definition: This property is defined by the following 223 notation: 225 caldesc = "CALENDAR-DESCRIPTION" caldescparam ":" text 226 CRLF 228 caldescparam = *( 229 ; 230 ; The following are OPTIONAL, 231 ; but MUST NOT occur more than once. 232 ; 233 (";" altrepparam) / (";" languageparam) / 234 ; 235 ; The following is OPTIONAL, 236 ; and MAY occur more than once. 237 ; 238 (";" other-param) 239 ; 240 ) 242 Example: The following is an example of this property: 244 CALENDAR-DESCRIPTION:This calendar contains all the \ 245 official vacation days of our company.\nThese repre\ 246 sent paid time-off - make sure you have fun, we'll \ 247 be working you hard on the other days! 249 4.3. CALENDAR-UID Property 251 Property Name: CALENDAR-UID 253 Purpose: This property specifies the persistent, globally unique 254 identifier for the calendar. 256 Value Type: TEXT 258 Property Parameters: IANA and non-standard property parameters can 259 be specified on this property. 261 Conformance: This property can be specified once in an iCalendar 262 object. 264 Description: The value of this property MUST be a globally unique 265 identifier. The generator of the property MUST guarantee that the 266 value is unique. This can be done following the recommendations 267 in Section 3.8.4.7 of [RFC5545]. Implementations MUST be able to 268 receive and persist values of at least 255 octets for this 269 property, but they MUST NOT truncate values in the middle of a 270 UTF-8 multi-octet sequence. 272 Format Definition: This property is defined by the following 273 notation: 275 caluid = "CALENDAR-UID" caluidparam ":" text CRLF 277 caluidparam = *(";" other-param) 279 Example: The following is an example of this property: 281 CALENDAR-UID:19960401T080045Z-4000F192713-0052@example.com 283 4.4. CALENDAR-URL Property 285 Property Name: CALENDAR-URL 287 Purpose: This property specifies a URL from where the calendar data 288 was retrieved or where it can be refreshed. 290 Value Type: URI 291 Property Parameters: IANA and non-standard property parameters can 292 be specified on this property. 294 Conformance: This property can be specified once in an iCalendar 295 object. 297 Description: This property specifies a URL identifying the source of 298 the calendar data and a location from where updates can be 299 retrieved. 301 Format Definition: This property is defined by the following 302 notation: 304 calurl = "CALENDAR-URL" calurlparam ":" uri CRLF 306 calurlparam = *(";" other-param) 308 Example: The following is an example of this property: 310 CALENDAR-URL:http://calendars.example.com/holidays/canada.ics 312 4.5. CALENDAR-TZID Property 314 Property Name: CALENDAR-TZID 316 Purpose: This property specifies the default time zone identifier 317 for the calendar. 319 Value Type: TEXT 321 Property Parameters: IANA and non-standard property parameters can 322 be specified on this property. 324 Conformance: This property can be specified once in an iCalendar 325 object. 327 Description: This property specifies a time zone identifier that 328 represents the default timezone for which floating time or all-day 329 events in the iCalendar object can be assumed to be relative to. 330 It can also be used to choose an initial time zone for use when 331 creating new components in the iCalendar object. A "VTIMEZONE" 332 component having a "TZID" property matching the value specified in 333 this property MUST be present in the iCalendar object. 335 Format Definition: This property is defined by the following 336 notation: 338 caltzid = "CALENDAR-TZID" caltzidparam ":" [tzidprefix] 339 text CRLF 341 caltzidparam = *(";" other-param) 343 Example: The following is an example of this property: 345 CALENDAR-TZID:America/New_York 347 4.6. CALENDAR-REFRESH-INTERVAL Property 349 Property Name: CALENDAR-REFRESH-INTERVAL 351 Purpose: This property specifies a suggested minimum interval for 352 polling for changes of the calendar data from the original source 353 of that data. 355 Value Type: DURATION 357 Property Parameters: IANA and non-standard property parameters can 358 be specified on this property. 360 Conformance: This property can be specified once in an iCalendar 361 object. 363 Description: This property specifies a positive duration that gives 364 a suggested minimum polling interval for checking for updates to 365 the calendar data. The value of this property SHOULD be used by 366 calendar user agents to limit the polling interval for calendar 367 data updates to the minimum interval specified. 369 Format Definition: This property is defined by the following 370 notation: 372 calrefesh = "CALENDAR-REFRESH-INTERVAL" calrefreshparam 373 ":" dur-value CRLF 374 ;consisting of a positive duration of time. 376 calrefeshparam = *(";" other-param) 378 Example: The following is an example of this property: 380 CALENDAR-REFRESH-INTERVAL:P1W 382 4.7. CALENDAR-COLOR Property 384 Property Name: CALENDAR-COLOR 386 Purpose: This property specifies a color used for displaying the 387 calendar data. 389 Value Type: INTEGER. The value MUST be three SEMICOLON-separated 390 INTEGER values. 392 Property Parameters: IANA and non-standard property parameters can 393 be specified on this property. 395 Conformance: This property can be specified once in an iCalendar 396 object. 398 Description: This property specifies a color that client MAY use 399 when presenting the calendar data to a user. Typically this would 400 appear as the "background" color of events or tasks. The value 401 MUST be an RGB value with integer value components in the range 402 0..255 404 Format Definition: This property is defined by the following 405 notation: 407 calcolor = "CALENDAR-COLOR" calcolorparam ":" 408 calcolorvalue CRLF 410 calcolorparam = *(";" other-param) 412 calcolorvalue = integer ";" integer ";" integer 413 ; Red, green, and blue values in the range 414 ; 0 - 255. 416 Example: The following is an example of this property: 418 CALENDAR-COLOR:255;0;255 420 4.8. CALENDAR-IMAGE Property 422 Property Name: CALENDAR-IMAGE 424 Purpose: This property specifies an image associated with the 425 calendar. 427 Value Type: The default value type for this property is URI. The 428 value type can also be set to BINARY to indicate inline binary 429 encoded content information. The value MUST refer to or be data 430 with a media type of "image". 432 Property Parameters: IANA, non-standard, display, inline encoding, 433 and value data type property parameters can be specified on this 434 property. The format type parameter can be specified on this 435 property and is RECOMMENDED for inline binary encoded content 436 information. 438 Conformance: This property can be specified multiple times in an 439 iCalendar object. 441 Description: This property specifies an image for an iCalendar 442 object via a uri or directly with inline data that can be used by 443 calendar user agents when presenting the calendar data to a user. 444 Multiple properties MAY be used to specify alternative sets of 445 images with, for example, varying media subtypes, resolutions or 446 sizes. When multiple properties are present, calendar user agents 447 SHOULD display only one of them, picking one that provides the 448 most appropriate image quality, or display none. The "DISPLAY" 449 parameter is used to indicate the intended display mode for the 450 image. 452 Format Definition: This property is defined by the following 453 notation: 455 calimg = "CALENDAR-IMAGE" calimgparam ( ":" uri ) / 456 ( 457 ";" "ENCODING" "=" "BASE64" 458 ";" "VALUE" "=" "BINARY" 459 ":" binary 460 ) 461 CRLF 463 calimgparam = *( 464 ; 465 ; The following is OPTIONAL for a URI value, 466 ; RECOMMENDED for a BINARY value, 467 ; and MUST NOT occur more than once. 468 ; 469 (";" fmttypeparam) / 470 ; 471 ; The following is OPTIONAL, 472 ; and MOST NOT occur more than once. 473 ; 474 (";" displayparam) / 475 ; 476 ; The following is OPTIONAL, 477 ; and MAY occur more than once. 478 ; 479 (";" other-param) 480 ; 481 ) 483 Example: The following is an example of this property: 485 CALENDAR-IMAGE;DISPLAY=BADGE;FMTTYPE=image/png:http://ex 486 ample.com/images/holiday.png 488 5. Component Properties 490 5.1. IMAGE Property 492 Property Name: IMAGE 494 Purpose: This property specifies an image associated with a calendar 495 component. 497 Value Type: The default value type for this property is URI. The 498 value type can also be set to BINARY to indicate inline binary 499 encoded content information. The value MUST refer to or be data 500 with a media type of "image". 502 Property Parameters: IANA, non-standard, display, inline encoding, 503 and value data type property parameters can be specified on this 504 property. The format type parameter can be specified on this 505 property and is RECOMMENDED for inline binary encoded content 506 information. 508 Conformance: This property can be specified multiple times in a 509 "VEVENT", "VTODO", or "VJOURNAL" calendar component. 511 Description: This property specifies an image for a calendar 512 component via a uri or directly with inline data that can be used 513 by calendar user agents when presenting the calendar data to a 514 user. Multiple properties MAY be used to specify alternative sets 515 of images with, for example, varying media subtypes, resolutions 516 or sizes. When multiple properties are present, calendar user 517 agents SHOULD display only one of them, picking one that provides 518 the most appropriate image quality, or display none. The 519 "DISPLAY" parameter is used to indicate the intended display mode 520 for the image. 522 Format Definition: This property is defined by the following 523 notation: 525 image = "IMAGE" imageparam ( ":" uri ) / 526 ( 527 ";" "ENCODING" "=" "BASE64" 528 ";" "VALUE" "=" "BINARY" 529 ":" binary 530 ) 531 CRLF 533 imageparam = *( 534 ; 535 ; The following is OPTIONAL for a URI value, 536 ; RECOMMENDED for a BINARY value, 537 ; and MUST NOT occur more than once. 538 ; 539 (";" fmttypeparam) / 540 ; 541 ; The following is OPTIONAL, 542 ; and MOST NOT occur more than once. 543 ; 544 (";" displayparam) / 545 ; 546 ; The following is OPTIONAL, 547 ; and MAY occur more than once. 548 ; 549 (";" other-param) 550 ; 551 ) 553 Example: The following is an example of this property: 555 IMAGE;DISPLAY=BACKGROUND;FMTTYPE=image/png:htt 556 p://example.com/images/party.png 558 5.2. CONFERENCE Property 560 Property Name: CONFERENCE 562 Purpose: This property specifies information for accessing a 563 conferencing system. 565 Value Type: URI. 567 Property Parameters: IANA, non-standard, information, and language 568 property parameters can be specified on this property. 570 Conformance: This property can be specified multiple times in a 571 "VEVENT" or "VTODO" calendar component. 573 Description: This property specifies information for accessing a 574 conferencing system for attendees of a meeting or to-do. This 575 might be a tel: URI [RFC3496] for a telephone-based conference 576 number dial-in (with access codes included), or it might be an 577 http: URI [RFC2616] for a web-based video chat, or a URI for an 578 instant messaging group chat room. If a specific URI for a 579 conferencing system is not available, a data: URI [RFC2397] 580 containing a text description can be used. 582 The "INFO" property paramater is used to convey additional details 583 on the use of the URI. For example, the URIs or access codes for 584 the moderator and attendee of a teleconference system could be 585 different, and the "INFO" property parameter could be used to 586 "tag" each "CONFERENCE" property to indicate which is which. 588 The "LANGUAGE" property parameter is used to indicate the language 589 associated with the property, and in particular any "INFO" 590 property parameter. 592 Format Definition: This property is defined by the following 593 notation: 595 conference = "CONFERENCE" confparam ":" uri CRLF 597 confparam = *( 598 ; 599 ; The following are OPTIONAL, 600 ; and MOST NOT occur more than once. 601 ; 602 (";" infoparam) / (";" languageparam) / 603 ; 604 ; The following is OPTIONAL, 605 ; and MAY occur more than once. 606 ; 607 (";" other-param) 608 ; 609 ) 611 Example: The following are examples of this property: 613 CONFERENCE;INFO=Moderator dial-in;:tel:+1-412- 614 555-0123,,,654321 615 CONFERENCE;INFO=Attendee dial-in;:tel:+1-412-5 616 55-0123,,,555123 617 CONFERENCE;INFO=Chat room:xmpp:chat-123@confer 618 ence.example.com 620 6. Property Parameters 622 6.1. DISPLAY Property Parameter 624 Parameter Name: DISPLAY 626 Purpose: To specify different ways in which an image for a calendar 627 or component can be displayed. 629 Format Definition: This property parameter is defined by the 630 following notation: 632 displayparam = "DISPLAY" "=" 633 ("BADGE" / ; A small "badge" image 634 "BACKGROUND" / ; Use as a background image 635 "OVERLAY" / ; Use as an overlay image 636 "BANNER" / ; Use as a "banner" across the top 637 x-name / ; Experimental type 638 iana-token) ; Other IANA registered type 639 ; 640 ; Default is BADGE 642 Description: This property parameter MAY be specified on "CALENDAR- 643 IMAGE" or "IMAGE" properties. In the absence of this parameter, 644 the value "BADGE" MUST be used for the default behavior. The 645 value determines how a client ought to present an image supplied 646 in iCalendar data to the user. 648 Values for this parameter are registered with IANA as per 649 Section 8.3. New values can be added to this registry following 650 the procedure outlined in Section 8.2.1 of [RFC5545]. 652 Servers and clients MUST handle x-name and iana-token values they 653 don't recognize by not displaying any image at all. 655 Example: 657 IMAGE;DISPLAY=BANNER;FMTTYPE=image/png:htt 658 p://example.com/images/weather-cloudy.png 660 6.2. INFO Property Parameter 661 Parameter Name: INFO 663 Purpose: To specify descriptive text about a property. 665 Format Definition: This property parameter is defined by the 666 following notation: 668 infoparam = "INFO" "=" paramtext 670 Description: This property parameter MAY be specified on 671 "CONFERENCE" properties. 673 Example: 675 CONFERENCE;INFO="Web video chat, access code=7654 676 3";:http://video-chat.example.com/;group-id=1234 678 7. Security Considerations 680 TODO:Perhaps discuss issues with image processing related buffer 681 overflows, accessing external URLs (privacy), etc. 683 8. IANA Considerations 685 8.1. Property Registrations 687 This document defines the following new iCalendar properties to be 688 added to the registry defined in Section 8.2.3 of [RFC5545]: 690 +---------------------------+---------+----------------------+ 691 | Property | Status | Reference | 692 +---------------------------+---------+----------------------+ 693 | CALENDAR-NAME | Current | RFCXXXX, Section 4.1 | 694 | CALENDAR-DESCRIPTION | Current | RFCXXXX, Section 4.2 | 695 | CALENDAR-UID | Current | RFCXXXX, Section 4.3 | 696 | CALENDAR-URL | Current | RFCXXXX, Section 4.4 | 697 | CALENDAR-TZID | Current | RFCXXXX, Section 4.5 | 698 | CALENDAR-REFRESH-INTERVAL | Current | RFCXXXX, Section 4.6 | 699 | CALENDAR-COLOR | Current | RFCXXXX, Section 4.7 | 700 | CALENDAR-IMAGE | Current | RFCXXXX, Section 4.8 | 701 | IMAGE | Current | RFCXXXX, Section 5.1 | 702 | CONFERENCE | Current | RFCXXXX, Section 5.2 | 703 +---------------------------+---------+----------------------+ 705 8.2. Parameter Registrations 707 This document defines the following new iCalendar property parameters 708 to be added to the registry defined in Section 8.2.4 of [RFC5545]: 710 +--------------------+---------+----------------------+ 711 | Property Parameter | Status | Reference | 712 +--------------------+---------+----------------------+ 713 | DISPLAY | Current | RFCXXXX, Section 6.1 | 714 | INFO | Current | RFCXXXX, Section 6.2 | 715 +--------------------+---------+----------------------+ 717 8.3. Display Types Registry 719 This document defines the following new iCalendar value registry as 720 per Section 8.2.6 of [RFC5545]: 722 +--------------+---------+----------------------+ 723 | Display Type | Status | Reference | 724 +--------------+---------+----------------------+ 725 | BADGE | Current | RFCXXXX, Section 6.1 | 726 | BACKGROUND | Current | RFCXXXX, Section 6.1 | 727 | OVERLAY | Current | RFCXXXX, Section 6.1 | 728 | BANNER | Current | RFCXXXX, Section 6.1 | 729 +--------------+---------+----------------------+ 731 9. Acknowledgments 733 This specification came about via discussions at the Calendaring and 734 Scheduling Consortium. 736 10. References 738 10.1. Normative References 740 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 741 Requirement Levels", BCP 14, RFC 2119, March 1997. 743 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 744 Specifications: ABNF", STD 68, RFC 5234, January 2008. 746 [RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling 747 Core Object Specification (iCalendar)", RFC 5545, 748 September 2009. 750 10.2. Informative References 752 [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, 753 August 1998. 755 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 756 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 757 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 759 [RFC3496] Malis, A. and T. Hsiao, "Protocol Extension for Support of 760 Asynchronous Transfer Mode (ATM) Service Class-aware 761 Multiprotocol Label Switching (MPLS) Traffic Engineering", 762 RFC 3496, March 2003. 764 [RFC5546] Daboo, C., "iCalendar Transport-Independent 765 Interoperability Protocol (iTIP)", RFC 5546, 766 December 2009. 768 Appendix A. Change History (To be removed by RFC Editor before 769 publication) 771 Changes in -02: 773 1. Minor wording changes. 775 2. Interval is now described as the "minimum interval". 777 3. Added CONFERENCE property and INFO parameter. 779 Changes in -01: 781 1. Fixed DISPLAY parameter handling of x- and iana tokens to state 782 that clients ignore the image if the token is not recognized. 784 2. Allow language variants for CALENDAR-NAME and CALENDAR- 785 DESCRIPTION. 787 3. Added registry for DISPLAY values. 789 Author's Address 791 Cyrus Daboo 792 Apple Inc. 793 1 Infinite Loop 794 Cupertino, CA 95014 795 USA 797 Email: cyrus@daboo.name 798 URI: http://www.apple.com/