From aadcc2d325b08007060abedc476d5f27b0c81695 Mon Sep 17 00:00:00 2001
From: Kevin Smith <git@kismith.co.uk>
Date: Thu, 29 Mar 2018 08:45:27 +0100
Subject: [PATCH] Reflect messages

This doesn't wrap them in a forward, which is something that needs
discussion
---
 inbox/im-ng.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/inbox/im-ng.xml b/inbox/im-ng.xml
index 9ffb564d..f44f3bbd 100644
--- a/inbox/im-ng.xml
+++ b/inbox/im-ng.xml
@@ -89,7 +89,7 @@
             type='result'/>]]></example>
     </section2>
     <section2 topic='Sending messages' anchor='sending'>
-        <p>When an entity wants to send a non-error message to be handled by all a user's IM-NG clients they will send it to the user's bare JID, which the receiving server then MUST send to all IM-NG resources.</p>
+        <p>When an entity wants to send a non-error message to be handled by all a user's IM-NG clients they will send it to the user's bare JID, which the receiving server then MUST send to all the contact's IM-NG resources, and the sending server must reflect to all the user's IM-NG resources.</p>
         <example caption='Client sends a message that IM-NG will route to all resources'><![CDATA[
       <message xmlns='jabber:client'
           from='montague@montague.example/bas149a'
@@ -117,6 +117,7 @@
   <p>A client activating IM-NG MUST NOT also activate Carbons.</p>
   <p>An IM-NG client SHOULD send all IM-related messages to bare JIDs (as full-JID messages would not be distributed appropriately).</p>
   <p>An IM-NG client SHOULD ignore any IM-related messages that are sent to a full-JID with an &lt;im-ng xmlns='urn:xmpp:im-ng:0'&gt; element (see Security Considerations).</p>
+  <p>When reflecting an IM-NG client's outbound bare-JID messages, the server SHOULD reflect the archived version (i.e. after any transforms have taken place).</p>
 </section1>
 <!--<section1 topic='Implementation Notes' anchor='impl'>
   <p>OPTIONAL.</p>