[Din] Re: next steps for DINRG
Christian Huitema <huitema@huitema.net> Tue, 22 October 2024 06:47 UTC
Return-Path: <huitema@huitema.net>
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 08008C1E6411; Mon, 21 Oct 2024 23:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.095
X-Spam-Level:
X-Spam-Status: No, score=0.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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, URI_DOTEDU=1.999] 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 hydFNdYfc8E0; Mon, 21 Oct 2024 23:47:12 -0700 (PDT)
Received: from se04.mfg.siteprotect.com (se04.mfg.siteprotect.com [64.26.60.167]) (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 148AAC1ED17F; Mon, 21 Oct 2024 23:47:08 -0700 (PDT)
Received: from smtpauth02.mfg.siteprotect.com ([64.26.60.151]) by se04.mfg.siteprotect.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1t38fW-00GR3n-Uz; Tue, 22 Oct 2024 02:47:07 -0400
Received: from [192.168.1.109] (unknown [172.56.169.218]) (Authenticated sender: huitema@huitema.net) by smtpauth02.mfg.siteprotect.com (Postfix) with ESMTPSA id 4XXjQY5NHLz2YQR6m; Tue, 22 Oct 2024 02:47:01 -0400 (EDT)
Message-ID: <4a6ffff3-0ca5-4636-849a-6634b5c6a23d@huitema.net>
Date: Mon, 21 Oct 2024 23:46:59 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "eburger-l@standardstrack.com" <eburger-l=40standardstrack.com@dmarc.ietf.org>, "din@irtf.org" <din@irtf.org>
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> <0E0BA301-F8D4-469F-95F5-0D85F7C14DF5@standardstrack.com>
Content-Language: en-US
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <0E0BA301-F8D4-469F-95F5-0D85F7C14DF5@standardstrack.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Authentication-Results: mfg.siteprotect.com; auth=pass smtp.auth=huitema@huitema.net
X-Originating-IP: 64.26.60.151
X-SpamExperts-Domain: mfg.outbound
X-SpamExperts-Username: 64.26.60.150/31
Authentication-Results: mfg.siteprotect.com; auth=pass smtp.auth=64.26.60.150/31@mfg.outbound
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.17)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+nfCy2ps7kh9RNJr/YgGHnPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zPBpdOVfFzSIrBYSKdtRAKI0qX/idXt8HW1ZgTBZnhGXbi NRRd3b9l0whETz17iKOQt8zdps5PdmSRHyZb8GsoIIon7zyTe6Ob+addVWQ7w/xBBURrPCDE1Yhg fEP5NLh4mkvGNo8cTUD87Jn5X53EzF15PCSui5+4L7hkfDTShnQOD0r6/AaHZiEtdTMtMli49y/l 0hTSEPM9sGhiHuwwrEi0xXpdqQoV2VEVTL5KHGfPfoYZI4Eyb6mxKZxvI9OOFSu8LDHlWv6Ktlj1 6+bZyF5kPcY3yyBSmhMsWvJAHLDY27xZiOmTUqT1Bu490izs/sb16ESDOWr/ATs5NT2bPEg+PVRT iaxPY52n0Pp/84HxfltMiSZ83GC+sfvCub65ly/KzXZcbxEplFAY2HW4x77VIfsaFU/Ln+CB+gPb YsViU2BjcxhUDV/LpAkZZ077Ihw1/2aYJ0di+mUsVIbgoFJ80FFIe862PoHHEB5bxfnsBRcwLyS7 /dLQBK2jgbYY4L7u6QJ/jXXAPItovk04SHGRxyggC88Xt6L7WCGe+7kOaWoOILZYlh9qvou52Uwk by6/IfQd2Aiv1booGg+YrSOIPpeqwlm2NDGXIJ2x7NYxnEz+k42lJWdonCrrul/Y56S87TkaUZKJ VeZtu4pya+Qn+z5krvhLk/vl+AFNFH3ligAgSzNnSYDhv/BI/rPPgwcF1qJAplOh2sp5ZoqD0mCT pRgcoQPyBmzG6HJjvZ5ECu3zMC6/UIvU+dfuPW5lpvsHuKYSZZJWrfSRdSppGBZ9WqzVCVc3XCLd ApIlvs05xNkDixZkyu3YxR8DqirUsFwxUNXSz5fN97hW3Modd3bFD5e7rlmRAk8Q6Bi8St9cgwfE SnT0xiMu6dXEPs5bZTOJtRe8KjrKlstUG2LnBj1xWO9djbmqs0AOQOZgIATiZUr9jJhgIra1kzwO Z5qsbcSt35Qfv1p/R09BN2KFlJMRPkiuApKqkLmPwA7Qe6T9NadvA6Ixg4dk9fQdVkF5+KSQ0yZK EOzaaDVrPJlqGcwsUgXqOasNbkUEae8RjkWRQ0r+yjWdkSe7YM5CQjE=
X-Report-Abuse-To: spam@se02.mfg.siteprotect.com
Message-ID-Hash: N5EANZI4EJYYYLW755QPWGP52P5IUN3N
X-Message-ID-Hash: N5EANZI4EJYYYLW755QPWGP52P5IUN3N
X-MailFrom: huitema@huitema.net
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/bl0mrjiE_71qUU_DiHVO7464r3Q>
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>
The classic economic theory of centralization was all about economies of scale. Per that theory, the limits to centralization was set by the increased complexity of the ever larger enterprise. Per the theory, at some point the conglomerate could not react fast enough, and more agile competitors would start competing efficiently. That classic theory did not take into account network effects, which reinforce the monopolies. Also, information technology supposedly makes conglomerates easier to manage -- at least compared to pushing forms in triplicate and taking the train to go to meetings. The "identity" issue that Abraham Chem mentioned is an example of these network effects. Decentralized solutions may help mitigate the network effects. That would mean "commoditizing" a number of platform components -- naming and discovery, introduction, etc. Din RG may be a good place to identify these solutions. Then, the community might produce helpful standards -- similar to what happened with MLS. And applications will use them. Maybe. Also, it would be nice if instead of focusing on platforms developments could focus on a few applications. The good platforms components almost come after the application. Developing platforms before developing applications seems rational, but it almost never works for software. So maybe identify a couple of applications first... -- Christian Huitema On 10/21/2024 2:44 PM, eburger-l@standardstrack.com wrote: > 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 > > > _______________________________________________ > Din mailing list -- din@irtf.org > To unsubscribe send an email to din-leave@irtf.org
- [Din] next steps for DINRG Dirk Kutscher
- [Din] Re: next steps for DINRG Chad Kohalyk
- [Din] Re: next steps for DINRG Thomas Hardjono
- [Din] Re: next steps for DINRG 김우태(Operation연구TF)
- [Din] Re: next steps for DINRG Re: 202410191733.A… Abraham Y. Chen
- [Din] Re: next steps for DINRG Lixia Zhang
- [Din] Re: next steps for DINRG Lixia Zhang
- [Din] Re: next steps for DINRG William Lehr
- [Din] Re: next steps for DINRG Thomas Hardjono
- [Din] Re: next steps for DINRG Re: 202410191733.A… Lixia Zhang
- [Din] Re: next steps for DINRG eburger-l@standardstrack.com
- [Din] Re: next steps for DINRG Lixia Zhang
- [Din] Re: next steps for DINRG Christian Huitema
- [Din] Re: next steps for DINRG Jon Crowcroft
- [Din] Re: next steps for DINRG William Lehr
- [Din] Re: next steps for DINRG Thomas Hardjono
- [Din] Re: next steps for DINRG Re: 202410191733.A… William Lehr
- [Din] Re: next steps for DINRG Re: 202410191733.A… Jens Finkhäuser
- [Din] Re: next steps for DINRG Dirk Trossen
- [Din] Re: next steps for DINRG Dirk Trossen
- [Din] Re: next steps for DINRG Re: 202410230956.A… Abraham Y. Chen
- [Din] Re: next steps for DINRG Re: 2024110211733.… Abraham Y. Chen
- [Din] Re: next steps for DINRG Re: 202410231010.A… Abraham Y. Chen
- [Din] Re: next steps for DINRG Re: 2024110211733.… William Lehr