Found 2 records.

Status: Verified (2)

RFC 4517, "Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules", June 2006

Errata ID: 4653
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Emmanuel Lecharny
Date Reported: 2016-03-31
Verifier Name: Barry Leiba
Date Verified: 2016-03-31

Section 4.2 says:

4.2.  Matching Rule Definitions

   Nominated character strings in assertion and attribute values are
   prepared according to the string preparation algorithms [RFC4518] for
   LDAP when evaluating the following matching rules:

      numericStringMatch,
      numericStringSubstringsMatch,
      caseExactMatch,
      caseExactOrderingMatch,
      caseExactSubstringsMatch,
      caseExactIA5Match,
      caseIgnoreIA5Match,
      caseIgnoreIA5SubstringsMatch,
      caseIgnoreListMatch,
      caseIgnoreListSubstringsMatch,
      caseIgnoreMatch,
      caseIgnoreOrderingMatch,
      caseIgnoreSubstringsMatch,
      directoryStringFirstComponentMatch,
      telephoneNumberMatch,
      telephoneNumberSubstringsMatch and
      wordMatch.

It should say:

4.2.  Matching Rule Definitions

   Nominated character strings in assertion and attribute values are
   prepared according to the string preparation algorithms [RFC4518] for
   LDAP when evaluating the following matching rules:

      numericStringMatch,
      numericStringOrderingMatch,
      numericStringSubstringsMatch,
      caseExactMatch,
      caseExactOrderingMatch,
      caseExactSubstringsMatch,
      caseExactIA5Match,
      caseIgnoreIA5Match,
      caseIgnoreIA5SubstringsMatch,
      caseIgnoreListMatch,
      caseIgnoreListSubstringsMatch,
      caseIgnoreMatch,
      caseIgnoreOrderingMatch,
      caseIgnoreSubstringsMatch,
      directoryStringFirstComponentMatch,
      telephoneNumberMatch,
      telephoneNumberSubstringsMatch and
      wordMatch.

Notes:

The 'numericStringOrderingMatch' matching rule should be in the list of Matching Rules that are prepared accordingly to RFC 4518.

In 4.2.23, a reference to the String Preparation algorithm is made :

"In preparing the attribute value and assertion value for comparison,
characters are not case folded in the Map preparation step, and only
numericString Insignificant Character Handling is applied in the
Insignificant Character Handling step."

Errata ID: 7917
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Jesse Coretta
Date Reported: 2024-04-30
Verifier Name: Orie Steele
Date Verified: 2024-05-01

Section 3.3.10 says:

      subset        = "baseobject" / "oneLevel" / "wholeSubtree"

It should say:

      subset        = "baseObject" / "oneLevel" / "wholeSubtree"

Notes:

The Enhanced Guide "subset" token SHOULD honor the case folding scheme for a search scope, as this refers to actual ASN.1 ENUMERATED / INTEGER components; see RFC 4511 Section 4.5.1 and ITU-T Rec. X.511 Clause 11.2.1 respectively.

Therefore, "baseobject" SHOULD be "baseObject".

Additionally, outreach to author failed due to unknown recipient at specified address/domain.

Report New Errata