From b4bacd8f415cacc633d750f59ea760d28854396d Mon Sep 17 00:00:00 2001
From: nicoco <nicoco@nicoco.fr>
Date: Thu, 1 Dec 2022 06:50:26 +0100
Subject: [PATCH] Add MUC service shutdown example

---
 xep-0045.xml | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/xep-0045.xml b/xep-0045.xml
index c102cb9d..331fbc14 100644
--- a/xep-0045.xml
+++ b/xep-0045.xml
@@ -45,6 +45,12 @@
   </schemaloc>
   <registry/>
   &stpeter;
+  <revision>
+    <version>1.34.5</version>
+    <date>2022-12-01</date>
+    <initials>NC</initials>
+    <remark><p>Add MUC service shut down example.</p></remark>
+  </revision>
   <revision>
     <version>1.34.4</version>
     <date>2022-10-05</date>
@@ -4986,6 +4992,31 @@
      and they are not linked to any user (e.g. moderator) action that the 307 code usually indicates. It is therefore recommended for the
      client to ignore the 307 code if a 333 status code is present.</p>
   </section2>
+  <section2 topic='Service removes user because of service shut down' anchor='service-shutdown-kick'>
+    <p>When a MUC service shuts downs, it SHOULD inform its participant by sending presences containing the 332 status code</p>
+    <example caption='MUC service removes user because of service shutdown'><![CDATA[
+<presence
+    from='harfleur@chat.shakespeare.lit/pistol'
+    to='pistol@shakespeare.lit/client'
+    type='unavailable'>
+  <x xmlns='http://jabber.org/protocol/muc#user'>
+    <item affiliation='none' role='none' />
+    <status code='110'/>
+    <status code='332'/>
+  </x>
+</presence>
+<presence
+    from='harfleur@chat.shakespeare.lit/othello'
+    to='othello@shakespeare.lit/client'
+    type='unavailable'>
+  <x xmlns='http://jabber.org/protocol/muc#user'>
+    <item affiliation='none' role='none' />
+    <status code='110'/>
+    <status code='332'/>
+  </x>
+</presence>
+]]></example>
+  </section2>
 </section1>
 
 <section1 topic='Status Codes' anchor='statuscodes'>