On 07.12.2017 18:35, Jonas Wielicki (XSF Editor) wrote:
This message constitutes notice of a Last Call for comments on
XEP-0352.
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
2017-12-21.
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.
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?
It is intentionally leaves lot of space for implementers, but we can
live with it for the time being.
Presence and bodiless stanzas are called out and they represent majority
of the messages which could be safely dropped/delayed (yes, there's also
omemo).
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
