Re: [arch-d] A Public Option for the Core

Toerless Eckert <tte@cs.fau.de> Mon, 17 August 2020 16:43 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 017DE3A0D47 for <architecture-discuss@ietfa.amsl.com>; Mon, 17 Aug 2020 09:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level:
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vzKDt4TrSzAn for <architecture-discuss@ietfa.amsl.com>; Mon, 17 Aug 2020 09:43:01 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF8083A0D42 for <architecture-discuss@ietf.org>; Mon, 17 Aug 2020 09:43:00 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 3ECBD54802F; Mon, 17 Aug 2020 18:42:56 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 370A5440059; Mon, 17 Aug 2020 18:42:56 +0200 (CEST)
Date: Mon, 17 Aug 2020 18:42:56 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Christian Huitema <huitema@huitema.net>
Cc: Joseph Touch <touch@strayalpha.com>, architecture-discuss@ietf.org
Message-ID: <20200817164256.GB62842@faui48f.informatik.uni-erlangen.de>
References: <754DE168-DF3B-4471-A145-39C6143E538A@comcast.net> <FB381338-A278-45B2-A40B-3A065E3A3ED1@strayalpha.com> <1fd2ed7d-d4bc-c5b7-9a4a-7966d5e60513@gmail.com> <20200817074637.GW62842@faui48f.informatik.uni-erlangen.de> <60B2B44D-5E6D-4CB2-AD63-1A8CB846BFA3@strayalpha.com> <0e575946-dfd4-7753-8c34-47987d0b3c7e@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0e575946-dfd4-7753-8c34-47987d0b3c7e@huitema.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/b239fjlIlLHh0YBgRXgFXp0LkXI>
Subject: Re: [arch-d] A Public Option for the Core
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2020 16:43:06 -0000

On Mon, Aug 17, 2020 at 08:19:59AM -0700, Christian Huitema wrote:
> Given the knowledge and trust issue,
> one-size-fits-all looks actually very practical. That does mean a
> compromise, because the network should allow those applications that
> want low latency to get it, but should not limit the bandwidth that
> applications can use if it is available. That probably requires more
> research and development in active queue management, and in congestion
> control algorithms that can cooperate with active queue management and
> deliver the profile that fits the application.

Thats again the look for networks we currently call "the Internet",
and quite valid there. But certainly not the only type of networks
IETF should be interested in.

When you look at managing traffic flows in e.g.: networks of an airplane,
you will see every individual flow being designed, and planned for before
the plane is built. And those parameters ar then embodied into the network
during plane building. I would call this the other end of the spectrum.

Instead of just talking about some of the tools (CC, ACM), it would be
nice to try to set goals first, to see if we could get agreement there:

-> I would like traffic to get the same throughput under congestion
   whatever its RTT is.

-> I would like for traffic to get bandwidth share indpendent of the
   number of 5 tuple flows it utilizes (no gaming the system). But
   rather fair per subscriber (weighted by how much the subscriber pays).

-> I would like to be able for traffic to indicate preferences for
   lower latency or higher throughput... If you ask for lower latency,
   you get less throughput.

-> Goodput always > 95%

That would be a start for the most simple "one-size-fits" all i could
imagine. But there is a lot more things i would like to factor in beyond
that.

Cheers
    Toerless

> -- Christian Huitema
> 
> 

-- 
---
tte@cs.fau.de