diff options
| author | Roger Dingledine <arma@torproject.org> | 2007-03-14 23:06:19 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2007-03-14 23:06:19 +0000 |
| commit | 17c055ce6e36734b813614cf038bdfbc5e91808a (patch) | |
| tree | bcc18a9f7415d6e672ec23ff942e7cf4181d203e | |
| parent | f0b131f1c0b9f7863391e0f2304ab6c5b7e8a05e (diff) | |
| download | tor-17c055ce6e36734b813614cf038bdfbc5e91808a.tar.gz tor-17c055ce6e36734b813614cf038bdfbc5e91808a.zip | |
clarify a confusion weasel had
svn:r9816
| -rw-r--r-- | doc/spec/proposals/110-avoid-infinite-circuits.txt | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/spec/proposals/110-avoid-infinite-circuits.txt b/doc/spec/proposals/110-avoid-infinite-circuits.txt index f26c38c77c..6f00fe488f 100644 --- a/doc/spec/proposals/110-avoid-infinite-circuits.txt +++ b/doc/spec/proposals/110-avoid-infinite-circuits.txt @@ -44,14 +44,16 @@ Design: the circuit (if more research shows us what to do), because Alice can choose how many of the K to mark as relay_extend. Note that relay_extend cells *can* contain any sort of data cell; so in effect it's actually - the relay type cells that are restricted. + the relay type cells that are restricted. By default, she would just + send the first K data cells over the stream as relay_extend cells, + regardless of their actual type. Each intermediate server would pass on the same type of cell that it received (either relay or relay_extend), and the cell's destination will be able to learn whether it's allowed to contain an Extend request. If an intermediate server receives a relay_extend cell after it has - already seen k cells, or if it sees a relay cell that contains an + already seen k data cells, or if it sees a relay cell that contains an extend request, then it tears down the circuit (protocol violation). Security implications: |