Re: [tsvwg] a new method of congestion control

Mitchell Erblich <erblichs@earthlink.net> Mon, 05 June 2023 04:14 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 4A659C14CF1A for <tsvwg@ietfa.amsl.com>; Sun, 4 Jun 2023 21:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_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=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 A9-1EMUDH1A0 for <tsvwg@ietfa.amsl.com>; Sun, 4 Jun 2023 21:14:31 -0700 (PDT)
Received: from mta-202a.earthlink-vadesecure.net (mta-202a.earthlink-vadesecure.net [51.81.232.240]) (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 EAC37C14CEFC for <tsvwg@ietf.org>; Sun, 4 Jun 2023 21:14:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; bh=b6FmdDNbHyKrMSZ+2IPs8Jtx39qpx/JjAUSAF/ yZkro=; 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=1685938451; x=1686543251; b=FkB/6uo03Bc16Ya38l8LVFv0sZzpQ688g7gype+UyRcXWv+C7tZzW1V DiFXrnbHckwOJEILTxbSoWw/toJ5XVK6HSA0gzLCe9K1aMXE+oSouFnEcBRnufAFUaJ0ya7 CNdxQd22M26vzFn2rxcwSXcoFmf6IGeamAtlzMKLEpfpClussDgjZ+rndXH2PlerZIUFeFa yMLi7W4FNryoK4QBomlKfWfFkIG2Yfh2SLmNa87SWU5UXzFdMlS0Ff1C9xDnXVhyqcVw9qA f1/u83vW0IacIoQgZ9BmkB92GXynnBvScBAeTLfd6RTOD8QBOUZlJRqY4MT/vdFtHy1jrnA 7yA==
Received: from [10.0.0.43] ([98.210.102.146]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id 460a13d9-1765a816d2d361a9; Mon, 05 Jun 2023 04:14:11 +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: <16922F7E-EED2-4298-98EC-AA7784A0D4AD@strayalpha.com>
Date: Sun, 04 Jun 2023 21:14:10 -0700
Cc: Dave Taht <dave.taht@gmail.com>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EB4FCC9-99F3-4E29-BB12-22B2DAC9AB95@earthlink.net>
References: <CAA93jw6TJEciW8QhgbSe=0ZTk6njhpxMTQ3ETxzy73hhcP0yAw@mail.gmail.com> <C21F06B7-79DE-4726-9DD7-D91BF9DB9AC5@earthlink.net> <16922F7E-EED2-4298-98EC-AA7784A0D4AD@strayalpha.com>
To: touch@strayalpha.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/AC-0wxhTr3Qk9NbAGZuvCd_jwTQ>
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 04:14:36 -0000

Joe,

	One would need to duplicate Appropriate Byte Counting (ABC) by Allman / Pacing in Ethernet, but why would you want to when you already had it within a experimental CA in TCP?

	If you flood packets and a intermediate system (router) did a tail-drop or a random-early drop, you still drop packets.

	If you have out-of-orderness that jumps because… then you drop packets

	If you fragment and drop a fraction of the packet you drop…
	
	If you re-route because of the change of the routing table and you re-order, you drop,,,,

	Yes,we have selective asks…. But not in Ethernet or IPvX.

	Ethernet supports two sizes of IP (IPv4 and IPv6) … do you do something special for a fraction of the packets in your network?

	You need to have 1 hop networks … Again ,,, weird…

	Can’t guarantee no drop of packets… Yes, you can mitigate if and if  and if… but is’t it just worth to use Selective Acks and other existing RFCs 

	Why create a wheel when it already exists???


Group,,, Sorry, about the verbose response….

Mitchell Erblich
erblichs@earthlink.net



> On Jun 4, 2023, at 8:15 PM, touch@strayalpha.com wrote:
> 
> Ethernet has a LOT of extensions:
> 
> IEEE 802.1
> en.wikipedia.org
> <wikipedia.png>
> 
> 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
>>> 
>> 
>