Re: [arch-d] Splintering (fragmentation) vs Centralization vs Users

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 05 May 2023 22:02 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 82FA4C17CEA1 for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 15:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afS9zgBFemp4 for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 15:02:00 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 D5CF1C1782B0 for <architecture-discuss@ietf.org>; Fri, 5 May 2023 15:02:00 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id 41be03b00d2f7-52cbd7e73d2so123872a12.3 for <architecture-discuss@ietf.org>; Fri, 05 May 2023 15:02:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683324120; x=1685916120; 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=MASForFcLSlavLVVePwdcd/IrXBhbh/p3qx3ctKRgOk=; b=Rp4Lqhy3AejyiZP5LlYSFKAJP1gFjcOcrtpslPmdkjxZ+zt9LZc+gbKY62EBXnXEsi nxaPX/1Qycv7CqB6O/IOEqcLcJq+ZUzFAcGRP464+VirjFMUwSItjfiOgtlUogqjS5vk 3aDBj61D8r8iB9c8yUCIxN2pt7Iv8b1bmAjKY91vC3Vz0OCOd6TIXh363fIFlfXbStmM fSi8Q9xRPKEpF7xUxSf3zM3pdjuWDZpoTa3cO+2Jy2x0/vG47sBu5xhQEfAmjDG1Wt6W vpVhMyHRtbPuanhatVHLXbeX6AtiRDkplH9MGNBXSehLu7Z3++qnEyEF9jI/HETDw2n+ fuqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683324120; x=1685916120; 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=MASForFcLSlavLVVePwdcd/IrXBhbh/p3qx3ctKRgOk=; b=OcgpKQjm6w4neDajRZWYF61zZBd0uVwzEdbUuA3WDeN2XDt2+GnNyEvD1lkzW9ABNw AnlOBuUSvTmpoehqfQWCQjdWc/qZ6pU8oOewZGFkyJA6h2m44lOhtKksZ4YiZYP8TA0D kX51326IK74h6P881J+JgDC5xTaufXacABQAR8yLhH6AdlTumJjSkjiYPRzCWxHFtUJJ RBrB7vzOZ8DHn8yFCayn+A1qpO9367tw+xqoBWzL7h/VB2KCxEWlzXkNEcAna+afksSa 5nQHjcqq89J41s7q8/xlyGygTvdJ7nioWFoOcOq++4iecb29ehGqCTzHkEdeD2QHIyrK o4yA==
X-Gm-Message-State: AC+VfDzV8aZ04CEnw4lKtDfNBxVVZ/d4jM1878smzhWQ3GX47FNdHuIV C2A++/hcrPn7i1bvkhSMaeHShIkWAZHBhw==
X-Google-Smtp-Source: ACHHUZ5PNHLhJKuPKmmt39NpMSBHp+KyzEGjenOOJdkipEIfI8Nx0sAHzCEreN3kCeiaqLPztPf4Eg==
X-Received: by 2002:a17:902:d34b:b0:19f:188c:3e34 with SMTP id l11-20020a170902d34b00b0019f188c3e34mr2866547plk.53.1683324119738; Fri, 05 May 2023 15:01:59 -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 be11-20020a170902aa0b00b001a63b051b0csm2203309plb.282.2023.05.05.15.01.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 May 2023 15:01:59 -0700 (PDT)
Message-ID: <4b961812-fd87-a445-9b73-079347944130@gmail.com>
Date: Sat, 06 May 2023 10:01:55 +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: Toerless Eckert <tte@cs.fau.de>
Cc: architecture-discuss@ietf.org, Internet Architecture Board <iab@iab.org>
References: <0f0da4833f81463b972558d972285595@boeing.com> <12045445-15D9-40F9-8306-4F3F98AB6BBE@apple.com> <911c3777-47e0-fad0-b0f9-7cbb81ba5a56@gmail.com> <ZFTziiTt5NX1mRdW@faui48e.informatik.uni-erlangen.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <ZFTziiTt5NX1mRdW@faui48e.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/1cOVl1H1I7Tlru1Bp4PBZrsd02I>
Subject: Re: [arch-d] Splintering (fragmentation) vs Centralization vs Users
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: Fri, 05 May 2023 22:02:01 -0000

On 06-May-23 00:16, Toerless Eckert wrote:
> Brian,
> 
> When you say "centralization", what do you mean ?

I mean that, to continue your example, there is basically exactly
one on-line bookseller in the world, which has all the properties of
a monopolist. How that is implemented in terms of servers, private
networks, CDNs, distributed data centres, etc. is a separate question.

For continuation of the argument, see Christian Huitema's message.

    Brian

> 
> If one Internet bookseller has one server in Seattle for all its global
> customers, is that centralized, or is it decentralized because its just one
> out of many equal booksellers with servers on the Internet ?
> 
> If the same bookseller has millions of servers to buy books all over the planet,
> is that decentralized now, or do you call that centralized, because the Internet
> enabled that one bookseller to eliminate most others ?
> 
> How can therer even be an answer to these questions without admitting that
> we do have an interest in the higher-layer reasons and implications of our
> protocol work, and that we can not even make technical judgmenets with that
> "use-case" discussion.
> 
> And i thought we also already agreed that we needed to be more precise in terminology,
> such as attempting not to use centralized/decentralized for everything unqualified.
> E.g.: monopolization was bought up as another good term to distinguish cases.
> 
> Cheers
>      Toerless
> 
> On Fri, May 05, 2023 at 09:39:17AM +1200, Brian E Carpenter wrote:
>> Hi,
>>
>> After a little off-list discussion, I have a few more general thoughts
>> on this topic. (I won't identify the other person in that discussion,
>> to respect their privacy.)
>>
>> I mentioned that some security technology that we develop could be
>> "dual use", e.g. useful both for privacy and useful for walled gardens.
>> So perhaps we should be careful when evaluating new ideas that they
>> cannot be used for undesirable purposes as well as the intended purpose.
>> If we consider that both excessive centralization and excessive
>> splintering (a.k.a. fragmentation) are bad things, does a new technology
>> drive those tendendencies? Could we design it differently to avoid
>> this?
>>
>> Is there scope for IAB guidance to the IETF about what aspects of
>> protocols, especially security protocols, might encourage or discourage
>> either centralization or splintering?
>>
>> That could be a productive use of the IAB's resources where we might
>> have some impact. Discussion of wider societal, commercial and
>> political issues in the IAB and IETF would get nowhere, and in my
>> opinion is best left to ISOC.
>>
>> There's very clearly a 3-way tussle, and that makes all discussion
>> difficult, especially since each national government has different
>> goals. ASCII art:
>>
>>                  Users
>>             (freedom of action,
>>                  privacy)
>>                  /    \
>>                 /      \
>>                /        \
>>        National          Global
>>     governments -------- businesses
>>     (defend or          (capture &
>>      control             exploit
>>      citizens &          customers)
>>      economy)
>>
>> Regards
>>     Brian Carpenter
>>
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/architecture-discuss
>