-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathdrivers.html
825 lines (815 loc) · 40.6 KB
/
drivers.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="AsciiDoc 8.6.9">
<title>NTPD driver retention analysis</title>
<link rel="stylesheet" href="./asciidoc.css" type="text/css">
<script type="text/javascript" src="./asciidoc.js"></script>
<script type="text/javascript">
/*<![CDATA[*/
asciidoc.install();
/*]]>*/
</script>
</head>
<body class="article">
<div id="header">
<h1>NTPD driver retention analysis</h1>
<span id="author">Eric S. Raymond</span><br>
<span id="email" class="monospaced"><<a href="mailto:[email protected]">[email protected]</a>></span><br>
<span id="revnumber">version 1.4,</span>
<span id="revdate">2015-06-30</span>
</div>
<div id="content">
<div class="sect1">
<h2 id="_summary">Summary</h2>
<div class="sectionbody">
<div class="paragraph"><p>ntpd contains support for 42 driver types. Of these: 2 are IPC drivers
which must be retained; 10 are for hardware that might, under very
generous assumptions, still be of use; and 30 can be discarded.</p></div>
<div class="paragraph"><p>Out of that 10, the actual utility of some remains dubious, but the
cultural/political context of the project probably requires that we
retain them. I discuss related issues in a concluding section.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_technological_context">Technological context</h2>
<div class="sectionbody">
<div class="paragraph"><p>NTP’s driver inventory contains several different classes of precision
time sources. The software is now around 40 years old, and some of
those classes are now obsolescent or semi-obsolescent.</p></div>
<div class="paragraph"><p>See <a href="http://www.catb.org/gpsd/time-service-intro.html">"Introduction to
Time Service"</a> for terminology, device classes, and accuracy. The
summary version is that inexpensive 1PPS-capable GPS devices have a
nearly overwhelming cost-effectivenee advantage over older time source
types, and the utility of supporting those older types is accordingly
plummeting.</p></div>
<div class="paragraph"><p>I think it is actually seriously questionable whether support for
<strong>any</strong> of these legacy devices is worth maintaining. No hardware
drivers have been added since 2006, and possibly none since 2002.
NIST’s modulation change in 2013 laid waste to the U.S. time-radio
industry. It may actually be the case that <strong>all</strong> the Stratum 1 sites
running non-custom ntpd instances are using GPSes now.</p></div>
<div class="paragraph"><p>However, political reality - especially for a federally-funded project
with customers in a lot of .gov and .mil shops running very old iron -
does not necessarily allow the best technical move, which would be to
drop all the drivers, see who screams, and reinstate the fewest we
can. I will return to this issue.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_objectives_and_criteria">Objectives and criteria</h2>
<div class="sectionbody">
<div class="paragraph"><p>Two of our main objectives in the ntpd rescue are (1) to eliminate security
vulnerabilities and (2) move the code to a maintainable state. An
effective way of accomplishing both would be to outright remove as
much code as possible from ntpd.</p></div>
<div class="paragraph"><p>ntpd includes no fewer than 46 device drivers for local clock sources.
Some effective means of removing code would be to remove drivers which
are obsolescent by the following criteria:</p></div>
<div class="dlist"><dl>
<dt class="hdlist1">
INTRINSIC
</dt>
<dd>
<p>
Remove hardware that can no longer work for intrinsic technical reasons.
</p>
</dd>
<dt class="hdlist1">
DEPRECATED
</dt>
<dd>
<p>
Remove deprecated drivers - that is, drivers which the ntpd
documentation itself declares obsolete or no longer documents.
</p>
</dd>
<dt class="hdlist1">
DISCONTINUED
</dt>
<dd>
<p>
Remove drivers for products that have been discontinued for
more than seven years. (In the first version of this report
the proposal was ten years. Please see the final section
on policy and conclusions.)
</p>
</dd>
<dt class="hdlist1">
UNAVAILABLE
</dt>
<dd>
<p>
Remove drivers for products which cannot be found for sale
with a web search. (I have noted when remaindered units are
available on e-Bay and second-hand sites.)
</p>
</dd>
<dt class="hdlist1">
REDUNDANT
</dt>
<dd>
<p>
Remove drivers that duplicate capabilities better provided by
GPSD (or, in principle, other sensor managers).
</p>
</dd>
<dt class="hdlist1">
INACCURATE
</dt>
<dd>
<p>
Remove GPS drivers and time radios for which the hardware offers no
better source accuracy than a timing GPS available for less than
$75 in 2015; that is, about 5µs. (However, do not necessarily
remove poorer-performing GPS-conditioned <strong>clocks</strong>, as they continue
to supply time in holdover mode when the GPS cannot get satellite lock.)
</p>
</dd>
</dl></div>
<div class="paragraph"><p>We should certainly keep drivers such as SHM and GPSD-NG that are IPC
methods for peer time-source programs in ntpd itself.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_first_round_triage">First-round triage</h2>
<div class="sectionbody">
<div class="paragraph"><p>The following lists the drivers in ntpd4, categorizes them, and
recommends a disposition for each. It’s based on the master list
from the NTP Classic documentation.</p></div>
<div class="paragraph"><p>Types 15, 23, 24, and 25 are not listed because they are reserved and
not in use.</p></div>
<div class="sect2">
<h3 id="_type_1_undisciplined_local_clock">Type 1: Undisciplined Local Clock</h3>
<div class="paragraph"><p>This driver type is described as deprecated. It is in any case
obsolete anywhere with a sky view, where a GPS will do a better job.</p></div>
<div class="paragraph"><p>Disposition: Fails tests DEPRECATED and INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_2_trak_8820_gps_receiver">Type 2: Trak 8820 GPS Receiver</h3>
<div class="paragraph"><p>This driver still existed only as one mention in the ntp4
documentation. There is no refclock implementation for it.</p></div>
<div class="paragraph"><p>Web searches reach one copy of the technical manual dating from 1994
and preserved here:</p></div>
<div class="paragraph"><p><a href="http://www.to-way.com/tf/trak8820a.pdf">http://www.to-way.com/tf/trak8820a.pdf</a></p></div>
<div class="paragraph"><p>All other references are to copies of old ntpd documentation. I
conclude that this hardware is extremely obsolete and
discontinued well before before 2000.</p></div>
<div class="paragraph"><p>Disposition: Fails tests DEPRECATED, DISCONTINUED, UNAVAILABLE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_3_psti_traconex_1020_wwv_wwvh_receiver_wwv_pst">Type 3: PSTI/Traconex 1020 WWV/WWVH Receiver (WWV_PST)</h3>
<div class="paragraph"><p>This device is described <a href="http://prc68.com/I/PST1020.shtml">here</a> with a
2005 note that it is "not very reliable" having drifted by a full minute.</p></div>
<div class="paragraph"><p>Investigating the vendor site at U.S. Traffic Corp (now Peek Traffic)
reveals that this device was discontinued, probably before 2000.</p></div>
<div class="paragraph"><p>According to this August 2001 post</p></div>
<div class="paragraph"><p><a href="https://groups.google.com/forum/#!topic/comp.protocols.time.ntp/0jOItglBTLE">https://groups.google.com/forum/#!topic/comp.protocols.time.ntp/0jOItglBTLE</a></p></div>
<div class="paragraph"><p>the device required manual intervention every year and was not
designed for use after 2001. Dave Mills replied to that one in a way
that implies he still has two of these and there is a workaround to
the problem described, but also says they have a service life of only
a few years due to a failure-prone component.</p></div>
<div class="paragraph"><p>I could not find any for sale on the Web. This hardware
would no longer work even if a specimen could be found, due to WWVB’s
modulation change as described in the next entry.</p></div>
<div class="paragraph"><p>Disposition: Fails tests INTRINSIC, DISCONTINUED, UNAVAILABLE, and
INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_4_spectracom_wwvb_gps_receivers_wwvb_spec">Type 4: Spectracom WWVB/GPS Receivers (WWVB_SPEC)</h3>
<div class="paragraph"><p>Since WWVB changed its modulation scheme in January 2013
Spectracom WWVB receivers from before that date no longer function.
The models covered by this driver (Model 8170, Netclock/2 WWVB) are in
this category. Spectracom has not produced any new time-radio gear
since the modulation change.</p></div>
<div class="paragraph"><p>However, the Spectracom 9300 (still in production and support)
is a GPS clock that can emit the type 0 and 2 formats recognized
by this driver.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_5_truetime_gps_goes_omega_receivers_truetime">Type 5: TrueTime GPS/GOES/OMEGA Receivers (TRUETIME) ==</h3>
<div class="paragraph"><p>True Time was a product line of timer sources. The most recent manual
I can find is from 1997:</p></div>
<div class="paragraph"><p>www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA324042</p></div>
<div class="paragraph"><p>The devices can be found for sale, but only on e-Bay and electronics
remainder sites. The vendor seems to be long gone.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_6_irig_audio_decoder_irig_audio">Type 6: IRIG Audio Decoder (IRIG_AUDIO)</h3>
<div class="paragraph"><p>This driver is a very, very bad idea given flesh. It demodulates an
<strong>audio signal</strong> emitted by several radio time sources, requiring custom
wiring to connect to a microphone or line-in port. All for
accuracy two orders of magnitude worse (500µs) than a cheap 1PPS GPS
and no holdover capability.</p></div>
<div class="paragraph"><p>Disposition: INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_7_radio_chu_audio_demodulator_decoder_chu">Type 7: Radio CHU Audio Demodulator/Decoder (CHU)</h3>
<div class="paragraph"><p>A very bad idea similarly wired to Type 6, using a Canadian analog
of WWVB. Cited as 1ms accuracy without GPS calibration.</p></div>
<div class="paragraph"><p>Disposition: INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_8_generic_reference_driver_parse">Type 8: Generic Reference Driver (PARSE)</h3>
<div class="paragraph"><p>This is a driver supporting a large variety of time radios, some of
which (such as the Meinberg line) are still generally available.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_9_magnavox_mx4200_gps_receiver_gps_mx4200">Type 9: Magnavox MX4200 GPS Receiver (GPS_MX4200)</h3>
<div class="paragraph"><p>A line of GPSes produced by Magnavox, discontinued in 1994, with
the surplus stock marketed by Leica Geosystems. Leica no longer
sells them. They shipped 1PPS. I could find none available for sale.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED, UNAVAILABLE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_10_austron_2200a_2201a_gps_receivers_gps_as2201">Type 10: Austron 2200A/2201A GPS Receivers (GPS_AS2201)</h3>
<div class="paragraph"><p>An obsolete line of 1PPS GPS receivers. Austron was acquired some
time before 1996 and the product line apparently discontinued then.
A few units were still in hobbyist use in 2006, but there don’t
seem to be more recent references even on the time-nuts list.
I could find none available for sale.</p></div>
<div class="paragraph"><p>Disposition: Fails tests DISCONTINUED, UNAVAILABLE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_11_arbiter_1088a_b_gps_receiver_gps_arbiter">Type 11: Arbiter 1088A/B GPS Receiver (GPS_ARBITER)</h3>
<div class="paragraph"><p>Arbiter systems is still alive at <a href="http://www.arbiter.com/">http://www.arbiter.com/</a></p></div>
<div class="paragraph"><p>With 100ns worst-case accuracy relative to 1PPS this is still a viable
time source.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_12_ksi_odetics_tpro_s_irig_interface_irig_tpro">Type 12: KSI/Odetics TPRO/S IRIG Interface (IRIG_TPRO)</h3>
<div class="paragraph"><p>An obsolete clock source that connected directly to the SBus of a Sun
workstation. SBus was replaced rapidly by PCI after 1997; no hardware
based on SBus has been shipped for at least a decade and the last
of these were probably shipped before the year 2000. I could find
none of them for sale.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED, UNAVAILABLE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_13_leitch_csd_5300_master_clock_controller_atom_leitch">Type 13: Leitch CSD 5300 Master Clock Controller (ATOM_LEITCH)</h3>
<div class="paragraph"><p>Documentation has been removed from the ntpd4 webpages.</p></div>
<div class="paragraph"><p>A clock source that synchronized with the U.S. national time authority
via modem. Leitch was acquired by Harris Broadcasting in 2005.</p></div>
<div class="paragraph"><p>Propagation jitter in the POTS network dooms any chance this could
even match the performance of a cheap serial GPS. Remnant units are
available on eBay and electronics remainder sites.</p></div>
<div class="paragraph"><p>Disposition: DEPRECATED, DISCONTINUED, and INACCURATE; already removed.</p></div>
</div>
<div class="sect2">
<h3 id="_type_14_ees_m201_msf_receiver_msf_ees">Type 14: EES M201 MSF Receiver (MSF_EES)</h3>
<div class="paragraph"><p>Documentation for this driver has been removed from the ntpd4 webpages.</p></div>
<div class="paragraph"><p>All the references to it I can find on the Web point back
to old NTP documentation. I conclude that it is obsolete.</p></div>
<div class="paragraph"><p>Disposition: Fails test DEPRECATED and DISCONTINUED; already removed.</p></div>
</div>
<div class="sect2">
<h3 id="_type_16_bancomm_gps_irig_receiver_gps_bancomm">Type 16: Bancomm GPS/IRIG Receiver (GPS_BANCOMM)</h3>
<div class="paragraph"><p>A discontinued VME board for Sun 4 systems. The last VME-based
Sun 4 issued in 1989 to be replaced by SBus systems also now
obsolete.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_17_datum_precision_time_system_gps_datum">Type 17: Datum Precision Time System (GPS_DATUM)</h3>
<div class="paragraph"><p>Documentation has been removed from the ntpd4 webpages. There used to
be a company called Datum that sold clock sources, but it has left no
traces on the Web and I can find no evidence of surviving hardware.</p></div>
<div class="paragraph"><p>Disposition: DEPRECATED, DISCONTINUED, UNAVAILABLE; already removed.</p></div>
</div>
<div class="sect2">
<h3 id="_type_18_nist_usno_ptb_modem_time_services_acts_modem">Type 18: NIST/USNO/PTB Modem Time Services (ACTS_MODEM)</h3>
<div class="paragraph"><p>The USNO timer service still nominally exists, but requires a
Hayes-compatible 1200bps modem, hardware now 20 years obsolete:</p></div>
<div class="paragraph"><p><a href="http://tycho.usno.navy.mil/modem_time.html">http://tycho.usno.navy.mil/modem_time.html</a></p></div>
<div class="paragraph"><p>It claims 4ms jitter (before propagation delays in the POTS network).
Retain because it might be useful in holdover mode.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_19_heath_wwv_wwvh_receiver_wwv_heath">Type 19: Heath WWV/WWVH Receiver (WWV_HEATH)</h3>
<div class="paragraph"><p>Pre-1992 time-radio receiver, cited as worse than 100ms accuracy.
Undated web pages suggest that a few may survive in hobbyist use.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED, UNAVAILABLE, INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_20_generic_nmea_gps_receiver_nmea">Type 20: Generic NMEA GPS Receiver (NMEA)</h3>
<div class="paragraph"><p>GPSD does this better.</p></div>
<div class="paragraph"><p>Disposition: REDUNDANT; Remove</p></div>
</div>
<div class="sect2">
<h3 id="_type_21_truetime_gps_vme_interface_gps_vme">Type 21: TrueTime GPS-VME Interface (GPS_VME)</h3>
<div class="paragraph"><p>VME-bus time source for Sun workstations, long dead, documentation
removed.</p></div>
<div class="paragraph"><p>Disposition: INTRINSIC, DEPRECATED, DISCONTINUED; already removed.</p></div>
</div>
<div class="sect2">
<h3 id="_type_22_pps_clock_discipline_pps">Type 22: PPS Clock Discipline (PPS)</h3>
<div class="paragraph"><p>I had this marked for retention in the 1.0 version of this document;
it could still have been potentially useful in some very odd
situations - the documentation mentions "the vicinity of Mars".</p></div>
<div class="paragraph"><p>However, Hal Murray reports that the PPS support in ntpd is "kludgy"
and needs to be fixed. That says to me that this driver is too
broken to be worth saving.</p></div>
<div class="paragraph"><p>Disposition: INTRINSIC; Remove</p></div>
</div>
<div class="sect2">
<h3 id="_type_26_hewlett_packard_58503a_gps_receiver_gps_hp">Type 26: Hewlett Packard 58503A GPS Receiver (GPS_HP)</h3>
<div class="paragraph"><p>Support for two discontinued HP time sources, not updated since 2005.
Used units can be found on the Web. Accuracy cited as better than 1µs
when GPS-locked, drift of better than 10ms in holdover mode. Some
are available on eBay.</p></div>
<div class="paragraph"><p>I had this marked for removal in the 1.0 version of this document,
but Hal Murray - who is credible when he says such things - reports
that (a) these were heavily used in cell towers before being
discontinued, so surplus units are easy to find, and (b) they’re
widely used in the time-hacker community.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED; move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_27_arcron_msf_receiver_msf_arcron">Type 27: Arcron MSF Receiver (MSF_ARCRON)</h3>
<div class="paragraph"><p>Obsolete time source, noted in 2003 posting</p></div>
<div class="paragraph"><p><a href="http://comp.protocols.time.ntp.narkive.com/0sT20Wjc/trimble-s-acutime-2000-compared-to-arcron-msf">http://comp.protocols.time.ntp.narkive.com/0sT20Wjc/trimble-s-acutime-2000-compared-to-arcron-msf</a></p></div>
<div class="paragraph"><p>to be "not very good" and inferior to a common Trimble GPS. The
vendor is gone. Web searches do not find units for sale.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED, UNAVAILABLE, INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_28_shared_memory_driver_shm">Type 28: Shared Memory Driver (SHM)</h3>
<div class="paragraph"><p>IPC driver, to be retained.</p></div>
</div>
<div class="sect2">
<h3 id="_type_29_trimble_navigation_palisade_gps_gps_palisade">Type 29: Trimble Navigation Palisade GPS (GPS_PALISADE)</h3>
<div class="paragraph"><p>GPSD does this better.</p></div>
<div class="paragraph"><p>Disposition: REDUNDANT; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_30_motorola_ut_oncore_gps_gps_oncore">Type 30: Motorola UT Oncore GPS GPS_ONCORE)</h3>
<div class="paragraph"><p>GPSD does this better.</p></div>
<div class="paragraph"><p>Disposition: REDUNDANT; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_31_rockwell_jupiter_gps_gps_jupiter">Type 31: Rockwell Jupiter GPS (GPS_JUPITER)</h3>
<div class="paragraph"><p>GPSD does this better.</p></div>
<div class="paragraph"><p>Disposition: REDUNDANT; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_32_chrono_log_k_series_wwvb_receiver_chronolog">Type 32: Chrono-log K-series WWVB receiver (CHRONOLOG)</h3>
<div class="paragraph"><p>Discontinued WWVB receiver described as "very old" in 2010. Vendor
still exists but is now making blood-platelet counters rather than
clocks. Only 1 second accuracy. Wouldn’t work following the WWVB
modulation change, anyway.</p></div>
<div class="paragraph"><p>Disposition: INTRINSIC, DISCONTINUED, UNAVAILABLE, INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_33_dumb_clock_dumbclock">Type 33: Dumb Clock (DUMBCLOCK)</h3>
<div class="paragraph"><p>I can find no evidence that non-GPS ASCII clocks of this kind still
exist. It is not clear to me that they <strong>ever</strong> existed except as custom
hobbyist rigs! Precision 2000 times worse than a cheap serial GPS.</p></div>
<div class="paragraph"><p>Disposition: INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_34_ultralink_wwvb_receivers_ulink">Type 34: Ultralink WWVB Receivers (ULINK)</h3>
<div class="paragraph"><p>A discontinued time radio. Most recent references on the
Web are from 2008; still on sale in 2004. This posting</p></div>
<div class="paragraph"><p><a href="http://fixunix.com/ntp/337036-ultralink-325-wwvb-receiver.html">http://fixunix.com/ntp/337036-ultralink-325-wwvb-receiver.html</a></p></div>
<div class="paragraph"><p>notes that accuracy is bad compared to a GPS. Would no
longer work due to the WWVB modulation change.</p></div>
<div class="paragraph"><p>Disposition: INTRINSIC, DISCONTINUED and INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_35_conrad_parallel_port_radio_clock_pcf">Type 35: Conrad Parallel Port Radio Clock (PCF)</h3>
<div class="paragraph"><p>Obsolete port type, obsolete clock. The vendor is still in business
but this product has been discontinued. All web references I found,
except one 404, are pointers to ntpd documentation from before 2010.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED, UNAVAILABLE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_36_radio_wwv_h_audio_demodulator_decoder_wwv">Type 36: Radio WWV/H Audio Demodulator/Decoder (WWV)</h3>
<div class="paragraph"><p>Yet another really bad idea based on audio signal demodulation. Only
accurate to 1ms; a cheap GPS can do 200 times better.</p></div>
<div class="paragraph"><p>Disposition: INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_37_forum_graphic_gps_dating_station_fg">Type 37: Forum Graphic GPS Dating station (FG)</h3>
<div class="paragraph"><p>Product discontinued, vendor vanished, more than 15 years old and
had a Y2K issue then.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED, INACCURATE; Remove.</p></div>
</div>
<div class="sect2">
<h3 id="_type_38_hopf_gps_dcf77_6021_komp_for_serial_line_hopf_s">Type 38: hopf GPS/DCF77 6021/komp for Serial Line (HOPF_S)</h3>
<div class="paragraph"><p>The list of all Hopf products at</p></div>
<div class="paragraph"><p><a href="http://www.hopf.com/en/index_article_en.html">http://www.hopf.com/en/index_article_en.html</a></p></div>
<div class="paragraph"><p>does not list the Hopf 6021. Because the 6039 still shipping issued
in 2001 or earlier it is almost certain that the 6021 was discontinued
sooner yet.</p></div>
<div class="paragraph"><p>The manual for the 6039 mentions a 2ms accuracy limit for time radios
synchronized to DCF77, so the DCF77 variant is also INACCURATE.</p></div>
<div class="paragraph"><p>Disposition: DISCONTINUED; Remove</p></div>
</div>
<div class="sect2">
<h3 id="_type_39_hopf_gps_dcf77_6039_for_pci_bus_hopf_p">Type 39: hopf GPS/DCF77 6039 for PCI-Bus (HOPF_P)</h3>
<div class="paragraph"><p>Still a live product - an industrial-grade timing receiver, or what
passed for one in 2001 (date of manual). At a claimed jitter of 2ms it
is 400 times less accurate than any common 1PPS device today and half
the accuracy of a $30 USB timing GPS. However, as a clock rather than
plain GPS the DCF77 variant evades the INACCURATE tag (just barely).</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_40_jjy_receivers_jjy">Type 40: JJY Receivers (JJY)</h3>
<div class="paragraph"><p>The TriState and C-Dex devices this supports may still be live
products, though little information seems to be available in English.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_41_truetime_560_irig_b_decoder">Type 41: TrueTime 560 IRIG-B Decoder</h3>
<div class="paragraph"><p>Documentation has been removed from the ntpd4 web pages, but from web
searches and context this is another obsolete product in the
audio-decoder class from a dead vendor.</p></div>
<div class="paragraph"><p>Disposition: DEPRECATED and DISCONTINUED; already removed.</p></div>
</div>
<div class="sect2">
<h3 id="_type_42_zyfer_gpstarplus_receiver">Type 42: Zyfer GPStarplus Receiver</h3>
<div class="paragraph"><p>Live product with a supporting vendor. 100ns accuracy.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_43_ripe_ncc_interface_for_trimble_palisade">Type 43: RIPE NCC interface for Trimble Palisade</h3>
<div class="paragraph"><p>Requires custom hardware no longer being made.</p></div>
<div class="paragraph"><p>Disposition: INTRINSIC.</p></div>
</div>
<div class="sect2">
<h3 id="_type_44_neoclock4x_dcf77_tdf_serial_line">Type 44: NeoClock4X - DCF77 / TDF serial line</h3>
<div class="paragraph"><p>This is a radio clock synchronized to DCF77 and thus has 2ms jitter.
I found a source page at <a href="http://www.linux-funkuhr.de/">http://www.linux-funkuhr.de/</a> that suggests it
was written by a small software company "Linum Software GmbH" for
Linux hosts. It may still be available.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_45_spectracom_tsync_pci">Type 45: Spectracom TSync PCI</h3>
<div class="paragraph"><p>Spectracom is a product line of of time sources that is still
available and supported by a vendor. The TSync is a GPS clock
with a specified accuracy of 100ns.</p></div>
<div class="paragraph"><p>Disposition: Move to refclockd.</p></div>
</div>
<div class="sect2">
<h3 id="_type_46_gpsd_ng_client_protocol">Type 46: GPSD NG client protocol</h3>
<div class="paragraph"><p>IPC driver, to be retained.</p></div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_summary_2">Summary</h2>
<div class="sectionbody">
<div class="paragraph"><p>For hardware marked "<2000?" the date it was end-of-lifed cannot
be determined cetainly but was almost certainly in the last century.</p></div>
<table class="tableblock frame-all grid-all"
style="
width:100%;
">
<caption class="title">Table 1. Hardware status summary</caption>
<col style="width:50%;">
<col style="width:50%;">
<tbody>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">1</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DEPRECATED, INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">2</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DEPRECATED, DISCONTINUED (<2000?), UNAVAILABLE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">3</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INTRINSIC, DISCONTINUED (<2000?), UNAVAILABLE, INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">4</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">5</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2000?)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">6</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">7</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">8</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">9</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (1994), UNAVAILABLE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">10</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (1996), UNAVAILABLE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">11</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">12</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">UNDOCUMENTED, DISCONTINUED (<2000?), UNAVAILABLE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">13</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2005), INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">14</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DEPRECATED and DISCONTINUED (<2000?)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">16</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2000?)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">17</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">UNDOCUMENTED, DEPRECATED, DISCONTINUED (<2000?), UNAVAILABLE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">19</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<1992), UNAVAILABLE, INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">20</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">REDUNDANT</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">21</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INTRINSIC, DEPRECATED, DISCONTINUED (<2000?)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">26</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (2005?)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">27</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2000?), UNAVAILABLE, INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">29</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">REDUNDANT</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">30</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">REDUNDANT</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">31</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">REDUNDANT</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">32</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INTRINSIC, DISCONTINUED (<2000?), UNAVAILABLE, INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">33</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">34</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INTRINSIC, DISCONTINUED (>2004,<2015) and INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">35</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2010), UNAVAILABLE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">36</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">37</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2000), INACCURATE</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">38</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DISCONTINUED (<2001).</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">39</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">40</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">41</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">DEPRECATED, DISCONTINUED</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">42</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">43</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">INTRINSIC</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">44</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">45</p></td>
<td class="tableblock halign-left valign-top" ><p class="tableblock">-</p></td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="sect1">
<h2 id="_second_round_triage">Second-round triage</h2>
<div class="sectionbody">
<table class="tableblock frame-all grid-all"
style="
width:100%;
">
<caption class="title">Table 2. Potentially viable drivers</caption>
<col style="width:100%;">
<tbody>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 4: Spectracom WWVB/GPS Receivers (WWVB_SPEC)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 8: Generic Reference Driver (PARSE)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 11: Arbiter 1088A/B GPS Receiver (GPS_ARBITER)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 18: NIST/USNO/PTB Modem Time Services (ACTS_MODEM)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 26: Hewlett Packard 58503A GPS Receiver (GPS_HP)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 28: Shared Memory Driver (SHM)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 39: hopf GPS/DCF77 6039 for PCI-Bus (HOPF_P)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 40: JJY Receivers (JJY)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 42: Zyfer GPStarplus Receiver</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 44: NeoClock4X - DCF77 / TDF serial line</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 45: Spectracom TSync PCI</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top" ><p class="tableblock">Type 46: GPSD NG client protocol</p></td>
</tr>
</tbody>
</table>
<div class="paragraph"><p>The Type 4 driver supports recent Spectracom GPS clocks, if I can
believe their protocol documentation. But Spectracom no longer
makes WWVB receivers; this needs to be renamed "Spectracom Type 2
protocol".</p></div>
<div class="paragraph"><p>Types 28 and 46 are no-brainers to keep. We will eventually want to
deprecate the SHM driver in favor of the JSON one. That needs to be
described as a future direction in the documentation.</p></div>
<div class="paragraph"><p>Kludgy PPS support in ntpd may compromise types 4, 8, and 45. This
is an issue we need to keep an eye on.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_policy_consequences">Policy consequences</h2>
<div class="sectionbody">
<div class="paragraph"><p>The 1.0 version of this document contained a technical policy proposal
but no conclusions. It was, essentially, to remove all drivers tagged
INTRINSIC, DEPRECATED, OBSOLETE, REDUNDANT, and INACCURATE, but
allow for reinstatement of merely OBSOLETE drivers on demonstration of
a real-world use case.</p></div>
<div class="paragraph"><p>At that time the proposed obsolescence timeout was ten years. I noted
that there is only one driver for hardware that has been discontinued,
but possibly too recently - Type 35; the date it was end-of-lifed is
unclear. I have continued to designate it OBSOLETE, as its reliance
on a parallel port means it is extremely likely to have been
discontinued before 2008.</p></div>
<div class="paragraph"><p>Susan Sons, acting as program manager, changed the timeout to seven
years. She endorsed the exception that obsolete drivers may be
reinstated if and when specific users demonstrate a need for them.</p></div>
<div class="paragraph"><p>To date, there has been one such reinstatement: the Hewlett Packard
58503A (type 26), requested by Hal Murray.</p></div>
<div class="paragraph"><p>Accordingly, the list under "Potentially viable drivers" is the list
to be retained in the cleanup release of NTP. This list may be
revised as we receive new information.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_appendix_test_equipment_available">Appendix: Test equipment available</h2>
<div class="sectionbody">
<div class="paragraph"><p>Harlan Stenn reports:</p></div>
<div class="listingblock">
<div class="content monospaced">
<pre>Here at my lab I have:
- Meinberg LANtime M600
- SEL-2407
- Sure GPS
- ublox
At ISC we have:
- Meinberg GPS167BGT
- - IRIG Audio
- - Serial with no PPS
- - Serial with PPS
- - DCF77 output
- Meinberg DCF77 receiver
- Trimble Acutime 2000
I think we have a Trimble Acutime Gold as well, but no cable for it.
> |==========================================================
> |Type 4: Spectracom WWVB/GPS Receivers (WWVB_SPEC)
> |Type 11: Arbiter 1088A/B GPS Receiver (GPS_ARBITER)
Dave Mills might have these two, but I have no idea if they're up and
running and there's no good way to access them at his place. If they
are up and running I might be able to get logs for you.
> |Type 42: Zyfer GPStarplus Receiver
I had one of these back when I wrote the driver, but I haven't seen one
since. There is no maintainer for this refclock, so if a problem is
found with it I'll ping the manufacturer and either they'll fix it or
I'll deprecate the driver. I wrote this driver because Zyfer had a
customer (the NSA) who asked for it. I haven't heard a word about this</pre>
</div></div>
</div>
</div>
<div class="sect1">
<h2 id="_history">History</h2>
<div class="sectionbody">
<div class="dlist"><dl>
<dt class="hdlist1">
Version 1.0, 2015-03-03
</dt>
<dd>
<p>
Initial version.
</p>
</dd>
<dt class="hdlist1">
Version 1.1, 2015-03-06
</dt>
<dd>
<p>
Dropped type 22, reinstated type 26. Added hardware status summary.
</p>
</dd>
<dt class="hdlist1">
Version 1.2, 2015-03-10
</dt>
<dd>
<p>
Added section on policy and conclusions. ACTS is still used
for backup at government Stratum 1 sites, so keep it.
</p>
</dd>
<dt class="hdlist1">
Version 1.3, 2015-06-16
</dt>
<dd>
<p>
Minor typo fixes.
</p>
</dd>
<dt class="hdlist1">
Version 1.4, 2015-06-30
</dt>
<dd>
<p>
Add DEPRECATED tags to three refclocks because they are
undocumented. Note that driver 2 was already gone and that
13, 14, 17, 21, and 41 have already been removed.
</p>
</dd>
</dl></div>
</div>
</div>
</div>
<div id="footnotes"><hr></div>
<div id="footer">
<div id="footer-text">
Version 1.4<br>
Last updated
2015-11-10 15:58:05 EST
</div>
</div>
</body>
</html>