Timeline


and

23/10/14:

21:07 Ticket #28 (JSON format or not JSON) closed by mglt.ietf@…
fixed
15:09 Ticket #33 (“substantive” change) created by cyrus@…
Current draft has: When listing time zones, a timestamp is …
14:55 Ticket #32 (managing historical data) created by lester@…
If I provide archived data that has been created using the current set …
14:46 Ticket #16 (draft-ietf-tzdist-service: definition of "substantive" in Section 4.1.3) closed by mglt.ietf@…
fixed
14:39 Ticket #9 (TZIDs overlap?!) closed by mglt.ietf@…
fixed
11:52 Ticket #31 (Include leap seconds?) created by martin.burnicki@…
If you are going to work with historical data it might be important to …

06/10/14:

18:56 Ticket #30 (DHCP option for tzdist servers available?) created by martin.burnicki@…
The idea behind this is that just like with DNS or NTP services there …

29/09/14:

19:35 Ticket #29 (URL design) created by mglt.ietf@…
I have finally taken the time to read the URL aspects of the spec, and …

24/09/14:

19:37 Ticket #28 (JSON format or not JSON) created by mglt.ietf@…
I am not sure I understand what Barry says. I understand he saying …
12:25 Ticket #4 (clarification on the "name" pattern) closed by mglt.ietf@…
fixed: Version 01 changed name to pattern. …
12:11 Ticket #12 (meaning of timezone (related to timezone->time zone)) closed by mglt.ietf@…
fixed: text has been modified in section 1.2 …
12:08 Ticket #13 (definition of "Timezone Data") closed by mglt.ietf@…
fixed: Section 1.2 has been modified consequently …
11:58 Ticket #21 (Semantics of year fields, and clarifying onset) closed by mglt.ietf@…
fixed: Text of section 6.4 seems to have reached consensus. …
11:46 Ticket #7 (security consideration: why do we need an insecure version of the ...) closed by mglt.ietf@…
fixed: Hi Lester, tzdist@…, --On September 22, 2014 at 3:26:03 PM …
Note: See TracTimeline for information about the timeline view.