[Din] Re: next steps for DINRG
Thomas Hardjono <hardjono@mit.edu> Mon, 21 October 2024 20:39 UTC
Return-Path: <hardjono@mit.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 1D37AC216624 for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 13:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.094
X-Spam-Level:
X-Spam-Status: No, score=-0.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_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=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, URI_DOTEDU=1.999] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mit.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 V7DQ3OZWBYXY for <din@ietfa.amsl.com>; Mon, 21 Oct 2024 13:39:01 -0700 (PDT)
Received: from CY4PR02CU008.outbound.protection.outlook.com (mail-westcentralusazlp170110003.outbound.protection.outlook.com [IPv6:2a01:111:f403:c112::3]) (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 0EA2EC1D4A66 for <din@irtf.org>; Mon, 21 Oct 2024 13:38:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=YW5gh+BjjA2vuvgn1TyYgKWkz9alsWIkJjnngBm4dXsDT6yJ3DCaSs8w6LnsOM0dK8FWIOSgnKWWZBTDH8zvVmGdmfVjvBwr/PfzvfYJIao3SiZIbRHD7/kNdvYV1GWXBlkbn+7DCoviHGy5Jkd2laWGksDU6cgjlvkZcFQcRHiseC85xcyhZ1aV+Rs6wVKXFMBFKiigOyetPAdHRAHW/hARv/XH8GCw3Xynwel6Cc2ZRDOPYI1bidcMyk9lCQFg+iYicBT/8zuMPhTYajJ78KvxsvlL15AQOG6Dq/uPsN0NNixwZy5PUpSyafRkKBEqLAUhPWeS55Q88qy6mS0m7Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=6kUT2actt56vfH9MIVpM1Pa0Arka4r3tZ0m76QDD+iQ=; b=n4KGnRNLsYFpKg9KmxyYe43LMkot30BDynne56+70hefPkXSve2KX01SeJLJanWOSlP5Dj2xL1Z4PqnN1Y2HZsH+lcnDiKER5LBouS2099xpKrfhw+fORAwwgVVZauVyWmA7uVclplbI/Si3FqeybgRO/ISiC5Bl7YORgbAMloEQOg9MvsC1/qVo64m7dzNdm9LdPCd4DeYbYfW8tGU/q4hKtoHfc2OuLHBWyfnUh4nhLeFqiByAo1pyLFYSVzt3BPhxYRf2ze0lwXvZplJK42BtryKPdCcZ/tn51jKmCW09/Roc2dcfMcMydERMtoKdiRe8KQDgUB2GO3EUadjy9g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=mit.edu; dmarc=pass action=none header.from=mit.edu; dkim=pass header.d=mit.edu; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6kUT2actt56vfH9MIVpM1Pa0Arka4r3tZ0m76QDD+iQ=; b=UgUUVnWl/xnxmcFF2r0W6kk4dry2gaFG0zinGpnkWppj8EIy4sVuUbyCL0DkOzeF8zUgkDyJ7RPkHYFJ2iJ9ZntFXvQPrUwMRaQOsAcpfobAZszltNUk3vh4QlB71krHIGk/6wsBxGlqfOrL1DN4rA8p3v4Y1Apm1rueSGotVHo=
Received: from BYAPR01MB4391.prod.exchangelabs.com (2603:10b6:a03:99::26) by CH7PR01MB8929.prod.exchangelabs.com (2603:10b6:610:24a::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8093.16; Mon, 21 Oct 2024 20:38:53 +0000
Received: from BYAPR01MB4391.prod.exchangelabs.com ([fe80::48f1:7e3d:5503:5c76]) by BYAPR01MB4391.prod.exchangelabs.com ([fe80::48f1:7e3d:5503:5c76%3]) with mapi id 15.20.7982.033; Mon, 21 Oct 2024 20:38:53 +0000
From: Thomas Hardjono <hardjono@mit.edu>
To: William Herndon Lehr <wlehr@mit.edu>, Lixia Zhang <lixia@cs.ucla.edu>
Thread-Topic: [Din] Re: next steps for DINRG
Thread-Index: AQHbI/iS9WLfKEe2fkiCPF2F5R+sF7KRqh2y
Date: Mon, 21 Oct 2024 20:38:53 +0000
Message-ID: <BYAPR01MB4391707D30E9EA689A7F5407CB432@BYAPR01MB4391.prod.exchangelabs.com>
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>
In-Reply-To: <ac3bea84-aeac-4af2-a956-9cb23511656b@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-reactions: allow
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=mit.edu;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BYAPR01MB4391:EE_|CH7PR01MB8929:EE_
x-ms-office365-filtering-correlation-id: 09049e61-1cfe-453e-ee8b-08dcf210609b
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|376014|366016|4022899009|1800799024|10070799003|8096899003|38070700018;
x-microsoft-antispam-message-info: 4bC/b+p7/l43JnyYlmsnanAqFLoi4dDZ3pm7m9HEazrbLUXvnG+8Ul+TWpal5KKqXUpr11qijiSEt+5BdOevuF2vYkU5e76sMfZTjBaABkSD+3AzZ1jcl9ChtAtVESY5/d6dDxnqqXiEX22y8JPd21HsvFX5ybGutSx2YzmSrjFr0OlHAb8cVn5zTaRcDOdCN9v6uId8oGZH5Vzekz/ydmxGcuidvr4pFj8PevXsE1sZdSgOBB4RLoecgzJG+ozP2l5IBPZ/xIsBGJPgghy8krYt9P4JKDOI2f6HHE3FdhemM1h1WTEwD4QGYB1dwVZGYFcYL9Jz+MUICx4VV2IDH+G9kx2sAB84FdNVjzCQLMVqEdW7B9NAR2kLCCusDgOf9WWlczxwkJufI7O2NValdcrHD6QrB6stIxQa4bK+Z3sgp/mCQ/cNOlEwyLGtVpeixc3qRWWVGv+SxuOIPiPQ/ecnU7CDulPYdBjAeIPUCPbx0LhB4eYa6FPqQGFvsCBb8Sr3m6eCVm6sthg0Il0wJpyRsj/gkXSCxIlor9CQX/vYVHoZ3lRVKVkXe6BEtCJmAv0kFZJJftYmCHXwv4HSXDu/k1+4w+PeKOzumDC11KeQ6u+NuNHaMJuhcZLa+hruQe2kREZ74pcSAWPww6VKJkwRdUJ2PQIebMWRBv9F2Zmak+ejoKq6josUt8H6x2WjBhOoL17sflKZgdhW9JK5xf5p7MVjYi8IfNO2cFzIuwDtnpjo0xkqxI8W7BoU7Q63IWKKe7Xl2Vd2oIOR23jZh9Tsfd2B1k6S1fAcXS5wezUZTX36CNfiueE/9gTMDEHU8viP+qCIOXBOyHIEsQokFUeaBikmbo8JeCVCRfGYJYHPFiTaqGvDBBUZnGkDgmZZ0Po4opGudIUhMqJ5xLNFFf8iAL2EVrbDDW2lr9nc1AKLk3uF37xszi+HrVfRTKOqJx9Le3aVOvd/K9z6MCpf3LvVdyONdbChXfRajqQWnMS2m7OC1Xz/ufoKVoB5VEh9UitReDtlA+xYDBHTz7SVBieHgaXQsohIKGxUEgGdoT1cUh5jRWLRD3TdJFGuGrU4loElXeK6bjDgWuslJbjHcclBjH7cfhoV0a9YiGm9CRPGjVV6JIq2+kDUNqBs2AR4PAVaf5nRj6JSuBQbzKYpA3O9w36orUkRq1+YJv9zfazRiNBT1MWJixE/C4QiT5/MxVy+CMTBE0m2yQYNcPlYjR8ik/9XlJwsZts/4J+fXbYHbbwRHMymXJXZUo5J7R50okYDHVbneX1fz9j7jYZYFxlsqibk8s+eagdKYqr41lU59K4EwY1khbYQsAVdI4V3
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:BYAPR01MB4391.prod.exchangelabs.com;PTR:;CAT:NONE;SFS:(13230040)(376014)(366016)(4022899009)(1800799024)(10070799003)(8096899003)(38070700018);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: Vldt15HHz6Wf4q7RxtuUBFy3fCFS89+tr+X/0qgiMMv4Q/eO12NUOYDO2z5F+tqLDUQgruMztSKRjrmg+mdu3rEExpQyporzWYeyzp/hLftqSySw6WOo+yMRfs++TN3pqo5MlRxXr0calVz6Nxy7a0h6snDk+0k3lPZiqexegnIo18jfdYelYxgvHfPSMUuNNfWXt9t2ySCod9L7aqJP9Nv+2JvMXJhs9/LBaRpLvC6ZRQngvQqmeRSwIKss5V/VM9xFb6LQSPUcCB+eq/UityQfQhKHs69HdoUWyzsapxCKtr5iwYx0Hoil46ezJbSLSEbVtwTEo/7jcVM8qXtqLubFdV62AFfFDgOTdjY2F3bg0Co+pIxK0KNRsXbKu+x0EY2GfuBcpcHLKk5t0SzFw/ve7lROE0X2boynNDvs+npGT7woc4tleocsKxe1OU6Rc2zjxYzdyRlHd629dqv7Sqc0T4Jq+OyaXw250qUncnKpULmdS9AbeptzW7I9oU7VqMJ3J9gOE2I0AkJMICUAp+xbxiXx0bDPjWBZfkaD66aJzWgtbuQGyhi4gLz71REsVaCA/X0BlnNzkpfRGX/3Y1wTjZzezvbA67SpIQeh3CV9E3mtUQZF93ZetTkh9c/6CKti7e21E1Idab8q4KIF7EejfCh9PamuITPO3ulm9owS0vHlbcxv3ddIu75Fr+HTJc4DF8JPZRcbUaRbnO+L6jp0X/INzKItfaZ1BIMPc3hEwiwTVqG/2X2G2E8Qmz0EEGFQ9AHUVcpqkAWakg9KfqDWG0DqciOaGq9lGMvRjBjNUrfdrWmKt3gNILZXALDJm9E7sRRpD6NxfCmLFDatrd8ZfZ2p5ZZaW+5Wo5NJOfxEYYu1dFStGG0HqBsF1FgyeOaF4RmGbDupQJTOtNkiBd4BCBdQzBIa8bIO7ZrVmYaz7M1mdmAGefGDrerRuMed0eo+2grw/fzYPBvVRZCDKKCmT230fdovzSmgfeGslJXqLNu/OgPDd6hL6zjdJTTItea9A1rdg6CP3OBTo/VVqKvuLXxM3kawZ1ktkZUcibE/UdarRgppsR7AZVUckcvRGicOdssGm6MIkWY1amkNpGDtPHVQbsvw+YEGCmTOkHGPf3MnhY2FvycEu+lQJs32ufmPxQwMCvRkzigia4efV7aR97rfqT9Eu/pik68U1k4HgPkDXgGN6CqFQ8pGai4H9C9hxFMSmZF+Eg85CKuadXnRDOr9TEmiC8j+fndXRZbVxT3jT+0OKmZC0w4eGcaOZyYGllbD2y9szgKeZNli2Np4o7eROn7XI16v4STM0ueftkkILc4EybeWXbA/qqpnBLOFtBtF6HRJCjjDoJoHDBvS+b6Lhe++7/S5CZTcDZB1Xpl/U0NmxmXcZBu/bqtAV0M+Heg2+x9MQRmxt0ssYJQN1vi5/Z7LOnaRU80HwT38ZaZsHXyo8vvbbWL7k4lYr/AsRBDeU0q76iKOx9OFHgp2FWZUZr3hha+93k9CiwVXs6l0QzW8Lz8OsUZHDvvqCp3Fpqo6hcnR2pD6h70rNT9XwPssYS3exQaAEPrdC4Z0/wVqzXMyoFckmKNFbqbtd8fE/khvadKXlK+CGkUC3DOEcrFh4RzhTjgJ1jrwhfIWwzc6HK3VZ7OpnQ7dtmNV
Content-Type: multipart/alternative; boundary="_000_BYAPR01MB4391707D30E9EA689A7F5407CB432BYAPR01MB4391prod_"
MIME-Version: 1.0
X-OriginatorOrg: mit.edu
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR01MB4391.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 09049e61-1cfe-453e-ee8b-08dcf210609b
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2024 20:38:53.3857 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1BfdB/A+gU131a8cZd5ONz4k+b+s9p4uXXtDkA6pxcI0cYj1zNO8yw8tmb8mF2szjAW3+F2lPCmpRxHUi9PL4g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH7PR01MB8929
Message-ID-Hash: 46YI6RUO3MMDXICMAUP7U3IN7CS6F2PG
X-Message-ID-Hash: 46YI6RUO3MMDXICMAUP7U3IN7CS6F2PG
X-MailFrom: hardjono@mit.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: Chad Kohalyk <chad@kohalyk.com>, "din@irtf.org" <din@irtf.org>, Volker Stocker <vstocker@inet.tu-berlin.de>
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/4hbf72a07ITpRNftogWSPfdNygc>
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>
Thanks William, I think you provided a very good summary of the complexity of the problem. The question for DIN RG (from my perspective) is: what part of the complexity can DIN provide possible solutions for? Best --thomas From: William Lehr <wlehr@mit.edu> Date: Monday, October 21, 2024 at 4:34 PM To: Lixia Zhang <lixia@cs.ucla.edu>, Thomas Hardjono <hardjono@mit.edu> Cc: Chad Kohalyk <chad@kohalyk.com>, din@irtf.org <din@irtf.org>, Volker Stocker <vstocker@inet.tu-berlin.de> Subject: Re: [Din] Re: next steps for DINRG 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] 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