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

Melvin Carvalho <melvincarvalho@gmail.com> Tue, 05 September 2023 18:35 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 90595C14CEFD for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:35:23 -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 Typ3dE0JESzU for <multiformats@ietfa.amsl.com>; Tue, 5 Sep 2023 11:35:19 -0700 (PDT)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (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 BFB4FC14EB17 for <multiformats@ietf.org>; Tue, 5 Sep 2023 11:35:19 -0700 (PDT)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-59231a1ca9eso27513167b3.1 for <multiformats@ietf.org>; Tue, 05 Sep 2023 11:35:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693938918; x=1694543718; 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=a+Xfr9tmDLicz/g9vsb8ewnKOD33TL3UWAw1eo1lN3U=; b=Ui+95q72S2hH3O2ChKlhxmu0b6ZF+wSM0O8I7YL9jcaKoOew29DZ0uKuvIRqAxZcB7 yJ/BTJJlD9TLE7PTIif1WT3MWupyh9Wx0C9bi9ZZYPZzjhA+ylos6WNBDUoxLCGbk66G zaRBlpE7y2hAOdc8zRcVLMsW+Z923Qvs4RRuOy9rGrlMZeppDCHU90xv19BW7vpjF9Rj 10hqmSnJDfwSq/p3zToRozSyxWkZjYPXZWsqXowb6FQUMCD/pl6f3E3a7gS1pPkmPAWq 1lWwOqc08OAmNGGkJOitFDI+Bhi+McEBe2ZAbu13LIYLaGwKp/mxz2x+4kux8fRQNRM3 tASA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693938918; x=1694543718; 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=a+Xfr9tmDLicz/g9vsb8ewnKOD33TL3UWAw1eo1lN3U=; b=b8+FsEZb5PEmKyA2ibKGA45hMIG6hfMvMSz/bM+Gfgwq/yFRLlU3lcLhNg/xQl2JGM Mt5R3GvSsIJR9W/83p996g6GUVLMhWGozYv6RR4aYMyI7KBTCvDZPk2eu7872htMiQaG adMCKqzO9PAteADBi9mirWGRkyATqwmipiZoKy7X/kHRZZtTyGCirNaeIspk5TFaS9HI SHoyDCppDiFLlDi0JM7c39BkxLSkDcipqowls75ptOKiJWgapwHTrBT7vXGjENCLBzt9 jqlEBVH4r+sOZc6gmgTkP28UwhxyuIg+a6GGS/NXZ7rM716kAZf35ZDos/LlUume3ehE 252A==
X-Gm-Message-State: AOJu0Ywm9rZSjszEDJI+w2sZv8IjQKr8IiYYctm6g+HKpzJgenNhWhux PAJDqoRp9Hb4zUW6M2KO5CJBS8ok7XGF5gJ7tZEZplGta10=
X-Google-Smtp-Source: AGHT+IEMs1RqDKF+U7V+x1H3TrF8GYFtMMTEh27k/g18lpEZdQwBomduC8flGnlpcIaPcKwwqDwICR+BP91ng6eNT8g=
X-Received: by 2002:a25:dc86:0:b0:d07:23bf:2824 with SMTP id y128-20020a25dc86000000b00d0723bf2824mr14251488ybe.50.1693938918637; Tue, 05 Sep 2023 11:35:18 -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>
In-Reply-To: <CAMBN2CRw6+7D85N_M32pM==vuMZf7fQ32QwYmBcvpsun1RYYxw@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Tue, 05 Sep 2023 20:35:06 +0200
Message-ID: <CAKaEYhLD5qY-xzfWOPE6QkGM18tcmS2iCguv7TRXZP9WH6mOxw@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: multiformats@ietf.org
Content-Type: multipart/alternative; boundary="00000000000084473a0604a0e3b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/QqgxaJTvC84m_z-Z0OgY8Ku3eps>
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:35:23 -0000

út 5. 9. 2023 v 20:29 odesílatel Manu Sporny <msporny@digitalbazaar.com>
napsal:

> On Tue, Sep 5, 2023 at 2:19 PM Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
> > Two possible suggestions:
> > 1. a second standardization effort around cid: or urn:cid: which
> includes multihash identifiers
>
> ^ This is probably the best path forward for you, Melvin. You probably
> need to take it through IETF Dispatch at IETF 119 (which the current
> proposals have gone through and ended up here). Ideally, you'd need a
> spec before you took it through dispatch. Based on what Bengo has
> said, and your response, it seems as if there is some controversy
> around this topic that we'd like to avoid in the first iteration of a
> Multiformats WG.
>

Could you clarify what you're referencing in regards to Bengo and the
associated controversy?

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.

>
>
> > 2. try and incoporate a way to express a CID character for character in
> the existing work.
>
> The "existing work" proposed includes Multibase (which isn't about
> CIDs) and Multihash (which isn't about CIDs). It also explicitly puts
> everything out of scope as people were concerned about us taking on
> too much in the first iteration of the charter.
>

Given the widespread deployment of CID strings, this approach may not be
optimal. It seems to divide standardization and might not be backward
compatible. However, if you feel strongly about this direction, I'm open to
considering two standardization paths.


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