Re: [arch-d] Musings on Internet evolution

Jari Arkko <> Thu, 09 July 2020 08:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5F9D3A08C6 for <>; Thu, 9 Jul 2020 01:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iqrzIG1h-W9w for <>; Thu, 9 Jul 2020 01:12:09 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EFCC93A08B9 for <>; Thu, 9 Jul 2020 01:12:08 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 643326601DA; Thu, 9 Jul 2020 11:12:07 +0300 (EEST)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id baGTqaLlnxdZ; Thu, 9 Jul 2020 11:12:05 +0300 (EEST)
Received: from [] ( [IPv6:2001:14b8:1829::130]) by (Postfix) with ESMTPS id 88040660166; Thu, 9 Jul 2020 11:12:05 +0300 (EEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <>
In-Reply-To: <>
Date: Thu, 9 Jul 2020 11:12:05 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Bill Woodcock <>
X-Mailer: Apple Mail (2.3273)
Archived-At: <>
Subject: Re: [arch-d] Musings on Internet evolution
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Jul 2020 08:12:11 -0000


> I assume you saw this:
> We had quite a lot of expert input which didn’t make it into the report, as well, which I can summarize, if people are interested.

Thanks for this - I had actually not seen that before. Very useful.

One observation that I have heard from many who have been involved in practical day-to-day Internet businesses is that while the user experience may be relatively smooth, that doesn’t mean that nothing needed to be done. A *lot* of work has happened behind the scenes, capacity added, issues addressed, things moved, calls made, etc. etc.

> From my point of view, I think the most interesting finding is that this is the end of network-to-network (i.e. routed subnet) VPNs for home-office situations.  While that was supportable for a few executives, it doesn’t work if most of your workforce is WFH


> One of the big positives in the “new normal” has been the democratization of Internet governance meetings…  My colleagues Sara Alamin and Gaël Hernandez have a brief article coming out shortly on that topic.  When meetings happen online, they’re less dominated by people from countries which issue each other travel visas and which have inexpensive and frequent air travel between each other.  That’s good news, in a more-eyes-on-the-problem sense, and in a design-that-works-better-for-everybody-works-better-for-everybody sense.

Yes, that has been very good!

> The main conclusion I’ve been seeing people draw from the Zoom situation is that we’ve passed some sort of tipping-point of ridiculousness in the everything-as-a-service, in-the-cloud shitshow, and that governments, particularly, need to get back to a point where they’re capable of standing on their own feet and operating the services they need, using code they’re familiar with.  So, good news for open-source and open-standards, if people pay attention to that.

I certainly hope so. (Cautiously optimistic but lets see in few years.)

Anyway, I think this has been a part of a more general realisation in the society, e.g., critical supplies and services availability. And it applies to companies as well, not just governments. Business continuity.