[Multiformats] IETF 116 Dispatch Multiformats: Responses to Sean Turner and Richard Barnes

Manu Sporny <msporny@digitalbazaar.com> Mon, 10 April 2023 16:18 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 9E38BC14F721 for <multiformats@ietfa.amsl.com>; Mon, 10 Apr 2023 09:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_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=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 NQ4qJ8GnskQK for <multiformats@ietfa.amsl.com>; Mon, 10 Apr 2023 09:18:17 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 9C8EDC14F693 for <multiformats@ietf.org>; Mon, 10 Apr 2023 09:18:17 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id y193so78068iof.5 for <multiformats@ietf.org>; Mon, 10 Apr 2023 09:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digitalbazaar.com; s=google; t=1681143496; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=DR2QKmKF5C8fh9tIcpe389X7WF3zNpnZ/1ydeNlbq4A=; b=dK6u2Ygtq8lV+Mh+1ocyqboAb6dljj35vZb9ZMkHw7lk/qUexGWpgpX3EKswjaRdNl nCQaX9CX92T9GpGJYJIy0TZ+Wy9+Pwwj85QtUB6UTpjvI/u6LJ9H6v9BL5Sy4vbRmSxj 2Dn5+7/mITx1kdfYzsVegd98GUWQAxBhd830/ldCcfjDNnRhGjBvS6E3D3zVEWfewtwR 99lTkqb3FM7U+zt10hixc54cTi3Dlq7YXXyW1p6PfWKYOzNC+d8Sn8SSaR9Y03XGjcxb jK/o7EmNMs80Jsa9mvu7pJ8cdGHtM+OCkpoLBkeu8SBbrHOUnsTVFUfvuj+Xu7F86UXF SbGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681143496; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DR2QKmKF5C8fh9tIcpe389X7WF3zNpnZ/1ydeNlbq4A=; b=g/2D/CQ47mvQ0sCPPib1P55XzTGkAu77U2/bZJF6FmH7iIRqHu4QkWPxuktKTA3JQm pyO+0rjVu5h6UinwBGMkrMSXND9x3hpqqY2JN3NexPVJjU4oOe9XD8grHD6d8K4dxBSZ s0/I3ZboLjGmt2cW6NCwNYBpTYecwuGrSuRTjUCy2Nzq/ihG2OModNu4jMLjnO6+530S 1uXS2U578aUkHUlnaR2gaHnOQq/D7z+0i4/TOGq/xNJKZ8VcA2mEc8e4smvy2m96Rw11 bzvWdPlYZ7W8kiLwX9dOUUj3/a+xK1P/FYVtB+9e7OcB9W9oo5ALH4O9fmabJrlO4V+v fOXQ==
X-Gm-Message-State: AAQBX9dYcmabaKJlI8RAMIO7SVgm25YD0HK96fc1iFtamaajdCoQIadb 5DFqvljmK5u+BnneIeBnIOv8PocGkaG4h58M6cuxDDHTN4rIOSEn2/o=
X-Google-Smtp-Source: AKy350a/EDz4WrzMLdaysX3r3SnWFdrP9BvxFaDGV+Av0Mitawevm1GO+x6QZwQ24XTjFHx6JbjR4KV/8nO6XHkwT3E=
X-Received: by 2002:a5e:890f:0:b0:745:b287:c281 with SMTP id k15-20020a5e890f000000b00745b287c281mr3105ioj.2.1681143496146; Mon, 10 Apr 2023 09:18:16 -0700 (PDT)
MIME-Version: 1.0
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Mon, 10 Apr 2023 12:17:40 -0400
Message-ID: <CAMBN2CTDx4WNq7xWhF-f3nya205YeUx-VBk7aqG5rk=WMh9ONQ@mail.gmail.com>
To: multiformats@ietf.org
Cc: sean+ietf@sn3rd.com, Richard Barnes <rlb@ipv.sx>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multiformats/t4Lf8M-R73fwLUKo1oQvm_2ELek>
Subject: [Multiformats] IETF 116 Dispatch Multiformats: Responses to Sean Turner and Richard Barnes
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: Mon, 10 Apr 2023 16:18:21 -0000

Sean channel'd Richard and asked:
> Multiformats seem to be domain specific, do we need a global registry?

Multiformats use a global registry for all multiformat types today;
that's what's broadly deployed and implemented.

The primary reason for doing so, as far as I understand it, is that
using a global namespace means that you can nest Multiformats inside
one another (e.g., Multibase-encoded MultiX value) without having to
worry about inevitable conflicts between the MultiX values (e.g., you
don't have to worry about Multihash values colliding with the Multikey
values when nested inside of a Multibase value).

While some conflate this desire with the "magic header bytes" in a
file, this does not seem to be the driving purpose of Multiformats.
The driving purpose is to have byte headers for snippets of data
inside of an application-layer data format, not to be the magic bytes
header on a file.

I hope that answers your clarifying question during the IETF 116
Dispatch meeting.

-- manu

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