mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-21 23:28:51 -05:00
Editorial
This commit is contained in:
Steve Kille
parent
18ca8d4ad4
commit
c39dc20e96
79
xep-0408.xml
79
xep-0408.xml
@ -7,10 +7,10 @@
|
||||
<?xml-stylesheet type="text/css" href="xmpp.css"?>
|
||||
<xep>
|
||||
<header>
|
||||
<title>Mediated Information eXchange (MIX): C0-existence with MUC</title>
|
||||
<title>Mediated Information eXchange (MIX): Co-existence with MUC</title>
|
||||
<abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369. It specifies how MIX and MUC can be operated together. </abstract>
|
||||
&LEGALNOTICE;
|
||||
<number>0404</number>
|
||||
<number>0408</number>
|
||||
<status>Experimental</status>
|
||||
<type>Standards Track</type>
|
||||
<sig>Standards</sig>
|
||||
@ -37,7 +37,7 @@
|
||||
&skille;
|
||||
<revision>
|
||||
<version>0.1.0</version>
|
||||
<date>2018-05-14</date>
|
||||
<date>2018-05-21</date>
|
||||
<initials>sek</initials>
|
||||
<remark><p>
|
||||
Split out from MIX 0.10.0;
|
||||
@ -46,31 +46,36 @@
|
||||
|
||||
</header>
|
||||
<section1 topic='Introduction' anchor='intro'>
|
||||
<p>The Mediated Information eXchange (MIX) protocol framework and core capbilities are specified in &xep0369; (MIX-CORE).
|
||||
|
||||
<p>The Mediated Information eXchange (MIX) protocol framework and core capabilities are specified in &xep0369; (MIX-CORE).
|
||||
MIX can be used independently of &xep0045; (MUC).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
It may be desirable to operate a service that provides MIX and MUC together. This specification specifies three options for achieving this.
|
||||
</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Requirements' anchor='reqs'>
|
||||
|
||||
<p></p>
|
||||
|
||||
</section1>
|
||||
|
||||
|
||||
|
||||
<section1 topic="Supporting MIX and MUC together" anchor="mix-and-muc-together">
|
||||
<p>
|
||||
MIX is specified as a service that can be used independent of MUC and a MIX service MAY be implemented without MUC. If both MIX and MUC are implemented, three approaches are noted.
|
||||
If both MIX and MUC are implemented, three approaches are noted.
|
||||
</p>
|
||||
<ol>
|
||||
<li>Entirely separate MIX and MUC implementation, with MIX and MUC using separate domains and MIX channels being completely separate from MUC rooms.</li>
|
||||
<li>Fully integrated MIX and MUC implementation, with MIX and MUC sharing a single domain and rooms/channels equivalent.</li>
|
||||
<li>Partially integrated MIX and MUC implementation, with MIX and MUC using separate domains, but rooms/channel are common. This means that each MIX channel will have MUC room of the same name and same participants.</li>
|
||||
<li>Partially integrated MIX and MUC implementation, with MIX and MUC using separate domains, but all rooms/channel are common. This means that each MIX channel will have MUC room of the same name and same participants. </li>
|
||||
</ol>
|
||||
<p>The fully integrated approach would be transparent to clients. The following example shows how a MIX service that also supported MUC would respond:</p>
|
||||
<example caption="Service responds with Disco Info result showing MIX and MUC support" ><![CDATA[
|
||||
<p>The fully integrated approach would be transparent to clients. The following example shows how a service that supports MIX and MUC in a fully integrated manner would respond following the specification of MIX-CORE:</p>
|
||||
<example caption="Client uses Disco to show fully integrated MIX and MUC support" ><![CDATA[
|
||||
<iq from='hag66@shakespeare.example/UUID-c8y/1573'
|
||||
id='lx09df27'
|
||||
to='mix.shakespeare.example'
|
||||
type='get'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||
</iq>
|
||||
|
||||
<iq from='mix.shakespeare.example'
|
||||
id='lx09df27'
|
||||
to='hag66@shakespeare.example/UUID-c8y/1573'
|
||||
@ -80,20 +85,27 @@
|
||||
category='conference'
|
||||
name='Shakespearean Chat Service'
|
||||
type='text'/>
|
||||
<feature var='urn:xmpp:mix:1'/>
|
||||
<feature var='urn:xmpp:mix:core:0'/>
|
||||
<feature var='http://jabber.org/protocol/muc'/>
|
||||
<x xmlns='jabber:x:data' type='result'>
|
||||
<field var='FORM_TYPE' type='hidden'>
|
||||
<value>urn:xmpp:mix:1#serviceinfo</value>
|
||||
</field>
|
||||
</x>
|
||||
<feature var='urn:xmpp:mix:core:0#searchable'>
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>In the fully integrated service item discovery on the MIX/MUC service determines a list of channels. The protocol used for this is the same in MUC and MIX. Discovery actions on a channel in MIX MUST use 'node=mix' attribute in the discovery which will lead to the return of MIX channel specific information, as mandated for this discovery in MIX. If is not set, MUC room specific information is returned.
|
||||
<p>In the fully integrated service item discovery on the MIX/MUC service determines a list of channels. The protocol used for this is the same in MUC and MIX. Discovery actions on a channel in MIX MUST use 'node=mix' attribute in the discovery which will lead to the return of MIX channel specific information, as mandated for this discovery in MIX-CORE. If is not set, MUC room specific information is returned.
|
||||
</p>
|
||||
<p>For the partially integrated service, it will be useful for clients that support both MIX and MUC to be able to determine that the server supports both protocols. For a MIX client, it will be useful to know the MUC service, so that this information can be shared with a MUC client invitation. This information is provided by the initial service discovery:</p>
|
||||
<example caption="MIX Service responds with Disco Info result sharing MUC service location" ><![CDATA[
|
||||
<p>For the partially integrated service, MIX servers will reference the associated MUC server and MUC servers will reference the associated MIX service. This will allow a client that only support MUC or only supports MIX to find the right server if it is given a reference to the other one. For a client that supports both MUC and MIX, it will enable the client to select its preferred service.
|
||||
For a MIX client, it will also be useful to know the MUC service, so that this information can be shared with a MUC client invitation.
|
||||
The following example shows how a MIX server identifies the associated MUC server:
|
||||
|
||||
</p>
|
||||
<example caption="Client uses Disco to find MUC server assocated with MIX server" ><![CDATA[
|
||||
<iq from='hag66@shakespeare.example/UUID-c8y/1573'
|
||||
id='lx09df27'
|
||||
to='mix.shakespeare.example'
|
||||
type='get'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||
</iq>
|
||||
|
||||
<iq from='mix.shakespeare.example'
|
||||
id='lx09df27'
|
||||
to='hag66@shakespeare.example/UUID-c8y/1573'
|
||||
@ -106,7 +118,7 @@
|
||||
<feature var='urn:xmpp:mix:1'/>
|
||||
<x xmlns='jabber:x:data' type='result'>
|
||||
<field var='FORM_TYPE' type='hidden'>
|
||||
<value>urn:xmpp:mix:1#serviceinfo</value>
|
||||
<value>urn:xmpp:mix:muc:0#muc-mirror</value>
|
||||
</field>
|
||||
<field var='muc-mirror'
|
||||
type='jid-single'
|
||||
@ -117,9 +129,16 @@
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>The result is returned in an extended disco results in a form whose type value is 'urn:xmpp:mix:1#serviceinfo'. The field with var='muc-mirror' is the value of which is the mirrored MUC domain's JID. </p>
|
||||
<p>Where a client supporting both MIX and MUC is given a reference to a MUC room, it is desirable that the client can determine the MIX channel and join using MIX. This is achieved by an equivalent extension to MUC service discover.</p>
|
||||
<example caption="MUC Service responds with Disco Info result sharing MIX service location" ><![CDATA[
|
||||
<p>The result is returned in an extended disco results in a form whose type value is 'urn:xmpp:mix:muc:0#muc-mirror'. The field with var='muc-mirror' is the value of which is the mirrored MUC domain's JID. </p>
|
||||
<p>Similarly, a MUC service can advertise an associated MIX doming. The following example shows discovery of a MUC domain.</p>
|
||||
<example caption="Client uses Disco to find MIX server assocated with MUC server" ><![CDATA[
|
||||
<iq from='hag66@shakespeare.example/UUID-c8y/1573'
|
||||
id='lx09df27'
|
||||
to='mix.shakespeare.example'
|
||||
type='get'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||
</iq>
|
||||
|
||||
<iq from='chat.shakespeare.example'
|
||||
id='lx09df27'
|
||||
to='hag66@shakespeare.example/UUID-c8y/1573'
|
||||
@ -132,7 +151,7 @@
|
||||
<feature var='http://jabber.org/protocol/muc'/>
|
||||
<x xmlns='jabber:x:data' type='result'>
|
||||
<field var='FORM_TYPE' type='hidden'>
|
||||
<value>urn:xmpp:mix:1#serviceinfo</value>
|
||||
<value>urn:xmpp:mix:muc:0#mix-mirror</value>
|
||||
</field>
|
||||
<field var='mix-mirror'
|
||||
type='jid-single'
|
||||
@ -143,11 +162,11 @@
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>The result is returned in an extended disco results in a form whose type value is 'urn:xmpp:mix:1#serviceinfo'. The field with var='mix-mirror' is the value of which is the mirrored MIX domain's JID. </p>
|
||||
<p>The result is returned in an extended disco results in a form whose type value is 'urn:xmpp:mix:muc:0#mux-mirror'. The field with var='mix-mirror' is the value of which is the mirrored MIX domain's JID. </p>
|
||||
<section2 topic="Choosing Which Invite to Send" anchor="mix-muc-invite-choice">
|
||||
<p>
|
||||
Where a client supports MUC and MIX and has determined that for a channel that the server also supports a MUC room, the client has a choice as to which type of invite to send. This SHOULD be done by determining if the client support MIX using the mechanism specified in
|
||||
<link url='#mix-client-discovery'>Discovering Client MIX Capability</link>. If the client supports MIX a MIX invite SHOULD be sent.
|
||||
MIX-CORE. If the client supports MIX a MIX invite SHOULD be sent.
|
||||
</p>
|
||||
</section2>
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user