Closes torspec#25

The operatorurl field got renamed to 'url' in
https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/
This motivated this change, so we do not have to change prop 326
everything the referenced spec is updated.

it is not required since only subscribed users can
send emails to this list.

Alexander Færøy authored May 18, 2019 and David Goulet committed Oct 06, 2020

This patch adds support for the TOR_PT_OUTBOUND_BIND_ADDRESS variable to
both PT proxies and servers.

See: https://bugs.torproject.org/5304

Also, note when we dropped support for the various obsolete options.

No editing yet; only movement.

Since the authorities can produce a signed consensus as soon as
`ValidAfter` minus `DistSeconds`, and since they serve a signed
consensus as soon as it has enough signatures, it's possible that a
client or relay that's starting late in the hour can get an "early"
consensus.  Back in tor#25756, we fixed this issue in Tor, but we
didn't document the behavior in the spec.

A keyword may not begin with '-'.  Otherwise, "-----BEGIN" would be
a keyword, and the grammar would be ambiguous.

A beginline or endline may have multiple words in its tag.

For indistinguishability, other implementations should pad the same
way that we do.

Right now, tor encodes them in a certain order; specifying that
order can help other implementations be indistinguishable.

There were extraneous entries in the lists of signed key types:
these values describe the type of the key being signed (eg, ed25519
or RSA), not the type of the certificate.

Further, clarify Tor bug 40124, so that people know to expect
incorrect cert key types on older signing->link certs.