[Telepathy-commits] [telepathy-spec/master] Message_Flag_Report_Delivery: delivery failure reports should usually occur

Simon McVittie simon.mcvittie at collabora.co.uk
Tue Oct 28 11:11:01 PDT 2008


---
 spec/Channel_Interface_Messages.xml |   17 +++++++++++------
 1 files changed, 11 insertions(+), 6 deletions(-)

diff --git a/spec/Channel_Interface_Messages.xml b/spec/Channel_Interface_Messages.xml
index 5b18ca6..0963ffc 100644
--- a/spec/Channel_Interface_Messages.xml
+++ b/spec/Channel_Interface_Messages.xml
@@ -740,15 +740,20 @@ USA.</p>
       </tp:docstring>
 
       <tp:flag suffix="Report_Delivery" value="1">
-        <tp:docstring>
-          Provide a delivery report via the DeliveryReporting interface, if
-          possible, even if this is not the default for this protocol.
-          Ignored if delivery reports are not possible on this protocol.
+        <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
+          <p>Provide a successful delivery report if possible, even if this is
+            not the default for this protocol. Ignored if delivery reports are
+            not possible on this protocol.</p>
 
           <tp:rationale>
-            In some protocols, like XMPP, it is not conventional to request
-            or send delivery notifications.
+            <p>In some protocols, like XMPP, it is not conventional to request
+              or send positive delivery notifications.</p>
           </tp:rationale>
+
+          <p>Delivery failure reports SHOULD always be sent, but if this flag
+            is present, the connection manager MAY also try harder to obtain
+            failed delivery reports or allow them to be matched to outgoing
+            messages.</p>
         </tp:docstring>
       </tp:flag>
     </tp:flags>
-- 
1.5.6.5




More information about the Telepathy-commits mailing list