Is proto required for alternate relay implementations?

Mike reports on tor-relays that authorities treat the "proto" line as mandatory for non-Tor implementations.

We should document that here:

https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n773

changed milestone to %Tor: 0.3.3.x-final in legacy/trac

added component::core tor/tor in Legacy / Trac doc in Legacy / Trac easy in Legacy / Trac milestone::Tor: 0.3.3.x-final in Legacy / Trac points::0.1 in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tor-spec in Legacy / Trac type::defect in Legacy / Trac labels

What do we mean by mandatory? That is, what fails?

Replying to arma:

What do we mean by mandatory? That is, what fails?

According to Mike, the relay is not included in the consensus unless it has a "proto" line.

So, it's not actually mandatory: Tor versions before 0.2.9 didn't have it, and they are still listed in the consensus. Possibly, it is mandatory when the platform line is empty? We should investigate.

Trac:
Keywords: easy doc deleted, easy doc tor-spec added

Ah, that appears to be what Mike said.

We don't have to do this in 0.3.2

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final
Owner: teor to N/A

Mark all tickets that are assigned to nobody as "new".

Trac:
Status: assigned to new

See also legacy/trac#24245 (moved).

e6c3257b065f7fe816843bf37de3c3b958d30ee7 in torspec to document that the field will become mandatory.

Trac:
Status: new to closed
Resolution: N/A to implemented

closed

changed time estimate to 48m

mentioned in issue legacy/trac#24257 (moved)

moved from legacy/trac#24023 (moved)

added Bug First Contribution labels and removed 1 deleted label

added Specifications + 1 deleted label and removed 1 deleted label

added Documentation label and removed 1 deleted label