mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-17 21:32:35 -05:00
90 lines
4.9 KiB
XML
90 lines
4.9 KiB
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<!DOCTYPE xep SYSTEM 'xep.dtd' [
|
|
<!ENTITY % ents SYSTEM 'xep.ent'>
|
|
%ents;
|
|
]>
|
|
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
|
|
<xep>
|
|
<header>
|
|
<title>Nonzas (are not Stanzas)</title>
|
|
<abstract>This specification defines the term "Nonza", describing every top level stream element that is not a Stanza.</abstract>
|
|
&LEGALNOTICE;
|
|
<number>0360</number>
|
|
<status>Deferred</status>
|
|
<type>Standards Track</type>
|
|
<sig>Standards</sig>
|
|
<approver>Council</approver>
|
|
<dependencies>
|
|
<spec>XMPP Core</spec>
|
|
</dependencies>
|
|
<supersedes/>
|
|
<supersededby/>
|
|
<shortname>NOT_YET_ASSIGNED</shortname>
|
|
&flow;
|
|
<revision>
|
|
<version>0.2</version>
|
|
<date>2017-09-11</date>
|
|
<initials>XEP Editor (jwi)</initials>
|
|
<remark>Defer due to lack of activity.</remark>
|
|
</revision>
|
|
<revision>
|
|
<version>0.1</version>
|
|
<date>2015-07-14</date>
|
|
<initials>XEP Editor (mam)</initials>
|
|
<remark><p>Initial published version approved by the XMPP Council.</p></remark>
|
|
</revision>
|
|
<revision>
|
|
<version>0.0.1</version>
|
|
<date>2015-06-01</date>
|
|
<initials>fs</initials>
|
|
<remark><p>First draft.</p></remark>
|
|
</revision>
|
|
</header>
|
|
<section1 topic='Introduction' anchor='intro'>
|
|
<p>The usage of non-Stanza top-level XMPP stream elements is steadily increasing in the last years. Starting with &xep0198;, one of the earliest XEPs which specified and used additional non-Stanza elements, the XMPP community sees an increasing usage of those elements in submitted specifications. Unlike Stanzas which are specified in &rfc6120; § 4.1 "Stream Fundamentals" and § 8. "XML Stanzas", there is no term and definition provided for them.</p>
|
|
<p>This leads to the unfortunate situation where some submitted XEPs erroneous refer to non-Stanza top level stream elements as 'Stanzas'. Thus causing confusion, and opening the door to possible interoperability breakage and security vulnerabilities.</p>
|
|
<p>This XEP tries to fix this by providing a term, a definition and declaring some rules for those XMPP stream elements.</p>
|
|
</section1>
|
|
<section1 topic='Nonza Definition' anchor='nonza'>
|
|
<p><strong>Nonza:</strong> A Nonza is every XML element found at the XMPP stream's top level which is not a Stanza. The top level of an XMPP stream is the child XML level beneath the last <stream> opening tag as defined in RFC 6120 § 4.2. "Opening a Stream", i.e. at depth=1 of the stream.</p>
|
|
<p><strong>Informal definition:</strong> A XMPP stream element is a Nonza, if its element name is not 'message', 'iq' or 'presence'.</p>
|
|
<p>The term 'Nonza' originates from the beginning and ending letters of its definition and thus makes it easy to recall that definition: <strong>No</strong>t a Sta<strong>nza</strong>.</p>
|
|
</section1>
|
|
<section1 topic='Nonza Examples' anchor='nonza-examples'>
|
|
<section2 topic='Nonzas used before resource binding' anchor='nonza-examples-before-binding'>
|
|
<example caption='The Stream Compression (XEP-0138) <compress/> Nonza'><![CDATA[
|
|
<compress xmlns='http://jabber.org/protocol/compress'>
|
|
<method>zlib</method>
|
|
</compress>]]></example>
|
|
</section2>
|
|
<section2 topic='Nonzas used after resource binding' anchor='nonza-examples-after-binding'>
|
|
<example caption='The Stream Management (XEP-0198) <enable/> Nonza'><![CDATA[
|
|
<enable xmlns='urn:xmpp:sm:3'/>]]></example>
|
|
<example caption='The Client State Indication (XEP-0352) <active/> Nonza'><![CDATA[
|
|
<active xmlns='urn:xmpp:csi:0'/>]]></example>
|
|
</section2>
|
|
</section1>
|
|
<section1 topic='Use Cases' anchor='usecases'>
|
|
<p>Nonzas are commonly used when it is not necessary to route the exchanged information behind the endpoints of an XMPP stream. For example, one use case is to control the XMPP stream like it is done in <cite>XEP-0198: Stream Management</cite>.</p>
|
|
<p>Nonzas sent before resource binding, as defined in RFC 6120 § 7., usually follow a request-response pattern. But after the client successfully bound a resource, they are used in a more "asynchronous" fashion, where a 'request' Nonza does not, or at least not immediately, trigger a 'result' Nonza sent back.</p>
|
|
</section1>
|
|
<section1 topic='Business Rules' anchor='rules'>
|
|
<ol>
|
|
<li>Nonzas MUST NOT be routed, i.e. they are only exchanged between the two endpoints of an XMPP stream.</li>
|
|
<li>Nonzas SHOULD NOT have a 'from' or 'to' attribute.</li>
|
|
</ol>
|
|
<p>
|
|
Note that an exception from 2. are the the widely used <db/> Nonzas defined in &xep0220;.
|
|
</p>
|
|
</section1>
|
|
<section1 topic='Security Considerations' anchor='security'>
|
|
<p>As noted, Nonzas MUST NOT get routed, because this could introduce the ability for third parties to spoof them.</p>
|
|
</section1>
|
|
<section1 topic='IANA Considerations' anchor='iana'>
|
|
<p>This document requires no interaction with &IANA;.</p>
|
|
</section1>
|
|
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
|
|
<p>This document requires no interaction with ®ISTRAR;.</p>
|
|
</section1>
|
|
</xep>
|