Dave, I'd be curious to know what you think is the proper shape for either of the problems that you pose. Both have deep ambiguities/conflicts in the definition of correct, in the sense that solutions that would be considered optimal by some audiences call for behaviors that would be considered anti-optimal by others.
Thanks, --MM-- Evil is defined by mortals who think they know "The Truth" and use force to apply it to others. On Fri, Feb 17, 2023 at 9:16 AM Dave Taht <dave.t...@gmail.com> wrote: > wow! what a blast from the past, and what sadness I felt when > stumbling across Sally Floyd's name in the credits. > > My primary comment is that I wish somehow, in the IETF, we attempted > to address the congestion control problems our wireless transports > have, as that seems to be the principal means of users' access to the > internet. > > Secondary comment is what I always harp on, in aiming for an internet > that can safely and reliably transport videoconferencing and gaming > traffic while duking it it out with more aggressive capacity seeking > traffic. > > > On Fri, Feb 17, 2023 at 7:41 AM Scheffenegger, Richard <rs.i...@gmx.at> > wrote: > > > > Hello, > > > > In order to facilitate the github based editorial process of a revised > > RFC5033 document that outlines the current best practises when it comes > > to designing new congestion control mechanisms, I want to invite > > everyone who has commented across various lists and in meetings, to > > raise issues and contribute text here: > > > > > > https://rscheff.github.io/rfc5033bis > > > > https://github.com/rscheff/rfc5033bis/issues > > > > > > As the home for this work has not yet fully formed yet, I created this > > as an individual draft. There are no text changes in rfc50333bis-00 > > compared to rfc5033, only minor editorial changes due to the use of > > markdown for the body of the document. > > > > A number of individuals have already expressed their interest in > > contributing improvements to this document. I am looking forward to > > those contributions - either as issues and discussion points, or as > > concrete text snippets - in order to reflect the current best > > understanding of the congestion control environment. > > > > > > A new version of I-D, draft-scheffenegger-congress-rfc5033bis-00.txt > > has been successfully submitted by Richard Scheffenegger and posted to > > the IETF repository. > > > > Name: draft-scheffenegger-congress-rfc5033bis > > Revision: 00 > > Title: Specifying New Congestion Control Algorithms > > Document date: 2023-02-17 > > Group: Individual Submission > > Pages: 11 > > URL: > > > https://www.ietf.org/archive/id/draft-scheffenegger-congress-rfc5033bis-00.txt > > Status: > > > https://datatracker.ietf.org/doc/draft-scheffenegger-congress-rfc5033bis/ > > Html: > > > https://www.ietf.org/archive/id/draft-scheffenegger-congress-rfc5033bis-00.html > > Htmlized: > > > https://datatracker.ietf.org/doc/html/draft-scheffenegger-congress-rfc5033bis > > > > > > Abstract: > > The IETF's standard congestion control schemes have been widely shown > > to be inadequate for various environments (e.g., high-speed > > networks). Recent research has yielded many alternate congestion > > control schemes that significantly differ from the IETF's congestion > > control principles. Using these new congestion control schemes in > > the global Internet has possible ramifications to both the traffic > > using the new congestion control and to traffic using the currently > > standardized congestion control. Therefore, the IETF must proceed > > with caution when dealing with alternate congestion control > > proposals. The goal of this document is to provide guidance for > > considering alternate congestion control algorithms within the IETF. > > > > > > > > > > The IETF Secretariat > > > > > -- > This song goes out to all the folk that thought Stadia would work: > > https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz > Dave Täht CEO, TekLibre, LLC > > -- > Congress mailing list > congr...@ietf.org > https://www.ietf.org/mailman/listinfo/congress >
