Re: What is the long term plan for Internet evolution?

Nick Hilliard <nick@foobar.org> Tue, 29 June 2021 20:46 UTC

Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19623A097E for <ietf@ietfa.amsl.com>; Tue, 29 Jun 2021 13:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.238
X-Spam-Level:
X-Spam-Status: No, score=-2.238 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.338, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 HPYqLdY9rRFd for <ietf@ietfa.amsl.com>; Tue, 29 Jun 2021 13:46:36 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01B9A3A097A for <ietf@ietf.org>; Tue, 29 Jun 2021 13:46:35 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 15TKkP3M022696 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jun 2021 21:46:26 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
Subject: Re: What is the long term plan for Internet evolution?
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <CAMm+LwiFajxuV3E_u7b-f=7DqTHXG_4Y=VLoCsUxknD_mCp1=Q@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <00722e06-a385-251c-d95d-2ff67e83f5c1@foobar.org>
Date: Tue, 29 Jun 2021 21:46:24 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.48
MIME-Version: 1.0
In-Reply-To: <CAMm+LwiFajxuV3E_u7b-f=7DqTHXG_4Y=VLoCsUxknD_mCp1=Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1gTkvy0kbxFDUZ0JvyFVjXXome4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2021 20:46:38 -0000

Phillip Hallam-Baker wrote on 29/06/2021 19:44:
> telemetry. The reason we run application services over HTTP is really a 
> matter of inertia and the fact that there are simply not enough ports 
> for static port assignments to be viable.

nothing to do with the availability ports. It's that http provides a 
generic transport layer for transmitting any sort of data with low-brow 
signaling to hint at the data format.  It's inelegant in the way that 
any evolved generic protocol is inelegant, but mostly it works like many 
things that evolve to fit a purpose.  DNA coding is inelegant too.

> IPv6 is slowly deploying but that is only because the pain of IPv4
> address exhaustion is starting to become serious.
I've long given up any expectation that ipv6 will outlive ipv4.

You may be fighting a losing battle here.  Protocols and applications 
have evolved together and they work, so any attempt to change is 
battling evolution and that's an uphill job.  Likely, the only way out 
of this is revolution, i.e. when the internet is supplanted by something 
so cool that we nearly won't even bother using the internet any more 
because it's so meh and old hat, like the POTS.

Nick