Re: [Multiformats] IETF 116 Dispatch Multiformats: Responses to Jonathan Rosenberg

Orie Steele <orie@transmute.industries> Tue, 11 April 2023 20:59 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 BEA11C1D9FD6 for <multiformats@ietfa.amsl.com>; Tue, 11 Apr 2023 13:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 N459CmJH6S-i for <multiformats@ietfa.amsl.com>; Tue, 11 Apr 2023 13:59:23 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 C6D42C1D9FC7 for <multiformats@ietf.org>; Tue, 11 Apr 2023 13:59:23 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id sg7so35117799ejc.9 for <multiformats@ietf.org>; Tue, 11 Apr 2023 13:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1681246761; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9jP0iXcOnM2iC2DNbSzUPLuP1AL+FZqj7bfkFjsLSNk=; b=iZHZ1OXQSyK4QFXk4zXp6Au6eTdDGsP26DeGCs5LY7pBWNZisM5JjEWb/ZXdVY9BGO 1yiH+uSeAhpIT+dJtibarpH08Sc33HUSe1tM/6gi0AAEx3IvXvpcshVyu+YtGFtNtZZP /pdyaw2L5u4b87yRufeYs7SgtGoIAmfq2abgt3kdcPAtqBK/Z+UBNFUJjNfkghEHVsB+ KEF+sr9sejmfg97fD/n28nuIRK5Ba+SX3Vxetw2dL/Z57XTyx4NDXGKrzw5Dhj26V1Zc 38czRcPLMlTsR1xHfM/T6XW3L2f8X9L82tobeWqm0YxNFRcQD3NiRcgzxeID468bhy4J NbEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681246761; 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=9jP0iXcOnM2iC2DNbSzUPLuP1AL+FZqj7bfkFjsLSNk=; b=fnEyFgAi8l192oudUpLX+GzfcVgHLPJEsxMU0ALOD50aDGEPz1nffi2BDmyfrhF5fu F2oqHgmGHl6uqD47BOFD2judQG9+WNHKuXGQbTNzV08pkhRg/fpGOu1UQU1wIudgCAvg jhHHzEyR0H31ROS/dojQDiQk3qHE6XR0CbMcTv4b1UeN53qukBbQaN1exA/umpqWsEzp c1D3mol5CiodLtLrqdxv97CzwXhIPY6bhapZwGDdikbhcSI2odrmlgqQ/HmS9SDTRTW6 EBvVo8ysGLyV7oxpItIYibCbXbZ/jN+L0f2wGuH2+vWM0an7+cXL1eMQU9rVsaCJmDaV xPiA==
X-Gm-Message-State: AAQBX9eQYEfVuCWbT97fhFX+iGON+dBVgJjczjXLtFyXOwe34U9oQfge 8qX+6sQIjYQLdtws1VWlBt+p/3a9xcdSTvMdX9N1YAFR8RHsg4S+I4Q=
X-Google-Smtp-Source: AKy350Zh8pALbw66rNoO3vscSU5kRCdXFZ5IxOxRUBzc47P+32KftSdU0qUuHWn7HF3cRUhUUbEMUIA+zJbhtijzX4c=
X-Received: by 2002:a17:906:1584:b0:931:fb3c:f88d with SMTP id k4-20020a170906158400b00931fb3cf88dmr6323541ejd.5.1681246761311; Tue, 11 Apr 2023 13:59:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CRybrgLB=M-Thgidv6tif=PdCfkRsQSNgm+aYFskrZa5w@mail.gmail.com>
In-Reply-To: <CAMBN2CRybrgLB=M-Thgidv6tif=PdCfkRsQSNgm+aYFskrZa5w@mail.gmail.com>
From: Orie Steele <orie@transmute.industries>
Date: Tue, 11 Apr 2023 15:59:09 -0500
Message-ID: <CAN8C-_L-ha2oTeo7MXyhKuNijaW_=bEFq5EG9AfBW=+bh-encA@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: multiformats@ietf.org, jdrosen@jdrosen.net
Content-Type: multipart/alternative; boundary="000000000000fcf61f05f915c38b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/1KDuDZ2ErsyoD_3ghnunTcjl-GM>
Subject: Re: [Multiformats] IETF 116 Dispatch Multiformats: Responses to Jonathan Rosenberg
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, 11 Apr 2023 20:59:27 -0000

They are "content identifiers", either using hashes, or by encoding the
content bytes with a prefix.

https://github.com/multiformats/multiformats

The are imo closest to a family of URNs.

And very popular in the blockchain community.

OS



On Tue, Apr 11, 2023, 3:55 PM Manu Sporny <msporny@digitalbazaar.com> wrote:

> Jonathan Rosenberg said:
> > I was surprised there was no magic cookie in front of these
> Multiformats, it collides with UU-encoded strings, is this a specific
> domain encoding or something meant for global use? Is there a reason there
> is no magic cookie in front of it?
>
> If I understand your question correctly, Multiformats are not designed
> to be a replacement for magic bytes in file headers or as a
> replacement for things like uuencoding.
>
> They are meant to be used in application-specific data structures
> expressed in syntaxes like JSON, YAML, and CBOR. In other words, there
> is always an encapsulating data model that signals that the value is a
> Multiformat. For example, in JSON
>
> {
>   "url": "https://foo.example/file.dat",
>   "digestMultibase": "zjEkl...Wkd"
> }
>
> One could imagine that the JSON object above is identifying a file by
> a URL and then associating a Multibase encoded digest value
> (presumably encoded as a Multihash value). The specification
> associated with that JSON object would state clearly what Multibase
> and Multihash combinations are expected/allowed.
>
> Therefore, I believe that the answer to your question is: "There is no
> magic cookie in front of it because Multiformats are always used where
> the fact that the value is a Multiformat value is known before the
> value is consumed. Multiformats are not a replacement for magic bytes
> in file headers or uuencoding."
>
> Did that answer your question, Jonathan?
>
> -- 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
>