[Din] Re: next steps for DINRG

Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> Tue, 22 October 2024 06:55 UTC

Return-Path: <crowcroft@gmail.com>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A0DC1E0D89 for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 23:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.653
X-Spam-Level:
X-Spam-Status: No, score=-1.653 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 y5oyaBtDMAIR for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 23:55:44 -0700 (PDT)
Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE11BC1840DD for <din@irtf.org>; Mon, 21 Oct 2024 23:55:43 -0700 (PDT)
Received: by mail-lj1-f171.google.com with SMTP id 38308e7fff4ca-2fb5a9c7420so52047041fa.3 for <din@irtf.org>; Mon, 21 Oct 2024 23:55:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729580142; x=1730184942; 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=RgOMTOcJwLN/fLU0LVGv5zG3ze8+ENvj11X6Zec39kg=; b=OJbYLQLClnVWOuia+smQ87tN/q8KKACBNW0B3rftWczOGal7WOVS39YkjaOUQ5ZuQn PfZP3igKOMwtWTUEIr8wqWVAEPMxAI9cSI1ma1kGwHXF0KuIwq2k6wTVVUgmX2wNRFYI xn6pXI6XLZJ3EX117Ni+yx5yfYDYe1fz/Z2b2pFgX14PcSScoj7hOuOM3JayTk0wqsJu hcsZyWqbZKka1YSLs1WEYaFHjMGrUFqOt+FLggPSCusOrU0V+WdTNLPWaFOnjaCtDRks eif4UlgV2u0hQ6xxr5nYCox4/Jo1G3rogjV73Zo1O7sCTxP55MSJ9+LNXeGOUgSJOFhv bk1A==
X-Forwarded-Encrypted: i=1; AJvYcCWMjmH/Lh/aRCWOPh+6Fc8GW1L6vkVju1kijcvqBwtqj+rkk+fsnqUTpXcU71AYQ3JJ6+0=@irtf.org
X-Gm-Message-State: AOJu0Yx25T9j6fwbSCP8OwSgtMVjjzhfaD2ek3l9MV60ukXyPSBXdgPX yN4rtyti5Vn7fNl6j+DBmz347vcDgRsIk06418EDS9NbrTas7u9Au4qKi0pi4zvcMO9Qp2tesXz fUGQPjzqJ/e2AonnYY3RmKyrrcQY=
X-Google-Smtp-Source: AGHT+IGRn/DyaMjm9ImQ7h4nNT2ndJRXPlejqGXWLv6YMfqj5qfohKWp71k21L2hP7IkxIjdtBbiJf9yge3KJ97tYnE=
X-Received: by 2002:a2e:4a11:0:b0:2fb:34dc:7beb with SMTP id 38308e7fff4ca-2fb82ea71a5mr48667071fa.12.1729580141528; Mon, 21 Oct 2024 23:55:41 -0700 (PDT)
MIME-Version: 1.0
References: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net> <6d66bdb8-b546-40b1-b723-ee8ac80b8adb@app.fastmail.com> <BYAPR01MB4391391642D149D59316D9F0CB402@BYAPR01MB4391.prod.exchangelabs.com>
In-Reply-To: <BYAPR01MB4391391642D149D59316D9F0CB402@BYAPR01MB4391.prod.exchangelabs.com>
From: Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>
Date: Tue, 22 Oct 2024 07:55:24 +0100
Message-ID: <CAEeTej+iRbi+cCuvKFRDaWU=XgpHR4xOMXZ9FpOo040gEwOQVw@mail.gmail.com>
To: Thomas Hardjono <hardjono@mit.edu>
Content-Type: multipart/alternative; boundary="000000000000f2512006250b410a"
Message-ID-Hash: PACXD232BMSTZMNXETLOF257G7MIECUV
X-Message-ID-Hash: PACXD232BMSTZMNXETLOF257G7MIECUV
X-MailFrom: crowcroft@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-din.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Chad Kohalyk <chad@kohalyk.com>, "din@irtf.org" <din@irtf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Din] Re: next steps for DINRG
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/pkQp9Qx_yTRTQtM7AW6R6sweUlk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Owner: <mailto:din-owner@irtf.org>
List-Post: <mailto:din@irtf.org>
List-Subscribe: <mailto:din-join@irtf.org>
List-Unsubscribe: <mailto:din-leave@irtf.org>

what if 90% of those blockchain/cryptocurrency nodes are running in the
same country on a network powerd by a single electricity provider? with a
single state controlled border to the rest of the world, for IP and people?
or indeed we could have a decentralised phone-based currency that requires
SIMs from a specific provider and government regstraton of users of those
SIMs/phones with national id cards/passports ....

note the other way around, many cloud service providers are
administratively/economically/politically (e.g. subject to laws from one
dominant jurisdicrtion) centralised, but use decentralised or at least
distributed or federated techniques to provide resilience - hence
replicated state machines/consensus algorithms, conflict-free
replicated data types all allow systems to scale across multiple data
centers so that we get fault tolerance and continuous operation, but they
are not organisationally decentralised in any way.

On Fri, Oct 18, 2024 at 8:33 PM Thomas Hardjono <hardjono@mit.edu> wrote:

>
>
> Just some quick thoughts on the “What’s next” question.
>
>
>
> One of the things DINRG could focus on is the standards (architectures,
> protocols, etc.) and tools to measure the degree of decentralization of
> systems and networks (notably those DLT-based offerings that claim to be
> “decentralized”).
>
>
>
> Let’s say a DLT network (e.g. blockchain) has 100 nodes and the network
> claims to be operating in decentralized manner.   What if it turns out that
> 90% of those nodes are actually VMs running in the cloud, and what if it
> turns out that 90% of those cloud-based VMs are running on the same Cloud
> Provider? (worse, what if they’re running on the same  Zones, like US-West
> and US-East).  Would you accept their claim of decentralization seriously?
>
>
>
>
>
> Some possible future work for DINRG:
>
>
>
> -- Could DIN look at protocols that report on which nodes are running on
> bare-metal, versus physically separated VMs, versus VMs clustered in a
> given zone.
>
>
>
> -- Could Device-ID and device-stack identifiers be useful (building on
> protocols defined in the RATS WG and TEEP WG).
>
>
>
> -- Could DIN leverage the work already being done in the IEF WGs (e.g.
> RATS, SCITT, etc), and also from other industry bodies (e.g. TCG DICE;
> OpenCompute; Confidential Computing Consortium; etc).
>
>
>
> -- Could DIN be the funnel/filter into which near-mature proposal can be
> fed into working groups in the IETF. An example of this was the Group
> Security RG (GSEC) that funneled some ready items into the MSEC WG.
>
>
>
> https://www.irtf.org/concluded/gsec.html
>
> https://datatracker.ietf.org/wg/msec/about/
>
>
>
>
>
>
>
> PS.  Yes I’m aware of economic papers/analysis stating that efficiency and
> cost-savings favors centralization.  In contrast, I’m referring to future
> so-called Web3 systems that bake-in decentralization patterns to avoid
> these concentrations of power.
>
>
>
>
>
> Best
>
>
>
> --thomas
>
>
>
>
>
>
>
>
>
>
>
>
>
> *From: *Chad Kohalyk <chad@kohalyk.com>
> *Date: *Friday, October 18, 2024 at 12:41 PM
> *To: *din@irtf.org <din@irtf.org>
> *Subject: *[Din] Re: next steps for DINRG
>
> Thanks Dirk.
>
>
>
> One possibility is to discuss “What now?”
>
>
>
> I think that was one of the conclusions of the IETF120 discussion: who
> should DINRG collaborate with in order to effect change?
>
>
>
> In other words, what is DINRG’s theory of change? Where does the research
> go once it is complete? Is DINRG’s role purely observatory? On who’s
> behalf? (merely the IRTF?)
>
>
>
> Possibly these were answered when DINRG was stood up, but based on the
> conversation in Vancouver it didn’t seem like the community understood
> what’s next.
>
>
>
> So I submit this as a topic suggestion.
>
>
>
> Thank you,
>
>
>
> Chad Kohalyk
>
>
>
>
>
>
>
> On Fri, Oct 18, 2024, at 1:41 AM, Dirk Kutscher wrote:
>
> Dear all,
>
> in Dublin, we are planning to continue our discussion on next steps for
> DINRG.
>
> To that end, we are soliciting suggestions, interests indications, and
> questions here. If you have a suggestion, please feel free to share it here
> or by personal e-mail.
>
> We will collect everything and then prepare a summary before the meeting.
>
> As a bit of background:
>
> As chartered, DINRG has different objectives:
>
>    - Investigation of the root causes of Internet centralization, and
>    articulation of the impacts of the market economy, architecture and
>    protocol designs, as well as government regulations;
>    - Measurement of the Internet centralization and the consequential
>    societal impacts;
>    - Characterization and assessment of observed Internet centralization;
>    - Development of a common terminology and understanding of
>    (de-)centralization;
>    - Interaction with the broader research community to explore new
>    research topics and technical solutions for decentralized system and
>    application development;
>    - Documentation of the outcome from the above efforts via different
>    means (e.g., research papers and RFCs) as inputs to the broader
>    conversation around centralization; and
>    - Facilitation of discussions between researchers, organizations and
>    individuals involved in Internet standards and regulations.
>
> Let us know, which of these objectives should be emphasized in your view,
> and whether you have specific interests within these topics that should be
> discussed more.
>
> Best regards,
>
> Dirk and Lixia
>
> _______________________________________________
>
> Din mailing list -- din@irtf.org
>
> To unsubscribe send an email to din-leave@irtf.org
>
>
>
>
>
> *Attachments:*
>
>    - signature.asc
>
>
> _______________________________________________
> Din mailing list -- din@irtf.org
> To unsubscribe send an email to din-leave@irtf.org
>