At 10:07 AM 24-09-2018, The IESG wrote:
The IESG has received a request from the Network Time Protocol WG (ntp) to
consider the following document: - 'Network Time Protocol Best Current
Practices'
<draft-ietf-ntp-bcp-07.txt> as Best Current Practice
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2018-10-08. Exceptionally, comments may be
I would like to thank Tom Petch as his review prompted me to take a
look at this draft.
The write-up states that type of RFC being requested is
"Informational". However, the request received (please see above)
states that the document is intended to be a BCP. Section 1 states
that this documentation is a collection of best practices from the
NTP community. As a comment about overall document quality, the
draft needs some work as it looks like a collection of informal
advice which a person might give instead of advice which has been
formalized. It is unclear whether some of the URLs in the draft are
acknowledgments of past work or advertisements.
Section 3 is about general network security best practices. The
section mentions BCP 38 and explains that it has been approved in
2000. There is a document from 2008 [1] about it. Is BCP 38
well-deployed nowadays?
In Section 4.1:
"Interested readers should read"
Have the authors read the IETF RFC about uncapitalized letters? Does
it apply for the above?
Section 4.1 provides some examples of use of time sources. It sounds
like the draft is trying to explain different "use cases" instead of
specifying a best practice.
Section 4.2 contains some questions about diversity. It attempts to
highlight the issues in terms of "are you doing this" and points out
to a possible issue.
Section 4.6 states that "The IETF maintains a leap second list". How
is that list updated by the IETF?
Section 6 has the following: "but these concepts may (or may not)
have been mitigate". How are concepts mitigated?
Regards,
S. Moonesamy
1. https://www.ripe.net/publications/docs/ripe-432
