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

"Pengshuping (Peng Shuping)" <> Thu, 02 March 2023 07:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4C47CC151B19 for <>; Wed, 1 Mar 2023 23:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1aNJC0P5e0oS for <>; Wed, 1 Mar 2023 23:00:30 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 807FCC14CE55 for <>; Wed, 1 Mar 2023 23:00:30 -0800 (PST)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4PS26l1vRyz6J6cC for <>; Thu, 2 Mar 2023 15:00:15 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 2 Mar 2023 07:00:24 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 2 Mar 2023 15:00:23 +0800
Received: from ([]) by ([]) with mapi id 15.01.2507.021; Thu, 2 Mar 2023 15:00:23 +0800
From: "Pengshuping (Peng Shuping)" <>
To: Christopher Allen <>, "" <>
Thread-Topic: [dispatch] IETF 116 - do you have something for DISPATCH?
Thread-Index: AQHZTMRWflZYNtdmk0OUWoL2+dYrQ67nBfjg
Date: Thu, 02 Mar 2023 07:00:23 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5b48df1d182f418f9d1cc7d8ec3b2ad1huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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 07:00:32 -0000

Hi Christopher,

Welcome to present your project in Dispatch and hope we could together figure out something helpful.

I will book a slot for you in our Agenda in this meeting. Shall I use the title of “Gordian Envelope” and put you as the presenter?
You mentioned about your willingness about a revised draft, would it be a new draft or based on this draft You could present the work you want to do in your presentation so people would know more about your idea and work with you.

Regarding the BoF, it is great that you have the support to justify a BOF. However, it would be too late to have a BoF in this IETF116 since the Cut-off date (2023-02-17) for Area Directors to approve BOFs has passed. By presenting and attending this IETF you would probably get more support, and you would collect advice to have an effective BoF in the next IETFs.

Regarding the work with CBOR, I found that there are some discussions on this topic in CBOR WG recently. Please see the archived email. It was actually your email being forwarded. Maybe you could start joining the discussions there.

You could summarize your requests in your presentation at Dispatch WG and ask for advice from the community.

Best Regards,

From: dispatch [] On Behalf Of Christopher Allen
Sent: Thursday, March 2, 2023 1:02 PM
Subject: Re: [dispatch] IETF 116 - do you have something for DISPATCH?

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 process.

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