Home Library Learn Samples Downloads Support Community Forums
MSDN Library
Open Specifications
Standards
Microsoft Exchange Server and Outlook Standards
[MS-STANOICAL]: Outlook iCalendar Standards Support
2 Standards Support Statements
2.2 Clarifications
2.2.1 [RFC5545] Section 3.1, Content Lines
2.2.2 [RFC5545] Section 3.1.2, Multiple Values
2.2.3 [RFC5545] Section 3.1.3, Binary Content
2.2.4 [RFC5545] Section 3.1.4, Character Set
2.2.5 [RFC5545] Section 3.2, Property Parameters
2.2.6 [RFC5545] Section 3.2.1, Alternate Text Representation
2.2.7 [RFC5545] Section 3.2.2, Common Name
2.2.8 [RFC5545] Section 3.2.3, Calendar User Type
2.2.9 [RFC5545] Section 3.2.4, Delegators
2.2.10 [RFC5545] Section 3.2.5, Delegatees
2.2.11 [RFC5545] Section 3.2.6, Directory Entry Reference
2.2.12 [RFC5545] Section 3.2.7, Inline Encoding
2.2.13 [RFC5545] Section 3.2.8, Format Type
2.2.14 [RFC5545] Section 3.2.9, Free/Busy Time Type
2.2.15 [RFC5545] Section 3.2.10, Language
2.2.16 [RFC5545] Section 3.2.11, Group or List Membership
2.2.17 [RFC5545] Section 3.2.12, Participation Status
2.2.18 [RFC5545] Section 3.2.13, Recurrence Identifier Range
2.2.19 [RFC5545] Section 3.2.14, Alarm Trigger Relationship
2.2.20 [RFC5545] Section 3.2.15, Relationship Type
2.2.21 [RFC5545] Section 3.2.16, Participation Role
2.2.22 [RFC5545] Section 3.2.17, RSVP Expectation
2.2.23 [RFC5545] Section 3.2.18, Sent By
2.2.24 [RFC5545] Section 3.2.19, Time Zone Identifier
2.2.25 [RFC5545] Section 3.2.20, Value Data Types
2.2.26 [RFC5545] Section 3.3, Property Value Data Types
2.2.27 [RFC5545] Section 3.3.1, Binary
2.2.28 [RFC5545] Section 3.3.2, Boolean
2.2.29 [RFC5545] Section 3.3.3, Calendar User Address
2.2.30 [RFC5545] Section 3.3.4, Date
2.2.31 [RFC5545] Section 3.3.5, Date-Time
2.2.32 [RFC5545] Section 3.3.6, Duration
2.2.33 [RFC5545] Section 3.3.7, Float
2.2.34 [RFC5545] Section 3.3.8, Integer
2.2.35 [RFC5545] Section 3.3.9, Period of Time
2.2.36 [RFC5545] Section 3.3.10, Recurrence Rule
2.2.37 [RFC5545] Section 3.3.11, Text
2.2.38 [RFC5545] Section 3.3.12, Time
2.2.39 [RFC5545] Section 3.3.13, URI
2.2.40 [RFC5545] Section 3.3.14, UTC Offset
2.2.41 [RFC5545] Section 3.4, iCalendar Object
2.2.42 [RFC5545] Section 3.5, Property
2.2.43 [RFC5545] Section 3.6, Calendar Components
2.2.44 [RFC5545] Section 3.6.2, To-do Component
2.2.45 [RFC5545] Section 3.6.3, Journal Component
2.2.46 [RFC5545] Section 3.6.4, Free/Busy Component
2.2.47 [RFC5545] Section 3.6.5, Time Zone Component
2.2.48 [RFC5545] Section 3.6.6, Alarm Component
2.2.49 [RFC5545] Section 3.7, Calendar Properties
2.2.50 [RFC5545] Section 3.7.1, Calendar Scale
2.2.51 [RFC5545] Section 3.7.2, Method
2.2.52 [RFC5545] Section 3.7.3, Product Identifier
2.2.53 [RFC5545] Section 3.7.4, Version
2.2.54 [RFC5545] Section 3.8.1.1, Attachment
2.2.55 [RFC5545] Section 3.8.1.2, Categories
2.2.56 [RFC5545] Section 3.8.1.3, Classification
2.2.57 [RFC5545] Section 3.8.1.4, Comment
2.2.58 [RFC5545] Section 3.8.1.5, Description
2.2.59 [RFC5545] Section 3.8.1.6, Geographic Position
2.2.60 [RFC5545] Section 3.8.1.7, Location
2.2.61 [RFC5545] Section 3.8.1.8, Percent Complete
2.2.62 [RFC5545] Section 3.8.1.9, Priority
2.2.63 [RFC5545] Section 3.8.1.10, Resources
2.2.64 [RFC5545] Section 3.8.1.11, Status
2.2.65 [RFC5545] Section 3.8.1.12, Summary
2.2.66 [RFC5545] Section 3.8.2.1, Date-Time Completed
2.2.67 [RFC5545] Section 3.8.2.2, Date-Time End
2.2.68 [RFC5545] Section 3.8.2.3 Date-Time Due
2.2.69 [RFC5545] Section 3.8.2.4 Date-Time Start
2.2.70 [RFC5545] Section 3.8.2.5 Duration
2.2.71 [RFC5545] Section 3.8.2.6 Free/Busy Time
2.2.72 [RFC5545] Section 3.8.2.7 Time Transparency
2.2.73 [RFC5545] Section 3.8.3.1 Time Zone Identifier
2.2.74 [RFC5545] Section 3.8.3.2 Time Zone Name
2.2.75 [RFC5545] Section 3.8.3.3 Time Zone Offset From
2.2.76 [RFC5545] Section 3.8.3.4 Time Zone Offset To
2.2.77 [RFC5545] Section 3.8.3.5 Time Zone URL
2.2.78 [RFC5545] Section 3.8.4.1 Attendee
2.2.79 [RFC5545] Section 3.8.4.2 Contact
2.2.80 [RFC5545] Section 3.8.4.3 Organizer
2.2.81 [RFC5545] Section 3.8.4.4 Recurrence ID
2.2.82 [RFC5545] Section 3.8.4.5 Related To
2.2.83 [RFC5545] Section 3.8.4.6 Uniform Resource Locator
2.2.84 [RFC5545] Section 3.8.4.7 Unique Identifier
2.2.85 [RFC5545] Section 3.8.5.1 Exception Date-Times
2.2.86 [RFC5545] Section 3.8.5.2 Recurrence Date-Times
2.2.87 [RFC5545] Section 3.8.5.3 Recurrence Rule
2.2.88 [RFC5545] Section 3.8.6.1 Action
2.2.89 [RFC5545] Section 3.8.6.2 Repeat Count
2.2.90 [RFC5545] Section 3.8.6.3 Trigger
2.2.91 [RFC5545] Section 3.8.7.1 Date-Time Created
2.2.92 [RFC5545] Section 3.8.7.2 Date-Time Stamp
2.2.93 [RFC5545] Section 3.8.7.3 Last Modified
2.2.94 [RFC5545] Section 3.8.7.4 Sequence Number
2.2.95 [RFC5545] Section 3.8.8.2 Non-standard Properties
2.2.96 [RFC5545] Section 3.8.8.3 Request Status
2.2.97 [RFC5545] Section 5 Recommended Practices
2.2.98 [RFC5545] Section 8.1 iCalendar Media Type Registration
2.2.99 [RFC5546] Section 2 Interoperability Models
2.2.100 [RFC5546] Section 2.1 Application Protocol
2.2.101 [RFC5546] Section 2.1.3 Acting on Behalf of Other Calendar Users
2.2.102 [RFC5546] Section 2.1.4 Component Revisions
2.2.103 [RFC5546] Section 2.1.5 Message Sequencing
2.2.104 [RFC5546] Section 3 Application Protocol Elements
2.2.105 [RFC5546] Section 3.1.1 VCALENDAR
2.2.106 [RFC5546] Section 3.1.2 VTIMEZONE
2.2.107 [RFC5546] Section 3.1.3 VALARM
2.2.108 [RFC5546] Section 3.2 Methods for VEVENT Calendar Components
2.2.109 [RFC5546] Section 3.2.1 PUBLISH
2.2.110 [RFC5546] Section 3.2.2 REQUEST
2.2.111 [RFC5546] Section 3.2.2.1 Rescheduling an Event
2.2.112 [RFC5546] Section 3.2.2.2 Updating or Reconfirmation of an Event
2.2.113 [RFC5546] Section 3.2.2.3 Delegating an Event to Another CU
2.2.114 [RFC5546] Section 3.2.2.4 Changing the Organizer
2.2.115 [RFC5546] Section 3.2.2.5 Sending on Behalf of the Organizer
2.2.116 [RFC5546] Section 3.2.2.6 Forwarding to an Uninvited CU
2.2.117 [RFC5546] Section 3.2.2.7 Updating Attendee Status
2.2.118 [RFC5546] Section 3.2.3 REPLY
2.2.119 [RFC5546] Section 3.2.4 ADD
2.2.120 [RFC5546] Section 3.2.5 CANCEL
2.2.121 [RFC5546] Section 3.2.6 REFRESH
2.2.122 [RFC5546] Section 3.2.7 COUNTER
2.2.123 [RFC5546] Section 3.2.8 DECLINECOUNTER
2.2.124 [RFC5546] Section 3.3 Methods for VFREEBUSY Components
2.2.125 [RFC5546] Section 3.3.1 PUBLISH
2.2.126 [RFC5546] Section 3.3.2 REQUEST
2.2.127 [RFC5546] Section 3.3.3 REPLY
2.2.128 [RFC5546] Section 3.4 Methods for VTODO Components
2.2.129 [RFC5546] Section 3.4.1 PUBLISH
2.2.130 [RFC5546] Section 3.4.2 REQUEST
2.2.131 [RFC5546] Section 3.4.3 REPLY
2.2.132 [RFC5546] Section 3.4.4 ADD
2.2.133 [RFC5546] Section 3.4.5 CANCEL
2.2.134 [RFC5546] Section 3.4.6 REFRESH
2.2.135 [RFC5546] Section 3.4.7 COUNTER
2.2.136 [RFC5546] Section 3.4.8 DECLINECOUNTER
2.2.137 [RFC5546] Section 3.5 Methods for VJOURNAL Components
2.2.138 [RFC5546] Section 3.5.1 PUBLISH
2.2.139 [RFC5546] Section 3.5.2 ADD
2.2.140 [RFC5546] Section 3.5.3 CANCEL
2.2.141 [RFC5546] Section 3.6 Status Replies
2.2.142 [RFC5546] Section 3.7.1 Working with Recurrence Instances
2.2.143 [RFC5546] Section 3.7.2 Attendee Property Considerations
2.2.144 [RFC5546] Section 3.7.3 X-Tokens
2.2.145 [RFC5546] Section 5.1 Partial Implementation
2.2.146 [RFC5546] Section 5.1.1 Event-Related Fallbacks
2.2.147 [RFC5546] Section 5.1.2 Free/Busy-Related Fallbacks
2.2.148 [RFC5546] Section 5.1.2 To-Do-Related Fallbacks
2.2.149 [RFC5546] Section 5.1.2 Journal-Related Fallbacks
2.2.150 [RFC5546] Section 5.2.1 Cancellation of an Unknown Calendar Component
2.2.151 [RFC5546] Section 5.2.2 Unexpected Reply from an Unknown Delegate
2.2.152 [RFC5546] Section 5.3 Sequence Number
2.2.153 [RFC5546] Section 6.1.1 Spoofing the Organizer
2.2.154 [RFC5546] Section 6.1.2 Spoofing the Attendee
2.2.155 [RFC5546] Section 6.1.3 Unauthorized Replacement of the Organizer
2.2.156 [RFC5546] Section 6.1.4 Eavesdropping and Data Integrity
2.2.157 [RFC5546] Section 6.1.5 Flooding a Calendar
2.2.158 [RFC5546] Section 6.1.6 Unauthorized Refresh Requests
2.2.159 [RFC5546] Section 6.2 Recommendations
2.2.160 [RFC5546] Section 6.2.1 Securing iTIP Transactions
2.2.161 [RFC5546] Section 6.2.2 Implementation Controls
2.2.162 [RFC6047] Section 1.1 Related Memos
2.2.163 [RFC6047] Section 2.1 MIME Media Type
2.2.164 [RFC6047] Section 2.2.1 Authorization
2.2.165 [RFC6047] Section 2.2.2 Authentication
2.2.166 [RFC6047] Section 2.2.3 Confidentiality
2.2.167 [RFC6047] Section 2.3 Email Addresses
2.2.168 [RFC6047] Section 2.4 Content-Type Header Field
2.2.169 [RFC6047] Section 2.5 Content-Transfer-Encoding Header Field
2.2.170 [RFC6047] Section 2.6 Content-Disposition Header Field
2.2.171 [RFC6047] Section 3 Security Considerations
2.2.172 [RFC6047] Section 4.1 Single Component with an ATTACH Property
2.2.173 [RFC6047] Section 4.2 Using multipart/alternative for Low-Fidelity Clients
2.2.174 [RFC6047] Section 4.3 Single Component With An ATTACH Property and Inline Attachment
2.2.175 [RFC6047] Section 4.4 Multiple Similar Components
2.2.176 [RFC6047] Section 4.5 Multiple Mixed Components
2.2.177 [RFC6047] Section 4.6 Detailed Components with an ATTACH Property
2.2.178 [RFC6047] Section 5.1 Use of Content and Message IDs
Expand Minimize
This topic has not yet been rated - Rate this topic

2.2.92 [RFC5545] Section 3.8.7.2 Date-Time Stamp

V0209:

The specification states that non-standard property parameters can be specified on the DTSTAMP property.

Microsoft Office Outlook 2007, Microsoft Outlook 2010, Microsoft Outlook 2013

Outlook does not export any parameters on the DTSTAMP property. On import, Outlook ignores all parameters except TZID on the DTSTAMP property.

V0210:

The specification states that the DTSTAMP property MUST be specified within the VEVENT, VTODO, VJOURNAL, and VFREEBUSY components.

Office Outlook 2007, Outlook 2010, Outlook 2013

Outlook exports exactly one DTSTAMP property in each VEVENT component. Outlook does not export VTODO, VJOURNAL, or VFREEBUSY components.

On import, if the DTSTAMP property is not present on a VEVENT component, Outlook uses the time of import. If multiple DTSTAMP properties are found, Outlook ignores all but the first. Outlook ignores all DTSTAMP properties outside of a VEVENT component.

V0211:

The specification states that the DTSTAMP property value MUST be specified in UTC time format.

Office Outlook 2007, Outlook 2010, Outlook 2013

On import, Outlook can import DTSTAMP property values specified in UTC, local, or floating time format.

Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft. All rights reserved.