Opened 8 years ago

Last modified 8 years ago

#27 new defect

draft-ietf-caldav-timezone-ref: Section 3.1.2: when to not send VTIMEZONE information

Reported by: lear@… Owned by: cyrus@…
Priority: major Milestone:
Component: caldav-timezone-ref Version:
Severity: Active WG Document Keywords:


Section 3.1.2 contains the following text:

Servers that follow this specification MUST NOT send "VTIMEZONE"
components in iCalendar data to clients, when the time zone
identifier and corresponding time zone definitions are available on
any of the advertised time zone data distribution services.

It is important for interoperability for the server to KNOW that the client is making use of the tzdist service. Therefore, this text would better read as follows:

Servers that follow this specification MUST NOT send VTIMEZONE components in iCalendar data to clients who have indicated they support this specification.

This raises a broader question:

What is an appropriate order to determine whether or not a client actually has connectivity to a tzdist server? If the client has no access, then it may not want to use this extension (especially on first use). Can it indicate that mid-session? I ask because the set of tzdist servers is returned in the CALDAV:timezone-service-set WebDAV property

Change History (1)

comment:1 Changed 8 years ago by lear@…

  • Owner changed from draft-ietf-tzdist-caldav-timezone-ref@… to cyrus@…
Note: See TracTickets for help on using tickets.