Subject: [Tzdist] Tracker issues:

From: Daniel Migault <[email-masked]>
Date: Tue, 26 Aug 2014 18:00:06 +0200

Dear friends and colleagues,

We have tracked most of the issues that have been raised.
http://trac.tools.ietf.org/wg/tzdist/trac/report/1

I encourage these issues are discussed and meet consensus. In order we make
sure we are discussion on the appropriated issue, mention the issue in the
subject.

The key idea is that discussions close these issues so the draft can be
appropriately being updated.

BR

Daniel and Eliot

Networking & Security Issues:
#2     Section: 4.2.1.1. Timezone Service SRV Service Labels
#3     Section 4.1.3: Scalability
#8     POSH problems
#7     security consideration: why do we need an insecure version of the
timezone service?
#20     IS TLS mandatory?
#19     tzdist uses HTTP (not DNS for example)

Semantics Issues:
#4     clarification on the "name" pattern
#5     Use of underscores in names
#12     meaning of timezone (related to timezone->time zone)
#6     timezone -> time zone
#16     draft-douglass-timezone-11: definition of "substantive" in Section
4.1.3
#17     draft-douglass-timezone-11: what is "invalid-action" in Section
4.1.6?
#13     definition of "Timezone Data"

Protocol Clarifications:
#9     TZIDs overlap?!
#10     We should truncate (entirely) truncation ;-)
#11     how to represent the JSON "schema"
#14     draft-douglass-timezone-11: localized names like "EST"
#15     draft-douglass-timezone-service-11: truncation of future data
#18     draft-douglass-timezone-11: removal of timezones?
#21     Semantics of year fields, and clarifying onset
#22     a short notice change will affect current meeting times
#23     Some of the 'optional' parts of VTIMEZONE should perhaps be tagged
as required for the server situation
#1     LMT Transition

-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58