2.2.103 [RFC5546] Section 3.1.2 VTIMEZONE

  • 2 minutes to read

V0226:

The specification specifies the allowed number of instances of components and properties in a VTIMEZONE component in the following table.

Component/property

Presence

Notes

VTIMEZONE

0+

MUST be present if any date/time refers to time zone.

•DAYLIGHT

0+

MUST be one or more of either STANDARD or DAYLIGHT.

••COMMENT

0 or 1

••DTSTART

1

MUST be local time format.

••RDATE

0+

If present, RRULE MUST NOT be present.

••RRULE

0+

If present, RDATE MUST NOT be present.

••TZNAME

0 or 1

••TZOFFSETFROM

1

••TZOFFSETTO

1

••IANA-PROPERTY

0+

••X-PROPERTY

0+

•LAST-MODIFIED

0 or 1

•STANDARD

0+

MUST be one or more of either STANDARD or DAYLIGHT.

••COMMENT

0 or 1

••DTSTART

1

MUST be local time format.

••RDATE

0+

If present, RRULE MUST NOT be present.

••RRULE

0+

If present, RDATE MUST NOT be present.

••TZNAME

0 or 1

••TZOFFSETFROM

1

••TZOFFSETTO

1

••IANA-PROPERTY

0+

••X-PROPERTY

0+

•TZID

1

•TZURL

0 or 1

•IANA-PROPERTY

0+

•X-PROPERTY

0+

Microsoft Exchange Server 2007, Microsoft Exchange Server 2010

The following table specifies the number of instances Microsoft Exchange Server exports for these components and properties in a VTIMEZONE component.

Component/property

Number of instances exported

Notes

VTIMEZONE

0+

•DAYLIGHT

0-1

••COMMENT

0

••DTSTART

1

••RDATE

0

••RRULE

1

••TZNAME

0

••TZOFFSETFROM

1

••TZOFFSETTO

1

••IANA-PROPERTY

0

••X-PROPERTY

0

•LAST-MODIFIED

0

•STANDARD

1

••COMMENT

0

••DTSTART

1

••RDATE

0

••RRULE

0-1

••TZNAME

0

••TZOFFSETFROM

1

••TZOFFSETTO

1

••IANA-PROPERTY

0

••X-PROPERTY

0

•TZID

1

•TZURL

0

•IANA-PROPERTY

0

•X-PROPERTY

0

The following table specifies the number of instances Microsoft Exchange imports for these components and properties in a VTIMEZONE component. If more instances are found, Microsoft Exchange fails to import the iCalendar object. If fewer instances than required are found, Microsoft Exchange fails to import the iCalendar object.

Component/property

Number of instances imported

Notes

VTIMEZONE

0+

If not present for a TZID, a default time zone is used.

•DAYLIGHT

0-1

VTIMEZONE components that contain no STANDARD or DAYLIGHT components are ignored.

••COMMENT

0

••DTSTART

0-1

Values in UTC are treated as local time.

••RDATE

0

••RRULE

0-1

••TZNAME

0

••TZOFFSETFROM

1

••TZOFFSETTO

1

••IANA-PROPERTY

0

••X-PROPERTY

0

•LAST-MODIFIED

0

•STANDARD

0-1

VTIMEZONE components that contain no STANDARD or DAYLIGHT components are ignored.

••COMMENT

0

••DTSTART

1

Values in UTC are treated as local time.

••RDATE

0

••RRULE

0-1

••TZNAME

0

••TZOFFSETFROM

1

••TZOFFSETTO

1

••IANA-PROPERTY

0

••X-PROPERTY

0

•TZID

1

•TZURL

0

•IANA-PROPERTY

0

•X-PROPERTY

0

Microsoft Exchange Server 2010 Service Pack 1 (SP1), Microsoft Exchange Server 2013, Microsoft Exchange Server 2016, Microsoft Exchange Server 2019

Exchange 2010 SP1, Exchange 2013, Exchange 2016, and Exchange 2019 import and export VTIMEZONE components in the same manner as Exchange 2010, except for the DAYLIGHT and STANDARD properties. The following table specifies the number of instances that Exchange 2010 SP1, Exchange 2013, Exchange 2016, and Exchange 2019 import for the DAYLIGHT and STANDARD components.

Component/property

Number of instances imported

Notes

•DAYLIGHT

0+

VTIMEZONE components that contain no STANDARD or DAYLIGHT components are ignored.

•STANDARD

0+

VTIMEZONE components that contain no STANDARD or DAYLIGHT components are ignored.