Re: [Congress] [tsvwg] New Version Notification for draft-scheffenegger-congress-rfc5033bis-00.txt

Matt Mathis <mattmathis@measurementlab.net> Fri, 17 February 2023 18:43 UTC

Return-Path: <mattmathis@measurementlab.net>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85F73C14F736 for <tsv-area@ietfa.amsl.com>; Fri, 17 Feb 2023 10:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=measurementlab-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjnUQt2W0PR0 for <tsv-area@ietfa.amsl.com>; Fri, 17 Feb 2023 10:43:30 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B284BC14CF17 for <tsv-area@ietf.org>; Fri, 17 Feb 2023 10:43:17 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id i9so1072276pgh.10 for <tsv-area@ietf.org>; Fri, 17 Feb 2023 10:43:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=measurementlab-net.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tmWzvZOTpnRniICZLAu+YB2hwmMvkrW2CXklnwxBg3k=; b=dBi7p/9lkIFVdIV63ZCOGhNVLBUrfCjmjiQ6OugukSCaEXvd9OhvoTBLdrBp/E+lpI /jE5hXlizYVUp6N9uUU8c1jCW3kkhzkbiIvTiww9aOIYvwzGoavCdxEqsHWkMaGqI6ZH BCPcRWcHajQPHv+/Gf+x5Xf4Ot487ltT89yuhYT32XMlrHbCcFHggZhVkZ9ZI+vcL+8N 151bZ0JGkvjyqY41JhskWuh6iID/Jm0PDE+MVcQleB3jqF1v11qoXkUlTuNns8BsPvE0 WHIBDuZyBqYLRVxX8qX18KuX9dAZrn6vlZJA7W2XVZB8p6cUvznQtVoZOYT6uZYu5Fw8 q03g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tmWzvZOTpnRniICZLAu+YB2hwmMvkrW2CXklnwxBg3k=; b=TL1/ifa+r4FD4X2WJ/0y0BGqE/UbrhRXXpXoq3FZwvB8pqxtjYx5jYDQIzxeXzmr0U 0h9DlB+EXvXBl8dCulHRNfe/HZzHZ7MhNBa2DTu0bxsM4mGeSf12EM6AP5Kvrt+J2sqX 0NE/22pob8KAZXzFOh23eoBzixGio6gBnxd8bL7TAYUldyjNFOx3QVWAMgDPqDWjAtUx oKyO3SAllyGTHiWH/l7UOSIApFQ62YQegVtFvG9sdk6hey/c1PWzWoSfKwaj/n8Jda/O JgGuxg7nI8evZlPQvLzNRIEFjCuMdgz7PLuWwx2vmXlni3cO5nRUNj6k74tS04go8Y2k gFtw==
X-Gm-Message-State: AO0yUKVZJc8w4Uag6GSi1mvIE/+F7mrsLo4nMyxIDoFuH58IZs6vFH7X 94g3JnWTMaenbUm4/beGGXnEzJDSuQHs9EH67y1ucQ==
X-Google-Smtp-Source: AK7set//PHXbXsQJ7FYttFKpBI+MIymso/ISqQ0P+/aG60wjjmeLAJ9ewAxE0YcuULXOTbZN2dJJ6uxb5CKW4gCVlSw=
X-Received: by 2002:a62:8144:0:b0:5aa:2216:5c55 with SMTP id t65-20020a628144000000b005aa22165c55mr477587pfd.35.1676659396863; Fri, 17 Feb 2023 10:43:16 -0800 (PST)
MIME-Version: 1.0
References: <80ccaea8-1813-06ff-6b0f-9f66e2a8a00f@gmx.at> <CAA93jw63z6En6a_EteQxc70jJkfSb3QgXNCeJwRyamFB1Ae7eA@mail.gmail.com>
In-Reply-To: <CAA93jw63z6En6a_EteQxc70jJkfSb3QgXNCeJwRyamFB1Ae7eA@mail.gmail.com>
From: Matt Mathis <mattmathis@measurementlab.net>
Date: Fri, 17 Feb 2023 10:43:05 -0800
Message-ID: <CAEsRLK8FYE8Rru0+OHK4H4Cfnz-fW_Lg+ho-y9_uJK2oQpdNtA@mail.gmail.com>
Subject: Re: [Congress] [tsvwg] New Version Notification for draft-scheffenegger-congress-rfc5033bis-00.txt
To: Dave Taht <dave.taht@gmail.com>
Cc: rscheff@freebsd.org, congress@ietf.org, Martin Duke <martin.h.duke@gmail.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Reese Enghardt <ietf@tenghardt.net>, Eric Kinnear <ekinnear@apple.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, tsv-area@ietf.org, "tcpm@ietf.org" <tcpm@ietf.org>, quic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c2845405f4e9af91"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/BabI_YomJ9dRwO-nuOWfUf5LNog>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2023 18:43:34 -0000

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.taht@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.ietf@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
> Congress@ietf.org
> https://www.ietf.org/mailman/listinfo/congress
>