mirrors/arti.git/crates/tor-circmgr/src/build.rs, branch arti-v1.4.6

proto: Refactor cc fallback.

2025-06-10T15:52:28Z

The fallback CC algorithm is _always_ fixed-window, and we should only use it when the selected CC algorithm is not supported.

Move responsibility for choosing extensions into tor-proto

2025-06-10T15:52:28Z

Now tor-circmgr no longer needs to check which Protover capabilities are enabled, or construct a separate CircParameters for each hop. Instead, tor-proto decides whether to use the fallback CC mode, based on whether the target supports FLOWCTRL_CC. Closes #1967.

proto: Provide and use a create_firsthop() wrapper too.

2025-04-28T17:35:06Z

tor-proto: New extend() to pick between ntor and ntor3

2025-04-28T17:24:11Z

In the future, when we add more circuit handshakes (PQ anyone?) we'll want to have the logic for choosing which to use be unified. Almost nobody calling tor-proto should need to care which circuit handshake is going to be used. Closes #1970.

tor-circmgr: put vegas cc in `CircParameters` behind `if false`

2025-04-23T20:48:35Z

This means that even with the "flowctl-cc" feature enabled, we shouldn't try to negotiate congestion control.

tor-circmgr: only use congestion control if "flowctl-cc" feature is enabled

2025-04-23T18:39:16Z

tor-circmgr: switch from `supports_{known,named}_subver()`

2025-04-23T18:38:25Z

circ: Don't pin CC algorithm to FixedWindow anymore

2025-04-23T18:36:28Z

Circuit handshake negotiation for congestion control has been added in previous commit so stop pinning the algorithm. This commit marks the start of congestion control usage by arti client. Closes #1817 Signed-off-by: David Goulet

circ: Apply possible subprotocol changes to circ params

2025-04-23T18:36:28Z

Congestion control can change the circuit parameters if the relay we are negotiating with doesn't support FlowCtrl=2. This commit adds a function in the circuit builder that will apply any changes to the circuit parameters of the hop based on the hop protocol values. For now, only congestion control applies. Part of #1817 Signed-off-by: David Goulet

circ: Remove CircParameters reference in call stack

2025-04-23T18:36:28Z

This avoids cloning the object and instead allows us to have a CircParameters per hop on the circuit path. This will come handy with congestion control where each hop might have different congestion control parameters. Part of #1817 Signed-off-by: David Goulet