IETF Logo Mail Archive

Re: [tsvwg] a new method of congestion control

"touch@strayalpha.com" <touch@strayalpha.com> Mon, 05 June 2023 03:15 UTC

Return-Path: <touch@strayalpha.com>
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 02E86C151064 for <tsvwg@ietfa.amsl.com>; Sun, 4 Jun 2023 20:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.315
X-Spam-Level:
X-Spam-Status: No, score=-1.315 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 39FLCrhpMlza for <tsvwg@ietfa.amsl.com>; Sun, 4 Jun 2023 20:15:41 -0700 (PDT)
Received: from server217-2.web-hosting.com (server217-2.web-hosting.com [198.54.115.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B341BC14CF05 for <tsvwg@ietf.org>; Sun, 4 Jun 2023 20:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=LM7KGiRmAgtGZ0xnD5n46A1qwnWSA/ahYnepK8z6Kuw=; b=2rfqwEiVbu+VDCgFZGHMEWyZ3j 0jDn1lY1hQ0VOXIKwA3FoBjSWxlhvkJ7nkEB1yzGblqJk+IDMaZ4a66IVOmFlnyAP02/gCQu2H5tk C+yVxCwoiGJqfwMX/Y2SrsFtWDp+lWnnJMMaN9YlEyoz5m41LVNKymi7aSg4bFWFSVBg8kBXh7k+b DqxLwe3D4GPYJW2m/MbE6+4e8Qc6eR5Ps7pa/z9TxN9Z6Izjmmosskly25fLxuc0ypgy6ZMFPV9lF V32gtaNfbzFXySwTfXJNmmccXx9rITREHOjl+eivVH5sL4TolgARE6hef6Edh8jetKYsqWUhQiE/6 Qk0oAeMA==;
Received: from [172.58.208.6] (port=11222 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <touch@strayalpha.com>) id 1q60gw-00H3gS-OC; Sun, 04 Jun 2023 23:15:39 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_971C66BB-86BC-4C71-A272-90D17531B542"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <C21F06B7-79DE-4726-9DD7-D91BF9DB9AC5@earthlink.net>
Date: Sun, 04 Jun 2023 20:15:22 -0700
Cc: Dave Taht <dave.taht@gmail.com>, tsvwg IETF list <tsvwg@ietf.org>
Message-Id: <16922F7E-EED2-4298-98EC-AA7784A0D4AD@strayalpha.com>
References: <CAA93jw6TJEciW8QhgbSe=0ZTk6njhpxMTQ3ETxzy73hhcP0yAw@mail.gmail.com> <C21F06B7-79DE-4726-9DD7-D91BF9DB9AC5@earthlink.net>
To: Mitchell Erblich <erblichs@earthlink.net>
X-Mailer: Apple Mail (2.3731.600.7)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/3bjERrx97D4zeR2-A6Afnd34Lfw>
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 03:15:46 -0000

Ethernet has a LOT of extensions:

https://en.wikipedia.org/wiki/IEEE_802.1

Could this either be some subset of newer extensions or revival/vendor-specific variants of past attempts?

Joe

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Jun 4, 2023, at 7:50 PM, Mitchell Erblich <erblichs@earthlink.net> wrote:
> 
> 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