draft-ietf-calsify-rfc2445bis-08.txt   draft-ietf-calsify-rfc2445bis-09.txt 
Network Working Group B. Desruisseaux, Ed. Network Working Group B. Desruisseaux, Ed.
Internet-Draft Oracle Internet-Draft Oracle
Obsoletes: 2445 (if approved) February 6, 2008 Obsoletes: 2445 (if approved) October 31, 2008
Intended status: Standards Track Intended status: Standards Track
Expires: August 9, 2008 Expires: May 4, 2009
Internet Calendaring and Scheduling Core Object Specification Internet Calendaring and Scheduling Core Object Specification
(iCalendar) (iCalendar)
draft-ietf-calsify-rfc2445bis-08 draft-ietf-calsify-rfc2445bis-09
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 9, 2008. This Internet-Draft will expire on May 4, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines the iCalendar data format for representing and This document defines the iCalendar data format for representing and
exchanging calendaring and scheduling information such as events, to- exchanging calendaring and scheduling information such as events, to-
dos, journal entries and free/busy information, independent of any dos, journal entries and free/busy information, independent of any
particular calendar service or protocol. particular calendar service or protocol.
Editorial Note (To be removed by RFC Editor prior to publication) Editorial Note (To be removed by RFC Editor prior to publication)
This document is a product of the Calendaring and Scheduling This document is a product of the Calendaring and Scheduling
Standards Simplification (Calsify) working group of the Internet Standards Simplification (Calsify) working group of the Internet
Engineering Task Force. Comments on this draft are welcomed, and Engineering Task Force. Comments on this draft are welcomed, and
should be addressed to the ietf-calsify@osafoundation.org [1] mailing should be addressed to the ietf-calsify@osafoundation.org [1] mailing
list. list.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7
2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 7 2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 8
2.1. Formatting Conventions . . . . . . . . . . . . . . . . . 7 2.1. Formatting Conventions . . . . . . . . . . . . . . . . . 8
2.2. Related Memos . . . . . . . . . . . . . . . . . . . . . . 8 2.2. Related Memos . . . . . . . . . . . . . . . . . . . . . . 9
3. iCalendar Object Specification . . . . . . . . . . . . . . . 9 3. iCalendar Object Specification . . . . . . . . . . . . . . . 10
3.1. Content Lines . . . . . . . . . . . . . . . . . . . . . . 9 3.1. Content Lines . . . . . . . . . . . . . . . . . . . . . . 10
3.1.1. List and Field Separators . . . . . . . . . . . . . . 11 3.1.1. List and Field Separators . . . . . . . . . . . . . . 12
3.1.2. Multiple Values . . . . . . . . . . . . . . . . . . . 12 3.1.2. Multiple Values . . . . . . . . . . . . . . . . . . . 13
3.1.3. Binary Content . . . . . . . . . . . . . . . . . . . 12 3.1.3. Binary Content . . . . . . . . . . . . . . . . . . . 13
3.1.4. Character Set . . . . . . . . . . . . . . . . . . . . 13 3.1.4. Character Set . . . . . . . . . . . . . . . . . . . . 14
3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 13 3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 14
3.2.1. Alternate Text Representation . . . . . . . . . . . . 14 3.2.1. Alternate Text Representation . . . . . . . . . . . . 15
3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 15 3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 16
3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 16 3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 17
3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 16 3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 18
3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 17 3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 18
3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 18 3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 19
3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 18 3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 19
3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 19 3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 20
3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 19 3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 20
3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 20 3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 21
3.2.11. Group or List Membership . . . . . . . . . . . . . . 21 3.2.11. Group or List Membership . . . . . . . . . . . . . . 22
3.2.12. Participation Status . . . . . . . . . . . . . . . . 21 3.2.12. Participation Status . . . . . . . . . . . . . . . . 23
3.2.13. Recurrence Identifier Range . . . . . . . . . . . . . 24 3.2.13. Recurrence Identifier Range . . . . . . . . . . . . . 24
3.2.14. Alarm Trigger Relationship . . . . . . . . . . . . . 24 3.2.14. Alarm Trigger Relationship . . . . . . . . . . . . . 25
3.2.15. Relationship Type . . . . . . . . . . . . . . . . . . 25 3.2.15. Relationship Type . . . . . . . . . . . . . . . . . . 25
3.2.16. Participation Role . . . . . . . . . . . . . . . . . 26 3.2.16. Participation Role . . . . . . . . . . . . . . . . . 26
3.2.17. RSVP Expectation . . . . . . . . . . . . . . . . . . 27 3.2.17. RSVP Expectation . . . . . . . . . . . . . . . . . . 27
3.2.18. Sent By . . . . . . . . . . . . . . . . . . . . . . . 27 3.2.18. Sent By . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.19. Time Zone Identifier . . . . . . . . . . . . . . . . 28 3.2.19. Time Zone Identifier . . . . . . . . . . . . . . . . 28
3.2.20. Value Data Types . . . . . . . . . . . . . . . . . . 29 3.2.20. Value Data Types . . . . . . . . . . . . . . . . . . 29
3.3. Property Value Data Types . . . . . . . . . . . . . . . . 30 3.3. Property Value Data Types . . . . . . . . . . . . . . . . 30
3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 31 3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 31 3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 32 3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 32
3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 33 3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 33
3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 36 3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 36
3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 37 3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 37 3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 38 3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 38
3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 39 3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 39
3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 46 3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 48 3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 50 3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 50 3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 50
3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 51 3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 51
3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 52 3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 52
3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 52 3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 52
3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 53 3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 54
3.6.2. To-do Component . . . . . . . . . . . . . . . . . . . 57 3.6.2. To-do Component . . . . . . . . . . . . . . . . . . . 57
3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 59 3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 60
3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 61 3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 61
3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 64 3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 64
3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 73 3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 73
3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 78 3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 78
3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 78 3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 78
3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 79 3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 79
3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 80 3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 80
3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 81 3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 81
3.8. Component Properties . . . . . . . . . . . . . . . . . . 82 3.8. Component Properties . . . . . . . . . . . . . . . . . . 82
3.8.1. Descriptive Component Properties . . . . . . . . . . 82 3.8.1. Descriptive Component Properties . . . . . . . . . . 82
3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 82 3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 82
3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 83 3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 83
3.8.1.3. Classification . . . . . . . . . . . . . . . . . 84 3.8.1.3. Classification . . . . . . . . . . . . . . . . . 84
3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 85 3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 85
3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 87 3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 86
3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 88 3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 87
3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 89 3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 89
3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 91 3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 90
3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 91 3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 91
3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 93 3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 93
3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 94 3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 94
3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 96 3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 95
3.8.2. Date and Time Component Properties . . . . . . . . . 97 3.8.2. Date and Time Component Properties . . . . . . . . . 96
3.8.2.1. Date/Time Completed . . . . . . . . . . . . . . . 97 3.8.2.1. Date/Time Completed . . . . . . . . . . . . . . . 96
3.8.2.2. Date/Time End . . . . . . . . . . . . . . . . . . 97 3.8.2.2. Date/Time End . . . . . . . . . . . . . . . . . . 97
3.8.2.3. Date/Time Due . . . . . . . . . . . . . . . . . . 99 3.8.2.3. Date/Time Due . . . . . . . . . . . . . . . . . . 98
3.8.2.4. Date/Time Start . . . . . . . . . . . . . . . . . 100 3.8.2.4. Date/Time Start . . . . . . . . . . . . . . . . . 99
3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 101 3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 101
3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 102 3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 102
3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 103 3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 103
3.8.3. Time Zone Component Properties . . . . . . . . . . . 104 3.8.3. Time Zone Component Properties . . . . . . . . . . . 104
3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 104 3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 104
3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 106 3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 105
3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 107 3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 106
3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 107 3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 107
3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 108 3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 108
3.8.4. Relationship Component Properties . . . . . . . . . . 109 3.8.4. Relationship Component Properties . . . . . . . . . . 108
3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 109 3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 109
3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 112 3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 111
3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 113 3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 113
3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 115 3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 114
3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 117 3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 116
3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 119 3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 118
3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 120 3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 119
3.8.5. Recurrence Component Properties . . . . . . . . . . . 121 3.8.5. Recurrence Component Properties . . . . . . . . . . . 120
3.8.5.1. Exception Date/Times . . . . . . . . . . . . . . 121 3.8.5.1. Exception Date/Times . . . . . . . . . . . . . . 120
3.8.5.2. Recurrence Date/Times . . . . . . . . . . . . . . 123 3.8.5.2. Recurrence Date/Times . . . . . . . . . . . . . . 122
3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 125 3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 124
3.8.6. Alarm Component Properties . . . . . . . . . . . . . 135 3.8.6. Alarm Component Properties . . . . . . . . . . . . . 134
3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 135 3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 134
3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 136 3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 135
3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 136 3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 135
3.8.7. Change Management Component Properties . . . . . . . 139 3.8.7. Change Management Component Properties . . . . . . . 138
3.8.7.1. Date/Time Created . . . . . . . . . . . . . . . . 139 3.8.7.1. Date/Time Created . . . . . . . . . . . . . . . . 138
3.8.7.2. Date/Time Stamp . . . . . . . . . . . . . . . . . 140 3.8.7.2. Date/Time Stamp . . . . . . . . . . . . . . . . . 139
3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 141 3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 140
3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 142 3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 141
3.8.8. Miscellaneous Component Properties . . . . . . . . . 143 3.8.8. Miscellaneous Component Properties . . . . . . . . . 142
3.8.8.1. IANA Properties . . . . . . . . . . . . . . . . . 143 3.8.8.1. IANA Properties . . . . . . . . . . . . . . . . . 142
3.8.8.2. Non-standard Properties . . . . . . . . . . . . . 143 3.8.8.2. Non-standard Properties . . . . . . . . . . . . . 142
3.8.8.3. Request Status . . . . . . . . . . . . . . . . . 144 3.8.8.3. Request Status . . . . . . . . . . . . . . . . . 144
4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 148 4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 147
5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 152 5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 152
6. Internationalization Considerations . . . . . . . . . . . . . 153 6. Internationalization Considerations . . . . . . . . . . . . . 153
7. Security Considerations . . . . . . . . . . . . . . . . . . . 153 7. Security Considerations . . . . . . . . . . . . . . . . . . . 154
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 153 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 155
8.1. iCalendar Media Type Registration . . . . . . . . . . . . 154 8.1. iCalendar Media Type Registration . . . . . . . . . . . . 155
8.2. New iCalendar Elements Registration . . . . . . . . . . . 157 8.2. New iCalendar Elements Registration . . . . . . . . . . . 158
8.2.1. iCalendar Elements Registration Procedure . . . . . . 157 8.2.1. iCalendar Elements Registration Procedure . . . . . . 158
8.2.2. Registration Template for Components . . . . . . . . 157 8.2.2. Registration Template for Components . . . . . . . . 158
8.2.3. Registration Template for Properties . . . . . . . . 158 8.2.3. Registration Template for Properties . . . . . . . . 159
8.2.4. Registration Template for Parameters . . . . . . . . 158 8.2.4. Registration Template for Parameters . . . . . . . . 160
8.2.5. Registration Template for Value Data Types . . . . . 159 8.2.5. Registration Template for Value Data Types . . . . . 160
8.2.6. Registration Template for Values . . . . . . . . . . 159 8.2.6. Registration Template for Values . . . . . . . . . . 160
8.3. Initial iCalendar Elements Registries . . . . . . . . . . 160 8.3. Initial iCalendar Elements Registries . . . . . . . . . . 161
8.3.1. Components Registry . . . . . . . . . . . . . . . . . 160 8.3.1. Components Registry . . . . . . . . . . . . . . . . . 161
8.3.2. Properties Registry . . . . . . . . . . . . . . . . . 161 8.3.2. Properties Registry . . . . . . . . . . . . . . . . . 162
8.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 162 8.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 164
8.3.4. Value Data Types Registry . . . . . . . . . . . . . . 162 8.3.4. Value Data Types Registry . . . . . . . . . . . . . . 166
8.3.5. Calendar User Types Registry . . . . . . . . . . . . 163 8.3.5. Calendar User Types Registry . . . . . . . . . . . . 166
8.3.6. Free/Busy Time Types Registry . . . . . . . . . . . . 163 8.3.6. Free/Busy Time Types Registry . . . . . . . . . . . . 167
8.3.7. Participation Statuses Registry . . . . . . . . . . . 164 8.3.7. Participation Statuses Registry . . . . . . . . . . . 167
8.3.8. Relationship Types Registry . . . . . . . . . . . . . 164 8.3.8. Relationship Types Registry . . . . . . . . . . . . . 168
8.3.9. Participation Roles Registry . . . . . . . . . . . . 164 8.3.9. Participation Roles Registry . . . . . . . . . . . . 168
8.3.10. Actions Registry . . . . . . . . . . . . . . . . . . 165 8.3.10. Actions Registry . . . . . . . . . . . . . . . . . . 169
8.3.11. Classifications Registry . . . . . . . . . . . . . . 165 8.3.11. Classifications Registry . . . . . . . . . . . . . . 169
8.3.12. Methods Registry . . . . . . . . . . . . . . . . . . 165 8.3.12. Methods Registry . . . . . . . . . . . . . . . . . . 169
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 165 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 170
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 166 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 171
10.1. Normative References . . . . . . . . . . . . . . . . . . 166 10.1. Normative References . . . . . . . . . . . . . . . . . . 171
10.2. Informative References . . . . . . . . . . . . . . . . . 167 10.2. Informative References . . . . . . . . . . . . . . . . . 172
Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 168 Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 175
A.1. New restrictions . . . . . . . . . . . . . . . . . . . . 168 A.1. New restrictions . . . . . . . . . . . . . . . . . . . . 175
A.2. Restrictions removed . . . . . . . . . . . . . . . . . . 168 A.2. Restrictions removed . . . . . . . . . . . . . . . . . . 175
A.3. Deprecated features . . . . . . . . . . . . . . . . . . . 169 A.3. Deprecated features . . . . . . . . . . . . . . . . . . . 175
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 169 publication) . . . . . . . . . . . . . . . . . . . . 176
B.1. Changes in -08 . . . . . . . . . . . . . . . . . . . . . 169 B.1. Changes in -09 . . . . . . . . . . . . . . . . . . . . . 176
B.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . 170 B.2. Changes in -08 . . . . . . . . . . . . . . . . . . . . . 176
B.3. Changes in -06 . . . . . . . . . . . . . . . . . . . . . 171 B.3. Changes in -07 . . . . . . . . . . . . . . . . . . . . . 177
B.4. Changes in -05 . . . . . . . . . . . . . . . . . . . . . 173 B.4. Changes in -06 . . . . . . . . . . . . . . . . . . . . . 179
B.5. Changes in -04 . . . . . . . . . . . . . . . . . . . . . 173 B.5. Changes in -05 . . . . . . . . . . . . . . . . . . . . . 180
B.6. Changes in -03 . . . . . . . . . . . . . . . . . . . . . 175 B.6. Changes in -04 . . . . . . . . . . . . . . . . . . . . . 181
B.7. Changes in -02 . . . . . . . . . . . . . . . . . . . . . 175 B.7. Changes in -03 . . . . . . . . . . . . . . . . . . . . . 182
B.8. Changes in -01 . . . . . . . . . . . . . . . . . . . . . 176 B.8. Changes in -02 . . . . . . . . . . . . . . . . . . . . . 183
B.9. Changes in -01 . . . . . . . . . . . . . . . . . . . . . 183
1. Introduction 1. Introduction
The use of calendaring and scheduling has grown considerably in the The use of calendaring and scheduling has grown considerably in the
last decade. Enterprise and inter-enterprise business has become last decade. Enterprise and inter-enterprise business has become
dependent on rapid scheduling of events and actions using this dependent on rapid scheduling of events and actions using this
information technology. However, the longer term growth of information technology. This memo is intended to progress the level
calendaring and scheduling is currently limited by the lack of of interoperability possible between dissimilar calendaring and
Internet standards for the message content types that are central to scheduling applications. This memo defines a MIME content type for
these knowledgeware applications. This memo is intended to progress exchanging electronic calendaring and scheduling information. The
the level of interoperability possible between dissimilar calendaring Internet Calendaring and Scheduling Core Object Specification, or
and scheduling applications. This memo defines a MIME content type
for exchanging electronic calendaring and scheduling information.
The Internet Calendaring and Scheduling Core Object Specification, or
iCalendar, allows for the capture and exchange of information iCalendar, allows for the capture and exchange of information
normally stored within a calendaring and scheduling application; such normally stored within a calendaring and scheduling application; such
as a Personal Information Manager (PIM) or a Group Scheduling as a Personal Information Manager (PIM) or a Group Scheduling
product. product.
The iCalendar format is suitable as an exchange format between The iCalendar format is suitable as an exchange format between
applications or systems. The format is defined in terms of a MIME applications or systems. The format is defined in terms of a MIME
content type. This will enable the object to be exchanged using content type. This will enable the object to be exchanged using
several transports, including but not limited to SMTP, HTTP, a file several transports, including but not limited to SMTP, HTTP, a file
system, desktop interactive protocols such as the use of a memory- system, desktop interactive protocols such as the use of a memory-
skipping to change at page 9, line 15 skipping to change at page 10, line 15
3. iCalendar Object Specification 3. iCalendar Object Specification
The following sections define the details of a Calendaring and The following sections define the details of a Calendaring and
Scheduling Core Object Specification. The Calendaring and Scheduling Scheduling Core Object Specification. The Calendaring and Scheduling
Core Object is a collection of calendaring and scheduling Core Object is a collection of calendaring and scheduling
information. Typically, this information will consist of an information. Typically, this information will consist of an
iCalendar stream with one or more iCalendar objects. The body of the iCalendar stream with one or more iCalendar objects. The body of the
iCalendar object consists of a sequence of calendar properties and iCalendar object consists of a sequence of calendar properties and
one or more calendar components. one or more calendar components.
Section 3.1. defines the content line format; Section 3.2. defines Section 3.1 defines the content line format; Section 3.2 defines the
the property parameter format; Section 3.3. defines the data types property parameter format; Section 3.3 defines the data types for
for property values; Section 3.4. defines the iCalendar object property values; Section 3.4 defines the iCalendar object format;
format; Section 3.5. defines the iCalendar property format; Section Section 3.5 defines the iCalendar property format; Section 3.6
3.6. defines the calendar component format; Section 3.7. defines defines the calendar component format; Section 3.7 defines calendar
calendar properties; and Sectiopn 3.8. defines calendar component properties; and Section 3.8 defines calendar component properties.
properties.
This information is intended to be an integral part of the MIME This information is intended to be an integral part of the MIME
content type registration. In addition, this information can be used content type registration. In addition, this information can be used
independent of such content registration. In particular, this memo independent of such content registration. In particular, this memo
has direct applicability for use as a calendaring and scheduling has direct applicability for use as a calendaring and scheduling
exchange format in file-, memory- or network-based transport exchange format in file-, memory- or network-based transport
mechanisms. mechanisms.
3.1. Content Lines 3.1. Content Lines
skipping to change at page 12, line 34 skipping to change at page 13, line 34
3.1.2. Multiple Values 3.1.2. Multiple Values
Some properties defined in the iCalendar object can have multiple Some properties defined in the iCalendar object can have multiple
values. The general rule for encoding multi-valued items is to values. The general rule for encoding multi-valued items is to
simply create a new content line for each value, including the simply create a new content line for each value, including the
property name. However, it should be noted that some properties property name. However, it should be noted that some properties
support encoding multiple values in a single property by separating support encoding multiple values in a single property by separating
the values with a COMMA character (US-ASCII decimal 44). Individual the values with a COMMA character (US-ASCII decimal 44). Individual
property definitions should be consulted for determining whether a property definitions should be consulted for determining whether a
specific property allows multiple values and in which of these two specific property allows multiple values and in which of these two
forms. forms. Multi-valued properties MUST NOT be used to specify multiple
language variants of the same value. Calendar applications SHOULD
display all values.
3.1.3. Binary Content 3.1.3. Binary Content
Binary content information in an iCalendar object SHOULD be Binary content information in an iCalendar object SHOULD be
referenced using a URI within a property value. That is the binary referenced using a URI within a property value. That is the binary
content information SHOULD be placed in an external MIME entity that content information SHOULD be placed in an external MIME entity that
can be referenced by a URI from within the iCalendar object. In can be referenced by a URI from within the iCalendar object. In
applications where this is not feasible, binary content information applications where this is not feasible, binary content information
can be included within an iCalendar object, but only after first can be included within an iCalendar object, but only after first
encoding it into text using the "BASE64" encoding method defined in encoding it into text using the "BASE64" encoding method defined in
skipping to change at page 13, line 44 skipping to change at page 14, line 45
of the property value and other attributes. of the property value and other attributes.
Property parameter values that contain the COLON (US-ASCII decimal Property parameter values that contain the COLON (US-ASCII decimal
58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44) 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
character separators MUST be specified as quoted-string text values. character separators MUST be specified as quoted-string text values.
Property parameter values MUST NOT contain the DQUOTE (US-ASCII Property parameter values MUST NOT contain the DQUOTE (US-ASCII
decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is
used as a delimiter for parameter values that contain restricted used as a delimiter for parameter values that contain restricted
characters or URI text. For example: characters or URI text. For example:
DESCRIPTION;ALTREP="http://www.example.org":The Fall'98 Wild DESCRIPTION;ALTREP="cid:part1.0001@example.org":The Fall'98 Wild
Wizards Conference - - Las Vegas\, NV\, USA Wizards Conference - - Las Vegas\, NV\, USA
Property parameter values that are not in quoted strings are case Property parameter values that are not in quoted strings are case
insensitive. insensitive.
The general property parameters defined by this memo are defined by The general property parameters defined by this memo are defined by
the following notation: the following notation:
icalparameter = altrepparam ; Alternate text representation icalparameter = altrepparam ; Alternate text representation
/ cnparam ; Common name / cnparam ; Common name
skipping to change at page 15, line 7 skipping to change at page 16, line 7
Purpose: To specify an alternate text representation for the Purpose: To specify an alternate text representation for the
property value. property value.
Format Definition: This property parameter is defined by the Format Definition: This property parameter is defined by the
following notation: following notation:
altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
Description: This parameter specifies a URI that points to an Description: This parameter specifies a URI that points to an
alternate representation for a textual property value. A property alternate representation for a textual property value. A property
specifying this parameter MUST also include a value that reflects specifying this parameter MUST also include a value that reflects
the default representation of the text value. The individual URI the default representation of the text value. The URI parameter
parameter values MUST each be specified in a quoted-string. value MUST be specified in a quoted-string.
Note: While there is no restriction imposed on the URI schemes
allowed for this parameter, CID [RFC2392], HTTP [RFC2616], and
HTTPS [RFC2818] are the URI schemes most commonly used by
current implementations.
Example: Example:
DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com": DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com":
Project XYZ Review Meeting will include the following agenda Project XYZ Review Meeting will include the following agenda
items: (a) Market Overview\, (b) Finances\, (c) Project Man items: (a) Market Overview\, (b) Finances\, (c) Project Man
agement agement
The "ALTREP" property parameter value might point to a "text/html" The "ALTREP" property parameter value might point to a "text/html"
content portion. content portion.
skipping to change at page 18, line 20 skipping to change at page 19, line 25
the calendar user specified by the property. the calendar user specified by the property.
Format Definition: This property parameter is defined by the Format Definition: This property parameter is defined by the
following notation: following notation:
dirparam = "DIR" "=" DQUOTE uri DQUOTE dirparam = "DIR" "=" DQUOTE uri DQUOTE
Description: This parameter can be specified on properties with a Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter specifies a reference to CAL-ADDRESS value type. The parameter specifies a reference to
the directory entry associated with the calendar user specified by the directory entry associated with the calendar user specified by
the property. The parameter value is a URI. The URI parameter the property. The parameter value SHOULD be a CID [RFC2392], DATA
value MUST be specified in a quoted-string. [RFC2397], FILE [RFC1738], FTP [RFC1738], HTTP [RFC2616], HTTPS
[RFC2818], LDAP [RFC4516], or MID [RFC2392] URI. The URI
parameter value MUST be specified in a quoted-string.
Example: Example:
ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries,
c=US???(cn=Jim%20Dolittle)":mailto:jimdo@example.com c=US???(cn=Jim%20Dolittle)":mailto:jimdo@example.com
3.2.7. Inline Encoding 3.2.7. Inline Encoding
Parameter Name: ENCODING Parameter Name: ENCODING
skipping to change at page 19, line 11 skipping to change at page 20, line 16
corresponding to a property value consisting of text. The corresponding to a property value consisting of text. The
"BASE64" encoding type corresponds to a property value encoded "BASE64" encoding type corresponds to a property value encoded
using the "BASE64" encoding defined in [RFC2045]. using the "BASE64" encoding defined in [RFC2045].
If the value type parameter is ";VALUE=BINARY", then the inline If the value type parameter is ";VALUE=BINARY", then the inline
encoding parameter MUST be specified with the value encoding parameter MUST be specified with the value
";ENCODING=BASE64". ";ENCODING=BASE64".
Example: Example:
ATTACH;FMTYPE=IMAGE/JPEG;ENCODING=BASE64;VALUE=BINARY:MIICajC ATTACH;FMTYPE=image/jpeg;ENCODING=BASE64;VALUE=BINARY:MIICajC
CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA
qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw
<...remainder of "BASE64" encoded binary data...> <...remainder of "BASE64" encoded binary data...>
3.2.8. Format Type 3.2.8. Format Type
Parameter Name: FMTTYPE Parameter Name: FMTTYPE
Purpose: To specify the content type of a referenced object. Purpose: To specify the content type of a referenced object.
skipping to change at page 21, line 12 skipping to change at page 22, line 16
property. The value of the "LANGUAGE" property parameter is that property. The value of the "LANGUAGE" property parameter is that
defined in [RFC4646]. defined in [RFC4646].
For transport in a MIME entity, the Content-Language header field For transport in a MIME entity, the Content-Language header field
can be used to set the default language for the entire body part. can be used to set the default language for the entire body part.
Otherwise, no default language is assumed. Otherwise, no default language is assumed.
Example: The following are examples of this parameter on the Example: The following are examples of this parameter on the
"SUMMARY" and "LOCATION" properties: "SUMMARY" and "LOCATION" properties:
SUMMARY;LANGUAGE=us-EN:Company Holiday Party SUMMARY;LANGUAGE=en-US:Company Holiday Party
LOCATION;LANGUAGE=en:Germany LOCATION;LANGUAGE=en:Germany
LOCATION;LANGUAGE=no:Tyskland LOCATION;LANGUAGE=no:Tyskland
3.2.11. Group or List Membership 3.2.11. Group or List Membership
Parameter Name: MEMBER Parameter Name: MEMBER
Purpose: To specify the group or list membership of the calendar Purpose: To specify the group or list membership of the calendar
skipping to change at page 36, line 42 skipping to change at page 36, line 42
doesn't support the "Y" and "M" designators to specify durations doesn't support the "Y" and "M" designators to specify durations
in terms of years and months. in terms of years and months.
The duration of a week or a day depends on its position in the The duration of a week or a day depends on its position in the
calendar. In the case of discontinuities in the time scale, such calendar. In the case of discontinuities in the time scale, such
as the change from standard time to daylight time and back, the as the change from standard time to daylight time and back, the
computation of the exact duration requires the substraction or computation of the exact duration requires the substraction or
addition of the change of duration of the discontinuity. Leap addition of the change of duration of the discontinuity. Leap
seconds MUST NOT be considered when computing an exact duration. seconds MUST NOT be considered when computing an exact duration.
When computing an exact duration, the greatest order time When computing an exact duration, the greatest order time
components MUST be added first, that is, the number of weeks MUST components MUST be added first, that is, the number of days MUST
be added first, followed by the number of days, number of hours, be added first, followed by the number of hours, number of
number of minutes, and number of seconds. minutes, and number of seconds.
Negative durations are typically used to schedule an alarm to Negative durations are typically used to schedule an alarm to
trigger before an associated time (see Section 3.8.6.3). trigger before an associated time (see Section 3.8.6.3).
No additional content value encoding (i.e., BACKSLASH character No additional content value encoding (i.e., BACKSLASH character
encoding, see Section 3.3.11) are defined for this value type. encoding, see Section 3.3.11) are defined for this value type.
Example: A duration of 15 days, 5 hours and 20 seconds would be: Example: A duration of 15 days, 5 hours and 20 seconds would be:
P15DT5H0M20S P15DT5H0M20S
skipping to change at page 41, line 45 skipping to change at page 41, line 45
include SECONDLY, to specify repeating events based on an interval include SECONDLY, to specify repeating events based on an interval
of a second or more; MINUTELY, to specify repeating events based of a second or more; MINUTELY, to specify repeating events based
on an interval of a minute or more; HOURLY, to specify repeating on an interval of a minute or more; HOURLY, to specify repeating
events based on an interval of an hour or more; DAILY, to specify events based on an interval of an hour or more; DAILY, to specify
repeating events based on an interval of a day or more; WEEKLY, to repeating events based on an interval of a day or more; WEEKLY, to
specify repeating events based on an interval of a week or more; specify repeating events based on an interval of a week or more;
MONTHLY, to specify repeating events based on an interval of a MONTHLY, to specify repeating events based on an interval of a
month or more; and YEARLY, to specify repeating events based on an month or more; and YEARLY, to specify repeating events based on an
interval of a year or more. interval of a year or more.
The INTERVAL rule part contains a positive integer representing The INTERVAL rule part contains a positive integer representing at
how often the recurrence rule repeats. The default value is "1", which intervals the recurrence rule repeats. The default value is
meaning every second for a SECONDLY rule, or every minute for a "1", meaning every second for a SECONDLY rule, every minute for a
MINUTELY rule, every hour for an HOURLY rule, every day for a MINUTELY rule, every hour for an HOURLY rule, every day for a
DAILY rule, every week for a WEEKLY rule, every month for a DAILY rule, every week for a WEEKLY rule, every month for a
MONTHLY rule and every year for a YEARLY rule. MONTHLY rule, and every year for a YEARLY rule. For example,
within a DAILY rule, a value of "8" means every eight days.
The UNTIL rule part defines a DATE or DATE-TIME value which bounds The UNTIL rule part defines a DATE or DATE-TIME value which bounds
the recurrence rule in an inclusive manner. If the value the recurrence rule in an inclusive manner. If the value
specified by UNTIL is synchronized with the specified recurrence, specified by UNTIL is synchronized with the specified recurrence,
this DATE or DATE-TIME becomes the last instance of the this DATE or DATE-TIME becomes the last instance of the
recurrence. The value of the UNTIL rule part MUST have the same recurrence. The value of the UNTIL rule part MUST have the same
value type as the "DTSTART" property. Furthermore, if the value type as the "DTSTART" property. Furthermore, if the
"DTSTART" property is specified as a date with local time, then "DTSTART" property is specified as a date with local time, then
the UNTIL rule part MUST also be specified as a date with local the UNTIL rule part MUST also be specified as a date with local
time. If the "DTSTART" property is specified as a date with UTC time. If the "DTSTART" property is specified as a date with UTC
skipping to change at page 47, line 12 skipping to change at page 47, line 12
Format Definition: This value type is defined by the following Format Definition: This value type is defined by the following
notation. notation.
text = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR) text = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
; Folded according to description above ; Folded according to description above
ESCAPED-CHAR = ("\\" / "\;" / "\," / "\N" / "\n") ESCAPED-CHAR = ("\\" / "\;" / "\," / "\N" / "\n")
; \\ encodes \, \N or \n encodes newline ; \\ encodes \, \N or \n encodes newline
; \; encodes ;, \, encodes , ; \; encodes ;, \, encodes ,
TSAFE-CHAR = %x20-21 / %x23-2B / %x2D-39 / %x3C-5B / TSAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-5B /
%x5D-7E / NON-US-ASCII %x5D-7E / NON-US-ASCII
; Any character except CTLs not needed by the current ; Any character except CONTROLs not needed by the current
; character set, DQUOTE, ";", ":", "\", "," ; character set, DQUOTE, ";", ":", "\", ","
Description: If the property permits, multiple TEXT values are Description: If the property permits, multiple TEXT values are
specified by a COMMA character (US-ASCII decimal 44) separated specified by a COMMA character (US-ASCII decimal 44) separated
list of values. list of values.
The language in which the text is represented can be controlled by The language in which the text is represented can be controlled by
the "LANGUAGE" property parameter. the "LANGUAGE" property parameter.
An intentional formatted text line break MUST only be included in An intentional formatted text line break MUST only be included in
skipping to change at page 53, line 46 skipping to change at page 53, line 46
An iCalendar object MUST include the "PRODID" and "VERSION" calendar An iCalendar object MUST include the "PRODID" and "VERSION" calendar
properties. In addition, it MUST include at least one calendar properties. In addition, it MUST include at least one calendar
component. Special forms of iCalendar objects are possible to component. Special forms of iCalendar objects are possible to
publish just busy time (i.e., only a "VFREEBUSY" calendar component) publish just busy time (i.e., only a "VFREEBUSY" calendar component)
or time zone (i.e., only a "VTIMEZONE" calendar component) or time zone (i.e., only a "VTIMEZONE" calendar component)
information. In addition, a complex iCalendar object that is used to information. In addition, a complex iCalendar object that is used to
capture a complete snapshot of the contents of a calendar is possible capture a complete snapshot of the contents of a calendar is possible
(e.g., composite of many different calendar components). More (e.g., composite of many different calendar components). More
commonly, an iCalendar object will consist of just a single "VEVENT", commonly, an iCalendar object will consist of just a single "VEVENT",
"VTODO" or "VJOURNAL" calendar component. Applications MUST ignore "VTODO" or "VJOURNAL" calendar component. Applications MUST ignore
x-comp and iana-comp they don't recognized. x-comp and iana-comp they don't recognized. Applications that
support importing iCalendar objects SHOULD support all of the
component types defined in this document, and SHOULD NOT silently
drop any components as that can lead to user data loss.
3.6.1. Event Component 3.6.1. Event Component
Component Name: VEVENT Component Name: VEVENT
Purpose: Provide a grouping of component properties that describe an Purpose: Provide a grouping of component properties that describe an
event. event.
Format Definition: A "VEVENT" calendar component is defined by the Format Definition: A "VEVENT" calendar component is defined by the
following notation: following notation:
eventc = "BEGIN" ":" "VEVENT" CRLF eventc = "BEGIN" ":" "VEVENT" CRLF
eventprop *alarmc eventprop *alarmc
skipping to change at page 54, line 21 skipping to change at page 54, line 24
eventc = "BEGIN" ":" "VEVENT" CRLF eventc = "BEGIN" ":" "VEVENT" CRLF
eventprop *alarmc eventprop *alarmc
"END" ":" "VEVENT" CRLF "END" ":" "VEVENT" CRLF
eventprop = *( eventprop = *(
; the following are REQUIRED, ; the following are REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
dtstamp / dtstart / uid / dtstamp / uid /
; the following is REQUIRED if the component
; appears in an iCalendar object that doesn't
; specify the "METHOD" property, otherwise it
; is OPTIONAL, in any case it MUST NOT occur
; more than once
dtstart /
; the following are OPTIONAL, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
class / created / description / geo / class / created / description / geo /
last-mod / location / organizer / priority / last-mod / location / organizer / priority /
seq / status / summary / transp / seq / status / summary / transp /
url / recurid / url / recurid /
; the following is OPTIONAL, ; the following is OPTIONAL,
; but SHOULD NOT occur more than once ; but SHOULD NOT occur more than once
skipping to change at page 55, line 31 skipping to change at page 56, line 11
"DTEND" property value is set to a calendar date after the "DTEND" property value is set to a calendar date after the
"DTSTART" property value). If such a "VEVENT" has a "DURATION" "DTSTART" property value). If such a "VEVENT" has a "DURATION"
property, it MUST be specified as a "dur-day" or "dur-week" value. property, it MUST be specified as a "dur-day" or "dur-week" value.
The "DTSTART" property for a "VEVENT" specifies the inclusive The "DTSTART" property for a "VEVENT" specifies the inclusive
start of the event. For recurring events, it also specifies the start of the event. For recurring events, it also specifies the
very first instance in the recurrence set. The "DTEND" property very first instance in the recurrence set. The "DTEND" property
for a "VEVENT" calendar component specifies the non-inclusive end for a "VEVENT" calendar component specifies the non-inclusive end
of the event. For cases where a "VEVENT" calendar component of the event. For cases where a "VEVENT" calendar component
specifies a "DTSTART" property with a DATE value type but no specifies a "DTSTART" property with a DATE value type but no
"DTEND" nor DURATION property, the event's duration is taken to be "DTEND" nor "DURATION" property, the event's duration is taken to
one day. For cases where a "VEVENT" calendar component specifies be one day. For cases where a "VEVENT" calendar component
a "DTSTART" property with a DATE-TIME value type but no "DTEND" specifies a "DTSTART" property with a DATE-TIME value type but no
property, the event ends on the same calendar date and time of day "DTEND" property, the event ends on the same calendar date and
specified by the "DTSTART" property. time of day specified by the "DTSTART" property.
The "VEVENT" calendar component cannot be nested within another The "VEVENT" calendar component cannot be nested within another
calendar component. However, "VEVENT" calendar components can be calendar component. However, "VEVENT" calendar components can be
related to each other or to a "VTODO" or to a "VJOURNAL" calendar related to each other or to a "VTODO" or to a "VJOURNAL" calendar
component with the "RELATED-TO" property. component with the "RELATED-TO" property.
Example: The following is an example of the "VEVENT" calendar Example: The following is an example of the "VEVENT" calendar
component used to represent a meeting that will also be opaque to component used to represent a meeting that will also be opaque to
searches for busy time: searches for busy time:
skipping to change at page 62, line 19 skipping to change at page 62, line 19
fbprop = *( fbprop = *(
; the following are REQUIRED, ; the following are REQUIRED,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
dtstamp / uid / dtstamp / uid /
; the following are OPTIONAL, ; the following are OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
contact / dtstart / dtend / duration / contact / dtstart / dtend /
organizer / url / organizer / url /
; the following are OPTIONAL, ; the following are OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
attendee / comment / freebusy / rstatus / x-prop / attendee / comment / freebusy / rstatus / x-prop /
iana-prop iana-prop
) )
Description: A "VFREEBUSY" calendar component is a grouping of Description: A "VFREEBUSY" calendar component is a grouping of
skipping to change at page 63, line 31 skipping to change at page 63, line 31
requests for busy time, requests for both free and busy, and the requests for busy time, requests for both free and busy, and the
associated replies. associated replies.
Free/Busy information is represented with the "FREEBUSY" property. Free/Busy information is represented with the "FREEBUSY" property.
This property provides a terse representation of time periods. This property provides a terse representation of time periods.
One or more "FREEBUSY" properties can be specified in the One or more "FREEBUSY" properties can be specified in the
"VFREEBUSY" calendar component. "VFREEBUSY" calendar component.
When present in a "VFREEBUSY" calendar component, the "DTSTART" When present in a "VFREEBUSY" calendar component, the "DTSTART"
and "DTEND" properties SHOULD be specified prior to any "FREEBUSY" and "DTEND" properties SHOULD be specified prior to any "FREEBUSY"
properties. In a free time request, these properties can be used properties.
in combination with the "DURATION" property to represent a request
for a duration of free time within a specified window of time.
The recurrence properties ("RRULE", "RDATE", "EXDATE") are not The recurrence properties ("RRULE", "RDATE", "EXDATE") are not
permitted within a "VFREEBUSY" calendar component. Any recurring permitted within a "VFREEBUSY" calendar component. Any recurring
events are resolved into their individual busy time periods using events are resolved into their individual busy time periods using
the "FREEBUSY" property. the "FREEBUSY" property.
Example: The following is an example of a "VFREEBUSY" calendar Example: The following is an example of a "VFREEBUSY" calendar
component used to request free or busy time information: component used to request free or busy time information:
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
skipping to change at page 66, line 25 skipping to change at page 66, line 25
in time zone rules in effect for New York City starting from 1967. in time zone rules in effect for New York City starting from 1967.
Each line represents a description or rule for a particular Each line represents a description or rule for a particular
observance. observance.
Effective Observance Rule Effective Observance Rule
+-----------+--------------------------+--------+--------------+ +-----------+--------------------------+--------+--------------+
| Date | (Date/Time) | Offset | Abbreviation | | Date | (Date/Time) | Offset | Abbreviation |
+-----------+--------------------------+--------+--------------+ +-----------+--------------------------+--------+--------------+
| 1967-1973 | last Sun in Apr, 02:00 | -0400 | EDT | | 1967-1973 | last Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 1967-2006 | last Sun in Oct, 02:00 | -0500 | EST | | 1967-2006 | last Sun in Oct, 02:00 | -0500 | EST |
| | | | |
| 1974-1974 | Jan 6, 02:00 | -0400 | EDT | | 1974-1974 | Jan 6, 02:00 | -0400 | EDT |
| | | | |
| 1975-1975 | Feb 23, 02:00 | -0400 | EDT | | 1975-1975 | Feb 23, 02:00 | -0400 | EDT |
| | | | |
| 1976-1986 | last Sun in Apr, 02:00 | -0400 | EDT | | 1976-1986 | last Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 1987-2006 | first Sun in Apr, 02:00 | -0400 | EDT | | 1987-2006 | first Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 2007-* | second Sun in Mar, 02:00 | -0400 | EDT | | 2007-* | second Sun in Mar, 02:00 | -0400 | EDT |
| | | | |
| 2007-* | first Sun in Nov, 02:00 | -0500 | EST | | 2007-* | first Sun in Nov, 02:00 | -0500 | EST |
+-----------+--------------------------+--------+--------------+ +-----------+--------------------------+--------+--------------+
Note: The specification of a global time zone registry is not Note: The specification of a global time zone registry is not
addressed by this document and is left for future study. addressed by this document and is left for future study.
However, implementers may find the TZ database [TZDB] a useful However, implementers may find the TZ database [TZDB] a useful
reference. It is an informal, public-domain collection of time reference. It is an informal, public-domain collection of time
zone information, which is currently being maintained by zone information, which is currently being maintained by
volunteer Internet participants, and is used in several volunteer Internet participants, and is used in several
operating systems. This database contains current and operating systems. This database contains current and
skipping to change at page 68, line 48 skipping to change at page 69, line 4
The mandatory "TZOFFSETFROM" property gives the UTC offset which The mandatory "TZOFFSETFROM" property gives the UTC offset which
is in use when the onset of this time zone observance begins. is in use when the onset of this time zone observance begins.
"TZOFFSETFROM" is combined with "DTSTART" to define the effective "TZOFFSETFROM" is combined with "DTSTART" to define the effective
onset for the time zone sub-component definition. For example, onset for the time zone sub-component definition. For example,
the following represents the time at which the observance of the following represents the time at which the observance of
Standard Time took effect in Fall 1967 for New York City: Standard Time took effect in Fall 1967 for New York City:
DTSTART:19671029T020000 DTSTART:19671029T020000
TZOFFSETFROM:-0400 TZOFFSETFROM:-0400
The mandatory "TZOFFSETTO" property gives the UTC offset for the The mandatory "TZOFFSETTO" property gives the UTC offset for the
time zone sub-component (Standard Time or Daylight Saving Time) time zone sub-component (Standard Time or Daylight Saving Time)
when this observance is in use. when this observance is in use.
The optional "TZNAME" property is the customary name for the time The optional "TZNAME" property is the customary name for the time
zone. It may be specified multiple times, to allow for specifying zone. This could be used for displaying dates.
multiple language variants of the time zone names. This could be
used for displaying dates.
The onset date-times for the observance defined by the time zone The onset date-times for the observance defined by the time zone
sub-component is defined by the "DTSTART", "RRULE", and "RDATE" sub-component is defined by the "DTSTART", "RRULE", and "RDATE"
properties. properties.
The "RRULE" property defines the recurrence rule for the onset of The "RRULE" property defines the recurrence rule for the onset of
the observance defined by this time zone sub-component. Some the observance defined by this time zone sub-component. Some
specific requirements for the usage of "RRULE" for this purpose specific requirements for the usage of "RRULE" for this purpose
include: include:
* If observance is known to have an effective end date, the * If observance is known to have an effective end date, the
"UNTIL" recurrence rule parameter MUST be used to specify the "UNTIL" recurrence rule parameter MUST be used to specify the
last valid onset of this observance (i.e., the UNTIL date-time last valid onset of this observance (i.e., the UNTIL date-time
will be equal to the last instance generated by the recurrence will be equal to the last instance generated by the recurrence
pattern). It MUST be specified in UTC time. pattern). It MUST be specified in UTC time.
* The "DTSTART" and the "TZOFFSETFROM" properties MUST be used * The "DTSTART" and the "TZOFFSETFROM" properties MUST be used
when generating the onset date-time values (instances) from the when generating the onset date-time values (instances) from the
"RRULE". "RRULE".
Alternatively, the "RDATE" property can be used to define the The "RDATE" property can also be used to define the onset of the
onset of the observance by giving the individual onset date and observance by giving the individual onset date and times. "RDATE"
times. "RDATE" in this usage MUST be specified as a local DATE- in this usage MUST be specified as a local DATE-TIME value,
TIME value, relative to the UTC offset specified in the relative to the UTC offset specified in the "TZOFFSETFROM"
"TZOFFSETFROM" property. property.
The optional "COMMENT" property is also allowed for descriptive The optional "COMMENT" property is also allowed for descriptive
explanatory text. explanatory text.
Example: The following are examples of the "VTIMEZONE" calendar Example: The following are examples of the "VTIMEZONE" calendar
component: component:
This is an example showing all the time zone rules for New York This is an example showing all the time zone rules for New York
City since April 30, 1967 at 03:00:00 EDT. City since April 30, 1967 at 03:00:00 EDT.
skipping to change at page 71, line 5 skipping to change at page 71, line 5
END:DAYLIGHT END:DAYLIGHT
BEGIN:STANDARD BEGIN:STANDARD
DTSTART:20071104T020000 DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZOFFSETFROM:-0400 TZOFFSETFROM:-0400
TZOFFSETTO:-0500 TZOFFSETTO:-0500
TZNAME:EST TZNAME:EST
END:STANDARD END:STANDARD
END:VTIMEZONE END:VTIMEZONE
This is an example showing time zone information for New York City This is an example showing time zone information for New York City
using "RDATE" property. Note that this is only suitable for a using property. Note that this is only suitable for a recurring
recurring event that starts on or later than March 11, 2007 at 03: event that starts on or later than March 11, 2007 at 03:00:00 EDT
00:00 EDT (i.e., the earliest effective transition date and time) (i.e., the earliest effective transition date and time) and ends
and ends no later than March 9, 2008 at 01:59:59 EST (i.e., latest no later than March 9, 2008 at 01:59:59 EST (i.e., latest valid
valid date and time for EST in this scenario). For example, this date and time for EST in this scenario). For example, this can be
can be used for a recurring event that occurs every Friday, 8:00 used for a recurring event that occurs every Friday, 8:00 A.M.-
A.M.-9:00 A.M., starting June 1, 2007, ending December 31, 2007, 9:00 A.M., starting June 1, 2007, ending December 31, 2007,
BEGIN:VTIMEZONE BEGIN:VTIMEZONE
TZID:America/New_York TZID:America/New_York
LAST-MODIFIED:20050809T050000Z LAST-MODIFIED:20050809T050000Z
BEGIN:STANDARD BEGIN:STANDARD
DTSTART:20071104T020000 DTSTART:20071104T020000
TZOFFSETFROM:-0400 TZOFFSETFROM:-0400
TZOFFSETTO:-0500 TZOFFSETTO:-0500
TZNAME:EST TZNAME:EST
END:STANDARD END:STANDARD
skipping to change at page 94, line 28 skipping to change at page 93, line 48
; and MAY occur more than once ; and MAY occur more than once
(";" other-param) (";" other-param)
) )
Example: The following is an example of this property: Example: The following is an example of this property:
RESOURCES:EASEL,PROJECTOR,VCR RESOURCES:EASEL,PROJECTOR,VCR
RESOURCES;LANGUAGE=fr:1 raton-laveur RESOURCES;LANGUAGE=fr:Nettoyeur haute pression
3.8.1.11. Status 3.8.1.11. Status
Property Name: STATUS Property Name: STATUS
Purpose: This property defines the overall status or confirmation Purpose: This property defines the overall status or confirmation
for the calendar component. for the calendar component.
Value Type: TEXT Value Type: TEXT
skipping to change at page 100, line 27 skipping to change at page 100, line 8
MUST be one of the forms defined for the DATE-TIME value type. MUST be one of the forms defined for the DATE-TIME value type.
The value type can be set to a DATE value type. The value type can be set to a DATE value type.
Property Parameters: IANA, non-standard, value data type, and time Property Parameters: IANA, non-standard, value data type, and time
zone identifier property parameters can be specified on this zone identifier property parameters can be specified on this
property. property.
Conformance: This property can be specified once in the "VEVENT", Conformance: This property can be specified once in the "VEVENT",
"VTODO", or "VFREEBUSY" calendar components as well as in the "VTODO", or "VFREEBUSY" calendar components as well as in the
"STANDARD" and "DAYLIGHT" sub-components. This property is "STANDARD" and "DAYLIGHT" sub-components. This property is
REQUIRED in "VEVENT" calendar components and in all types of REQUIRED in all types of recurring calendar components that
recurring calendar components. specify the "RRULE" property. This property is also REQUIRED in
"VEVENT" calendar components contained in iCalendar objects that
don't specify the "METHOD" property.
Description: Within the "VEVENT" calendar component, this property Description: Within the "VEVENT" calendar component, this property
defines the start date and time for the event. defines the start date and time for the event.
Within the "VFREEBUSY" calendar component, this property defines Within the "VFREEBUSY" calendar component, this property defines
the start date and time for the free or busy time information. the start date and time for the free or busy time information.
The time MUST be specified in UTC time. The time MUST be specified in UTC time.
Within the "STANDARD" and "DAYLIGHT" sub-components, this property Within the "STANDARD" and "DAYLIGHT" sub-components, this property
defines the effective start date and time for a time zone defines the effective start date and time for a time zone
skipping to change at page 101, line 40 skipping to change at page 101, line 19
Property Name: DURATION Property Name: DURATION
Purpose: This property specifies a positive duration of time. Purpose: This property specifies a positive duration of time.
Value Type: DURATION Value Type: DURATION
Property Parameters: IANA and non-standard property parameters can Property Parameters: IANA and non-standard property parameters can
be specified on this property. be specified on this property.
Conformance: This property can be specified in "VEVENT", "VTODO", Conformance: This property can be specified in "VEVENT", "VTODO", or
"VFREEBUSY" or "VALARM" calendar components. "VALARM" calendar components.
Description: In a "VEVENT" calendar component the property may be Description: In a "VEVENT" calendar component the property may be
used to specify a duration of the event, instead of an explicit used to specify a duration of the event, instead of an explicit
end date/time. In a "VTODO" calendar component the property may end date/time. In a "VTODO" calendar component the property may
be used to specify a duration for the to-do, instead of an be used to specify a duration for the to-do, instead of an
explicit due date/time. In a "VFREEBUSY" calendar component the explicit due date/time. In a "VALARM" calendar component the
property may be used to specify the interval of free time being property may be used to specify the delay period prior to
requested. In a "VALARM" calendar component the property may be repeating an alarm. When the "DURATION" property relates to a
used to specify the delay period prior to repeating an alarm. "DTSTART" property that is specified as a DATE value, then the
When the "DURATION" property relates to a "DTSTART" property that "DURATION" property MUST be specified as a "dur-day" or "dur-week"
is specified as a DATE value, then the "DURATION" property MUST be value.
specified as a "dur-day" or "dur-week" value.
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
duration = "DURATION" durparam ":" dur-value CRLF duration = "DURATION" durparam ":" dur-value CRLF
;consisting of a positive duration of time. ;consisting of a positive duration of time.
durparam = *(";" other-param) durparam = *(";" other-param)
Example: The following is an example of this property that specifies Example: The following is an example of this property that specifies
skipping to change at page 106, line 20 skipping to change at page 105, line 42
time zone description. time zone description.
Value Type: TEXT Value Type: TEXT
Property Parameters: IANA, non-standard, and language property Property Parameters: IANA, non-standard, and language property
parameters can be specified on this property. parameters can be specified on this property.
Conformance: This property can be specified in "STANDARD" and Conformance: This property can be specified in "STANDARD" and
"DAYLIGHT" sub-components. "DAYLIGHT" sub-components.
Description: This property may be specified in multiple languages; Description: This property specifies a customary name that can be
in order to provide for different language requirements. used when displaying dates that occur during the observance
defined by the time zone sub-component.
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
tzname = "TZNAME" tznparam ":" text CRLF tzname = "TZNAME" tznparam ":" text CRLF
tznparam = *( tznparam = *(
; the following is OPTIONAL, ; the following is OPTIONAL,
; but MUST NOT occur more than once ; but MUST NOT occur more than once
(";" languageparam) / (";" languageparam) /
; the following is OPTIONAL, ; the following is OPTIONAL,
; and MAY occur more than once ; and MAY occur more than once
(";" other-param) (";" other-param)
) )
Example: The following are example of this property: Example: The following are examples of this property:
TZNAME:EST TZNAME:EST
The following is an example of this property when two different
languages for the time zone name are specified:
TZNAME;LANGUAGE=en:EST
TZNAME;LANGUAGE=fr-CA:HNE TZNAME;LANGUAGE=fr-CA:HNE
3.8.3.3. Time Zone Offset From 3.8.3.3. Time Zone Offset From
Property Name: TZOFFSETFROM Property Name: TZOFFSETFROM
Purpose: This property specifies the offset which is in use prior to Purpose: This property specifies the offset which is in use prior to
this time zone observance. this time zone observance.
Value Type: UTC-OFFSET Value Type: UTC-OFFSET
skipping to change at page 142, line 39 skipping to change at page 141, line 39
The "Attendee" includes this property in an iCalendar object that The "Attendee" includes this property in an iCalendar object that
it sends to the "Organizer" to specify the version of the calendar it sends to the "Organizer" to specify the version of the calendar
component that the "Attendee" is referring to. component that the "Attendee" is referring to.
A change to the sequence number is not the mechanism that an A change to the sequence number is not the mechanism that an
"Organizer" uses to request a response from the "Attendees". The "Organizer" uses to request a response from the "Attendees". The
"RSVP" parameter on the "ATTENDEE" property is used by the "RSVP" parameter on the "ATTENDEE" property is used by the
"Organizer" to indicate that a response from the "Attendees" is "Organizer" to indicate that a response from the "Attendees" is
requested. requested.
Recurrence instances of a recurring component MAY have different
sequence numbers.
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
seq = "SEQUENCE" seqparam ":" integer CRLF seq = "SEQUENCE" seqparam ":" integer CRLF
; Default is "0" ; Default is "0"
seqparam = *(";" other-param) seqparam = *(";" other-param)
Example: The following is an example of this property for a calendar Example: The following is an example of this property for a calendar
component that was just created by the "Organizer": component that was just created by the "Organizer":
SEQUENCE:0 SEQUENCE:0
The following is an example of this property for a calendar The following is an example of this property for a calendar
component that has been revised two different times by the component that has been revised two different times by the
"Organizer": "Organizer":
SEQUENCE:2 SEQUENCE:2
skipping to change at page 146, line 5 skipping to change at page 144, line 40
46) separated pair or 3-tuple of integers. For example, "3.1" or 46) separated pair or 3-tuple of integers. For example, "3.1" or
"3.1.1". The successive levels of integers provide for a "3.1.1". The successive levels of integers provide for a
successive level of status code granularity. successive level of status code granularity.
The following are initial classes for the return status code. The following are initial classes for the return status code.
Individual iCalendar object methods will define specific return Individual iCalendar object methods will define specific return
status codes for these classes. In addition, other classes for status codes for these classes. In addition, other classes for
the return status code may be defined using the registration the return status code may be defined using the registration
process defined later in this memo. process defined later in this memo.
|==============+===============================================| +--------+----------------------------------------------------------+
| Short Return | Longer Return Status Description | | Short | Longer Return Status Description |
| Status Code | | | Return | |
|==============+===============================================| | Status | |
| 1.xx | Preliminary success. This class of status | | Code | |
| | of status code indicates that the request has | +--------+----------------------------------------------------------+
| | request has been initially processed but that | | 1.xx | Preliminary success. This class of status code |
| | completion is pending. | | | indicates that the request has been initially processed |
|==============+===============================================| | | but that completion is pending. |
| 2.xx | Successful. This class of status code | | | |
| | indicates that the request was completed | | 2.xx | Successful. This class of status code indicates that |
| | successfuly. However, the exact status code | | | the request was completed successfuly. However, the |
| | can indicate that a fallback has been taken. | | | exact status code can indicate that a fallback has been |
|==============+===============================================| | | taken. |
| 3.xx | Client Error. This class of status code | | | |
| | indicates that the request was not successful.| | 3.xx | Client Error. This class of status code indicates that |
| | The error is the result of either a syntax or | | | the request was not successful. The error is the result |
| | a semantic error in the client formatted | | | of either a syntax or a semantic error in the client |
| | request. Request should not be retried until | | | formatted request. Request should not be retried until |
| | the condition in the request is corrected. | | | the condition in the request is corrected. |
|==============+===============================================| | | |
| 4.xx | Scheduling Error. This class of status code | | 4.xx | Scheduling Error. This class of status code indicates |
| | indicates that the request was not successful.| | | that the request was not successful. Some sort of error |
| | Some sort of error occurred within the | | | occurred within the calendaring and scheduling service, |
| | calendaring and scheduling service, not | | | not directly related to the request itself. |
| | directly related to the request itself. | +--------+----------------------------------------------------------+
|==============+===============================================|
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
rstatus = "REQUEST-STATUS" rstatparam ":" rstatus = "REQUEST-STATUS" rstatparam ":"
statcode ";" statdesc [";" extdata] statcode ";" statdesc [";" extdata]
rstatparam = *( rstatparam = *(
; the following is OPTIONAL, ; the following is OPTIONAL,
skipping to change at page 149, line 26 skipping to change at page 148, line 26
BEGIN:DAYLIGHT BEGIN:DAYLIGHT
DTSTART:19990404T020000 DTSTART:19990404T020000
TZOFFSETFROM:-0500 TZOFFSETFROM:-0500
TZOFFSETTO:-0400 TZOFFSETTO:-0400
TZNAME:EDT TZNAME:EDT
END:DAYLIGHT END:DAYLIGHT
END:VTIMEZONE END:VTIMEZONE
BEGIN:VEVENT BEGIN:VEVENT
DTSTAMP:19980309T231000Z DTSTAMP:19980309T231000Z
UID:guid-1.example.com UID:guid-1.example.com
ORGANIZER;ROLE=CHAIR:mailto:mrbig@example.com ORGANIZER:mailto:mrbig@example.com
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP: ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:
mailto:employee-A@example.com mailto:employee-A@example.com
DESCRIPTION:Project XYZ Review Meeting DESCRIPTION:Project XYZ Review Meeting
CATEGORIES:MEETING CATEGORIES:MEETING
CLASS:PUBLIC CLASS:PUBLIC
CREATED:19980309T130000Z CREATED:19980309T130000Z
SUMMARY:XYZ Project Review SUMMARY:XYZ Project Review
DTSTART;TZID=America/New_York:19980312T083000 DTSTART;TZID=America/New_York:19980312T083000
DTEND;TZID=America/New_York:19980312T093000 DTEND;TZID=America/New_York:19980312T093000
LOCATION:1CP Conference Room 4350 LOCATION:1CP Conference Room 4350
skipping to change at page 152, line 29 skipping to change at page 152, line 12
END:VFREEBUSY END:VFREEBUSY
END:VCALENDAR END:VCALENDAR
5. Recommended Practices 5. Recommended Practices
These recommended practices should be followed in order to assure These recommended practices should be followed in order to assure
consistent handling of the following cases for an iCalendar object. consistent handling of the following cases for an iCalendar object.
1. Content lines longer than 75 octets SHOULD be folded. 1. Content lines longer than 75 octets SHOULD be folded.
2. 2. When the combination of the "RRULE" and "RDATE" properties in a
3. When the combination of the "RRULE" and "RDATE" properties in a
recurring component produces multiple instances having the same recurring component produces multiple instances having the same
start DATE-TIME value, they should be collapsed to, and start DATE-TIME value, they should be collapsed to, and
considered as, a single instance. If the "RDATE" property is considered as, a single instance. If the "RDATE" property is
specified as a PERIOD value the duration of the recurrence specified as a PERIOD value the duration of the recurrence
instance will be the one specified by the "RDATE" property, and instance will be the one specified by the "RDATE" property, and
not the duration of the recurrence instance defined by the not the duration of the recurrence instance defined by the
"DTSTART" property. "DTSTART" property.
4. When a calendar user receives multiple requests for the same 3. When a calendar user receives multiple requests for the same
calendar component (e.g., REQUEST for a "VEVENT" calendar calendar component (e.g., REQUEST for a "VEVENT" calendar
component) as a result of being on multiple mailing lists component) as a result of being on multiple mailing lists
specified by "ATTENDEE" properties in the request, they SHOULD specified by "ATTENDEE" properties in the request, they SHOULD
respond to only one of the requests. The calendar user SHOULD respond to only one of the requests. The calendar user SHOULD
also specify (using the "MEMBER" parameter of the "ATTENDEE" also specify (using the "MEMBER" parameter of the "ATTENDEE"
property) which mailing list they are a member of. property) which mailing list they are a member of.
5. An implementation can truncate a "SUMMARY" property value to 255 4. An implementation can truncate a "SUMMARY" property value to 255
octets, but MUST NOT truncate the value in the middle of a UTF-8 octets, but MUST NOT truncate the value in the middle of a UTF-8
multi-octet sequence. multi-octet sequence.
6. If seconds of the minute are not supported by an implementation, 5. If seconds of the minute are not supported by an implementation,
then a value of "00" SHOULD be specified for the seconds then a value of "00" SHOULD be specified for the seconds
component in a time value. component in a time value.
7. 6. "TZURL" values SHOULD NOT be specified as a file URI type. This
URI form can be useful within an organization, but is problematic
8. "TZURL" values SHOULD NOT be specified as a file URI type. This in the Internet.
URI form can be useful within an organization, but is
problematic in the Internet.
9. Some possible English values for "CATEGORIES" property include 7. Some possible English values for "CATEGORIES" property include
"ANNIVERSARY", "APPOINTMENT", "BUSINESS", "EDUCATION", "ANNIVERSARY", "APPOINTMENT", "BUSINESS", "EDUCATION", "HOLIDAY",
"HOLIDAY", "MEETING", "MISCELLANEOUS", "NON-WORKING HOURS", "NOT "MEETING", "MISCELLANEOUS", "NON-WORKING HOURS", "NOT IN OFFICE",
IN OFFICE", "PERSONAL", "PHONE CALL", "SICK DAY", "SPECIAL "PERSONAL", "PHONE CALL", "SICK DAY", "SPECIAL OCCASION",
OCCASION", "TRAVEL", "VACATION". Categories can be specified in "TRAVEL", "VACATION". Categories can be specified in any
any registered language. registered language.
10. Some possible English values for "RESOURCES" property include 8. Some possible English values for "RESOURCES" property include
"CATERING", "CHAIRS", "COMPUTER PROJECTOR", "EASEL", "OVERHEAD "CATERING", "CHAIRS", "COMPUTER PROJECTOR", "EASEL", "OVERHEAD
PROJECTOR", "SPEAKER PHONE", "TABLE", "TV", "VCR", "VIDEO PROJECTOR", "SPEAKER PHONE", "TABLE", "TV", "VCR", "VIDEO PHONE",
PHONE", "VEHICLE". Resources can be specified in any registered "VEHICLE". Resources can be specified in any registered
language. language.
6. Internationalization Considerations 6. Internationalization Considerations
Applications MUST generate iCalendar stream in the UTF-8 charset and Applications MUST generate iCalendar stream in the UTF-8 charset and
MUST accept iCalendar stream in the UTF-8 or US-ASCII charset. MUST accept iCalendar stream in the UTF-8 or US-ASCII charset.
7. Security Considerations 7. Security Considerations
Because calendaring and scheduling information is very privacy- Because calendaring and scheduling information is very privacy-
skipping to change at page 160, line 41 skipping to change at page 162, line 9
8.3.1. Components Registry 8.3.1. Components Registry
The following table is to be used to initialize the components The following table is to be used to initialize the components
registry. registry.
+-----------+---------+------------------------+ +-----------+---------+------------------------+
| Component | Status | Reference | | Component | Status | Reference |
+-----------+---------+------------------------+ +-----------+---------+------------------------+
| VCALENDAR | Current | RFCXXXX, Section 3.4 | | VCALENDAR | Current | RFCXXXX, Section 3.4 |
| | | |
| VEVENT | Current | RFCXXXX, Section 3.6.1 | | VEVENT | Current | RFCXXXX, Section 3.6.1 |
| | | |
| VTODO | Current | RFCXXXX, Section 3.6.2 | | VTODO | Current | RFCXXXX, Section 3.6.2 |
| | | |
| VJOURNAL | Current | RFCXXXX, Section 3.6.3 | | VJOURNAL | Current | RFCXXXX, Section 3.6.3 |
| | | |
| VFREEBUSY | Current | RFCXXXX, Section 3.6.4 | | VFREEBUSY | Current | RFCXXXX, Section 3.6.4 |
| | | |
| VTIMEZONE | Current | RFCXXXX, Section 3.6.5 | | VTIMEZONE | Current | RFCXXXX, Section 3.6.5 |
| | | |
| VALARM | Current | RFCXXXX, Section 3.6.6 | | VALARM | Current | RFCXXXX, Section 3.6.6 |
| | | |
| STANDARD | Current | RFCXXXX, Section 3.6.5 | | STANDARD | Current | RFCXXXX, Section 3.6.5 |
| | | |
| DAYLIGHT | Current | RFCXXXX, Section 3.6.5 | | DAYLIGHT | Current | RFCXXXX, Section 3.6.5 |
+-----------+---------+------------------------+ +-----------+---------+------------------------+
8.3.2. Properties Registry 8.3.2. Properties Registry
The following table is to be used to initialize the properties The following table is to be used to initialize the properties
registry. registry.
+------------------+------------+---------------------------+ +------------------+------------+---------------------------+
| Property | Status | Reference | | Property | Status | Reference |
+------------------+------------+---------------------------+ +------------------+------------+---------------------------+
| CALSCALE | Current | RFCXXXX, Section 3.7.1 | | CALSCALE | Current | RFCXXXX, Section 3.7.1 |
| | | |
| METHOD | Current | RFCXXXX, Section 3.7.2 | | METHOD | Current | RFCXXXX, Section 3.7.2 |
| | | |
| PRODID | Current | RFCXXXX, Section 3.7.3 | | PRODID | Current | RFCXXXX, Section 3.7.3 |
| | | |
| VERSION | Current | RFCXXXX, Section 3.7.4 | | VERSION | Current | RFCXXXX, Section 3.7.4 |
| | | |
| ATTACH | Current | RFCXXXX, Section 3.8.1.1 | | ATTACH | Current | RFCXXXX, Section 3.8.1.1 |
| | | |
| CATEGORIES | Current | RFCXXXX, Section 3.8.1.2 | | CATEGORIES | Current | RFCXXXX, Section 3.8.1.2 |
| | | |
| CLASS | Current | RFCXXXX, Section 3.8.1.3 | | CLASS | Current | RFCXXXX, Section 3.8.1.3 |
| | | |
| COMMENT | Current | RFCXXXX, Section 3.8.1.4 | | COMMENT | Current | RFCXXXX, Section 3.8.1.4 |
| | | |
| DESCRIPTION | Current | RFCXXXX, Section 3.8.1.5 | | DESCRIPTION | Current | RFCXXXX, Section 3.8.1.5 |
| | | |
| GEO | Current | RFCXXXX, Section 3.8.1.6 | | GEO | Current | RFCXXXX, Section 3.8.1.6 |
| | | |
| LOCATION | Current | RFCXXXX, Section 3.8.1.7 | | LOCATION | Current | RFCXXXX, Section 3.8.1.7 |
| | | |
| PERCENT-COMPLETE | Current | RFCXXXX, Section 3.8.1.8 | | PERCENT-COMPLETE | Current | RFCXXXX, Section 3.8.1.8 |
| | | |
| PRIORITY | Current | RFCXXXX, Section 3.8.1.9 | | PRIORITY | Current | RFCXXXX, Section 3.8.1.9 |
| | | |
| RESOURCES | Current | RFCXXXX, Section 3.8.1.10 | | RESOURCES | Current | RFCXXXX, Section 3.8.1.10 |
| | | |
| STATUS | Current | RFCXXXX, Section 3.8.1.11 | | STATUS | Current | RFCXXXX, Section 3.8.1.11 |
| | | |
| SUMMARY | Current | RFCXXXX, Section 3.8.1.12 | | SUMMARY | Current | RFCXXXX, Section 3.8.1.12 |
| | | |
| COMPLETED | Current | RFCXXXX, Section 3.8.2.1 | | COMPLETED | Current | RFCXXXX, Section 3.8.2.1 |
| | | |
| DTEND | Current | RFCXXXX, Section 3.8.2.2 | | DTEND | Current | RFCXXXX, Section 3.8.2.2 |
| | | |
| DUE | Current | RFCXXXX, Section 3.8.2.3 | | DUE | Current | RFCXXXX, Section 3.8.2.3 |
| | | |
| DTSTART | Current | RFCXXXX, Section 3.8.2.4 | | DTSTART | Current | RFCXXXX, Section 3.8.2.4 |
| | | |
| DURATION | Current | RFCXXXX, Section 3.8.2.5 | | DURATION | Current | RFCXXXX, Section 3.8.2.5 |
| | | |
| FREEBUSY | Current | RFCXXXX, Section 3.8.2.6 | | FREEBUSY | Current | RFCXXXX, Section 3.8.2.6 |
| | | |
| TRANSP | Current | RFCXXXX, Section 3.8.2.7 | | TRANSP | Current | RFCXXXX, Section 3.8.2.7 |
| | | |
| TZID | Current | RFCXXXX, Section 3.8.3.1 | | TZID | Current | RFCXXXX, Section 3.8.3.1 |
| | | |
| TZNAME | Current | RFCXXXX, Section 3.8.3.2 | | TZNAME | Current | RFCXXXX, Section 3.8.3.2 |
| | | |
| TZOFFSETFROM | Current | RFCXXXX, Section 3.8.3.3 | | TZOFFSETFROM | Current | RFCXXXX, Section 3.8.3.3 |
| | | |
| TZOFFSETTO | Current | RFCXXXX, Section 3.8.3.4 | | TZOFFSETTO | Current | RFCXXXX, Section 3.8.3.4 |
| | | |
| TZURL | Current | RFCXXXX, Section 3.8.3.5 | | TZURL | Current | RFCXXXX, Section 3.8.3.5 |
| | | |
| ATTENDEE | Current | RFCXXXX, Section 3.8.4.1 | | ATTENDEE | Current | RFCXXXX, Section 3.8.4.1 |
| | | |
| CONTACT | Current | RFCXXXX, Section 3.8.4.2 | | CONTACT | Current | RFCXXXX, Section 3.8.4.2 |
| | | |
| ORGANIZER | Current | RFCXXXX, Section 3.8.4.3 | | ORGANIZER | Current | RFCXXXX, Section 3.8.4.3 |
| | | |
| RECURRENCE-ID | Current | RFCXXXX, Section 3.8.4.4 | | RECURRENCE-ID | Current | RFCXXXX, Section 3.8.4.4 |
| | | |
| RELATED-TO | Current | RFCXXXX, Section 3.8.4.5 | | RELATED-TO | Current | RFCXXXX, Section 3.8.4.5 |
| | | |
| URL | Current | RFCXXXX, Section 3.8.4.6 | | URL | Current | RFCXXXX, Section 3.8.4.6 |
| | | |
| UID | Current | RFCXXXX, Section 3.8.4.7 | | UID | Current | RFCXXXX, Section 3.8.4.7 |
| | | |
| EXDATE | Current | RFCXXXX, Section 3.8.5.1 | | EXDATE | Current | RFCXXXX, Section 3.8.5.1 |
| | | |
| EXRULE | Deprecated | RFC2445, Section 4.8.5.2 | | EXRULE | Deprecated | RFC2445, Section 4.8.5.2 |
| | | |
| RDATE | Current | RFCXXXX, Section 3.8.5.2 | | RDATE | Current | RFCXXXX, Section 3.8.5.2 |
| | | |
| RRULE | Current | RFCXXXX, Section 3.8.5.3 | | RRULE | Current | RFCXXXX, Section 3.8.5.3 |
| | | |
| ACTION | Current | RFCXXXX, Section 3.8.6.1 | | ACTION | Current | RFCXXXX, Section 3.8.6.1 |
| | | |
| REPEAT | Current | RFCXXXX, Section 3.8.6.2 | | REPEAT | Current | RFCXXXX, Section 3.8.6.2 |
| | | |
| TRIGGER | Current | RFCXXXX, Section 3.8.6.3 | | TRIGGER | Current | RFCXXXX, Section 3.8.6.3 |
| | | |
| CREATED | Current | RFCXXXX, Section 3.8.7.1 | | CREATED | Current | RFCXXXX, Section 3.8.7.1 |
| | | |
| DTSTAMP | Current | RFCXXXX, Section 3.8.7.2 | | DTSTAMP | Current | RFCXXXX, Section 3.8.7.2 |
| | | |
| LAST-MODIFIED | Current | RFCXXXX, Section 3.8.7.3 | | LAST-MODIFIED | Current | RFCXXXX, Section 3.8.7.3 |
| | | |
| SEQUENCE | Current | RFCXXXX, Section 3.8.7.4 | | SEQUENCE | Current | RFCXXXX, Section 3.8.7.4 |
| | | |
| REQUEST-STATUS | Current | RFCXXXX, Section 3.8.8.3 | | REQUEST-STATUS | Current | RFCXXXX, Section 3.8.8.3 |
+------------------+------------+---------------------------+ +------------------+------------+---------------------------+
8.3.3. Parameters Registry 8.3.3. Parameters Registry
The following table is to be used to initialize the parameters The following table is to be used to initialize the parameters
registry. registry.
+----------------+---------+-------------------------+ +----------------+---------+-------------------------+
| Parameter | Status | Reference | | Parameter | Status | Reference |
+----------------+---------+-------------------------+ +----------------+---------+-------------------------+
| ALTREP | Current | RFCXXXX, Section 3.2.1 | | ALTREP | Current | RFCXXXX, Section 3.2.1 |
| | | |
| CN | Current | RFCXXXX, Section 3.2.2 | | CN | Current | RFCXXXX, Section 3.2.2 |
| | | |
| CUTYPE | Current | RFCXXXX, Section 3.2.3 | | CUTYPE | Current | RFCXXXX, Section 3.2.3 |
| | | |
| DELEGATED-FROM | Current | RFCXXXX, Section 3.2.4 | | DELEGATED-FROM | Current | RFCXXXX, Section 3.2.4 |
| | | |
| DELEGATED-TO | Current | RFCXXXX, Section 3.2.5 | | DELEGATED-TO | Current | RFCXXXX, Section 3.2.5 |
| | | |
| DIR | Current | RFCXXXX, Section 3.2.6 | | DIR | Current | RFCXXXX, Section 3.2.6 |
| | | |
| ENCODING | Current | RFCXXXX, Section 3.2.7 | | ENCODING | Current | RFCXXXX, Section 3.2.7 |
| | | |
| FMTTYPE | Current | RFCXXXX, Section 3.2.8 | | FMTTYPE | Current | RFCXXXX, Section 3.2.8 |
| | | |
| FBTYPE | Current | RFCXXXX, Section 3.2.9 | | FBTYPE | Current | RFCXXXX, Section 3.2.9 |
| | | |
| LANGUAGE | Current | RFCXXXX, Section 3.2.10 | | LANGUAGE | Current | RFCXXXX, Section 3.2.10 |
| | | |
| MEMBER | Current | RFCXXXX, Section 3.2.11 | | MEMBER | Current | RFCXXXX, Section 3.2.11 |
| | | |
| PARTSTAT | Current | RFCXXXX, Section 3.2.12 | | PARTSTAT | Current | RFCXXXX, Section 3.2.12 |
| | | |
| RANGE | Current | RFCXXXX, Section 3.2.13 | | RANGE | Current | RFCXXXX, Section 3.2.13 |
| | | |
| RELATED | Current | RFCXXXX, Section 3.2.14 | | RELATED | Current | RFCXXXX, Section 3.2.14 |
| | | |
| RELTYPE | Current | RFCXXXX, Section 3.2.15 | | RELTYPE | Current | RFCXXXX, Section 3.2.15 |
| | | |
| ROLE | Current | RFCXXXX, Section 3.2.16 | | ROLE | Current | RFCXXXX, Section 3.2.16 |
| | | |
| RSVP | Current | RFCXXXX, Section 3.2.17 | | RSVP | Current | RFCXXXX, Section 3.2.17 |
| | | |
| SENT-BY | Current | RFCXXXX, Section 3.2.18 | | SENT-BY | Current | RFCXXXX, Section 3.2.18 |
| | | |
| TZID | Current | RFCXXXX, Section 3.2.19 | | TZID | Current | RFCXXXX, Section 3.2.19 |
| | | |
| VALUE | Current | RFCXXXX, Section 3.2.20 | | VALUE | Current | RFCXXXX, Section 3.2.20 |
+----------------+---------+-------------------------+ +----------------+---------+-------------------------+
8.3.4. Value Data Types Registry 8.3.4. Value Data Types Registry
The following table is to be used to initialize the value data types The following table is to be used to initialize the value data types
registry. registry.
+-----------------+---------+-------------------------+ +-----------------+---------+-------------------------+
| Value Data Type | Status | Reference | | Value Data Type | Status | Reference |
+-----------------+---------+-------------------------+ +-----------------+---------+-------------------------+
| BINARY | Current | RFCXXXX, Section 3.3.1 | | BINARY | Current | RFCXXXX, Section 3.3.1 |
| | | |
| BOOLEAN | Current | RFCXXXX, Section 3.3.2 | | BOOLEAN | Current | RFCXXXX, Section 3.3.2 |
| | | |
| CAL-ADDRESS | Current | RFCXXXX, Section 3.3.3 | | CAL-ADDRESS | Current | RFCXXXX, Section 3.3.3 |
| | | |
| DATE | Current | RFCXXXX, Section 3.3.4 | | DATE | Current | RFCXXXX, Section 3.3.4 |
| | | |
| DATE-TIME | Current | RFCXXXX, Section 3.3.5 | | DATE-TIME | Current | RFCXXXX, Section 3.3.5 |
| | | |
| DURATION | Current | RFCXXXX, Section 3.3.6 | | DURATION | Current | RFCXXXX, Section 3.3.6 |
| | | |
| FLOAT | Current | RFCXXXX, Section 3.3.7 | | FLOAT | Current | RFCXXXX, Section 3.3.7 |
| | | |
| INTEGER | Current | RFCXXXX, Section 3.3.8 | | INTEGER | Current | RFCXXXX, Section 3.3.8 |
| | | |
| PERIOD | Current | RFCXXXX, Section 3.3.9 | | PERIOD | Current | RFCXXXX, Section 3.3.9 |
| | | |
| RECUR | Current | RFCXXXX, Section 3.3.10 | | RECUR | Current | RFCXXXX, Section 3.3.10 |
| | | |
| TEXT | Current | RFCXXXX, Section 3.3.11 | | TEXT | Current | RFCXXXX, Section 3.3.11 |
| | | |
| TIME | Current | RFCXXXX, Section 3.3.12 | | TIME | Current | RFCXXXX, Section 3.3.12 |
| | | |
| URI | Current | RFCXXXX, Section 3.3.13 | | URI | Current | RFCXXXX, Section 3.3.13 |
| | | |
| UTC-OFFSET | Current | RFCXXXX, Section 3.3.14 | | UTC-OFFSET | Current | RFCXXXX, Section 3.3.14 |
+-----------------+---------+-------------------------+ +-----------------+---------+-------------------------+
8.3.5. Calendar User Types Registry 8.3.5. Calendar User Types Registry
The following table is to be used to initialize the calendar user The following table is to be used to initialize the calendar user
types registry. types registry.
+--------------------+---------+------------------------+ +--------------------+---------+------------------------+
| Calendar User Type | Status | Reference | | Calendar User Type | Status | Reference |
+--------------------+---------+------------------------+ +--------------------+---------+------------------------+
| INDIVIDUAL | Current | RFCXXXX, Section 3.2.3 | | INDIVIDUAL | Current | RFCXXXX, Section 3.2.3 |
| | | |
| GROUP | Current | RFCXXXX, Section 3.2.3 | | GROUP | Current | RFCXXXX, Section 3.2.3 |
| | | |
| RESOURCE | Current | RFCXXXX, Section 3.2.3 | | RESOURCE | Current | RFCXXXX, Section 3.2.3 |
| | | |
| ROOM | Current | RFCXXXX, Section 3.2.3 | | ROOM | Current | RFCXXXX, Section 3.2.3 |
| | | |
| UNKNOWN | Current | RFCXXXX, Section 3.2.3 | | UNKNOWN | Current | RFCXXXX, Section 3.2.3 |
+--------------------+---------+------------------------+ +--------------------+---------+------------------------+
8.3.6. Free/Busy Time Types Registry 8.3.6. Free/Busy Time Types Registry
The following table is to be used to initialize the free/busy time The following table is to be used to initialize the free/busy time
types registry. types registry.
+---------------------+---------+------------------------+ +---------------------+---------+------------------------+
| Free/Busy Time Type | Status | Reference | | Free/Busy Time Type | Status | Reference |
+---------------------+---------+------------------------+ +---------------------+---------+------------------------+
| FREE | Current | RFCXXXX, Section 3.2.9 | | FREE | Current | RFCXXXX, Section 3.2.9 |
| | | |
| BUSY | Current | RFCXXXX, Section 3.2.9 | | BUSY | Current | RFCXXXX, Section 3.2.9 |
| | | |
| BUSY-UNAVAILABLE | Current | RFCXXXX, Section 3.2.9 | | BUSY-UNAVAILABLE | Current | RFCXXXX, Section 3.2.9 |
| | | |
| BUSY-TENTATIVE | Current | RFCXXXX, Section 3.2.9 | | BUSY-TENTATIVE | Current | RFCXXXX, Section 3.2.9 |
+---------------------+---------+------------------------+ +---------------------+---------+------------------------+
8.3.7. Participation Statuses Registry 8.3.7. Participation Statuses Registry
The following table is to be used to initialize the participation The following table is to be used to initialize the participation
statuses registry. statuses registry.
+--------------------+---------+-------------------------+ +--------------------+---------+-------------------------+
| Participant Status | Status | Reference | | Participant Status | Status | Reference |
+--------------------+---------+-------------------------+ +--------------------+---------+-------------------------+
| NEEDS-ACTION | Current | RFCXXXX, Section 3.2.12 | | NEEDS-ACTION | Current | RFCXXXX, Section 3.2.12 |
| | | |
| ACCEPTED | Current | RFCXXXX, Section 3.2.12 | | ACCEPTED | Current | RFCXXXX, Section 3.2.12 |
| | | |
| DECLINED | Current | RFCXXXX, Section 3.2.12 | | DECLINED | Current | RFCXXXX, Section 3.2.12 |
| | | |
| TENTATIVE | Current | RFCXXXX, Section 3.2.12 | | TENTATIVE | Current | RFCXXXX, Section 3.2.12 |
| | | |
| DELEGATED | Current | RFCXXXX, Section 3.2.12 | | DELEGATED | Current | RFCXXXX, Section 3.2.12 |
| | | |
| COMPLETED | Current | RFCXXXX, Section 3.2.12 | | COMPLETED | Current | RFCXXXX, Section 3.2.12 |
| | | |
| IN-PROCESS | Current | RFCXXXX, Section 3.2.12 | | IN-PROCESS | Current | RFCXXXX, Section 3.2.12 |
+--------------------+---------+-------------------------+ +--------------------+---------+-------------------------+
8.3.8. Relationship Types Registry 8.3.8. Relationship Types Registry
The following table is to be used to initialize the property The following table is to be used to initialize the property
parameters registry. parameters registry.
+-------------------+---------+-------------------------+ +-------------------+---------+-------------------------+
| Relationship Type | Status | Reference | | Relationship Type | Status | Reference |
+-------------------+---------+-------------------------+ +-------------------+---------+-------------------------+
| CHILD | Current | RFCXXXX, Section 3.2.15 | | CHILD | Current | RFCXXXX, Section 3.2.15 |
| | | |
| PARENT | Current | RFCXXXX, Section 3.2.15 | | PARENT | Current | RFCXXXX, Section 3.2.15 |
| | | |
| SIBLING | Current | RFCXXXX, Section 3.2.15 | | SIBLING | Current | RFCXXXX, Section 3.2.15 |
+-------------------+---------+-------------------------+ +-------------------+---------+-------------------------+
8.3.9. Participation Roles Registry 8.3.9. Participation Roles Registry
The following table is to be used to initialize the participation The following table is to be used to initialize the participation
roles registry. roles registry.
+-----------------+---------+-------------------------+ +-----------------+---------+-------------------------+
| Role Type | Status | Reference | | Role Type | Status | Reference |
+-----------------+---------+-------------------------+ +-----------------+---------+-------------------------+
| CHAIR | Current | RFCXXXX, Section 3.2.16 | | CHAIR | Current | RFCXXXX, Section 3.2.16 |
| | | |
| REQ-PARTICIPANT | Current | RFCXXXX, Section 3.2.16 | | REQ-PARTICIPANT | Current | RFCXXXX, Section 3.2.16 |
| | | |
| OPT-PARTICIPANT | Current | RFCXXXX, Section 3.2.16 | | OPT-PARTICIPANT | Current | RFCXXXX, Section 3.2.16 |
| | | |
| NON-PARTICIPANT | Current | RFCXXXX, Section 3.2.16 | | NON-PARTICIPANT | Current | RFCXXXX, Section 3.2.16 |
+-----------------+---------+-------------------------+ +-----------------+---------+-------------------------+
8.3.10. Actions Registry 8.3.10. Actions Registry
The following table is to be used to initialize the actions registry. The following table is to be used to initialize the actions registry.
+-----------+------------+--------------------------+ +-----------+------------+--------------------------+
| Action | Status | Reference | | Action | Status | Reference |
+-----------+------------+--------------------------+ +-----------+------------+--------------------------+
| AUDIO | Current | RFCXXXX, Section 3.8.6.1 | | AUDIO | Current | RFCXXXX, Section 3.8.6.1 |
| | | |
| DISPLAY | Current | RFCXXXX, Section 3.8.6.1 | | DISPLAY | Current | RFCXXXX, Section 3.8.6.1 |
| | | |
| EMAIL | Current | RFCXXXX, Section 3.8.6.1 | | EMAIL | Current | RFCXXXX, Section 3.8.6.1 |
| | | |
| PROCEDURE | Deprecated | RFC2445, Section 4.8.6.1 | | PROCEDURE | Deprecated | RFC2445, Section 4.8.6.1 |
+-----------+------------+--------------------------+ +-----------+------------+--------------------------+
8.3.11. Classifications Registry 8.3.11. Classifications Registry
The following table is to be used to initialize the classifications The following table is to be used to initialize the classifications
registry. registry.
+----------------+---------+--------------------------+ +----------------+---------+--------------------------+
| Classification | Status | Reference | | Classification | Status | Reference |
+----------------+---------+--------------------------+ +----------------+---------+--------------------------+
| PUBLIC | Current | RFCXXXX, Section 3.8.1.3 | | PUBLIC | Current | RFCXXXX, Section 3.8.1.3 |
| | | |
| PRIVATE | Current | RFCXXXX, Section 3.8.1.3 | | PRIVATE | Current | RFCXXXX, Section 3.8.1.3 |
| | | |
| CONFIDENTIAL | Current | RFCXXXX, Section 3.8.1.3 | | CONFIDENTIAL | Current | RFCXXXX, Section 3.8.1.3 |
+----------------+---------+--------------------------+ +----------------+---------+--------------------------+
8.3.12. Methods Registry 8.3.12. Methods Registry
No values are defined in this document for the "METHOD" property. No values are defined in this document for the "METHOD" property.
9. Acknowledgements 9. Acknowledgements
The editor of this document wish to thank Frank Dawson and Derik The editor of this document wish to thank Frank Dawson and Derik
Stenerson, the original authors of RFC2445, as well as the following Stenerson, the original authors of RFC2445, as well as the following
individuals who have participated in the drafting, review and individuals who have participated in the drafting, review and
discussion of this memo: discussion of this memo:
Joe Abley, Hervey Allen, Jay Batson, Oliver Block, Stephane Joe Abley, Hervey Allen, Steve Allen, Jay Batson, Oliver Block,
Bortzmeyer, Chris Bryant, Tantek Celik, Mark Crispin, Cyrus Daboo, Stephane Bortzmeyer, Chris Bryant, Tantek Celik, Mark Crispin, Cyrus
Mike Douglass, Andrew N. Dowden, Lisa Dusseault, Ned Freed, Ted Daboo, Mike Douglass, Andrew N. Dowden, Lisa Dusseault, Gren Eliot,
Hardie, Tim Hare, Jeffrey Harris, Helge Hess, Leif Johansson, Ben Fortuna, Ned Freed, Neal Gafter, Ted Hardie, Tim Hare, Jeffrey
Reinhold Kainhofer, Eliot Lear, Michiel van Leeuwen, Jonathan Lennox, Harris, Helge Hess, Paul B. Hill, Thomas Hnetila, Leif Johansson,
Jeff McCullough, Bill McQuillan, Alexey Melnikov, Aki Niemi, John W. Ciny Joy, Bruce Kahn, Reinhold Kainhofer, Martin Kiff, Eliot Lear,
Noerenberg II, Chuck Norris, Mark Paterson, Simon Pilette, Arnaud Michiel van Leeuwen, Jonathan Lennox, Jeff McCullough, Bill
Quillaud, Robert Ransdell, Julian F. Reschke, Caleb Richardson, Sam McQuillan, Alexey Melnikov, Aki Niemi, John W. Noerenberg II, Chuck
Roberts, George Sexton, Nigel Swinson, Simon Vaillancourt, and Sandy Norris, Mark Paterson, Simon Pilette, Arnaud Quillaud, Robert
Wills. Ransdell, Julian F. Reschke, Caleb Richardson, Sam Roberts, Mike
Samuel, George Sexton, Nigel Swinson, Clint Talbert, Simon
Vaillancourt, and Sandy Wills.
The editor would also like to thank the Calendaring and Scheduling The editor would also like to thank the Calendaring and Scheduling
Consortium for advice with this specification, and for organizing Consortium for advice with this specification, and for organizing
interoperability testing events to help refine it. interoperability testing events to help refine it.
10. References 10. References
10.1. Normative References 10.1. Normative References
[ISO.8601.2004] International Organization for [ISO.8601.2004] International Organization for
skipping to change at page 166, line 26 skipping to change at page 171, line 22
interchange -- Representation of dates interchange -- Representation of dates
and times", 2004. and times", 2004.
[ISO.9070.1991] International Organization for [ISO.9070.1991] International Organization for
Standardization, "Information Standardization, "Information
Technology_SGML Support Facilities -- Technology_SGML Support Facilities --
Registration Procedures for Public Registration Procedures for Public
Text Owner Identifiers, Second Text Owner Identifiers, Second
Edition", April 1991. Edition", April 1991.
[RFC1738] Berners-Lee, T., Masinter, L., and M.
McCahill, "Uniform Resource Locators
(URL)", RFC 1738, December 1994.
[RFC2045] Freed, N. and N. Borenstein, [RFC2045] Freed, N. and N. Borenstein,
"Multipurpose Internet Mail Extensions "Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet (MIME) Part One: Format of Internet
Message Bodies", RFC 2045, Message Bodies", RFC 2045,
November 1996. November 1996.
[RFC2046] Freed, N. and N. Borenstein, [RFC2046] Freed, N. and N. Borenstein,
"Multipurpose Internet Mail Extensions "Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types", (MIME) Part Two: Media Types",
RFC 2046, November 1996. RFC 2046, November 1996.
skipping to change at page 167, line 21 skipping to change at page 172, line 21
October 2006. October 2006.
[RFC5234] Crocker, D. and P. Overell, "Augmented [RFC5234] Crocker, D. and P. Overell, "Augmented
BNF for Syntax Specifications: ABNF", BNF for Syntax Specifications: ABNF",
STD 68, RFC 5234, January 2008. STD 68, RFC 5234, January 2008.
10.2. Informative References 10.2. Informative References
[I-D.ietf-calsify-2446bis] Daboo, C., "iCalendar Transport- [I-D.ietf-calsify-2446bis] Daboo, C., "iCalendar Transport-
Independent Interoperability Protocol Independent Interoperability Protocol
(iTIP)", draft-ietf-calsify-2446bis-04 (iTIP)", draft-ietf-calsify-2446bis-07
(work in progress), November 2007. (work in progress), July 2008.
[I-D.ietf-calsify-rfc2447bis] Melnikov, A., "iCalendar Message-Based [I-D.ietf-calsify-rfc2447bis] Melnikov, A., "iCalendar Message-Based
Interoperability Protocol(iMIP)", Interoperability Protocol(iMIP)",
draft-ietf-calsify-rfc2447bis-03 (work draft-ietf-calsify-rfc2447bis-05 (work
in progress), February 2007. in progress), June 2008.
[RFC2392] Levinson, E., "Content-ID and [RFC2392] Levinson, E., "Content-ID and
Message-ID Uniform Resource Locators", Message-ID Uniform Resource Locators",
RFC 2392, August 1998. RFC 2392, August 1998.
[RFC2397] Masinter, L., "The "data" URL scheme",
RFC 2397, August 1998.
[RFC2425] Howes, T., Smith, M., and F. Dawson, [RFC2425] Howes, T., Smith, M., and F. Dawson,
"A MIME Content-Type for Directory "A MIME Content-Type for Directory
Information", RFC 2425, Information", RFC 2425,
September 1998. September 1998.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME [RFC2426] Dawson, F. and T. Howes, "vCard MIME
Directory Profile", RFC 2426, Directory Profile", RFC 2426,
September 1998. September 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, J.,
Frystyk, H., Masinter, L., Leach, P.,
and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1",
RFC 2616, June 1999.
[RFC2818] Rescorla, E., "HTTP Over TLS",
RFC 2818, May 2000.
[RFC4516] Smith, M. and T. Howes, "Lightweight [RFC4516] Smith, M. and T. Howes, "Lightweight
Directory Access Protocol (LDAP): Directory Access Protocol (LDAP):
Uniform Resource Locator", RFC 4516, Uniform Resource Locator", RFC 4516,
June 2006. June 2006.
[RFC4791] Daboo, C., Desruisseaux, B., and L. [RFC4791] Daboo, C., Desruisseaux, B., and L.
Dusseault, "Calendaring Extensions to Dusseault, "Calendaring Extensions to
WebDAV (CalDAV)", RFC 4791, WebDAV (CalDAV)", RFC 4791,
March 2007. March 2007.
skipping to change at page 168, line 46 skipping to change at page 175, line 26
2. The "RRULE" property SHOULD NOT occur more than once in a 2. The "RRULE" property SHOULD NOT occur more than once in a
component. component.
3. The BYHOUR, BYMINUTE and BYSECOND rule parts MUST NOT be 3. The BYHOUR, BYMINUTE and BYSECOND rule parts MUST NOT be
specified in the "RRULE" property when the "DTSTART" property is specified in the "RRULE" property when the "DTSTART" property is
specified as a DATE value. specified as a DATE value.
4. The value type of the "DTEND" or "DUE" properties MUST match the 4. The value type of the "DTEND" or "DUE" properties MUST match the
value type of "DTSTART" property. value type of "DTSTART" property.
5. The "DURATION" property can no longer appear in "VFREEBUSY"
components.
A.2. Restrictions removed A.2. Restrictions removed
1. The "DTSTART" and "DTEND" properties are no longer required to be 1. The "DTSTART" and "DTEND" properties are no longer required to be
specified as date with local time and time zone reference when specified as date with local time and time zone reference when
used with a recurrence rule. used with a recurrence rule.
A.3. Deprecated features A.3. Deprecated features
1. The "EXRULE" property can no longer be specified in a component. 1. The "EXRULE" property can no longer be specified in a component.
2. The "THISANDPRIOR" value can no longer be used with the "RANGE" 2. The "THISANDPRIOR" value can no longer be used with the "RANGE"
parameter. parameter.
3. The "PROCEDURE" value can no longer be used with the "ACTION" 3. The "PROCEDURE" value can no longer be used with the "ACTION"
property. property.
4. x-name rule parts can no longer be specified in properties of 4. The value type RECUR no longer allow multiple values to be
RECUR value type (e.g., RRULE). x-param can be used on RECUR specified by a COMMA (US-ASCII decimal 44) character separated
list of values.
5. x-name rule parts can no longer be specified in properties of
RECUR value type (e.g., "RRULE"). x-param can be used on RECUR
value type properties instead. value type properties instead.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -08 B.1. Changes in -09
A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-09.changes.html.
a. Issue 60: Clarified that multi-valued properties MUST NOT be used
to specify multiple language variants of the same value.
b. Issue 67: Forbid the use of the "DURATION" property in
"VFREEBUSY" components.
c. AD-Issue 1: Added note on most commonly used URI schemes for the
"ALTREP" parameter.
d. AD-Issue 2: Added recommendation on the URI schemes to use for
the "DIR" parameter.
e. AD-Issue 4: Added recommendation for calendar applications that
support importing iCalendar objects.
f. iTIP-APPS-Issue 1: Allowed "DTSTART" to be OPTIONAL for iTIP.
g. iTIP-APPS-Issue 2: Fixed time zone example.
h. iTIP-APPS-Issue 3: Clarified that recurrence instances MAY have
different sequence numbers.
i. iTIP-APPS-Issue 4: Clarified description of the "INTERVAL" rule
part.
j. Modified TSAFE-CHAR to allow HTAB (US-ASCII decimal 9) in TEXT
values.
k. Few editorial changes.
l. Added names to the Acknowledgments section.
B.2. Changes in -08
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-08.changes.html. draft-ietf-calsify-rfc2445bis-08.changes.html.
a. Issue 48: Revert the change to deprecate the "RANGE" parameter. a. Issue 48: Revert the change to deprecate the "RANGE" parameter.
Only the value "THISANDPRIOR" is deprecated. Only the value "THISANDPRIOR" is deprecated.
b. Issue 81: BYSETPOS: Clarify that "a set" starts at the beginning b. Issue 81: BYSETPOS: Clarify that "a set" starts at the beginning
of the interval defined by the FREQ rule part. of the interval defined by the FREQ rule part.
skipping to change at page 170, line 11 skipping to change at page 177, line 37
i. Removed the text that specifies when the sequence number MUST be i. Removed the text that specifies when the sequence number MUST be
incremented. Text will be added to rfc2446bis. incremented. Text will be added to rfc2446bis.
j. Removed normative reference to RFC2822. j. Removed normative reference to RFC2822.
k. Changed reference of RFC4234 to RFC5234. k. Changed reference of RFC4234 to RFC5234.
l. Few editorial changes. l. Few editorial changes.
B.2. Changes in -07 B.3. Changes in -07
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-07.changes.html. draft-ietf-calsify-rfc2445bis-07.changes.html.
a. Issue 8: Clarified how to compute the exact duration of a nominal a. Issue 8: Clarified how to compute the exact duration of a nominal
duration. duration.
b. Issue 10: Added new examples for "VEVENT" and "VTODO" to b. Issue 10: Added new examples for "VEVENT" and "VTODO" to
demonstrate that end times are always non-inclusive, that is, demonstrate that end times are always non-inclusive, that is,
skipping to change at page 171, line 33 skipping to change at page 179, line 12
s. Clarified some differences with ISO 8601. s. Clarified some differences with ISO 8601.
t. Updated reference to CalDAV and ISO 8601. t. Updated reference to CalDAV and ISO 8601.
u. Updated section "Differences from RFC 2445": added new u. Updated section "Differences from RFC 2445": added new
restrictions and added list of removed restrictions. restrictions and added list of removed restrictions.
v. Numerous editorial changes. v. Numerous editorial changes.
B.3. Changes in -06 B.4. Changes in -06
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-06.changes.html. draft-ietf-calsify-rfc2445bis-06.changes.html.
a. Issue 19: Defined new IANA registries. [Work in progress]; a. Issue 19: Defined new IANA registries. [Work in progress];
b. Issue 23: Clarified that the UNTIL rule part MUST specify a value b. Issue 23: Clarified that the UNTIL rule part MUST specify a value
of the same type as the value specified by "DTSTART"; of the same type as the value specified by "DTSTART";
skipping to change at page 173, line 4 skipping to change at page 180, line 31
p. Issue 74: Deprecated the "PROCEDURE" value for the "ACTION" p. Issue 74: Deprecated the "PROCEDURE" value for the "ACTION"
property; property;
q. Issue 78: Fixed the text to specify that "TZOFFSETFROM" and not q. Issue 78: Fixed the text to specify that "TZOFFSETFROM" and not
"TZOFFSETTO" must be used with "DTSTART" when generating the "TZOFFSETTO" must be used with "DTSTART" when generating the
onset date-time values from the "RRULE" in a "VTIMEZONE" onset date-time values from the "RRULE" in a "VTIMEZONE"
component; component;
r. Clarified that the "DTSTART" property MUST be specified in a r. Clarified that the "DTSTART" property MUST be specified in a
"VTODO" component when the "DURATION" property is specified; "VTODO" component when the "DURATION" property is specified;
s. Started to update the time zone information / examples; s. Started to update the time zone information / examples;
t. Numerous editorial changes. t. Numerous editorial changes.
B.4. Changes in -05 B.5. Changes in -05
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-05.changes.html. draft-ietf-calsify-rfc2445bis-05.changes.html.
a. Fixed ABNF with references in .txt version of the draft; a. Fixed ABNF with references in .txt version of the draft;
b. Numerous editorial changes; b. Numerous editorial changes;
c. Clarified that normative statements in ABNF comments should be c. Clarified that normative statements in ABNF comments should be
skipping to change at page 173, line 38 skipping to change at page 181, line 18
g. Changed the partstatparam ABNF rule for clarity; g. Changed the partstatparam ABNF rule for clarity;
h. Clarified the purpose of negative durations; h. Clarified the purpose of negative durations;
i. Added informational references to RFC 2392 (CID URL) and RFC 4516 i. Added informational references to RFC 2392 (CID URL) and RFC 4516
(LDAP URL). (LDAP URL).
j. Updated TZDB reference. j. Updated TZDB reference.
B.5. Changes in -04 B.6. Changes in -04
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-04.changes.html. draft-ietf-calsify-rfc2445bis-04.changes.html.
a. Issue 16: Clarified that recurrence instances, generated by a a. Issue 16: Clarified that recurrence instances, generated by a
recurrence rule, with an invalid date or nonexistent local time recurrence rule, with an invalid date or nonexistent local time
must be ignored and not counted as part of the recurrence set. must be ignored and not counted as part of the recurrence set.
b. Issue 26: Clarified how to handle the BYHOUR, BYMINUTE and b. Issue 26: Clarified how to handle the BYHOUR, BYMINUTE and
skipping to change at page 175, line 12 skipping to change at page 182, line 39
specified as a "dur-day" or "dur-week" value when the "DTSTART" specified as a "dur-day" or "dur-week" value when the "DTSTART"
is a DATE. is a DATE.
q. Issue 58: Changed the jourprop ABNF rule to allow the q. Issue 58: Changed the jourprop ABNF rule to allow the
"DESCRIPTION" property to occur more than once. "DESCRIPTION" property to occur more than once.
r. Numerous editorial changes. r. Numerous editorial changes.
s. Changed reference to RFC 4646 for Language-Tag. s. Changed reference to RFC 4646 for Language-Tag.
B.6. Changes in -03 B.7. Changes in -03
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-03.changes.html. draft-ietf-calsify-rfc2445bis-03.changes.html.
a. Numerous editorial changes. a. Numerous editorial changes.
b. Specified that "DTSTART" should match the pattern of "RRULE" and b. Specified that "DTSTART" should match the pattern of "RRULE" and
is always part of the "COUNT". is always part of the "COUNT".
skipping to change at page 175, line 34 skipping to change at page 183, line 13
components. components.
d. Deprecated "EXRULE". d. Deprecated "EXRULE".
e. Fixed all ABNF errors reported by Bill Fenner's ABNF parsing web e. Fixed all ABNF errors reported by Bill Fenner's ABNF parsing web
service available at: service available at:
http://rtg.ietf.org/~fenner/abnf.cgi. http://rtg.ietf.org/~fenner/abnf.cgi.
f. Changed reference to RFC 4648 for Base64 encoding. f. Changed reference to RFC 4648 for Base64 encoding.
B.7. Changes in -02 B.8. Changes in -02
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-02.changes.html. draft-ietf-calsify-rfc2445bis-02.changes.html.
a. Numerous editorial changes including the typos listed in the a. Numerous editorial changes including the typos listed in the
"RFC2445 Errata": "RFC2445 Errata":
http://www.rfc-editor.org/cgi-bin/errataSearch.pl?rfc=2445& http://www.rfc-editor.org/cgi-bin/errataSearch.pl?rfc=2445&
and in the "RFC2445 Issues List": and in the "RFC2445 Issues List":
http://www.softwarestudio.org/iCal/2445Issues.html. http://www.softwarestudio.org/iCal/2445Issues.html.
skipping to change at page 176, line 20 skipping to change at page 183, line 46
g. Fixed all the examples to use RFC2606-compliant FQDNs. g. Fixed all the examples to use RFC2606-compliant FQDNs.
h. Fixed the Content-ID URLs in the examples. h. Fixed the Content-ID URLs in the examples.
i. Fixed the LDAP URLs in the examples. i. Fixed the LDAP URLs in the examples.
j. Moved multiple references in the Informative References section. j. Moved multiple references in the Informative References section.
k. Updated the Acknowledgments section. k. Updated the Acknowledgments section.
B.8. Changes in -01 B.9. Changes in -01
A detailed list of changes is available at the following page: A detailed list of changes is available at the following page:
http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/ http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/
draft-ietf-calsify-rfc2445bis-01.changes.html. draft-ietf-calsify-rfc2445bis-01.changes.html.
a. Numerous editorial changes (typos, errors in examples, etc.). a. Numerous editorial changes (typos, errors in examples, etc.).
b. Fixed invalid media types in examples. b. Fixed invalid media types in examples.
c. Fixed the "DTSTAMP" values in the examples. c. Fixed the "DTSTAMP" values in the examples.
skipping to change at page 177, line 44 skipping to change at line 8119
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 198 change blocks. 
258 lines changed or deleted 442 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/