Re: iTIP: Outdated VTIMEZONE

[Antoine Leca <Antoine.Leca@xxxxxxxxxx>]

First, sorry for the delay: I was offline for two weeks.

Keith Moore wrote, answering to me:
> 
> > Suppose a CUA receive a VCALENDAR object, containing a VTIMEZONE
> > with outdated datas (as far as the concerned CUA thinks).
> >
> 
> I can't imagine that the CUA should argue about the timezone

You are right, I made a mistake: the above should read:
(as far as the concerned CU thinks).

Then, an example is someone which propose to you a appointment
at your own location, using false (outdated) TZ informations.
More precisely, when the law has just changed at your location.

I am sure the CU will be sure the infos are wrong and should be
corrected.


> Even for globally-scoped
> timezones, how does the CUA know that it's notion of timezone is older
> or newer than the one in the VCALENDAR object?

I thougth this is DTSTAMP in VTIMEZONE is for.


Then the basic question remains:

> > What is the correct behavior is this case?
> >
> > I believe the CUA should send a COUNTER proposal with the
> > corrected VTIMEZONE component (then following the described
> > workflow for COUNTER proposals).
> >
> > If I am right, may this process be described in iTIP?