From 2c1d626b9f86a72c41f2b0768aa3e127cb7e4cb0 Mon Sep 17 00:00:00 2001 From: Mike Perry Date: Mon, 6 Jul 2020 11:32:05 -0500 Subject: Document relay commands for circpad cells. --- padding-spec.txt | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'padding-spec.txt') diff --git a/padding-spec.txt b/padding-spec.txt index b9d99b7..f6356ed 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -309,8 +309,12 @@ the anonymity and load-balancing implications of their choices. Because circuit padding machines only become active at certain points in circuit lifetime, and because more than one padding machine may be active at - any given point in circuit lifetime, there is also a padding negotiation cell, - with fields as follows: + any given point in circuit lifetime, there is also a padding negotiation + cell and a negotiated response. These are relay commands 41 and 42, with + relay headers as per section 6.1 of tor-spec.txt. + + The fields of the relay cell Data payload of a negotiate request are + as follows: const CIRCPAD_COMMAND_STOP = 1; const CIRCPAD_COMMAND_START = 2; @@ -341,7 +345,8 @@ the anonymity and load-balancing implications of their choices. When a relay receives a circpad_negotiate cell, it checks that it supports the requested machine, and sends a circpad_negotiated cell, which is formatted - as follows: + in the data payload of a relay cell with command number 42 (see tor-spec.txt + section 6.1), as follows: struct circpad_negotiated { u8 version IN [0]; -- cgit v1.2.3-54-g00ecf