Re: [arch-d] [EXT] Re: IAB Technical Discussion on Fragmentation: 2023-05-03

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 06 May 2023 22:33 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 05E01C14CF12 for <architecture-discuss@ietfa.amsl.com>; Sat, 6 May 2023 15:33:30 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pOb0rWPDyA5d for <architecture-discuss@ietfa.amsl.com>; Sat, 6 May 2023 15:33:28 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 346CEC14F74E for <architecture-discuss@ietf.org>; Sat, 6 May 2023 15:33:28 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-24e01ba9e03so2216056a91.1 for <architecture-discuss@ietf.org>; Sat, 06 May 2023 15:33:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683412407; x=1686004407; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=MTihq8iKeK7vSgqJFTaNwUD6AgxkgtPRPD2JohwgjCw=; b=EOIdlsDLIjI6AMjmcVdDYtU+mxcWV2aeRRI48WXa/pDJCTs81lFXH1Htk+YBj/tTSw dSmr0SuXOe/ukJ+6iasQMZ6WawYxyY7/wG1YECT+TvihK/pXZE4xtCOxWS7c4qMB/4FQ dFbQV+hJc3rFRWHRPycaB05+bsAGRD9kxjg7d3eIP6IZWgq0uCxBym/Ver3h64f7HcDk yrOWpExmq8VfM9ahMIOjg5Tffk62h1aIsfw4/FR6V7AVTbj1hWH4BdtMD7P8hKVkeZkK xZxcFnyvJZSG7SPrYn9klWA3OhZ6sattePyheQrbv1Bky1/HBKVd45I4uVpbav8isT8R Ky0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683412407; x=1686004407; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MTihq8iKeK7vSgqJFTaNwUD6AgxkgtPRPD2JohwgjCw=; b=SAohxLrj/E5iWBVKfuGx2TcoxzgvbtXyD3HzILye85VfM+F7/NrPfEmy3t8tMB/Qxb RA0DCAMcYUkhxtQlaYMr7ERqpZHYqcC/Aoig2CGcT+Z09jAr1XgdpLoEgUC+tHbQrm/N vgc3AseaGN5r/fv6Y5qv7nsduqM7MiDyHniF6AKdd88N+WOjc3LLHpmvOPAJsJR3uhdd KVFL8SZpff8P0Ds6CpVpW/XJuqNNB5cKyOV/HXnDgDxOq6IZcJEF2BQ2GmxYspyAw9se aF3ebanMlSnzA8jn5HG5usQ3J70ujI3Fyj2zBrQ4V9EQhX7Ibht8wq99W5/tIYSpIJPZ hnQw==
X-Gm-Message-State: AC+VfDwKtbgSO1jQm+J+Fsiojy+xZTN4UxsRH+kZopGSfhKaua9aO9A8 8NtKYBHZIPHO834u84WKeP4=
X-Google-Smtp-Source: ACHHUZ7Pj/miWz6ZehCI4+pzRq2qAQPfZu8bhW/pTFBxmEEw+YSdIXwrLYKjJdGUETzMv5uMtttNJw==
X-Received: by 2002:a17:90a:b013:b0:246:7b1d:8817 with SMTP id x19-20020a17090ab01300b002467b1d8817mr5291357pjq.48.1683412407433; Sat, 06 May 2023 15:33:27 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id c6-20020a63d146000000b0051b595b26adsm3543090pgj.91.2023.05.06.15.33.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 06 May 2023 15:33:27 -0700 (PDT)
Message-ID: <749f75d8-9239-ed0f-e0f4-29c76e38a91b@gmail.com>
Date: Sun, 07 May 2023 10:33:22 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>, Watson Ladd <watsonbladd@gmail.com>
Cc: IAB <iab@iab.org>, architecture-discuss@ietf.org
References: <168271026305.50065.11855031975777547008@ietfa.amsl.com> <CABcZeBPQRCg_9P20TVf=t-6+h7xvmgOWjAJ3oQc5BUJ14VvBrA@mail.gmail.com> <99b74fec-5f3b-d7be-fd4e-1c300b1d85d1@gmail.com> <1B995EBE-ECDB-4FCC-8ECD-57BE24182FD5@gmail.com> <CAA=duU2=-0i6BqXWWqFS+-Gu+K9KBoRVRDRPAoojj5p4eeDWWg@mail.gmail.com> <680069303.5441.1683023514937@appsuite-gw2.open-xchange.com> <CACsn0cmtewbqPA5aku70eeqvcCSYH8wFU0VzpWS90KaW-UHVdg@mail.gmail.com> <805562902.29484.1683363363741@appsuite-gw2.open-xchange.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <805562902.29484.1683363363741@appsuite-gw2.open-xchange.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/cSu6FDgPIspVQlgOZ36MlLiX1lQ>
Subject: Re: [arch-d] [EXT] Re: IAB Technical Discussion on Fragmentation: 2023-05-03
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 06 May 2023 22:33:30 -0000

Vittorio,

On 06-May-23 20:56, Vittorio Bertola wrote:

...

> The original idea was that we would have places where we would talk and reach rough consensus around policy compromises, such as the IGF, and then the technical community would follow. However, "the technical community never accepted to consider anyone else's views and in most cases only showed up in those venues to say that engineers know best and that the decisions they made in the 1970s were still the best possible ones" (sorry for this summary, but this is how things were described to me by a government officer some time ago).

It's many years since I last had the pleasure of discussing Internet infrastructure with government officials, but I still think this is a caricature. (Especially since the basic decisions taken in the 1970s were taken under the aegis of a US Government agency, but let's leave that aside.) That type of criticism used to come from officials who were heavily under the influence of PTT monopoly thinking; we never got it from officials who were working to break those monopolies.

Well, that was a long time ago and the issues are different now, but I still doubt the validity of the argument. What is undoubtedly true is that changing the nature of Internet infrastructure is essentially impossible at this point in history; even the trivial change of increasing the address size has taken us 30 years and is only 43% complete.

The issues discussed here (splintering and centralization) aren't really infrastructure issues anyway, so the potential IAB/IETF influence is quite small.

> 
>> The fact that the Internet is permissionless and implementation
>> precedes standardization is good: it creates a dynamic environment
>> that has tremendously benefited everyone involved, and has prevented
>> rent-seekers who would like to stop investing and innovating and
>> instead charge tolls.
> 
> You must be stuck in time at least 15 years ago. Today, the most common device for accessing the Internet is a smartphone, on which you can only pick between two operating systems. Each of their owners controls everyone else's access to offering services: you cannot distribute an app without their permission and without abiding by their unilateral requirements, and often without conceding them small perks (rents) like a 30% commission on any payment. And this is just an example: the cloud infrastructure market, as another example, is increasingly like that, with 3-4 dominant operators (mostly the same as above) progressively conquering all others.

Correct. Almost none of that is a result of the infrastructure specifications from the IETF. Ironically enough, after breaking the national PTT monopolies 20 or 30 years ago, the Internet is now the superhighway for a new set of international monopolies. As I used to say many years ago during early discussions of network security, don't blame the roads for helping the bank robbers escape.
    
> As happened before in other industries, the lack of regulation and the consolidation that follows innovation fostered mono/oligopolies, and now we need a bit of permissions and planning to rein them back and restore choice and competition. This will inevitably make the Internet less uniform, less global and less borderless, but it's a price that we need to pay.

It's the upper layers that are concerned here, not the transport infrastructure. Is the W3C having the same discussion?

    Brian