Re: LAST CALL: XEP-0424 (Message Retraction)

JC Brand <[email protected]> Wed, 8 Jul 2026 11:28:51 +0200
Newsgroups	gmane.network.jabber.standards-jig
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============5257751053660165963==
Content-Type: multipart/alternative;
 boundary="------------VaRBVcpia40ABhpyYfZWWg50"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------VaRBVcpia40ABhpyYfZWWg50
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 7/3/26 14:15, Daniel Gultsch wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0424.
>
> Title: Message Retraction
> Abstract:
> This specification defines a method for indicating that a message
> should be retracted.
>
> URL:https://xmpp.org/extensions/xep-0424.html
>
> This Last Call begins today and shall end at the close of business on
> 2026-07-20.
>
> Please consider the following questions during this Last Call and send
> your feedback to [email protected] discussion list:

Disclosure, I'm one of the authors of the XEP.


> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?

Yes. Even if retractions cannot be guaranteed in an open, federated 
network, they do still indicate intent.

And in closed deployments they can be fully implemented and enforced.

> 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?

I've implemented it in Converse.

> 4. Do you have any security concerns related to this specification?
Nothing beyond what's documented already.
> 5. Is the specification accurate and clearly written?
Yes.
--------------VaRBVcpia40ABhpyYfZWWg50
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 7/3/26 14:15, Daniel Gultsch wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre wrap="" class="moz-quote-pre">This message constitutes notice of a Last Call for comments on
XEP-0424.

Title: Message Retraction
Abstract:
This specification defines a method for indicating that a message
should be retracted.

URL: <a class="moz-txt-link-freetext" href="https://xmpp.org/extensions/xep-0424.html">https://xmpp.org/extensions/xep-0424.html</a>

This Last Call begins today and shall end at the close of business on
2026-07-20.

Please consider the following questions during this Last Call and send
your feedback to the <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> discussion list:</pre>
    </blockquote>
    <p>Disclosure, I'm one of the authors of the XEP.</p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre wrap="" class="moz-quote-pre">1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?</pre>
    </blockquote>
    <p>Yes. Even if retractions cannot be guaranteed in an open,
      federated network, they do still indicate intent.</p>
    <p>And in closed deployments they can be fully implemented and
      enforced.</p>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre wrap="" class="moz-quote-pre">2. Does the specification solve the problem stated in the introduction
and requirements?</pre>
    </blockquote>
    <p>Yes</p>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre wrap="" class="moz-quote-pre">3. Do you plan to implement this specification in your code? If not,
why not?</pre>
    </blockquote>
    <p>I've implemented it in Converse.</p>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre wrap="" class="moz-quote-pre">4. Do you have any security concerns related to this specification?</pre>
    </blockquote>
    Nothing beyond what's documented already.
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre wrap="" class="moz-quote-pre">5. Is the specification accurate and clearly written?</pre>
    </blockquote>
    Yes.
  </body>
</html>

--------------VaRBVcpia40ABhpyYfZWWg50--

--===============5257751053660165963==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============5257751053660165963==--