IETF Logo Mail Archive

Re: [Multiformats] Welcome to Multiformats; the near-term plan

Orie Steele <orie@transmute.industries> Wed, 03 May 2023 14:45 UTC

Return-Path: <orie@transmute.industries>
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 58B15C151984 for <multiformats@ietfa.amsl.com>; Wed, 3 May 2023 07:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.681
X-Spam-Level:
X-Spam-Status: No, score=-0.681 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_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=transmute.industries
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 I7IlwMJuzkJi for <multiformats@ietfa.amsl.com>; Wed, 3 May 2023 07:44:57 -0700 (PDT)
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 4CF34C151B0D for <multiformats@ietf.org>; Wed, 3 May 2023 07:44:57 -0700 (PDT)
Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-95316faa3a8so1047076266b.2 for <multiformats@ietf.org>; Wed, 03 May 2023 07:44:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1683125095; x=1685717095; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZrhxMTf4kldKXGw200hcEtTQCqbJW7dLNI8PB2UX1FA=; b=AGqMXNBCRmiu0bqJsqOQw4ApgQy98DvZ6fHYNVc84RsfK/VrvG/+QYdMdYN+O7dDx7 uTEGkNDzbUyFgjWTsJgYdXcMSUKY4qKZSvos9Q2Z46KAODrWVzE1DTLHFsaN3iELgrHw fiZQ8JcpN/hY6mitvqGVrmw/m39rtQGqBm5uTTUwziv2MaUjlewkCkljm/8jmmvIhr0Q U6F88RfFlY2Rf4EtRIbKObkt1UlMwUnQhGzty7K6gcc72z5FDpG9pJ+lNvNEez8hpRFy 3+JnT/0/vfTiNg/OnVHBqYwngMX6la/c+5HCrkClFxNnaOhJCniymiTnwvKKfWru12hC /R2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683125095; x=1685717095; 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=ZrhxMTf4kldKXGw200hcEtTQCqbJW7dLNI8PB2UX1FA=; b=ZMWr0esLhoCUy5He0WHMH+THLLc2FzGvtznYrVBeHJJp1ZPne4c9srVE6IsT01TDph kXXFn8RNSZ3I8ABTna5wp2aBVfDHLebWmlbP/r9wegqUtfyPYWvSlxBQYzGhrxvzF8CJ XPEPEV2hN+a6gDdpIsWcilwiXvjKNEjka9NO33ucU+2de1WZdP5nixz9MbgS9tAiTVJF Wl0GLZNJjJVbPCvZImvf2ud1QmZ+8539tkXZT/zKbPcOLA9df2wy6yGNoAzvOxeP0z3A 0n49wMWJPVpll84qcm5Oc0dmvutpVytyR6WdqVn36yD6dKigIsrV4bWo4CwTjE++JCuy QafQ==
X-Gm-Message-State: AC+VfDxS4FDrf+IHFPk2YCBkm3ofDsJeavilTP+PmR2Oz5O7te1Q6khU Ssxvdl1cY2uPAEBhAukhzR7F1K7K1dPaobfUVU8DBQ==
X-Google-Smtp-Source: ACHHUZ4d9lEXjOwUyON0R6muDmGvfOzQx0dZFDcugeeBOUGwYJjfBr2/RSy1T1O55TXttYDX9iMzIXUdSmpzcMV2Xtg=
X-Received: by 2002:a17:907:a0d:b0:94f:2c22:a7a2 with SMTP id bb13-20020a1709070a0d00b0094f2c22a7a2mr2984562ejc.68.1683125095223; Wed, 03 May 2023 07:44:55 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CSFmQKKaPvdS8y+0ReQQVKubrYwYvHSyVivOJ7VApzeng@mail.gmail.com> <CAKaEYhL=aZ6_EHL3KASF3wpJXKXQ7TGvTD3rd-JGD=r2yCfCbA@mail.gmail.com> <862cb63a-d31c-8d03-2f50-115bdac0dcbf@berjon.com>
In-Reply-To: <862cb63a-d31c-8d03-2f50-115bdac0dcbf@berjon.com>
From: Orie Steele <orie@transmute.industries>
Date: Wed, 03 May 2023 09:44:44 -0500
Message-ID: <CAN8C-_K1=Km-k+Y6T6-OJ7fuWQ02mWDHctmyO43-Rjd6U_-3Jw@mail.gmail.com>
To: Robin Berjon <robin@berjon.com>
Cc: Melvin Carvalho <melvincarvalho@gmail.com>, Manu Sporny <msporny@digitalbazaar.com>, multiformats@ietf.org
Content-Type: multipart/alternative; boundary="00000000000069e3eb05facb193e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/OvP4cPu-Aq1_sxfNcl6MNZ4fPsE>
Subject: Re: [Multiformats] Welcome to Multiformats; the near-term plan
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: Wed, 03 May 2023 14:45:01 -0000

I agree, they should be separate documents.

multibase is about string encoding of binary data.

multicodec / multihash is about prefixing binary data with type information.

OS

On Wed, May 3, 2023 at 9:42 AM Robin Berjon <robin@berjon.com> wrote:

> On 10/04/2023 18:17, Melvin Carvalho wrote:
> > Interested in multihash, but not multiformats which is a much bigger
> > project.  I hope that the two do not get closely coupled in a single
> spec.
>
> I don't see any reason to couple everything into a single spec. These
> need to work well together but that doesn't require significant
> coordination to achieve.
>
> --
> 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
>


-- 
*ORIE STEELE*
Chief Technical Officer
www.transmute.industries

<https://www.transmute.industries>

v2.23.0 | Report a Bug | By Email