[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
>>>    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
>>>    seem to work too well either...
>>
>> As far as i know, namespaced XML elements like the one google  
>> sends are
>> allowed. I never seen a client send them, but Google does, and most
>> 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.
>

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


__________________
Robert Quattlebaum
Mobile: +1(650) 223-4974
eMail:  darco at deepdarc.com
Jabber: darco at deepdarc.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2149 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20060309/451471a6/attachment-0002.bin>