atagar points out that the control protocol still lets you ask for stuff in v2-formatted ways, and I believe that is still working. So maybe not all of v2 is in the attic yet.
Is this still the case? If so, we should probably remove the code that gives out version 2 descriptors to controllers. And the code that lets controllers ask for version 2 descriptors. And the respective parts in control-spec. Version 2 is dead.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
I don't think it's such a good idea to drop that code. (This isn't v2 descriptors, btw. It's v2-style routerstatus lines. They aren't taken directly from the networkstatus; they're generated based on our opinions of the nodes.)
Controller are allowed to use this info, and it's a comparatively small amount of code to keep it for now IMO. I'd like to have a better node-status export format, but it's not trivial to drop the "v2 routerstatus" format right now.
From a spec pov however, it would be nice to take just the v2 routerstatus format, document it by comparison to the v3 routerstatus format, and put that in control-spec.txt or in an appendix to it, so that we can retire dir-spec-v2.txt.
The proper fix is not to stop providing the new format, but rather to add support for providing the new format.
Trac: Summary: Stop giving out version 2 descriptors to controllers to Stop giving out version 2-style routerstatuses to controllers Sponsor: N/AtoN/A Resolution: N/Ato wontfix Severity: N/Ato Normal Status: new to closed Reviewer: N/AtoN/A