[Din] Re: next steps for DINRG Re: 202410191733.AYC
Jens Finkhäuser <jens@interpeer.org> Tue, 22 October 2024 10:35 UTC
Return-Path: <jens@interpeer.org>
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 DDEE3C1CAE6A for <din@ietfa.amsl.com>; Tue, 22 Oct 2024 03:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=interpeer.org
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 R5aSwE4SjvB4 for <din@ietfa.amsl.com>; Tue, 22 Oct 2024 03:35:18 -0700 (PDT)
Received: from mailout-l3b-97.contactoffice.com (mailout-l3b-97.contactoffice.com [212.3.242.97]) (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 67051C18DB98 for <din@irtf.org>; Tue, 22 Oct 2024 03:35:16 -0700 (PDT)
Received: from ichabod.co-bxl (ichabod.co-bxl [10.2.0.36]) by mailout-l3b-97.contactoffice.com (Postfix) with ESMTP id DE53B12AE; Tue, 22 Oct 2024 12:35:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1729593313; s=20241018-hq79; d=interpeer.org; i=jens@interpeer.org; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type; bh=k28QjOrfpF8lD7ovpUhiEPAfBH0/vRgFgyAPRVkV6Zo=; b=kVIhsWdozquXF9Rln0NoKsh7Neo4buCsEX9+b7y6s2us8hJ8RV/JvHhX7K4yjIdy DHBirScHemqTNsM4xgMYzZ9/0Ullf/w/6onIbKuNTM1m4vok7D6NxVyNlauryZO6NDr kjb031PJBadPIyowdnSnHC7Fxp545Ik9wbK1UkjDuPtvBG73mLWCxPsAzmZfbD+I4QQ d8Tu2SYw26sfhSg684pkT5cg1o2jz8LiX8wDrHx5XPbYjRJEnkYiAUoS7EOrnHRAGzL bx9psZe2hb9WhnXiTPTzY1c3y4d9VYGlmDBWHdqgt/p7BV4CfI++PcE9GQuaw4gyjVP Rj7QjC2rwQ==
Date: Tue, 22 Oct 2024 12:35:09 +0200
From: Jens Finkhäuser <jens@interpeer.org>
To: Lixia Zhang <lixia@cs.ucla.edu>, William Lehr <wlehr@mit.edu>, "Abraham Y. Chen" <aychen=40avinta.com@dmarc.ietf.org>
Message-ID: <158492064.805253.1729593309069@ichabod.co-bxl>
In-Reply-To: <8730a6a0-cb89-45e6-868c-26993453ed4e@mit.edu>
References: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net> <65eb7bb8-7017-4a4f-a3c0-838e2ebe1887@avinta.com> <79528934-BCED-44CD-A44C-C4440A939771@cs.ucla.edu> <8730a6a0-cb89-45e6-868c-26993453ed4e@mit.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_805251_1136294314.1729593309061"
X-Mailer: ContactOffice Mail
X-ContactOffice-Account: com:366827674
Message-ID-Hash: ETBSKH3Q4S25CNQUMNMGQ356BWDCZC23
X-Message-ID-Hash: ETBSKH3Q4S25CNQUMNMGQ356BWDCZC23
X-MailFrom: jens@interpeer.org
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: "din@irtf.org" <din@irtf.org>, Dirk Kutscher <ietf@dkutscher.net>, "Chen, Abraham Y." <AYChen@alum.MIT.edu>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Din] Re: next steps for DINRG Re: 202410191733.AYC
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/hsSRuvjVfNGxOEW2zIxcA2PMgy8>
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>
Hi all, On Oct 21, 2024 at 10:40 PM, William Lehr <wlehr@mit.edu> wrote: distributed and decentralized often mean two different things. A distributed mechanism may be subject to centralized control. That's the same with decentralized mechanisms. Blockchain comes to mind, where control over the algorithms employed is typically centralized. Baran's old RAND memorandum has good definitions of distributed/decentralized with regards to network architectures. One should perhaps distinguish between network architectures and control mechanisms, to avoid this kind of confusion. Jens decentralization has important implications for independence wrt failure modes which impacts reliability. Telephone service reliability is enhanced because failure of PSTN and Internet are not perfectly correlated so failure of PSTN need not mean failure of ability to make phone call. virtualization allows control and function to be separated in geospace (distributed) that can have implications for performance (e.g., latency, reliability) that may not be known to higher-layer users that may seek to exert centralized control over a system that is distributed, etc. On 10/21/24 10:17 AM, Lixia Zhang wrote: Hi Abe, I think you brought up a set of very interesting, and also very important, questions and comments. To me, the top few are: "distributed or decentralized": it seems worth clarifying whether the two words mean the same or different things in the DINRG context. the question in Thomas msg showed up again: how much the node locations matter. "we find that Internet users have no permanent identity": this is a fact, how this fact relates/impacts (de)centralization. To everyone on the list: please share your suggestions about next step. Dirk and I will try our best to summarize and structure all the suggested discussion topics into Dublin agenda. Lixia On Oct 20, 2024, at 7:21 AM, Abraham Y. Chen <aychen=40avinta.com@dmarc.ietf.org> wrote: Dear Dirk: 0) I have been reading the eMail threads and learning the charter of this Group for awhile. I would like to start from trying to understand your first DINRG objective: 1) " Investigation of the root causes of Internet centralization ... ": Centralization vs. decentralization in a system could manifest in surprisingly alternating manners depending on which particular perspective that one's investigation is focused upon. For example, A. During the Internet infancy days, the PSTN (Public Switched Telephone Network) was criticized as being too centralized implying that the Internet would be distributed or decentralized. As this Group agrees, the Internet is now far from being decentralized, after all. The reason for this discrepancy is that back then colleagues were looking at the network facility to assume that the operations would have the same characteristics. B. Comparing the operations today, we find that Internet users have no permanent identity, except temporarily assigned by multi-national business conglomerates, thus not able to freely communicate with one another, starting from even a neighbor. This means that the Internet operation today is a centralized one. In contrast, PSTN supports dial-up modems that enable any and every user the freedom / flexibility / independence of contacting anyone around the world anytime for data communication (This was how the Internet initially got popularized, although very slow by today's standards) which is clearly a distributed and decentralized operation. 2) The above may sound contradicting that a centralized facility supports decentralized operation while a decentralized one operates centralized. The fact is that the top layer operational behavior of a system determines which way it is from a user's viewpoint. In OSI 7 Layer model, as far as I could understand, we should set distributed/decentralized as the criterion at OSI Layer 7 for every system. Which way the lower Layers appear to be really does not matter, as long as they can eventually support the ultimate goal. 3) More specifically, the PSTN core equipment is so centralized that the identity of every subscriber loop is predetermined with a phone number. So, a CPE (Customer Premises Equipment) can be mass produced without the capability to acquire an identification upon plugging into a jack at the end of a subscriber loop. Essentially, the DHCP operation has already been accomplished in a user's mind. In the Internet, however, an IoT has to go through the process of acquiring an IP address (yet temporary) from the network core before it can operate, which means that an user can not operate independently at well. 4) The above may be vague, unorganized, or philosophical. This is because I just began to formulate this analytical approach for visualizing the problem at hand. I believe that we do need to exercise our minds from this angle, or similar to be able to set the criteria and priority for qualifying an application or operation. So that, we may have some chance to achieve the goal of "decentralizing the Internet". 5) Essentially, I believe that if a user does not have a permanent identity (static IP address) for communication through a system, the operation becomes centralized by having to rely upon a focal facility serving the coordination functions. I look forward to your thoughts. Regards, Abe (2024-10-20 10:21 EDT) On 2024-10-18 04:41, 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 Virus-free.www.avast.com _______________________________________________ Din mailing list -- din@irtf.org To unsubscribe send an email to din-leave@irtf.org _______________________________________________Din mailing list -- din@irtf.orgTo unsubscribe send an email to 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==+==+==+==+==+==+==+==+==+==+==+==+==+ _______________________________________________ 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