Update statuses for several proposals

We have a large number of proposals that are fully or partially implemented, but which are not marked as such. We should update their status so that we have less cruft sitting around in our list of active proposals.

I believe that the following proposals are OBSOLETE:

• 098-todo.txt: Proposals that should be written (Meta) @nickm ✔️
• 099-misc.txt: Miscellaneous proposals (Meta) @nickm ✔️
• 308-counter-galois-onion.txt: Counter Galois Onion: A New Proposal for Forward-Secure Relay Cryptography (Open) (obsoleted by in-progress CGO draft) @nickm ✔️

I think that we have implemented some or all of these proposals, and they should be updated accordingly. Ones that are implemented in the form described here should be FINISHED or CLOSED depending on whether the specs are up-to-date. Ones that are mostly implemented as written should be cleaned up, possibly with a section describing what did and did not get built, and marked as FINISHED.

• 265-load-balancing-with-overhead.txt: Load Balancing with Overhead Parameters (Accepted)
  • @mikeperry says: This is not done; Deferred until arti-dirauth; may become obsolete by smarter flag assigning before load balancing ✅
• 282-remove-named-from-consensus.txt: Remove "Named" and "Unnamed" handling from consensus voting (Accepted)
  • @dgoulet says: This is NOT implemented. We still have Named and Unnamed being handled by our voting code. And so, it has to stay in Accepted land. ✅
• 285-utf-8.txt: Directory documents should be standardized as UTF-8 (Accepted)
  • @dgoulet says: This is NOT implemented: tor#40131 and so it has to stay in Accepted land. ✅
• 327-pow-over-intro.txt: A First Take at PoW Over Introduction Circuits (Draft)
  • @mikeperry says: This is Finished.
  • (Next task 🏗️ is to review for accuracy then mark as Finished) ✅
• 329-traffic-splitting.txt: Overcoming Tor's Bottlenecks with Traffic Splitting (Needs-Revision)
  • @mikeperry says: This is Finished.
  • (Next task 🏗️ is to review for accuracy then mark as Finished) ✅
• 291-two-guard-nodes.txt: The move to two guard nodes (Needs-Revision)
  • @mikeperry says: This is done via consensus param (set to 2) ✅
• 292-mesh-vanguards.txt: Mesh-based vanguards (Accepted)
  • @mikeperry says: Should remain "Accepted" - it seems worthwhile to have arti provide it
  • (This is the one implemented in the vanguards controller)
  • Next step 🏗️: Maybe note as "finished" or turn it into a spec along with vanguards-lite?
• 296-expose-bandwidth-files.txt: Have Directory Authorities expose raw bandwidth list files (Open)
  • @dgoulet says: This is implemented. I moved it in Close state. ✔️
• 301-dont-vote-on-package-fingerprints.txt: Don't include package fingerprints in consensus documents (Open)
  • @nickm says: I'm pretty sure we did this? I can double-check.
  • @nickm says: No; this is not implemented. Let's mark as acccepted?
  • Accepted as !159 (merged). ✔️
• 309-optimistic-socks-in-tor.txt: Optimistic SOCKS Data (Open)
  • @dgoulet says: This is NOT implemented. ❌
• 311-relay-ipv6-reachability.txt: Tor Relay IPv6 Reachability (Accepted)
  • @dgoulet says: This is NOT implemented. ❌
• 312-relay-auto-ipv6-addr.txt: Tor Relay Automatic IPv6 Address Discovery (Accepted)
  • @dgoulet says: This is NOT implemented.❌
• 313-relay-ipv6-stats.txt: Tor Relay IPv6 Statistics (Accepted)
  • @dgoulet says: This is NOT implemented.❌
• 324-rtt-congestion-control.txt: RTT-based Congestion Control for Tor (Open)
  • @mikeperry says: This is Finished (and has been kept up to date with C-Tor)
  • (Next task 🏗️ is to review for accuracy then mark as Finished) ✅
• 331-res-tokens-for-anti-dos.md: Res tokens: Anonymous Credentials for Onion Service DoS Resilience (Draft)
  • definitely not built, @nickm got confused.❌
• 336-randomize-guard-retries.md: Randomized schedule for guard retries (Accepted)
  • @nickm says: I believe Arti does this.
  • Next task: double check, describe implementation status, mark FINISHED. (See !165 (merged))✔️
• 337-simpler-guard-usability.md: A simpler way to decide, "Is this guard usable?" (Accepted)
  • @nickm says: I believe Arti does this.
  • Next task: double check, describe implementation status, mark FINISHED. (See !165 (merged))✔️

We plan to implement this soon; it should be ACCEPTED:

• 340-packed-and-fragmented.md: Packed and fragmented relay messages (Open)
  • next action 🏗️: @dgoulet says: I can change that. I'm working on it and have already fixes for it.