Re: [jdev] Re: Recent Google Talk S2S Problems

[Robert B Quattlebaum, Jr.]

On Mar 9, 2006, at 5:02 AM, Ralph Meijer wrote:

On Thu, Mar 09, 2006 at 07:29:51AM +0100, Remko Troncon wrote:

   My friend who is using trillian says that the trillian log is

   seem to work too well either...

complaining that <cli:message ...> isn't a valid top level stanza and drops it. Looks like a namespace issue of some sorts? Pandion doesn't

allowed. I never seen a client send them, but Google does, and most

As far as i know, namespaced XML elements like the one google sends are off the shelf XML parsers used in clients seem to be able to handle it.

The point is that using prefixes for elements in the jabber:client
namespace is specifically not allowed. This is clearly defined in
section 11.2.2 of RFC 3920 (XMPP Core).

If Google's implementation sends <cli:message/> where cli is a prefix
for the jabber:client namespace, this is simply not compliant. Other
implementations cannot be blamed for rejecting it.

__________________
Robert Quattlebaum
Mobile: +1(650) 223-4974
eMail:  [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED]

Are the Google Talk engineers monitoring this forum? This seems like a rather significant issue that requires attention ASAP.

smime.p7s
Description: S/MIME cryptographic signature