[Jabber-IETF] SASL Namespace
ben at blahr.com
Fri Oct 11 18:42:56 CDT 2002
-----BEGIN PGP SIGNED MESSAGE-----
Not to be nit-picky, but I was catching up on the mailing list here and
I must say that I like the ideas coming through for advertising feature
support. My only beef is that, aren't these features? I realize that in
other contexts (POP3 comes to mind), these extra abilities are
referenced as capabilities. However, it has been common with the Jabber
community to call these features. For that reason, I would propose that
we use the element <stream:features>, instead of of <stream:capabilities>.
The rest make sense to me, but I think this works better with regard to
| 2.sasl namespace
| note that i didn't include the namespace "thread" in the list above
| because, frankly, it's hard for me to get excited about it. however, i
| think that the robert norris/joe hildebrand approach, e.g.,
| <stream:stream xmlns='jabber:client'
| from='jabber.org' version='1.0'>
| <starttls xmlns='http://blah'/>
| shows a lot of promise.
| could i ask that folks talking about the namespace issue send a message
| to the list with this subject:
| Subject: SASL namespace
| in particular, i'd be interested in hearing people's views on what
| robert & joe are talking about, and whether there are better ways
| of doing it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the xmppwg