diff --git a/xep-0298.xml b/xep-0298.xml index 866da81f..4c937c18 100644 --- a/xep-0298.xml +++ b/xep-0298.xml @@ -16,7 +16,7 @@ &LEGALNOTICE; 0298 - Deferred + Experimental Standards Track Standards Council @@ -30,15 +30,27 @@ Emil Ivov emcho@jitsi.org - emcho@sip-communicator.org + emcho@jit.si Enrico Marocco enrico.marocco@telecomitalia.it - enrico@tilab.com + enrico@tilab.com + + + Saúl Ibarra + Corretgé + saul@ag-projects.com + saul@ag-projects.com jingle + + 0.2 + 2015-07-02 + sic +

Correcting errors in grammar and examples; aligning closer to dependent specifications.

 + 0.1 2011-06-09 @@ -74,8 +86,8 @@

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;

+ are connected via alternative mechanisms such as SIP conferencing as defined + in &rfc4579;

@@ -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 + 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.
@@ -97,12 +111,12 @@
  • Provide a means for mixer agents in tightly coupled conferences to advertise call and member state information to the call participants.
    • -
  • Reuse as much as possible the existing format and XML schema already +
  • Reuse the existing format and XML schema already defined in RFC 4575.
  • Impose no requirements on agents joining the call other than those necessary to establish a regular one-to-one call.
  • Allow straightforward interoperability with other conferencing - mechanisms such as RFC 4575; or &xep0272;
    • + mechanisms such as &rfc4579; or &xep0272; @@ -114,8 +128,8 @@ accordingly.

    -

    Once in a call, call members and mixers can use Coin to exchange - RFC 4575 conference information indicating what participants +

    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.

     @@ -138,7 +152,7 @@ - + ]]> @@ -164,6 +178,7 @@ id='zid615d9' to='juliet@capulet.lit/balcony' type='set'> + - Romeo + Juliet - + Juliet's netbook connected @@ -239,13 +254,15 @@ ]]> +

    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.

    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.

    - + ]]> @@ -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