From 33dd5386b17eea2be3cdfa6a39459579382139bb Mon Sep 17 00:00:00 2001
From: Steve Kille <steve.kille@isode.com>
Date: Tue, 11 Dec 2018 08:52:13 +0000
Subject: [PATCH] Add participant ID to roster;

---
 xep-0405.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/xep-0405.xml b/xep-0405.xml
index 8293d5e3..acd89ff6 100644
--- a/xep-0405.xml
+++ b/xep-0405.xml
@@ -44,6 +44,7 @@
     <initials>sek</initials>
     <remark>
       Discovery on Account rather than Server;
+      Add participant ID to roster;
     </remark>
   </revision>
   <revision>
@@ -541,12 +542,12 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
 ]]></example>
 
     <p>
-      MIX channels in the roster information returned in response to a request for this additional MIX information MUST have an element &lt;channel/&gt; qualified by the ‘urn:xmpp:mix:roster:0' namespace  included in the roster item, as shown inf the following example.
+      MIX channels in the roster information returned in response to a request for this additional MIX information MUST have an element &lt;channel/&gt; qualified by the ‘urn:xmpp:mix:roster:0' namespace  included in the roster item.  The &lt;channel/&gt; element MUST also include a 'participant-id' attribute that is the stable ID of the client.   This facilitates the client to match messages that reference this stable ID.   A MIX extended roster item is shown in the following example.
     </p>
 
     <example caption="Roster Item Encoding of a MIX Channel"><![CDATA[
   <item jid='balcony@example.net'>
-      <channel xmlns='urn:xmpp:mix:roster:0'/>
+      <channel xmlns='urn:xmpp:mix:roster:0' participant-id='123456'/>
   </item>
 ]]></example>