IETF Logo Mail Archive

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

Orie Steele <orie@transmute.industries> Sun, 20 August 2023 15:20 UTC

Return-Path: <orie@transmute.industries>
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 C35EBC14CF09 for <multiformats@ietfa.amsl.com>; Sun, 20 Aug 2023 08:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=transmute.industries
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 IO6Me1TnvNZb for <multiformats@ietfa.amsl.com>; Sun, 20 Aug 2023 08:20:41 -0700 (PDT)
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 ACBD2C14CEFF for <multiformats@ietf.org>; Sun, 20 Aug 2023 08:20:41 -0700 (PDT)
Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-99bf1f632b8so338978466b.1 for <multiformats@ietf.org>; Sun, 20 Aug 2023 08:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1692544839; x=1693149639; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rGtnh2kmsMFjxLjdtmOUKlkq//UJSedIOniY1isuvcQ=; b=dYp4mnik0NQU0dHsEoL+q8cgwpIdTmH1Mw3hE6XDQLezlL9wlI1Do+NAJ+dcBwA+A6 LuzpWkN476xrYbalp5GInPpOWF+eHo5x/AtjZPxt6KoUDG0OAYVa6lOWNza4C5HM5d8F 9UKGS9vLW5SdY0xq6SZS0Y9QnCFUm/XMAvnCe+HTXcnmN1c9bniyobGbqPodC8ynUrjr ppwO0xHBVH/AMlh5Z4gF72BrFcCDjtAY2cecp0NadhVEh+3Dm6KZnvHFijiIjDoL2I/1 u6Qq5khG2F/Px8SOsihsCj7CIIoFGeRWOkfEjqqURCmwgrQZzpe/KEGzuyYKrEl/DOWu BS7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692544839; x=1693149639; 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=rGtnh2kmsMFjxLjdtmOUKlkq//UJSedIOniY1isuvcQ=; b=JziKLMZDyXS1e0nUY2V6sB0XvFou6j17uVV4tD6PJ+Dq7dUxxssSdHcjBn5/dO3v+a YdmU9iKn2znaYK+Vi3rRfQhIpi2Stbs+MTcW63lriddvU7UM5tUdeSnNe83R3GJ1r1sF sjnJbZnU4zhG4pstgcGtrw33fwEAUoLjjxcHMnrH1Wedj5BNFxqG5BMVeManxtJS8k2t UUbZMB7sCOcdNI6+00o45gMsQ03y6GcEm8ANy7uESjxNVgdonYuGuYTGEYvuqnJel4dt 0tlIDjJk9XBMEn6982e5KZr3XGaZPcFAZMrha7ZmY+D28tpk2pUNSW9/inG6zQOxC8lt 27zQ==
X-Gm-Message-State: AOJu0YxFOIFapewMo4KfbKnONFeO0D1icyz5f1KA3vPCT04ZqrJr+2ft XMrGCYugxT9Ma4c1XLA9Dt85i5I/46urJtVXHWyyVnrDRIkSzc1b
X-Google-Smtp-Source: AGHT+IGN51NRMkg/QK7QLkhzRvdJWFVP9GLBCNeX1FfHToU49Bw9+42U33RkDdLHWcSqIF4q7Of2lwiVclRMt2bEMuE=
X-Received: by 2002:a17:906:8a67:b0:99d:dff6:40a0 with SMTP id hy7-20020a1709068a6700b0099ddff640a0mr3244712ejc.13.1692544839178; Sun, 20 Aug 2023 08:20:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CRDN9ft+youRagbFMypD8_z4tMn49DHzBNsR66ZgGxBkA@mail.gmail.com> <CAKaEYhLMAEd_4oyA-ahuCtB501weT3RCMAMCaq74SnVTQjNAWg@mail.gmail.com>
In-Reply-To: <CAKaEYhLMAEd_4oyA-ahuCtB501weT3RCMAMCaq74SnVTQjNAWg@mail.gmail.com>
From: Orie Steele <orie@transmute.industries>
Date: Sun, 20 Aug 2023 11:20:26 -0400
Message-ID: <CAN8C-_KEBvEbrkAoNUMRBjcqsWiyWjqFnvNpDsfOZFnRnqw69w@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: Manu Sporny <msporny@digitalbazaar.com>, multiformats@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e7ed1106035c4d45"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/f8BBJ82hUeRGe15_oJ7yE6My0Cw>
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: Sun, 20 Aug 2023 15:20:45 -0000

Is the expectation that draft registry entries might be reassigned in the
future?

Why is Poseidon / bls12381 included without a specification or reference?



On Sun, Aug 20, 2023, 10:57 AM Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

>
>
> ne 20. 8. 2023 v 16:46 odesílatel Manu Sporny <msporny@digitalbazaar.com>
> napsal:
>
>> Hi IETF Multiformats group (bcc: W3C Credentials CG),
>>
>> New versions of Multibase and Multihash have been published:
>>
>> https://www.ietf.org/archive/id/draft-multiformats-multibase-08.html
>> https://www.ietf.org/archive/id/draft-multiformats-multihash-07.html
>>
>> Changes in Multibase include:
>>
>> * reducing the IANA registry table to only include permanent entries
>> (previous tables included draft Multibase values).
>>
>> Changes to Multihash include:
>>
>> * adding a reference to the unsigned varint definition (referencing
>> the 1993 DWARF binary format specification! -- thanks JuanC!).
>> * reducing the IANA registry table to only include permanent entries
>> (previous tables included draft Multibase values).
>>
>
> Couple of questions:
>
> Is it back compat (ie using the same string of characters) with the widely
> used CID format?
>
> Can I turn a CID into a URI and what would that look like?
>
> mh://<cid>
>
> ni://mh/<cid>
>
> Something like this?
>
>
>>
>> These are fairly minor changes given that both of these specs have
>> been stable for a long while now. Feedback on what you think about the
>> reduction of the IANA registry table to only include permanent entries
>> would be appreciated.
>>
>> We're prepping these documents for an upcoming IETF Multiformats
>> Working Group, whose charter is currently under review by the IESG:
>>
>> https://github.com/msporny/charter-ietf-multiformats/blob/main/README.md
>>
>> If that charter is approved, we expect both of these documents to go
>> standards-track at IETF.
>>
>> -- 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
>>
> --
> Multiformats mailing list
> Multiformats@ietf.org
> https://www.ietf.org/mailman/listinfo/multiformats
>

v2.23.0 | Report a Bug | By Email