[dispatch] Demonstration of W3C Implementer Support for Multibase at IETF (was: Re: Finding a home for Multibase and Multihash)

Manu Sporny <msporny@digitalbazaar.com> Sun, 26 March 2023 18:34 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 390DAC1524D3 for <dispatch@ietfa.amsl.com>; Sun, 26 Mar 2023 11:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=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 VSieLEZhJvxQ for <dispatch@ietfa.amsl.com>; Sun, 26 Mar 2023 11:34:32 -0700 (PDT)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 DE45AC1524BC for <dispatch@ietf.org>; Sun, 26 Mar 2023 11:34:32 -0700 (PDT)
Received: by mail-il1-x134.google.com with SMTP id j6so3549073ilr.7 for <dispatch@ietf.org>; Sun, 26 Mar 2023 11:34:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digitalbazaar.com; s=google; t=1679855671; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5px0jYvLNrM8BO3g95exCwm4+Eb0NK+7bZu9uFmPVbY=; b=sGlLV8KvGi6hIpkNCY2brT7VE1PPzYXlSv1hUDi3IoZWR9f+d01B7ag/zy/VKcHCO6 6OfNF4OGyRCJBZ56LvdkQsmxD2jKXvFMwTa38cBbFLrpTXqS5ZgJt+PZAiEapKRPGq0K Tp1r73w27HutsNDpsd8CzrNfIXGj6zuPBsaLUxH/wWvh5aOxlhtpgXUUtvh20GihqR/+ wo1mUdaAKQlWjJOkEUKXhuskNuJkEDY2vZNZHutisMGoX4MGlMocpYO3S34XUm9RpAfj 39vKhWcm2SZCIRcR507/+kf2eOxLdSW2+IdULBh2NxCmpTPsdfC6sEEYHOEmeOnocbGy AZlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679855671; h=content-transfer-encoding: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=5px0jYvLNrM8BO3g95exCwm4+Eb0NK+7bZu9uFmPVbY=; b=XqgybIVnpaHXxj/40Rw0wye7wx7Pyax3iGdI4edCvta8PTLCJEoclA0bE7hz1FdbAc t42XsN07YqWJq587YvgdT9LxofRjIHN6c3/7A2l6sQ5XqTIGhH1umijNGOpd1s5z06Xj fr+PJpLgMfJbIPa9X669/nz9WhYbLsSu1f+DDXkoSZGPKV1EzYpQPctTP1/PEBc0qa3N k6Q6Gb7j6CYNeDFg9lPA8zsJfv5Nd6ak77onjwwo/kY4RSZ8qOlpgFXONe/VbeidhQOP bQWln03zfx2Mts8KdSV0dMeJW38dDilCuUiXtxpWCSjhuJByEKm+df8j+UVHO08TXqr5 L7nw==
X-Gm-Message-State: AAQBX9cGgb+1tWjYETZAWcNO40VezrkXP//s4DfXjecWT0ZuMOi4QcYQ W+905LvqCgPFV94aU09x6kPENoNgUkIK3I7FjFvXv4YcGB/4qdk7Gqzk/w==
X-Google-Smtp-Source: AKy350ZQkzLw8DWxisHubB00zxh25O/iWztqdMOYMP6eZtSIjl4xGRgluMAcXSQKRMfEnMt2JmVryku3t+s+Ae7zj0I=
X-Received: by 2002:a92:6708:0:b0:326:ce2:df9e with SMTP id b8-20020a926708000000b003260ce2df9emr72633ilc.4.1679855671476; Sun, 26 Mar 2023 11:34:31 -0700 (PDT)
MIME-Version: 1.0
References: <c9e0219c-0bca-32ab-56b4-ead9427e7578@gmail.com>
In-Reply-To: <c9e0219c-0bca-32ab-56b4-ead9427e7578@gmail.com>
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 26 Mar 2023 14:33:55 -0400
Message-ID: <CAMBN2CScMLz9UzB-Fzp2NKPhZ-t4D0rZ72DnDPLPiVYAJ0Wt8A@mail.gmail.com>
To: dispatch@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/96BLpOsWp-wKpQ1t1WQ7Dsm2fJo>
Subject: [dispatch] Demonstration of W3C Implementer Support for Multibase at IETF (was: Re: 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: Sun, 26 Mar 2023 18:34:37 -0000

Similar to the recent email documenting support from the Multiformats
implementer community, a number of implementers in the W3C Community
wrote a similar letter to the W3C Verifiable Credentials Working Group
in support of the use of Multiformats (specifically, Multibase and
Multikey). To be clear, Multikey is NOT being requested for dispatch
at this time... only Multibase and Multihash are. The full text of
that letter of support[1] is included below:

To the Verifiable Credentials Working Group, Chairs, and Staff,

We, the undersigned, support the adoption of the EdDSA Cryptosuite[1]
as a standards-track deliverable of the W3C Verifiable Credentials
Working Group. We note that this cryptography suite is listed as in
scope in the W3C VCWG Charter[2]. We are already using, or plan to
use, this cryptography suite in our software and desire a ratified W3C
global standard for the cryptography suite.

Sincerely, the undersigned,

Trusted Learner Network with Arizona State University
Kate Giovacchini / Managing Director
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

RANDA Solutions
Marty Reed, CEO
W3C Member: Yes
Multibase (did:key)
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Mesur.io
Michael Prorock, CTO
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Danube Tech
Markus Sabadello, CEO
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

MIT Open Learning / Digital Credentials Consortium (DCC)
Kerri Lemoie / Technology Director
W3C Member: No (VC WG Inv Expert)
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Mavennet Systems Inc
Mahmoud Alkhraishi, Director of Engineering
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

ProofSpace
Nick Mason / CEO
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Conexxus
David Ezell / Director, New Initiatives
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2020

Digital Bazaar, Inc.
Manu Sporny / CEO
W3C Member: Yes
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Learning Economy Foundation
Jacksón Smith / CTO
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Participate
Julie Keane / CLO
W3C Member: No
Multibase (did:key)
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

TruAge Solutions, LLC.
Kyle McKeen / CEO
Patrick Abernathy / Manager Retail & Systems Engagement
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2020

FuixLabs
Tim O’Brien/ CEO
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Gobekli, Inc.
Kayode Ezike / Chief Architect
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2020

SmartResume
Andy Griebel / CTO
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

The Pinnacle Corporation
Peter Steele / VP of R&D
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Minor Decliner LLC
Ron Tobb / CEO
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

Tenderfoot Software, Ltd
Raymond Huff / Chief Architect
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2020

Instructure
Jonathan Featherstone / Architect
W3C Member: No
Our software systems use (or plan to use): Multibase (did:key),
Multikey (Ed25519 did:key), Ed25519Signature2018, Ed25519Signature2020

[1]https://lists.w3.org/Archives/Public/public-vc-wg/2023Jan/0027.html