RFC Errata
Found 2 records.
Status: Verified (1)
RFC 5090, "RADIUS Extension for Digest Authentication", February 2008
Source of RFC: radext (sec)
Errata ID: 5115
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Denis Ovsienko
Date Reported: 2017-09-14
Verifier Name: Benoit Claise
Date Verified: 2017-09-15
Section 3 says:
3.17. Digest-Domain Attribute [...] Length 3 [...] 3.18. Digest-Stale Attribute [...] Length 3
It should say:
3.17. Digest-Domain Attribute [...] Length >= 3 [...] 3.18. Digest-Stale Attribute [...] Length >= 3
Notes:
Those two attributes contain string values. All other such attributes in Section 3 uniformly define Length >= 3.
Status: Held for Document Update (1)
RFC 5090, "RADIUS Extension for Digest Authentication", February 2008
Source of RFC: radext (sec)
Errata ID: 1326
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-02-17
Held for Document Update by: Dan Romascanu
Throughout the document, when it says:
a) header b) headers c) Header
It should say:
a) header field b) header fields c) Header Field
Notes:
As a Standards Track document, RFC 5090 should use established
IETF standard terminology, and not fall back to common sluggish
and confusing terminology. Concise Ref.: RFC 4249, Section 3.1.1.
There are 24 instances of case a) throughout the RFC;
only Section 3.20 makes proper use of the IETF standard
terminology; case b) occurs twice in the RFC;
case c) applies to the title of Section 2.1.3.