[Congress] Congress - Congestion Control - Combined Network QOS Routing Table Tree-Swarm - Quality of Service Protocol & the TCP & UDP & QUICC Protocols
Duke Abbaddon <duke.abbaddon@gmail.com> Wed, 22 February 2023 09:31 UTC
Return-Path: <duke.abbaddon@gmail.com>
X-Original-To: congress@ietfa.amsl.com
Delivered-To: congress@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEEAEC1516FF for <congress@ietfa.amsl.com>; Wed, 22 Feb 2023 01:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=gmail.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 ibJP3XhIuBgV for <congress@ietfa.amsl.com>; Wed, 22 Feb 2023 01:31:16 -0800 (PST)
Received: from mail-qv1-xf43.google.com (mail-qv1-xf43.google.com [IPv6:2607:f8b0:4864:20::f43]) (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 529EFC169509 for <congress@ietf.org>; Wed, 22 Feb 2023 01:31:16 -0800 (PST)
Received: by mail-qv1-xf43.google.com with SMTP id ev13so7991793qvb.10 for <congress@ietf.org>; Wed, 22 Feb 2023 01:31:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1677058275; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=NJDMe/5yfOiKllAkWyOnDNyftkKs1z3dYFyIPFi5g30=; b=JED+oYq9MeYe+q2x8QaOWz5DgeWzPrUXm+rfP669YycyFV8xhMRxjNhYscfYVn9CrH 3IaOryVA/LhsStIPgAlow7FH3AEa+3hhkRH2YJQyT/tucKW8Nt15SGlnOkmmnA/Uv03Q rFkmQPhC7ZoRgpFe/o3Vxk+scvp1g1C8O9luXRYQkf6jsr+a180HVQQEdjQ0qeCdlbYH azdpoti9MCZAHNI7onldEL6ojio3GH5S4xCoS7WEQs3SnaY3ZfrU4rvQbTknh1Qzuzoa zVwumVzQeUNPmvWMtR5NO2VSmqCRkGoLvJcAU7vafurGhKO+LNQfPB7HSfPw+V+qOsTs 9g0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677058275; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=NJDMe/5yfOiKllAkWyOnDNyftkKs1z3dYFyIPFi5g30=; b=q9uIiwSh5oSULmwNM4t+1hKD6tf9Y2GFYzM0FwmHfDrMZB/uJGu46y0HMsko8t3fiP QbB8ABGfP80ayEeU5qsMAIW+dNiMIq533oV/EE8Z8eMk0xLX9bWW+8/Y/F2a401FHNwx 87DPP2S+wYySS8YoNV2PCqECEoQj5LvNBgIr0X4+FZ3DtPBIKE8zok08qPJEzhgVolG3 bGNkz5hpOyvhPtgxPvsIF4BOVVHVDrOqwc8vDZmZQiV0eyST303/v5JFdZrKpMgcls4a EVMZEAlGgB2T6mkhT6GRL6VEvaeiRzPG355o7U1wzhRlytBthBNokl/nMZ58aOBElUpD lUtQ==
X-Gm-Message-State: AO0yUKUV4DEE6h3NqxTFSvip1Z/VXt1s92jewsLI/qd9amuMUw257pN5 2UV1ADvRYK98Bmsdxdmymxfud57fR+CQj3yYfhbOic/7gahqrg2f
X-Google-Smtp-Source: AK7set/DAId3r0m7kWIhg/UeapchgGjEpKHHwb4jwgTFW/QvUZgNS9M+i3OxgH24sfGKtFJYFTZPScseIpUyo1PIM4A=
X-Received: by 2002:a0c:8ec6:0:b0:56e:9bfe:c503 with SMTP id y6-20020a0c8ec6000000b0056e9bfec503mr1290369qvb.85.1677058274532; Wed, 22 Feb 2023 01:31:14 -0800 (PST)
MIME-Version: 1.0
From: Duke Abbaddon <duke.abbaddon@gmail.com>
Date: Wed, 22 Feb 2023 09:31:12 +0000
Message-ID: <CAHpNFcMORyYrsH=J6DyrfGYNL95Pc1eCkK=uYO5aiHM_YSExxw@mail.gmail.com>
To: congress@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/congress/679n0VG-rmos-Nhfx7kXZn3IdBs>
Subject: [Congress] Congress - Congestion Control - Combined Network QOS Routing Table Tree-Swarm - Quality of Service Protocol & the TCP & UDP & QUICC Protocols
X-BeenThere: congress@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussions about the CONGestion RESponse and Signaling \(CONGRESS\) Working Group" <congress.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/congress>, <mailto:congress-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/congress/>
List-Post: <mailto:congress@ietf.org>
List-Help: <mailto:congress-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/congress>, <mailto:congress-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2023 09:31:21 -0000
Quality of Service Protocol & the TCP & UDP & QUICC Protocols : https://www.ietf.org/archive/id/draft-scheffenegger-congress-rfc5033bis-00.txt * Processor Model for TCP, UDP & QUICC : (c)RS To put TCP, UDP & QUICC in a proper place in your minds for application, Think about Applying them to processors; Particularly Neuromorphic, ML & GPU/CPU! How exactly? Address space modelling for data transfer: Between RAM, HDD/SDD & CPU & Internally mapping across cache & Sparse Model NAND Gates. In the situation internal to Device Gates & Logic Circuits; We map address spaces across the processor, We internalize the location logic as a network & utilise TCP, UDP & QUICC, We do not need the sending strategy of Data Transfer to be Random; Random wastes Bandwidth! But we do need a QOS Data Transfer policy & Networking Tactics! Why ? Not all processor functions are directly connected in MultiChip & 3D Model Processor. * By thinking about the Processor Model for TCP, UDP & QUICC : (c)RS We soon find the best light TCP, UDP & QUICC Network Strategy. Think about this model designing the Network Protocols RS * "Kevin Cisco-Kevin Date: Tue, 21 Feb 2023 08:32:03 -0800 Subject: Re: To think about the Network Model : Processor Model for TCP, UDP & QUICC : (c)RS What we really need is a transfer layer mechanism modeled after Swarm where packets are broken up into chunks and reassembled after handshaking. But we don't live in that world." Kevin Suggests we think about Swarm : RS : What do i think on average (Swarm) I think that Swarm; Multi Target Networking is a primary method under consideration for QUICC & UDP & NTP Responses, Swarm is high noise; High Volume Send & Receive, With alteration though Statistical & Machine rout optimisation... That bandwidth cost reduces, ML : Neural network, Send, Receive & Confirm, Swarm, In effect on globally predictable commodities such as: NTP, DNS (popular), News & Decetralised command... Can work! Network Command requires directly applied logic; What i mean is : Confirmed Command & Reception affirmation & Action! So i propose the following: Combined Network QOS Routing Table Tree-Swarm : CNetQSRT-Tree-Sw : Rupert S 2023-02 Swarm:ML (Known Receiver : Known Sender) QOS NTP DNS Global Submit Network Tunneling, For example: Torado, Large Download Acceleration Secure Network Tunneling, For example: VPN, VPS, Ethernet, 3G, 4G LTE, Volt, 5G Volt, Telecommunications Networking & GPS) Defined routing with QOS Network optimisation (Localised) & Data bandwidth data (Localised) Global Zone routing through tables... Statistic Enhanced Routing & Delivery * QOS : Quality Of Service protocol : RS https://is.gd/LEDSource Personally I believe QOS : Quality Of Service protocol be introduced to all network traffic, Primarily the Point A to point Z route needs planning first. QOS Datagram Network throughput Capacity of the network card Advertise Capacity in local network Plan routes based on network capacity So the Quality Of Service Protocol needs to send a datagram to the network adapter of site: A to Z A list of local routes needs to be cached & prioritised based on Network point A's network capacity & priority, The rout needs Point A to Z mapped & Z to A We then send data with a packet listing preferred routes [QOS][Origin : Target][Preferred route list forward sent][Network Performance Metric Packet] [Origin : Target][Preferred route list forward sent][Semi Static Route Tunnel] [Packet ID][Origin : Target][Data Packet] Searching for a route with every packet costs processor Cycles; So preferred routes need to be tunnelled & Secured with TLS Rupert S https://is.gd/CryptographicProves https://science.n-helix.com/2022/03/ice-ssrtp.html https://science.n-helix.com/2022/01/ntp.html Code Speed https://science.n-helix.com/2022/08/simd.html https://science.n-helix.com/2022/09/ovccans.html Chaos https://science.n-helix.com/2022/02/interrupt-entropy.html https://science.n-helix.com/2022/02/rdseed.html https://science.n-helix.com/2020/06/cryptoseed.html Example of a Secure Tunnel System: https://is.gd/SecurityHSM https://is.gd/WebPKI TLS Optimised https://drive.google.com/file/d/10XL19eGjxdCGj0tK8MULKlgWhHa9_5v9/view?usp=share_link Ethernet Security https://drive.google.com/file/d/18LNDcRSbqN7ubEzaO0pCsWaJHX68xCxf/view?usp=share_link ***** Date: Fri, 17 Feb 2023 16:39:25 +0100 Subject: New Version Notification for draft-scheffenegger-congress-rfc5033bis-00.txt 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
- [Congress] Congress - Congestion Control - Combin… Duke Abbaddon