Re: [dispatch] Dispatch IETF 116 outcomes & minutes

Manu Sporny <> Thu, 30 March 2023 15:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 942FDC13AE45 for <>; Thu, 30 Mar 2023 08:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
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, 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=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6PBKda4WppmH for <>; Thu, 30 Mar 2023 08:06:34 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::d33]) (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 (Postfix) with ESMTPS id 758F6C13AE38 for <>; Thu, 30 Mar 2023 08:06:34 -0700 (PDT)
Received: by with SMTP id m22so8409215ioy.4 for <>; Thu, 30 Mar 2023 08:06:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; t=1680188793; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=rjF6RRua1y1QMeUj+cXSE4RBKJ9hJBJwZY++aBkL3bU=; b=pAVhTVCKfPGnKmcjsnWToshZ9ZcmWPrD5/5PELs+FKpaHakZIG9TuM5WESp9Cj/39C ya9N/D3Bc/QWn9/XTHU6Se0BfH2my8xBuJ8Mn27e0KYFQIzMkF4uvTVnmdPTBYFI7+Bw mNyCFIT9do/fASQNu5Sr1DZnROKPY1zLv+lEIJeuxeK9qM/JWVR4e0+FnKhpFPUSmBkD uVqSjVaKs5sFal5Zha2501jCu3HlVdc0XVow4mmF2xnluDMlitM+TJdYCALGJr+fspGb qADgIIjo1Q4JNBR3fIr/hM/Dk/fsz6YynAeV/HL8zV+bKaVZkKcC0Fv9aZd6phRtSdZM Tm2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1680188793; h=content-transfer-encoding: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=rjF6RRua1y1QMeUj+cXSE4RBKJ9hJBJwZY++aBkL3bU=; b=EjndkLwKC+MwJNCGG3iCmHE9XCmw7bA3RxylgheKGMsBOexZ+dMeWm/PKEDzGD542d 9DLFUEf25BO9NOBKD3pLIQv4l+cQf0StqToYt137MGJSrXZbS2KZQR4IkIm3K0rC7l2w EsOm+Q+QC3ZoQHbAXt2By81Rot2cFGSQ0cfNCP4URIEpiRls7rwDSaO03JVCWXC5CCoo lN+C5L1WqQfJMSxJlZK1KMIkO8HyiSKrP9vavxfaQ9LnNfJUkKBhBIrsDy/OCPY/pelw 4GLGlrEat1O7ep3QjArAzMrCoIqq7wW76reDMmYpP2TLAhMCfXCsz1BKcAqS6hsCcjfJ cajw==
X-Gm-Message-State: AAQBX9cB8H7d89O4cPrmcFtIDf2zud7pHP7x8lcVxFlRbPiyZtqPYKsk bInLsnaUvFZPPWSMzesyXk4tPFWQ5RQOq3uXmhy9m+y6vYY4aWuFvlrYOg==
X-Google-Smtp-Source: AKy350ZMgEI0DGbKUfORPJ098fiPAGr6ysObHoddLKpk94VYOpAFY2ANi03lBFdz9Zboi17JgQvstRdh3WVJqzbEdIQ=
X-Received: by 2002:a02:628f:0:b0:406:6686:2e0c with SMTP id d137-20020a02628f000000b0040666862e0cmr2908310jac.3.1680188792977; Thu, 30 Mar 2023 08:06:32 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Manu Sporny <>
Date: Thu, 30 Mar 2023 11:05:57 -0400
Message-ID: <>
To: DISPATCH list <>
Cc: dispatch-chairs <>,
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [dispatch] Dispatch IETF 116 outcomes & minutes
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 30 Mar 2023 15:06:38 -0000

On Mon, Mar 27, 2023 at 12:41 PM Manu Sporny <> wrote:
> The concept of a quick, tightly focused WG to just
> address the two work items proposed is compelling

Dispatch for Multiformats is now complete. An email list has been
created for further discussion on Multiformats at IETF, please join
that mailing list if you have input and/or want to track the mini-WG
path vs. ISE path discussion related to Multiformats at IETF:

> 1. Send an email to each commenter with unaddressed concerns,
>  to more completely address concerns raised during the
> dispatch presentation and confirm whether or not there was a
> misunderstanding or a design flaw.

This will happen on the IETF Multiformats mailing list.

> 2. Request input from the Multiformats implementers on their
> preference wrt. ISE or WG. One challenge would be finding a Chair for
> the WG and coordinating activity through IETF (given that much of the
> Multiformats community operates outside of IETF and W3C).

This will happen on the IETF Multiformats mailing list.

> 3. Start drafting a presumptive Multiformats mini-WG charter to
> determine what a mini-WG could look like and what it might and might
> not change.

A first draft of a mini-WG charter for Multiformats has been created here:

Discussion on that charter will proceed on the IETF Multiformats mailing list.

This will be the last email about Multiformats to the dispatch mailing
list. Join the Multiformats mailing list if you want to track or
participate in the discussion:

-- manu

Manu Sporny -
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)