<html lang='en'>
<head>
<meta content='text/html; charset=utf-8' http-equiv='Content-Type'>
<title>
GitLab
</title>
</meta>
</head>
<style>
img {
max-width: 100%;
height: auto;
}
p.details {
font-style:italic;
color:#777
}
.footer p {
font-size:small;
color:#777
}
pre.commit-message {
white-space: pre-wrap;
}
.file-stats a {
text-decoration: none;
}
.file-stats .new-file {
color: #090;
}
.file-stats .deleted-file {
color: #B00;
}
</style>
<body>
<div class='content'>
<h3>
Eric S. Raymond pushed to branch master
at <a href="https://gitlab.com/NTPsec/ntpsec">NTPsec / ntpsec</a>
</h3>
<h4>
Commits:
</h4>
<ul>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/9419cb6d46bc661cae244e9f7be21308bff997b9">9419cb6d</a></strong>
<div>
<span>by Matt Selsky</span>
<i>at 2016-02-25T00:29:05-05:00</i>
</div>
<pre class='commit-message'>Remove extra semicolon outside of a function.</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/09afc94d0552baaa4747c09ffadd4f3457a3886e">09afc94d</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-02-25T00:29:58-05:00</i>
</div>
<pre class='commit-message'>Work through FIXME in docs, updating markup and links</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/a44fd86f6a67972716b7036b01235415ca3f1ef4">a44fd86f</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-02-25T00:31:02-05:00</i>
</div>
<pre class='commit-message'>Document potential removal of some driver8 (PARSE) modes</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/8b2e68035359ca0b717ffb620562ffe9100154c1">8b2e6803</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-02-25T00:31:02-05:00</i>
</div>
<pre class='commit-message'>Add note on Mode 3 and 4 in refclock_parse.c</pre>
</li>
</ul>
<h4>10 changed files:</h4>
<ul>
<li class='file-stats'>
<a href='#diff-0'>
docs/authentic.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-1'>
docs/driver20.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-2'>
docs/driver30.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-3'>
docs/driver8.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-4'>
docs/driver9.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-5'>
docs/filter.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-6'>
docs/index.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-7'>
docs/rate.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-8'>
libntp/authkeys.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-9'>
ntpd/refclock_parse.c
</a>
</li>
</ul>
<h4>Changes:</h4>
<li id='diff-0'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-0'>
<strong>
docs/authentic.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/authentic.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/authentic.txt
</span><span style="color: #aaaaaa">@@ -164,7 +164,7 @@ selects the key used as the password for the {ntpqman} utility.
</span> //strong security against replay with or without modification, spoofing,
//masquerade and most forms of clogging attacks.
//
<span style="color: #000000;background-color: #ffdddd">-////FIXME: page reference may be invalid
</span><span style="color: #000000;background-color: #ddffdd">+//FIXME: page reference may be invalid
</span> //The Autokey protocol has several modes of operation corresponding to
//the various NTP modes supported. Most modes use a special cookie which
//can be computed independently by the client and server, but encrypted
</code></pre>
<br>
</li>
<li id='diff-1'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-1'>
<strong>
docs/driver20.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/driver20.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/driver20.txt
</span><span style="color: #aaaaaa">@@ -49,7 +49,6 @@ The various GPS sentences that this driver recognises look like this:
</span> |$GPZDG,GPSTIME,DD,MM,YYYY,AA.BB,V*CS<cr><lf>|Accord
|=============================================================================
<span style="color: #000000;background-color: #ffdddd">-//FIXME: 'GPS sync status' in table not indented properly
</span> .NMEA data items
[cols="15%,85%",options="header"]
[options="header"]
<span style="color: #aaaaaa">@@ -185,7 +184,6 @@ example:
</span> Sentences like $GPGSV that don't contain the time will get counted in
the total but otherwise ignored.
<span style="color: #000000;background-color: #ffdddd">-//FIXME: ntp.org reference
</span> http://support.ntp.org/bin/view/Support/ConfiguringNMEARefclocks[Configuring
NMEA Refclocks] might give further useful hints for specific hardware
devices that exhibit strange or curious behaviour.
</code></pre>
<br>
</li>
<li id='diff-2'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-2'>
<strong>
docs/driver30.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/driver30.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/driver30.txt
</span><span style="color: #aaaaaa">@@ -11,7 +11,7 @@ PPS Port: /dev/oncore.pps._u_
</span> == Description ==
This driver supports most models of the
<span style="color: #000000;background-color: #ffdddd">-http://www.mot.com/AECS/PNSB/products[Motorola Oncore GPS receivers]
</span><span style="color: #000000;background-color: #ddffdd">+https://web.archive.org/web/19990427102123/http://www.mot.com/AECS/PNSB/products/produt.html[Motorola Oncore GPS receivers]
</span> (Basic, PVT6, VP, UT, UT+, GT, GT+, SL, M12, M12+T), as long as they
support the _Motorola Binary Protocol_.
<span style="color: #aaaaaa">@@ -21,7 +21,7 @@ available new, and the UT, GT, and SL are at end-of-life. The Motorola
</span> evaluation kit can be recommended. It interfaces to a PC straightaway,
using the serial (DCD) or parallel port for PPS input and packs the
receiver in a nice and sturdy box. Less expensive interface kits are
<span style="color: #000000;background-color: #ffdddd">-available from http://www.tapr.org[TAPR] and
</span><span style="color: #000000;background-color: #ddffdd">+available from http://www.tapr.org[TAPR].
</span>
[width="100%",cols="<34%,<33%,<33%",align="center",frame="none",grid="none"]
|==========================================================================
<span style="color: #aaaaaa">@@ -84,10 +84,9 @@ on Linux, SunOS and Solaris.
</span>
=== Configuration ===
<span style="color: #000000;background-color: #ffdddd">-//FIXME: Ignored backticks around ntp.oncore
</span> There is a driver specific configuration file +ntp.oncore+ (or
<span style="color: #000000;background-color: #ffdddd">-+ntp.oncore.+_u_ or +ntp.oncore+_u_ if you must distinguish between more
-than one Oncore receiver) that contains information on the startup mode,
</span><span style="color: #000000;background-color: #ddffdd">++ntp.oncore.+'u' or +ntp.oncore+'u' if you must distinguish between more
+than one Oncore receiver _unit_) that contains information on the startup mode,
</span> the location of the GPS receiver, an offset of the PPS signal from zero,
and the cable delay. The offset shifts the PPS signal to avoid interrupt
pileups +on' the second, and adjusts the timestamp accordingly. See the
<span style="color: #aaaaaa">@@ -109,8 +108,8 @@ factor will be the timebase of the computer and the precision with which
</span> you can timestamp the rising flank of the PPS signal. Using FreeBSD, a
FPGA based Timecounter/PPS interface, and an ovenized quartz oscillator,
that performance has been reproduced. For more details on this aspect:
<span style="color: #000000;background-color: #ffdddd">-http://phk.freebsd.dk/rover.html[Sub-Microsecond timekeeping under
-FreeBSD].
</span><span style="color: #000000;background-color: #ddffdd">+https://web.archive.org/web/19990221121441/http://phk.freebsd.dk/rover.html[Sub-Microsecond
+timekeeping under FreeBSD].
</span>
'''''
</code></pre>
<br>
</li>
<li id='diff-3'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-3'>
<strong>
docs/driver8.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/driver8.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/driver8.txt
</span><span style="color: #aaaaaa">@@ -14,9 +14,15 @@ PPS device: /dev/refclockpps-'u'; alternate PPS device
</span>
== Description ==
<span style="color: #000000;background-color: #ffdddd">-The PARSE driver supports 20 different clock
</span><span style="color: #000000;background-color: #ddffdd">+The PARSE driver supports 25 different clock
</span> types/configurations. PARSE is actually a multi-clock driver.
<span style="color: #000000;background-color: #ddffdd">+Note that some of these modes below are to support equipment that
+has not been commercially available for a long time; and may be
+removed. See
+https://www.ntpsec.org/removal-plan.html[Feature removals] for a
+discussion of this issue.
+
</span> The actual receiver status is mapped into various synchronization states
generally used by receivers. The driver is configured to interpret the
time codes of Meinberg DCF77 AM receivers, DCF77 FM receivers, Meinberg
<span style="color: #aaaaaa">@@ -66,9 +72,10 @@ refclock_ppstime::
</span>
== Supported Devices ==
<span style="color: #000000;background-color: #ffdddd">-Currently, twenty-four clock types are supported by the PARSE driver and
</span><span style="color: #000000;background-color: #ddffdd">+Currently, twenty-five clock types are supported by the PARSE driver and
</span> up to four (devices /dev/refclock-0 - /dev/refclock-3) of these clocks
may be operational at any one time.
<span style="color: #000000;background-color: #ddffdd">+
</span> A note on the implementations:
* These implementations were mainly done without actual access to the
<span style="color: #aaaaaa">@@ -104,17 +111,23 @@ This implementation was provided and verified by SEL and
</span> http://networktimefoundation.org[Network Time Foundation] has an
SEL-2407 in one of its development labs.
<span style="color: #000000;background-color: #ffdddd">-The pictures below have been taken from and are linked to the vendors'
-web pages.
</span><span style="color: #000000;background-color: #ddffdd">+The pictures below have been archived from the vendors' web pages.
</span>
* *server 127.127.8.0-3 mode 0*
+
<span style="color: #000000;background-color: #ffdddd">-*http://www.meinberg.de[Meinberg] http://www.meinberg.de/english/products/timesource.htm#dcf---freq_sync[PZF5xx receiver family] (FM demodulation/TCXO / 50μs)*
-
</span><span style="color: #000000;background-color: #ddffdd">+*http://www.meinberg.de[Meinberg] https://www.meinbergglobal.com/english/archive/pzf511.htm[PZF5xx receiver family] (FM demodulation/TCXO / 50μs)*
++
+WARNING: This equipment is no longer available for commercial sale, and
+support may be removed in the future. See:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
</span>
* *server 127.127.8.0-3 mode 1*
+
<span style="color: #000000;background-color: #ffdddd">-*http://www.meinberg.de[Meinberg] http://www.meinberg.de/english/products/timesource.htm#dcf---freq_sync[PZF5xx receiver family] (FM demodulation/OCXO / 50μs)*
</span><span style="color: #000000;background-color: #ddffdd">+*http://www.meinberg.de[Meinberg] https://www.meinbergglobal.com/english/archive/pzf511.htm[PZF5xx receiver family] (FM demodulation/OCXO / 50μs)*
++
+WARNING: This equipment is no longer available for commercial sale, and
+support may be removed in the future. See:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
</span>
image::pic/pzf511.jpg[http://www.meinberg.de/english/products/pzf-eurocard.htm]
<span style="color: #aaaaaa">@@ -140,10 +153,18 @@ that comes with the Meinberg driver package.
</span> * *server 127.127.8.0-3 mode 3*
+
http://www.elv.de/[ELV] *DCF7000 (sloppy AM demodulation / 50ms)*
<span style="color: #000000;background-color: #ddffdd">++
+WARNING: This equipment is no longer available for commercial sale, and
+support may be removed in the future. See:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
</span>
* *server 127.127.8.0-3 mode 4*
+
*Walter Schmid DCF receiver Kit (AM demodulation / 1ms)*
<span style="color: #000000;background-color: #ddffdd">++
+WARNING: This equipment is no longer available for commercial sale, and
+support may be removed in the future. See:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
</span>
* *server 127.127.8.0-3 mode 5*
+
<span style="color: #aaaaaa">@@ -182,11 +203,19 @@ image:pic/igclock.gif[http://www.igel.de/eigelmn.html]
</span> * *server 127.127.8.0-3 mode 9*
+
*http://www.trimble.com[Trimble] ftp://ftp.trimble.com/pub/sct/embedded/bin/Data%20Sheets/SveeSix2.PDF[SVeeSix GPS receiver] TAIP protocol (GPS / <<1μs)*
<span style="color: #000000;background-color: #ddffdd">++
+WARNING: This equipment is no longer available for commercial sale, and
+support may be removed in the future. See:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
</span>
* *server 127.127.8.0-3 mode 10*
+
*http://www.trimble.com[Trimble] ftp://ftp.trimble.com/pub/sct/embedded/bin/Data%20Sheets/SveeSix2.PDF[SVeeSix GPS receiver] (GPS / <<1μs) (no kernel support yet)*
+
<span style="color: #000000;background-color: #ddffdd">+WARNING: This equipment is no longer available for commercial sale, and
+support may be removed in the future. See:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
++
</span> image:pic/pd_om011.gif[http://www.trimble.com/cgi/omprod.cgi/pd_om011.html]
+
image:pic/pd_om006.gif[http://www.trimble.com/cgi/omprod.cgi/pd_om006.html]
</code></pre>
<br>
</li>
<li id='diff-4'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-4'>
<strong>
docs/driver9.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/driver9.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/driver9.txt
</span><span style="color: #aaaaaa">@@ -21,11 +21,11 @@ precision timing applications. This driver supports all compatible
</span> receivers such as the 6-channel MX4200, MX4200D, and the 12-channel
MX9212, MX9012R, MX9112.
<span style="color: #000000;background-color: #ffdddd">-//FIXME: caption and float attributes not showing up correctly
-image:pic/9400n.jpg["MX9400N",float="left",link="http://www.leica-gps.com/", caption="Leica MX9400N Navigator"] http://www.leica-gps.com/[Leica Geosystems] acquired the
-Magnavox commercial GPS technology business in February of 1994. They
-now market and support former Magnavox GPS products such as the MX4200
-and its successors.
</span><span style="color: #000000;background-color: #ddffdd">+image:pic/9400n.jpg["MX9400N",float="left",caption="Leica MX9400N Navigator"]
+https://web.archive.org/web/19971014210945/http://www.leica-gps.com/[Leica
+Geosystems] acquired the Magnavox commercial GPS technology business in
+February of 1994. They marketed and supported former Magnavox GPS
+products such as the MX4200 and its successors.
</span>
== Operating Modes ==
</code></pre>
<br>
</li>
<li id='diff-5'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-5'>
<strong>
docs/filter.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/filter.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/filter.txt
</span><span style="color: #aaaaaa">@@ -72,8 +72,7 @@ process inserts a dummy infinity sample in the shift register for each
</span> poll sent. After eight polls, the register returns to its original
state.
<span style="color: #000000;background-color: #ffdddd">-//FIXME: Image pair not centered
-image:pic/flt1.gif[] image:pic/flt2.gif[]
</span><span style="color: #000000;background-color: #ddffdd">+image:pic/flt1.gif["Raw",align="left"] image:pic/flt2.gif["Filtered",align="right"]
</span>
Figure 2. Raw (left) and Filtered (right) Offsets
</code></pre>
<br>
</li>
<li id='diff-6'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-6'>
<strong>
docs/index.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/index.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/index.txt
</span><span style="color: #aaaaaa">@@ -161,7 +161,7 @@ link:rate.html[Rate Management]::
</span> Describes the principles of rate management to minimize network load
and defend against DoS attacks.
link:refclock.html[Reference Clock Support]::
<span style="color: #000000;background-color: #ffdddd">- Describes the collection of radio clocks used to synchronize primary
</span><span style="color: #000000;background-color: #ddffdd">+ Describes the collection of clocks and devices used to synchronize primary
</span> servers.
link:warp.html[How NTP Works]::
Gives an overview of the NTP daemon architecture and how it works.
</code></pre>
<br>
</li>
<li id='diff-7'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-7'>
<strong>
docs/rate.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/rate.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/rate.txt
</span><span style="color: #aaaaaa">@@ -36,10 +36,17 @@ that can clog the server and network infrastructure. On the other hand,
</span> friendly clients need to avoid configurations that can result in
unfriendly behavior.
<span style="color: #000000;background-color: #ffdddd">-//FIXME: add footnote ref.
</span> A review of past client abuse incidence shows the most frequent scenario
is a broken client that attempts to send packets at rates of one per
<span style="color: #000000;background-color: #ffdddd">-second or more. On one occasion due to a defective client design [1],
</span><span style="color: #000000;background-color: #ddffdd">+second or more. On one occasion due to a defective client design
+footnote:[1. Mills, D.L., J. Levine, R. Schmidt and D. Plonka. Coping with
+overload on the Network Time Protocol public servers. _Proc. Precision
+Time and Time Interval (PTTI) Applications and Planning Meeting_
+(Washington DC, December 2004), 5-16. Paper:
+{millshome}database/papers/ptti/ptti04a.pdf[PDF],
+Slides:{millshome}database/brief/ptti/ptti04.pdf[PDF]
+|
+{millshome}database/brief/ptti/ptti04.ppt[PowerPoint]]
</span> over 750,000 clients demonstrated this abuse. There have been occasions
where this abuse has persisted for days at a time. These scenarios are
the most damaging, as they can threaten not only the victim server but
</code></pre>
<br>
</li>
<li id='diff-8'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-8'>
<strong>
libntp/authkeys.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/libntp/authkeys.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/libntp/authkeys.c
</span><span style="color: #aaaaaa">@@ -55,7 +55,7 @@ static void freesymkey(symkey *, symkey **);
</span> static void free_auth_mem(void);
#endif
<span style="color: #000000;background-color: #ffdddd">-symkey key_listhead; /* list of all in-use keys */;
</span><span style="color: #000000;background-color: #ddffdd">+symkey key_listhead; /* list of all in-use keys */
</span> /*
* The hash table. This is indexed by the low order bits of the
* keyid. This gets updated in auth_resize_hashtable
</code></pre>
<br>
</li>
<li id='diff-9'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1#diff-9'>
<strong>
ntpd/refclock_parse.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/refclock_parse.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/refclock_parse.c
</span><span style="color: #aaaaaa">@@ -13,6 +13,8 @@
</span> * next time this code gets serious attention. In particular, modes 9 and 10
* support the Trimble SVeeSix, which was discontinued before 2003. Related
* code in the parse library could also be dropped.
<span style="color: #000000;background-color: #ddffdd">+ * Also see modes 3 and 4, for which no information in use since 1999 and
+ * 2001 respectively can be found on the web.
</span> */
#include "config.h"
</code></pre>
<br>
</li>
</div>
<div class='footer' style='margin-top: 10px;'>
<p>
—
<br>
<a href="https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1">View it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
adjust your notification settings.
</p>
</div>
</body>
</html>