From 53d9cd7be7809e3154ee978947f8f7937f3fb821 Mon Sep 17 00:00:00 2001
From: Steve Kille <steve.kille@isode.com>
Date: Wed, 19 Jul 2017 11:47:00 +0100
Subject: [PATCH] Clarification on join with no subscribes

---
 xep-0369.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xep-0369.xml b/xep-0369.xml
index 4606de52..d01440cd 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -961,7 +961,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
 <section1 topic='Use Cases' anchor='usecases'>
   <section2 topic='Common User Use Cases' anchor='usecases-user'>
     <section3 topic='Joining a Channel' anchor='usecase-user-join'>
-      <p>A user joins a channel by sending a MIX "join" command. There is no default set of nodes, so the user MUST specify the set of nodes to be subscribed to. To achieve the equivalent service to MUC, a user would subscribe to messages, and presence. The &lt;join/&gt; is a child element of &lt;iq/&gt; element.  The &lt;join/&gt; element is qualified by the 'urn:xmpp:mix:1' namespace.  The channel is specified by a 'channel' attribute in the &lt;join/&gt; element.  The requested nodes are encoded as &lt;subscribe/&gt; child elements of the &lt;join/&gt; element.
+      <p>A user joins a channel by sending a MIX "join" command. There is no default set of nodes, so the user MUST specify the set of nodes to be subscribed to. To achieve the equivalent service to MUC, a user would subscribe to both messages and presence nodes.  A user will typically subscribe to at least the message and/or presence nodes but MAY join and not subscribe to any nodes. The &lt;join/&gt; is a child element of &lt;iq/&gt; element.     The &lt;join/&gt; element is qualified by the 'urn:xmpp:mix:1' namespace.  The channel is specified by a 'channel' attribute in the &lt;join/&gt; element.  The requested nodes are encoded as &lt;subscribe/&gt; child elements of the &lt;join/&gt; element.
          The join leads to the server subscribing the user to each of the requested nodes associated with the channel. The MIX service will also add the user to the participant list by injecting a new item into the "urn:xmpp:mix:nodes:participants" node automatically.
 
       </p>
@@ -1036,7 +1036,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
 </iq>
 ]]></example>
       <p>
-        If a user cannot be subscribed to one or more of the requested nodes (e.g., because the node does not exist), but can be subscribed to some the response simply lists the nodes successfully subscribed.    If none of the nodes requested are successfully subscribed to, an error response is sent indicating the reason that the first node requested was not subscribed to.   This error response will also include other nodes requested where subscription failed for the same reason. </p>
+        If a user cannot be subscribed to one or more of the requested nodes (e.g., because the node does not exist), but can be subscribed to some the response simply lists the nodes successfully subscribed.    If at least one node is requested and none of the nodes requested are successfully subscribed to, an error response is sent indicating the reason that the first node requested was not subscribed to.   This error response will also include other nodes requested where subscription failed for the same reason. </p>
 
       <p>
         The following response example shows a successful response to the initial request example where