moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

XEP-0220 v1.1rc2: see revision log

Browse Source
This commit is contained in:
Matthew A. Miller 2014-06-19 20:55:22 -06:00
parent d4afd93edd
commit e95d88f598
1 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
xep-0220.xml
View File

@ -11,7 +11,6 @@
&LEGALNOTICE;
<number>0220</number>
<status>Draft</status>
<interim/>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
@ -28,10 +27,16 @@
&stpeter;
&fippo;
<revision>
<version>1.1rc1</version>
<date>2014-05-28</date>
<initials>ph</initials>
<remark><p>Added resource-constraint dialback error condition.</p></remark>
<version>1.1rc2</version>
<date>2014-06-18</date>
<initials>ph/psa</initials>
<remark>
<ul>
<li>Added resource-constraint dialback error condition.</li>
<li>Provided guidance on the usage of the &lt;failed/&gt; dialback error.</li>
<li>Clarified that the dialback error conditions table is not exhaustive and any stanza error condition can be used.</li>
</ul>
</remark>
</revision>
<revision>
<version>1.0</version>
@ -521,7 +526,7 @@ send: <db:result
to='capulet.example'
type='invalid'/>
]]></example>
<p>If the type is "invalid", the Initiating Server is attempting to spoof the Sender Domain. The Receiving Server MUST NOT accept stanzas from the Initiating Server for the Sender Domain, ought to log the attempt, and MUST close the XML stream.</p>
<p>If the result is "invalid", the Initiating Server is either attempting to spoof the Sender Domain, or misconfigured. The Receiving Server MUST NOT accept stanzas from the Initiating Server for the Sender Domain and ought to log the attempt. If no other valid domain pairs exist for this connection (ie, if this is the first attempt), the Receiving Server SHOULD send a result with type "invalid" and MUST close the XML stream. If there exist other valid domain pairs for this connection, the Initiating Server might merely have a misconfiguration for the Sender Domain. In this case, the Receiving Server MAY return an error condition of &lt;forbidden/&gt; as described under Section 2.5 of this document.</p>
</section3>
<section3 topic="Authoritative Server Handles Inbound Verification Request from Receiving Server">
@ -612,7 +617,7 @@ send: <db:verify
<!-- credits: Matthias in http://mail.jabber.org/pipermail/standards/2007-June/015662.html -->
<p><cite>RFC 3920</cite> introduced stream errors for any errors related to dialback. However, this turned out to be overly aggressive, particularly if the XML stream was used to multiplex stanzas for more than one domain pair (since closing the stream would result in throwing away accumulated dialback state for a potentially large number of domain pairs). Therefore this specification defines a third value for the 'type' attribute: "error".</p>
<p>This usage of the 'error' value for the 'type' attribute is not fully backward compatible with <cite>RFC 3920</cite>. However, the server that generates the error SHOULD still attempt to send the dialback error instead of terminating the stream, as the worst thing that can happen is that the remote server terminates the stream if it does not understand the error or if it eventually times out the connection. Dialback errors are to be considered non-fatal for the XML stream, but the Initiating Server MUST return queued stanzas to the respective senders with a &timeout; stanza error. If an error is encountered in Step 3 of the dialback negotiation, the Receiving Server MUST send a &lt;remote-server-not-found/&gt; dialback error to the Initiating Server.</p>
<p>When the &lt;db:verify/&gt; or &lt;db:result/&gt; element is of type "error", the element MUST contain an &lt;error/&gt; element (implicitly qualified by the 'jabber:server' namespace), which MUST in turn contain an XML element qualified by the 'urn:ietf:params:xml:ns:xmpp-stanzas' namespace (i.e., a stanza error condition), in accordance with the following table.</p>
<p>When the &lt;db:verify/&gt; or &lt;db:result/&gt; element is of type "error", the element MUST contain an &lt;error/&gt; element (implicitly qualified by the 'jabber:server' namespace), which MUST in turn contain an XML element qualified by the 'urn:ietf:params:xml:ns:xmpp-stanzas' namespace (i.e., a stanza error condition) as those errors are defined in RFC 6120. The following table provides additional guidance regarding the most relevant stanza error conditions:</p>
<table caption='Dialback error conditions'>
<tr>
<th>Condition</th>