[Din] Re: next steps for DINRG Re: 202410191733.AYC

"Abraham Y. Chen" <aychen@avinta.com> Sun, 20 October 2024 14:21 UTC

Return-Path: <aychen@avinta.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 A6105C18DBA3 for <din@ietfa.amsl.com>; Sun, 20 Oct 2024 07:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=avinta.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 LHzow9coB6Sn for <din@ietfa.amsl.com>; Sun, 20 Oct 2024 07:21:41 -0700 (PDT)
Received: from cp22.lowesthosting.com (cp22.lowesthosting.com [23.111.133.162]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E47DC137360 for <din@irtf.org>; Sun, 20 Oct 2024 07:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avinta.com; s=default; h=In-Reply-To:References:Cc:To:Subject:From:MIME-Version:Date: Message-ID:Content-Type:Sender:Reply-To: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=B5Td+zzYulLZF7N/76wi43EKJYxucf4oxkKEQ+nBEl4=; b=wbOxMmgJ+Tkae9mw6475W6D22S xCvS+L+ialfIBXLBJNZWeCeazMaVbF2p2JxJczDpGin7tUJ4yxwYpvciOpN6PoWnshQJvJf97R/xl asZvKCY5Ci8/tLJMI+peYrlgoxePUeSRZZYoBgwHjgNRtJPoDpFMYcMiCLeR7bLAatNvPR1pHgzoP yRGq4QQS9DiNwwjKHVeTGlEV7+Sh7wXrfTQnEzVUfhewNQHESC7uv2PkFwlQ92MH8QlkAsV0c4eI9 A/u1fS7RZDqsqriBEIdN3SoGa87QpW8zsElJ6y1e1B8dtLWZ2nP2OecGDGWYNSA0gj5HbpDyVx4Db 84ziPFzA==;
Received: from syn-184-153-001-039.res.spectrum.com ([184.153.1.39]:64616 helo=[192.168.1.142]) by cp22.lowesthosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from <aychen@avinta.com>) id 1t2WoM-00E948-4I; Sun, 20 Oct 2024 10:21:38 -0400
Content-Type: multipart/alternative; boundary="------------ywFmN6OouMHswaaz0Elm4pxw"
Message-ID: <65eb7bb8-7017-4a4f-a3c0-838e2ebe1887@avinta.com>
Date: Sun, 20 Oct 2024 10:21:32 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: "Abraham Y. Chen" <aychen@avinta.com>
To: Dirk Kutscher <ietf@dkutscher.net>
References: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net>
Content-Language: en-US
X-Priority: 1 (Highest)
In-Reply-To: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net>
X-Antivirus: Avast (VPS 241020-2, 10/20/2024), Outbound message
X-Antivirus-Status: Clean
X-MagicSpam-TUUID: a45ec86d-bb31-45ba-8dcf-9600f5b98284
X-MagicSpam-SUUID: 5878135b-c71b-4768-9db3-9223e8d16c76
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cp22.lowesthosting.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - avinta.com
X-Get-Message-Sender-Via: cp22.lowesthosting.com: authenticated_id: aychen@avinta.com
X-Authenticated-Sender: cp22.lowesthosting.com: aychen@avinta.com
X-Source:
X-Source-Args:
X-Source-Dir:
Message-ID-Hash: SHG7H2PFLKZDCSZHTDERIITTVV6BS4EF
X-Message-ID-Hash: SHG7H2PFLKZDCSZHTDERIITTVV6BS4EF
X-MailFrom: aychen@avinta.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: din@irtf.org, "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/PYZnJkSaJWcnNAM5JWPH8m--teg>
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>

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 todin-leave@irtf.org



-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com