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

["Ramsay, Ron" <Ron.Ramsay@ca.com>]

'pair' no longer makes any sense. What about 'escape' or 'escape-seq'?

Ron.

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, 31 October 2000 13:54
To: Jim Sermersheim
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: I-D ACTION:draft-zeilenga-ldapbis-rfc2253-01.txt


At 07:06 PM 10/30/00 -0700, Jim Sermersheim wrote:
>>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 " "?

"#" was in special, " " wasn't (hence my reading of 2.4).
I don't have objection to adding it, as like you say, 2.4
can be viewed as having " " in "the list".

>>Then, in 3, special should include "#".
> 
>This forces people to escape "#" inside the string.

Good catch.  The treatment of " ", "#" and "=" need to be per 2.4.
Something like:

      string            = *( stringchar | pair )

      special           = "#" / "=" / " " / escaped

      escaped           = "," / "+" / """ / "<" /  ">" / ";" /

      pair              = ESC ( ESC / special / hexpair )
      stringchar        = <any character except one of escaped or ESC>


Kurt