Re: [Tzdist] Next step

Cyrus Daboo <cyrus@daboo.name> Tue, 20 October 2015 02:03 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 E147C1AD10A for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 19:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 ea9u0QVE6vKR for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 19:03:05 -0700 (PDT)
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 4259A1A000F for <tzdist@ietf.org>; Mon, 19 Oct 2015 19:02:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 8221A2325B68; Mon, 19 Oct 2015 22:02:54 -0400 (EDT)
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 ujl0q4WE3kmV; Mon, 19 Oct 2015 22:02:54 -0400 (EDT)
Received: from [10.0.1.10] (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id 48DDE2325B5B; Mon, 19 Oct 2015 22:02:54 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Cyrus Daboo <cyrus@daboo.name>
X-Mailer: iPad Mail (13A452)
In-Reply-To: <5625A03C.9070708@cs.ucla.edu>
Date: Mon, 19 Oct 2015 22:02:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7364AE0-87EC-44BC-8BF0-E63FD822D451@daboo.name>
References: <CADZyTkmO_PcfWTw-36U_6vo=EuDAnAmvUo6nvPZjkHjb_ALPSQ@mail.gmail.com> <50DBD330DB51FDFC0C3E86D4@cyrus.local> <5625323F.4060102@cisco.com> <56259231.1030704@cs.ucla.edu> <BF8D641CBC49495AE8950B8E@cyrus.local> <5625A03C.9070708@cs.ucla.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/7uRT84KivHnwLS3bKwirLbEXFWk>
Cc: Time Zone Data Distribution Service <tzdist@ietf.org>, Daniel Migault <daniel.migault@ericsson.com>, Barry Leiba <barryleiba@computer.org>, tzdist-chairs@tools.ietf.org, Eliot Lear <lear@cisco.com>
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 02:03:06 -0000

Ok, then that greatly simplifies things. So we just define application/zoneinfo and we are pretty much done...

-- 
Cyrus Daboo
(Tapped out on my iPad)


> On Oct 19, 2015, at 10:00 PM, Paul Eggert <eggert@cs.ucla.edu>; wrote:
> 
> Cyrus Daboo wrote:
>> I think the tricky part about tzfile is dealing with the endian and 32/64-bit
>> differences. I am assuming we would need to serve up all possible variants of
>> those if we used the binary format as is.
> 
> That's not a problem, because there's only one binary format. The tzfile format is well-defined to be bigendian on all platforms, and to be independent of native word size. The reference code to read and write tzfile format is designed to work even on unusual machines where words are neither 32 nor 64 bits wide (e.g., Unisys mainframes). So there's not much need for a JSON tool to convert to "native" format.