Congestion control interacting with the path

[notBroman]

I'm trying to understand how the congestion control algos interact with the connection. I understand that the parameters are defined on the path not the connect using picoquic_path_t, does the CC algorithm change the path variables? How does this result in sending a different amount of packets?

I've looked through the documentation, but it only briefly goes over the pacing by using picoquic_get_earliest_cnx_to_wake(...). However I couldn't find any more in depth explanation on how the picoquic_path_t and cc algorithms are interacting.

I've tried looking through the code, but I am struggling to understand.

[huitema]

The CC normally uses two methods:

• directly write the variable path->cwin
• use the pacing API to set the pacing rate and the "quantum"

[huitema]

In the other direction, we have a callback API used by the transport to inform the CC when important events happen.