RFC Errata
Found 3 records.
Status: Verified (2)
RFC 2251, "Lightweight Directory Access Protocol (v3)", December 1997
Note: This RFC has been obsoleted by RFC 4510, RFC 4511, RFC 4513, RFC 4512
Note: This RFC has been updated by RFC 3377, RFC 3771
Source of RFC: asid (app)
Errata ID: 8844
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Shreyas Rajagopal
Date Reported: 2026-03-18
Verifier Name: RFC Editor
Date Verified: 2026-03-18
Section 4.2.3 says:
f the bind was successful, the resultCode will be success, therwise it will be one of:
It should say:
If the bind was successful, the resultCode will be success, otherwise it will be one of:
Notes:
The sentence is missing an 'I' for 'If' and an 'o' for 'otherwise'.
Errata ID: 8845
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Shreyas Rajagopal
Date Reported: 2026-03-18
Verifier Name: RFC Editor
Date Verified: 2026-03-18
Section 4.11 says:
The MessageID MUST be that of a an operation which was requested earlier in this connection.
It should say:
The MessageID MUST be that of an operation which was requested earlier in this connection.
Notes:
The sentence has "a an operation" which should be "an operation".
Status: Reported (1)
RFC 2251, "Lightweight Directory Access Protocol (v3)", December 1997
Note: This RFC has been obsoleted by RFC 4510, RFC 4511, RFC 4513, RFC 4512
Note: This RFC has been updated by RFC 3377, RFC 3771
Source of RFC: asid (app)
Errata ID: 8868
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Shreyas Rajagopal
Date Reported: 2026-04-06
Section 4.5.2 says:
-- may also have zero elements (if types only was requested, or -- all values were excluded from the result.)
It should say:
-- may also have zero elements (if typesOnly was requested, or -- all values were excluded from the result.)
Notes:
The phrase "types only" appears to refer to the typesOnly field defined in Section 4.5.1. Using the field name directly improves clarity and avoids ambiguity.