commit dca09fda52993babfc00d3e76e681913450d5f82 Author: Sebastian Hahn <sebastian@torproject.org> Date: Tue Sep 6 21:06:35 2016 +0200 Specify "p" lines in a consensus as required This is motivated to remove an ambiguity about what a missing "p" line means when comparing historical consensus data. --- dir-spec.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index db1378f..d5e8376 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1369,16 +1369,17 @@ "p" SP ("accept" / "reject") SP PortList NL - [At most once] + [Exactly once.] - The exit-policy summary as specified in sections 3.4.1 and 3.8.2. A - missing "p" line is equivalent to "p reject 1-65535". + The exit-policy summary as specified in sections 3.4.1 and 3.8.2. [With microdescriptors, clients don't learn exact exit policies: clients can only guess whether a relay accepts their request, try the BEGIN request, and might get end-reason-exit-policy if they guessed wrong, in which case they'll have to try elsewhere.] + [In consensus methods before 5, this line was omitted.] + "p6" SP ("accept" / "reject") SP PortList NL [At most once]