Re: [Tzdist] AD review of draft-ietf-tzdist-caldav-timezone-ref-03

[Barry Leiba <[e-mail]>]

> Sorry for the delay - addressing this now I am back from vacation.

I hope you enjoyed...

Just on points that need a response:


> From my perspective I have not yet come across a client that I know would
> be broken by this. I would be OK adding text such as the following, though:
>
>    To support legacy clients that do not send the XXX header field in
>    requests, yet expect "VTIMEZONE" components to be present, servers MAY
>    provide an administrator configuration setting to override the new
>    default behavior based on client User-Agent request header field values.

That sounds reasonable and wise.

> I think the wording of that bullet point is too strong and I would like to
> propose the following instead:
>
>    In this case, clients will have to retrieve the missing standard time
>    zone definitions either from its own cache of standard time zones, or
>    from the set of time zone distribution servers advertised by the CalDAV
>    server (see Section 3.1.2).

Yes, I like the removal of the 2119 key word from there.  In your
text, just change "its own" to "their own" for number agreement.

> Since there was push back along the same lines by the Prefer designated
> expert I would like to propose removing use of the Prefer header and instead
> replace it with a new HTTP request header:
>
> CalDAV-Timezones: Y
> CalDAV-Timezones: N
>
> With the "Y" value requesting the server to send VTZ data, and "N"
> requesting that no VTZ data is sent.
>
> If there is agreement that this addresses the problem of using Prefer, then
> I will go ahead and make this change in the next document update.

That also sounds reasonable.  What will the default be if
CalDAV-Timezones is absent?

b