From 86677952d6fe9dbf9590be99b53cc8aefd8e91e2 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Sat, 12 May 2007 01:52:28 +0000 Subject: [PATCH] 0.2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@830 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0208.xml | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/xep-0208.xml b/xep-0208.xml index 988cbf9a..992d295d 100644 --- a/xep-0208.xml +++ b/xep-0208.xml @@ -22,6 +22,12 @@ N/A &stpeter; + + 0.2 + 2007-05-11 + psa +

Specified use of port 17777 as default.

 + 0.1 2007-04-10 @@ -44,12 +50,12 @@

&xep0166; defines a framework for negotiating and managing out-of-band data exchange sessions over XMPP. 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.

-

Note: The methods specified herein are provided for experimental use only and are not intended for inclusion in released software or production environments.

+

Note: The methods specified herein are provided for experimentation and unit testing only and 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;. 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 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.)

+ - + ]]> -

Note: The standard port for the echo protocol is 7. However, since access to that port may be restricted, any other port MAY be negotiated.

+

Note: The port SHOULD be 17777.

]]> -

If no negotiation is required (e.g., to modify the port number or transport protocol), the receiver simply accepts 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.)

- - - - - - - + sid='a73sjjvkla37jfea'/> ]]>

As noted, the methods specified herein are provided for experimental use only and are not intended for inclusion in released software or production environments.

-

On some operating systems, access to the root or administrative user may be necessary in order to use the echo protocol over TCP or UDP port 7. Therefore it is recommended to negotiate use of the echo protocol on a different port if necessary.

+

On some operating systems, access to the root or administrative user may be necessary in order to use the echo protocol over TCP or UDP port 7; therefore it is RECOMMENDED to use port 17777 instead.