Re: [dispatch] Finding a home for Multibase and Multihash

Manu Sporny <msporny@digitalbazaar.com> Fri, 12 August 2022 12:46 UTC

Return-Path: <msporny@digitalbazaar.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B592DC14CF0E for <dispatch@ietfa.amsl.com>; Fri, 12 Aug 2022 05:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_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 e-5DcpDrBmyB for <dispatch@ietfa.amsl.com>; Fri, 12 Aug 2022 05:46:14 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 C626AC14CF0A for <dispatch@ietf.org>; Fri, 12 Aug 2022 05:46:14 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id k2so667372vsk.8 for <dispatch@ietf.org>; Fri, 12 Aug 2022 05:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digitalbazaar.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=9lNt5EMoCVQvNyS2tIhKC59SbCt3S9fo+KR5WXnjJvE=; b=gZLCtN380vSKM1L/E00A0EupP0Upzfbq/7cGLLnNkxBpDgxcyjOt+Q2GlbxqKU072f gh6peXHlKpFe3hqCSQUL5JOCsejVbkxPBWS45B5hPnjIAxZ0VK6hWF4vAXSX4nE6i5yg 8j76tvHUWlDTOEhBh8JyyzRVaPbPUCWMxIODJH6S5676UiL133BYSjkrGLrSos0H6NEo ZcyZqSmZNO38xw9ScW7SBXnlKS6XAkBQBBcDSk3CzaScDCY8UMk7q/uC45p4mSUlwfb4 CquZz1RzqY5ZWLq6ROujotZecX5ta/IdSc0t9ubKcMlGbKC3zVjZOVEAM21h33Wlr49f zmUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=9lNt5EMoCVQvNyS2tIhKC59SbCt3S9fo+KR5WXnjJvE=; b=sIa3kORSDNYL+dRVTpf+kNilF/A1OWNMrsw9TiQuo8tcrV5yCxYksUAYehRKy/KvOz uTNCHZ3l5T1/x2Xppx6FMtrYA3cxibGjH+cgNBm95f/dPZ9SOl3oUX7PdlQfVcwGArAl jZnbtAmWRNnZB0KQStIzh3QyPXz2Vutzp6HPmblqawIH6uJ/NzfxHeQRnNpMg78+CLyc KfWmoR+9KcJrwiOffMFmTpu3IuN6MRLL7oIN0TocCW/vCX/De7SA77LlTwi9LFuS0u4F aYNyx2DzAjcORGQkwWfQjCcQ6bMj9tmad+/lQX8xxJfxEBswfY3rbpMFVi+6/LdswO+J 1eiQ==
X-Gm-Message-State: ACgBeo2i0B0uTdrzGkaqTECFsNx3t+5FZEWYcgqpCCxEcOgdIaV5NODa K4ZAcgQM5IMDQsxHMfyZ+aL2r8LRGXa3emQdTckXx52+FNMBsdAd
X-Google-Smtp-Source: AA6agR6lEVXONCKdutViNCCMDH7ZCCg9Rd4Qy4vUXBLZtwn5nx02K2c1i9VNV5XVs+YgmX7K5SSV6QX1tE9JKqdt8AY=
X-Received: by 2002:a67:f60a:0:b0:388:6c5d:4579 with SMTP id k10-20020a67f60a000000b003886c5d4579mr1670787vso.19.1660308373659; Fri, 12 Aug 2022 05:46:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAMBN2CT8=V5diio=UwJO-rFiGPO1v3n7gp6_e4s7kENSBMLUmg@mail.gmail.com> <CAHbrMsBTQSyr8vdbS36YML7KLzByO=NjBiPUjbnhnea7eYB6rQ@mail.gmail.com>
In-Reply-To: <CAHbrMsBTQSyr8vdbS36YML7KLzByO=NjBiPUjbnhnea7eYB6rQ@mail.gmail.com>
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Fri, 12 Aug 2022 08:45:37 -0400
Message-ID: <CAMBN2CQ1YzG0ow14oH4tEjohS8TiM5469hNX3i7QoUd7ruigjQ@mail.gmail.com>
To: Ben Schwartz <bemasc@google.com>
Cc: Dispatch WG <dispatch@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/ztUE_9aAWDhX4aLrwHpnzhmAgnQ>
Subject: Re: [dispatch] Finding a home for Multibase and Multihash
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2022 12:46:18 -0000

On Fri, Aug 12, 2022 at 2:55 AM Ben Schwartz <bemasc@google.com> wrote:
> Do you intend to make the IETF the change controller of record for these specifications, or do you intend only to document an existing practice?

I expect IETF would be the change controller of record for the specifications.

We could just document existing practice for now if that is an easier
path. I'll note that there are at least two W3C WGs that would like to
normatively reference these specifications, and I'm uncertain if the
"document existing practice" path allows for that to happen. What are
the benefits of just documenting an existing practice for now?

> Would you open an IANA registry for managing the values in these headers, or do you view the set of values as finite and fixed?

I expect an IANA registry would need to be created as the set of
values will be expanded over time.

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
https://www.digitalbazaar.com/