> 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? >
Yes > 2. Does the specification solve the problem stated in the introduction > and requirements? > It solves the problem described and introduces a new problem. Migration to this standard is not possible without data loss. It removed the <password> element without any explanation. Clients who migrate to this standard have no standard way to sync passwords across devices. I'm not sure what the thought process was here, the password of the MUC is known to the server anyway, it does not matter if its stored in a second place on the same server. 3. Do you plan to implement this specification in your code? If not, > why not? > I have implemented behind a development flag, but im not sure i want to really migrate to this standard for reasons described above > 4. Do you have any security concerns related to this specification? > No > 5. Is the specification accurate and clearly written? > Yes > Your feedback is appreciated! > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
