aboutsummaryrefslogtreecommitdiff
path: root/proposals/196-transport-control-ports.txt
diff options
context:
space:
mode:
authorGeorge Kadianakis <desnacked@riseup.net>2013-02-06 00:42:23 +0000
committerNick Mathewson <nickm@torproject.org>2013-08-15 12:20:27 -0400
commit3fe179789a9c0e86fe69240cf183fd7a196f3a5f (patch)
tree32160bf57fb65d57ca4f633ac5d591df21065993 /proposals/196-transport-control-ports.txt
parent1656e00cabb9d638c705494bbd3cfe40244eaee6 (diff)
downloadtorspec-3fe179789a9c0e86fe69240cf183fd7a196f3a5f.tar.gz
torspec-3fe179789a9c0e86fe69240cf183fd7a196f3a5f.zip
Add descriptions for the commands of the Extended ORPort.
Diffstat (limited to 'proposals/196-transport-control-ports.txt')
-rw-r--r--proposals/196-transport-control-ports.txt26
1 files changed, 25 insertions, 1 deletions
diff --git a/proposals/196-transport-control-ports.txt b/proposals/196-transport-control-ports.txt
index 0488934..db97ea7 100644
--- a/proposals/196-transport-control-ports.txt
+++ b/proposals/196-transport-control-ports.txt
@@ -55,6 +55,8 @@ Target: 0.2.4.x
3.1. The new extended ORPort protocol
+3.1.1. Protocol
+
The extended server port protocol is as follows:
COMMAND [2 bytes, big-endian]
@@ -68,7 +70,7 @@ Target: 0.2.4.x
(body ignored)
[0x0001] USERADDR: an address:port string that represents the
- user's address.
+ client's address.
[0x0002] TRANSPORT: a string of the name of the pluggable
transport currently in effect on the connection.
@@ -90,6 +92,28 @@ Target: 0.2.4.x
If the server receives a recognized command that does not parse, it
MUST close the connection to the client.
+3.1.2. Command descriptions
+
+3.1.2.1. USERADDR
+
+ An ASCII string holding the TCP/IP address of the client of the
+ pluggable transport proxy. A Tor bridge SHOULD use that address to
+ collect statistics about its clients.
+
+ The string MUST not be NUL-terminated.
+
+3.1.2.2. TRANSPORT
+
+ An ASCII string holding the name of the pluggable transport used by
+ the client of the pluggable transport proxy. A Tor bridge that
+ supports multiple transports SHOULD use that information to collect
+ statistics about the popularity of individual pluggable transports.
+
+ The string MUST not be NUL-terminated.
+
+ Pluggable transport names are C-identifiers and Tor MUST check them
+ for correctness.
+
3.2. The new TransportControlPort protocol
The TransportControlPort protocol is as follows: