Re: [Tzdist] Create and distribution process of events with TZ data.

Lester Caine <lester@lsces.co.uk> Fri, 12 December 2014 09:23 UTC

Return-Path: <lester@lsces.co.uk>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89ACE1A90D3 for <tzdist@ietfa.amsl.com>; Fri, 12 Dec 2014 01:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qAP6X_hKCcHT for <tzdist@ietfa.amsl.com>; Fri, 12 Dec 2014 01:23:51 -0800 (PST)
Received: from mail4.serversure.net (mail4-2.serversure.net [217.147.176.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CAEF1A19E5 for <tzdist@ietf.org>; Fri, 12 Dec 2014 01:23:50 -0800 (PST)
Received: (qmail 764 invoked by uid 89); 12 Dec 2014 09:23:48 -0000
Received: by simscan 1.3.1 ppid: 757, pid: 761, t: 0.0853s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677
Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.178.188.220) by mail4.serversure.net with ESMTPA; 12 Dec 2014 09:23:48 -0000
Message-ID: <548AB424.5010505@lsces.co.uk>
Date: Fri, 12 Dec 2014 09:23:48 +0000
From: Lester Caine <lester@lsces.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Time Zone Data Distribution Service <tzdist@ietf.org>
References: <54888642.1030108@lsces.co.uk> <F2F4FB8F282334E543F462B5@caldav.corp.apple.com> <54889270.7040801@lsces.co.uk> <CADC+-gQTgF8HYKoO=vLrgC=5jWDQuOn9ZTrtLH4e7ABAgJqtEw@mail.gmail.com> <54889940.9000900@lsces.co.uk> <54889EC9.90500@gmail.com> <5489D56D.5010206@gmail.com> <5489DB49.90309@lsces.co.uk> <CAFpi07xLdvqpt=NX1Z+NTbyWzqNPm7LWH5XaB-65xo0_ZF-X+Q@mail.gmail.com> <548AAEB3.3030409@cisco.com>
In-Reply-To: <548AAEB3.3030409@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/NYB5gjt9U9IGJFbLDhtTb99QwXk
Subject: Re: [Tzdist] Create and distribution process of events with TZ data.
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>, <mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 09:23:52 -0000

On 12/12/14 09:00, Eliot Lear wrote:
>> That said, the tzdist protocol can help with these best practices in
>> some ways.  In particular, I think Paul's question of "I've got
>> version tz2014a of America/Los_Angeles; is that good enough?" is a
>> useful one to be able to answer.
>>  (http://www.ietf.org/mail-archive/web/tzdist/current/msg01018.html)
>>  To ask this question, you only need to store one additional data
>> point per zone used, or ideally, one additional data point altogether.
> 
> To whom does one that question?  The meeting organizer?  The
> communication path to that individual is not what I would call real
> time.  After all, it is the meeting organizer with whom one must have a
> common view, and not the tzdist server, which I think seveal people have
> stated in several different ways.

Since the meeting organizer may well be sleeping when a short term
change is actioned, tzdist is the mechanism to publish that something
has changed. The meeting organiser will get to hear of the problem when
they wake up and if they have planned properly it is just a matter of
their publishing a revised agenda. In the meantime attendees who wake up
earlier will see that the data used by the event has changed overnight
and there is a potential problem. They know to check! This is why having
a common view of the VERSION of data being used is important and ideally
all publishers would return the same view of a version sourced from the
same original data?

tzdist sets a standard so that other users only need to worry about
'VTIMEZONE version' or some similar tag when publishing events. If the
version changes we at least have an indication that action may be
required ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk