Re: Omit VTIMEZONE when using global identifiers?

John Stracke wrote:

> George Babics wrote:
> > Eric Busboom wrote:
> > > Also, if we define the global TZ registry, can we remove the requirement
> > > to include a VTIMEZONE in a component when the TZID parameters reference
> > > global names?
> >
> >   Good idea.
> >
> >   What happens when an application encounters a timezone from the
> > the global TZ registry that was recently added, and that the application
> > is not aware about?
>
> Or, worse, if it's a TZID that the receiver recognizes, but whose definition has
> changed.  The sender knows the change, the receiver doesn't.  Result: the receiver
> will show up to the meeting at the wrong time--unacceptable.
>
> I think we have to keep the VTIMEZONE in, no matter what.

Or a version number with the TZID.  The tz database has a simple yearletter code (eg:
2001b) for it's versioning.  If the ietf does somehow codify the tz database, that
might come in handy.

dmadeo