From 66a6ba98b952b50dc09131e0870b24d7e11f61f9 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Thu, 9 Feb 2017 09:17:13 +0000 Subject: [PATCH] Add error handling section --- xep-0369.xml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/xep-0369.xml b/xep-0369.xml index 0cc8370e..e50e6ec8 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -50,6 +50,8 @@ Clarifications of password control, voice and name/description (summit 4/5/6) Removal of Subject and reference future Sticky Messages XEP (summit 7); Use example JIDs aligned to anticipated BIND2 specification; + Clarify PubSub Node Type; + Clarify Error handling and Add Error for messages rejected by channel;

@@ -597,6 +599,17 @@ This approach enables flexible support of multiple clients for a MIX channel pa + +

+ The MIX specification is built on layered services that have defined errors. This enables the core MIX specification to reflect primarily the successful use case, as in almost all cases the error reporting of the layer service provide what is needed. A message sender MUST be prepared to handle any valid error from the layer services. When a message receiver encounters an error situation, it MUST use the most appropriate layer server error to report this issue back to the sender. For example a message receiver might use the "not authorized" IQ error in response to a MIX disco that is not authorized. Errors for the following layer services need to be handled for MIX: +

+
    +
  1. IQ. All of the IQ errors of &rfc6120; MUST be supported.
    2. +
  2. Messages. If a message is received and an error situation is encountered, an message of type error MUST be sent back to the message sender of type error specified in &rfc6121; containing an error defined in &rfc6120;, which is the same error set as for IQs.
    3. +
  3. Presence. Any responses to presence messages MUST follow the rules of &rfc6121;.
    4. +
  4. PubSub. Where MIX protocol messages use PubSub protocol, the errors defined in &xep0060; MUST be used and supported.
    5. +
+