Re: [icnrg] This view on web3has some interesting ties to ICN
Dirk Kutscher <ietf@dkutscher.net> Mon, 10 January 2022 20:20 UTC
Return-Path: <ietf@dkutscher.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 79D673A11ED
for <icnrg@ietfa.amsl.com>; Mon, 10 Jan 2022 12:20:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 1xZoLImOOIB7 for <icnrg@ietfa.amsl.com>;
Mon, 10 Jan 2022 12:20:04 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id BB9BC3A11EA
for <icnrg@irtf.org>; Mon, 10 Jan 2022 12:20:03 -0800 (PST)
Received: from [192.168.1.50] ([95.89.114.110]) by mrelayeu.kundenserver.de
(mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id
1MpUMc-1mYoIj33eO-00ptXR; Mon, 10 Jan 2022 21:14:21 +0100
From: Dirk Kutscher <ietf@dkutscher.net>
To: "David R. Oran" <daveoran@orandom.net>
Cc: icnrg <icnrg@irtf.org>
Date: Mon, 10 Jan 2022 21:14:16 +0100
X-Mailer: MailMate (1.14r5852)
Message-ID: <08289530-AE53-4797-923D-2E49B1F7F9D8@dkutscher.net>
In-Reply-To: <FDAFD852-1109-4A49-9840-4C76716A8ECA@orandom.net>
References: <FDAFD852-1109-4A49-9840-4C76716A8ECA@orandom.net>
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="=_MailMate_C923AEE9-2BBA-4F69-91EC-C621874C23BD_="; micalg=sha-256;
protocol="application/pkcs7-signature"
X-Provags-ID: V03:K1:CZW3AdtTDS+WvUhqLcF3RbP3upfN13o5Qs4hN0cjnVLydbxiuLa
QkjRvrVA2UmsGxrVaCn9i4OKCJbSKleUq8TjPF3sY8fmmNOwhcPGBJqXN4Vwt0kEJpGjo4s
d/swtcmhptQf/GVXAQipakDysQrIkmdBL3BIDAj5XkZ4YangbN0uxYvMMgzoI1qW8zf9L/6
4gxEvToVFJn5uod+4wcdw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:7pOtQzE5vU8=:z8fjp3uhR16QEJelhYFdpI
mLMvMtIf7MVytIZTTZLS7YHNBiBhqApra1mtt4VYZiOwhG0HL3kjqwxpx/Czd9EdS6P9aDS1j
EsK5mA5dRpzEeeGmCHTRF3zP0K2FBJ3mIst09CX4emiJ0arXtzHPUNSilzUmz1nNcHPxpKYIb
Arlz9EsPqcX5TabI4GNpksCEhZo+fo/lepZjXplS7Dh3TTKS/2OManuWEVia/bwzeRAJ4BGzW
sMXqW81pCpl/mAIcVCAr7Ez4VkGpfy08o/OwLIX1yKlcRFrGI7Wp70pieeehrNeAexnrg/MUC
F6fxxUczDsOqoNPqJ6kd3q0DwPaxCQMQ5yfteTrD7RE7tu9GreG2FR3G0UKqB2fY4aCSiucsk
lOv2aA2WuoO16vGlQkBrbQv8Jv2ZT9NVzVvVW3zieGmt614RIf24wF5KDvPNRgee+mNJC8wkA
J2tvF5KINmWkzHp7kMzGE6Z10+vRoKisVc32NNh4ZDQa+6EDnz2QC+vUd8UiFZAI/WfZ/02fm
sFJWZxz17IvQO9DCPNJCikvProSNKZsx34Idg/f/5+h5qksW5U9IgP82/oFcA7axaqBoJlRGf
sbkadDyFIQn4Ue9lavb+02lUEWcl9FK/fnOU+IRatgP8r8X1bJJZ/Ck4ZBMU11fRb8f2Nr8pw
Kp/MHj0zAVucpdZbDnPUBrZovhW2rmCnVoge8YTjFH2NFUcGiOvYTSGElKjbaEtX7CIs=
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/vDQRrffWMNK9FrBma-4i_s2gdqM>
Subject: Re: [icnrg] This view on web3has some interesting ties to ICN
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list
<icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>,
<mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>,
<mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 20:20:13 -0000
> …at least in my opinion. It’s not clear if you follow this person’s reasoning whether some of the similar arguments about NDN/CCNx’s allegedly better distributed protocol design matters in practice. Thanks for sharing and for re-kindling this discussion. I had seen the article, too. My view on this: * the hilarious difference between "crypto" claims and reality it well observed, in my experience. I could imagine though that most of the contradictions (actual centralized mode of operation) will probably be ascribed to initial deployment factors by web3 proponents. * in any case, both the scientific quality (peer-review, let alone meritocratic processes as we have in the IETF) as well as the level of operational considerations (that would be required for Internet-scale operation, and that is typically very important in Internet protocol/system design) leaves room for improvement. On the analogy with ICN on distributed protocol design and decentralization: * While some web3 proposal make broader claims, it is IMO obvious that these systems generally try to establish an alternative platform for content (i.e., file) access – but **not** for an Internet-level infrastructure. Even for web services, these systems fall short of expectations, because the web today has so many more applications, services and protocols – take WebRTC for example. Totally unclear, how systems such as IPFS would cater to that. Obviously, ICN operates on a different level. * The discussion and my analysis on centralization so far has many people, including me, to think that the main driver is really economic concentration and correlated phenomenons such as exploiting personal information on centralized platforms, i.e., it could be seen as a failure to apply antitrust and similar actions. There is probably little hope that ICN would be able to induce any measurable difference in the same socio-economic environment. Still, IMO it's worthwhile zooming a bit into the technologies for a more nuanced comparison: Most web3 proposals that I have seen assumed some kind of overlay, P2P-inspired system, using DHTs for name resolution etc. – plus a good portion of cryptocurrency fluff of course. These systems are not amenable to decentralized operation in a strict sense, because you need access to some form of logically centralized resolution system etc. ICN has two main tenants that are relevant to mention here: access to named data as first-order principle (i.e., really not requiring resolution conceptually at all) and the built-in security framework, enabling building local trust relationships for communication without dependencies on external trust anchors (in the blockchain or web PKI). Unlike most web3 systems, you can really build autonomous application in local networks, i.e., operate in a decentralized way. Moreover you can build systems accessing named data without location notion at all, not only for files or web objects, but for any kind of data and service. Some of complexities in todays networks stem from issues such as: * complexities in setting up and managing secure communication endpoints, servers etc. * limitations in TCP/IP or QUIC/UDP with respect to steering traffic to copies or alternative loci of data/computation The latter is a real issue in CDN, edge computing today, and ICN has a potential opportunity here in making content replication, local provisioning, location-independent access to computation results less complex without compromising on security. Now, this alone will not change value chains, business models and general capital concentration – this would take political actions etc. However, legislation and regulation also need a solution space to navigate, e.g., when demanding anti-monopolistic measures such as user data and service portability, there needs to be technical alternative in the first place. All of this a very much theoretic deliberation of course, unless more systems get built to demonstrate some of this. Looking forward to your comments. Dirk
- [icnrg] This view on web3has some interesting tie… David R. Oran
- Re: [icnrg] This view on web3has some interesting… Dirk Kutscher
- Re: [icnrg] This view on web3has some interesting… David R. Oran
- Re: [icnrg] This view on web3has some interesting… Joerg Ott
- Re: [icnrg] This view on web3has some interesting… Dirk Kutscher