IETF Logo Mail Archive

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

Melvin Carvalho <melvincarvalho@gmail.com> Tue, 05 September 2023 18:17 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 E7F9AC15198C for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:17:07 -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_DNSWL_NONE=-0.0001, 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 UuT9JlryOcTm for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:17:04 -0700 (PDT)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 2C94BC151073 for <multiformats@ietf.org>; Tue, 5 Sep 2023 11:17:04 -0700 (PDT)
Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-d7ecdb99b7aso2397004276.3 for <multiformats@ietf.org>; Tue, 05 Sep 2023 11:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693937823; x=1694542623; 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=OLmEQQQGg2+NO/hvXe9hxCQTSgOVU9qNPckZGqBD2Yw=; b=p6X+m110Sg5nIFFlD4cS9N3HqQFcJDz65LlHKDBqlArYy8DmIk0fMDjTFG1vwxwwOw FCOPiYKHHxaOToaWTq22l+40g8ef3dY/cQ668HOxRMJfjqRFqfdEDFLCo66ZnqKSEpc0 rEgpjWmrFWMV22fkE15kjehtAJQ2fmfqfMqXwY3nURssko9CuqkFYnJ/N5HDfRpp/7JT b/DJlLunYxV1MOKATyrQ46hHtfjwrNP+bmB2RNNSCWJv1D23KFQXpTs4iOkYAa9gKrgd 3fiu1L5m4mnElBH4uwMOahPThA2xDwCJiUrYNgihXarklrXfKMJzycSFQT3S1697WwEW vLgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693937823; x=1694542623; 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=OLmEQQQGg2+NO/hvXe9hxCQTSgOVU9qNPckZGqBD2Yw=; b=KeQa1lRC1S/4RVwLOdCRLT8SOERDpLf/szoPQr8M9F7PwXyKBzkmg/rA5rhRTZ00nw n4D/iXa/mevlrHxRbPKOFaoGquHSswEIWmJkSZErajbld8vX0WS2kqQfSEs00nOe4rS8 WE8sfXKojOVOsWaOo8gC6u6QOh8W9P0Kxh6qyUpD6dnDu5DbvW+pWdcN0a1xTHI5TK5c gMFeEoUFNHVfe/HGRCl5eCoY0RiWmSFUUEg95AePP7/0a8fgFAoOgplTzBN9sVaWyunt mY73DrcZ167GiBeidAax8hCEnAsdZS+JbLLdIXjwH+fqDho/8y22Epvb+w7HFFdUYDyo tfvQ==
X-Gm-Message-State: AOJu0YysY8VSWqfcfDKdQsOZDqE0qctG/qf3CBfiOqMUb94yWzGouPc+ FyiffVUGsnzakkJcl029QWn21MGRGaUkuO4hyBI=
X-Google-Smtp-Source: AGHT+IG10BxzR9xTfNmKvAOeDQ7MXthAbCNRStxOd2/5KaAW5uCLtQZHA0b9K2EfRoCJzua84JN+utcehfkY0sls9kU=
X-Received: by 2002:a25:d88e:0:b0:d11:1f4a:67e3 with SMTP id p136-20020a25d88e000000b00d111f4a67e3mr13286041ybg.2.1693937822930; Tue, 05 Sep 2023 11:17:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAKaEYhL6VV10G35AjRLASMoqvQOQY=QwNAB_6auXhpEfMPha-g@mail.gmail.com> <E5933802-C5EA-4C60-987F-50491656E6F2@bengo.co>
In-Reply-To: <E5933802-C5EA-4C60-987F-50491656E6F2@bengo.co>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Tue, 05 Sep 2023 20:16:51 +0200
Message-ID: <CAKaEYhLUtOCNPVZZ=-p6Pj=A+x6Js01pU9qXFM3y+CnVNaCbhg@mail.gmail.com>
To: "ben@bengo.co" <ben@bengo.co>
Cc: Manu Sporny <msporny@digitalbazaar.com>, multiformats@ietf.org
Content-Type: multipart/alternative; boundary="000000000000351d820604a0a282"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/XFvywUJjI51-8db39PGFOlGd4uU>
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:17:08 -0000

út 5. 9. 2023 v 20:15 odesílatel ben@bengo.co <ben@bengo.co> napsal:

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

ipfs is tied to transport, this is about the identifier not the transport

there's s degree of controversy around dweb: and I'd rather not use that


>
> (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
>>
>> 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/
>>
> --
> Multiformats mailing list
> Multiformats@ietf.org
> https://www.ietf.org/mailman/listinfo/multiformats
>
>

v2.23.0 | Report a Bug | By Email