Shepherd writeup
rfc7808-11

1. Summary

The document is "Time Zone Data Distribution Service" [1] from M. Douglass and C. Daboo. The Working Group is TZDIST. The document shepherd is Daniel Migault. The responsible Area Director is Barry Leiba.

This document defines the protocol for time zone and leap second distribution.

2. Review and Consensus


a) Addressed Issues

In my opinion, all issues have been addressed, and there are no remaining open issues. Issues have been tracked in the data tracker, and all issues have been closed. The WG has been notified of the last version of the draft no issues have been raised so far.

Issues have been methodologically tracked and addressed. The individual draft came through 11 revisions and once adopted as WG document, the WG draft came through 7 additional revisions. They were among 22 open issues. All these issues have reached the WG consensus on the mailing list. In addition, the document was also approved on the saag, app-discuss, int-area, ops-area and ietf-privacy Mailing lists.

b) Strong consensus

In my opinion, I believe a strong consensus has been reached, and the last version results in global agreement from the WG as well as from the person raising the issue. As far as I know none believes the current version does not address one issue it has raised.
 
Consensus was reached as we spent a significant amount of time to expose and address the different issues. The WG was pretty much active, with around 80 discussion threads and 15 active participants. There were no face to face meeting during IETF regular meetings, but two phone conference meetings have been set on 2014/10/24 and 2014/12/18.

As a result to the numerous addressed issues with a strong consensus, the initial proposal has significantly changed from its initial version. Among the changes are 1) leap seconds, 2) redesign of the API, 3) historical data management has been considered, 4) security and privacy both in design and considerations section. 


3. Intellectual Property

Each author has confirmed conformance with BCP 78/79. There are no IPR disclosures on the document.

4. Other points

I-D nits shows a downref: Normative reference to an Informational RFC: RFC 2818.  This is a very common reference and is already in the downref registry.

[1] https://datatracker.ietf.org/doc/draft-ietf-tzdist-service/
[2] http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry
[3] http://datatracker.ietf.org/doc/rfc2818/referencedby/


Back