On 8 February 2017 at 23:07, XMPP Extensions Editor <[email protected]> wrote: > 1. Is this specification needed to fill gaps in the XMPP protocol stack or to > clarify an existing protocol?
Yes. A number of private extensions have been filling this gap. > 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, ultimately. > 4. Do you have any security concerns related to this specification? No. > 5. Is the specification accurate and clearly written? Not in parts. Beyond the typo in Example 4 (baCLony), there is constant use of some made-up word with no reference as to what it might mean. Dave. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
