diff options
author | Roger Dingledine <arma@torproject.org> | 2007-10-18 23:14:58 +0000 |
---|---|---|
committer | Roger Dingledine <arma@torproject.org> | 2007-10-18 23:14:58 +0000 |
commit | 0a865bc277d49dfedf4163b253ccaaafc07869ca (patch) | |
tree | f77d46a52136fc726f5a2a342a55ea325829975b /doc | |
parent | 322eddb045288fd83387f9e911c23c18329f2a6e (diff) | |
download | tor-0a865bc277d49dfedf4163b253ccaaafc07869ca.tar.gz tor-0a865bc277d49dfedf4163b253ccaaafc07869ca.zip |
various fixes from reading or-cvs the past few days
svn:r12035
Diffstat (limited to 'doc')
-rw-r--r-- | doc/spec/proposals/105-handshake-revision.txt | 4 | ||||
-rw-r--r-- | doc/spec/proposals/122-unnamed-flag.txt | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/doc/spec/proposals/105-handshake-revision.txt b/doc/spec/proposals/105-handshake-revision.txt index c4fb50a40f..709c01663d 100644 --- a/doc/spec/proposals/105-handshake-revision.txt +++ b/doc/spec/proposals/105-handshake-revision.txt @@ -121,9 +121,9 @@ Proposal: VERSIONS cell before sending any other cells. (But see below.) VersionsLen [1 byte] - Versions [NumVersions bytes] + Versions [VersionsLen bytes] - "Versions" is a sequence of NumVersions bytes. Each value between 1 and + "Versions" is a sequence of VersionsLen bytes. Each value between 1 and 127 inclusive represents a single version; current implementations MUST ignore other bytes. Parties should list all of the versions which they are able and willing to support. Parties can only communicate if they diff --git a/doc/spec/proposals/122-unnamed-flag.txt b/doc/spec/proposals/122-unnamed-flag.txt index 6d3d8c639c..8b169b6535 100644 --- a/doc/spec/proposals/122-unnamed-flag.txt +++ b/doc/spec/proposals/122-unnamed-flag.txt @@ -107,19 +107,19 @@ Status: Open 4. Changes to the v2 directory - Previously v2 authorities that had a binding for a server named Bob did + Previously, v2 authorities that had a binding for a server named Bob did not list any other server named Bob. This will change too: Version 2 authorities will start listing all routers they know about, whether they conflict with a name-binding or not: Servers for which this authority has a binding will continue to be marked Named, - additionally all other servers of that will be listed without the + additionally all other servers of that nickname will be listed without the Named flag (i.e. there will be no Unnamed flag in v2 status documents). Clients already should handle having a named Bob alongside unnamed Bobs correctly, and having the unnamed Bobs in the status file even - without the named server is no worse than the curren status quo where - clients learn about those severs from other authorities. + without the named server is no worse than the current status quo where + clients learn about those servers from other authorities. The benefit of this is that an authority's opinion on a server like Guard, Stable, Fast etc. can now be learned by clients even if that |