The NORM (NACK-Oriented Reliable Multicast) protocol (RFC 5740) implements a form of TCP-Friendly congestion control. An open-source implementation is available at:
https://github.com/USNavalResearchLaboratory/norm The implementation provides for message delivery in a couple of different forms in addition to bulk content transfer and a number of controls are available for customizing flow control including application-controlled positive acknowledgement and reliability mechanisms including options for hybrid packet erasure FEC coding / ARQ. Incidentally, it can also work a reliable UDP-based unicast protocol with some advantages for some use cases and network environments. Just pointing it out as a candidate for where multicast and congestion control may be needed. Best regards, Brian On 12/18/22, 2:12 AM, "routing-discussion on behalf of Jonathan Morton" <[email protected] <mailto:[email protected]> on behalf of [email protected] <mailto:[email protected]>> wrote: > On 17 Dec, 2022, at 4:32 pm, Jeffrey (Zhaohui) Zhang > <[email protected] <mailto:[email protected]>> > wrote: > > - There are situations where a non-TCP based solution is needed even when a > parallel TCP-based option is also present, so we can not simply disallow the > former. We can discuss examples separately (one example is actually PIM as > BIER overlay vs mLDP/BGP as BIER overlay). There are also congestion control algorithms that don't rely on an underlying TCP session, such as TFRC (TCP Friendly Rate Control). Possibly these could be applied to existing protocols. - Jonathan Morton _______________________________________________ routing-discussion mailing list [email protected] <mailto:[email protected]> https://www.ietf.org/mailman/listinfo/routing-discussion <https://www.ietf.org/mailman/listinfo/routing-discussion>
