There are some inconsistencies between the two ways the string is represented in 2.4 and 3.
2.4 talks about escaping a space character at the beginning or the end of the string. It doesn't say whether multiple spaces each need to be escaped.
3 includes "#" as a special char but not " ". The only time "#" needs to be escaped is when it appears at the beginning of the string. Likewise, the space char should be accounted for. I suggest these changes:
string = [ ESC "#" ] [ *( ESC SPACE ) ] *( stringchar | pair ) [ *( ESC SPACE ) ]
special = "," / "=" / "+" / "<" / ">" / ";"
SPACE = <the ASCII space character " ">
; decimal 32
Adjust if only the first or last of multiple leading or following spaces needs to be escaped.
>>> <Internet-Drafts@ietf.org> 10/26/00 4:46:52 AM >>>
A New Internet-Draft is available from the on-line Internet-Drafts directories.
Title : Lightweight Directory Access Protocol (v3bis): UTF-8
String Representation of Distinguished Names
Author(s) : K. Zeilenga
Filename : draft-zeilenga-ldapbis-rfc2253-01.txt
Pages : 9
Date : 25-Oct-00
The X.500 Directory uses distinguished names as the primary keys to
entries in the directory. Distinguished Names are encoded in ASN.1 in
the X.500 Directory protocols. In the Lightweight Directory Access
Protocol, a string representation of distinguished names is
transferred. This specification defines the string format for
representing names, which is designed to give a clean representation
of commonly used distinguished names, while being able to represent
any distinguished name.
A URL for this Internet-Draft is:
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
A list of Internet-Drafts directories can be found in
Internet-Drafts can also be obtained by e-mail.
Send a message to:
In the body type:
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the