RFC Errata
Found 8 records.
Status: Verified (7)
RFC 4511, "Lightweight Directory Access Protocol (LDAP): The Protocol", June 2006
Source of RFC: ldapbis (app)
Errata ID: 7216
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-10-31
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section 4.1.6 says:
the value syntax. See objectIdentiferFirstComponentMatch in
It should say:
the value syntax. See objectIdentifierFirstComponentMatch in
Notes:
Typo.
Errata ID: 7217
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-01
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section 4.1.11 says:
- direction as to what value the sender should provide for the
criticality field (note: the semantics of the criticality field are
defined above should not be altered by the control's
specification),
It should say:
- direction as to what value the sender should provide for the
criticality field (note: the semantics of the criticality field
defined above should not be altered by the control's
specification),
Notes:
Erroneous "are".
Errata ID: 7218
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-01
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section 4.4 says:
choice using the ExtendedResponse type (See Section 4.12). The
It should say:
choice using the ExtendedResponse type (see Section 4.12). The
Notes:
The word "see" should not be capitalized here.
Errata ID: 7219
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-01
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section 4.4 says:
- the OBJECT IDENTIFIER assigned to the notification (to be specified
in the responseName,
It should say:
- the OBJECT IDENTIFIER assigned to the notification (to be specified
in the responseName),
Notes:
Missing parenthesis.
Errata ID: 7220
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-01
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section 8 says:
[RFC4512] Zeilenga, K., Lightweight Directory Access Protocol
(LDAP): Directory Information Models", RFC 4512, June
2006.
It should say:
[RFC4512] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Directory Information Models", RFC 4512, June
2006.
Notes:
Missing quotation mark.
Errata ID: 7221
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-01
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section A.2 says:
the code may used to indicate an alias has been dereferenced
that names no object.
It should say:
the code may be used to indicate an alias has been
dereferenced that names no object.
Notes:
Missing "be".
Errata ID: 7222
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-01
Verifier Name: RFC Editor
Date Verified: 2022-11-01
Section C.1.17 says:
- The SubstringFilter substrings 'initial, 'any', and 'final' types
are now AssertionValue rather than LDAPString. Also, added
It should say:
- The SubstringFilter substrings 'initial', 'any', and 'final'
types are now AssertionValue rather than LDAPString. Also, added
Notes:
Missing quotation mark.
Status: Reported (1)
RFC 4511, "Lightweight Directory Access Protocol (LDAP): The Protocol", June 2006
Source of RFC: ldapbis (app)
Errata ID: 5292
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Markus Ansmann
Date Reported: 2018-03-21
Section 4.5.1/Appx.B says:
Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF filter Filter,
or [1] SET SIZE (1..MAX) OF filter Filter,
not [2] Filter,
It should say:
Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF filter Filter,
or [1] SET SIZE (1..MAX) OF filter Filter,
not [2] EXPLICIT Filter,
Notes:
As currently written, the specification requires IMPLICIT tagging for the not-filter. This, according to ITU-T X.690, Section 8.14.3, Example "Type5", requires the [2]-tag of the not-filter to overwrite the tag of the negated filter, making reliable identification of the type of the negated filter impossible. Thus, the definition of the not-filter needs to specify EXPLICIT tagging. Alternatively, the filter could be specified as
not [2] SEQUENCE { filter Filter },
or (to match the definition of "and" and "or")
not [2] SET SIZE (1..1) OF filter Filter,
This applies to both, Section 4.5.1 and Appendix B.