[Git][NTPsec/ntpsec][master] 5 commits: Add link to IETF NTP WG docs

Sun May 28 19:30:34 UTC 2017

Eric S. Raymond pushed to branch master at NTPsec / ntpsec


Commits:
bd299b21 by Sanjeev Gupta at 2017-05-28T20:33:03+08:00
Add link to IETF NTP WG docs

- - - - -
62433f4c by Sanjeev Gupta at 2017-05-28T20:41:25+08:00
Proofread and typos

- - - - -
15f9277a by Sanjeev Gupta at 2017-05-28T20:45:40+08:00
Add note on non-RTC systems

Systems without an RTC, and which run some variant of Linux
may initialise the system clock to 01-01-1970.

- - - - -
956dbf10 by Sanjeev Gupta at 2017-05-28T20:55:56+08:00
Read and polish some language, no semantic changes

- - - - -
b3b27f4c by Sanjeev Gupta at 2017-05-28T21:00:39+08:00
Document location of ifdex tool

- - - - -


5 changed files:

- devel/ifdex-ignores
- devel/ntpv5.txt
- devel/packaging.txt
- devel/pre-release.txt
- devel/testing.txt


Changes:

=====================================
devel/ifdex-ignores
=====================================

--- a/devel/ifdex-ignores
+++ b/devel/ifdex-ignores
@@ -2,6 +2,8 @@
 # and filter reports about #if guards in order to locate configuration symbols
 # and plain old cruft.
 #
+# The ifdex tool is available at http://www.catb.org/~esr/ifdex/
+#
 # Should be used together with waf's config.h output, which ifdex can
 # interpret to exclude most of its config symbols. Thus, from the toplevel
 # directory:


=====================================
devel/ntpv5.txt
=====================================
--- a/devel/ntpv5.txt
+++ b/devel/ntpv5.txt
@@ -1,7 +1,8 @@
 = Preliminary design notes for the NTPv5 protocol =
 
 NTPv4 is showing its age.  There are functional capabilities that
-would be very useful if they could be standardized, but are not.
+would be very useful if they could be standardized, but
+currently are not.
 
 This document will first list these missing bits, then discuss
 ways to incorporate them.
@@ -14,8 +15,8 @@ Reference IDs are used by Stratum 1 sources to identify clocks and
 clock types, and by hosts at higher strata to perform loop detection.
 
 The REFID field is 4 octets long, sufficient to hold an IPv4 address
-for loop detection. This is inadequate for IPV6, so the reference ID of
-an IPv6 host is a 4-octet hash of itscactual address. Hash collisions
+for loop detection. This is inadequate for IPv6, so the reference ID of
+an IPv6 host is a 4-octet hash of its actual address. Hash collisions
 have been observed in the wild, possiblty resulting in false-positive
 loop detection.
 
@@ -28,7 +29,7 @@ Most servers ship UTC.  Some ship TAI. Some perform leap-second
 smearing, some do not.
 
 The new protocol should enable a server to advertise its timescale,
-including its current leapsecond offset.
+including, if applicable in its timescale, its current leapsecond offset.
 
 === Era ===
 
@@ -41,6 +42,8 @@ epoch.
 
 The IETF is attempting to develop a new cryptographic standard for
 secure/authenticated time exchange: Network Time Security.
+Further information on this is available at:
+https://tools.ietf.org/wg/ntp/
 
 The new protocol needs to allow a block of data of as-yet unspecified
 and possibly variable size to be dedicated to NTS use.
@@ -73,7 +76,7 @@ world's firewalls to pass through a new port is not easy.
 
 === Newmode ===
 
-In this approach, the the NTP port number is retained.  So is at least
+In this approach, the NTP port number is retained.  So is at least
 the first byte of the v4 packet header structure, so that the version
 number and packet mode are at the same offset as in v4. The version
 field *is* incremented to 5.


=====================================
devel/packaging.txt
=====================================
--- a/devel/packaging.txt
+++ b/devel/packaging.txt
@@ -79,7 +79,8 @@ sensors, the NMEA driver in NTPsec sometimes has to make an assumption
 about what century it is.  Choice of a base-century hits the same
 issues; so here the year derived from the BUILD_EPOCH is also used.  The
 alternative - trusting the system clock to report the right century -
-could produce very bad behavior near century boundaries.
+could produce very bad behavior near century boundaries, and also on
+cold-start of systems without an RTC.
 
 // end
 


=====================================
devel/pre-release.txt
=====================================
--- a/devel/pre-release.txt
+++ b/devel/pre-release.txt
@@ -28,6 +28,7 @@ know if that is ready yet. (Jan 2017)
 We really need to test on an other-endian platform.
 NetBSD runs Big Endian on some ARM systems.
   https://wiki.netbsd.org/ports/evbarm/allwinner/
+Debian runs Big Endian on MIBSbe (tested May 2017).
 
 We should try as many refclocks as we can on as many
 OS/distros as we can.  This is testing the OS kernel
@@ -45,7 +46,7 @@ We should review any documentation for best-practices and verify
 that any sample code and build recipies work as expected.  In
 particular, we should make sure the pool option works and that
 the Raspberry Pi Stratum 1 server HOWTO works.
-(There are two sample ntp.conf files in contrib/
+(There are two sample ntp.conf files in contrib/ .
 Both use the pool.  Jan 2017)
 
 
@@ -60,7 +61,7 @@ will override that panic and allow one big step.
 
 We should verify that the cx_Freeze recipe for converting
 our Python based utilities to non-Python works.
-Details in devel/packaging.txt
+Details are in devel/packaging.txt
 
 We should test cold-start with no drift file.
 


=====================================
devel/testing.txt
=====================================
--- a/devel/testing.txt
+++ b/devel/testing.txt
@@ -3,7 +3,8 @@
 This assumes you have downloaded the source and built a system
 and now you want to test your new ntpd.
 
-For help on getting that far, see ../INSTALL
+For help on getting that far, see the file INSTALL in the top-level
+directory.
 
 == Path problems with the test tools ==
 
@@ -14,7 +15,7 @@ directory to ntpclients/ and run ./ntpq there. If you get a message that says
 ntpq: can't find Python NTP library -- check PYTHONPATH.
 ---------------------------------------------------------------------
 
-you have a problem.  A lot of what was C code in legacy versions
+you *may* have a problem.  A lot of what was C code in legacy versions
 (pretty much everything except ntpd itself, in fact) has been moved to
 Python in order to improve maintainability and decrease attack
 surface.  Most of these tools share a Python library of critical
@@ -58,7 +59,7 @@ For a one-off test:
 
 3. Run ./build/ntpd/ntpd plus the command line parameters from above. 
 
-4. It will daemonize itself and give you back your terminal.
+4. It will daemonize itself and give you back your terminal prompt.
 
 Your current /etc/ntp.conf should work correctly.
 



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/35ebc3c80a43c1cffc51868cb93d6890bdcde914...b3b27f4cb3dae8c224b29f47d5cca29888a2e20d

---
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/35ebc3c80a43c1cffc51868cb93d6890bdcde914...b3b27f4cb3dae8c224b29f47d5cca29888a2e20d
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20170528/1b386383/attachment.html>
