Re: [dispatch] IETF 116 - do you have something for DISPATCH?

Christopher Allen <> Thu, 02 March 2023 05:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E6DB3C151B0E for <>; Wed, 1 Mar 2023 21:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cXn4QW-LjQLW for <>; Wed, 1 Mar 2023 21:02:36 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::529]) (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 1FC3AC15152B for <>; Wed, 1 Mar 2023 21:02:36 -0800 (PST)
Received: by with SMTP id cw28so13722496edb.5 for <>; Wed, 01 Mar 2023 21:02:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1677733353; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=xuIWYwmO0djfwaKzarwmns3ptnZG7wxTBsf7BAd7Ujc=; b=6B+JJNaesmJ1eUP77FqyktcuP0p0/mq74MjFic9d4w0JFytTTEQuYLhkGE7wg1Laeh VS6K3HMVCc8uASrZi8bq/Khrt0fPrUvtmGWYba6FIaq0fiMYDgL1+qJn2Vl4wh/QAac2 GFxmYLQLfim2liBZRh6/Mm2Jl8cqH7PcF+ZAh7w9Lv/bzIJCNN1aUWrrtqlF0TvNChaz L+GTV3dekzGbZFDM45dIy+hB5PFgMNQfhE5waRhbJwLDfEyGfBrTkLj/krJLG+0cCHeE IQemP8FQa1c4Zg/QNVB8ZefRrOKmHHc24fqLxsQ4ntrdVtyXlioj8+30+uoOe+k1qWj/ NQEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1677733353; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xuIWYwmO0djfwaKzarwmns3ptnZG7wxTBsf7BAd7Ujc=; b=qowxnxCOsf1a/bBj9iZu39IkaVS/IvjVIwca1kDRDWPudgC63fPI1+Ky02H9mr8BvT E5fxrwFfXKN/xDnAxDR4cHm6VzMhwleqyx77L9e0qw1W1NmJQgoaLvyK7SK7KK+peZ+F LhPbhrXDWiTTNvdJJwPm4jSbQ6AF3PdlTn/72XHaZhoTnR6uSBmnfni2xus5cMR+2LQY cdT9izKl36fGdipiMhNU4hCmvMY6IZWTVJ3cB8m/xXz8nAF9TfjRIELXWw9W7dXCn4Qi Txl0jJe6RAiiTErbDdP7DD9Y5IeA91dQxPJ3xrtJnoThklj5U9eA/zs+XtMw8oE4g/8R BvVA==
X-Gm-Message-State: AO0yUKXjQNtdo+hwhN+BpNL/m/Lvyh1haVoXecQm29IIL7ddLmgX0TMq QleFwifyVOUlgy2XAUCh+dvEvXTIkMzBabvAVzZX3tqePkHqJuIlHGw=
X-Google-Smtp-Source: AK7set9vBtQwf3T5uFLZT9B8lROzTvWSzBzwEe8/4mBLMNdFzc5xAjvAn/8o7VtQFpzVffZ9f/tEhQXwPA+R85PJ0B8=
X-Received: by 2002:a50:9f44:0:b0:4be:f5a0:a80f with SMTP id b62-20020a509f44000000b004bef5a0a80fmr1505246edf.0.1677733353450; Wed, 01 Mar 2023 21:02:33 -0800 (PST)
MIME-Version: 1.0
From: Christopher Allen <>
Date: Wed, 01 Mar 2023 21:02:22 -0800
Message-ID: <>
Content-Type: multipart/alternative; boundary="0000000000008f880f05f5e3bc6b"
Archived-At: <>
Subject: Re: [dispatch] IETF 116 - do you have something for DISPATCH?
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, 02 Mar 2023 05:02:37 -0000

On Tue, 21 Feb 2023 06:40:27 +0000 "Pengshuping (Peng Shuping)" <> wrote:

> It's that time again - we're calling for agenda topics for our next
> meeting at IETF 116 (25 - 31 Mar 2023). No matter how big or small, if you
> have something you'd like dispatching or that you think will be of interest
> to the ART AREA, get in touch and get involved.

My name is Christopher Allen. I’ve worked with IETF previously as the
editor of the TLS 1.0 standard, but it’s been a number of years since I've
been actively involved with IETF — most of my recent standards work has
been with the W3C.

I’m now the Principal Architect of Blockchain Commons, and I would love to
join your agenda for Dispatching a new project.

Blockchain Commons is working on Gordian Envelope, a “smart document” that
supports the secure, reliable, and deterministic storage and transmission
of data such as seeds, keys, decentralized identifiers, and verifiable
credentials in a way that enables privacy while preserving structure.

We’ve submitted it as an IETF Draft (and plan to have -01 submitted before
the I-D deadline this month):

Here are some general thoughts:

PROBLEM STATEMENT: Current document formats don’t focus on a user’s ability
to use elision, encryption, herd privacy, and other methods to preserve the
privacy of their data in a granular way.

EXISTING INTEREST: Several companies have seen the need for these
capabilities and have been participating in regular meetings on the topic. (

INTENDED DELIVERABLE: We want to produce a revised draft with more
community input to ensure that the specification meets the requirements of
a larger community.

We’d like to present on Gordian Envelope to Dispatch and get the best
advice on how to move forward. We would obviously like to work with groups
who might want to make use of Envelope for its privacy-preserving document
format. We also think we have critical mass on the US west coast to justify
a BOF there and would like to see if Dispatch would be interested in
supporting that.

As part of our work on the Gordian Envelope, we embraced deterministic CBOR
(dCBOR), which is the foundation of Envelope. dCBOR is an optional variant
of CBOR that lies in the CBOR spec but hasn’t been widely used. Because
determinism is very important for the hashing that we use at the center of
the Envelope format, we’ve created and released what we believe are the
only reference libraries focused on dCBOR as part of our intersectional
work on the topic. We’d love to get advice from Dispatch on how to work
with other CBOR-focused groups who might be interested in the work we’ve
done to support the deterministic subset defined in the IETF CBOR
specification. (We’ve tried to contact some on our own, but we appear to
getting stuck in email filters.)

Finally, we would like advice from Dispatch on the best way to register our
cryptographic-focused CBOR tags used in Envelope with IANA, namely whether
we should do so now, or whether we should wait for later in the IETF

Thank you very much for your advice and support. Please let us know of
anything else we can tell you and what else we’d need to do in order to
schedule a presentation with Dispatch.

-- Christopher Allen
   Blockchain Commons