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-0282.xml 26KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666
  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>DMUC2: Distributed MUC</title>
  10. <abstract>Multi-User Chats, distributed over several nodes in the XMPP network, using a master/slave architecture</abstract>
  11. &LEGALNOTICE;
  12. <number>0282</number>
  13. <status>Deferred</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>NOT-YET-ASSIGNED</shortname>
  24. <author>
  25. <firstname>Carlo</firstname>
  26. <surname>von Loesch</surname>
  27. <jid>lynx@psyced.org</jid>
  28. </author>
  29. <author>
  30. <firstname>Philipp</firstname>
  31. <surname>Hancke</surname>
  32. <jid>fippo@ve.symlynx.com</jid>
  33. </author>
  34. <revision>
  35. <version>0.1</version>
  36. <date>2010-06-11</date>
  37. <initials>psa</initials>
  38. <remark><p>Initial published version.</p></remark>
  39. </revision>
  40. <revision>
  41. <version>0.0.1</version>
  42. <date>2010-03-15</date>
  43. <initials>cvl/ph</initials>
  44. <remark><p>First draft.</p></remark>
  45. </revision>
  46. </header>
  47. <section1 topic='Introduction' anchor='intro'>
  48. <p class='box'><em>This document is one of several proposals for distributing XMPP chat rooms across multiple chat services. It is expected that the various approaches will be refined and harmonized before a final protocol is developed.</em></p>
  49. <p>The architecture is that of a single root node, called MASTER and several repeater nodes, each called SLAVE. Every stanza is submitted via the slaves to the master, control is centralized there. The master then sends a copy of the stanza to each of the slaves where it is processed and then distributed to each of the slave's leaf nodes, local users at this point. During redistribution, the slave shall not change the stanza's 'from' attribute, which is only possible if the slave is in the same security domain as the user. The result of that is a decreased number of messages on the server-to-server links between the master's server and each of the slave servers.</p>
  50. <code><![CDATA[
  51. BigCheese ----> vesa.yeggmaex.irc ----> wallops MUC ----> killrc.oulubox.irc ----> Wumpus
  52. killrc.oulubox.irc ----> Phaedrus
  53. killrc.oulubox.irc ----> Valdis
  54. wallops MUC ----> eris.dclxvii.irc ----> WiZ
  55. eris.dclxvii.irc ----> Troy
  56. wallops MUC ----> vesa.yeggmaex.irc ----> BigCheese
  57. vesa.yeggmaex.irc ----> Efchen
  58. ]]></code>
  59. <p>Note that this only applies to stanzas that are directed to all occupants, such as the change of availability status and messages whose 'type' attribute is set to 'groupchat'.</p>
  60. <p>While 1-1 stanzas such as in-room private messages or vcard-temp requests may also travel along that path they are currently unaffected by this.</p>
  61. </section1>
  62. <section1 topic='Requirements' anchor='reqs'>
  63. <p>This specification addresses the following requirements:</p>
  64. <ul>
  65. <li>The existence of the slave shall be transparent for the user.</li>
  66. <li>Enable detection of connection loss.</li>
  67. <li>Enable occupants to remain in instance of the conference if connectivity is lost to other instances.</li>
  68. <li>Enable occupants to leave a chatroom while connectivity is lost.</li>
  69. <li>Enable syncing of history and room rosters on reconnect.</li>
  70. <li>Improve distribution of 'broadcast' stanzas'.</li>
  71. </ul>
  72. </section1>
  73. <section1 topic='Terminology' anchor='terms'>
  74. <!--
  75. <section2 topic='General Terms' anchor='terms-general'>
  76. <dl>
  77. <di>
  78. <dt>Master</dt>
  79. <dd></dd>
  80. </di>
  81. <di>
  82. <dt>Slave</dt>
  83. <dd></dd>
  84. </di>
  85. <di>
  86. <dt>Netsplit</dt>
  87. <dd></dd>
  88. </di>
  89. <di>
  90. <dt>CASTMSG</dt>
  91. <dd>wut? you don't need this</dd>
  92. </di>
  93. <di>
  94. <dt>ENTER</dt>
  95. <dd>?</dd>
  96. </di>
  97. <di>
  98. <dt>LEAVE</dt>
  99. <dd>?</dd>
  100. </di>
  101. </dl>
  102. </section2>
  103. -->
  104. <section2 topic='Dramatis Personae' anchor='terms-personae'>
  105. <p>Most of the examples in this document use the scenario of the 1990 war that split the <cite>Internet Relay Chat</cite> into several incompatible networks. The battlefield is represented here by the "wallops@channel.avalon.irc" chatroom. The characters are as follows:</p>
  106. <table caption='Dramatis Personae'>
  107. <tr>
  108. <th>Room Nickname</th>
  109. <th>Full JID</th>
  110. <th>Role</th>
  111. </tr>
  112. <tr>
  113. <td>Wumpus</td>
  114. <td>argl@killrc.oulubox.irc/laptop</td>
  115. <td>Moderator</td>
  116. </tr>
  117. <tr>
  118. <td>Valdis</td>
  119. <td>valdis@killrc.oulubox.irc/desktop</td>
  120. <td>Participant</td>
  121. </tr>
  122. <tr>
  123. <td>Phaedrus</td>
  124. <td>phaedrus@killrc.oulubox.irc/phone</td>
  125. <td>Participant</td>
  126. </tr>
  127. <tr>
  128. <td>WiZ</td>
  129. <td>squit@eris.dclxvii.irc/jupiter</td>
  130. <td>Moderator</td>
  131. </tr>
  132. <tr>
  133. <td>Troy</td>
  134. <td>troy@eris.dclxvii.irc/screwdriver</td>
  135. <td>Moderator</td>
  136. </tr>
  137. <tr>
  138. <td>BigCheese</td>
  139. <td>rubenro@vesa.yeggmaex.irc/shaver</td>
  140. <td>Participant</td>
  141. </tr>
  142. <tr>
  143. <td>Efchen</td>
  144. <td>msa@vesa.yeggmaex.irc/bicycle</td>
  145. <td>Participant</td>
  146. </tr>
  147. </table>
  148. <p>In our example we are presuming that three slaves from three hosts have registered with the master for traffic redistribution. They are doing so using slave@host jids, but they could be using any temporary jid the implementor finds useful to choose.</p>
  149. </section2>
  150. </section1>
  151. <section1 topic='MASTER/SLAVE Protocol' anchor='masterslave'>
  152. <p>This section describes the protocol between the master and the slaves, the interaction between each slave and its users are described in the next section.</p>
  153. <!--
  154. <section2 topic='Narrative Protocol Description'>
  155. <p>some blabla</p>
  156. </section2>
  157. -->
  158. <section2 topic='Slave Requirements'>
  159. <p>The slave</p>
  160. <ul>
  161. <li>must be able to intercept any stanzas sent to the masters jid,</li>
  162. <li>must be able to verify if a local user has sent directed presence to the masters jid,</li>
  163. <li>must store room roster,</li>
  164. <li>must store local room roster</li>
  165. <li>must store room history (if desired by master)</li>
  166. </ul>
  167. </section2>
  168. <section2 topic='Creating a Slave'>
  169. <p>to follow</p>
  170. <p>Might include things like negotiation of keepalive frequency and amount of room might be useful to set some things like keepalive frequency, keeping/storing room history etc.</p>
  171. <!--
  172. <p>maxstanzas / maxbytes attribute</p>
  173. <p>PARANOIA: why should the slave let the master create the slave and send room roster and history?</p>
  174. -->
  175. </section2>
  176. <section2 topic='Initial Room Roster'>
  177. <p>After the creation of a new slave, the master must send the room roster (which at that time only consists of remote participants) to the slave:</p>
  178. <example caption="Master Sends Room Roster to Slave"><![CDATA[
  179. <presence
  180. from='wallops@channel.avalon.irc/Wumpus'
  181. to='slave@vesa.yeggmaex.irc'>
  182. <x xmlns='http://jabber.org/protocol/muc#user'>
  183. <item affiliation='owner' role='moderator'/>
  184. </x>
  185. </presence>
  186. <presence
  187. from='wallops@channel.avalon.irc/Valdis'
  188. to='slave@vesa.yeggmaex.irc'>
  189. <x xmlns='http://jabber.org/protocol/muc#user'>
  190. <item affiliation='none' role='participant'/>
  191. </x>
  192. </presence>
  193. <presence
  194. from='wallops@channel.avalon.irc/Phaedrus'
  195. to='slave@vesa.yeggmaex.irc'>
  196. <x xmlns='http://jabber.org/protocol/muc#user'>
  197. <item affiliation='none' role='participant'/>
  198. </x>
  199. </presence>
  200. <presence
  201. from='wallops@channel.avalon.irc/WiZ'
  202. to='slave@vesa.yeggmaex.irc'>
  203. <x xmlns='http://jabber.org/protocol/muc#user'>
  204. <item affiliation='admin' role='moderator'/>
  205. </x>
  206. </presence>
  207. <presence
  208. from='wallops@channel.avalon.irc/Troy'
  209. to='slave@vesa.yeggmaex.irc'>
  210. <x xmlns='http://jabber.org/protocol/muc#user'>
  211. <item affiliation='participant' role='moderator'/>
  212. </x>
  213. </presence>]]></example>
  214. <!--
  215. <p>Tricky: if this does not contain the full jid, the (initial) presence information sent to moderators that join later will not be possible... mh!</p>
  216. -->
  217. </section2>
  218. <section2 topic='Initial Room History'>
  219. <p>After the creation of a new slave, the master MAY also send the discussion history to the slave. The slave shall store this and deliver it to entering participants.</p>
  220. <p>from=masterjid to=slavejid?</p>
  221. </section2>
  222. <section2 topic='ENTER'>
  223. <p>If a new occupant requests to enter the room, the master first sends a presence update to all participants to inform them of the presence of the new user. Then, the master sends the affected slave a stanza requesting it to add the user to the distribution list</p>
  224. <example caption="Master informs Slave of New Occupant"><![CDATA[
  225. <presence
  226. from='wallops@channel.avalon.irc/BigCheese'
  227. to='slave@vesa.yeggmaex.irc'>
  228. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  229. <enter jid='rubenro@vesa.yeggmaex.irc/shaver'/>
  230. <history maxstanzas='20'/>
  231. </x>
  232. ...
  233. </presence>]]></example>
  234. <p>The slave MUST verify that the user has sent directed presence to the masters JID before. This helps to ensure that the user intended to enter the room. If this is ture, the slave shall add the user to the distribution list and send the room roster, occupants own presence in room and discussion history to the full jid of the added user.</p>
  235. </section2>
  236. <section2 topic='LEAVE'>
  237. <p>If an occupant sends an unavailable presence to the room, the master sends the affected slave a stanza requesting it to remove the user from the distribution list.</p>
  238. <example caption="Master informs Slave of Occupant's Departure"><![CDATA[
  239. <presence
  240. from='wallops@channel.avalon.irc/BigCheese'
  241. to='slave@vesa.yeggmaex.irc'
  242. type='unavailable'>
  243. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  244. <leave jid='rubenro@vesa.yeggmaex.irc/shaver'/>
  245. </x>
  246. ...
  247. </presence>]]></example>
  248. <p>The slave removes user and forwards the stanza to user.</p>
  249. <p>The master then sends a presence update to all slaves to announce the occupants departure.</p>
  250. </section2>
  251. <section2 topic='Presence Update'>
  252. <p>Presence updates are distributed by the master to all slaves.</p>
  253. <example caption="Master sends presence update"><![CDATA[
  254. <presence
  255. from='wallops@channel.avalon.irc/BigCheese'
  256. to='slave@killrc.oulubox.irc'>
  257. <x xmlns='http://jabber.org/protocol/muc#user'>
  258. <item affiliation='none'
  259. jid='rubenro@vesa.yeggmaex.irc/shaver'
  260. role='participant'/>
  261. </x>
  262. ...
  263. </presence>
  264. <presence
  265. from='wallops@channel.avalon.irc/BigCheese'
  266. to='slave@eris.dclxvii.irc'>
  267. <x xmlns='http://jabber.org/protocol/muc#user'>
  268. <item affiliation='none'
  269. jid='rubenro@vesa.yeggmaex.irc/shaver'
  270. role='participant'/>
  271. </x>
  272. ...
  273. </presence>
  274. <presence
  275. from='wallops@channel.avalon.irc/BigCheese'
  276. to='slave@vesa.yeggmaex.irc'>
  277. ...
  278. </presence>]]></example>
  279. <p>Note that the master MUST NOT send the full jid of the user to any slaves without members that are moderators.</p>
  280. <p>When rebroadcasting this stanza to its local occupants, the slave MUST remove the participants full JID subject to the rules of XEP-0045. In addition, the slave stores the resulting changes to the room roster, so that it can send the correct state to entering users.</p>
  281. </section2>
  282. <section2 topic='Slave Forwards Stanza to Master'>
  283. <p>The slave may relay messages from local users to the master. When doing so, it MUST NOT modify the stanzas 'from' attribute but MUST retain the original address of the sender.</p>
  284. <!--
  285. <p>Die Regel ist relativ einfach... from=fulljid to=masterjid/undevtlresource</p>
  286. <p>fulljid deshalb, damit der master nicht checken muss ob der jeweilige user auf dem slave ist und ausserdem der jeweilige user nicht zwangsläufig im Raum sein muss...</p>
  287. <p>Beispiele: message submit, presence update, privatchat innerhalb raum, vcard avatar get</p>
  288. -->
  289. <example caption="Slave Relays a Message to the Master"><![CDATA[
  290. <message
  291. from='rubenro@vesa.yeggmaex.irc/shaver'
  292. to='wallops@channel.avalon.irc'
  293. type='groupchat'>
  294. <body>Phaedrus, we're all having a truly rotten time.</body>
  295. </message>]]></example>
  296. <!--
  297. <p>Some rules:</p>
  298. <ul>
  299. <li>The stanzas 'from' attribute MUST be retained.</li>
  300. <li>Stanzas from participants and non-participants must be routed</li>
  301. </ul>
  302. -->
  303. </section2>
  304. <section2 topic='Message Broadcast'>
  305. <p>When relaying a message, the master SHOULD add a urn:xmpp:delay element inside dmuc element so that the slave can provide proper timestamps to new users. The master then sends a copy of the stanza to each slave.</p>
  306. <example caption="Message from Master to all Slaves"><![CDATA[
  307. <message
  308. from='wallops@channel.avalon.irc/BigCheese'
  309. to='slave@killrc.oulubox.irc'
  310. type='groupchat'>
  311. <body>Phaedrus, we're all having a truly rotten time.</body>
  312. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  313. <delay xmlns='urn:xmpp:delay'
  314. from='wallops@channel.avalon.irc/BigCheese'
  315. stamp='1990-10-13T23:58:37Z'/>
  316. </x>
  317. </message>
  318. <message
  319. from='wallops@channel.avalon.irc/BigCheese'
  320. to='slave@eris.dclxvii.irc'
  321. type='groupchat'>
  322. <body>Phaedrus, we're all having a truly rotten time.</body>
  323. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  324. <delay xmlns='urn:xmpp:delay'
  325. from='wallops@channel.avalon.irc/BigCheese'
  326. stamp='1990-10-13T23:58:37Z'/>
  327. </x>
  328. </message>
  329. <message
  330. from='wallops@channel.avalon.irc/BigCheese'
  331. to='slave@vesa.yeggmaex.irc'
  332. type='groupchat'>
  333. <body>Phaedrus, we're all having a truly rotten time.</body>
  334. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  335. <delay xmlns='urn:xmpp:delay'
  336. from='wallops@channel.avalon.irc/BigCheese'
  337. stamp='1990-10-13T23:58:37Z'/>
  338. </x>
  339. </message>]]></example>
  340. <p>After saving the stanza for the purpose of keeping a room history, the slave SHOULD remove the urn:xmpp:tmp:dmuc:0 element and send the stanza to each local user.</p>
  341. </section2>
  342. <section2 topic='Master-Slave Keepalive'>
  343. <p>To ensure a working connecting, the master SHOULD send an XMPP Ping stanza to each slave if there has been no traffic for a certain amount of time.</p>
  344. <p>Likewise, each slave should ping the master if there has been no traffic for more than the usual amount of time.</p>
  345. </section2>
  346. <section2 topic='Netsplit' anchor='netsplit'>
  347. <section3 topic='Netsplit Detection' anchor='netsplit-detect'>
  348. <p>A 'lost connection' can be detected by either slave or master when a stanza sent to the master or a slave respectively bounced.</p>
  349. <section4 topic='At the Master'>
  350. <p>If the master receives a stanza with type=error from the slave JID, it MUST:</p>
  351. <ul>
  352. <li>mark the slave as 'split', making sure that any further broadcasts are not sent to the affected slave</li>
  353. <li>start sending pings to the slave with a higher frequency to get a timely notification if the slave reappears</li>
  354. <li>resync when the slave reappears as described below</li>
  355. </ul>
  356. <p>In addition, the master MAY send a presence update for each user on the affected slave, marking them as away.</p>
  357. </section4>
  358. <section4 topic='At the Slave'>
  359. <p>If the slave receives a stanza with type=error from the master's JID, it MUST:</p>
  360. <ul>
  361. <li>stop submitting messages to the master</li>
  362. <li>react to people sending presence updates or leaving the room and broadcast those changes to local users</li>
  363. </ul>
  364. <p>In addition, the slave MAY (and be careful when using this):</p>
  365. <ul>
  366. <li>enable local participants to continue their in-room conversation with other local participants</li>
  367. <li>enable local participants to continue 1-1 messaging in the context of a room (such as private chat or vcard retrieval)</li>
  368. <li>enable local users to enter the room (DANGER!!!)</li>
  369. <li>enable moderators (as designated by the master) to kick participants</li>
  370. <li>mark non-local users as away</li>
  371. </ul>
  372. </section4>
  373. </section3>
  374. <section3 topic='Netjoin' anchor='netjoin'>
  375. <p>to follow</p>
  376. </section3>
  377. </section2>
  378. </section1>
  379. <section1 topic='Use-Cases' anchor='Uses-Cases'>
  380. <p>This section narratively describes the master-slave protocol in context with client interactions.</p>
  381. <section2 topic='Entering a Room' anchor='enter'>
  382. <p>The user seeks to enter the wallops chatroom with the room nickname BigCheese:</p>
  383. <example caption="User Seeks to Enter Room"><![CDATA[
  384. <presence
  385. from='rubenro@vesa.yeggmaex.irc/shaver'
  386. to='wallops@channel.avalon.irc/BigCheese'>
  387. <x xmlns='http://jabber.org/protocol/muc'/>
  388. </presence>]]></example>
  389. <p>The master sends the presence update to each slave to inform the current occupants of BigCheese's arrival:</p>
  390. <example caption="Master Sends Presence Update to all Slaves"><![CDATA[
  391. <presence
  392. from='wallops@channel.avalon.irc/BigCheese'
  393. to='slave@killrc.oulubox.irc'>
  394. <x xmlns='http://jabber.org/protocol/muc#user'>
  395. <item affiliation='none'
  396. jid='rubenro@vesa.yeggmaex.irc/shaver'
  397. role='participant'/>
  398. </x>
  399. ...
  400. </presence>
  401. <presence
  402. from='wallops@channel.avalon.irc/BigCheese'
  403. to='slave@eris.dclxvii.irc'>
  404. <x xmlns='http://jabber.org/protocol/muc#user'>
  405. <item affiliation='none'
  406. jid='rubenro@vesa.yeggmaex.irc/shaver'
  407. role='participant'/>
  408. </x>
  409. ...
  410. </presence>
  411. <presence
  412. from='wallops@channel.avalon.irc/BigCheese'
  413. to='slave@vesa.yeggmaex.irc'>
  414. ...
  415. </presence>]]></example>
  416. <p>Each slave then distributes this presence update:</p>
  417. <example caption="Slaves Distribute Presence Update to Users - killrc Slave"><![CDATA[
  418. <presence
  419. from='wallops@channel.avalon.irc/BigCheese'
  420. to='argl@killrc.oulubox.irc/laptop'>
  421. <x xmlns='http://jabber.org/protocol/muc#user'>
  422. <item affiliation='none'
  423. jid='rubenro@vesa.yeggmaex.irc/shaver'
  424. role='participant'/>
  425. </x>
  426. ...
  427. </presence>
  428. <presence
  429. from='wallops@channel.avalon.irc/BigCheese'
  430. to='valdis@killrc.oulubox.irc/desktop'>
  431. ...
  432. </presence>
  433. <presence
  434. from='wallops@channel.avalon.irc/BigCheese'
  435. to='phaedrus@killrc.oulubox.irc/phone'>
  436. ...
  437. </presence>]]></example>
  438. <example caption="Slaves Distribute Presence Update to Users - eris Slave"><![CDATA[
  439. <presence
  440. from='wallops@channel.avalon.irc/WiZ'
  441. to='squit@eris.dclxvii.irc/jupiter'>
  442. <x xmlns='http://jabber.org/protocol/muc#user'>
  443. <item affiliation='none'
  444. jid='rubenro@vesa.yeggmaex.irc/shaver'
  445. role='participant'/>
  446. </x>
  447. ...
  448. </presence>
  449. <presence
  450. from='wallops@channel.avalon.irc/WiZ'
  451. to='troy@eris.dclxvii.irc/screwdriver'>
  452. <x xmlns='http://jabber.org/protocol/muc#user'>
  453. <item affiliation='none'
  454. jid='rubenro@vesa.yeggmaex.irc/shaver'
  455. role='participant'/>
  456. </x>
  457. ...
  458. </presence>]]></example>
  459. <example caption="Slaves Distribute Presence Update to Users - vesa Slave"><![CDATA[
  460. <presence
  461. from='wallops@channel.avalon.irc/BigCheese'
  462. to='rubenro@vesa.yeggmaex.irc/shaver'>
  463. ...
  464. </presence>]]></example>
  465. <p>The master then informs the slave of the entered user about a new occupant:</p>
  466. <example caption="Master Informs Slave of New Occupant"><![CDATA[
  467. <presence
  468. from='wallops@channel.avalon.irc/BigCheese'
  469. to='slave@vesa.yeggmaex.irc'>
  470. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  471. <enter jid='rubenro@vesa.yeggmaex.irc/shaver'/>
  472. </x>
  473. ...
  474. </presence>]]></example>
  475. <p>The slave sends presence from existing occupants to new occupant:</p>
  476. <example caption='Slave Sends Presence from Existing Occupants to New Occupant'><![CDATA[
  477. <presence
  478. from='wallops@channel.avalon.irc/Wumpus'
  479. to='rubenro@vesa.yeggmaex.irc/shaver'>
  480. <x xmlns='http://jabber.org/protocol/muc#user'>
  481. <item affiliation='owner' role='moderator'/>
  482. </x>
  483. </presence>
  484. <presence
  485. from='wallops@channel.avalon.irc/Valdis'
  486. to='rubenro@vesa.yeggmaex.irc/shaver'>
  487. <x xmlns='http://jabber.org/protocol/muc#user'>
  488. <item affiliation='none' role='participant'/>
  489. </x>
  490. </presence>
  491. <presence
  492. from='wallops@channel.avalon.irc/Phaedrus'
  493. to='rubenro@vesa.yeggmaex.irc/shaver'>
  494. <x xmlns='http://jabber.org/protocol/muc#user'>
  495. <item affiliation='none' role='participant'/>
  496. </x>
  497. </presence>
  498. <presence
  499. from='wallops@channel.avalon.irc/WiZ'
  500. to='rubenro@vesa.yeggmaex.irc/shaver'>
  501. <x xmlns='http://jabber.org/protocol/muc#user'>
  502. <item affiliation='admin' role='moderator'/>
  503. </x>
  504. </presence>
  505. <presence
  506. from='wallops@channel.avalon.irc/Troy'
  507. to='rubenro@vesa.yeggmaex.irc/shaver'>
  508. <x xmlns='http://jabber.org/protocol/muc#user'>
  509. <item affiliation='participant' role='moderator'/>
  510. </x>
  511. </presence>
  512. <presence
  513. from='wallops@channel.avalon.irc/Efchen'
  514. to='rubenro@vesa.yeggmaex.irc/shaver'>
  515. <x xmlns='http://jabber.org/protocol/muc#user'>
  516. <item affiliation='none' role='participant'/>
  517. </x>
  518. </presence>]]></example>
  519. <p>and concludes the room roster by sending the new occupant's presence to the new occupant:</p>
  520. <example caption="Slave Sends New Occupant's Presence to New Occupant"><![CDATA[
  521. <presence
  522. from='wallops@channel.avalon.irc/BigCheese'
  523. to='rubenro@vesa.yeggmaex.irc/shaver'
  524. ...
  525. </presence>]]></example>
  526. <p>After that, the slave will send the discussion history to the new occupant:</p>
  527. <example caption='Slave Sends Discussion History to New Occupant'><![CDATA[
  528. <message from='wallops@channel.avalon.irc/Trillian'
  529. to='rubenro@vesa.yeggmaex.irc/shaver'
  530. type='groupchat'>
  531. <body>Honest! He did!!</body>
  532. <delay xmlns='urn:xmpp:delay'
  533. from='wallops@channel.avalon.irc/Trillian'
  534. stamp='1990-01-23T19:50:01Z'/>
  535. </message>
  536. <message from='wallops@channel.avalon.irc/BlondeBoy'
  537. to='rubenro@vesa.yeggmaex.irc/shaver'
  538. type='groupchat'>
  539. <body>Was that absolutely necessary????????</body>
  540. <delay xmlns='urn:xmpp:delay'
  541. from='wallops@channel.avalon.irc/BlondeBoy'
  542. stamp='1990-01-23T19:50:30Z'/>
  543. </message>
  544. <message from='wallops@channel.avalon.irc/DCLXVI'
  545. to='rubenro@vesa.yeggmaex.irc/shaver'
  546. type='groupchat'>
  547. <body>SUUUUUUURE he did</body>
  548. <delay xmlns='urn:xmpp:delay'
  549. from='wallops@channel.avalon.irc/DCLXVI'
  550. stamp='1990-01-23T19:50:51Z'/>
  551. </message>
  552. <message from='wallops@channel.avalon.irc/Cerebus'
  553. to='rubenro@vesa.yeggmaex.irc/shaver'
  554. type='groupchat'>
  555. <body>He did. really truly he did.</body>
  556. <delay xmlns='urn:xmpp:delay'
  557. from='wallops@channel.avalon.irc/Cerebus'
  558. stamp='1990-01-23T19:51:20Z'/>
  559. </message>
  560. ]]></example>
  561. </section2>
  562. <section2 topic='Sending a Message to All Occupants' anchor='msg'>
  563. <example caption="Occupant Sends a Message to All Occupants"><![CDATA[
  564. <message
  565. from='rubenro@vesa.yeggmaex.irc/shaver'
  566. to='wallops@channel.avalon.irc'
  567. type='groupchat'>
  568. <body>Phaedrus, we're all having a truly rotten time.</body>
  569. </message>]]></example>
  570. <p>The master will broadcast this message to all slaves:</p>
  571. <example caption="Master Distributes Message to all Slaves"><![CDATA[
  572. <message
  573. from='wallops@channel.avalon.irc/BigCheese'
  574. to='slave@killrc.oulubox.irc'
  575. type='groupchat'>
  576. <body>Phaedrus, we're all having a truly rotten time.</body>
  577. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  578. <delay xmlns='urn:xmpp:delay'
  579. from='wallops@channel.avalon.irc/BigCheese'
  580. stamp='1990-10-13T23:58:37Z'/>
  581. </x>
  582. </message>
  583. <message
  584. from='wallops@channel.avalon.irc/BigCheese'
  585. to='slave@eris.dclxvii.irc'
  586. type='groupchat'>
  587. <body>Phaedrus, we're all having a truly rotten time.</body>
  588. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  589. <delay xmlns='urn:xmpp:delay'
  590. from='wallops@channel.avalon.irc/BigCheese'
  591. stamp='1990-10-13T23:58:37Z'/>
  592. </x>
  593. </message>
  594. <message
  595. from='wallops@channel.avalon.irc/BigCheese'
  596. to='slave@vesa.yeggmaex.irc'
  597. type='groupchat'>
  598. <body>Phaedrus, we're all having a truly rotten time.</body>
  599. <x xmlns='urn:xmpp:tmp:dmuc:0'>
  600. <delay xmlns='urn:xmpp:delay'
  601. from='wallops@channel.avalon.irc/BigCheese'
  602. stamp='1990-10-13T23:58:37Z'/>
  603. </x>
  604. </message>]]></example>
  605. <p>And each slave distributes to local occupants</p>
  606. <example caption="Slave Distributes Message to Occupants - killrc Slave"><![CDATA[
  607. <message
  608. from='wallops@channel.avalon.irc/BigCheese'
  609. to='argl@killrc.oulubox.irc/laptop'
  610. type='groupchat'>
  611. <body>Phaedrus, we're all having a truly rotten time.</body>
  612. </message>
  613. <message
  614. from='wallops@channel.avalon.irc/BigCheese'
  615. to='valdis@killrc.oulubox.irc/desktop'
  616. type='groupchat'>
  617. <body>Phaedrus, we're all having a truly rotten time.</body>
  618. </message>
  619. <message
  620. from='wallops@channel.avalon.irc/BigCheese'
  621. to='phaedrus@killrc.oulubox.irc/phone'
  622. type='groupchat'>
  623. <body>Phaedrus, we're all having a truly rotten time.</body>
  624. </message>]]></example>
  625. <example caption="Slave Distributes Message to Occupants - eris Slave"><![CDATA[
  626. <message
  627. from='wallops@channel.avalon.irc/BigCheese'
  628. to='squit@eris.dclxvii.irc/jupiter'
  629. type='groupchat'>
  630. <body>Phaedrus, we're all having a truly rotten time.</body>
  631. </message>
  632. <message
  633. from='wallops@channel.avalon.irc/BigCheese'
  634. to='troy@eris.dclxvii.irc/screwdriver'
  635. type='groupchat'>
  636. <body>Phaedrus, we're all having a truly rotten time.</body>
  637. </message>]]></example>
  638. <example caption="Slave Distributes Message to Occupants - vesa Slave"><![CDATA[
  639. <message
  640. from='wallops@channel.avalon.irc/BigCheese'
  641. to='rubenro@vesa.yeggmaex.irc/shaver'
  642. type='groupchat'>
  643. <body>Phaedrus, we're all having a truly rotten time.</body>
  644. </message>
  645. <message
  646. from='wallops@channel.avalon.irc/BigCheese'
  647. to='msa@vesa.yeggmaex.irc/bicycle'
  648. type='groupchat'>
  649. <body>Phaedrus, we're all having a truly rotten time.</body>
  650. </message>]]></example>
  651. </section2>
  652. </section1>
  653. <section1 topic='Security Considerations' anchor='security'>
  654. <p>to follow</p>
  655. <p>Careful with channel overtakes :-)</p>
  656. </section1>
  657. <section1 topic='IANA Considerations' anchor='iana'>
  658. <p>This document requires no interaction with &IANA;.</p>
  659. </section1>
  660. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  661. <p>This document requires no interaction with the &REGISTRAR;.</p>
  662. </section1>
  663. <section1 topic='XML Schema' anchor='schema'>
  664. <p>to follow</p>
  665. </section1>
  666. </xep>