[Jabber-IETF] SASL Namespace

Peter Saint-Andre stpeter at jabber.org
Mon Oct 14 14:34:21 CDT 2002


Agreed. I'd prefer <stream:features>. That seems to dovetail well with the
ideas expressed in JEPs like feature negotiation (JEP-0020) and service
discovery (JEP-0030, new version to be released soon).

Peter

--
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.php

On Fri, 11 Oct 2002, Ben Schumacher wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> All-
> 
> 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
> XMPP.
> 
> Cheers,
> 
> bs.
> 
> | 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'
> |                    xmlns:stream='http://etherx.jabber.org/streams'
> |                    from='jabber.org' version='1.0'>
> |      <stream:capabilities>
> |        <mechanisms
> xmlns='http://www.iana.org/assignments/sasl-mechanisms'>
> |          <mechanism>DIGEST-MD5</mechanism>
> |          <mechanism>PLAIN</mechanism>
> |        </mechanisms>
> |        <starttls xmlns='http://blah'/>
> |      </stream:capabilities>
> |    </stream:stream>
> |
> | 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
> 
> iD8DBQE9p2H+UpoGqensAXIRAtLSAJ9Clp6EyK1vHHguSAShhvbDrPm5ZgCfSK4U
> rhUCzx+NciubkWX4zGpUAsY=
> =WAFV
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Jabber-IETF mailing list
> Jabber-IETF at jabber.org
> http://jabber.org/cgi-bin/mailman/listinfo/jabber-ietf
> 




More information about the xmppwg mailing list