diff --git a/xep-0352.xml b/xep-0352.xml
index aee6331b..cb3aa52e 100644
--- a/xep-0352.xml
+++ b/xep-0352.xml
@@ -10,7 +10,8 @@
   <abstract>This document defines a way for the client to indicate its active/inactive state.</abstract>
   &LEGALNOTICE;
   <number>0352</number>
-  <status>Experimental</status>
+  <status>Proposed</status>
+  <lastcall>2015-09-07</lastcall>
   <type>Standards Track</type>
   <sig>Standards</sig>
   <approver>Council</approver>
@@ -55,10 +56,10 @@
     <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>
-  
+
     <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>
-  
+
     <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.</p>
   </section2>
@@ -96,12 +97,12 @@
     <example caption='Client indicates it is inactive'><![CDATA[
       <inactive xmlns='urn:xmpp:csi:0'/>
     ]]></example>
-    
+
     <p>As might be anticipated, when the client is active again it sends an &lt;active/&gt; element:</p>
     <example caption='Client indicates it is active'><![CDATA[
       <active xmlns='urn:xmpp:csi:0'/>
     ]]></example>
-  
+
     <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).</p>
   </section2>
@@ -109,10 +110,10 @@
 <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>
-  
+
   <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>
-  
+
   <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.</p>