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

Richard Dobson richard at dobson-i.net
Mon Mar 29 04:34:05 CST 2004

Something along the lines of msn:user at hotmail.com would be cool if we could
do it but it would require server support to direct the messages correctly
to the correct transport server, also this sort of change would need to be
done by the XMPP workgroup as this would seem to be a core routing issue and
im not really sure if there would be much support for this sort of thing,
somehow I doubt it.

Also I havent really seen any news lately indicating that microsoft are
planning to SIP enable the public .NET Messenger Service, the only news
about SIP and microsoft is that certain versions of MSN and Windows
messenger are SIP enabled so they can connect to corporate LAN's IM server
(powered by microsoft's SIP Live communication server). With the current
tend in the way the public .NET messenger service is going (locking it down
with challenges and licensing agreements for people that want to connect to
it) I doubt microsoft are currently putting much effort into allowing S2S
type operations.


----- Original Message ----- 
From: "Jean-Louis Seguineau/EXC/ENG" <jean-louis.seguineau at antepo.com>
To: <members at jabber.org>
Sent: Sunday, March 28, 2004 9:38 PM
Subject: [Members] RE: MOTION: JEP-0106 (JID Escaping)

> IMHO, the example given illustrates perfectly that the issue is not with
> 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
> 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
> > 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
> _______________________________________________
> Members mailing list
> Members at jabber.org
> https://jabberstudio.org/mailman/listinfo/members

More information about the Members mailing list