On Dienstag, 8. Januar 2019 17:54:22 CET Jonas Schäfer wrote: > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol?
Yes, sadly. The introduction covers this quite nicely. > 2. Does the specification solve the problem stated in the introduction > and requirements? Yes. > 3. Do you plan to implement this specification in your code? If not, > why not? Yes. > 4. Do you have any security concerns related to this specification? No. > 5. Is the specification accurate and clearly written? Yes. It needs to remove/fill the placeholder sections though. IMO, this is close to an Informational track document by the way, because it doesn’t really define wire protocol. Instead, it describes the use of an existing protocol for a specific use case. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
