IETF Logo Mail Archive

Re: [Tzdist] Getting to closure Re: [tzdist] #31 (service): Include leap seconds?

Cyrus Daboo <cyrus@daboo.name> Sat, 29 November 2014 02:37 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 2A07C1A1BDA for <tzdist@ietfa.amsl.com>; Fri, 28 Nov 2014 18:37:16 -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, 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 AJzr0z1pCr9J for <tzdist@ietfa.amsl.com>; Fri, 28 Nov 2014 18:37: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 09DCE1A1BD7 for <tzdist@ietf.org>; Fri, 28 Nov 2014 18:37:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 3B6244A9F11; Fri, 28 Nov 2014 21:37: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 kOE4Gdm4Uo5i; Fri, 28 Nov 2014 21:37:13 -0500 (EST)
Received: from [10.0.1.25] (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id 546924A9F06; Fri, 28 Nov 2014 21:37:13 -0500 (EST)
Date: Fri, 28 Nov 2014 21:37:10 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Paul Eggert <eggert@cs.ucla.edu>, Time Zone Data Distribution Service <tzdist@ietf.org>
Message-ID: <DBF699F8219F2627B7413640@cyrus.local>
In-Reply-To: <54793054.8080705@cs.ucla.edu>
References: <069.a9e77f1fcc6f2f4fb0da4bfcf8c8ce3e@tools.ietf.org> <5448F851.7030505@lsces.co.uk> <5448FE60.2050309@burnicki.net> <54490484.6030802@lsces.co.uk> <CADZyTk=j8t_jUcf=vv-6HUJCh3CWvZo75rai_CWZQTzk12Uc-g@mail.gmail.com> <CADZyTk=9kP2Mjhq_PqbOjp5hs89B8RWNSUwu-wWy6Qx=me0S9w@mail.gmail.com> <547859A8.6050302@lsces.co.uk> <54785D92.6000102@burnicki.net> <54786240.609@cisco.com> <5478A726.2070404@cs.ucla.edu> <5478AAB2.6080108@lsces.co.uk> <5478ADD0.2030407@cs.ucla.edu> <54790249.7050503@burnicki.net> <547910E7.4020407@lsces.co.uk> <7BE7527BD73E055AD5F2F7F8@cyrus.local> <54793054.8080705@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="679"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/jfRDXhq0NJoAdB-T67OWi4vr4Tg
Subject: Re: [Tzdist] Getting to closure Re: [tzdist] #31 (service): Include leap seconds?
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, 29 Nov 2014 02:37:16 -0000

Hi Paul,

--On November 28, 2014 at 6:32:52 PM -0800 Paul Eggert <eggert@cs.ucla.edu> 
wrote:

> That being said, I don't see why tzdist doesn't also have a standard way
> to exchange binary tz data. The binary tz format is ubiquitous, portable,
> and just as commonly used as iCalendar if not more so. Billions of
> clients already use the binary format and won't be able to use iCalendar
> without serious upgrades and/or compatibility hassles. What's not to like?

So all we need is a registration and formal definition of 
application/zoneinfo (or whatever is appropriate for the binary format) and 
clients can request that format in addition to iCalendar.

-- 
Cyrus Daboo

v2.23.0 | Report a Bug | By Email