summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | Rename section 5.Karsten Loesing2014-01-14
| | |
| * | Fix section number of new appendix B.Karsten Loesing2014-01-14
| | |
| * | Move section 4.5 to the appendix.Karsten Loesing2014-01-14
| | | | | | | | | | | | | | | | | | | | | "General-use HTTP URLs" is not an operation but a reference, and references belong in the appendix. This commit does not yet repair section numbering or references.
| * | Move client-specific parts of 4.4 to 5.4.Karsten Loesing2014-01-14
| | |
| * | Rename section 4.4.Karsten Loesing2014-01-14
| | |
| * | Rename section 4.3.Karsten Loesing2014-01-14
| | |
| * | Rename section 4.1 and make it cache-only.Karsten Loesing2014-01-14
| | |
| * | Remove now empty section 4.1, and renumber sections.Karsten Loesing2014-01-14
| | |
| * | Rename section 4.Karsten Loesing2014-01-14
| | |
| * | Distribute what's left over from 4.1 to 3.*.Karsten Loesing2014-01-14
| | | | | | | | | | | | | | | Section 4.1 "Voting" describes much more than just the voting operation. Move these operation fragments to the subsections they belong in.
| * | Rename section 3.10.Karsten Loesing2014-01-14
| | |
| * | Rename section 3.9.Karsten Loesing2014-01-14
| | |
| * | Clean up copied section 3.7 and section 4.5.Karsten Loesing2014-01-14
| | | | | | | | | | | | | | | | | | | | | Section 3.7 should only contain parts that are relevant for authorities, and section 4.5 should only contain parts that are relevant for caches (right now, it also describes what clients should do, but that's something to change when cleaning up 4.5).
| * | Fix section numbers from copying 4.5 after 3.6.Karsten Loesing2014-01-14
| | |
| * | Copy 4.5 "Downloading extra-info documents" after 3.6Karsten Loesing2014-01-14
| | | | | | | | | | | | This commit does not yet repair section numbering or references.
| * | Clean up copied section 3.6 and section 4.3.Karsten Loesing2014-01-14
| | | | | | | | | | | | Take out cache-only parts from 3.6 and authority-only parts from 4.3.
| * | Fix section numbers from copying 4.3 after 3.5.Karsten Loesing2014-01-14
| | |
| * | Copy 4.3 "Downloading router descriptors" after 3.5.Karsten Loesing2014-01-14
| | | | | | | | | | | | This commit does not yet repair section numbering or references.
| * | Add new section 3.5 "Downloading missing certificates".Karsten Loesing2014-01-14
| | | | | | | | | | | | | | | | | | This subsection is just a placeholder for now. Also fix section numbers and references.
| * | Make 3.5 and 3.6 subsections of 3.4.Karsten Loesing2014-01-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The vote status document format (3.5) and the process of assigning flags in a vote (3.6) are both part of the authority operation "exchanging votes" and not operations on their own. That's why they should be subsubsections rather than subsections. This results in the following changes to section numbers: * 3.5 -> 3.4.1 * 3.6 -> 3.4.2 * 3.7 -> 3.5 * 3.8 -> 3.6 * 3.9 -> 3.7
| * | Fix section references from adding new section 3.4.Karsten Loesing2014-01-14
| | |
| * | Move part of 4.1. "Voting" to new 3.4.Karsten Loesing2014-01-14
| | | | | | | | | | | | This commit does not yet repair section numbering or references.
| * | Tweak section 3.3 "Microdescriptors".Karsten Loesing2014-01-13
| | | | | | | | | | | | | | | | | | Phrase subsection title as operation. Also, remove subsubsection implying that there would be other subsubsections in the future, which is not the case.
| * | Rephrase subsection title to be more precise.Karsten Loesing2014-01-13
| | |
| * | Fix references from moving section 4.1 to 3.2.Karsten Loesing2014-01-13
| | |
| * | Move section 4.1 "Accepting uploads" to 3.2.Karsten Loesing2014-01-13
| | | | | | | | | | | | This commit does not yet repair section numbering or references.
| * | Phrase subsection title as operation.Karsten Loesing2014-01-13
| | |
| * | Rename section 3 and remove obsolete overview part.Karsten Loesing2014-01-13
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Make new subsection for routers uploading descriptors.Karsten Loesing2014-01-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The rule we're trying to follow here is that sections are for roles (client, authority, cache, client) and subsections are for operations performed by the role. Routers really only perform a single operation: they periodically upload their descriptors to the authorities. That's why there should be a single subsection for this operation. This effectively substitutes section number parts "2." with "2.1.": * 2 -> 2.1 * 2.1 -> 2.1.1 * 2.2 -> 2.1.2 * 2.2.1 -> 2.1.2.1 * 2.3 -> 2.1.3
| * | Make section references easier to search for.Karsten Loesing2014-01-13
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Prefix all section references with the word "section", and avoid line breaks between "section[s]" and section numbers. Searching for section references should now be as easy as (for example): grep "section.* 1\.4" dir-spec.txt Also, while going through section references, lower-case 1 instance of "Section" to be consistent with the rest and fix 2 broken references.
* | Revise proposal 147 based on discussion with Nick.Karsten Loesing2014-01-15
|/ | | | https://lists.torproject.org/pipermail/tor-dev/2014-January/006022.html
* Revise proposal 185 to make DirCache flag unconditionalNick Mathewson2014-01-06
| | | | | | | | | | | | | Based on review by Karsten, who says: """I'm not sure why a) relays with a working DirPort shouldn't include "dir-cache 1" in their router descriptor and b) authorities shouldn't assign the "DirCache" flag to relays with a working DirPort that don't have a "dir-cache 1" line in their router descriptor. I understand that neither of the two actions are necessary to make the proposal work. But this could be a chance to get rid of the DirPort concept entirely and only rely on "dir-cache 1" and "DirCache" flags in the future."""
* Merge remote-tracking branch 'karsten/prop165tweaks'Nick Mathewson2014-01-06
|\
| * Fix typos and unclear phrasing in proposal 165.Karsten Loesing2013-12-22
| |
* | Make the rendezvous-cookie passing more explicit.George Kadianakis2014-01-06
|/ | | | It's not clear that REND_TOKEN refers to the rendezvous cookie.
* Add references to other documentsNick Mathewson2013-12-05
|
* Make rend-spec-ng.txt into a proper (pair of) proposals.Nick Mathewson2013-11-29
| | | | See rendspec-ng branch in my torspec repository for the revision history.
* Proposal 223: make auth_input values match. not my fault. Thanks weaselNick Mathewson2013-11-20
|
* Another 223 fix from weasel. My fault this timeNick Mathewson2013-11-20
|
* Clarify MULTIEXPONEN in 223Nick Mathewson2013-11-20
| | | | Based on suggestion from weasel.
* Add 223-ace-handshake.txtNick Mathewson2013-11-20
|
* reindex proposalsNick Mathewson2013-11-18
|
* Merge remote-tracking branch 'public/finish_prop157'Nick Mathewson2013-11-18
|\
| * Mark the dir-key-crosscert element as required.Nick Mathewson2013-11-14
| | | | | | | | This closes proposal 157.
* | Mark proposal 217 finished. Still needs merging into specNick Mathewson2013-11-14
| |
* | Mark proposal 146 superseded by 206Nick Mathewson2013-11-14
| |
* | Looks like Roger marked 213 as "should be marked Dead" without Deadening it. ↵Nick Mathewson2013-11-14
|/ | | | Deadening.
*-. Merge remote-tracking branches 'atagar/10086' and 'atagar/10085'Nick Mathewson2013-11-04
|\ \
| | * Don't enumerate event types in section 3.4Damian Johnson2013-11-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | When adding an event type we expect spec authors to edit both section 3.4 and 4.1.x. This is error prone... https://trac.torproject.org/10085 Dropping the redundant listing of event types and simply citing 4.1.x.
| * | Describing CONN_BW's ConnTypeDamian Johnson2013-11-03
| |/ | | | | | | | | | | | | | | | | | | Our new CONN_BW events' ConnType enumeration is poorly defined... https://trac.torproject.org/10086 This is just a guess on my part for what it's supposed to be. I have *not* trudged through the tor code to puzzle out how it actually allocates this enumeration.
generated by cgit v1.2.1 (git 2.18.0) at 2024-02-08 07:43:32 +0000