diff --git a/xep-0208.xml b/xep-0208.xml index b1aaa553..e985c792 100644 --- a/xep-0208.xml +++ b/xep-0208.xml @@ -22,6 +22,12 @@ N/A &stpeter; + + 0.3 + 2007-11-15 + psa +

Editorial review and consistency check.

+
0.2 2007-05-11 @@ -49,13 +55,13 @@ -

&xep0166; defines a framework for using XMPP to negotiate and manage out-of-band media sessions. Unfortunately, most developers of XMPP clients have limited experience with multimedia applications such as voice and video, making it difficult to get started with implementation of Jingle technologies. Therefore this document provides a simple transport and session type that client developers can use to bootstrap Jingle implementations.

+

&xep0166; defines a framework for using XMPP to negotiate and manage out-of-band media sessions. Unfortunately, most developers of XMPP clients have limited experience with multimedia applications such as voice and video, making it difficult to get started with implementation of Jingle technologies. Therefore this document provides a simple application format that client developers can use to bootstrap Jingle implementations.

Note: The methods specified herein are provided for experimentation and unit testing only. They are not intended for inclusion in released software or production environments.

-

The intent of this simple Jingle profile is to enable exchange of data using the Echo Protocol specified in &rfc0862;, but using a port other than 7 (the default port for this experimental usage is 17777). The protocol flow is as follows. (The following examples use &xep0177; as the transport protocol; although it is possible to complete echo protocol exchanges via TCP, that is deemed less useful and there is no Jingle transport for direct TCP exchanges.)

- The intent of this simple Jingle profile is to enable exchange of data using the Echo Protocol specified in &rfc0862;, but using a port other than 7 (the default port for this experimental usage is 17777). The protocol flow is as follows. (The following examples use &xep0177; as the transport protocol; although it is possible to complete echo protocol exchanges via TCP, that is deemed less useful and there is no Jingle transport method for direct TCP exchanges.)

+ ]]> - If none of the errors specified in XEP-0166 occurs, the receiver acknowledges the session request.

+ ]]> -

If no negotiation is required (e.g., to modify the port number or transport protocol), the receiver simply accepts the session request. (Alternatively, if the receiver wants to use a port other 17777, it SHOULD negotiate the port using a Jingle content-add action; see XEP-0166 for details and examples.)

- If no negotiation is required (e.g., to modify the port number or transport method), the receiver simply accepts the session request. (Alternatively, if the receiver wants to use a port other 17777, it SHOULD negotiate the port using a Jingle content-add action; see XEP-0166 for details and examples.)

+ ]]> - ]]>

The parties may now exchange data using the echo protocol in order to test the connection.