RFC Errata
Found 3 records.
Status: Verified (3)
RFC 4876, "A Configuration Profile Schema for Lightweight Directory Access Protocol (LDAP)-Based Agents", May 2007
Source of RFC: INDEPENDENT
Errata ID: 989
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-05-27
Verifier Name: Nevil Brownlee
Date Verified: 2010-04-15
Appendix A says:
Example 4: | serviceSearchDescriptor: email:ou=\\mar\\\\keting,\\"?base attributeMap: email:cn=name | base: ou=\\mar\\keting," scope: base filter (&(objectclass=inetOrgPerson)(name~=Jane Hernandez))
It should say:
serviceSearchDescriptor: email:ou=\\mar\\\\keting\",?base attributeMap: email:cn=name base: ou=\mar\\keting",o=airius.com scope: base filter (&(objectclass=inetOrgPerson)(name~=Jane Hernandez))
Notes:
Issues:
- unescaping of `\\mar` should give `\mar` , not `\\mar`
- to obtain `ing,"` , the escaped version should be `ing,\"'
(This presentation is biased to attribute one error each to the
two tagged lines - you might have intended another version.)
Discussed this with author, corrected version as above, with comment
"I have moved the quote to before the comma (since that is more of a
constructive example) and properly escaped it, as well as properly
processed the first escaped backslash."
Errata ID: 990
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-05-27
Verifier Name: Nevil Brownlee
Date Verified: 2010-04-07
Appendix A says:
Example 6: serviceSearchDescriptor: email:??(&(objectclass=person) | (ou=Org1 \\\\(temporary\\\\))) base: o=airius.com scope: sub | filter: (&((&(objectclass=person)(ou=Org1 \\(Temporary\\))) (cn~=Jane Henderson)))
It should say:
Example 6: serviceSearchDescriptor: email:??(&(objectclass=person) | (ou=Org1 \\\\(temporary\\\\))) base: o=airius.com scope: sub | filter: (&((&(objectclass=person)(ou=Org1 \\(temporary\\))) (cn~=Jane Henderson)))
Notes:
There's a spelling mismatch in capitalization:
'temporary' <--> 'Temporary'
from pending
Errata ID: 988
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-05-27
Verifier Name: RFC Editor
Date Verified: 2007-11-02
(1) Section 3.1 -- word omission in DESC On page 9, the RFC says: ( 1.3.6.1.4.1.11.1.3.1.1.15 NAME 'serviceAuthenticationMethod' | DESC 'Specifies types authentication methods either used, required, or supported by a particular service' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) It should say: ( 1.3.6.1.4.1.11.1.3.1.1.15 NAME 'serviceAuthenticationMethod' | DESC 'Specifies types of authentication methods either used, required, or supported by a particular service' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) (2) Section 4.6 -- typo/grammar On page 19, just above the headline 'Example:', the RFC says: | The authors' belief that the user community is more familiar with the search filter syntax described by RFC 4515 than with that described by the enhancedSearchGuide syntax. It should say either: | The authors' belief is that the user community is more familiar with the search filter syntax described by RFC 4515 than with that described by the enhancedSearchGuide syntax. or, even simpler: | The authors believe that the user community is more familiar with the search filter syntax described by RFC 4515 than with that described by the enhancedSearchGuide syntax. (3) Section 4.13 -- missing articles On page 26, the RFC says: Example: Suppose a DUA is acting on behalf of an email service. By default the "email" service uses the "mail", "cn", and "sn" attributes to | discover mail addresses in entries created using inetOrgPerson object class [RFC2789]. However, the email service has been | deployed in an environment that uses entries created using "employee" object class. [...] It should perhaps better say: Suppose a DUA is acting on behalf of an email service. By default the "email" service uses the "mail", "cn", and "sn" attributes to | discover mail addresses in entries created using the inetOrgPerson object class [RFC2789]. However, the email service has been | deployed in an environment that uses entries created using the "employee" object class. [...]
It should say:
[see above]
Notes:
from pending