From df0f08bf1dc5925b624e7176e514269ff104b9b3 Mon Sep 17 00:00:00 2001
From: Mickael Remond <mremond@process-one.net>
Date: Tue, 22 Sep 2015 22:47:20 +0200
Subject: [PATCH] Better wording and attempt to prepare revision notes

---
 xep-0033.xml | 41 +++++++++++++++++++++++++++++------------
 1 file changed, 29 insertions(+), 12 deletions(-)

diff --git a/xep-0033.xml b/xep-0033.xml
index 0b932ecc..f212a88b 100644
--- a/xep-0033.xml
+++ b/xep-0033.xml
@@ -26,6 +26,13 @@
         &hildjj;
         &stpeter;
 
+        <revision>
+            <version>1.2</version>
+            <date>2015-09-22</date>
+            <initials>mre</initials>
+            <remark>Clarification: Multicast service MUST track directed presence broadcast to later ensure broadcast of subsequent unvailable presence to the same receiving parties.</remark>
+        </revision>
+
         <revision>
             <version>1.1</version>
             <date>2004-09-15</date>
@@ -287,18 +294,28 @@
     <section1 topic='Business Rules' anchor='rules'>
       <section2 topic='Directed Presence' anchor='presence'>
 
-        <p>The multicast service MUST keep track of the entities it
-        sent a presence with an absent 'type' attribute (i.e. an
-        'available' presence) to and the originating entity of that
-        presence. If the multicast service receives an unavailable
-        presence from one of the tracked originating entities, it MUST
-        broadcast this presence to all tracked entities which have not
-        yet received an unavailable presence from the originating
-        entity, even if the presence does not contain explicit
-        broadcast addresses. Thus the multicast service ensures that
-        all entities, which have received an (directed) 'available'
-        presence over it, receive the related 'unavailable'
-        presence.</p>
+        <p>This specification can be used to, in effect, send directed
+        presence (see Section 4.6 of &rfc6121;). In order to ensure
+        that entities that have received directed available presence
+        through the service also are informed when the originating
+        entity sends unavailable presence, the multicast service MUST
+        do the following:</p>
+
+
+        <ol>
+          <li>Keep track of the entities to which it sends available
+          presence (i.e., presence stanzas with no 'type' attribute)
+          along with the originating entity of that presence.</li>
+
+          <li>Upon receiving a presence stanza of type "unavailable"
+          from an originating entity, broadcast that unavailable
+          presence to all entities to which it has send available
+          presence.</li>
+        </ol>
+
+        <p>In this way, the multicast service ensures that all
+        entities which have received available presence through the
+        service also receive the associated unavailable presence.</p>
       </section2>
     </section1>