From 31356f8071fc4266e6a935f85ad44a501a813cf8 Mon Sep 17 00:00:00 2001
From: Florian Schmaus <flo@geekplace.eu>
Date: Sat, 18 Feb 2017 11:01:23 +0100
Subject: [PATCH] XEP-0352: Clarify the CSI state after SM resumption.

---
 xep-0352.xml | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/xep-0352.xml b/xep-0352.xml
index 8cfba763..4c2c2bff 100644
--- a/xep-0352.xml
+++ b/xep-0352.xml
@@ -23,6 +23,12 @@
   <supersededby/>
   <shortname>csi</shortname>
   &mwild;
+  <revision>
+    <version>0.2.1</version>
+    <date>2017-02-18</date>
+    <initials>fs</initials>
+    <remark><p>Clarify that the CSI state is not restored when the stream is resumed.</p></remark>
+  </revision>
   <revision>
     <version>0.2</version>
     <date>2015-10-02</date>
@@ -146,6 +152,14 @@ and responds to the ping with a pong -->
 <iq to='juliet@capulet.lit/baclony' from='capulet.lit' id='ping1' type='result'/>
 <!-- Stream state is now 'active' -->]]></example>
   </section2>
+  <section2 topic='Interaction with Stream Resumption' anchor='stream-resumption'>
+    <p>After a previous stream was resumed using mechanisms like
+    &xep0198;, the CSI state is <em>not</em> restored. That is, stream
+    resumption does not affect the current CSI state, which always
+    defaults to 'active' for new and resumed streams. Clients wishing
+    to immediately go to the inactive state should do so after stream
+    resumption.</p>
+  </section2>
 </section1>
 <section1 topic='Security Considerations' anchor='security'>
   <p>To protect the privacy of users, servers MUST NOT reveal the clients active/inactive state to other
@@ -180,4 +194,7 @@ and responds to the ping with a pong -->
 </xs:schema>
 ]]></code>
 </section1>
+<section1 topic='Acknowledgements' anchor='acknowledgements'>
+  <p>Thanks to Florian Schmaus for his feedback.</p>
+</section1>
 </xep>