|
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 10/30/00
6:45:29 PM >>>
>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". Again, does "list shown above" apply to the list of characters in the third
bullet item, or the bullet item list itself?
>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). This would be nice.
>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). Why is "#" treated differently from " "?
>Then, in 3, special should include "#". This forces people to escape "#" inside the string. This is legal today per
2.4 and will cause problems with existing
servers.
Jim |