Timeline
24/09/14:
- 19:37 Ticket #28 (JSON format or not JSON) created by
- I am not sure I understand what Barry says. I understand he saying …
- 12:25 Ticket #4 (clarification on the "name" pattern) closed by
- fixed: Version 01 changed name to pattern. …
- 12:11 Ticket #12 (meaning of timezone (related to timezone->time zone)) closed by
- fixed: text has been modified in section 1.2 …
- 12:08 Ticket #13 (definition of "Timezone Data") closed by
- fixed: Section 1.2 has been modified consequently …
- 11:58 Ticket #21 (Semantics of year fields, and clarifying onset) closed by
- 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
- fixed: Hi Lester, tzdist@…, --On September 22, 2014 at 3:26:03 PM …
19/09/14:
- 08:49 Ticket #6 (timezone -> time zone) closed by
- fixed: This change was made in -01, as requested.
03/09/14:
- 17:24 Ticket #25 (draft-ietf-tzdist-service: authentication and authorization of clients) closed by
- fixed: I propose adding the following text to the last paragraph of the …
- 07:35 Ticket #8 (POSH problems) closed by
- fixed: Fair point. To be clearer, there is a problem if there are going to …
02/09/14:
- 20:29 Ticket #3 (Section 4.1.3: Scalability) closed by
- fixed: the scalability issue raised by this thread concerns data truncation …
31/08/14:
28/08/14:
- 06:22 Ticket #27 (draft-ietf-caldav-timezone-ref: Section 3.1.2: when to not send ...) created by
- Section 3.1.2 contains the following text: > Servers that follow this …
- 06:13 Ticket #26 (draft-ietf-tzdist-caldav-timezone-ref: 3.1.1 bad advice on initial ...) created by
- The authors motivate the need for a caldav extension by discussion …
- 06:07 Ticket #25 (draft-ietf-tzdist-service: authentication and authorization of clients) created by
- Are all clients authorized to use all TZ distribution services? This …
- 06:00 Ticket #24 (draft-ietf-caldav-timezone-ref: Section 3 inappropriate MUST) created by
- Section 3 contains the following text: > If CalDAV clients and …
27/08/14:
- 19:42 Ticket #19 (tzdist uses HTTP (not DNS for example)) closed by
- fixed
- 12:18 Ticket #20 (IS TLS mandatory?) closed by
- duplicate: This is a duplicate of Issue 7.
- 07:34 Ticket #14 (draft-douglass-timezone-11: localized names like "EST") closed by
- fixed
- 07:19 Ticket #17 (draft-douglass-timezone-11: what is "invalid-action" in Section 4.1.6?) closed by
- fixed: I propose changing the last paragraph in Section 4.1.6 to: When an …
- 07:16 Ticket #2 (Section: 4.2.1.1. Timezone Service SRV Service Labels) closed by
- fixed
26/08/14:
- 09:46 Ticket #23 (Some of the 'optional' parts of VTIMEZONE should perhaps be tagged as ...) created by
- > Can you enumerate some specific things you think are missing from > …
- 09:42 Ticket #22 (a short notice change will affect current meeting times) created by
- >> Either the service is to provide timezone data in it's entirety, or …
Note: See TracTimeline
for information about the timeline view.