From dc4c0b1dc5951bb8b9bf895e41fa75addff2a20c Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Mon, 14 Nov 2016 11:43:58 -0600 Subject: [PATCH] XEP-0003: Fix minor XML issues --- xep-0003.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/xep-0003.xml b/xep-0003.xml index 03689c19..f738e08c 100644 --- a/xep-0003.xml +++ b/xep-0003.xml @@ -140,7 +140,7 @@

A Jabber client can send various controls to the PASS service via the set to control how the PASS service behaves, how the server handles a listening port.

-

This tells the server to shut down the port after a specified number of seconds. After the timeout period, the PASS service MUST send an to the JID to tell it that the port has been closed down. It notifies the client with:

+

This tells the server to shut down the port after a specified number of seconds. After the timeout period, the PASS service MUST send an <iq/> to the JID to tell it that the port has been closed down. It notifies the client with:

 -

This tells the server to listen once, and then close the port. Even if the has not been met, the overrides that and shuts down the listening port. When this happens the server notifies the client with the following packet:

+

This tells the server to listen once, and then close the port. Even if the <expire/> has not been met, the <oneshot/> overrides that and shuts down the listening port. When this happens the server notifies the client with the following packet:

400 - Missing specification. - Sent a w/o a + Missing <proxy/> specification. + Sent a <close/> w/o a <proxy/> 401 @@ -225,12 +225,12 @@ 404 Port not found in registry. - The was not a defined port. + The <proxy port=''/> was not a defined port. 405 Proxy IP does not match. - The IP sent in the does not match the IP of the pass-service + The IP sent in the <proxy/> does not match the IP of the pass-service @@ -258,10 +258,10 @@ ]]> -

Obviously the port is not going to be known, but the IP address will let you authenticate the JID via the PASS service since the PASS service tells you the information upon a connection.

+

Obviously the port is not going to be known, but the IP address will let you authenticate the JID via the PASS service since the PASS service tells you the <client/> information upon a connection.

-

When a server gets an Incoming Connection notification the client has the right to deny that connection based on the information that it receives. It can return an error to the PASS service specifying the port and hangup on the active connection and start listening again. This does not affect the control. For example:

+

When a server gets an Incoming Connection notification the client has the right to deny that connection based on the <client/> information that it receives. It can return an error to the PASS service specifying the <proxy/> port and hangup on the active <client/> connection and start listening again. This does not affect the <oneshot/> control. For example:

The PASS service sends you:

401 Unauthorized - The incoming does not match the from the client you want to exchange data with. + The incoming <client/> does not match the <client/> from the client you want to exchange data with.