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-0249.xml 11KB

  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>Direct MUC Invitations</title>
  10. <abstract>This specification defines a method for inviting a contact to a multi-user chat room directly, instead of sending the invitation through the chat room.</abstract>
  12. <number>0249</number>
  13. <status>Draft</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XEP-0045</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>x-conference</shortname>
  24. <schemaloc>
  25. <url></url>
  26. </schemaloc>
  27. &stpeter;
  28. <revision>
  29. <version>1.2</version>
  30. <date>2011-09-22</date>
  31. <initials>psa</initials>
  32. <remark><p>Added continue and thread attributes for feature parity with mediated invitations when converting a one-to-one chat to a groupchat.</p></remark>
  33. </revision>
  34. <revision>
  35. <version>1.1</version>
  36. <date>2009-12-07</date>
  37. <initials>psa</initials>
  38. <remark><p>Added password attribute for feature parity with mediated invitations.</p></remark>
  39. </revision>
  40. <revision>
  41. <version>1.0</version>
  42. <date>2009-06-25</date>
  43. <initials>psa</initials>
  44. <remark><p>Per a vote of the XMPP Council, advanced specification from Experimental to Draft.</p></remark>
  45. </revision>
  46. <revision>
  47. <version>0.3</version>
  48. <date>2009-06-22</date>
  49. <initials>psa</initials>
  50. <remark><p>Defined several possible security attacks along with solutions.</p></remark>
  51. </revision>
  52. <revision>
  53. <version>0.2</version>
  54. <date>2009-03-30</date>
  55. <initials>psa</initials>
  56. <remark><p>Added optional reason attribute for feature parity with XEP-0045.</p></remark>
  57. </revision>
  58. <revision>
  59. <version>0.1</version>
  60. <date>2008-09-03</date>
  61. <initials>psa</initials>
  62. <remark><p>Initial published version.</p></remark>
  63. </revision>
  64. <revision>
  65. <version>0.0.5</version>
  66. <date>2008-09-02</date>
  67. <initials>psa</initials>
  68. <remark><p>Modified to use old jabber:x:conference namespace.</p></remark>
  69. </revision>
  70. <revision>
  71. <version>0.0.4</version>
  72. <date>2008-08-18</date>
  73. <initials>psa</initials>
  74. <remark><p>Added note about handling multiple invitations.</p></remark>
  75. </revision>
  76. <revision>
  77. <version>0.0.3</version>
  78. <date>2008-08-16</date>
  79. <initials>psa</initials>
  80. <remark><p>Added implementation note about members-only rooms.</p></remark>
  81. </revision>
  82. <revision>
  83. <version>0.0.2</version>
  84. <date>2008-08-14</date>
  85. <initials>psa</initials>
  86. <remark><p>Changed venue element to conference element.</p></remark>
  87. </revision>
  88. <revision>
  89. <version>0.0.1</version>
  90. <date>2008-08-12</date>
  91. <initials>psa</initials>
  92. <remark><p>First draft.</p></remark>
  93. </revision>
  94. </header>
  95. <section1 topic='Introduction' anchor='intro'>
  96. <p>&xep0045; defines a protocol for groupchat over XMPP. That specification includes a method for inviting a contact to a room, where the invitation is mediated by the room itself: the user sends the invitation to the room, which in turn sends it to the contact. Unfortunately, a mediated invitation might not be delivered to the contact, for example if the contact blocks communication with entities not in its roster as specified in &xep0016;. As privacy lists have become more common, MUC invitations have been increasingly blocked at the server side, resulting in an undesirable user experience. Therefore, this specification defines a method for sending an invitation directly from the user to the contact, which re-uses the original 'jabber:x:conference' namespace in use before <cite>XEP-0045</cite> was written (with the addition of 'reason', 'continue', and 'thread' attributes for feature parity with mediated invitations).</p>
  97. </section1>
  98. <section1 topic='How It Works' anchor='howitworks'>
  99. <p>A user invites a contact to a room by sending a &MESSAGE; stanza containing only an &lt;x/&gt; element qualified by the 'jabber:x:conference' namespace.</p>
  100. <example caption="A direct invitation"><![CDATA[
  101. <message
  102. from='crone1@shakespeare.lit/desktop'
  103. to='hecate@shakespeare.lit'>
  104. <x xmlns='jabber:x:conference'
  105. jid='darkcave@macbeth.shakespeare.lit'
  106. password='cauldronburn'
  107. reason='Hey Hecate, this is the place for all good witches!'/>
  108. </message>
  109. ]]></example>
  110. <p>The 'jid' attribute, which is REQUIRED, specifies the address of the groupchat room to be joined.</p>
  111. <p>The 'password' attribute, which is OPTIONAL, specifies a password needed for entry into a password-protected room and maps to the &lt;password/&gt; element in a mediated invitation.</p>
  112. <p>The 'reason' attribute, which is OPTIONAL, specifies a human-readable purpose for the invitation and maps to the &lt;reason/&gt; element in a mediated invitation.</p>
  113. <p>The 'continue' and 'thread' attributes, which are OPTIONAL, specify that the groupchat room continues a one-to-one chat having the designated thread; these map to the &lt;continue/&gt; element (with 'thread' attribute) in a mediated invitation. Note that the 'continue' attribute has a datatype of boolean. &BOOLEANNOTE;</p>
  114. <example caption="A direct invitation that continues a one-to-one chat"><![CDATA[
  115. <message
  116. from='crone1@shakespeare.lit/desktop'
  117. to='hecate@shakespeare.lit'>
  118. <x xmlns='jabber:x:conference'
  119. continue='true'
  120. jid='darkcave@macbeth.shakespeare.lit'
  121. password='cauldronburn'
  122. reason='Hey Hecate, this is the place for all good witches!'
  123. thread='e0ffe42b28561960c6b12b944a092794b9683a38'/>
  124. </message>
  125. ]]></example>
  126. <p>Upon receiving a direct invitation, the contact's client SHOULD present the invitation to the contact so that the contact can accept it or decline it. If the contact accepts the invitation, the contact's client shall join the room as described in <cite>XEP-0045</cite>. If the contact declines the invitation, it shall silently discard the invitation.</p>
  127. </section1>
  128. <section1 topic='Determining Support' anchor='support'>
  129. <p>If an entity supports the protocol specified herein, it MUST advertise that fact by returning a feature of "jabber:x:conference" in response to &xep0030; information requests &NSNOTE;.</p>
  130. <example caption="Service discovery information request"><![CDATA[
  131. <iq from='crone1@shakespeare.lit/desktop'
  132. id='disco1'
  133. to='hecate@shakespeare.lit/broom'
  134. type='get'>
  135. <query xmlns=''/>
  136. </iq>
  137. ]]></example>
  138. <example caption="Service discovery information response"><![CDATA[
  139. <iq from='hecate@shakespeare.lit/broom'
  140. id='disco1'
  141. to='crone1@shakespeare.lit/desktop'
  142. type='result'>
  143. <query xmlns=''>
  144. <feature var='jabber:x:conference'/>
  145. </query>
  146. </iq>
  147. ]]></example>
  148. <p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
  149. </section1>
  150. <section1 topic='Implementation Notes' anchor='impl'>
  151. <p>Before inviting a contact to a members-only room, a user SHOULD check to see if the contact is already a member and, if not, add the contact to the member list (or ask a room administrator to do so).</p>
  152. <p>If a client receives multiple invitations to the same room (e.g., a mediated invitation as defined in <cite>XEP-0045</cite> and a direct invitation as defined here), the client SHOULD present only one of the invitations to a human user. If a client receives an invitation to a room in which the user is already an occupant, the client SHOULD silently discard the invitation.</p>
  153. </section1>
  154. <section1 topic='Security Considerations' anchor='security'>
  155. <p>The following attacks are possible, in roughly the order of probability. See also &xep0205; and &rfc3552;.</p>
  156. <ol>
  157. <li><p>The sender of an invitation could overload the 'reason' attribute with malicious or offensive text. The recipient can mitigate this attack by blocking the sender using technologies such as &xep0016; and &xep0191;.</p></li>
  158. <li><p>A passive attacker could flood the recipient with a large number of chatroom invitations. This attack, too, can be mitigated with <cite>Privacy Lists</cite> or <cite>Simple Communications Blocking</cite>.</p></li>
  159. <li><p>A passive attacker could use a mimicked JID to fool the recipient into thinking that the sender is a known or trusted contact. This attack requires knowledge of the recipient's known or trusted contacts, and can be mitigated by following the recommendations in &xep0165;.</p></li>
  160. <li><p>In the absence of end-to-end encryption, a passive attacker could eavesdrop on the chatroom invitations that a user sends or receives. This is especially threatening if the invitation includes a 'password' attribute for a password-protected room.</p></li>
  161. <li><p>In the absence of end-to-end encryption or signing, an active attacker could modify the invitation in transit so that the recipient is directed to a different room than intended by the sender.</p></li>
  162. </ol>
  163. </section1>
  164. <section1 topic='IANA Considerations' anchor='iana'>
  165. <p>This document requires no interaction with &IANA;.</p>
  166. </section1>
  167. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  168. <section2 topic='Protocol Namespaces' anchor='ns'>
  169. <p>The &REGISTRAR; includes 'jabber:x:conference' in its registry of protocol namespaces at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
  170. </section2>
  171. </section1>
  172. <section1 topic='XML Schema' anchor='schema'>
  173. <code><![CDATA[
  174. <?xml version='1.0' encoding='UTF-8'?>
  175. <xs:schema
  176. xmlns:xs=''
  177. targetNamespace='jabber:x:conference'
  178. xmlns='jabber:x:conference'
  179. elementFormDefault='qualified'>
  180. <xs:annotation>
  181. <xs:documentation>
  182. The protocol documented by this schema is defined in
  183. XEP-0249:
  184. </xs:documentation>
  185. </xs:annotation>
  186. <xs:element name='x'>
  187. <xs:complexType>
  188. <xs:simpleContent>
  189. <xs:extension base='empty'>
  190. <xs:attribute
  191. name='continue'
  192. type='xs:boolean'
  193. use='optional'/>
  194. <xs:attribute
  195. name='jid'
  196. type='xs:string'
  197. use='required'/>
  198. <xs:attribute
  199. name='password'
  200. type='xs:string'
  201. use='optional'/>
  202. <xs:attribute
  203. name='reason'
  204. type='xs:string'
  205. use='optional'/>
  206. <xs:attribute
  207. name='thread'
  208. type='xs:string'
  209. use='optional'/>
  210. </xs:extension>
  211. </xs:simpleContent>
  212. </xs:complexType>
  213. </xs:element>
  214. <xs:simpleType name='empty'>
  215. <xs:restriction base='xs:string'>
  216. <xs:enumeration value=''/>
  217. </xs:restriction>
  218. </xs:simpleType>
  219. </xs:schema>
  220. ]]></code>
  221. </section1>
  222. <section1 topic='Acknowledgements' anchor='ack'>
  223. <p>Thanks to Joe Hildebrand for his feedback.</p>
  224. </section1>
  225. </xep>