[Members] RE: MOTION: JEP-0106 (JID Escaping)

Jean-Louis Seguineau/EXC/ENG jean-louis.seguineau at antepo.com
Sun Mar 28 14:38:06 CST 2004


IMHO, the example given illustrates perfectly that the issue is not with JID
escaping, but rather with the  address translation between XMPP and any
other communication/IM namespace.
We have a logic associated with converting the MSN namespace to the XMPP
namespace, and the legacy solution has been to include the MSN address as
the node in the gateway addressing. If we come up with another mapping
between the two namespace that does not contain a logic in the node, then
the escaping of @ should not be necessary. Unless I am missing something...

Jean-Louis

------------------------------

Message: 3
Date: Fri, 26 Mar 2004 15:47:09 +0100
From: Jacek Konieczny <jajcus at bnet.pl>
Subject: Re: RE : [Members] MOTION: JEP-0106 (JID Escaping)
To: JSF members discussion list <members at jabber.org>
Message-ID: <20040326144708.GD31850 at serwis2.beta>
Content-Type: text/plain; charset=us-ascii

On Fri, Mar 26, 2004 at 10:15:56AM -0000, Richard Dobson wrote:
> Now I hope you can see that things would not get double escaped, as we
only
> need reuse the aspects that are useful to use (again just like we did with
> SOCKS5).

JID is not an URI, but will often be used in URI, e.g:
im:jajcus at jabber.bnet.pl

So, "example at example.com" in MSN network accessed via a transport
gateway would have JID e.g.: example%40example.com at msn.jabber.example.com
Which written as na URI would be:
	im:example%2540example.com at msn.jabber.example.com
This could be misleading. But you are right. This can be done and can be
usable if implemented properly.

Greets,
	Jacek






More information about the Members mailing list