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

Christopher Allen <> Thu, 02 March 2023 21:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EC0BCC151AED for <>; Thu, 2 Mar 2023 13:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Status: No, score=-6.896 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_HI=-5, 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
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oFQv-i5_fPpS for <>; Thu, 2 Mar 2023 13:59:45 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::534]) (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 130E7C14CE33 for <>; Thu, 2 Mar 2023 13:59:45 -0800 (PST)
Received: by with SMTP id cw28so2840838edb.5 for <>; Thu, 02 Mar 2023 13:59:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1677794383; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=8npzspVTVnJPO96nHOR6kbacd1Ke3RH/IIDVXIkWLVg=; b=yRUaWkZGWRg//81va6I+OQmfZ2dGm5t+MVRh/HoJiKrRRM/QO20F52vFjGhvOgZoY+ PeVVSHtpSMaWrZ0QngQCmJuHkUG8ZL8FQ5AzY26cCAW+BerNrKyfCV5rX8Ii3CI6AbFd +eh79qaiKjQZ6xU5SEio/9HxcfSB+AXuz+46qsctyvN0qw0X7pSSPI12r1F3gIehBE5i ZqxEljf/hHRlpNQ1nQv73a7itaU9bTrAgB6bps2giCNu2BcZUv0/8H58C0BsQ2zdMsMQ XqaQ0tQp2ZoLVyP15uJ5UCTunhddHJIoTdtdClC1ZfmkHiIBFnjRtr1tr2M2lyk2A4wf yyag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1677794383; h=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=8npzspVTVnJPO96nHOR6kbacd1Ke3RH/IIDVXIkWLVg=; b=YW5JCCleLBIIkPFXo1+DnmfPYxQrNuOFwm9uZNrf1+KJCO6CDw6EHZ7AauVi1GeAbE MWFt9OUCMken+0g9CPmbBzBYEDKa8prMn+3ho8GEvU27BddZUWiwwUdT83bh1sGUtIn6 tF9p1gKSD1h6bU23wV4RWFQJ93g582vrQr0sJcD47FrCbqUFKDE5CjRzg2QKuptyaRYQ Mv6GIiHlLNXcR3vLz43jUOulnj8Jb73bzclybWml686IcR6fC3n3mJkzABYE2zvQm4Wf JENCjX8e9c+6Lk9kF04tebKyYwSYUVPW4rQeUP0q9g3rBL7HFDU93thLLoLyglgA5+6z m5jg==
X-Gm-Message-State: AO0yUKXoI5a3ayY/xiEYhNNGIZ9DZY/0wnmMtZNz8qYBsPUZ8wQmRH11 ius2omAIDoVrfFNWa0wKjhm0VQxItTg1uPctZhde8IC5RN8Xp4JbzOs=
X-Google-Smtp-Source: AK7set/sNxBLkRg6zkkG9Iys5/nRetiqPb0fF8xvkdJd8PbONCTUiekh2sX6HcJjMMKbgqvVZOj7QrtIm7r2hJLoR1k=
X-Received: by 2002:a17:906:af6a:b0:87d:ce4:eb7a with SMTP id os10-20020a170906af6a00b0087d0ce4eb7amr5708709ejb.13.1677794383017; Thu, 02 Mar 2023 13:59:43 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Christopher Allen <>
Date: Thu, 02 Mar 2023 13:59:32 -0800
Message-ID: <>
Content-Type: multipart/alternative; boundary="00000000000034cad605f5f1f2a5"
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 21:59:49 -0000

*(sorry if this msg might be a dup — I'm having problems with emails sent
from google to ietf, and am trying an alternative sender)*

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

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

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