Update XEP-0298

Ported original changes from https://github.com/emcho/coin
Saúl Ibarra Corretgé 2015-07-01 00:10:40 +02:00 committed by Matthew A. Miller
parent 44b8c2cd1f
commit 4b3918acac
1 changed files with 36 additions and 19 deletions

View File

@ -16,7 +16,7 @@
<type>Standards Track</type>
@ -30,15 +30,27 @@
<jid>enrico@tilab.com </jid>
<firstname>Saúl Ibarra</firstname>
<remark><p>Correcting errors in grammar and examples; aligning closer to dependent specifications.</p></remark>
@ -74,8 +86,8 @@
<p>A conference participant exchanges Coin IQs only with the agent they
have established a session with. This means that it can also be used in
cases where only a subset of the users on a call are using XMPP while others
are connected via alternative mechanisms such as SIP's conference
package &rfc4575;</p>
are connected via alternative mechanisms such as SIP conferencing as defined
in &rfc4579;</p>
<section1 topic='Terminology' anchor='terms'>
@ -86,7 +98,9 @@
signalling and media. Other specifications refer to mixers and focus
agents as two distinct entities but we find this separation to be
unnecessary in the current specification and view both as a single logical
entity. This entity may be a person hosting the conference and doing the mixing
or a dedicated entity to which participants connect in order to establish a conference.
For the purposes of this specification, both scenarios are equivalent.</dd>
@ -97,12 +111,12 @@
<li>Provide a means for mixer agents in tightly coupled
conferences to advertise call and member state information to the call
<li>Reuse as much as possible the existing format and XML schema already
<li>Reuse the existing format and XML schema already
defined in <cite>RFC 4575</cite>.</li>
<li>Impose no requirements on agents joining the call other than those
necessary to establish a regular one-to-one call.</li>
<li>Allow straightforward interoperability with other conferencing
mechanisms such as <cite>RFC 4575</cite>; or &xep0272;</li>
mechanisms such as &rfc4579; or &xep0272;</li>
<section1 topic='How It Works' anchor='howitworks'>
@ -114,8 +128,8 @@
<p>Once in a call, call members and mixers can use Coin to exchange
<cite>RFC 4575</cite> conference information indicating what participants
<p>Once in a call, participants and mixers can use Coin to exchange
&rfc4575; conference information indicating what participants
are currently on the call and what their status is.</p>
<section1 topic='Creating a conference call' anchor='call-create'>
@ -138,7 +152,7 @@
<description xmlns='urn:xmpp:jingle:apps:stub:0'/>
<transport xmlns='urn:xmpp:jingle:transports:stub:0'/>
<conference-info isfocus='true'/>
<conference-info xmlns='urn:xmpp:coin:1' isfocus='true'/>
@ -164,6 +178,7 @@
<jingle xmlns='urn:xmpp:jingle:1' sid='a73sjjvkla37jfea'/>
<conference-info xmlns="urn:ietf:params:xml:ns:conference-info"
@ -203,10 +218,10 @@
<user entity="xmpp:juliet@capulet.lit" state="full">
<!-- ENDPOINTS -->
<endpoint entity="juliet@capulet.lit/balcony/orchard">
<endpoint entity="juliet@capulet.lit/balcony">
<display-text>Juliet's netbook</display-text>
@ -239,13 +254,15 @@
<p>The IQ message containing the conference info document MAY also contain a jingle element with the
session id attribute indicting the session to which the conference information refers to.</p>
<section1 topic='Determining Support' anchor='support'>
<p>If an entity supports Coin, it SHOULD advertise that fact by returning
a feature of "urn:xmpp:coin" in response to a &xep0030;
a feature of "urn:xmpp:coin:1" in response to a &xep0030;
information request.</p>
<example caption="Service Discovery Information Request"><![CDATA[
<iq from='kingclaudius@shakespeare.lit/castle'
@ -261,7 +278,7 @@
<query xmlns='http://jabber.org/protocol/disco#info'>
<feature var='urn:xmpp:coin'/>
<feature var='urn:xmpp:coin:1'/>
@ -294,14 +311,14 @@
The protocol documented by this schema is defined in
XEP-0XXX: http://www.xmpp.org/extensions/xep-0XXX.html
XEP-0298: http://www.xmpp.org/extensions/xep-0298.html
@ -329,7 +346,7 @@
The protocol documented by this schema is defined in
RFC 4575: http://tools.ietf.org/html/rfc4575 and reused by
XEP XXXX http://www.xmpp.org/extensions/xep-XXXX.html
XEP-0298 http://www.xmpp.org/extensions/xep-0298.html