Opened 8 years ago

Closed 8 years ago

#34 closed defect (fixed)

should we include a raw tzdb format media type?

Reported by: lear@… Owned by: cyrus@…
Priority: minor Milestone:
Component: service Version:
Severity: Active WG Document Keywords:


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.

Change History (1)

comment:1 Changed 8 years ago by mglt.ietf@…

  • Resolution set to fixed
  • Status changed from new to closed

the protocol can easily include additional format:

section 4.1.2
Clients use the HTTP Accept header field (see

Section 5.3.2 of [RFC7231]) to indicate their preference for the
returned data format. Servers indicate the available formats that
they support via the "capabilities" action response

Note: See TracTickets for help on using tickets.