[Din] Re: next steps for DINRG

"eburger-l@standardstrack.com" <eburger-l@standardstrack.com> Mon, 21 October 2024 21:44 UTC

Return-Path: <eburger-l@standardstrack.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 E12AAC1E0D9B for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 14:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=standardstrack.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 Xk5cCkIwE_yb for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 14:44:38 -0700 (PDT)
Received: from se6i-iad1.servconfig.com (se6i-iad1.servconfig.com [173.231.241.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B2B6C1E6419 for <din@irtf.org>; Mon, 21 Oct 2024 14:44:38 -0700 (PDT)
Received: from biz221.inmotionhosting.com ([192.145.239.201]) by se6-iad1.servconfig.com with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <eburger-l@standardstrack.com>) id 1t30CO-001mmd-Q6 for din@irtf.org; Mon, 21 Oct 2024 17:44:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=Message-Id:In-Reply-To:To:References:Date: Subject:Mime-Version:Content-Type:From:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4NNcDwqUfv0SBjp5X/vMB+c+cwgDmCHs9rAZQoLj3Fo=; b=ZfU2Ose1RSUtOMX4jkr5MbxD1b d6DODNor4kpTPEBB0ts7vpOcg4LUOQnnnUIEstvNx5MJB7O0rEIvW/7tk3KvfiY5mmy00vnoVaXp2 1Kmx04xG0r6Z+q/1m3xbw0wvboPnTa8NZhCAqp7WGv1obG+5E5ObyCUVERBWQ19FWNoUTSTFbkR0Y oBp0+Uyyb+GnlpO/jy2+U2Vech/bDV0FrD+AYF/0gUJc+YpuPATlefZ0nN4BpKUbxP31lKmE1j6uk tkMLPRB++xn6vlHungfa6+L8QwuhKGMw0I5sTy7HN8hyNhIia3/lRYmo+vvxJxU+1EAv+uYQkEPzk Iwng+STA==;
Received: from [68.100.97.239] (port=62724 helo=smtpclient.apple) by biz221.inmotionhosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <eburger-l@standardstrack.com>) id 1t30CN-00C3mk-1f for din@irtf.org; Mon, 21 Oct 2024 14:44:23 -0700
From: "eburger-l@standardstrack.com" <eburger-l@standardstrack.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F0E0341B-A6E3-45AD-BAF5-3CD05BD3D258"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Date: Mon, 21 Oct 2024 17:44:12 -0400
References: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net> <6d66bdb8-b546-40b1-b723-ee8ac80b8adb@app.fastmail.com> <BYAPR01MB4391391642D149D59316D9F0CB402@BYAPR01MB4391.prod.exchangelabs.com> <F0DCA536-FBE4-4292-923A-796977A90052@cs.ucla.edu> <ac3bea84-aeac-4af2-a956-9cb23511656b@mit.edu>
To: "din@irtf.org" <din@irtf.org>
In-Reply-To: <ac3bea84-aeac-4af2-a956-9cb23511656b@mit.edu>
Message-Id: <0E0BA301-F8D4-469F-95F5-0D85F7C14DF5@standardstrack.com>
X-Mailer: Apple Mail (2.3776.700.51.11.1)
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger-l@standardstrack.com
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger-l@standardstrack.com
X-Originating-IP: 192.145.239.201
X-SpamExperts-Domain: biz221.inmotionhosting.com
X-SpamExperts-Username: 192.145.239.201
Authentication-Results: servconfig.com; auth=pass smtp.auth=192.145.239.201@biz221.inmotionhosting.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT8K5sWFm1kG3DMIcM0cCSEnPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5wAnfCnTCZunuP0OK3Vuj0Pj3CSdYahsEhiizd3WfZtETe3 423/tRoIeEXdj45Qj7TlYLLlWSy3OGfGBNeqx2anSNm0uvGkQ9N3T1B7GSW8UU1ASQliVZgeYx9h jgIqvLkbbXv5t2AKpifmmFNdgos1TTrJV7QCxh2EoXFp5aAV72bMT5B6fVPaaM1DGoKbzOEgChGt JK7hkwwZxIKzfl+4p6KrPCklAmnloYenuVMJiq7VZqJmzCeHtqZ+QtMgTB3ouQYW33h0HHdOkCiQ DhSZsIZXKmwzbGT4VvpTL0Eb54bT3EszvIbAbB2Zy01d/7IXjkdTeVZ2qGWx/wHRpX689SKIcp7K A7p/sHfpQQwXaNclsf95ERnfa5/3utVu63cGgIqsnjgPIxt+QJb5OikLXkWnVOQkrQHWbOxhyRTo tpJPAxQcPye9PqqNmj15et+ZSjmmVb1jzWCjpHhh1WjZqXWvTtyZt5+E2rHRTxiOPQKf33qQtTYr DPixEr4D2aetI4g+l6rCWbY0MZcgnbHs5GDDsmZps+zWSndDjfAX1FPC7nhBalu6FpNu+vpEvEuj EdkF5Xi2k41TfMEM71Mzxf+XspAxVAxwNHnF50xJ3jFi6zY7IPb59mOJ3U3G1fEqM56VVlcswDb0 N8Su4voNiwQzKw+6v3CaIMG6s7LqJGvZAoaaaP911N9Xvv+Ex/E0rvVnjb0Ichcyq7aIVE7mOf8K 6gi7LLkWJMzMfntN5do1PCcgCFH4kF3SzLbKBwk8CVsONrMJuGzuoGnKTKcynfe6ItSMP8viZU9Y RdHPGRgIbopubRss8xkqpmE+JcjtpM4E3MthniXwMnyBEVPa8GPC8Eyd4JcHdvS3AcklTGe7bjdu wuXOd+dEYbnY0a22Km4sAJ1Q+VAXXWPIu0H96ERCN/TYO8Po1sFYLrYxp7Wpcv7j2jxrOCLgGCCA 55675p5YDwmJJgZ5l8uaoKnRBIgbHMEXa7YftfqFkw047PojpG0kUm0Gzq2MTdkIrHc=
X-Report-Abuse-To: spam@se1-lax1.servconfig.com
Message-ID-Hash: VFQB6DJ52UJ27Y7DUTAJQ5RFWAB2YT5Q
X-Message-ID-Hash: VFQB6DJ52UJ27Y7DUTAJQ5RFWAB2YT5Q
X-MailFrom: eburger-l@standardstrack.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
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/MSqTwbv-E9mWHk4WhnoUQOtwkB8>
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>

And let us not forget that there might be economic value in the trust value-proposition of distributed networks, which outweighs the simple calculation of more expensive capital expense and stupidly more expensive operating expense.

> On Oct 21, 2024, at 4:33 PM, William Lehr <wlehr@mit.edu> wrote:
> 
> RE: "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."
> 
> There are certainly economic models that argue that efficiency and cost-savings favor centralization, but that is definitely NOT a consensus conclusion since it very much depends on the context. In a dynamic environment  centralization may very well be less efficient and more costly. The economic arguments for productive efficiency (cost-savings) often rely on scale economies that are assumed to depend on centralized organization of production. The technical and economic implications of more or less decentralization depend on the context and dimension of performance you are considering. Control (decision-making power), ownership, and Parties bearing costs/benefits may all vary in different degrees with respect to the extent of centralization or decentralization. 
> 
> On 10/21/24 9:54 AM, Lixia Zhang wrote:
>> Hi Thomas, 
>> 
>> thanks for your great set of questions. 
>> Just a personal comment: most of your questions seem to me related to one basic question one way or another: what is exactly the definition of "Internet decentralization" that we are aiming at?
>> 
>> I think clarifying this definition would directly answer the questions about VMs vs bare-metal, machine locations etc. This would also indirectly touch on some other questions (e.g. do so-called Web3 systems have bake-in decentralization). 
>> 
>> I also appreciate your suggestion of identifying potential relations between DINRG and some WGs work.
>> 
>> Lixia
>> 
>>> On Oct 18, 2024, at 12:30 PM, Thomas Hardjono <hardjono@MIT.EDU> <mailto: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 <mailto:chad@kohalyk.com>>
>>> Date: Friday, October 18, 2024 at 12:41 PM
>>> To: din@irtf.org <mailto:din@irtf.org> <din@irtf.org <mailto: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 <mailto:din@irtf.org>
>>> To unsubscribe send an email to din-leave@irtf.org <mailto:din-leave@irtf.org>
>>>  
>>>  
>>> Attachments:
>>> signature.asc
>>>  
>>> _______________________________________________
>>> Din mailing list -- din@irtf.org <mailto:din@irtf.org>
>>> To unsubscribe send an email to din-leave@irtf.org <mailto:din-leave@irtf.org>
>> 
>> 
>> _______________________________________________
>> Din mailing list -- din@irtf.org <mailto:din@irtf.org>
>> To unsubscribe send an email to din-leave@irtf.org <mailto:din-leave@irtf.org>
> -- 
> 
> ==+==+==+==+==+==+==+==+==+==+==+==+==+
>  Dr. William Lehr
>  Research Associate
>  Computer Science and Artificial Intelligence Laboratory (CSAIL)
>  
>  MIT Office:
>    Massachusetts Institute of Technology
>    32 Vassar Street (32-G532)
>    Cambridge, MA 02139
>   
>    tel:     617-258-0630
>    fax:     617-253-2673
> 
>  Home Office (preferred):
>    94 Hubbard street
>    Concord, MA 01742
> 
>    cell:    978-618-3775 (preferred)
>    fixed:   978-287-0525
> 
>  website: http://csail.mit.edu/~wlehr
>  email:   wlehr@mit.edu <mailto:wlehr@mit.edu>
> 
> ==+==+==+==+==+==+==+==+==+==+==+==+==+
> _______________________________________________
> Din mailing list -- din@irtf.org
> To unsubscribe send an email to din-leave@irtf.org