[tahoe-lafs-trac-stream] [Tahoe-LAFS] #867: use ipv6

[Tahoe-LAFS]

#867: use ipv6
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  ClashTheBunny
         Type:           |     Status:  assigned
  enhancement            |
     Priority:  major    |  Milestone:  undecided
    Component:  code-    |    Version:  1.5.0
  network                |   Keywords:  ipv6 firewall twisted foolscap
   Resolution:           |  test-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 The main remaining issue is that Foolscap needs to support it:
 http://foolscap.lothar.com/trac/ticket/155

 The last time I looked at this, Foolscap was blocked on a different
 Twisted bug ([https://twistedmatrix.com/trac/ticket/8014 twisted#8014]),
 which is preventing us from using a !HostnameEndpoint to connect. We
 really want to use !HostnameEndpoint because they handle A **or** AAAA
 records in DNS, so you can publish a normal hostname in your FURL and have
 clients connect over whichever of v4/v6 both ends support.

 The consequence is that the process emits unhandled
 {{{AlreadyCalledError}}} failures when there are multiple connection hints
 and some of them don't answer right away. This happens all the time with
 automatically-generated FURLs, since they include non-routable (local)
 addresses and other unconnectable things. The errors cause Foolscap's unit
 tests to fail, and would show up as errors in the logs for a real
 application (probably causing Tahoe's unit tests to fail too, although
 maybe there we can constraint the FURLs to not hit this case).

 I haven't seen any movement on that ticket since I filed it 5 months ago,
 but it's possible that other changes in Twisted may have fixed the
 problem. The next step will be to re-introduce the !HostnameEndpoint
 change and see if the Foolscap tests pass or fail with the latest version
 of Twisted.

 There are probably some other cosmetic things that need updating: we need
 to make sure the FURL parser can handle dotted-quad IP addresses, and
 Tahoe has a handful of places that want to display IP addresses that may
 need changes.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/867#comment:26>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage