On Mon, 18 Mar 2024 at 09:00, Daniel Gultsch <[email protected]> wrote:
> This message constitutes notice of a Last Call for comments on > XEP-0388. > > Title: Extensible SASL Profile > Abstract: > This document describes a replacement for the SASL profile documented > in RFC 6120 which allows for greater extensibility. > > URL: https://xmpp.org/extensions/xep-0388.html > > This Last Call begins today and shall end at the close of business on > 2024-04-01. > > Please consider the following questions during this Last Call and send > your feedback to the [email protected] discussion list: > > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? > > Well, I think so, yes. > 2. Does the specification solve the problem stated in the introduction > and requirements? > > Again, I believe so. > 3. Do you plan to implement this specification in your code? If not, > why not? > > I implemented this some time ago in order to get TOTP working in Openfire - I never merged the code into the main branch, but it is available. > 4. Do you have any security concerns related to this specification? > > Not that aren't already specified. > 5. Is the specification accurate and clearly written? > > I can't really judge this; but after implementing it I did do a sweep over it in order to tidy it up. I have noticed that Example 8 no longer has the additional data Base64 encoded, which is wrong, so this needs fixing prior to advancing it. It also spoils the joke. > Your feedback is appreciated! > _______________________________________________ > 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]
