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

Hesham ElBakoury <helbakoury@gmail.com> Sat, 06 May 2023 00:44 UTC

Return-Path: <helbakoury@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 84C2DC151549 for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 17:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 WzJsSLRH2kYM for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 17:44:30 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 E91BDC14CE3B for <architecture-discuss@ietf.org>; Fri, 5 May 2023 17:44:30 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id d2e1a72fcca58-64115eef620so23229234b3a.1 for <architecture-discuss@ietf.org>; Fri, 05 May 2023 17:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683333870; x=1685925870; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=erwvWXttkiEqBNcTu0OyVepCbCdUPcxZb8QVFoFGrBI=; b=lSJ5C0BRwW6BPOkMrYOTQb6dnq80wzt0NSPd0tW/iAk8uW0ez7JlXA6LxydrOZ8MC+ TtC6cl6mg+SzzO9KEwTqX9OKQ8MedBnDVy+qXEMyBXMM8k3f5aXuqIzW6Cn/fIY1Pa+A bNOZxsnEylDPWUcs0j4y4aN5AsNICSwpdFgJzSv6ARp1JqNJBCq6WtdiImrryXz8iSAO CLHBacBeS+EzC65k0ifhEYHY4VDdX0QwXTBT3UVBuQ2VtDtbcbndIBDi2fHeIevagsG8 q9SIKOFi3ljP3IRSTpaSSLt23Jml+ptCyZoWErifAnA32ig7lqaydX46GLmbe86VOLia EXog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683333870; x=1685925870; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=erwvWXttkiEqBNcTu0OyVepCbCdUPcxZb8QVFoFGrBI=; b=Wf6fx1IG+xTQORTpBZgTXbSs8gsrWTAOA3liOiMAbD5OxqG0VAghFoPE6Rxu6Jrd3v a6xz7TJrxdEb7SkpiHAqM85aOYUQcE3a1kUfLfxXzVJOcbVlyk+Jn/e7zzdpOPVYLc2E JUl50Q6W8XRriBzD4RuoI9nkUk0zmdtkNCR/xfuRHMqTbx6DdPreCCQSNxT9jQ05093i 8qDrhicAbN/M6MD7hfCo7EoTBN4DmWF1D0UepKC8gTtCBgRytaWB7C4zojaPruu2er9/ biykr9QUJSF+nPGMMwXrv2O4WGDwnptgQ/s8ElSMVRywyxZkPk91lmeytODr5RiT6exr 8jKg==
X-Gm-Message-State: AC+VfDwlF4dIyc6u+lw/jLDxYtflCEmh/uRICY6UMoAID5RbdMLK2UiX V89hP/i2h3z/eRd3BMhoURcOK6zQeC8ts7snA3I8u3A6c4g=
X-Google-Smtp-Source: ACHHUZ7WPCDurlkf47iA1meo3A93KI3xqfp4xqySWUPTz97MaHTAcRRjeUd+3RyBpoOn+V9P5RruyhyGMvR5avpFEX8=
X-Received: by 2002:a17:90a:4b0d:b0:24e:5f5f:d292 with SMTP id g13-20020a17090a4b0d00b0024e5f5fd292mr8454730pjh.2.1683333869645; Fri, 05 May 2023 17:44:29 -0700 (PDT)
MIME-Version: 1.0
References: <0f0da4833f81463b972558d972285595@boeing.com> <12045445-15D9-40F9-8306-4F3F98AB6BBE@apple.com> <911c3777-47e0-fad0-b0f9-7cbb81ba5a56@gmail.com> <ZFTziiTt5NX1mRdW@faui48e.informatik.uni-erlangen.de> <4b961812-fd87-a445-9b73-079347944130@gmail.com>
In-Reply-To: <4b961812-fd87-a445-9b73-079347944130@gmail.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Fri, 05 May 2023 17:44:17 -0700
Message-ID: <CAFvDQ9oBOe6-Sux9TQ1WB=mLG6JdmSfnNo+p+4gpDoT0bfKPxg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Toerless Eckert <tte@cs.fau.de>, architecture-discuss@ietf.org, Internet Architecture Board <iab@iab.org>
Content-Type: multipart/alternative; boundary="00000000000056b8b105fafbb576"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/p8UPXwLLZK2Ysr13T26-JmsyHDY>
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: Sat, 06 May 2023 00:44:33 -0000

Constantinos (one of the speaker) supports decentralization since
"Centralised systems have built-in security that’s however vulnerable as
they act as single points of attack and failure".

Hesham

On Fri, May 5, 2023, 3:02 PM Brian E Carpenter <brian.e.carpenter@gmail.com>
wrote:

> 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
> >
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>