Re: I-D ACTION:draft-zeilenga-ldapbis-rfc2253-01.txt

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 05:02 PM 10/30/00 -0800, Kurt D. Zeilenga wrote:
>" " should not be in special as it would allow:
>  cn=\ foo\ ,dc=example,dc=com
>
>which is bogus per 2.4....

Note also that 2.4 disallows '#' from being escaped as "\#"
as it is not in the "list shown above".   That is,
"cn=\#,dc=example,dc=com" is inappropriate per RFC2253.
It should be written as "cn=\23,dc=example,dc=com".

Also, 2.4 disallow hex escaping when the value is in
the list.  I believe hex escaping should be allowed for
any character (as this is exactly what many implementations
do).

I'd like to replace the second and third to last paragraphs
of 2.4 with:

  The character to be escaped is replaced by a backslash and two hex
  digits, which form a single byte in the code of the character.
  Alternatively, if and only if the character to be escaped is one of
      ",", "+", """, "\", "<", ">", ";", "#", or "=",        
  it may be prefixed by a backslash ('\\' ASCII 92).               

Then, in 3, special should include "#".

Comments?

I rather not otherwise expand the list of specials (even in regard to " ").