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

Daniel Migault <mglt.ietf@gmail.com> Sat, 01 November 2014 13:14 UTC

Return-Path: <mglt.ietf@gmail.com>
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 B14051A8729 for <tzdist@ietfa.amsl.com>; Sat, 1 Nov 2014 06:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 EDYu_ubR8gye for <tzdist@ietfa.amsl.com>; Sat, 1 Nov 2014 06:14:33 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 060E41A19E2 for <tzdist@ietf.org>; Sat, 1 Nov 2014 06:14:32 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id x12so7701649wgg.31 for <tzdist@ietf.org>; Sat, 01 Nov 2014 06:14:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ERah0skKFTQ65eprAVWtY6BE3wkQJMNzlyfehUDUGu0=; b=EiBSM4FAVCiDUN3om7+XY+7FAStLF4LdWzrpmyR8y98TmfZLxuFoL1t4N5RLwWKEzL 06wUM6ytGPwAFWLUkPj0ofys/fT39HYd17uz6u62nZhDz3Ql73FmE5lvNfoYoufPIEZn 686aubN1ue29PnKL8jDJNPHS/GpY1FVfliMvE8N4kLMYHr/duD+pD0AFqE/fOCQ6Abl4 p2U2PqcLeRg196ocNNKrYq/cu+zG0K+C3xURAvqQmldQf+ZCH2sCwuPC7AGN4gOea2dv 87SFTbDACm6Ga5uKrrVwpiwUrFAc7g4qLQM/vo5Z2Y50cAndLrNmNqExq8JDHu6necaT fDFA==
MIME-Version: 1.0
X-Received: by 10.194.222.162 with SMTP id qn2mr35315469wjc.74.1414847671182; Sat, 01 Nov 2014 06:14:31 -0700 (PDT)
Received: by 10.194.110.4 with HTTP; Sat, 1 Nov 2014 06:14:31 -0700 (PDT)
In-Reply-To: <544ADFB7.80705@lsces.co.uk>
References: <059.5da79d7c9d394e20e3c22513cfe04c33@tools.ietf.org> <074.141a9388d35dbdf392fcdf7384321e4e@tools.ietf.org> <544A88D8.7010108@lsces.co.uk> <544A9442.5010805@cs.ucla.edu> <544AA116.8030003@lsces.co.uk> <CAAGevbVBacBaX0syYc5eOVvO72N2UjCOJN-quPPGekOf7yzNqw@mail.gmail.com> <544ADFB7.80705@lsces.co.uk>
Date: Sat, 01 Nov 2014 14:14:31 +0100
Message-ID: <CADZyTkmK89hSUBqdrrjJUwTccn+NrW+gJB81RJqDkGZTO=TuEA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Content-Type: multipart/alternative; boundary="001a11c3a156da2ae30506cbe4db"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/GR92pYNEwDlXL6ehP0bQ7rNuPkI
Cc: Time Zone Data Distribution Service <tzdist@ietf.org>
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: Sat, 01 Nov 2014 13:14:48 -0000

Hi Lester,

Given the new URL format discussed in Issue #29. A version has been
specified. Can you let us know if it solves the historical data issue
completely. If it does not solve it completely, could you expose the
appropriated extensions that would solve this issue?

>From the call conference, I thought that this issue would be solved by
introducing redirections to tzids. That is if I need the complete time zone
related to Paris from let say 1875 to 2056, I would be returned a list:
 [{utc_start:start_time0,
   utc_stop:stop_time0,
   tzid: tzid0}
   ....
   {utc_start:start_timeN,
   utc_stop:stop_timeN,
   tzid: tzidN}
]

where tzid is one of the Time zones we are distributing. I might be
completely wrong. Suppose i am not, I am not also sure that such a
mechanisms will be described in the current service distribution. It might
be another document. However, the current service distribution should
clearly make that possible.

BR,
Daniel



On Sat, Oct 25, 2014 at 1:24 AM, Lester Caine <lester@lsces.co.uk> wrote:

> On 24/10/14 20:05, Tobias Conradi wrote:
> >> You are right.
> > No he is not. If the "need to put local time into a log for some
> > reason", then it does not mean that "they can log UTC offset".
>
> Log sequence is gauranteed by the use of UTC base, and since we do not
> need to know about any other time than the logged time, the offset is
> all that is needed. BUT the audit trail still needs to know if the
> correct offset was used for that offset which is where a version stamp
> is important.
>
> --
> 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
>
> _______________________________________________
> Tzdist mailing list
> Tzdist@ietf.org
> https://www.ietf.org/mailman/listinfo/tzdist
>



-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58