[Jabber-IETF] Agenda items
rob at cataclysm.cx
Wed Oct 9 19:42:49 CDT 2002
> I assert that existing implementations will return an error to the user
> if they send a sasl:mechanism request - maybe we should send a request
> always, rather than expecting our definition of the sasl namespace
> indicates a request? e.g.
> <stream:stream to='example.com' xmlns='jabber:client'
> if a server does not understand SASL authentication, it would respond with
> <saslish:mechanisms type='error'
> <error code='406'>Not Acceptable</error></saslish:mechanisms>
Is that documented though? I think thats just a byproduct of the
relatively poor checking that jabberd currently does (which most other
FWIW, at the moment, the upcoming jabberd 2.0 just drops unknown XML
fragments (as per xmpp-core 7.3, "Nodes and services ... SHOULD ignore
any non-conformant elements or attributes on the incoming XML stream").
This makes sense to me - if I'm a server, and you send me something I
don't recognise, then I don't know the correct way to flag an error.
Robert Norris GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://jabber.org/pipermail/xmppwg/attachments/20021010/f19a0135/attachment.pgp
More information about the xmppwg