Removal of fast increase, making it more rate-based, and the general change of the the delay-based approach, maybe we should actually call this also differently. It's definitely not only a bis where you try to fix some issues. It's really more a redesign. If you still want to obsolete the old scream draft, I propose to call this algorithm SCREAMv2.
Yes, it is actually a major redesign. In the github code it named ScreamV2Tx.cpp. I don't have a very strong opinion, which is the preferred, seen from an IETF perspective ?
Removal of fast increase, making it more rate-based, and the general change of the the delay-based approach, maybe we should actually call this also differently. It's definitely not only a bis where you try to fix some issues. It's really more a redesign. If you still want to obsolete the old scream draft, I propose to call this algorithm SCREAMv2.