IETF Logo Mail Archive

Re: [Multiformats] New versions of Multibase and Multihash published

"ben@bengo.co" <ben@bengo.co> Tue, 05 September 2023 18:16 UTC

Return-Path: <ben@bengo.co>
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 EE890C15198D for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.011
X-Spam-Level:
X-Spam-Status: No, score=-1.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bengo-co.20230601.gappssmtp.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 WlPlE4Sb0E0O for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:16:15 -0700 (PDT)
Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (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 557ACC151996 for <multiformats@ietf.org>; Tue, 5 Sep 2023 11:15:53 -0700 (PDT)
Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-5734b893a11so1851244eaf.1 for <multiformats@ietf.org>; Tue, 05 Sep 2023 11:15:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bengo-co.20230601.gappssmtp.com; s=20230601; t=1693937752; x=1694542552; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=yw8onv5SlYEaa/GhR5x35FgtFppHXbB/4wweQenSk0c=; b=X2v7JyktF7wjXdpIPSYva+/N7IQDRtoKCnLfHnzs8wPszCjLLJ81vI7w0osMPOwA0z O2Q/I6ZlizaHB8a6mOFjQxcMK50a1yLrp6F3t77ENi0+rp0fo/h1tvwJmN/eXOhBP/Yj 8YLDCcY3kCNpMo0nsnL3V0Z1EGxC0noq99Y8gsQNhu9vlcf95aZ4OJ7KMRcxpFqzJ9lM 57HTO04U0RjyrHbYEVsgNlRT9grsLw+py8F/r1uPxPWeQCab+6QpSvQu+lF7UQQy/ws8 Jq/oCAUGnypvG+8u6J3PXeSi0WdFeSwkCkafFfe3gXA0Rcpt+JpHsr6FXpNxPjdMbq0J YD9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693937752; x=1694542552; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=yw8onv5SlYEaa/GhR5x35FgtFppHXbB/4wweQenSk0c=; b=dL22SnAHJgOeQ24A6WkWCvXNqo3YEPQ6kY0c0jb61AXYFx8DdNXCkcTHIUMMVc0OnH 3K520eRnweUw9bT0dus4EWWvUwG+/ry0wIgt42+M8rKDswl6uniqldkhPf4QnsBzoNe0 Z0tbDeT8J3tFu2NKi0AK73FLgt2wRCDjvJ6CRegkCfJiD7ZZnNdWx47MveY/sBhYvUDX c1EFOJ+VeEwz3X0arqpx0/6mne349F/55tu25eEBvSY6+cOfK/BHE8HeVp7mwp4P2gEC soVqINh4UeKK/cy2J1Xw36TPuZqKHm+n/4u8Ir7GVIBrVwE1Hp8e+pzyJ/FkT+Wboi/g ijHQ==
X-Gm-Message-State: AOJu0Yw3P59/mqysOVHbgleD6RDVhR1zvLfMnq5glNw3wd4sFzH/2DPi cHUz5WdDR328v5qOT0oLcJNgzw==
X-Google-Smtp-Source: AGHT+IHeRS2kcloDfbYSyDGv/ArZ7FBEhB8TE13661hOyx2aaKZwRD7Bz2oPAxR76hQlt0FyGf9AAA==
X-Received: by 2002:a05:6820:284:b0:573:bc17:4b60 with SMTP id q4-20020a056820028400b00573bc174b60mr12510727ood.4.1693937752224; Tue, 05 Sep 2023 11:15:52 -0700 (PDT)
Received: from smtpclient.apple ([2605:a601:ac5f:2d00:1d91:6772:9f9e:337e]) by smtp.gmail.com with ESMTPSA id 3-20020a4a0d03000000b005736f96876esm6163285oob.41.2023.09.05.11.15.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Sep 2023 11:15:51 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-8335657B-64B2-48AA-BABB-F7FEB008211F"
Content-Transfer-Encoding: 7bit
From: "ben@bengo.co" <ben@bengo.co>
Mime-Version: 1.0 (1.0)
Date: Tue, 05 Sep 2023 13:15:40 -0500
Message-Id: <E5933802-C5EA-4C60-987F-50491656E6F2@bengo.co>
References: <CAKaEYhL6VV10G35AjRLASMoqvQOQY=QwNAB_6auXhpEfMPha-g@mail.gmail.com>
Cc: Manu Sporny <msporny@digitalbazaar.com>, multiformats@ietf.org
In-Reply-To: <CAKaEYhL6VV10G35AjRLASMoqvQOQY=QwNAB_6auXhpEfMPha-g@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
X-Mailer: iPhone Mail (20D67)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/HBoz_BrAwJzfzeOeuiCsCei2DPM>
Subject: Re: [Multiformats] New versions of Multibase and Multihash published
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: Tue, 05 Sep 2023 18:16:19 -0000

Melvin, I believe both dweb: and ipfs: URI schemes are registered with IANA and use CIDs.

(sent while mobile)

On Sep 5, 2023, at 1:13 PM, Melvin Carvalho <melvincarvalho@gmail.com> wrote:




ne 20. 8. 2023 v 17:24 odesílatel Manu Sporny <msporny@digitalbazaar.com> napsal:
On Sun, Aug 20, 2023 at 10:57 AM Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> Is it back compat (ie using the same string of characters) with the widely used CID format?

The short answer is "yes, almost certainly".

If by "widely used CID format", you mean the Multicodec headers 0x01,
0x02 and 0x03, then yes, nothing in these specifications prevent the
usage of those headers in a Multibase-encoded value and the Multihash
value headers don't conflict with the CID value headers.

However...

> Can I turn a CID into a URI and what would that look like?
>
> mh://<cid>
>
> ni://mh/<cid>
>
> Something like this?

No, because CIDs are not file hashes, so you can't just use Multihash for them:

I believe using a CID as an identifier is crucial, given its wide deployment and the need for character-to-character comparison. I had anticipated that this group would address this. How can we incorporate a CID into a URI? Does the spec not cover this, necessitating a new URI scheme? Implementing another scheme might seem redundant, but if needed, we can explore it. There seems great utility in reusing the widely deployed CID format can be seamlessly integrated into a URI while maintaining its character integrity.
 

https://docs.ipfs.tech/concepts/content-addressing/#cids-are-not-file-hashes" rel="noreferrer nofollow" target="_blank">https://docs.ipfs.tech/concepts/content-addressing/#cids-are-not-file-hashes

IOW, nothing we're doing here precludes encoding a CID in a Multibase
value... but CIDs (all versions of them) contain more information than
just the content hash itself (which is all Multihash encodes). We are
not standardizing CIDs at this point in time, but we're not precluding
their usage or future standardization, either.

-- manu

--
Manu Sporny - https://www.linkedin.com/in/manusporny/" rel="noreferrer nofollow" target="_blank">https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
https://www.digitalbazaar.com/" rel="noreferrer nofollow" target="_blank">https://www.digitalbazaar.com/
--
Multiformats mailing list
Multiformats@ietf.org
https://www.ietf.org/mailman/listinfo/multiformats

v2.23.0 | Report a Bug | By Email