diff --git a/xep-0166.xml b/xep-0166.xml index 399f975a..1e69530c 100644 --- a/xep-0166.xml +++ b/xep-0166.xml @@ -26,6 +26,20 @@ &robmcqueen; &seanegan; &hildjj; + + 0.30 + 2008-09-23 + ram/psa + + + + 0.29 2008-07-31 @@ -300,19 +314,19 @@ Romeo Juliet |---------------------------->| | | ]]> -

Naturally, more complex scenarios are probable; such scenarios are described in other specifications, such as XEP-0167 for voice chat.

-

The simplest flow might happen as follows. The example is that of a file transfer offer, where the transport method is &xep0065;.

+

Naturally, more complex scenarios are possible; such scenarios are described in other specifications, such as XEP-0167 for voice chat.

+

The simplest flow might happen as follows. The example is that of a voice chat offer, where the transport method is &xep0176;.

- + action='session-initiate' initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + @@ -320,7 +334,7 @@ Romeo Juliet - + @@ -338,17 +352,17 @@ Romeo Juliet id='accept1' to='romeo@montague.net/orchard' type='set'> - - + - + ]]>

The initiator and responder would then exchange media using any of the acceptable codecs.

-

Eventually, one of the parties (here the responder) can terminate the sessio.

+

Eventually, one of the parties (here the responder) will terminate the session.

- @@ -405,16 +419,16 @@ Romeo Juliet
  • Make it possible to manage a wide variety of peer-to-peer sessions (including but not limited to voice and video) within XMPP.
  • When a peer-to-peer connection cannot be negotiated, make it possible to fall back to relayed communications.
  • Clearly separate the signalling channel (XMPP) from the data channel.
    • -
  • Clearly separate the application formats (e.g., video) from the transport methods (e.g., RTP).
    • -
  • Make it possible to add, modify, and remove both application types and transport methods in relation to an existing session.
    • +
  • Clearly separate the application formats (e.g., audio) from the transport methods (e.g., RTP).
    • +
  • Make it possible to add, modify, and remove both application types and transport methods in an existing session.
  • Make it relatively easy to implement support for the protocol in standard Jabber/XMPP clients.
  • Where communication with non-XMPP entities is needed, push as much complexity as possible onto server-side gateways between the XMPP network and the non-XMPP network.

    • This document defines the signalling protocol only. Additional documents specify the following:

      -

    • Various application formats (audio, video, etc.) and, where possible, mapping of those types to the Session Description Protocol (SDP; see &rfc4566;); examples include Jingle RTP Sessions and Jingle Video via RTP.

      • -

    • Various transport methods; examples include &xep0176; and Raw UDP Transport.

      • -

    • Procedures for mapping the Jingle signalling protocol to existing signalling standards such as the IETF's Session Initiation Protocol (SIP) and the ITU's H.323 protocol (see &h323;); these documents are forthcoming.

      • +

    • Various application formats (audio, video, etc.) and, where possible, mapping of those types to the Session Description Protocol (SDP; see &rfc4566;); examples include Jingle RTP Sessions and &xep0234;.

      • +

    • Various transport methods; examples include Jingle ICE-UDP Transport and &xep0177;.

      • +

    • Procedures for mapping the Jingle signalling protocol to existing signalling standards such as the IETF's Session Initiation Protocol (SIP) and the ITU's H.323 protocol (see &h323;); see for example &xmppsipmedia;.

    @@ -430,7 +444,7 @@ Romeo Juliet Component - A numbered stream of data that needs to be transmitted between the endpoints for a given content type in the context of a given session. It is up to the transport to negotiate the details of each component. Depending on the content type, multiple components may be needed (e.g., two components might be needed, one to transmit an RTP stream and another to transmit RTCP timing information). + A numbered stream of data that needs to be transmitted between the endpoints for a given content type in the context of a given session. It is up to the transport to negotiate the details of each component. Depending on the content type, multiple components might be needed (e.g., one to transmit an RTP stream and another to transmit RTCP timing information). Content Type @@ -438,7 +452,7 @@ Romeo Juliet Session - One or more content types negotiated between two entities. It is delimited in time by an initiate request and session ending events. During the lifetime of a session, content types can be added or removed. A session consists of at least one content type at a time. + One or more content types negotiated between two entities. It is delimited in time by a session-initiate action and a session-terminate action. During the lifetime of a session, content types can be added or removed. A session consists of at least one content type at a time. Transport Method @@ -450,7 +464,7 @@ Romeo Juliet

    In diagrams, the following conventions are used:

    • Dashed lines (---) represent Jingle stanzas that are sent via the XMPP signalling channel.
      • -
    • Double-dashed lines (===) represent media packets that are sent via the non-XMPP media channel.
      • +
    • Double-dashed lines (===) represent media packets that are sent via the media channel, which typically is not an XMPP channel but a direct or mediated channel between the endpoints.
     @@ -464,15 +478,15 @@ Romeo Juliet

    This document defines the semantics and syntax for overall session management. It also provides pluggable "slots" for application formats and transport methods, which are specified in separate documents.

    At the most basic level, the process for initial negotiation of a Jingle session is as follows (i.e., the actions that can be generated during the PENDING state):

      -
    1. One user (the "initator") sends to another user (the "responder") a session request with at least one content definition.
      2. +
    2. One user (the "initiator") sends to another user (the "responder") a session initiation request with at least one content definition.
    3. If the responder wants to proceed, it acknowledges the session initiation request by sending an IQ result.
      4. -
    4. The parties attempt to set up data transmission over the designated transport method as defined in the relevant specification (e.g., this can involve sending multiple transport-info actions).
      5. -
    5. Optionally, the responder can remove content definitions via the content-remove action or change the direction of the media flow via the content-modify action.
      6. +
    6. The parties attempt to set up data transmission over the designated transport method as defined in the relevant specification.
      7. +
    7. Optionally, either party can add or remove content definitions, or change the direction of the media flow.
    8. Optionally, either party can send session-info actions (to inform the other party that it is attempting transport negotiation, that its device is ringing, etc.).
    9. As soon as the responder determines that data can flow over the designated transport, it sends to the initiator a session-accept action.
    10. The parties start sending data over the transport.
    -

    After the initial session negotiation has been completed and the session is in the ACTIVE state, the parties can adjust the session definition. This can involve sending the content-modify, content-remove, content-add, and transport-replace actions. In addition, certain transport methods allow continued sending of transport-info actions while in the ACTIVE state. And naturally the parties may send session-info actions at any time.

    +

    After the initial session negotiation has been completed and the session is in the ACTIVE state, the parties can adjust the session definition by sending the content-modify, content-remove, content-add, and transport-replace actions. In addition, certain transport methods allow continued sending of transport-info actions while in the ACTIVE state. And naturally the parties can send session-info actions at any time.

    The state machine for overall session management (i.e., the state per Session ID) is as follows:

    @@ -484,11 +498,12 @@ Romeo Juliet |/ | PENDING o----------------------+ | | | content-accept, | | + | | content-add, | | | | content-modify, | | | | content-remove, | | | | session-info, | | - | | transport-accept | | - | | transport-info | | + | | transport-accept, | | + | | transport-info, | | | | transport-replace | | | +-------------------+ | | | @@ -500,8 +515,8 @@ PENDING o----------------------+ | | | content-modify, | | | | content-remove, | | | | session-info, | | - | | transport-accept | | - | | transport-info | | + | | transport-accept, | | + | | transport-info, | | | | transport-replace | | | +-------------------+ | | | @@ -511,83 +526,46 @@ PENDING o----------------------+ | | o ENDED -

    There are three overall session states:

    +

    As shown, there are three overall session states:

    1. PENDING
    2. ACTIVE
    3. ENDED
    -

    The actions related to management of the overall Jingle session are described in the following table.

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ActionDescription
    content-acceptAccept a content-add action received from another party.
    content-addAdd one or more new content definitions to the session. The sender MUST specify only the added content definition(s), not the added content definition(s) plus the existing content definition(s). Therefore it is the responsibility of the recipient to maintain a local copy of the current content definition(s). This action MUST NOT be sent while the session is in the PENDING state. If the recipient wishes to include the new content definition in the session, it MUST send a content-accept action to the other party. In the event that a session contains two unidirectional streams of the same definition because a content-add was issued simultaneously by both parties, it is RECOMMENDED that participants close the duplicate stream in favor of that created by the session initiator, which should be made bidirectional via a content-modify action sent by the responder.
    content-modifyChange the direction of an existing content definition thorugh modification of the 'senders' attribute. If the recipient deems the directionality of a content-modify action to be unacceptable, it MAY reply with a contrary content-modify action, terminate the session, or simply refuse to send or accept application data in the new direction. In any case, the recipient MUST NOT send a content-accept action in response to the content-modify. If both parties send content-modify actions at the same time, the content-modify from the session initiator MUST trump the content-modify from the recipient and the initiator SHOULD return an &unexpected; error to the other party.
    content-removeRemove one or more content definitions from the session. The sender MUST specify only the removed content definition(s), not the removed content definition(s) plus the remaining content definition(s). Therefore it is the responsibility of the recipient to maintain a local copy of the current content definition(s). Upon receiving a content-remove from the other party, the recipient MUST NOT send a content-accept and MUST NOT continue to negotiate the transport method related to that content definition or send application data related to that content definition. The recipient MUST NOT send a content-accept in response to a content-remove. A client MUST NOT return an error upon receipt of a 'content-remove' action for a content definition that is received after a 'content-remove' action has been sent but before the action has been acknowledged by the peer. If the content-remove results in zero content definitions for the session, the entity that receives the content-remove SHOULD send a session-terminate action to the other party (since a session with no content definitions is void).
    session-acceptDefinitively accept a session negotiation (implicitly this action also serves as a content-accept).
    session-infoSend session-level information, such as (for Jingle RTP sessions) a ringing message.
    session-initiateRequest negotiation of a new Jingle session.
    session-terminateEnd an existing session.
    transport-acceptAccept a transport-replace action received from another party.
    transport-infoExchange transport candidates; it is mainly used in XEP-0176 but may be used in other transport specifications.
    transport-replaceRedefine a transport method.
    +

    The actions related to management of the overall Jingle session are as follows (detailed definitions are provided in under Action Attribute).

    +
      +
    • content-accept -- Accept a content-add action received from another party.
      • +
    • content-add -- Add one or more new content definitions to the session.
      • +
    • content-modify -- Change the directionality of media sending.
      • +
    • content-remove -- Remove one or more content definitions from the session.
      • +
    • session-accept -- Definitively accept a session negotiation.
      • +
    • session-info -- Send session-level information, such as a ringing message.
      • +
    • session-initiate -- Request negotiation of a new Jingle session.
      • +
    • session-terminate -- End an existing session.
      • +
    • transport-accept -- Accept a transport-replace action received from another party.
      • +
    • transport-info -- Exchange transport candidates.
      • +
    • transport-replace -- Redefine a transport method.
      • +

    This section defines the high-level flow of a Jingle session. More detailed descriptions are provided in the specifications for Jingle application formats and transport methods.

    -

    In order to initiate a Jingle session, the initiator must determine which of the responder's XMPP resources is best for the desired application format. Methods for doing so are out of scope for this specification. However, see the Determining Support section of this document (and associated specifications) for relevant information.

    +

    In order to initiate a Jingle session, the initiator needs to determine which of the responder's XMPP resources is best for the desired application format. Methods for doing so are out of scope for this specification. However, see the Determining Support section of this document (and associated specifications) for relevant information.

     -

    Once the initiator has discovered which of the responder's XMPP resources is ideal for the desired application format, it sends a session initiation request to the responder. This request is an IQ-set containing a &JINGLE; element qualified by the 'urn:xmpp:tmp:jingle' namespace &NSNOTE;, where the value of the 'action' attribute is "session-initiate" and where the &JINGLE; element contains one or more &CONTENT; elements. Each &CONTENT; element defines a content type to be transferred during the session, and each &CONTENT; element in turn contains one &DESCRIPTION; child element that specifies a desired application format and one &TRANSPORT; child element that specifies a potential transport method. If either party wishes to propose the use of multiple transport methods for the same application format, it must send multiple &CONTENT; elements.

    +

    Once the initiator has discovered which of the responder's XMPP resources is ideal for the desired application format, it sends a session initiation request to the responder. This request is an IQ-set containing a &JINGLE; element qualified by the 'urn:xmpp:jingle:0' namespace &VNOTE;, where the value of the 'action' attribute is "session-initiate" and where the &JINGLE; element contains one or more &CONTENT; elements. Each &CONTENT; element defines a content type to be transferred during the session, and each &CONTENT; element in turn contains one &DESCRIPTION; child element that specifies a desired application format and one &TRANSPORT; child element that specifies a potential transport method. If either party wishes to propose the use of multiple transport methods for the same application format, it MUST include multiple &CONTENT; elements.

    - + action='session-initiate' initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + @@ -595,13 +573,13 @@ PENDING o----------------------+ | - + ]]> -

    Note: The syntax and semantics of the &DESCRIPTION; and &TRANSPORT; elements are out of scope for this specification, since they are defined in related specifications. The syntax and semantics of the &JINGLE; and &CONTENT; elements are specified in this document under Formal Definition.

    -

    Note: In order to expedite session establishment, the initiator MAY send transport candidates (e.g., for negotiation of the ICE transport) immediately after sending the session-initiate action and before receiving acknowledgement from the responder (i.e., the initiator MUST consider the session to be PENDING even before receiving acknowledgement). Given in-order delivery, the responder should receive such transport-info actions after receiving the session-initiate action (if not, it is appropriate for the responder to return <unknown-session/> errors since according to its state machine the session does not exist).

    +

    Note: The syntax and semantics of the &DESCRIPTION; and &TRANSPORT; elements are out of scope for this document, since they are defined in related specifications. The syntax and semantics of the &JINGLE; and &CONTENT; elements are specified in this document under Formal Definition.

    +

    Note: In order to expedite session establishment, the initiator MAY send transport candidates (e.g., for negotiation of the ICE transport) immediately after sending the session-initiate action and before receiving acknowledgement from the responder (i.e., the initiator MUST consider the session to be PENDING even before receiving acknowledgement). Given in-order delivery in accordance with &xmppcore;, the responder will receive such transport-info actions after receiving the session-initiate action (if not, it is appropriate for the responder to return <unknown-session/> errors since according to its state machine the session does not exist).

    - + ]]> @@ -623,8 +601,7 @@ PENDING o----------------------+ | to='romeo@montague.net/orchard' type='result'/> ]]>     -

    However, after acknowledging the session initiation request, the responder may subsequently determine that it cannot proceed with negotiation of the session (e.g., because it does not support any of the offered application formats or transport methods, because a human user is busy or unable to accept the session, because a human user wishes to formally decline the session, etc.). In these cases, the responder SHOULD immediately acknowledge the session initiation request but then terminate the session with an appropriate reason as described in the Termination section of this document.

    -

    If the responder acknowledges receipt of the initation request, both parties must consider the session to be in the PENDING state.

    +

    However, after acknowledging the session initiation request, the responder might subsequently determine that it cannot proceed with negotiation of the session (e.g., because it does not support any of the offered application formats or transport methods, because a human user is busy or unable to accept the session, because a human user wishes to formally decline the session, etc.). In these cases, the responder SHOULD immediately acknowledge the session initiation request but then terminate the session with an appropriate reason as described in the Termination section of this document.

    There are several reasons why the responder might immediately return an error instead of acknowledging receipt of the initiation request:

    @@ -635,7 +612,7 @@ PENDING o----------------------+ |
  • The responder does not have sufficient resources to participate in a session.
  • The initiation request was malformed.
    • -

    If the initiator is unknown to the responder (e.g., via presence subscription as defined in &rfc3921; or stanza session negotiation as defined in &xep0155;) and the responder has a policy of not communicating via Jingle with unknown entities, it SHOULD return a &unavailable; error.

    +

    If the initiator is unknown to the responder (e.g., via presence subscription as defined in &rfc3921; or stanza session negotiation as defined in &xep0155;) and the responder has a policy of not communicating via Jingle with unknown entities, it MUST return a &unavailable; error.

    ]]> -

    If the responder wishes to redirect the request to another address, it SHOULD return a &redirect; error.

    +

    If the responder wishes to redirect the request to another address, it MUST return a &redirect; error.

    - voicemail@capulet.lit + xmpp:voicemail@capulet.lit ]]> -

    If the responder does not have sufficient resources to participate in a session, it SHOULD return a &constraint; error.

    +

    If the responder does not have sufficient resources to participate in a session, it MUST return a &constraint; error.

    Exchanging particular transport candidates via the transport-info action.
  • Modifying the communication direction for a content type via the content-modify action.
  • Changing the definition of a content type via the transport-replace action (typically to fall back to a more suitable transport).
    • -
  • Adding a content type via the content-add action (not allowed in the PENDING state).
    • -
  • Removing a content type via the content-remove action (not allowed in the PENDING state).
    • +
  • Adding a content type via the content-add action.
    • +
  • Removing a content type via the content-remove action.

    • If (after negotiation of transport methods and application formats as well as checking of transport candidates) the responder determines that it will be able to establish a connection, it sends a definitive acceptance to the initiator.

    -

    Note: In the session-accept stanza, the &JINGLE; element MUST contain one or more <content/> elements, each of which MUST contain one <description/> element and one <transport/> element. The &JINGLE; element SHOULD possess a 'responder' attribute that explicitly specifies the full JID of the responding entity; after sending acknowledgement of the session-accept, the initiator SHOULD send all future commmunications about this Jingle session to the JID provided in the 'responder' attribute and note the new JID in the user interface.

    -

    The initiator then acknowledges the responder's definitive acceptance, after which the parties can exchange media over the negotiated connection.

    -

    If one of the parties cannot find a suitable transport method or candidate, it SHOULD terminate the session as described below.

    -     - -

    Once a session is in the ACTIVE state, it may be modified via a content-add, content-modify, content-remove, or transport-info action. Examples of such modifications are shown in the specifications for various application formats and transport methods.

    -     - -

    In order to gracefully end the session (which MAY be done at any point after acknowledging receipt of the initiation request, including immediately thereafter in order to decline the request), either the responder or the initiator MUST send a session-terminate action to the other party.

    -

    The party that terminates the session SHOULD include a <reason/> element that specifies why the session is being terminated. Examples follow.

    -

    One reason for terminating the session is that the terminating party is busy; in this case, the recommended condition is "busy".

    - - - + - + - ]]> -

    And the initiator acknowledges session acceptance:

    - +

    The initiator then acknowledges the responder's definitive acceptance, after which the parties can exchange media over the negotiated connection.

    + - ]]> -

    The initiator and responder would then exchange media using any of the acceptable codecs.

    -

    Eventually, one of the parties (here the responder) can terminate the sessio.

    - +

    If one of the parties cannot find a suitable transport method or candidate, it SHOULD terminate the session as described below.

    +     + +

    Once a session is in the ACTIVE state, it might be modified via a content-add, content-modify, content-remove, or transport-info action. Examples of such modifications are shown in the specifications for various application formats and transport methods.

    +     + +

    In order to gracefully end the session (which can be done at any point after acknowledging receipt of the initiation request, including immediately thereafter in order to decline the request), either the responder or the initiator MUST send a session-terminate action to the other party.

    +

    The party that terminates the session SHOULD include a <reason/> element that specifies why the session is being terminated. Examples follow.

    +

    One reason for terminating the session is that the terminating party is busy; in this case, the recommended condition is "busy".

    + - @@ -776,10 +750,10 @@ PENDING o----------------------+ |

    Another reason for terminating the session is that the terminating party wishes to formally decline the session; in this case, the recommended condition is "decline".

    - @@ -791,10 +765,10 @@ PENDING o----------------------+ |

    Another reason for terminating the session is that the terminating party already has an existing session with the other party and wishes to use that session rather than initiate a new session; in this case, the recommended condition is "alternative-session" and the terminating party SHOULD include the session ID of the atlernative session in the <sid/> element.

    - @@ -808,10 +782,10 @@ PENDING o----------------------+ |

    Another reason for terminating the session is that the terminating party does not support any of the offered application formats; in this case, the recommended condition is "unsupported-applications".

    - @@ -823,10 +797,10 @@ PENDING o----------------------+ |

    Another reason for terminating the session is that the terminating party does not support any of the offered transport methods; in this case, the recommended condition is "unsupported-transports".

    - @@ -840,7 +814,7 @@ PENDING o----------------------+ | + type='result'/> ]]>

    Note: As soon as an entity sends a session-terminate action, it MUST consider the session to be in the ENDED state (even before receiving acknowledgement from the other party). If the terminating entity receives additional Jingle-related IQ-sets from the other party after sending the session-terminate action, it MUST reply with an <unknown-session/> error.

    Unfortunately, not all sessions end gracefully. In applications of Jingle that also involve the exchange of presence information, receipt of &UNAVAILABLE; from the other party MAY be considered a session-ending event. However, in this case there is nothing for the party to acknowledge.

    @@ -852,28 +826,44 @@ PENDING o----------------------+ | id='ringing1' to='romeo@montague.net/orchard' type='set'> - - + ]]>     -

    An informational message MUST be an IQ-set containing a &JINGLE; element whose 'action' attribute is set to a value of "session-info" or "transport-info"; the &JINGLE; element MUST further contain a payload child element (specific to the session or to a transport method) that specifies the information being communicated. If the party that receives an informational message does not understand the payload, it MUST return a &feature; error with a Jingle-specific error condition of <unsupported-info/>.

    +

    An informational message MUST be an IQ-set containing a &JINGLE; element whose 'action' attribute is set to a value of "session-info" or "transport-info"; the &JINGLE; element SHOULD further contain a payload child element (specific to the application format or transport method) that specifies the information being communicated. If the party that receives an informational message does not understand the payload, it MUST return a &feature; error with a Jingle-specific error condition of <unsupported-info/>.

    - + ]]> -

    If either party receives an empty session-info action for an active session, it MUST send an empty IQ result; this way, an empty session-info action may be used as a "ping" to determine session vitality.

    -

    Informational messages are specific to a particular application type or transport method and therefore are described in specifications other than this one.

    +

    However, the &JINGLE; element associated with a session-info action MAY be empty. If either party receives an empty session-info action for an active session, it MUST send an empty IQ result; this usage functions as a "ping" to determine session vitality.

    + + + + ]]> + + ]]>     @@ -889,17 +879,17 @@ PENDING o----------------------+ | action - A Jingle action as listed in this document (e.g., "session-terminate"). + A Jingle action as described under Action Attribute. REQUIRED initiator - The full JID of the entity that has initiated the session flow (which may be different from the 'from' address on the IQ-set). + The full JID of the entity that has initiated the session flow (which can be different from the 'from' address on the IQ-set). REQUIRED responder - The full JID of the entity that has replied to the initiation, which may be different from the 'to' address on the IQ-set. + The full JID of the entity that has replied to the initiation, which can be different from the 'to' address on the IQ-set. RECOMMENDED @@ -909,6 +899,45 @@ PENDING o----------------------+ | + +

    The value of the 'action' attribute SHOULD be one of the following. If an entity receives a value not defined here, it SHOULD ignore attribute and SHOULD return a &badrequest; error to the sender.

    + +

    The content-accept action is used to accept a content-add action received from another party.

    +     + +

    The content-add action is used to add one or more new content definitions to the session. The sender MUST specify only the added content definition(s), not the added content definition(s) plus the existing content definition(s). Therefore it is the responsibility of the recipient to maintain a local copy of the current content definition(s). If the recipient wishes to include the new content definition in the session, it MUST send a content-accept action to the other party.

    +     + +

    The content-modify action is used to change the direction of an existing content definition thorugh modification of the 'senders' attribute. If the recipient deems the directionality of a content-modify action to be unacceptable, it MAY reply with a contrary content-modify action, terminate the session, or simply refuse to send or accept application data in the new direction. In any case, the recipient MUST NOT send a content-accept action in response to the content-modify.

    +     + +

    The content-remove action is used to remove one or more content definitions from the session. The sender MUST specify only the removed content definition(s), not the removed content definition(s) plus the remaining content definition(s). Therefore it is the responsibility of the recipient to maintain a local copy of the current content definition(s). Upon receiving a content-remove from the other party, the recipient MUST NOT send a content-accept and MUST NOT continue to negotiate the transport method related to that content definition or send application data related to that content definition. If the content-remove results in zero content definitions for the session, the entity that receives the content-remove SHOULD send a session-terminate action to the other party (since a session with no content definitions is void).

    +     + +

    The session-accept action is used to definitively accept a session negotiation (implicitly this action also serves as a content-accept). A session-accept action indicates acceptance only of the content definition(s) included in the session-initiate, not any content definition(s) subsequently added during the PENDING state. In the session-accept stanza, the &JINGLE; element MUST contain one or more <content/> elements, each of which MUST contain one <description/> element and one <transport/> element. The &JINGLE; element SHOULD possess a 'responder' attribute that explicitly specifies the full JID of the responding entity; after sending acknowledgement of the session-accept, the initiator SHOULD send all future commmunications about this Jingle session to the JID provided in the 'responder' attribute and note the new JID in the user interface.

    +     + +

    The session-info action is used to send session-level information, such as (for Jingle RTP sessions) a ringing message.

    +     + +

    The session-initiate action is used to request negotiation of a new Jingle session.

    +     + +

    The session-terminate action is used to end an existing session.

    +     + +

    The transport-accept action is used to accept a transport-replace action received from another party.

    +     + +

    The transport-info action is used to exchange transport candidates; it is mainly used in XEP-0176 but might be used in other transport specifications.

    +     + +

    The transport-replace action is used to redefine a transport method.

    +     + +

    It is possible that two instances of certain actions can be sent at the same time in the context of an existing session, one by each party; for example, both parties might simulaneously attempt to send a content-add, content-modify, or content-remove action. In all such cases, the action sent by the initiator MUST overrule the action sent by the responder; i.e., both parties MUST accept the action sent by the initiator and the initiator MUST return an &unexpected; error to the responder for the duplicate action.

    +     +

    The attributes of the &CONTENT; element are as follows.

    @@ -919,17 +948,17 @@ PENDING o----------------------+ | - + - + - +
    creatorWhich party originally generated the content type (used to prevent race conditions regarding modifications).Which party originally generated the content type (used to prevent race conditions regarding modifications); the defined values are "initiator" and "responder" (where the default is "initiator"). REQUIRED
    nameA unique name or identifier for the content type according to the creator, which MAY have semantic meaning in order to differentiate this content type from other content types (e.g., two content types containing video media could differentiate between "room-pan" and "slides").A unique name or identifier for the content type according to the creator, which MAY have meaning to a human user in order to differentiate this content type from other content types (e.g., two content types containing video media could differentiate between "room-pan" and "slides"). REQUIRED
    sendersWhich parties in the session will be generating content; the allowable values are "initiator", "responder", or "both" (where "both" is the default).Which parties in the session will be generating content; the allowable values are "initiator", "responder", or "both" (where the default is "both"). RECOMMENDED
    @@ -941,7 +970,7 @@ PENDING o----------------------+ |
  • The <reason/> element MAY contain a <text/> element that provides human-readable information about the reason for the action.
  • The <reason/> element MAY contain an element qualified by some other namespace that provides more detailed machine-readable information about the reason for the action.
    • -

    The defined conditions are described in the folloiwing table.

    +

    The defined conditions are described in the following table.

    @@ -953,7 +982,7 @@ PENDING o----------------------+ | - + @@ -989,10 +1018,13 @@ PENDING o----------------------+ |
    Element
    <busy/>The party is busy and cannot accept communications.The party is busy and cannot accept a session.
    <connectivity-error/>
     + +

    The syntax and semantics of the <thread/> element exactly matches that of the <thread/> element as defined for the &MESSAGE; stanza (qualified by the 'jabber:client' namespace) as defined in &xmppim;. It is used to associate a Jingle session or sessions with an ongoing conversation, so that user interfaces with the ability to present multiple interactions in the same window can show an association between the conversation and the Jingle session(s).

    +     -

    The Jingle-specific error conditions are as follows. These condition elements are qualified by the 'urn:xmpp:tmp:jingle:errors' namespace &NSNOTE;.

    +

    The Jingle-specific error conditions are as follows. These condition elements are qualified by the 'urn:xmpp:jingle:errors:0' namespace &VNOTE;.

    @@ -1018,7 +1050,7 @@ PENDING o----------------------+ | -

    If an entity supports Jingle, it MUST advertise that fact by returning a feature of "urn:xmpp:tmp:jingle" &NSNOTE; in response to a &xep0030; information request. The response MUST also include features for the application formats and transport methods supported by the responding entity, as described in the relevant specifications.

    +

    If an entity supports Jingle, it MUST advertise that fact by returning a feature of "urn:xmpp:jingle:0" &VNOTE; in response to a &xep0030; information request. The response MUST also include features for the application formats and transport methods supported by the responding entity, as described in the relevant specifications.

    ... - + ... ]]> -

    Naturally, support MAY also be determined via the dynamic, presence-based profile of Service Discovery defined in XEP-0115.

    +

    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.

    A document that specifies a Jingle application format (e.g., RTP sessions) MUST define:

      -
    1. How successful application format negotiation occurs for encapsulation into Jingle.
      2. +
    2. How successful application format negotiation occurs.
    3. A &DESCRIPTION; element and associated semantics for representing the application format.
    4. If and how the application format can be mapped to the Session Description Protocol, including the appropriate SDP media type (see Section 8.2.1 of RFC 4566).
      5. -
    5. Whether the media for the application format should be sent over a stream transport method or a datagram transport method (or, if both, which is preferred).
      6. +
    6. Whether the media for the application format shall be sent over a stream transport method or a datagram transport method (or, if both, which is preferred).
    7. Exactly how the media is to be sent and received over a stream or datagram transport.
     -

    A document that specifies a Jingle transport method (e.g., Raw UDP) MUST define:

    +

    A document that specifies a Jingle transport method (e.g., raw UDP) MUST define:

      -
    1. How successful transport negotiation occurs for encapsulation into Jingle.
      2. +
    2. How successful transport negotiation occurs.
    3. A &TRANSPORT; element and associated semantics for representing the transport method.
    4. Whether the transport is stream or datagram.
      5. -
    5. If and how the transport handles components as defined herein (e.g., for the Real Time Control Protocol).
      6. +
    6. If and how the transport handles "components" (e.g., for the Real Time Control Protocol).
         -

    Jingle sessions may be resource-intensive. Therefore, it is possible to launch a denial-of-service attack against an entity by burdening it with too many Jingle sessions. Care must be taken to accept sessions only from known entities and only if the entity's device is able to process such sessions.

    +

    Jingle sessions can be resource-intensive. Therefore, it is possible to launch a denial-of-service attack against an entity by burdening it with too many Jingle sessions. Care must be taken to accept sessions only from known entities and only if the entity's device is able to process such sessions.

     -

    Jingle communications may be enabled through gateways to non-XMPP networks, whose security characteristics may be quite different from those of XMPP networks. (For example, on some SIP networks authentication is optional and "from" addresses can be easily forged.) Care must be taken in communicating through such gateways.

    +

    Jingle communications can be enabled through gateways to non-XMPP networks, whose security characteristics can be quite different from those of XMPP networks. (For example, on some SIP networks authentication is optional and "from" addresses can be easily forged.) Care must be taken in communicating through such gateways.

     -

    Mere negotiation of a Jingle session may expose sensitive information about the parties (e.g., IP addresses). Care must be taken in communicating such information, and end-to-end encryption should be used if the parties do not trust the intermediate servers or gateways.

    +

    Mere negotiation of a Jingle session can expose sensitive information about the parties (e.g., IP addresses). Care must be taken in communicating such information, and end-to-end encryption should be used if the parties do not trust the intermediate servers or gateways.

         @@ -1081,30 +1113,29 @@ PENDING o----------------------+ | - -

    Until this specification advances to a status of Draft, its associated namespaces shall be:

    + +

    This specification defines the following XML namespaces:

      -
    • urn:xmpp:tmp:jingle
      • -
    • urn:xmpp:tmp:jingle:errors
      • -
    -

    Upon advancement of this specification, the ®ISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.

    -

    The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:

    -
      -
    • urn:xmpp:jingle
      • -
    • urn:xmpp:jingle:errors
      • +
    • urn:xmpp:jingle:0
      • +
    • urn:xmpp:jingle:errors:0
    +

    Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

    +     + +

    If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.

    The XMPP Registrar shall maintain a registry of Jingle application formats. All application format registrations shall be defined in separate specifications (not in this document). Application types defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:jingle:app:name" (where "name" is the registered name of the application format).

    ®PROCESS; - the name of the application format - a natural-language summary of the application format + The name of the application format. + A natural-language summary of the application format. - whether the media can be sent over a "stream" transport, a "datagram" transport, or "both" + Whether the media can be sent over a "stream" transport, + a "datagram" transport, or "both". - the document in which this application format is specified + The document in which the application format is specified. ]]>     @@ -1128,8 +1159,8 @@ PENDING o----------------------+ | @@ -1143,6 +1174,10 @@ PENDING o----------------------+ | type='reasonElementType' minOccurs='0' maxOccurs='1'/> + @@ -1168,11 +1203,20 @@ PENDING o----------------------+ | + + + + + + - + @@ -1195,7 +1239,8 @@ PENDING o----------------------+ | - @@ -1207,16 +1252,19 @@ PENDING o----------------------+ | - - - - - + + + + + + @@ -1234,8 +1282,8 @@ PENDING o----------------------+ | @@ -1260,10 +1308,10 @@ PENDING o----------------------+ |
  • Recommend that all client developers implement a dual-stack (XMPP + SIP) solution.
  • Define a full-featured protocol for XMPP signalling.
    • -

    Implementation experience indicates that a dual-stack approach may not be feasible on all the computing platforms for which Jabber clients have been written, or even desirable on platforms where it is feasible. For example, one large ISP decided to switch to a pure XMPP approach after having implemented and deployed a dual-stack client for several years. Therefore, it seemed reasonable to define an XMPP signalling protocol that could provide the necessary session management semantics while also making it relatively straightforward to interoperate with existing Internet standards.

    +

    Implementation experience indicates that a dual-stack approach might not be feasible on all the computing platforms for which Jabber clients have been written, or even desirable on platforms where it is feasible. For example, one large ISP decided to switch to a pure XMPP approach after having implemented and deployed a dual-stack client for several years. Therefore, it seemed reasonable to define an XMPP signalling protocol that could provide the necessary session management semantics while also making it relatively straightforward to interoperate with existing Internet standards.

    As a result of feedback received on XEP-0111, the original authors of this document (Joe Hildebrand and Peter Saint-Andre) began to define such a signalling protocol, code-named Jingle. Upon communication with members of the Google Talk team, Google Talk is a messaging and voice chat service and client provided by Google; see <http://www.google.com/talk/>. it was discovered that the emerging Jingle approach was conceptually (and even syntactically) quite similar to the signalling protocol used in the Google Talk application. Therefore, in the interest of interoperability and adoption, we decided to harmonize the two approaches. The signalling protocol specified herein is, therefore, substantially equivalent to the original Google Talk protocol, with several adjustments based on feedback received from implementors as well as for publication by the XMPP Standards Foundation.

     -

    The authors would like to thank Rohan Mahy for his valuable input on early versions of the Jingle specifications. Thiago Camargo, Diana Cionoiu, Olivier Crête, Dafydd Harries, Antti Ijäs, Tim Julien, Lauri Kaila, Justin Karneges, Jussi Laako, Steffen Larsen, Anthony Minessale, Akito Nozaki, Matt O'Gorman, Rob Taylor, Matt Tucker, Justin Uberti, Saku Vainio, Brian West, Jeff Williams, and others have also provided helpful input. Thanks also to those who have commented on the &SSIG; and (earlier) Jingle Before this specification was formally accepted by the XMPP Standards Foundation as an XMPP Extension Protocol, it was discussed on the semi-private <jingle@jabber.org> mailing list; although that list is no longer used since the standards@xmpp.org list is the preferred discussion venue, for historical purposes it is publicly archived at <http://mail.jabber.org/pipermail/jingle/>. mailing lists.

    +

    The authors would like to thank Rohan Mahy for his valuable input on early versions of the Jingle specifications. Thiago Camargo, Diana Cionoiu, Olivier Crête, Dafydd Harries, Antti Ijäs, Tim Julien, Lauri Kaila, Justin Karneges, Jussi Laako, Steffen Larsen, Anthony Minessale, Akito Nozaki, Matt O'Gorman, Rob Taylor, Matt Tucker, Justin Uberti, Saku Vainio, Brian West, Jeff Williams, and others have also provided helpful input. Thanks also to those who have commented on the &SSIG; and Jingle Before this specification was formally accepted by the XMPP Standards Foundation as an XMPP Extension Protocol, it was discussed on the semi-private <jingle@jabber.org> mailing list. This list has since been resurrected as a special-purpose venue for discussion of Jingle protocols and implementation; interested developers can subscribe and access the archives at at <http://mail.jabber.org/mailman/listinfo/jingle/>. mailing lists.

    Jingle Condition