diff --git a/xep-0177.xml b/xep-0177.xml index 01249ff1..d195ab18 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -26,6 +26,12 @@ &scottlu; &hildjj; &seanegan; + + 0.8 + 2007-11-15 + psa +

Editorial review and consistency check.

 + 0.7 2007-06-25 @@ -70,7 +76,7 @@ -

&xep0166; defines a framework for negotiating and managing out-of-band data sessions over XMPP. In order to provide a flexible framework, the base Jingle specification defines neither data transport methods nor content formats, leaving that up to separate specifications. The current document defines a transport method for establishing and managing data between XMPP entities using a raw User Datagram Protocol (UDP) connection (see &rfc0768;). This "raw-udp" method results in a lossy transport method suitable for use in media applications where some packet loss is tolerable (e.g., audio and video).

+

&xep0166; defines a framework for negotiating and managing out-of-band data sessions over XMPP. In order to provide a flexible framework, the base Jingle specification defines neither data transport methods nor application formats, leaving that up to separate specifications. The current document defines a transport method for establishing and managing data between XMPP entities using a raw User Datagram Protocol (UDP) connection (see &rfc0768;). This "raw-udp" method results in a lossy transport method suitable for use in media applications where some packet loss is tolerable (e.g., audio and video).

The Jingle transport method defined herein is designed to meet the following requirements:

@@ -85,15 +91,15 @@

In accordance with Section 8 of XEP-0166, this document specifies the following information related to the Jingle Raw UDP transport type:

  1. The transport negotiation process is defined in the Protocol Description section of this document.

    2. -

  2. The semantics of the &DESCRIPTION; element are defined in the Transport Initiation section of this document.

    3. +

  3. The semantics of the &TRANSPORT; element are defined in the Transport Initiation section of this document.

  4. Successful negotiation of the Raw UDP method results in use of a lossy transport that is suitable for applications where some packet loss is tolerable, such as audio and video.

  5. If multiple components are to be communicated over the transport, the first component shall be associated with the port in the transport initiation stanza and the second component (e.g., for RTCP) shall be associated with a UDP port that is one number higher than the specified port (e.g., if the specified port is 13540 then the port for the second component shall be 13541).

 -

In order for the initiator in a Jingle exchange to start the negotiation, it MUST send a Jingle "session-initiate" stanza as described in XEP-0166. This stanza MUST include at least one content type. If the initiator wishes to negotiate the Raw UDP transport for a given content type, it MUST include a &TRANSPORT; child element qualified by the 'http://www.xmpp.org/extensions/xep-0177.html#ns' namespace (see Protocol Namespaces), which MUST This is required to avoid a round trip and help expedite the negotiation. include the initiator's Raw UDP candidate via the 'ip', 'port', 'generation', and 'name' attributes of the &CANDIDATE; element.

- In order for the initiator in a Jingle exchange to start the negotiation, it MUST send a Jingle "session-initiate" stanza as described in XEP-0166. This stanza MUST include at least one content type. If the initiator wishes to negotiate the Raw UDP transport for a given content type, it MUST include a &TRANSPORT; child element qualified by the 'http://www.xmpp.org/extensions/xep-0177.html#ns' namespace &NSNOTE;, which MUST This is required to avoid a round trip and help expedite the negotiation. include the initiator's Raw UDP candidate via the 'ip', 'port', 'generation', and 'name' attributes of the &CANDIDATE; element.

+

As described in XEP-0166, to provisionally accept the session initiation request, the receiver returns an IQ-result:

- ]]>

Once the responder provisionally accepts the session, it:

@@ -146,7 +152,7 @@

As noted, the responder SHOULD send its own Raw UDP candidate to the initiator by sending a transport-info message to the initiator, as shown in the following example.

- ]]>

The initiator MUST then acknowledge receipt by returning an IQ result (or a standard XMPP error).

- ]]> -

Naturally, the initiator SHOULD also attend to send media to the responder as specified above. This media too may or may not get through, but if it does then the other party should acknowledge receipt.

+

Naturally, the initiator SHOULD also attend to send media to the responder as specified above. This media too may or may not get through, but if it does then the other party SHOULD acknowledge receipt.

 -

When it attempts to send data to a Raw UDP candidate, a party SHOULD send an informational message of <trying/>. If a party receives data, it SHOULD send an informational message of <received/>.

-

Each informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element specified in the Informational Messages section of this document.

+

When it attempts to send data to a Raw UDP candidate, a party SHOULD send an informational message of <trying/>.

+ + + + + + ]]> + + ]]> +

If a party receives data, it SHOULD send an informational message of <received/>.

+ + + + + + ]]> + + ]]> @@ -194,7 +238,7 @@

If an entity supports the Jingle Raw UDP transport, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0177.html#ns" &NSNOTE; in response to &xep0030; information requests.

- ]]> -