[Din] Re: next steps for DINRG

Lixia Zhang <lixia@cs.ucla.edu> Mon, 21 October 2024 13:38 UTC

Return-Path: <lixia@cs.ucla.edu>
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 BAC88C14F5E0 for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 06:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level:
X-Spam-Status: No, score=-2.004 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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=cs.ucla.edu
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 ICwwF-MrVpyf for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 06:38:44 -0700 (PDT)
Received: from mail.cs.ucla.edu (mail.cs.ucla.edu [131.179.128.66]) (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 26D9BC1D8FAC for <din@irtf.org>; Mon, 21 Oct 2024 06:38:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id D09593C011BC5; Mon, 21 Oct 2024 06:38:43 -0700 (PDT)
Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id KZPGP9kDyv4C; Mon, 21 Oct 2024 06:38:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 625493C011BDD; Mon, 21 Oct 2024 06:38:43 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu 625493C011BDD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1729517923; bh=PwL/dWIVLp+m6IgFUpeOTSI+4w1l//E3QLTa4TH33uo=; h=From:Message-Id:Mime-Version:Date:To; b=KCpA/LFR1+tmTP4ft+nWipldE/mQxxdLZoCkjEkR6r+CgQglq3tHgFjk7F5mi1Jrg H0mctJTL+6Iulhhy2laUbi3o5P/5YLWKBJIEK6dXBk9VkyD0FYJ7Ff8Gk7QGAkNEN1 UahIAY8Kb2wzk6j07oMEH4KFfgBVZ7n4cw3F6qvlN8Pac+eWF28wWeHa058uLozsGR IieqxwlvIlKDoa3hLsRms6sBHzxcDqorJcdDqsjKO7bAntsc6yEZK1lUTdYNHKAzIG AaeRGe6FjL8fytKC3Kc+ITiD0v8HTEyitd/40X7J8Xro3XVSWfKXfi52m457nWR3DN 8AmsAymJY7lNQ==
X-Virus-Scanned: amavis at mail.cs.ucla.edu
Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id S60AMQqyrVqv; Mon, 21 Oct 2024 06:38:43 -0700 (PDT)
Received: from smtpclient.apple (syn-076-091-005-005.res.spectrum.com [76.91.5.5]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 3390A3C011BC5; Mon, 21 Oct 2024 06:38:43 -0700 (PDT)
From: Lixia Zhang <lixia@cs.ucla.edu>
Message-Id: <BBE600B4-A2E7-4DC3-A2B1-70CE548F35C9@cs.ucla.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C751AC34-B0F3-451A-B054-15752101BC86"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
Date: Mon, 21 Oct 2024 06:38:32 -0700
In-Reply-To: <6d66bdb8-b546-40b1-b723-ee8ac80b8adb@app.fastmail.com>
To: Chad Kohalyk <chad@kohalyk.com>
References: <18BAB346-D64A-40A3-A29B-9146562E5674@dkutscher.net> <6d66bdb8-b546-40b1-b723-ee8ac80b8adb@app.fastmail.com>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Message-ID-Hash: TUWT727LTQQZQASMVSLTBSSXOSBRPMNK
X-Message-ID-Hash: TUWT727LTQQZQASMVSLTBSSXOSBRPMNK
X-MailFrom: lixia@cs.ucla.edu
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>
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/okxPXlDevJSnS735eqNlkiq1cG0>
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>

Chad, 

thanks for your suggested questions. We'll try to incorporate them into the discussions at IETF 121.

Lixia

> On Oct 18, 2024, at 9:40 AM, Chad Kohalyk <chad@kohalyk.com> wrote:
> 
> 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>