mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-13 06:33:44 +01:00
Make spec docs reference RFC2119
Now people will have no excuse for not knowing what "MUST" and "MAY" mean. Fixes bug 1310.
This commit is contained in:
parent
43ab747fe4
commit
deb9e4aff7
@ -15,6 +15,11 @@
|
|||||||
versions 0.1.0.x; the protocol in this document only works with Tor
|
versions 0.1.0.x; the protocol in this document only works with Tor
|
||||||
versions in the 0.1.1.x series and later.)
|
versions in the 0.1.1.x series and later.)
|
||||||
|
|
||||||
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
|
||||||
|
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
|
||||||
|
"OPTIONAL" in this document are to be interpreted as described in
|
||||||
|
RFC 2119.
|
||||||
|
|
||||||
1. Protocol outline
|
1. Protocol outline
|
||||||
|
|
||||||
TC is a bidirectional message-based protocol. It assumes an underlying
|
TC is a bidirectional message-based protocol. It assumes an underlying
|
||||||
|
@ -18,13 +18,15 @@
|
|||||||
103 Splitting identity key from regularly used signing key
|
103 Splitting identity key from regularly used signing key
|
||||||
104 Long and Short Router Descriptors
|
104 Long and Short Router Descriptors
|
||||||
|
|
||||||
AS OF 14 JUNE 2007, THIS SPECIFICATION HAS NOT YET BEEN COMPLETELY
|
|
||||||
IMPLEMENTED, OR COMPLETELY COMPLETED.
|
|
||||||
|
|
||||||
XXX when to download certificates.
|
XXX when to download certificates.
|
||||||
XXX timeline
|
XXX timeline
|
||||||
XXX fill in XXXXs
|
XXX fill in XXXXs
|
||||||
|
|
||||||
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
|
||||||
|
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
|
||||||
|
"OPTIONAL" in this document are to be interpreted as described in
|
||||||
|
RFC 2119.
|
||||||
|
|
||||||
0.1. History
|
0.1. History
|
||||||
|
|
||||||
The earliest versions of Onion Routing shipped with a list of known
|
The earliest versions of Onion Routing shipped with a list of known
|
||||||
|
@ -14,6 +14,11 @@ of their choices.
|
|||||||
|
|
||||||
THIS SPEC ISN'T DONE YET.
|
THIS SPEC ISN'T DONE YET.
|
||||||
|
|
||||||
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
|
||||||
|
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
|
||||||
|
"OPTIONAL" in this document are to be interpreted as described in
|
||||||
|
RFC 2119.
|
||||||
|
|
||||||
1. General operation
|
1. General operation
|
||||||
|
|
||||||
Tor begins building circuits as soon as it has enough directory
|
Tor begins building circuits as soon as it has enough directory
|
||||||
|
@ -3,6 +3,11 @@
|
|||||||
|
|
||||||
0. Overview and preliminaries
|
0. Overview and preliminaries
|
||||||
|
|
||||||
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
|
||||||
|
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
|
||||||
|
"OPTIONAL" in this document are to be interpreted as described in
|
||||||
|
RFC 2119.
|
||||||
|
|
||||||
Read
|
Read
|
||||||
https://www.torproject.org/doc/design-paper/tor-design.html#sec:rendezvous
|
https://www.torproject.org/doc/design-paper/tor-design.html#sec:rendezvous
|
||||||
before you read this specification. It will make more sense.
|
before you read this specification. It will make more sense.
|
||||||
|
@ -16,6 +16,11 @@ see tor-design.pdf.
|
|||||||
|
|
||||||
0. Preliminaries
|
0. Preliminaries
|
||||||
|
|
||||||
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
|
||||||
|
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
|
||||||
|
"OPTIONAL" in this document are to be interpreted as described in
|
||||||
|
RFC 2119.
|
||||||
|
|
||||||
0.1. Notation and encoding
|
0.1. Notation and encoding
|
||||||
|
|
||||||
PK -- a public key.
|
PK -- a public key.
|
||||||
|
Loading…
Reference in New Issue
Block a user