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

"tzdist issue tracker" <trac+tzdist@tools.ietf.org> Wed, 07 January 2015 21:21 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: tzdist issue tracker <trac+tzdist@tools.ietf.org>
Precedence: bulk
Auto-Submitted: auto-generated
To: cyrus@daboo.name, lear@cisco.com
Date: Wed, 07 Jan 2015 21:21:38 -0000
Message-ID: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/YBk4dVAHWxKCi3npni_ViE5nPn0
Cc: tzdist@ietf.org
Subject: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb format media type?

#34: should we include a raw tzdb format media type?

 I am not fully convinced that this needs to be done in this draft, but I
 do think it would be a good idea to support the raw format, so that simple
 systems don't need to do the recompile.  An iPhone will not be the
 smallest system to run this code, we hope.

 In favor of putting the media type in the draft is that we can test
 whether multiple formats can in fact be supported.  The bad is that it
 could slow us down just a little, and I would rather not include anything
 for which there isn't a willingness by someone to write out some code on
 both ends to test.

 It is possible to include this as a separate draft, but we need to be very
 comfortable that we haven't made a mistake draft-ietf-tzdist-service that
 would cause a problem.  So for instance, those files normally come over at
 the level of a continent.  What would a query look like?

 Let's discuss.

-- 
--------------------------------+------------------------------
 Reporter:  lear@cisco.com      |      Owner:  cyrus@daboo.name
     Type:  defect              |     Status:  new
 Priority:  minor               |  Milestone:
Component:  service             |    Version:
 Severity:  Active WG Document  |   Keywords:
--------------------------------+------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/tzdist/trac/ticket/34>
tzdist <http://tools.ietf.org/tzdist/>

[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