[tor-bugs] #20916 [Core Tor/Tor]: Inconsistent IPv6 address between consensus and microdescriptor
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Mar 8 00:37:30 UTC 2017
#20916: Inconsistent IPv6 address between consensus and microdescriptor
-------------------------------------------------+-------------------------
Reporter: teor | Owner: teor
Type: defect | Status:
| assigned
Priority: Medium | Milestone: Tor:
| 0.3.1.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: needs-proposal, ipv6, regression, | Actual Points:
triage-out-030-201612 |
Parent ID: | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):
* keywords: ipv6, regression, triage-out-030-201612 => needs-proposal,
ipv6, regression, triage-out-030-201612
* owner: => teor
* status: new => assigned
Comment:
This also makes it easier for IPv6 clients to bootstrap, and makes happy-
eyeballs-style IPv6 detection possible.
We'll need a short proposal for this explaining why it will work (and why
it gets better once we have consensus diffs).
One decision will be:
* do we move IPv6 addresses from the microdesc to microconsensus in one
consensus method?
* (clients will be fine, back to 0.2.8 where we made IPv6 from the
consensus work)
* or, do we have one method to add them to the microconsensus, and another
to remove them from the microdesc in a later release?
(The staged option seems much more sensible, but maybe we could make them
N & N+1 in the same release, in case we need to run with both for a while
due to an unexpected bug.)
Some tools and external code might need to adapt. But much external code
uses the full consensus anyway.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20916#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list