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

text tweaks

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1419 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-11-27 19:31:43 +00:00
parent b593c8049a
commit 6f67dc4cfa
1 changed files with 21 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
xep-0208.xml
View File

@ -7,7 +7,7 @@
<xep>
<header>
<title>Bootstrapping Implementation of Jingle</title>
<abstract>This document provides guidelines to client developers for bootstrapping implementation of Jingle technologies.</abstract>
<abstract>This document provides guidelines to XMPP client developers for bootstrapping implementation of Jingle technologies.</abstract>
&LEGALNOTICE;
<number>0208</number>
<status>Proposed</status>
@ -62,7 +62,10 @@
<section1 topic='Protocol Flow' anchor='protocol'>
<p>The intent of this simple Jingle profile is to enable exchange of data using the Echo Protocol specified in &rfc0862;, but using a port other than 7 (the default port for this experimental usage is 17777). The protocol flow is as follows. (The following examples use &xep0177; as the transport protocol; although it is possible to complete echo protocol exchanges via TCP, that is deemed less useful and there is no Jingle transport method for direct TCP exchanges.)</p>
<example caption='Initiation'><![CDATA[
<iq from='romeo@montague.net/orchard' to='juliet@capulet.com/balcony' id='jingle1' type='set'>
<iq from='romeo@montague.net/orchard'
id='jingle1'
to='juliet@capulet.com/balcony'
type='set'>
<jingle xmlns='http://www.xmpp.org/extensions/xep-0166.html#ns'
action='session-initiate'
initiator='romeo@montague.net/orchard'
@ -76,13 +79,19 @@
</jingle>
</iq>
]]></example>
<p>If none of the errors specified in <cite>XEP-0166</cite> occurs, the receiver acknowledges the session request.</p>
<example caption='Receiver provisionally accepts the session request'><![CDATA[
<iq from='juliet@capulet.com/balcony' to='romeo@montague.net/orchard' type='result' id='jingle1'/>
<p>If none of the errors specified in <cite>XEP-0166</cite> occurs, the responder acknowledges the session initiation request.</p>
<example caption='Responder acknowledges session-initiate'><![CDATA[
<iq from='juliet@capulet.com/balcony'
id='jingle1'
to='romeo@montague.net/orchard'
type='result'/>
]]></example>
<p>If no negotiation is required (e.g., to modify the port number or transport method), the receiver simply accepts the session request. (Alternatively, if the receiver wants to use a port other 17777, it SHOULD negotiate the port using a Jingle content-add action; see <cite>XEP-0166</cite> for details and examples.)</p>
<example caption='Receiver definitively accepts the session request'><![CDATA[
<iq from='juliet@capulet.com/balcony' to='romeo@montague.net/orchard' id='jingle2' type='set'>
<p>If no negotiation is required (e.g., to modify the port number or transport method), the responder simply accepts the session. (Alternatively, if the responder wants to use a port other 17777, it SHOULD negotiate the port using a Jingle content-modify action; see <cite>XEP-0166</cite> for details and examples.)</p>
<example caption='Responder definitively accepts the session'><![CDATA[
<iq from='juliet@capulet.com/balcony'
id='jingle2'
to='romeo@montague.net/orchard'
type='set'>
<jingle xmlns='http://www.xmpp.org/extensions/xep-0166.html#ns'
action='session-accept'
initiator='romeo@montague.net/orchard'
@ -90,10 +99,12 @@
</iq>
]]></example>
<example caption='Initiating entity acknowledges definitive acceptance'><![CDATA[
<iq type='result' to='juliet@capulet.com/balcony' from='romeo@montague.net/orchard' id='accept1'/>
<iq from='romeo@montague.net/orchard'
id='accept1'
to='juliet@capulet.com/balcony'
type='result'/>
]]></example>
<p>The parties may now exchange data using the echo protocol in order to test the connection.</p>
<p>Note: Protocol flows for additional use cases (e.g., renegotiation) may be added to future versions of this specification.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>