[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):

 Replying to [comment:37 lpirl]:

 > Does it actually matter to have proper Endpoints (as a user: never
 cared)?
 > Do Tahoe users ever come in direct contact with Twisted (as a user:
 don't want to)?
 > But your point is definitely to consider and maybe a show stopper for
 `tcp4:`.

 Well, it's nice to be able to say "for more complex situations, read the
 Twisted endpoint docs, because --port is really just an endpoint string",
 and delegate all that documentation job to the Twisted folks.

 > Yes, IMHO the automatic mode should always be default unless explicitly
 configured otherwise.
 > `tahoe create-node --port …` could use the same delimiter as `tub.port`
 for consistency.

 Yeah. Ok, so I think we can say that `--listen=tcp` (which is the default)
 will mean "listen on both v4 and v6, whichever is available", and it can
 cause multiple endpoint strings to get written into tahoe.cfg.

 > Speaking of file system paths (mind Windows), there are not much
 delimiters we can use while maintaining full compatibility with all
 possible paths. It's probably inevitable to choose "just any".

 Good point. We'll just document that some unusual endpoint strings won't
 work, if their internal characters are mistaken as `tub.port` delimiters.

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