[jdev] JEP-0106 - Jid Escaping

[Peter Saint-Andre]

On Thu, Apr 28, 2005 at 03:51:23PM -0300, Hernan Tylim wrote:

> Peter Saint-Andre wrote:
> [...]
> >>But what 
> >>if we need to escape a character that is not allowed by STRINGPREP ?
> >
> >What character? The stringprep profiles used by XMPP are pretty liberal
> >in the characters they allow.
> 
> 
> Well, I don?t really know. I didn?t read carefully the STRINGPREP rfc so 
> I just assumed that it might exist some character allowed on some IM 
> network which might not be allowed by STRINGPREP.

OK. A full list might be good so that we can investigate the issue. Is
the Sametime protocol documented anywhere?

> >>and given that Sametime usernames are case sensitive I needed to 
> >>escape also all uppercase letters. 
> >
> >Ick. 

I still don't know what to do about that. See below.

> And thats not all. For example my sametime server reports my username as 
>  "CN=Hern?n Tylim/O=Novamens". Imagine now how it looks when escaped...

So let's say your gateway is sametime.example.com, it seems to me that
you would encode the foregoing address something like this (using the 
backslash format we seem to have agreed upon on the Standards-JIG list):

CN=Hernan\20Tylim\2fO=Novamens at sametime.example.com

It's not pretty, but it would work.

(Note: my email client does not support anything but US-ASCII as
currently configured, so the first instance of "a" in that address
should actually be U+00E1, also known as LATIN SMALL LETTER A WITH
ACUTE.)

It is unfortunate that Sametime addresses are case-sensitive for
US-ASCII characters. I find that confusing, since the foregoing Sametime
address seems to be a combination of LDAP attributes, yet according to
RFCs 2251 and 2252 LDAP attributes are case-insensitive.

Are you sure that Sametime addresses are case-sensitive for US-ASCII
characters?

Peter