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

Toerless Eckert <tte@cs.fau.de> Fri, 05 May 2023 17:55 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 D9AA0C13AE5F for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 10:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=no autolearn_force=no
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 fpxCg4isS1ok for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 10:55:52 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 04ED1C152561 for <architecture-discuss@ietf.org>; Fri, 5 May 2023 10:55:51 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4QCddb2wdsznkd7; Fri, 5 May 2023 19:55:47 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4QCddb2FDzzkvnN; Fri, 5 May 2023 19:55:47 +0200 (CEST)
Date: Fri, 05 May 2023 19:55:47 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "David R. Oran" <daveoran@orandom.net>
Cc: Tony Li <tony.li@tony.li>, Internet Architecture Board <iab@iab.org>, architecture-discuss@ietf.org, Arnaud Taddei <arnaud.taddei=40broadcom.com@dmarc.ietf.org>
Message-ID: <ZFVDIyyYa1FpTJ5m@faui48e.informatik.uni-erlangen.de>
References: <0f0da4833f81463b972558d972285595@boeing.com> <12045445-15D9-40F9-8306-4F3F98AB6BBE@apple.com> <911c3777-47e0-fad0-b0f9-7cbb81ba5a56@gmail.com> <4B5D79EE-062B-480D-AB58-E782476926BB@broadcom.com> <8af99305-de33-911a-6fd0-d9bd5f0c2294@huitema.net> <285E3C91-FD39-4565-A8A7-C32569C05A22@tony.li> <64FE3789-224F-4938-B15B-7901EA4532BD@orandom.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <64FE3789-224F-4938-B15B-7901EA4532BD@orandom.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/-6nWGmJ8mzMz-NlJRBUQqaYaSts>
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 17:55:55 -0000

On Fri, May 05, 2023 at 07:37:57PM +0200, David R. Oran wrote:
> > Consolidation is part of the natural evolution of any market. Anti-trust
> > legislation has been necessary to ensure consumer protection, as no
> > other mechanisms have ever sufficed. Expecting that we can do better
> > would seem like an act of hubris.
> > 
> 100% agree, although it might be worth pondering if the IAB could provide
> useful data and advice on the technical c consequences of postulated
> anti-trust law/policy or regulations.

I would prefer for such work to be done in a more open IETF community than
how IAB can do work. From the organizational options we have, an IRTF RG would
be most appropriate IMHO, similar to HRPC, although with more focus on
collection of data and bringing it to the community for review than on trying
to offer guidance (at least initially).

Cheers
    Toerless

> Possibly…
> 
> > Regards,
> > Tony
> > 
> > 
> > > On May 5, 2023, at 9:47 AM, Christian Huitema <huitema@huitema.net>
> > > wrote:
> > > 
> > > Brian asks: "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?" I think there
> > > is, or more likely, that the IAB (and the IETF) have better find
> > > something.
> > > 
> > > Because the alternative position is, "Yeah, we design protocols that
> > > can just as well enable decentralization or foster monopolization,
> > > be good for society or be atrocious. Whether they do one or the
> > > other is someone else's problem." And that sounds very much like
> > > "Our job is to put the rockets up. Where they fall, that's another
> > > department."
> > > 
> > > -- Christian Huitema
> > > 
> > > On 5/4/2023 11:14 PM, Arnaud Taddei wrote:
> > > > Good write up Brian which reminds me 2 things + 1 addition
> > > > 1) DINRG had a similar discussion in IETF 116 on the theme "does
> > > > a new technolog drive those tendendencies?” (This was about
> > > > centralisation)
> > > > 2) We looked at IMAP for example and I reminded a discussion I
> > > > had perhaps 25 years ago with Bill Yeager and he had a really
> > > > good metaphor (and that was prior to “social networks” era),
> > > > which then led me to another such discussion with Mark Crispin
> > > > (rip)
> > > > The addition is that my brain is missing security in the picture
> > > > as a "superposition state” (and I use Quantum Physics on purpose
> > > > … not just in memory of our joint past at CERN!) in particular
> > > > recognising the intrication of privacy and security.
> > > > Now I thought initially ‘because defence is creating its own
> > > > twist here’ but then I realized that to a certain degree this is
> > > > as well because each of the 3 constituencies of your picture are
> > > > not just defenders, they are attackers too in multiple forms.
> > > > I am not sure (this early morning) if this is a primary level
> > > > issue or if it is a secondary level issue in your proposal.
> > > > Hope this helps a little bit
> > > > > On 4 May 2023, at 23:39, Brian E Carpenter
> > > > > <brian.e.carpenter@gmail.com> 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.google.com/url?q=https://www.ietf.org/mailman/listinfo/architecture-discuss&source=gmail-imap&ust=1683841175000000&usg=AOvVaw3DIB56mqn7ZU0a53yuDvJE
> > > > _______________________________________________
> > > > 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
> > 
> > _______________________________________________
> > Architecture-discuss mailing list
> > Architecture-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/architecture-discuss
> DaveO

> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss


-- 
---
tte@cs.fau.de