[Standards-JIG] stream feature for jabber:iq:auth?

David Waite mass at akuma.org
Tue Feb 17 23:43:15 UTC 2004

I think it is wasted bytes; if a client supports XMPP and understands 
stream features, it should be using SASL for authentication. Only if a 
client does not support XMPP and cannot understand stream features 
should it attempt jabber:iq:auth.

-David Waite

On Feb 17, 2004, at 4:23 PM, Peter Saint-Andre wrote:

> A while back, we added a stream feature for jabber:iq:register so that
> in-band registration can be advertised by those servers that support 
> it:
> http://www.jabber.org/jeps/jep-0077.html
> I think a stream feature for jabber:iq:auth would be helpful as well. 
> Do
> people think this is desirable? If so, I will update JEP-0078 and the
> stream features registry accordingly.
> http://www.jabber.org/jeps/jep-0078.html
> http://www.jabber.org/registrar/stream-features.html
> Thanks!
> Peter
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> https://jabberstudio.org/mailman/listinfo/standards-jig
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2357 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20040217/18268bc9/attachment.bin>

More information about the Standards mailing list