commit 6956d6cb2b86385740abe9cf5f4b2b5257c9365a Author: Karsten Loesing karsten.loesing@gmx.net Date: Mon Jan 13 18:46:30 2014 +0100

Rename section 3 and remove obsolete overview part.

Section 3 will describe operations and data formats that are related to the authority role, and section 4 will specify which operations are performed by caches. Reflect this in the new section title of section 3, and remove the (already obsolete) overview part listing which documents are generated by authorities. --- dir-spec.txt | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt index 184bc2e..a66a684 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1010,7 +1010,7 @@

bool ::= "0" | "1"

-3. Formats produced by directory authorities. +3. Directory authority operation and formats

Every authority has two keys used in this protocol: a signing key, and an authority identity key. (Authorities also have a router identity @@ -1019,14 +1019,6 @@ sign new key certificates using new signing keys; it is very sensitive. The signing key is used to sign key certificates and status documents.

- There are three kinds of documents generated by directory authorities: - - Key certificates - Status votes - Status consensuses - - Each is discussed below. - 3.1. Key certificates

Key certificates consist of the following items: