Opened 9 months ago

Last modified 5 months ago

#33247 assigned enhancement

Prop 312: 3.2.7. Publish IPv4 Descriptor on Guessed IPv6 Reachability Failure

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop312, ipv6, 044-deferred
Cc: Actual Points:
Parent ID: #33049 Points: 0.5
Reviewer: Sponsor: Sponsor55-must

Description (last modified by teor)

Depends on disabling descriptor publication on reachability
failures in #33223.

Should be done after the first IPv6 address guessing feature: #33238
or #33240.

If both reachability checks succeed, relays should publish their IPv4 and IPv6 ORPorts in their descriptor.

If only the IPv4 ORPort check succeeds, and the IPv6 address was guessed
(rather than being explicitly configured), then relays should:

  • publish their IPv4 ORPort in their descriptor,
  • stop publishing their IPv6 ORPort in their descriptor, and
  • log a notice about the failed IPv6 ORPort reachability check.

See proposal 312, section 3.2.7, Guessed IPv6 Reachability Failure part:

Child Tickets

Change History (5)

comment:1 Changed 6 months ago by teor

Description: modified (diff)

comment:2 Changed 6 months ago by teor

Description: modified (diff)

comment:3 Changed 6 months ago by teor

Owner: teor deleted

Un-assign myself from future Sponsor 55 tasks.

comment:4 Changed 5 months ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

comment:5 Changed 5 months ago by nickm

Milestone: Tor: unspecified

Bulk-move prop311 and prop312 to 0.4.5

Note: See TracTickets for help on using tickets.