RFC Errata
Found 2 records.
Status: Verified (1)
RFC 4120, "The Kerberos Network Authentication Service (V5)", July 2005
Note: This RFC has been updated by RFC 4537, RFC 5021, RFC 5896, RFC 6111, RFC 6112, RFC 6113, RFC 6649, RFC 6806, RFC 7751, RFC 8062, RFC 8129, RFC 8429, RFC 8553
Source of RFC: krb-wg (sec)
Errata ID: 7022
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Gabriel Potter
Date Reported: 2022-07-13
Verifier Name: RFC Editor
Date Verified: 2022-07-26
Section 5.2.6.2 says:
checksumtype
It should say:
cksumtype
Notes:
The field is named "cksumtype" according to section 5.2
--VERIFIER NOTES--
Correction - The field is named in section 5.2.9.
Status: Held for Document Update (1)
RFC 4120, "The Kerberos Network Authentication Service (V5)", July 2005
Note: This RFC has been updated by RFC 4537, RFC 5021, RFC 5896, RFC 6111, RFC 6112, RFC 6113, RFC 6649, RFC 6806, RFC 7751, RFC 8062, RFC 8129, RFC 8429, RFC 8553
Source of RFC: krb-wg (sec)
Errata ID: 4399
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Thomas Maslen
Date Reported: 2015-06-24
Held for Document Update by: Paul Wouters
Date Held: 2024-01-16
Section 6.1 says:
All prefixes expect those beginning with used.
It should say:
??
Notes:
Hmmm, looks like part of the sentence ended up in /dev/null. (Also, was "expect" perhaps meant to be "except"?) It looks to me as though this happened between kerberos-clarifications-04 and -05. If I had to guess, it was probably trying to say that you can roll your own private-use prefixes (beginning with "X-" or "x-"), but any other prefixes must go through the official registry process, per RFC 6111?
Paul Wouters (AD): the -04 draft said: All prefixes must be assigned before they may be used. The -05 version is as in the RFC. It seems indeed that an exception was contemplated for specific prefixes starting with x- or X-. This can be read in The IANA Considerations section.