[ntpsec commit] Remove some duplication and historical references.

[Eric S. Raymond]

Module:    ntpsec
Branch:    master
Commit:    a1fb8ac21837c4bbe01b273c1b1891f578db6fee
Changeset: http://git.ntpsec.org/ntpsec/commit/?id=a1fb8ac21837c4bbe01b273c1b1891f578db6fee

Author:    Eric S. Raymond <esr at thyrsus.com>
Date:      Mon Oct 12 08:51:11 2015 -0400

Remove some duplication and historical references.

---

 docs/authentic.txt | 24 +++++++++++-------------
 1 file changed, 11 insertions(+), 13 deletions(-)

diff --git a/docs/authentic.txt b/docs/authentic.txt
index eb473fe..400d483 100644
--- a/docs/authentic.txt
+++ b/docs/authentic.txt
@@ -133,15 +133,15 @@ briefings, papers and reports at the {project-fullname} page linked from
 [[symm]]
 === Symmetric-Key Cryptography ===
 
-The original RFC-1305 specification allows any one of possibly 65,534
-keys, each distinguished by a 32-bit key identifier, to authenticate an
-association. The servers and clients involved must agree on the key and
-key identifier to authenticate NTP packets. Keys and related information
-are specified in a key file, usually called _{ntpkeys}_, which must be
-distributed and stored using secure means beyond the scope of the NTP
-protocol itself. Besides the keys used for ordinary NTP associations,
-additional keys can be used as passwords for the {ntpqman}
-utility program.
+NTP allows any one of possibly 65,534 keys, each distinguished by a
+32-bit key identifier, to authenticate an association. The servers and
+clients involved must agree on the key and key identifier to
+authenticate NTP packets. Keys and related information are specified
+in a key file, usually called _{ntpkeys}_, which must be distributed
+and stored using secure means beyond the scope of the NTP protocol
+itself. Besides the keys used for ordinary NTP associations,
+additional keys can be used as passwords for the {ntpqman} utility
+program.
 
 When {ntpdman} is first started, it reads the key file specified
 in the keys configuration command and installs the keys in the key cache.
@@ -154,8 +154,7 @@ selects the key used as the password for the {ntpqman} utility.
 
 //=== Public Key Cryptography ===
 //
-//NTPv4 supports the original NTPv3 symmetric key scheme described in
-//RFC-1305 and in addition the Autokey protocol, which is based on public
+//NTPv4 supports the Autokey protocol, which is based on public
 //key cryptography. The Autokey Version 2 protocol described on the
 //Autokey Protocol page verifies packet integrity using MD5 message
 //digests and verifies the source with digital signatures and any of
@@ -379,8 +378,7 @@ access to all but correctly authenticated clients..
 [[formats]]
 == Data Formats ==
 
-The original NTPv3 specification (RFC-1305), as well as the current
-NTPv4 specification (RFC-5905), allows any one of possibly 65,534
+The NTPv4 specification (RFC-5905) allows any one of possibly 65,534
 message digest keys (excluding zero), each distinguished by a 32-bit key
 ID, to authenticate an association. The servers and clients involved
 must agree on the key ID, key type and key to authenticate NTP packets.