[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33235 [Core Tor/Tor]: Proposal 312: 3.2.1. Test Address torrc Option Configurations
#33235: Proposal 312: 3.2.1. Test Address torrc Option Configurations
---------------------------+------------------------------------
Reporter: teor | Owner: teor
Type: task | Status: assigned
Priority: Medium | Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: prop312, ipv6 | Actual Points:
Parent ID: #33049 | Points: 1
Reviewer: | Sponsor: Sponsor55-must
---------------------------+------------------------------------
Description changed by teor:
Old description:
> This ticket depends on IPv6 Addresses in #33233, and automatic IPv6
> ORPorts in #33246.
>
> We should support the following combinations of address literals and
> hostnames:
>
> Legacy configurations:
> A. No configured Address option
> B. Address IPv4 literal
> C. Address hostname (use IPv4 and IPv6 DNS addresses)
>
> New configurations:
> D. Address IPv6 literal
> E. Address IPv4 literal / Address IPv6 literal
> F. Address hostname / Address hostname (use IPv4 and IPv6 DNS
> addresses)
> G. Address IPv4 literal / Address hostname (only use IPv6 DNS
> addresses)
> H. Address hostname (only use IPv4 DNS addresses) / Address IPv6
> literal
>
> If we can't find an IPv4 or IPv6 address using the configured Address
> options:
> * No IPv4: guess IPv4, and its reachability must succeed.
> * No IPv6: guess IPv6, publish if reachability succeeds.
>
> Combinations A and B are the most common legacy configurations. We want
> to support the following outcomes for all legacy configurations:
> * automatic upgrades to guessed and reachable IPv6 addresses,
> * continuing to operate on IPv4 when the IPv6 address can't be guessed,
> and
> * continuing to operate on IPv4 when the IPv6 address has been guessed,
> but it is unreachable.
>
> See proposal 312, section 3.2.1, testing notes:
> https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-
> ipv6-addr.txt#n270
New description:
This ticket depends on IPv6 Addresses in #33233, and automatic IPv6
ORPorts in #33246. These tests should be in CI, or they should be repeated
after each change.
We should support the following combinations of address literals and
hostnames:
Legacy configurations:
A. No configured Address option
B. Address IPv4 literal
C. Address hostname (use IPv4 and IPv6 DNS addresses)
New configurations:
D. Address IPv6 literal
E. Address IPv4 literal / Address IPv6 literal
F. Address hostname / Address hostname (use IPv4 and IPv6 DNS addresses)
G. Address IPv4 literal / Address hostname (only use IPv6 DNS addresses)
H. Address hostname (only use IPv4 DNS addresses) / Address IPv6 literal
If we can't find an IPv4 or IPv6 address using the configured Address
options:
* No IPv4: guess IPv4, and its reachability must succeed.
* No IPv6: guess IPv6, publish if reachability succeeds.
Combinations A and B are the most common legacy configurations. We want to
support the following outcomes for all legacy configurations:
* automatic upgrades to guessed and reachable IPv6 addresses,
* continuing to operate on IPv4 when the IPv6 address can't be guessed,
and
* continuing to operate on IPv4 when the IPv6 address has been guessed,
but it is unreachable.
See proposal 312, section 3.2.1, testing notes:
https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-
ipv6-addr.txt#n270
--
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33235#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs