Re: [tor-bugs] #33235 [Core Tor/Tor]: Proposal 312: 3.2.1. Test Address torrc Option Configurations

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33235 [Core Tor/Tor]: Proposal 312: 3.2.1. Test Address torrc Option Configurations

[Tor Bug Tracker & Wiki]

#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
---+

Old description:

> Once we have implemented IPv6 Addresses in #33233, and automatic IPv6
> ORPorts in #33246, tor should support the following Address
> configurations:
>   A. IPv4 Address / hostname (for IPv6 only),
>   B. IPv6 Address / hostname (for IPv4 only),
>   C. IPv4 Address only / try to guess IPv6, then check its reachability
>  (see section 4.3.1 in [Proposal 311: Relay IPv6 Reachability]), and
>   D. IPv6 Address only / guess IPv4, then its reachability must succeed.
> There are also similar configurations where a hostname is configured, but
> it only provides IPv4 or IPv6 addresses.
>
> Combination C is the most common legacy configuration. We want to
> support the following outcomes for 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.

 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

--

Comment (by teor):

 Update proposal and ticket.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33235 [Core Tor/Tor]: Proposal 312: 3.2.1. Test Address torrc Option Configurations

[Tor Bug Tracker & Wiki]

#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
---+

Old description:

> Tor should support the following Address configurations:
>   A. IPv4 Address / hostname (for IPv6 only),
>   B. IPv6 Address / hostname (for IPv4 only),
>   C. IPv4 Address only / try to guess IPv6, then check its reachability
>  (see section 4.3.1 in [Proposal 311: Relay IPv6 Reachability]), and
>   D. IPv6 Address only / guess IPv4, then its reachability must succeed.
> There are also similar configurations where a hostname is configured, but
> it only provides IPv4 or IPv6 addresses.
>
> Combination C is the most common legacy configuration. We want to
> support the following outcomes for 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:

 Once we have implemented IPv6 Addresses in #33233, and automatic IPv6
 ORPorts in #33246, tor should support the following Address
 configurations:
   A. IPv4 Address / hostname (for IPv6 only),
   B. IPv6 Address / hostname (for IPv4 only),
   C. IPv4 Address only / try to guess IPv6, then check its reachability
  (see section 4.3.1 in [Proposal 311: Relay IPv6 Reachability]), and
   D. IPv6 Address only / guess IPv4, then its reachability must succeed.
 There are also similar configurations where a hostname is configured, but
 it only provides IPv4 or IPv6 addresses.

 Combination C is the most common legacy configuration. We want to
 support the following outcomes for 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

--

Comment (by teor):

 Note dependencies on #33233 and #33246.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs