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

Paul Eggert <eggert@cs.ucla.edu> Fri, 24 October 2014 18:02 UTC

Return-Path: <eggert@cs.ucla.edu>
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 A28B51A8A7F for <tzdist@ietfa.amsl.com>; Fri, 24 Oct 2014 11:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 jyV3wU65lccX for <tzdist@ietfa.amsl.com>; Fri, 24 Oct 2014 11:02:56 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 354641A8A8B for <tzdist@ietf.org>; Fri, 24 Oct 2014 11:02:51 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id F09A2A600A8; Fri, 24 Oct 2014 11:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bMW24yiW52fR; Fri, 24 Oct 2014 11:02:42 -0700 (PDT)
Received: from [192.168.1.9] (pool-71-177-17-123.lsanca.dsl-w.verizon.net [71.177.17.123]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 4AA96A60061; Fri, 24 Oct 2014 11:02:42 -0700 (PDT)
Message-ID: <544A9442.5010805@cs.ucla.edu>
Date: Fri, 24 Oct 2014 11:02:42 -0700
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Lester Caine <lester@lsces.co.uk>, tzdist@ietf.org
References: <059.5da79d7c9d394e20e3c22513cfe04c33@tools.ietf.org> <074.141a9388d35dbdf392fcdf7384321e4e@tools.ietf.org> <544A88D8.7010108@lsces.co.uk>
In-Reply-To: <544A88D8.7010108@lsces.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/hNAvkoI_zKfLs81WzbcPVRnLAGI
Subject: Re: [Tzdist] [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: Fri, 24 Oct 2014 18:02:58 -0000

Lester Caine wrote:
> I would probably view this as optional, EXCEPT that if one takes the
> situation of a simple device which is also creating a log of it's data
> now correctly using UTC timestamps, it also needs to log any change in
> version of data set used while creating that log.

That's not needed in the simple devices that I help maintain.  They log UTC.

If devices need to put local time into a log for some reason, then they can log 
the UTC offset.  That is simpler and more reliable than logging the tz version 
number would be.

The problem of managing historical data is one that primarily concerns 
operations and system maintenance.  It's not something that low-level devices 
should need to worry about.  So it should be OK to make any version-control 
features optional.