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

Manu Sporny <msporny@digitalbazaar.com> Tue, 05 September 2023 18:51 UTC

Return-Path: <msporny@digitalbazaar.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 9654DC14F726 for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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=digitalbazaar.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 B59dP_1a6qrR for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:50:56 -0700 (PDT)
Received: from mail-ua1-x92e.google.com (mail-ua1-x92e.google.com [IPv6:2607:f8b0:4864:20::92e]) (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 C80AEC14CE46 for <multiformats@ietf.org>; Tue, 5 Sep 2023 11:50:56 -0700 (PDT)
Received: by mail-ua1-x92e.google.com with SMTP id a1e0cc1a2514c-7870821d9a1so84389241.1 for <multiformats@ietf.org>; Tue, 05 Sep 2023 11:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digitalbazaar.com; s=google; t=1693939855; x=1694544655; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=64yEIoEtYlGQO+4lKYzaiJ+PZ1JLeieX+QjYP3cpFW0=; b=HlcTiSHRKvBjzXBSLNA6g7N6ORl6kyPy8rBMcK6ATdvGnwTRUFhj6XJSSYkcFsB5dX NEA3BKKDpyJSA3m/gU3f0mNs+PpSCW7cNHCLgojDPN1bT3+C2DtAPsWylxRQstjQErMv nmRNGfo5jnOJfBQL1nN7QIdSFGWRDqlnmGUOZxTgvftmyod/+wkwcobyevoUQ8vEbxOp nVuEL7938I5kD4obwiJ3v0hNT2H0kQ+nuuMoF2Mr3DXiV4kwb8bCFW4kgw+OvntcsKMQ TghWBKIWc7UlTeIz0vArJ/gawQk8TLRFC3F9rD/F1hb0wN8jojyG2C0vVaKdCHrk++7c /diQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693939855; x=1694544655; h=content-transfer-encoding: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=64yEIoEtYlGQO+4lKYzaiJ+PZ1JLeieX+QjYP3cpFW0=; b=LAXWplUY/SHNuwnAVnVk/QWJ4eX8BnMUVQcA2qBCgkLh9Fjk0yzGiX1uG7ZNxzk//7 NWo5mQLvUP9n17y/UB849sNf1Y559msfTBVaWUnPk36go+nN07VEqyZi3TtETl4n+5lm VC93K8XEEbsHRvsqWsgGV+t51a310nZS8xC0JIA6AM2VPs0qMREEBVI60wJOVlbRRb5w 92VlIN3wrIxD8+F6+QwtHiXUyKfsTn2RaATAqUG2zKdOw7x7jrAELM/wKTMi4EwMbz3J bJ4aPg3kAx0Z6FMVqaadEhL4I0Cl+qTQwFkbJeo+b0tW3bKUNDmwxs8YaaH4IvY3M2RL 6NpQ==
X-Gm-Message-State: AOJu0YwuyBPtgfFoYnE3PKZQQcehwlEvkhf4qh8i9QGP0T4OAr0nfWSv JwAxb9zMlRc/CBQ27jXsPf/K9i6tC0s1TngwQAu/Wg==
X-Google-Smtp-Source: AGHT+IEQgxWXrFMjNdetSZHeOGVKjqSkSJp9sL+SMaUqi0Q5Eh2T5hdrsPL53YhLUe/x2TzgLRdUn14W0YUFu1JURbQ=
X-Received: by 2002:a05:6102:2441:b0:44d:42c4:f4bf with SMTP id g1-20020a056102244100b0044d42c4f4bfmr533202vss.10.1693939855287; Tue, 05 Sep 2023 11:50:55 -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> <CAKaEYhK7dE+5-F38384QrhTQ=ODtoDKzdYVAgkJBRZ1w3vv8Kg@mail.gmail.com> <CAMBN2CRw6+7D85N_M32pM==vuMZf7fQ32QwYmBcvpsun1RYYxw@mail.gmail.com> <CAKaEYhLD5qY-xzfWOPE6QkGM18tcmS2iCguv7TRXZP9WH6mOxw@mail.gmail.com>
In-Reply-To: <CAKaEYhLD5qY-xzfWOPE6QkGM18tcmS2iCguv7TRXZP9WH6mOxw@mail.gmail.com>
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 05 Sep 2023 14:50:19 -0400
Message-ID: <CAMBN2CTkGBFDSBdi3rUp+XggSVnqADGFV1d65qkKYZKV1sRQQw@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: multiformats@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/1gXvLnlC_U0Bhnb-gNcyVLC5ogo>
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:51:01 -0000

On Tue, Sep 5, 2023 at 2:35 PM Melvin Carvalho <melvincarvalho@gmail.com> wrote:
> Could you clarify what you're referencing in regards to Bengo and the associated controversy?

Yes, Bengo said this:

On Tue, Sep 5, 2023 at 2:15 PM ben@bengo.co <ben@bengo.co> wrote:
> Melvin, I believe both dweb: and ipfs: URI schemes are registered with IANA and use CIDs.

to which you responded with this:

On Tue, Sep 5, 2023 at 2:17 PM Melvin Carvalho <melvincarvalho@gmail.com> wrote:
> there's s degree of controversy around dweb: and I'd rather not use that

> I'm ready to utilize your work and register a provisional cid: scheme or urn:cid: scheme, based on your preference.  Should be a simple enough copy and paste.

I suggest you start with a spec that defines the "cid:" scheme (or
re-use the dweb: scheme) if what you're looking for is a URL scheme to
express content identifiers.

> Given the widespread deployment of CID strings, this approach may not be optimal. It seems to divide standardization and might not be backward compatible.

Hrm, how so?

> However, if you feel strongly about this direction, I'm open to considering two standardization paths.

Yes, CIDs are out of scope at present and I'm afraid that if we put
them in scope at this late juncture that we'll get objections.
However, a separate standardization path that defines a new CID URL
scheme, taken through dispatch, and then covered by an existing group
(or added to the charter for this group after our first iteration)
sounds like a viable path forward.

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
https://www.digitalbazaar.com/