[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #33222 [Core Tor/Tor]: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests

#33222: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests
---------------------------+------------------------------------
 Reporter:  teor           |          Owner:  teor
     Type:  enhancement    |         Status:  assigned
 Priority:  Medium         |      Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor   |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:  ipv6, prop311  |  Actual Points:  1.1
Parent ID:  #33221         |         Points:  6
 Reviewer:  nickm          |        Sponsor:  Sponsor55-must
---------------------------+------------------------------------

Comment (by teor):

 Thanks for the review!

 I might be a bit busy next week with non-work tasks, but I'll try to do at
 least one revision.

 Replying to [comment:7 teor]:
 > It sends IPv4-only and IPv6-only extends on reachability circuits, to
 any third hop.
 >
 > Here's what we need to do before we merge:
 > * 4.2.1 Selecting the Final Extending Relay (this ticket)
 >   * 5. Declare Support for Subprotocol Version "Relay=3" (#33226)
 > * unit tests
 > * changes files
 >
 > Then we can iterate on the remaining work.

 My next priority is to:
 * Separate tor's IPv4 and IPv6 reachability flags (#34067)

 So we know that we're actually getting IPv6 connections. (I'm pretty sure
 we are now, but we don't want to accidentally break them.)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33222#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs