Re: [Multiformats] Multiformats Considered Harmful

Melvin Carvalho <melvincarvalho@gmail.com> Thu, 07 September 2023 21:22 UTC

Return-Path: <melvincarvalho@gmail.com>
X-Original-To: multiformats@ietfa.amsl.com
Delivered-To: multiformats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFEEC15154A for <multiformats@ietfa.amsl.com>; Thu, 7 Sep 2023 14:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.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 G-FF4XzWm-rC for <multiformats@ietfa.amsl.com>; Thu, 7 Sep 2023 14:22:49 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4C65C151989 for <multiformats@ietf.org>; Thu, 7 Sep 2023 14:22:40 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-d7225259f52so1319629276.0 for <multiformats@ietf.org>; Thu, 07 Sep 2023 14:22:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694121759; x=1694726559; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=r3BXZvh+3HLSdItzrSRHiTCtuyA6hUGoRIDahjJRkNg=; b=qEGWwAHNzcVQ+nI2okHKK3l8PcVWvaAY4z6hzquIH9OXclvCTLKjWC7b4oNxcDom7f y9BIs1r/ypC0Eea87F9wK81GxnxWEYW4BmBt+mLn9Ei7i+9dG9pqtl4SABmvNArHn2dz jEFVIYMy1Y8q2cyn7K0lXvRtE90KfhLYSYyDLQzyC0tm+QL+PIMvkFBWk0hJnihtUtKg TW/YosINQzkafLtZSsqXtGcywaQaPhGmxnHFxILH14ty7RJqw8qkKoocZFcn7ZWLRe2N 71TO7pkVSnhvmVZCl/8wsrAkU3G64i7/HOMToXk9f/Q0Wvr1/G8ZRG1OtnejUvvp0tBn WqaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694121759; x=1694726559; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=r3BXZvh+3HLSdItzrSRHiTCtuyA6hUGoRIDahjJRkNg=; b=R+q6cH91JdX2X3kk9vU6ylZNaSWAl6dIIybtuznM+XrDZ6wNv9ak6OJcArpGk+1FKd jtrJmTB4eY/hLQL0eb8AS1pfYwEmK4L0bMPQeRXvS7vzGzac5/tYmC9p+O2Zh7Fef7YM t+GvJPxhXlF+ARKEpD4R24Yk5Bjtt+6iZumYlfY6S24sumnIo2et1dK5NHdOrZGiOklX 2KjO/kdS8mYsRNoE6P6MKfWmwSgbYgOEcoIKJOYvMv1LU4l7Hr4dbv3FA9cIQI0PeoUM NMaH1XgOG7BLSvZCeXS8QlItV6lk0QYAnPS+fNa5J5hqKWZjZcTPAAZJaSbRyizEoV63 s45Q==
X-Gm-Message-State: AOJu0YxyXtZ9swVLx9Mg2bMPwiOGOQ6IPUsM/J6oPqoolb/Oe7/AF53d PPbFNFThloD7VATGsuY+XW2WZI8mT7tpQRGmJGA=
X-Google-Smtp-Source: AGHT+IEShJxe6PnNoR8ufD8skHTgmT4jtXudZCdPspKtIhyDbJEdEEFFKKGNiXMtsjr2EAzCDStm82ej7bZhLJzekJk=
X-Received: by 2002:a25:3716:0:b0:d78:40da:3b25 with SMTP id e22-20020a253716000000b00d7840da3b25mr521168yba.47.1694121759548; Thu, 07 Sep 2023 14:22:39 -0700 (PDT)
MIME-Version: 1.0
References: <F814189D-031F-4CED-AC9A-F6049D010632@tzi.org> <81D17EDC-723D-4977-AA82-6164DDB5B431@tzi.org> <CAN8C-_LpYSimtHTn0nE7HN13iJ8FyxchaDm4G1mTX97MhYf=bw@mail.gmail.com> <MW4PR02MB7428BE7784A204FC9F945685B7EFA@MW4PR02MB7428.namprd02.prod.outlook.com> <CAL02cgSyS9AuVde_HYyP2Dghq6ZnVpVnis6egR8CTf24b4h37w@mail.gmail.com> <76fbb098-96eb-f93f-bb90-5a95791ef000@berjon.com>
In-Reply-To: <76fbb098-96eb-f93f-bb90-5a95791ef000@berjon.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Thu, 07 Sep 2023 23:22:27 +0200
Message-ID: <CAKaEYhK+4OaBZVEUfiC5f-pTT7SLpQ9rFU4T2tMMhN708MaC_Q@mail.gmail.com>
To: Robin Berjon <robin@berjon.com>
Cc: Richard Barnes <rlb@ipv.sx>, Michael Jones <michael_b_jones@hotmail.com>, Orie Steele <orie@transmute.industries>, Carsten Bormann <cabo@tzi.org>, "multiformats@ietf.org" <multiformats@ietf.org>, Murray Kucherawy <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>, Francesca Palombini <francesca.palombini@ericsson.com>, Roman Danyliw <rdd@cert.org>, Paul Wouters <paul.wouters@aiven.io>, Russ Housley <housley@vigilsec.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Content-Type: multipart/alternative; boundary="000000000000af2bf50604cb75e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/eddEnw8QxjNbi-Kyh7VkRD4k_A4>
Subject: Re: [Multiformats] Multiformats Considered Harmful
X-BeenThere: multiformats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion related to the various Multiformats data formats <multiformats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multiformats>, <mailto:multiformats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multiformats/>
List-Post: <mailto:multiformats@ietf.org>
List-Help: <mailto:multiformats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multiformats>, <mailto:multiformats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2023 21:22:53 -0000

čt 7. 9. 2023 v 23:05 odesílatel Robin Berjon <robin@berjon.com> napsal:

> Hey all,
>
> just jumping in briefly on behalf of factual and historical accuracy.
>
> On 06/09/2023 16:06, Richard Barnes wrote:
> > As I understand it, the reason multiformats exist is basically that the
> > blockchain community failed to organize itself well enough to agree on
> > an encoding, so there was a need to shove multiple encodings into a slot
> > and let the recipient figure it out.  While this seems to be a common
> > pattern in some W3C spaces (e.g., VC, DID), it is a compatibility
> > nightmare, and is not something we should build standards around.  Much
> > like DID, multiformats is a fine hack to multiplex multiple things into
> > a single slot, but one that should at best be documented for historical
> > purposes while we build forward to a common thing, not held out as in
> > any sense a good thing to do.
>
> I'm not sure where the idea that multiformats are a blockchain thing
> came from. Multiformats are a core component of the IPFS and libp2p
> protocol families, neither of which are in any way blockchains.
>
> It may be possible that the IETF isn't the right place to standardise
> widely deployed Internet protocols with multiple interoperable
> implementations or (as is the current topic) their component parts; I
> will defer to the the community on that. However, given how core
> multiformats are to some essential parts of these protocols (e.g.,
> CIDs), one way or another they need more than documentation for
> historical purposes.
>


It's worth noting that IPFS often finds itself linked with Filecoin, given
both were developed by Protocol Labs. As mentioned in the IPFS
documentation, there's an intended seamless compatibility between IPFS and
Filecoin. Furthermore, a recent Filecoin GitHub issue described Filecoin as
the incentive layer for IPFS data retention. Is this a fair understanding?

I concur on the importance of proper documentation. Perhaps the Filecoin
Foundation or CASA could be considered as potential custodians for such
documentation?



> --
> Robin Berjon (he/him)
> Governance & Standards at Protocol Labs
> https://berjon.com/ - https://mastodon.social/@robin
>
> --
> Multiformats mailing list
> Multiformats@ietf.org
> https://www.ietf.org/mailman/listinfo/multiformats
>