The set of characters needing escapement in 2.4 seems to be truncated. It now reads:
- one of the characters ",", "+", """, "
I believe it should still read
- one of the characters ",", "+", """, "\", "<", ">", or ";"
also, a few lines later "...by a backslash ('' ASCII 92)." is missing the backslash.
The BNF in section 3 has changed and needs a bit of fixing up:
Fix "ESC = <the ASCII backslash character ""
Fix "stringchar = <any character except one of special,"
Due to what looks like a malfunction of your editor, you may want to do a diff against the original in case I've missed some truncated lines.
If it ends up that the "Relationship with RFC 1779 and LDAPv2" section is to be re-added, I have some issues with the characters and such. My vote is to just leave it out.
>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/24/00 10:14:00 AM >>>
I draw your attention to the following I-D:
LDAPv3: UTF-8 String Representation of Distinguished Names
This I-D proposes a technical specification to replace
RFC 2253. I request you review this I-D as a strawman
proposal to fulfill LDAPbis proposed work item. As I
edited this I-D and to avoid any conflict of interest,
I yield chair responsibility to evaluate consensus in
regards to this proposal to Bob.
Summary of the proposed changes to RFC 2253:
- Remove IESG Note
- Remove all LDAPv2 dependencies
- Remove Relationship with RFC 1779 and LDAPv2 Section
- Rewrite DN grammar using ABNF [RFC2234]
- Rewrite examples
The most significant change is the removal of "Relationship
with RFC 1779 and LDAPv2" section as technical specification
only details the DN format used in LDAPv3. The format used
in LDAPv2 is detailed in RFC 1779. It may be appropriate to
re-add this section as a non-normative appendix.
Please note that there is no change in the specification
in respect to its use in LDAPv3.