commit f72544e7cd1b881b460413dc9c9683223e39c012 Author: Roger Dingledine arma@torproject.org Date: Tue Jun 12 06:36:25 2012 -0400

tiny touchups to proposal 189 --- proposals/189-authorize-cell.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/189-authorize-cell.txt b/proposals/189-authorize-cell.txt index 09f74e6..87bffe0 100644 --- a/proposals/189-authorize-cell.txt +++ b/proposals/189-authorize-cell.txt @@ -108,13 +108,13 @@ Status: Open

4.3. How should multiple round-trip authorization protocols be handled?

- Protocols that require multiple-round trips between the client and + Protocols that require multiple round trips between the client and the bridge should use AUTHORIZE cells for communication.

The format of the AUTHORIZE cell is flexible enough to support messages from the client to the bridge and the reverse.

- At the end of a successful multiple round-trip protocol, an + At the end of a successful multiple-round-trip protocol, an AUTHORIZED cell must be issued from the bridge to the client.

4.4. AUTHORIZED seems useless. Why not use VPADDING instead?