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

"Pengshuping (Peng Shuping)" <> Fri, 03 March 2023 01:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BFC59C151AF4; Thu, 2 Mar 2023 17:38:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 JTcaF7Czydna; Thu, 2 Mar 2023 17:38:16 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0CB7FC15171E; Thu, 2 Mar 2023 17:38:16 -0800 (PST)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4PSVpy4J1Mz687Rd; Fri, 3 Mar 2023 09:33:14 +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; Fri, 3 Mar 2023 01:38:12 +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; Fri, 3 Mar 2023 09:38:10 +0800
Received: from ([]) by ([]) with mapi id 15.01.2507.021; Fri, 3 Mar 2023 09:38:10 +0800
From: "Pengshuping (Peng Shuping)" <>
To: Christopher Allen <>
CC: "" <>, Wolf McNally <>, "" <>
Thread-Topic: [dispatch] IETF 116 - do you have something for DISPATCH?
Thread-Index: AQHZTMRWflZYNtdmk0OUWoL2+dYrQ67nBfjggAB7wICAAMQtMA==
Date: Fri, 03 Mar 2023 01:38:10 +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_66e2e92642504f16bde9aeb1e73c694ahuaweicom_"
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: Fri, 03 Mar 2023 01:38:17 -0000

Hi Christopher,

A 20-min slot has been booked for you with the information you mentioned, including your co-presenter, your draft and RFC8949 as references. Please let me know if 20-min is not enough.

Regarding advice on BoF and IANA registration, I would suggest you talking with our ADs directly to get more information. I have copied the ADs’ email.

You could find general information on BoF in this link

Best Regards,

From: Christopher Allen []
Sent: Friday, March 3, 2023 5:48 AM
To: Pengshuping (Peng Shuping) <>
Cc:; Wolf McNally <>
Subject: Re: [dispatch] IETF 116 - do you have something for DISPATCH?

On Wed, Mar 1, 2023 at 11:01 PM Pengshuping (Peng Shuping) <<>> wrote:
Welcome to present your project in Dispatch and hope we could together figure out something helpful.

That would be great! Thank you very much.

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?

I suggest "Gordian Envelope & Deterministic CBOR" as the talk title, to talk about our I-D, but it leverages specific § 4.2 subset of CBOR in RFC 8949 ( that may interest a broader audience.

Wolf McNally, my co-author of this draft will be my co-presenter.

How much time should we prepare for? We will need to participate virtually for the Japan IETF, but plan to be F2F for San Francisco.

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.

The plan is to update that draft from -00 to -01 in the next to address some comments already received from members of various standards groups (in particular W3C).  We presented to the W3C Credential Community Group two weeks ago.

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.

We knew that we didn't have what would be necessary to qualify for a BOF for Japan — our goal is to do what is required to demonstrate support for one in San Francisco. We are not quite sure of other requirements we need to satisfy beyond the deadline for applying by May 26 for a San Francisco BOF.

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.

Thank you, I missed that one. I will reply there. There are multiple other groups that we hope might consider taking Gordian Envelope under their wing.

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

One of the specific challenges that we are seeking advice for is IANA registration. We understand with our I-D that we probably have met the criteria for qualifying for higher ranges of numbers for IANA registration of our CBOR tags, but as part of the goal of Gordian Envelope use of CBOR is to be concise, getting a smaller byte tag can be quite advantageous for the long term. So should we request from IANA now to make sure there are no collisions with others requesting tags, or wait until a group helps us qualify for a smaller CBOR tag? Best practices for working with IANA would be great.

Again, thank you for your help!

-- Christopher Allen