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

Melvin Carvalho <melvincarvalho@gmail.com> Tue, 05 September 2023 18:19 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 D6E19C151073 for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 ZI2890JYbKCB for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:19:49 -0700 (PDT)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 C3066C14CE42 for <multiformats@ietf.org>; Tue, 5 Sep 2023 11:19:49 -0700 (PDT)
Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-d7e387c33f3so2214559276.1 for <multiformats@ietf.org>; Tue, 05 Sep 2023 11:19:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693937989; x=1694542789; 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=1MkxKFqAXRPWQXW8pzhMzgZ460HRvFoW4n1gABBD3ZI=; b=opOBCkfYOSpcqOH85gEUuK/IeP9eDgPa8/sUQz8/c2iIBaWPwUy+sUZ8TM9PVoloSj 0TLY1clm5PL6H4IhuvRVwpyu6HMW7+Og/tBaXf3sloC43SM/HwKchcRUaNbdqN/r5EGJ 97impj99wShAaQw4GWhktWK0tUB90K3LqVJLWbfQD1mg/Wufl8qVG4WAaKr0+FfIBed3 B6899BPXvQVCgrLgB6CKFPPBiuu0aHG92rUzb6i73FL7GvxUTH3HUx3Sv7TpxtSVBrgv dKxBay8cBeWvL3vLIoZde9+/XRBY6mhqu0xoVQYcfgBkTUlzc6aFFvnAUBuZ81Kpu6Sz sDGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693937989; x=1694542789; 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=1MkxKFqAXRPWQXW8pzhMzgZ460HRvFoW4n1gABBD3ZI=; b=TN9HFYCZv8ctNwdQ1j+ZrYFJcI5coMZQU/0O+acBPYCkSN9RTQRunjiiUhc85Y3nsK bgJlfFbrFR4DGbs5D2D9JxOlMxtR10MWiW689OIsoIWqzrmXnB++YpMn0N1fpxskVeUF xSPcZgfnRXf4FnBy/1ck22c5FP3pv0zGddltp8zev9xFsCnIKMV5Tx446B43RL2WtxR4 o+2v8eB5hn08fRABnWcfTQ5/Xgasw6eZHnuBgpabOPgB30QjHk+IJ20Yke+Wonbxu1X6 jBt1dGy8ntp48ZsljyWxQmy5LhxFz1oWwAvcjlxa+XZyqyO80hg7BGOjCflS2wq1puxP qKjw==
X-Gm-Message-State: AOJu0Yy3B0jccMDSFjqwWg8fucmrIDt3pQUjQkbOnpGcEfZ0zu7abX0M fc2C5ZBX0kPJA5GMDtW4s1EloaAdLGPR/sZyqKs=
X-Google-Smtp-Source: AGHT+IE327WEhD8ufk620CYfWnQm6rfMTa+jfiUu4S0pfxX2q3TTr0xVFFfup19j3AZNnA+cfNMRsMF78D/RE+F+W1o=
X-Received: by 2002:a05:6902:50a:b0:d7e:c920:9818 with SMTP id x10-20020a056902050a00b00d7ec9209818mr8993474ybs.8.1693937988731; Tue, 05 Sep 2023 11:19:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CRDN9ft+youRagbFMypD8_z4tMn49DHzBNsR66ZgGxBkA@mail.gmail.com> <CAKaEYhLMAEd_4oyA-ahuCtB501weT3RCMAMCaq74SnVTQjNAWg@mail.gmail.com> <CAMBN2CS__7r73EdsSC4Yjfho+HQKkcGextOxsyT4M60Bioq83A@mail.gmail.com> <CAKaEYhL6VV10G35AjRLASMoqvQOQY=QwNAB_6auXhpEfMPha-g@mail.gmail.com>
In-Reply-To: <CAKaEYhL6VV10G35AjRLASMoqvQOQY=QwNAB_6auXhpEfMPha-g@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Tue, 05 Sep 2023 20:19:36 +0200
Message-ID: <CAKaEYhK7dE+5-F38384QrhTQ=ODtoDKzdYVAgkJBRZ1w3vv8Kg@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: multiformats@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001709d90604a0acfb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/3BCaGvyuffX8NsGjWsM2eT1f9r8>
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:19:53 -0000

út 5. 9. 2023 v 20:12 odesílatel Melvin Carvalho <melvincarvalho@gmail.com>
napsal:

>
>
> 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.
>

Two possible ways forward:

Two possible suggestions:

1. a second standardization effort around cid: or urn:cid: which includes
multihash identifiers

2. try and incoporate a way to express a CID character for character in the
existing work.

There is a need to capture CIDs and identifiers, without changing the
encoding.


>
>
>>
>>
>> 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/
>> Founder/CEO - Digital Bazaar, Inc.
>> https://www.digitalbazaar.com/
>>
>