[Standards] LAST CALL: XEP-0352 (Client State Indication)

Holger Weiß holger at zedat.fu-berlin.de
Mon Aug 10 09:01:45 UTC 2020

* XEP Editor Pipeline <xep-editor-pipeline at zombofant.net> [2020-08-04 16:05]:
> Title: Client State Indication
> Abstract:
> This document defines a way for the client to indicate its
> active/inactive state.
> URL: https://xmpp.org/extensions/xep-0352.html
> This Last Call begins today and shall end at the close of business on
> 2020-08-18.
> Please consider the following questions during this Last Call and send
> your feedback to the standards at xmpp.org discussion list:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?

Yes, at least as long as there's clients maintaining a persistent
connection and interested in having the server perform traffic
optimizations.  But I can also imagine other use cases for making the
server aware of the client state.

> 2. Does the specification solve the problem stated in the introduction
> and requirements?


> 3. Do you plan to implement this specification in your code? If not,
> why not?

I've implemented it for ejabberd in 2014.

> 4. Do you have any security concerns related to this specification?


> 5. Is the specification accurate and clearly written?



More information about the Standards mailing list