<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title >Client State Indication </title>
<abstract >This document defines a way for the client to indicate its active/inactive state. </abstract>
<number >0352 </number>
<status >Proposed </status>
<lastcall >2017-03-01 </lastcall>
<lastcall >2017-02-22 </lastcall>
<lastcall >2015-09-07 </lastcall>
<type >Standards Track </type>
<sig >Standards </sig>
<approver >Council </approver>
<spec >XMPP Core </spec>
<shortname >csi </shortname>
<version >0.2 </version>
<date >2015-10-02 </date>
<initials >XEP Editor (mam) </initials>
<remark > <p >Clarified how CSI is affected by in-order processing (Florian Schmaus). </p> </remark>
<version >0.1 </version>
<date >2014-08-28 </date>
<initials >XEP Editor (asw) </initials>
<remark > <p >Initial published version approved by the XMPP Council. </p> </remark>
<version >0.0.1 </version>
<date >2014-08-14 </date>
<initials >mw </initials>
<remark > <p >First draft. </p> </remark>
<section1 topic= 'Introduction' anchor= 'intro' >
<p >It is common for IM clients to be logged in and 'online' even while the user is not interacting with the application. This
protocol allows the client to indicate to the server when the user is not actively using the client, allowing the server to
optimise traffic to the client accordingly. This can save bandwidth and resources on both the client and server.
<section1 topic= 'Requirements' anchor= 'reqs' >
<p >The aim of this specification is to provide a simple and efficient protocol for the client to report its
state to the server. Exactly how the server uses this information is beyond the scope of this document, although
some examples are given.
<p >Other extensions exist, such as &xep0273;, which also aim to optimise the traffic between the client and server.
A notable difference is that instead of being client-controlled, CSI shifts the responsibility to the server, and
aims to just provide the server with enough information to implement various optimisations itself.
<section1 topic= 'Use Cases' anchor= 'usecases' >
<section2 topic= 'User and client behaviour' anchor= 'behaviour-user' >
<p >Juliet has an XMPP client on her phone, which is available to receive messages. However most of the time
Juliet has her phone screen turned off and is not interested in the status of her contacts unless they are
communicating with her.
<p >Juliet's client informs the server when Juliet is not interacting with it. The server uses this information to
suppress or reduce stanzas that are unimportant, such as status updates.
<p >When Juliet returns to her IM client, the client again informs the server, this time to report that it is active
again. The server then disables its traffic optimisations and restores the stream to its normal state.
<section2 topic= "Server behaviour" >
<p >When the server knows that the user is not engaging with their client many optimisations become possible. For
example a server could:
<li >Suppress presence updates until the client becomes active again. On becoming active, push the latest
presence from each contact.
<li >Discard messages containing only &xep0085; payloads. </li>
<li >Defer or discard unimportant PEP notifications, possibly unsubscribe from certain PEP nodes
until the client becomes active again.
<p >This list is for example only, a server is not required to implement all or any of these, nor is it prevented
from implementing other behaviour not listed here. Regardless of what optimisations a server implements, it SHOULD
provide a way for administrators to configure them, and MAY provide such configuration to users also (e.g., through an
<section1 topic= "Protocol" anchor= "protocol" >
<section2 topic= "Discovering support" anchor= "discovery" >
<p >If the server supports CSI, it advertises it in the stream features after the client has authenticated: </p>
<example caption= 'Server indicates support for CSI' > <![CDATA[
<bind xmlns= 'urn:ietf:params:xml:ns:xmpp-bind' />
<csi xmlns= 'urn:xmpp:csi:0' />
<section2 topic= "Indicating state" anchor= "indication" >
<p >A stream always begins in 'active' state. If a client wishes to inform the server that it has become inactive,
it sends an
<inactive/ > element in the 'urn:xmpp:csi:0' namespace: </p>
<example caption= 'Client indicates it is inactive' > <![CDATA[
<inactive xmlns= 'urn:xmpp:csi:0' />
<p >As might be anticipated, when the client is active again it sends an <active/ > element: </p>
<example caption= 'Client indicates it is active' > <![CDATA[
<active xmlns= 'urn:xmpp:csi:0' />
<p >There is no reply from the server to either of these elements (though they may indirectly cause the server to
send stanzas, e.g., to update presence information when the client becomes active after a period of inactivity).
<section1 topic= 'Business Rules' anchor= 'rules' >
<p >As this protocol is for indication only, clients MUST NOT make assumptions about how the server
will use the active/inactive state information.
<p >The server MUST assume all clients to be in the 'active' state until the client indicates otherwise. Also the
CSI active/inactive state is unrelated to the user's presence, the server MUST treat the two independently.
<p >This protocol is intended primarily for clients with human interaction. Due to the open-ended nature of
the possible optimisations implemented by the server, it may not be suitable for non-IM purposes where the
fully standard behaviour of XMPP is required.
<section2 topic= "In-order processing" anchor= "in-order-processing" >
XMPP requires stanzas to be processed in order as per
&rfc6120; 10.1. Especially "If the server's processing of a particular request could have an effect on its processing of subsequent data it might receive over that input stream..., it MUST suspend processing of subsequent data until it has processed the request.". As a result, all actions triggered by a CSI nonza sent to the server must happen before processing further requests from the same client to the server.
For example: A client sends a CSI active nonza, followed by an XMPP Ping request to the server. The server first changes the CSI state to active and flushes all eventually queued stanzsa. After the state has been restored to 'active' and
all resulting stanzas have been put on the wire, the
server sends the pong.
<example caption= 'In-order processing' > <![CDATA[
<!-- Client sends 'active' and a ping to the server -->
<active xmlns= 'urn:xmpp:csi:0' />
<iq to= 'capulaet.lit' from= 'email@example.com/balcony' id= 'ping1' type= 'get' >
<ping xmlns= 'urn:xmpp:ping' />
<!-- Server restores stream state to active,
e.g. by flushing out queued stanzas to the client.
and responds to the ping with a pong -->
<iq to= 'firstname.lastname@example.org/baclony' from= 'capulet.lit' id= 'ping1' type= 'result' />
<!-- Stream state is now 'active' -->]]> </example>
<section1 topic= 'Security Considerations' anchor= 'security' >
<p >To protect the privacy of users, servers MUST NOT reveal the clients active/inactive state to other
entities on the network.
<section1 topic= 'IANA Considerations' anchor= 'iana' >
<p >This document requires no interaction with &IANA;. </p>
<section1 topic= 'XMPP Registrar Considerations' anchor= 'registrar' >
<p >This document requires no interaction with ®ISTRAR;. </p>
<section1 topic= 'XML Schema' >
<code > <![CDATA[
<?xml version='1.0' encoding='UTF-8'?>
<xs:element name= 'csi' type= 'empty' />
<xs:element name= 'active' type= 'empty' />
<xs:element name= 'inactive' type= 'empty' />
<xs:simpleType name= 'empty' >
<xs:restriction base= 'xs:string' >
<xs:enumeration value= '' />