From 6f67dc4cfacaed00baf484deaa9961a633448432 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 27 Nov 2007 19:31:43 +0000 Subject: [PATCH] text tweaks git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1419 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0208.xml | 31 +++++++++++++++++++++---------- 1 file changed, 21 insertions(+), 10 deletions(-) diff --git a/xep-0208.xml b/xep-0208.xml index fd9bfe20..181cfa8a 100644 --- a/xep-0208.xml +++ b/xep-0208.xml @@ -7,7 +7,7 @@
Bootstrapping Implementation of Jingle - This document provides guidelines to client developers for bootstrapping implementation of Jingle technologies. + This document provides guidelines to XMPP client developers for bootstrapping implementation of Jingle technologies. &LEGALNOTICE; 0208 Proposed @@ -62,7 +62,10 @@

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 none of the errors specified in XEP-0166 occurs, the responder acknowledges the session initiation request.

+ ]]> -

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.)

- +

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

+ ]]> + ]]>

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

-

Note: Protocol flows for additional use cases (e.g., renegotiation) may be added to future versions of this specification.