Re: Limited Domains:

Tom Herbert <tom@herbertland.com> Thu, 29 April 2021 00:42 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F06543A2714 for <ipv6@ietfa.amsl.com>; Wed, 28 Apr 2021 17:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 dPlgjyY-hORx for <ipv6@ietfa.amsl.com>; Wed, 28 Apr 2021 17:42:36 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EB913A2715 for <ipv6@ietf.org>; Wed, 28 Apr 2021 17:42:36 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id u21so97295142ejo.13 for <ipv6@ietf.org>; Wed, 28 Apr 2021 17:42:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9MF12+JNsLoqcFPy/YPu+7SKpkep4L6is/814T/DYqc=; b=HCiTluhh7E9bwsH5eBGPXL56kxZEJNna+Kalc8zbJ0eggJ+YiZEPSwrxSSb7pLsVFm 8FjQhGr34ceNWtCVyC+1ocb+croF/wjmb2/J+57l7gXLSWlQbBSeAIn9D0DR3WmapApG kDi/qbHuuWS+2PQSO+uayFpsg1zMyW5MIHwOb+ELvEng+6Pk+H64EkYtgptWtXVGZR+d vKG0b+FzB+kzVp4TLpu3+A/aEarlGNn6cFTWfYBKvkMUZd91k1e1I/WP2SXzZK9/MrZ1 lYiFqi4DUA/MAeoTom8oBKfXPU17I4PX2ACBrTAh9rq1zi0feviLHAFoM7t6hVWjfOae gMaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9MF12+JNsLoqcFPy/YPu+7SKpkep4L6is/814T/DYqc=; b=r5Wt9xPywa6rqKZIuVkzKCZXfopcOCWGSCioAJg/1YU83ollPge6UitwEcI+tOku/I gR0cruL4VXL8L119B384pgJUj0fBOOzAfrXJbaw/fYUUjYTFRF5LTrETPkNlwL1u3uwO pzecy+FKwi2eLm33Hl6LqYbc84TwcZW/97VqqsvV+mQjbfLF8E1uNkf4AINlWg2gtewD JGYdcAhNtYb5fP5UxajcRDvat1G6o1CqQMzo40/YBxnEtGu+idOZgirfwiJNLNLQqewr DFujlTz0HV2mOQ1W6hJEWkEktlHuGtcRv/h0U/LcIvQUEfZb6XyEdrT2a2CMxpYGmrxa ymiw==
X-Gm-Message-State: AOAM5325HHwzOD3rLlvCKTv2k7e2JPBZzKrBzid2hUUwCj1xgB/btk/K Z7ccQr9txDK832GBNl6dQqQe+VtNU5a5xdanugw+roiLpIT6nQ==
X-Google-Smtp-Source: ABdhPJykOM8m7O5YO8t8VaJObzTo5ika3mvB88Qt2nmN78I4kwBh52hXiZWdw8nbFdUOZBoqLwvVl+7oISWRv4MwgY0=
X-Received: by 2002:a17:906:2c55:: with SMTP id f21mr19492184ejh.41.1619656954640; Wed, 28 Apr 2021 17:42:34 -0700 (PDT)
MIME-Version: 1.0
References: <BL0PR05MB5316991D4124AD85BC69392AAE709@BL0PR05MB5316.namprd05.prod.outlook.com> <20210412170938.GB34032@faui48f.informatik.uni-erlangen.de> <BL0PR05MB53163BB3383E1DE6CA98D4C3AE709@BL0PR05MB5316.namprd05.prod.outlook.com> <CALx6S35JhJ_+WNpQ10JHB6L2E8MTEaCRO9c6g7rT-2BK3ZnsuA@mail.gmail.com> <43b67ede-b019-c573-5637-c07168e7ec6d@gmail.com> <CA+wi2hNcxPs_MLAKiQm2UzjMLgBVyH+-Z8SV__WDDOuc2rYafQ@mail.gmail.com> <20210428201140.GA21928@faui48e.informatik.uni-erlangen.de> <0df23143-1834-2ff9-3399-cde3de479fc0@foobar.org> <CA+wi2hOE=vU4=xLJnaPfDc_fEv5+zOSXK9orfPWs+W5g1_FYjg@mail.gmail.com> <20210428235851.GB21928@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <20210428235851.GB21928@faui48e.informatik.uni-erlangen.de>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 28 Apr 2021 17:42:23 -0700
Message-ID: <CALx6S35yk2opePy3k6-4j9XSEBHt9NjDEe03-DiLJoHbWehMSA@mail.gmail.com>
Subject: Re: Limited Domains:
To: Toerless Eckert <tte@cs.fau.de>
Cc: Tony Przygienda <tonysietf@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nkNujtEjV5lnaeqiqf6hNANLznw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Apr 2021 00:42:41 -0000

On Wed, Apr 28, 2021 at 4:59 PM Toerless Eckert <tte@cs.fau.de> wrote:
>
> On Wed, Apr 28, 2021 at 10:51:03PM +0200, Tony Przygienda wrote:
> > yepp, researchers are having fun unencumbered largely by harsh realities
>
> Well, the better researcher attempt to get more of an understanding
> of the harsh realities by working with whats available to them, which is
> quite limited - a few P4 platforms. This lack of openness to multi-party
> innovation is what causes high-speed router platforms to become less and
> less relevant and devolve into commodities, at least at the level where
> folks in IETF are interested in them. Obviously the spped&feed hardware
> level will stay an ongoing motor of innovation and maybe even sales
> margin, but for the packet layer forwarding, we can close shop if we do
> not have a strategy to allow new markets/innovation to be brought in.
>
> Heck, take a look at the challengers in 5G/6G. They are already moving
> purely into general purpose CPU because those challengers have no way to
> put innovation into accelerated forwarding hardware due to lack of access,
> complexity and also being stuck in a world of standards such as GTP that make
> innovation difficult.
>
Toerless,

While I agree with your sentiment, this is really a lament about a
segment of the market not about anything IETF has done. For instance,
no IETF standard  requires high performance routers to be implemented
in fixed ASIC, in fact I believe the technology has evolved to the
extent the datapath could go through the CPU simultaneously achieving
both performance and flexibility (my company is working precisely on
that).

The hard problem is legacy and the Least Common Denominator effect. On
the Internet we are bound by the least common denominator of protocols
which is plain TCP/IPv4 and TCP/IPv6 that generally make it through
the Internet. UDP is looking a little better, at least because of QUIC
which took a behemoth to force support. The end result of all this is
the ossification of the Internet which as you point out stifles
innovation and creation of new markets. This is actually the appeal of
limited domains, it creates walled gardens where in which the least
common denominator can be raised and we can innovate in that sand box,
however limited domains don't address the underlying issue unless
their scope continually expands to cover more and more of the
Internet.

Tom

> Its totally incomprehensible to me, why engineers who paycheck ultimately
> depends on hardware that already is way more flexible than what our current
> protocols use do not try harder to think about better models for third parties
> to get more value from this hardware. More flexible, programmable packet forwarding
> options are one core option here. And obviously no sane customer
> wants something thats not multi-vendor in this space which is where
> IETF could come in. And no sane network operator wants another protocol silo.
> Which is where IPv4/IPv6 compatibility comes in as a base level expectation.
>
> > while meanwhile large scale IP forwarding is still governed by the
> > microcents/bit payload that customers can run their business profitably at
> > and this is governed in turn by the merciless trifecta of physical laws of
> > power/cooling/space that did not only not change in the last 50 years but
> > last 500 and probably much longer even before Newton laid his cranium under
> > the said apple tree ...
>
> When single-family home systems are built from 19" CPU server racks
> providing compute across FTTH and powered by solar electricity, i think
> we are also starting to see big shifts in the economics of those core
> factors. But thats digression.
>
> I think we agree that from the protocols we remember, IP/IPv6 has
> done a pretty good job providing value out of the hardware
> deployed. But we also know that other protocols like Ethernet and MPLS
> have shown other sectors where they are doing better. So it seem to me
> obvious that as developers we should look ahead and see what it is we
> can best do to crearte more value. And certainly we know our hardware
> can already do more than what is utilized by the protocols.
>
> Cheers
>     Toerless
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------