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-0081.xml 14KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270
  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>Jabber MIME Type</title>
  10. <abstract>This document specifies a MIME type for launching a Jabber client as a helper application from most modern web browsers, and for completing basic use cases once the client is launched.</abstract>
  11. &LEGALNOTICE;
  12. <number>0081</number>
  13. <status>Retracted</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. <spec>XMPP IM</spec>
  19. <spec>RFC 2045</spec>
  20. <spec>RFC 3023</spec>
  21. <spec>XEP-0045</spec>
  22. <spec>XEP-0077</spec>
  23. </dependencies>
  24. <supersedes/>
  25. <supersededby/>
  26. <shortname>mimetype</shortname>
  27. &hildjj;
  28. &stpeter;
  29. <revision>
  30. <version>0.5</version>
  31. <date>2005-07-19</date>
  32. <initials>psa</initials>
  33. <remark>Retracted the proposal (again) in favor of draft-saintandre-xmpp-iri.</remark>
  34. </revision>
  35. <revision>
  36. <version>0.4</version>
  37. <date>2005-01-05</date>
  38. <initials>psa</initials>
  39. <remark>Reinstated the proposal since it fills a need not met by RFC 3923 and draft-saintandre-xmpp-uri; specified XML schema; specified IANA considerations, including content-type registration; further specified security considerations; removed use cases for service discovery, directory search, vCard lookup, and authentication; added more detailed descriptive text to remaining use cases.</remark>
  40. </revision>
  41. <revision>
  42. <version>0.3</version>
  43. <date>2004-07-26</date>
  44. <initials>psa</initials>
  45. <remark>Formally retracted this proposal in favor of the relevant Internet-Drafts.</remark>
  46. </revision>
  47. <revision>
  48. <version>0.2</version>
  49. <date>2003-08-18</date>
  50. <initials>psa</initials>
  51. <remark>Added authentication example.</remark>
  52. </revision>
  53. <revision>
  54. <version>0.1</version>
  55. <date>2003-04-21</date>
  56. <initials>psa</initials>
  57. <remark>Initial version.</remark>
  58. </revision>
  59. </header>
  60. <section1 topic='Introduction' anchor='intro'>
  61. <p>The value of a URI scheme (see &rfc3986;) for Jabber/XMPP communications has long been recognized within the Jabber community, and such a scheme has been formally defined in &rfc5122; as a way of identifying entities that adhere to &xmppcore; or its antecedents. Unfortunately, URI schemes are slow to be accepted on the Internet, such that it might be years (if ever) before widely deployed software such as web browsers will support addresses of the form &lt;xmpp:user@domain&gt;.</p>
  62. <p>Thankfully, it is not necessary for the large existing base of deployed software to support the xmpp: URI scheme in order to integrate Jabber/XMPP support. A well-accepted alternative approach
  63. <note>See, for instance, &lt;<link url='http://www.mozilla.org/docs/web-developer/mimetypes.html'>http://www.mozilla.org/docs/web-developer/mimetypes.html</link>&gt; for information about MIME support in the Mozilla family of web browsers.</note>
  64. is to define a MIME type (in accordance with &rfc2045;) and then reconfigure the relevant server and client software to correctly handle the new MIME type.</p>
  65. <p>Therefore, this document defines a MIME type of "application/jabber+xml" (in particular, an XML media type in accordance with &rfc3023;). Files of this MIME type would commonly be accessed with a web browser via HTTP, although other access methods are possible (e.g., attachment of the MIME type to an email message). On opening a file of this type, a browser would (by configuration) invoke an appropriate "helper" application (i.e., an external Jabber client, plugin, or internal module) that would enable the user to interact with a Jabber/XMPP server. If the user is not currently connected to a server, the invoked program would be responsible for connecting the user with appropriate prompting for authentication credentials. The file passed to the helper application would define parameters needed to complete a certain use case, such as sending a message to another user.</p>
  66. <p>Note: The "application/jabber+xml" MIME type defined herein is not to be confused with the "application/xmpp+xml" MIME type defined in &rfc3923;; the two MIME types address different requirements and do not overlap or conflict.</p>
  67. </section1>
  68. <section1 topic='Use Cases' anchor='usecases'>
  69. <p>The solution MUST enable a user to complete the following use cases, support for which is REQUIRED:</p>
  70. <ul>
  71. <li>Send a single message to another user.</li>
  72. <li>Initiate a one-to-one chat session with another user.</li>
  73. <li>Subscribe to another user's presence.</li>
  74. </ul>
  75. <p>In addition, the solution SHOULD enable a user to complete the following use cases, support for which is RECOMMENDED:</p>
  76. <ul>
  77. <li>Join a groupchat room.</li>
  78. <li>Register with a service.</li>
  79. <!--
  80. <li>Send a &xep0030; request.</li>
  81. <li>Search a user directory (see &xep0055;).</li>
  82. <li>Request another user's vCard.</li>
  83. -->
  84. </ul>
  85. <p>These use cases are defined below.</p>
  86. <section2 topic='Sending a Message' anchor='message'>
  87. <p>In order to send a message to a contact, the user opens an XMPP file of the following form:</p>
  88. <code><![CDATA[
  89. <?xml version='1.0' encoding='UTF-8'?>
  90. <jabber>
  91. <message jid='stpeter@jabber.org'/>
  92. </jabber>
  93. ]]></code>
  94. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for sending a single message to the JID defined in the file. If the user completes the interface, the helper application shall then send a message stanza of type='normal' as specified in &xmppim;, first authenticating with the user's Jabber/XMPP server if necessary.</p>
  95. </section2>
  96. <section2 topic='Starting a Chat' anchor='chat'>
  97. <code><![CDATA[
  98. <?xml version='1.0' encoding='UTF-8'?>
  99. <jabber>
  100. <chat jid='stpeter@jabber.org'/>
  101. </jabber>
  102. ]]></code>
  103. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for chatting with the JID defined in the file. If the user completes the interface, the helper application shall then send a message stanza of type='chat' as specified in <cite>XMPP IM</cite>, first authenticating with the user's Jabber/XMPP server if necessary.</p>
  104. </section2>
  105. <section2 topic='Subscribing to Presence' anchor='subscribe'>
  106. <code><![CDATA[
  107. <?xml version='1.0' encoding='UTF-8'?>
  108. <jabber>
  109. <subscribe jid='stpeter@jabber.org'/>
  110. </jabber>
  111. ]]></code>
  112. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for sending a presence subscription request to the JID defined in the file (e.g., specifying a name and/or group for the contact). If the user completes the interface, the helper application shall then send a presence stanza of type='subscribe' as specified in <cite>XMPP IM</cite>, first authenticating with the user's Jabber/XMPP server if necessary. The helper application SHOULD perform a "roster set" before sending the presence subscription request, as described in <cite>XMPP IM</cite>.</p>
  113. </section2>
  114. <section2 topic='Joining a Groupchat Room' anchor='groupchat'>
  115. <code><![CDATA[
  116. <?xml version='1.0' encoding='UTF-8'?>
  117. <jabber>
  118. <groupchat jid='jdev@conference.jabber.org'/>
  119. </jabber>
  120. ]]></code>
  121. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for joining the conference room associated with the JID defined in the file. If the user completes the interface, the helper application shall then send a directed presence stanza to the JID (appending a room nickname to the JID as the resource identifier) as described in &xep0045;, first authenticating with the user's Jabber/XMPP server if necessary.</p>
  122. </section2>
  123. <section2 topic='Registering with a Service' anchor='register'>
  124. <code><![CDATA[
  125. <?xml version='1.0' encoding='UTF-8'?>
  126. <jabber>
  127. <register jid='headlines.shakespeare.lit'/>
  128. </jabber>
  129. ]]></code>
  130. <p>The browser passes this file to the helper application, which shall send an IQ stanza of type='get' to the service associated with the JID defined in the file in order to determine the registration requirements (first authenticating with the user's Jabber/XMPP server if necessary), as described in &xep0077;. The helper application shall then instantiate an appropriate interface for registering with the service. If the user completes the interface, the helper application shall then send an IQ stanza of type='set' to the JID as described in <cite>XEP-0077</cite>.</p>
  131. </section2>
  132. <!--
  133. <section2 topic='Making a Service Discovery Request' anchor='disco'>
  134. <code><![CDATA[
  135. <?xml version='1.0' encoding='UTF-8'?>
  136. <jabber>
  137. <disco jid='shakespeare.lit'>
  138. <items/>
  139. <info/>
  140. </disco>
  141. </jabber>
  142. ]]></code>
  143. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for sending a service discovery request to the JID defined in the file.</p>
  144. </section2>
  145. <section2 topic='Searching a Directory' anchor='search'>
  146. <code><![CDATA[
  147. <?xml version='1.0' encoding='UTF-8'?>
  148. <jabber>
  149. <search jid='users.jabber.org'>
  150. <nick>stpeter</nick>
  151. </search>
  152. </jabber>
  153. ]]></code>
  154. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for searching the directory associated with the JID defined in the file, including pre-populated information as specified (e.g., nick, first name, last name).</p>
  155. </section2>
  156. <section2 topic='Requesting a vCard' anchor='vcard'>
  157. <code><![CDATA[
  158. <?xml version='1.0' encoding='UTF-8'?>
  159. <jabber>
  160. <vcard jid='stpeter@jabber.org'/>
  161. </jabber>
  162. ]]></code>
  163. <p>The browser passes this file to the helper application, which shall instantiate an appropriate interface for requesting the vCard of the JID defined in the file.</p>
  164. </section2>
  165. -->
  166. </section1>
  167. <!--
  168. <section1 topic='Authentication' anchor='auth'>
  169. <p>The solution should also enable a user to authenticate with a server using parameters defined in the file, e.g., for the purpose of single-sign-on (SSO).</p>
  170. <code><![CDATA[
  171. <connect>
  172. <host>somehost</host>
  173. <ip>10.1.1.1</ip>
  174. <port>5222</port>
  175. <ssl/>
  176. <authenticate>
  177. <username>foo</username>
  178. <password>test</password>
  179. <resource>Work</resource>
  180. </authenticate>
  181. </connect>
  182. ]]></code>
  183. <p>The username, password, and resource are not required if there is some other extension inside authenticate, that, e.g. does SSO. Authenticate is mostly useful only for these SSO situations, anyway. If the user is already connected, the application SHOULD ignore the &lt;connect/&gt; block.</p>
  184. </section1>
  185. -->
  186. <section1 topic='Security Considerations' anchor='security'>
  187. <p>Detailed security considerations for instant messaging and presence protocols are given in &rfc2779; (Sections 5.1 through 5.4), and for XMPP in particular are given in <cite>RFC 3920</cite> (Sections 12.1 through 12.6). In addition, all of the security considerations specified in <cite>RFC 3023</cite> apply to the "application/jabber+xml" media type.</p>
  188. <p>When a helper application has finished processing a file of type "application/jabber+xml", it SHOULD discard the file; this helps to prevent security-related problems that may result from HTTP caching.</p>
  189. </section1>
  190. <section1 topic='IANA Considerations' anchor='iana'>
  191. <p>This document requires registration of the "application/jabber+xml" content type with &IANA;. The registration is as follows:</p>
  192. <code><![CDATA[
  193. To: ietf-types@iana.org
  194. Subject: Registration of MIME media type application/jabber+xml
  195. MIME media type name: application
  196. MIME subtype name: jabber+xml
  197. Required parameters: (none)
  198. Optional parameters: (charset) Same as charset parameter of
  199. application/xml as specified in RFC 3023; per Section 11.5
  200. of RFC 3920, the charset must be UTF-8.
  201. Encoding considerations: Same as encoding considerations of
  202. application/xml as specified in RFC 3023; per Section 11.5
  203. of RFC 3920, the encoding must be UTF-8.
  204. Security considerations: All of the security considerations
  205. specified in RFC 3023 and RFC 3920 apply to this XML media
  206. type. Refer to Section 11 of XSF XEP-0081.
  207. Interoperability considerations: (none)
  208. Specification: XSF XEP-0081
  209. Applications which use this media type: non-XMPP applications
  210. (e.g., web browsers or email clients) that wish to invoke
  211. XMPP-compliant applications for instant messaging and
  212. presence functionality.
  213. Additional information: This media type is not to be confused
  214. with the "application/xmpp+xml" media type, which is for
  215. use by native XMPP applications.
  216. Person and email address to contact for further information:
  217. XMPP Registrar, <registrar@xmpp.org>
  218. Intended usage: COMMON
  219. Author/Change controller: XSF, XMPP Registrar
  220. ]]></code>
  221. </section1>
  222. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  223. <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
  224. <p>The &REGISTRAR; shall include 'http://jabber.org/protocol/mimetype' in its registry of protocol namespaces.</p>
  225. </section2>
  226. <section2 topic='IANA Interaction' anchor='registrar-iana'>
  227. <p>The XMPP Registrar shall interact with the IANA in order to register the media type defined herein.</p>
  228. </section2>
  229. </section1>
  230. <section1 topic='XML Schema' anchor='schema'>
  231. <code><![CDATA[
  232. <?xml version='1.0' encoding='UTF-8'?>
  233. <xs:schema
  234. xmlns:xs='http://www.w3.org/2001/XMLSchema'
  235. targetNamespace='http://jabber.org/protocol/mimetype'
  236. xmlns='http://jabber.org/protocol/mimetype'
  237. elementFormDefault='qualified'>
  238. <xs:element name='jabber'>
  239. <xs:complexType>
  240. <xs:choice>
  241. <xs:element name='chat' type='JabberAction'/>
  242. <xs:element name='groupchat' type='JabberAction'/>
  243. <xs:element name='message' type='JabberAction'/>
  244. <xs:element name='register' type='JabberAction'/>
  245. <xs:element name='subscribe' type='JabberAction'/>
  246. </xs:choice>
  247. </xs:complexType>
  248. </xs:element>
  249. <xs:complexType name='JabberAction'>
  250. <xs:restriction base='xs:string'>
  251. <xs:enumeration value=''/>
  252. </xs:restriction>
  253. <xs:attribute name='jid' use='required'>
  254. </xs:complexType>
  255. </xs:schema>
  256. ]]></code>
  257. </section1>
  258. <section1 topic='Open Issues'>
  259. <ol>
  260. <li>Add implementation notes for server MIME type registration and HTTP Content-Type output.</li>
  261. <li>Add implementation notes for client handling on various platforms (e.g., DDE messages in Windows).</li>
  262. </ol>
  263. </section1>
  264. </xep>