Improve visibility of IPv6 related settings

IPv6 related questions come up regularly, which is a good thing, because its adoption among relays can be improved.

There was some good stuff on the list (and probably also somewhere else) that could be added at our IPv6 FAQ entry or the [[TorRelayGuide#IPv6]]. (comparing both most of it is already there, maybe we instead should try to increase the visibility a bit more?) https://torproject.org/docs/faq.html.en#IPv6 https://torproject.org/docs/faq.html.en#IPv6Relay

related: legacy/trac#17811 (moved) (clients), see keywords

(assigning this to the relay guide to get another opinion and happily get it back for the website)

added component::community/relays in Legacy / Trac ipv6 in Legacy / Trac priority::low in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tor-relay in Legacy / Trac type::enhancement in Legacy / Trac labels

Replying to traumschule:

IPv6 related questions come up regularly, which is a good thing, because its adoption among relays can be improved.

There was some good stuff on the list

this content is already in the TorRelayGuide#IPv6

that could be added at our IPv6 FAQ entry

that would be a separate ticket/component

or the TorRelayGuide#IPv6. (comparing both most of it is already there, maybe we instead should try to increase the visibility a bit more?)

since I pointed the person directly to that content in https://lists.torproject.org/pipermail/tor-relays/2018-September/016223.html I don't think that in this particular case visibility is the problem

Trac:
Owner: Nusenu to N/A
Status: new to assigned

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

moved from legacy/trac#27753 (moved)

added Feature label and removed 1 deleted label

removed 1 deleted label

I'm closing this issue since we have covered IPv6 on community.tpo/relay.

closed