On Mon, 18 Mar 2024 at 14:19, Stephen Paul Weber <[email protected]> wrote:
> >1. Is this specification needed to fill gaps in the XMPP protocol > >stack or to clarify an existing protocol? > > Yes, we currently have no way to use multiple SASL or otherwise to acheive > a > similar result. > > >2. Does the specification solve the problem stated in the introduction > >and requirements? > > Yes. However it does lack any way to support indicating to the server > which > credential will be used, other than perhaps by implication from the SASL > mechanism. > > That's not the purview of a SASL profile. If a SASL mechanism supports multiple credentials, that's entirely encapsulated within that mechanism. > >3. Do you plan to implement this specification in your code? If not, > >why not? > > Yes, I have implemented this for xmpp.js -- except for "tasks" which I > have > not implemented and I think there are no official profiles of, making that > a > somewhat more risky area of the spec. > There's XEP-0400, actually, which defines two tasks. > > >4. Do you have any security concerns related to this specification? > > No, only usability concerns outlined above > > >5. Is the specification accurate and clearly written? > > Yes > _______________________________________________ > Standards mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
