No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0208.xml 9.2KB

  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Bootstrapping Implementation of Jingle</title>
  10. <abstract>This document provides guidelines to XMPP client developers for bootstrapping implementation of Jingle technologies.</abstract>
  12. <number>0208</number>
  13. <status>Retracted</status>
  14. <type>Informational</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XEP-0166</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>N/A</shortname>
  24. &stpeter;
  25. <revision>
  26. <version>0.4</version>
  27. <date>2009-01-06</date>
  28. <initials>psa</initials>
  29. <remark><p>Retracted because unnecessary given the wide implementation of Jingle.</p></remark>
  30. </revision>
  31. <revision>
  32. <version>0.3</version>
  33. <date>2007-11-15</date>
  34. <initials>psa</initials>
  35. <remark><p>Editorial review and consistency check.</p></remark>
  36. </revision>
  37. <revision>
  38. <version>0.2</version>
  39. <date>2007-05-11</date>
  40. <initials>psa</initials>
  41. <remark><p>Specified use of port 17777 as default.</p></remark>
  42. </revision>
  43. <revision>
  44. <version>0.1</version>
  45. <date>2007-04-10</date>
  46. <initials>psa</initials>
  47. <remark><p>Initial published version.</p></remark>
  48. </revision>
  49. <revision>
  50. <version>0.0.2</version>
  51. <date>2007-03-23</date>
  52. <initials>psa</initials>
  53. <remark><p>Changed echo namespace to be a content description format only; defined basic direct-tcp transport for bootstrapping purposes only.</p></remark>
  54. </revision>
  55. <revision>
  56. <version>0.0.1</version>
  57. <date>2007-02-27</date>
  58. <initials>psa</initials>
  59. <remark><p>First draft.</p></remark>
  60. </revision>
  61. </header>
  62. <section1 topic='Introduction' anchor='intro'>
  63. <p>&xep0166; defines a framework for using XMPP to negotiate and manage out-of-band media sessions. Unfortunately, most developers of XMPP clients have limited experience with multimedia applications such as voice and video, making it difficult to get started with implementation of Jingle technologies. Therefore this document provides a simple application format that client developers can use to bootstrap Jingle implementations.</p>
  64. <p><em>Note: The methods specified herein are provided for experimentation and unit testing only. They are not intended for inclusion in released software or production environments.</em></p>
  65. </section1>
  66. <section1 topic='Resource Determination' anchor='session-resource'>
  67. <p>In order to initiate a Jingle session, the initiator must determine which of the responder's XMPP resources is best for the desired application format. The following approach may be helpful to implementors:</p>
  68. <ol>
  69. <li><p>If the intended responder shares presence with the initiator (see &xmppim;) and has only one available resource, the initiator SHOULD attempt to negotiate a Jingle session with that resource unless the initiator knows via &xep0030; or &xep0115; that the resource does not support Jingle and the desired application format. <note>Naturally, instead of sending service discovery requests to every contact in a user's roster, it is more efficient to use <cite>Entity Capabilities</cite>, whereby support for Jingle and various Jingle application formats and transport methods is determined for a client version in general (rather than on a per-JID basis) and then cached. Refer to <cite>XEP-0115</cite> for details.</note></p></li>
  70. <li><p>If the intended responder shares presence with the initiator and has more than one available resource but only one of the resources supports Jingle and the desired application format, the initiator SHOULD initiate the Jingle session with that resource.</p></li>
  71. <li><p>If the intended responder shares presence with the initiator and has more than one available resource but more than one of the resources supports Jingle and the desired application format, the initiator SHOULD use &xep0168; in order to determine which is the best resource with which to initiate the desired Jingle session.</p></li>
  72. <li><p>If the intended responder does not share presence with the initiator, the initiator SHOULD first send a &xep0155; request to the responder in order to initiate the exchange of XMPP stanzas. The request SHOULD include a RAP routing hint as specified in <cite>XEP-0168</cite> and the &MESSAGE; stanza containing the request SHOULD be of type "headline" so that (typically) it is not stored offline for later delivery. The stanza session negotiation SHOULD result in temporary sharing of presence between the parties via the "presence" field as described in <cite>XEP-0155</cite>.</p></li>
  73. </ol>
  74. </section1>
  75. <section1 topic='Protocol Flow' anchor='protocol'>
  76. <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>
  77. <example caption='Initiation'><![CDATA[
  78. <iq from=''
  79. id='jingle1'
  80. to=''
  81. type='set'>
  82. <jingle xmlns=''
  83. action='session-initiate'
  84. initiator=''
  85. sid='a73sjjvkla37jfea'>
  86. <content creator='initiator' name='echo-this'>
  87. <description xmlns=''/>
  88. <transport xmlns=''>
  89. <candidate ip='' port='17777' generation='0'/>
  90. </transport>
  91. </content>
  92. </jingle>
  93. </iq>
  94. ]]></example>
  95. <p>If none of the errors specified in <cite>XEP-0166</cite> occurs, the responder acknowledges the session initiation request.</p>
  96. <example caption='Responder acknowledges session-initiate'><![CDATA[
  97. <iq from=''
  98. id='jingle1'
  99. to=''
  100. type='result'/>
  101. ]]></example>
  102. <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>
  103. <example caption='Responder definitively accepts the session'><![CDATA[
  104. <iq from=''
  105. id='jingle2'
  106. to=''
  107. type='set'>
  108. <jingle xmlns=''
  109. action='session-accept'
  110. initiator=''
  111. sid='a73sjjvkla37jfea'/>
  112. </iq>
  113. ]]></example>
  114. <example caption='Initiating entity acknowledges definitive acceptance'><![CDATA[
  115. <iq from=''
  116. id='accept1'
  117. to=''
  118. type='result'/>
  119. ]]></example>
  120. <p>The parties may now exchange data using the echo protocol in order to test the connection.</p>
  121. </section1>
  122. <section1 topic='Security Considerations' anchor='security'>
  123. <p>As noted, the methods specified herein are provided for experimental use only and are not intended for inclusion in released software or production environments.</p>
  124. <p>On some operating systems, access to the root or administrative user may be necessary in order to use the echo protocol over TCP or UDP port 7; therefore it is RECOMMENDED to use port 17777 instead.</p>
  125. </section1>
  126. <section1 topic='IANA Considerations' anchor='iana'>
  127. <p>This document requires no interaction with &IANA;.</p>
  128. </section1>
  129. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  130. <section2 topic='Protocol Namespaces' anchor='ns'>
  131. <p>Because this specification defines an experimental protocol that is to be used only for bootstrapping purposes, the &REGISTRAR; shall not issue a permanent namespace upon approval of this specification. Therefore, its associated namespace shall always be "".</p>
  132. </section2>
  133. <section2 topic='Jingle Content Description Formats' anchor='registrar-content'>
  134. <p>The XMPP Registrar shall include "echo" in its registry of Jingle content description formats. The registry submission is as follows:</p>
  135. <code><![CDATA[
  136. <content>
  137. <name>echo</name>
  138. <desc>A bootstrapping method for exchanging echo protocol data (see RFC 862).</desc>
  139. <doc>XEP-0208</doc>
  140. </content>
  141. ]]></code>
  142. </section2>
  143. </section1>
  144. <section1 topic='XML Schema' anchor='schema'>
  145. <code><![CDATA[
  146. <?xml version='1.0' encoding='UTF-8'?>
  147. <xs:schema
  148. xmlns:xs=''
  149. targetNamespace=''
  150. xmlns=''
  151. elementFormDefault='qualified'>
  152. <xs:element name='description' type='empty'/>
  153. <xs:simpleType name='empty'>
  154. <xs:restriction base='xs:string'>
  155. <xs:enumeration value=''/>
  156. </xs:restriction>
  157. </xs:simpleType>
  158. </xs:schema>
  159. ]]></code>
  160. </section1>
  161. </xep>