Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb format media type?
Eliot Lear <lear@cisco.com> Thu, 08 January 2015 05:29 UTC
Return-Path: <lear@cisco.com>
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 E855F1A1A15
for <tzdist@ietfa.amsl.com>; Wed, 7 Jan 2015 21:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001,
T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 FnF0-Sr8pSmv for <tzdist@ietfa.amsl.com>;
Wed, 7 Jan 2015 21:29:44 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 2F3141A0E10
for <tzdist@ietf.org>; Wed, 7 Jan 2015 21:29:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=1653; q=dns/txt; s=iport;
t=1420694984; x=1421904584;
h=message-id:date:from:mime-version:to:cc:subject:
references:in-reply-to;
bh=nAIvcwz3EqsHzhnQKd3U8eXc+eCHNDWJl/hW3rvQ0Hg=;
b=Mlahn14TV1OiZt+fePXtpPkWB2GSN7LV6RePKKXLvtaLDufrKsLbbwg0
dGcBxZapk/vf44T/fsPf4MOwki/1Jm5AEFf7LuCugCwKmiB0VSoZWDINZ
ZJA+a+SaDoQRp9dIyeRyRuZPVArfOhOK7AZkvdUhgMIzS+7gn57MrtWV+ M=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYEABoVrlStJssW/2dsb2JhbABcDocoyGgCgVUBAQEBAX2EDQEBBCNWEAsYCSECAg8CRgYBDAEHAQGIKLFIk1MBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj3gHgmiBQQEEj3qBKYYLhg+LVSKCMn8+PYJ0AQEB
X-IronPort-AV: E=Sophos;i="5.07,719,1413244800";
d="asc'?scan'208";a="303991261"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com)
([173.38.203.22])
by aer-iport-1.cisco.com with ESMTP; 08 Jan 2015 05:29:42 +0000
Received: from [10.61.204.119] ([10.61.204.119])
by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t085TgvW017804;
Thu, 8 Jan 2015 05:29:42 GMT
Message-ID: <54AE15C6.10807@cisco.com>
Date: Thu, 08 Jan 2015 06:29:42 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Paul Eggert <eggert@cs.ucla.edu>,
tzdist issue tracker <trac+tzdist@tools.ietf.org>, cyrus@daboo.name
References: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
<54ADC723.60707@cs.ucla.edu>
In-Reply-To: <54ADC723.60707@cs.ucla.edu>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="st1qIsECA7BRv5L3kiCIqtMFawq0CsTAd"
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/m-wjF36xKH_V3ldtmyXyvOQatdY
Cc: tzdist@ietf.org
Subject: Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb
format media type?
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: Thu, 08 Jan 2015 05:29:46 -0000
I stand corrected. Paul's right. I was thinking of the source file. Eliot On 1/8/15 12:54 AM, Paul Eggert wrote: > tzdist issue tracker wrote: >> those files normally come over at >> the level of a continent. What would a query look like? > > The tz binary format is specified per name, e.g., there's a separate > file in tz binary format for 'America/Los_Angeles'. This is the same > as the VTIMEZONE format, so presumably a query would look just like > the query for the VTIMEZONE format, except that it's ask for tz binary > format instead of VTIMEZONE format. > > I don't see how continents are involved with this, other than as > strings that appear as part of the name strings. > >
- [Tzdist] [tzdist] #34 (service): should we includ… tzdist issue tracker
- Re: [Tzdist] [tzdist] #34 (service): should we in… Paul Eggert
- Re: [Tzdist] [tzdist] #34 (service): should we in… Eliot Lear
- Re: [Tzdist] [tzdist] #34 (service): should we in… Lester Caine
- Re: [Tzdist] [tzdist] #34 (service): should we in… Paul Eggert
- Re: [Tzdist] [tzdist] #34 (service): should we in… Lester Caine
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… Ken Murchison
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… tzdist issue tracker