Re: [Tzdist] Fwd: [tzdist] #32 (service): managing historical data

Cyrus Daboo <cyrus@daboo.name> Tue, 16 December 2014 19:58 UTC

Return-Path: <cyrus@daboo.name>
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 20E1B1A86E2 for <tzdist@ietfa.amsl.com>; Tue, 16 Dec 2014 11:58:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 FZxhxzoIfmQi for <tzdist@ietfa.amsl.com>; Tue, 16 Dec 2014 11:58:51 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9FEA1A8758 for <tzdist@ietf.org>; Tue, 16 Dec 2014 11:58:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 10A096440E6; Tue, 16 Dec 2014 14:58:45 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CEN848xZHCqE; Tue, 16 Dec 2014 14:58:44 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id C41E76440D7; Tue, 16 Dec 2014 14:58:43 -0500 (EST)
Date: Tue, 16 Dec 2014 14:58:39 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Daniel Migault <mglt.ietf@gmail.com>, Doug Royer <douglasroyer@gmail.com>
Message-ID: <9A4B38EEDB927575ED1A77F1@caldav.corp.apple.com>
In-Reply-To: <CADZyTknKw3zYZgF4Udiu4Ythz3OD2-AXc-96VBrq1GXYtYfu8Q@mail.gmail.com>
References: <059.5da79d7c9d394e20e3c22513cfe04c33@tools.ietf.org> <5488921B.8020900@lsces.co.uk> <5488973F.7050400@andrew.cmu.edu> <54889C39.1080103@lsces.co.uk> <D2BE5C3BFE11019ECF4BEF62@caldav.corp.apple.com> <5488A6E6.8050903@lsces.co.uk> <CADC+-gTiyJ4QHZT6m3je9M9-ifSELnSWgmgy7iXSWNS+p8pthg@mail.gmail.com> <5488C0EA.8090505@lsces.co.uk> <CADC+-gTgckSe1ca6Sai6RguQid=ReM7bH6K8+dVVFm-YfbpFbA@mail.gmail.com> <5488DA56.2090306@lsces.co.uk> <CADC+-gQN=Qb2y8M-bHnPzMcK8r=xUG-seQ7XzvZwwcWsHpHnBQ@mail.gmail.com> <54895986.6060806@lsces.co.uk> <5489CA90.1070307@gmail.com> <35BC5886C9A58F866E8A46A8@caldav.corp.apple.com> <5489D9F7.3080207@gmail.com> <D196D63077FEC1B090DF7C86@caldav.corp.apple.com> <5489F79E.4080909@gmail.com> <BC19CC6916DC0E59CA63737D@caldav.corp.apple.com> <548B929C.3010505@gmail.com> <548C04F8.30005@lsces.co.uk> <D0F712C2A7EF425A8887E231@cyrus.local> <548DD49E.2050300@gmail.com> <4316F5E10254D07BBC24E4E1@caldav.corp.apple.com> <548F5B6B.4090702@gmail.com> <CADZyTknKw3zYZgF4Udiu4Ythz3OD2-AXc-96VBrq1GXYtYfu8Q@mail.gmail.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1268"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/4Xm0gmJN9up850yzIs49ssJtmSw
Cc: Time Zone Data Distribution Service <tzdist@ietf.org>
Subject: Re: [Tzdist] Fwd: [tzdist] #32 (service): managing historical 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: Tue, 16 Dec 2014 19:58:54 -0000

Hi Daniel,

--On December 16, 2014 at 8:12:40 PM +0100 Daniel Migault 
<mglt.ietf@gmail.com> wrote:

> I am thus inclined to have a mandatory version number. Although there are
> alternative ways to do/think. I would like to see if there are any strong
> opposition to this. Please send you opinion. I wish we find consensus
> by/during the phone call.

As I proposed before I want to see the version number be part of the 
meta-data associated with the time zone data - i.e., part of the list 
action response. I don't want to see it in the time zone data due to the 
fact that, with the current manner in which IANA tz data is "tagged" with a 
version, the entire set of time zones would be marked as changed.

I believe providing that information as meta-data is the right thing to do 
and gives clients/applications/protocols all the information they need to 
manage version discrepancies if that is something that is an issue for 
them. That does not preclude the possibility of using version ids that the 
publisher attaches to time zone data in the time zone data itself, if the 
publisher chooses to do that.

As for how the version information is stored and used - that should be left 
solely up to the applications using the time zone data.

-- 
Cyrus Daboo