Re: List of volunteers for the 2021-2022 NomCom

Stewart Bryant <stewart.bryant@gmail.com> Mon, 28 June 2021 14:39 UTC

Return-Path: <stewart.bryant@gmail.com>
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 3B3983A0AE6 for <ietf@ietfa.amsl.com>; Mon, 28 Jun 2021 07:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPiwIKOsa20q for <ietf@ietfa.amsl.com>; Mon, 28 Jun 2021 07:39:43 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 E16C33A0ADF for <ietf@ietf.org>; Mon, 28 Jun 2021 07:39:39 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id o33-20020a05600c5121b02901e360c98c08so12172324wms.5 for <ietf@ietf.org>; Mon, 28 Jun 2021 07:39:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=P5lgLCUH4n6it2Al+AJCxKEZ/poXlz1Hggi9b7yi5Fs=; b=odnQx22mepXHIGZzmYk5rFNOlg04wM2CKnAnPYFPfNPhBeH0+PCr/JtCOyE6I1N8vB ALJs9DbIQg0MX1wQbQ8uJvLpaw9A7GLAfAsgBmtH+GmD2uKNTh1oRImYX24Y/sn5dlRA VmjHI/MZHAbUAtWXC9xdvGkjZOWpXUv88NyjZOAXHbYP3O6GZ0m/hI99tXL3MUgXfCl9 LjHNZJdbtcrTNGX9Mrs2dq3v1gYs3V/xiT4cG3R3EeFFk7hxoYB0A67AlbIL4zGRcIjR UyACa5SeFCjEow8ikDHmUJy9FNBnifvGBpdNvq1zkkEjd3dUom9uqvtMnqtLpnDEpDui i6iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=P5lgLCUH4n6it2Al+AJCxKEZ/poXlz1Hggi9b7yi5Fs=; b=LaaOyHW9wtZeYDJTHvKfoqhuRkJk1ZrMLvGsquo8clkIvu/OLQnpp9slT5jLSdq4Kq 2XWjcHhnwNhLrHo8w6SvfvoI+QLflRCGPgAqPV2qsZQm0ZrugUYolceD/YVFzLHHDAVB A1/1TZ+yBA0tWmejMOTPdWQHeICuIX9xFcspVU4sJs6bgLYkKoi3iWwh7hqLfgfbv6gq GSosvRizy7FL4+s8+TDmQQI8GpKyum2easNc13UlIe5GFEfAcshJIT+Ln2oX5N78Hdcg LInSihFVpgnRd7C6pRhI3iKxKpKxZ+uoMwj7xtRu9gZ7PjjTDtG0AOGxt18Vq2W4Vo8e 0rxg==
X-Gm-Message-State: AOAM5320jbPUiNf7tCkYPJ2Anj/kzATU8YBURhV49+h+Wj3J+z83SUni mwi32d99ORwt4lgNEwJIn9AefAn7PGoEow==
X-Google-Smtp-Source: ABdhPJx2/SR4rCq1wcUutaP9Gp3gWwrOIchxYgVTKguL1hX2G5axDxfq2+9f6yJ9ZHwnmqKQoOcK3w==
X-Received: by 2002:a1c:ed0a:: with SMTP id l10mr26700453wmh.151.1624891177785; Mon, 28 Jun 2021 07:39:37 -0700 (PDT)
Received: from [192.168.8.185] ([85.255.237.89]) by smtp.gmail.com with ESMTPSA id o33sm8836691wms.32.2021.06.28.07.39.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Jun 2021 07:39:37 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Subject: Re: List of volunteers for the 2021-2022 NomCom
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <c2148075-606d-8aa9-d7b4-71aa92a09fae@comcast.net>
Date: Mon, 28 Jun 2021 15:39:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B70940E-168B-48FF-8BD3-C392BE1FD51F@gmail.com>
References: <162465400926.25294.9751737050582698159@ietfa.amsl.com> <c2148075-606d-8aa9-d7b4-71aa92a09fae@comcast.net>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mvHaKkZSKxDBi4jW7KYC_L35uNk>
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: Mon, 28 Jun 2021 14:39:44 -0000

There are various speculations as to why Nomcom is not supported at the level that it used to be.

An explanation that warrants investigation is whether this is structural. This is important because it is less easily reversed.

The organizations that used to make money from the Internet were the network equipment vendors. There was a good match between their needs and the IETF core capabilities, and the IETF thrived as part of a symbiotic relationship. If the network vendors are not making money out of the Internet at the level that they used to, they will not invest in the IETF at anything like their previous level. They will naturally stop paying the IETF “tax" on their business activities. The situation seems to be that it is now the Internet content and application providers instead  that take the majority of the profit.  However, the equipment vendors are unlikely to be replaced by the content and application providers in investing in the IETF, because their business model is to assume that a basic Internet is there where they need it, and to focus on delivering content and applications using content caches and edge computing so that their service is not degraded by performance issues in the best effort end to end Internet. There is indeed a hypothesis that so long as is is possible to get a tunnel between their application at the client and their application at the edge of the cloud, nothing else needs to be standardised other than through their internal private design process or through open source. 

Students of business know that the impact of such industry structural change can be sudden and decisive.  If this hypothesis is correct, the IETF faces a significant existential threat. 

Managing the IETF though or hopefully out of a decline that results from significant  industry structural change will be the most difficult task that the IESG has needed to address in the last 20 years.

- Stewart