From 14f0e3e14496ae7d58ad2eded566445debf52254 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre
Date: Tue, 30 Sep 2008 14:50:28 +0000
Subject: [PATCH] 0.8
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2291 4b5297f7-1745-476d-ba37-a9c6900126ab
---
xep-0234.xml | 114 +++++++++++++++------------------------------------
1 file changed, 34 insertions(+), 80 deletions(-)
diff --git a/xep-0234.xml b/xep-0234.xml
index d926fb94..9150fbfd 100644
--- a/xep-0234.xml
+++ b/xep-0234.xml
@@ -24,6 +24,12 @@
NOT_YET_ASSIGNED
&stpeter;
+
+ 0.8
+ 2008-09-30
+ psa
+ Corrected fallback scenario to use transport-replace and transport-accept.
+
0.7
2008-09-25
@@ -411,7 +417,7 @@ Claudius Laertes
-
+
@@ -437,15 +443,11 @@ Claudius Laertes
|<----------------------------|
| [ SOCKS5 failure! ] |
|x---------------------------x|
- | content-add (IBB) |
- |<----------------------------|
- | ack |
- |---------------------------->|
- | content-accept |
+ | transport-replace (IBB) |
|---------------------------->|
| ack |
|<----------------------------|
- | content-remove (SOCK5) |
+ | transport-accept |
|<----------------------------|
| ack |
|---------------------------->|
@@ -455,7 +457,7 @@ Claudius Laertes
|<----------------------------|
| ack |
|---------------------------->|
- | [ file transfer ] |
+ | [ file transfer via IBB] |
|============================>|
| terminate |
|<----------------------------|
@@ -530,98 +532,50 @@ Claudius Laertes
]]>
- At this point the file transfer has failed using SOCKS5 Bytestreams. However, all is not lost, because the parties can attempt to fall back to In-Band Bytestreams. Therefore the responder sends a content-add action including a transport of IBB and a request for the file originally offered (note the use of the <request/> element instead of the <offer/> element, since the responder wants the initiator to send the previously-offered file).
- At this point the file transfer has failed using SOCKS5 Bytestreams. However, all is not lost, because the parties can attempt to fall back to In-Band Bytestreams. Therefore the initiator sends a transport-replace action including a transport of IBB.
+
-
-
-
-
-
-
+
]]>
- The initiator then acknowledges the content-add action.
- The responder then acknowledges the transport-replace action.
+
]]>
- If the content definition is acceptable, the initiator then sends a content-accept action to the responder.
- If the transport replacement is acceptable, the responder then sends a transport-accept action to the initiator.
+
-
-
-
-
-
]]>
- The responder then acknowledges the content-accept action.
- The initiator then acknowledges the transport-accept action.
+
- ]]>
- The responder then sends a Jingle content-remove (deleting SOCKS5 Bytestreams) in order to choose the desired transport, which in this case is IBB.
-
-
-
-
-
-
- This is a test. If this were a real file...
-
-
-
-
-
-
-
- ]]>
- The initiator acknowledges receipt of the Jingle content-remove action.
-
]]>
The initiator then sends an IBB initiation request to the responder.
@@ -663,7 +617,7 @@ Claudius Laertes
-
+
@@ -716,24 +670,24 @@ Claudius Laertes
file-transfer
Jingle sessions for the transfer of a file
- reliable
+ streaming
XEP-0234
]]>
- The XMPP Registrar shall add to its registry of Jingle transport methods definitions for the reliable transport methods defined in XEP-0047 and XEP-0065. The registry submissions are as follows:
+ The XMPP Registrar shall add to its registry of Jingle transport methods definitions for the streaming transport methods defined in XEP-0047 and XEP-0065. The registry submissions are as follows:
bytestreams
A method for exchanging data over SOCKS5 Bytestreams.
- reliable
+ streaming
XEP-0065
ibb
A method for exchanging data over In-Band Bytestreams.
- reliable
+ streaming
XEP-0047
]]>