moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

1.0 DRAFT 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@365 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-01-17 21:28:07 +00:00
parent 911d79130b
commit d9b8123dec
1 changed files with 21 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
xep-0192.xml
View File

@ -10,7 +10,7 @@
<abstract>This document proposes improvements to the XML stream features definition for inclusion in the specification that supersedes RFC 3920.</abstract>
&LEGALNOTICE;
<number>0192</number>
<status>Proposed</status>
<status>Draft</status>
<type>Standards Track</type>
<sig>Standards</sig>
<dependencies>
@ -20,6 +20,12 @@
<supersededby>None</supersededby>
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>1.0</version>
<date>2007-01-17</date>
<initials>psa</initials>
<remark><p>Per a vote of the XMPP Council, advanced specification to Draft; assigned urn:xmpp:features:dialback as namespace for dialback stream feature.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2006-12-20</date>
@ -191,7 +197,14 @@ S: <iq type='result' id='bind_1'>
xmlns:db='jabber:server:dialback'
id='s2s_123'>
]]></example>
<p>However, it is not clear if inclusion of the dialback namespace indicates that a server supports the server dialback protocol or that it requires negotiation of server dialback. To make this clear, we define a stream feature for server dialback.</p>
<p>However, it is not clear if inclusion of the dialback namespace indicates that a server supports the server dialback protocol or that it requires negotiation of server dialback. To make this clear, we define a stream feature for server dialback:</p>
<example caption='Dialback stream feature'><![CDATA[
<stream:features>
<dialback xmlns='urn:xmpp:features:dialback'>
<required/>
</dialback>
</stream:features>
]]></example>
<p>Consider the following scenario, in which Server1 provides a self-signed certificate. According to Server2's local service policy, it does not consider self-signed certificates to be trustworthy and therefore requires negotiation of server dialback in this case.</p>
<example caption='A stream negotiation with server dialback'><![CDATA[
S1: <stream:stream
@ -235,7 +248,7 @@ S2: <stream:stream
version='1.0'>
S2: <stream:features>
<dialback xmlns='http://jabber.org/features/dialback'>
<dialback xmlns='urn:xmpp:features:dialback'>
<required/>
</dialback>
</stream:features>
@ -251,15 +264,15 @@ S2: <stream:features>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Stream Features' anchor='registrar-stream'>
<p>The &REGISTRAR; shall issue an XMPP URN for the dialback stream feature and include the feature in its stream feature registry (see &STREAMFEATURES;).</p>
<p>The &REGISTRAR; includes a dialback stream feature of 'urn:xmpp:features:dialback' in its registry of stream features (see &STREAMFEATURES;).</p>
<p>The submission is as follows:</p>
<code><![CDATA[
<feature>
<ns>TO BE ISSUED</ns>
<ns>urn:xmpp:features:dialback</ns>
<name>dialback</name>
<element>dialback</element>
<desc>Support for Server Dialback</desc>
<doc>rfc3920bis</doc>
<doc>XEP-0192 (rfc3920bis when published)</doc>
</feature>
]]></code>
</section2>
@ -381,8 +394,8 @@ S2: <stream:features>
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='TO BE ISSUED'
xmlns='TO BE ISSUED'
targetNamespace='urn:xmpp:features:dialback'
xmlns='urn:xmpp:features:dialback'
elementFormDefault='qualified'>
<xs:element name='dialback'>