IETF Logo Mail Archive

Re: [tsvwg] a new method of congestion control

Mitchell Erblich <erblichs@earthlink.net> Mon, 05 June 2023 02:50 UTC

Return-Path: <erblichs@earthlink.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 749DBC14CE5E for <tsvwg@ietfa.amsl.com>; Sun, 4 Jun 2023 19:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net
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 lNnq33Pe5KDX for <tsvwg@ietfa.amsl.com>; Sun, 4 Jun 2023 19:50:27 -0700 (PDT)
Received: from mta-102a.earthlink-vadesecure.net (mta-102a.earthlink-vadesecure.net [51.81.61.66]) (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 E3B20C14F75F for <tsvwg@ietf.org>; Sun, 4 Jun 2023 19:50:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; bh=Lni+n9gv+AC91x8ohccUosBIxC/36nWSJLj5B6 suYkc=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1685933425; x=1686538225; b=VFjBf3+iYNrydnHx+/WQffunL776584rLE1D7vQrJBtkBjS8ZOKL8Gh +RTWikduUZjzUo7DcozyyyO/G7q/FiyghLL65DcVy/JaqOlrSJS2TdFSwNCMl+9etIbVcmy Mniz9hsQH8V2NcbtudCgpOR93sI+4CBa9+5EkB6USa+Th71CCLVeftiStmDswH2JUELSIi1 umH5MT4BWrCTpEdOP+g/vuQ/yQObu9mCPJ8fMltvF/W8h52Wz34TNX2Cz6zcX9S2SQwVtFP +Z6WZE4KxPvdDW1d3F6+XF80QrxHSJldMUlE41zFnDzjEmUqp8PAqJcZzUkxUyiY2M3wclS 24w==
Received: from [10.0.0.43] ([98.210.102.146]) by vsel1nmtao02p.internal.vadesecure.com with ngmta id dc3bb3c1-1765a3847ea25b15; Mon, 05 Jun 2023 02:50:25 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mitchell Erblich <erblichs@earthlink.net>
In-Reply-To: <CAA93jw6TJEciW8QhgbSe=0ZTk6njhpxMTQ3ETxzy73hhcP0yAw@mail.gmail.com>
Date: Sun, 04 Jun 2023 19:50:23 -0700
Cc: tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C21F06B7-79DE-4726-9DD7-D91BF9DB9AC5@earthlink.net>
References: <CAA93jw6TJEciW8QhgbSe=0ZTk6njhpxMTQ3ETxzy73hhcP0yAw@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.3124)
Authentication-Results: earthlink-vadesecure.net; auth=pass smtp.auth=erblichs@earthlink.net smtp.mailfrom=erblichs@earthlink.net;
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ZEd2Fv-hQZ7K5VziGUqrD6jqak4>
Subject: Re: [tsvwg] a new method of congestion control
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 02:50:32 -0000

Weird, In my Opinion (IMO),

	How do you separate out AI versus non-AI flows, so you can tailer one type network flow to AI aware applications?

	Is AI consuming even 20% of network bandwidth at this time?

	Isn’t Apple’s ?Siri? an AI application approaching 10 years of age, which I find far from perfect.

	It is like having a different Ethernet protocol for UDP versus TCP.

	The article must be missing critical information or the writer doesn’t understand TCP and/or CA.

Mitchell Erblich
erblichs@earthlink.net



> On Jun 4, 2023, at 5:53 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 
> announced by nvidia here:
> https://www.zdnet.com/article/nvidia-unveils-new-kind-of-ethernet-for-ai-grace-hopper-superchip-in-full-production/
> 
> I have no idea what an AI workload looks like, familiarity with a ton
> of DC l2 protocols, and there are hints in this post about telemetry.
> 
> Anyone have clue here?
> 
> -- 
> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos
>

v2.23.0 | Report a Bug | By Email