Re: [Tzdist] Next step

Paul Eggert <eggert@cs.ucla.edu> Tue, 20 October 2015 19:08 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 C70B31ACEAF for <tzdist@ietfa.amsl.com>; Tue, 20 Oct 2015 12:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2pNxiKbZ2r-z for <tzdist@ietfa.amsl.com>; Tue, 20 Oct 2015 12:08:34 -0700 (PDT)
Received: from zimbra.cs.ucla.edu (zimbra.cs.ucla.edu [131.179.128.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B12CC1ACEA0 for <tzdist@ietf.org>; Tue, 20 Oct 2015 12:08:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 8B22E1601AD; Tue, 20 Oct 2015 12:08:34 -0700 (PDT)
Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id mOrK3EO9kf3F; Tue, 20 Oct 2015 12:08:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id D6B811608D3; Tue, 20 Oct 2015 12:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu
Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VYq36lNsZ1Yq; Tue, 20 Oct 2015 12:08:33 -0700 (PDT)
Received: from [192.168.1.9] (pool-100-32-155-148.lsanca.fios.verizon.net [100.32.155.148]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id B4A6C1601AD; Tue, 20 Oct 2015 12:08:33 -0700 (PDT)
To: Tim Parenti <tim@timtimeonline.com>, Lester Caine <lester@lsces.co.uk>
References: <CADZyTkmO_PcfWTw-36U_6vo=EuDAnAmvUo6nvPZjkHjb_ALPSQ@mail.gmail.com> <40285_1445262970_t9JDu8BA043191_50DBD330DB51FDFC0C3E86D4@cyrus.local> <5624FAC4.5030008@andrew.cmu.edu> <B38549591D4FFBE5A83BF0BD@cyrus.local> <56253CCB.6010602@gmail.com> <316D3AAC6E4A5336C1784897@caldav.corp.apple.com> <5625E08C.9040800@lsces.co.uk> <CAFpi07w7z3BZATsd895WL-mLpE2pkOc0j=Dsnow3VG7ECEZNBA@mail.gmail.com>
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
Message-ID: <56269131.3060305@cs.ucla.edu>
Date: Tue, 20 Oct 2015 12:08:33 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAFpi07w7z3BZATsd895WL-mLpE2pkOc0j=Dsnow3VG7ECEZNBA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/HmYR4uqDlgS9FBuvFoX5s9vxCFg>
Cc: Time Zone Data Distribution Service <tzdist@ietf.org>
Subject: Re: [Tzdist] Next step
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Oct 2015 19:08:35 -0000

Tim Parenti wrote:
> Implementations in this area might endeavor to distinguish between "borders
> that potentially matter" and "borders that definitely don't matter", which
> seems a tenuous distinction.

On my list of tzdata things to do is to add a file zonenow.tab, which would be 
like zone1970.tab except with the cutoff being now, i.e., it would partition the 
world into regions where civil-time clocks agree from now into the predicted 
future (but may disagree in the past). A server that wants to cater only to 
current and future timestamps could limit itself to zones in zonenow.tab.