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

[Tahoe-LAFS]

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

 * cc: tahoe-lafs.org@… (added)


Old description:

> Shawn Willden points out that IPv6 is a likely way to deal with the
> servers-behind-NAT problem (#169, #445, #49, #50), since a lot of ISPs
> offer v6 tunnel services these days, which effectively gives the server
> host a publically-reachable v6 address.
>
> To make this work, we need a couple of things, probably in the following
> order:
>
>  * python must handle v6 addresses, in the {{{socket}}} module
>  * twisted must handle v6 addresses: connecting to them, reporting them
> when asking a socket who it is connected to, and enumerating them on
> listenable interfaces. The existing {{{IPv4Address}}} class must grow a
> corresponding {{{IPv6Address}}} partner.
>  * foolscap must handle them: putting them in connection hints
> ([http://foolscap.lothar.com/trac/ticket/60 foolscap#60] has some notes
> on formats), connecting to them, etc
>  * tahoe must handle them: formatting them into Welcome page listings,
> passing them through the Introducer without problems, logging them
> correctly
>
> Let's collect pointers to other tickets (especially the twisted ones) and
> progress reports here.

New description:

 Shawn Willden points out that IPv6 is a likely way to deal with the
 servers-behind-NAT problem (#169, #445, #49, #50), since a lot of ISPs
 offer v6 tunnel services these days, which effectively gives the server
 host a publically-reachable v6 address.

 To make this work, we need a couple of things, probably in the following
 order:

  * python must handle v6 addresses, in the {{{socket}}} module
  * twisted must handle v6 addresses: connecting to them, reporting them
 when asking a socket who it is connected to, and enumerating them on
 listenable interfaces. The existing {{{IPv4Address}}} class must grow a
 corresponding {{{IPv6Address}}} partner.
  * foolscap must handle them: putting them in connection hints
 ([http://foolscap.lothar.com/trac/ticket/60 foolscap#60] has some notes on
 formats), connecting to them, etc
  * tahoe must handle them: formatting them into Welcome page listings,
 passing them through the Introducer without problems, logging them
 correctly

 Let's collect pointers to other tickets (especially the twisted ones) and
 progress reports here.

--

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