Re: [Tzdist] Next step

> 2) In conjunction with the IANA tzdb folks, define a media type that describes the "zoneinfo" file format (either a direct binary representation or, say, a JSON representation of that) so that tzdist servers can directly provide the zoneinfo file data that many OS's use.

Is anyone working with the ICU project to come up with a way to make it and tzdist work together?

Thanks,
Deborah

> On Oct 19, 2015, at 6:55 AM, Cyrus Daboo <cyrus@daboo.name> wrote:
> 
> Hi Daniel,
> 
> --On October 18, 2015 at 5:39:04 PM +0100 Daniel Migault <daniel.migault@ericsson.com> wrote:
> 
>>    OPTION 1: There is significant interest and energy to work on topics
>> in this area. In that case, we can think of re-chartering the WG. If you
>> see any work in this area, let it us know as soon as possible, so we can
>> define a new charter.
> 
> A couple of possible follow-up work items:
> 
> 1) Add a location->tzid mapping extension to the tzdist protocol. That ought to be a relatively trivial extension to define if there is interest.
> 
> 2) In conjunction with the IANA tzdb folks, define a media type that describes the "zoneinfo" file format (either a direct binary representation or, say, a JSON representation of that) so that tzdist servers can directly provide the zoneinfo file data that many OS's use.
> 
> -- 
> Cyrus Daboo
> 
> _______________________________________________
> Tzdist mailing list
> Tzdist@ietf.org
> https://www.ietf.org/mailman/listinfo/tzdist