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

[tahoe-lafs]

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

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.

--

Comment (by davidsarah):

 The relevant Twisted ticket now seems to be
 [http://twistedmatrix.com/trac/ticket/5085], which is fixed.

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