IETF Logo Mail Archive

Re: [Tzdist] Existing and new data ...

Lester Caine <lester@lsces.co.uk> Wed, 10 December 2014 19:28 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 1D6CD1A90D7 for <tzdist@ietfa.amsl.com>; Wed, 10 Dec 2014 11:28:51 -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 XAS29TTXVvlz for <tzdist@ietfa.amsl.com>; Wed, 10 Dec 2014 11:28:46 -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 925421A909F for <tzdist@ietf.org>; Wed, 10 Dec 2014 11:28:24 -0800 (PST)
Received: (qmail 1056 invoked by uid 89); 10 Dec 2014 19:28:22 -0000
Received: by simscan 1.3.1 ppid: 1050, pid: 1053, t: 0.0711s 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; 10 Dec 2014 19:28:22 -0000
Message-ID: <54889ED6.7050500@lsces.co.uk>
Date: Wed, 10 Dec 2014 19:28:22 +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: 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> <1AB55F65032994C79A7E4957@caldav.corp.apple.com>
In-Reply-To: <1AB55F65032994C79A7E4957@caldav.corp.apple.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/9VpZMGkUDUF3Y6EtKXq8BT8opGk
Subject: Re: [Tzdist] Existing and new 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: Wed, 10 Dec 2014 19:28:51 -0000

On 10/12/14 19:14, Cyrus Daboo wrote:
> Right, but the tzdist protocol should not be telling clients what to do
> in the absence of tzdist. A separate document describing best practices
> for use of time zones (be they from tzdist or any other source) would be
> a better place for that.

? Don't understand that. When tzdist starts to distribute data then it's
data will be used as it is today. Unless you expect every user to update
their published content using tzdist every time there is a change, there
HAS to be a mechanism to access the data at the point in time the
material was published. I see nothing external to a system for
publishing TZ data as the core process.

The ramifications of published changes may benefit from a separate
document, but maintaining published data IS a core function.

-- 
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

v2.23.0 | Report a Bug | By Email