IETF Logo Mail Archive

Re: [Tzdist] tzdist examples

Cyrus Daboo <cyrus@daboo.name> Mon, 05 January 2015 16:16 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 5A0BE1A1A31 for <tzdist@ietfa.amsl.com>; Mon, 5 Jan 2015 08:16:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 7nANNRU2aoDw for <tzdist@ietfa.amsl.com>; Mon, 5 Jan 2015 08:16:15 -0800 (PST)
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 E63EE1A19F7 for <tzdist@ietf.org>; Mon, 5 Jan 2015 08:16:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 134747F3DE8; Mon, 5 Jan 2015 11:16:14 -0500 (EST)
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 gmTJ2Tlh7PrE; Mon, 5 Jan 2015 11:16:13 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id E87377F3DDB; Mon, 5 Jan 2015 11:16:11 -0500 (EST)
Date: Mon, 05 Jan 2015 11:16:07 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Paul Eggert <eggert@cs.ucla.edu>, Daniel Migault <mglt.ietf@gmail.com>, Ken Murchison <murch@andrew.cmu.edu>
Message-ID: <C8E630F977DA8773B4B17D6D@caldav.corp.apple.com>
In-Reply-To: <54AAB2EB.1020209@cs.ucla.edu>
References: <9E54BBDC7F272E0E5799E1FE@cyrus.local> <CACzrW9D2UGZPPqEjrUdSZ28AXTc=RCfUzq5HBLPMSUMPg1ijgA@mail.gmail.com> <C3F1BA4B3DCB5656A683870D@cyrus.local> <5499D3B4.1000507@cs.ucla.edu> <B95F454529942901A2C436A7@cyrus.local> <CADZyTknKqX1huyTYRKMT90axQQ1HBxbT1HSiBBX+Z2ihWrJOFQ@mail.gmail.com> <85fa97ec-11d0-42a8-86ba-31b2ccbb248c.maildroid@localhost> <4CC1B5761BAFD1A5F64AECF3@cyrus.local> <db8d50f2-452a-487c-8a88-87edd8d824ac.maildroid@localhost> <CADZyTkngZptxhet-EzBp1=YtHKcR1hXj5Kz4wKSmjK50qTF+6g@mail.gmail.com> <54A15BB4.70909@andrew.cmu.edu> <CADZyTkn=sgHqS2RhtkGxVKh0NZ_HSCM31+qL-8f=P4eXaGodBQ@mail.gmail.com> <54AAB2EB.1020209@cs.ucla.edu>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1085"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/TmEXWmYe37EKyWpZiDQO8c9z42A
Cc: Time Zone Data Distribution Service <tzdist@ietf.org>
Subject: Re: [Tzdist] tzdist examples
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: Mon, 05 Jan 2015 16:16:19 -0000

Hi Paul,

--On January 5, 2015 at 7:51:07 AM -0800 Paul Eggert <eggert@cs.ucla.edu> 
wrote:

> There's one other remaining issue: there needs to be a standard way for
> tzdist to exchange tz-format binary data, as well as VTIMEZONE data.
> Eliot Lear mentioned this in
> <http://www.ietf.org/mail-archive/web/tzdist/current/msg01171.html> as an
> issue he's considering opening.  This one really should be opened and
> then solved.  In practice right now the binary data format is undoubtedly
> more popular than VTIMEZONE in real-world clients, and standardizing its
> use in tzdist will make the protocol significantly more useful and more
> likely to succeed.

I think the simple answer to this is to define a MIME media type for the 
zoneinfo data format. That might be as simple as one new section in the 
tzdist document to do that (with a pointer to the IANA time zones page), or 
it may require a more detailed formal write-up of the data format (beyond 
the code) along with the media type. If the later, then I think it would be 
better as a separate spec.


-- 
Cyrus Daboo

v2.23.0 | Report a Bug | By Email