Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb format media type?

Paul Eggert <eggert@cs.ucla.edu> Wed, 07 January 2015 23:54 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 BF8301A871D for <tzdist@ietfa.amsl.com>; Wed, 7 Jan 2015 15:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 OfmYfu8aLifJ for <tzdist@ietfa.amsl.com>; Wed, 7 Jan 2015 15:54:16 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA771A870B for <tzdist@ietf.org>; Wed, 7 Jan 2015 15:54:16 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id C14FDA600E3; Wed, 7 Jan 2015 15:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QPPky1JZOuJ; Wed, 7 Jan 2015 15:54:15 -0800 (PST)
Received: from [192.168.1.9] (pool-173-55-11-52.lsanca.fios.verizon.net [173.55.11.52]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 7C25CA600E1; Wed, 7 Jan 2015 15:54:15 -0800 (PST)
Message-ID: <54ADC723.60707@cs.ucla.edu>
Date: Wed, 07 Jan 2015 15:54:11 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: tzdist issue tracker <trac+tzdist@tools.ietf.org>, cyrus@daboo.name, lear@cisco.com
References: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
In-Reply-To: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/Yys929odkhGcI-ke_zArjRwYkiI
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: Wed, 07 Jan 2015 23:54:24 -0000

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.