On 26 Oct 2017, at 09:58, Jonas Wielicki <[email protected]> wrote: > > On Montag, 16. Oktober 2017 18:38:45 CEST Jonas Wielicki wrote: >> This message constitutes notice of a Last Call for comments on >> XEP-0313. >> >> Abstract: >> This document defines a protocol to query and control an archive of >> messages stored on a server. >> >> This Last Call begins today and shall end at the close of business on >> 2017-10-30. >> >> 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? > > Yes.
Yes. > >> 2. Does the specification solve the problem stated in the introduction >> and requirements? > > Yes. Yes > >> 3. Do you plan to implement this specification in your code? If not, >> why not? > > Yes. Yes (done, in multiple codebases). > >> 4. Do you have any security concerns related to this specification? > > Not beyond those stated in the XEP. No. >> 5. Is the specification accurate and clearly written? > > I am not happy with the archiving rules as they are. I think we should be > having the discussion Georg has started about Message Routing before > advancing > MAM, or at the very least think about it enough to be confident that we can > adapt the MAM rules without too much hassle after advancement. I think this is right. I suggest that instead of advancing 313, we instead try to solve the big questions here first. There’s nothing in our process stopping us deprecating 136 first while we’re still working at this. /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
