Re: [Suit] [COSE] draft-atkins-suit-cose-walnutdsa

Derek Atkins <> Wed, 31 July 2019 15:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0601212006D; Wed, 31 Jul 2019 08:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qYBwy8qiP7lP; Wed, 31 Jul 2019 08:12:34 -0700 (PDT)
Received: from (MAIL2.IHTFP.ORG []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EB4B412004F; Wed, 31 Jul 2019 08:12:33 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 85570E2044; Wed, 31 Jul 2019 11:12:32 -0400 (EDT)
Received: from ([]) by localhost ( []) (amavisd-maia, port 10024) with ESMTP id 24378-01; Wed, 31 Jul 2019 11:12:26 -0400 (EDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "IHTFP Consulting Certification Authority" (not verified)) by (Postfix) with ESMTPS id 66969E2040; Wed, 31 Jul 2019 11:12:26 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=default; t=1564585946; bh=GsOlVcbMjQpRtrpnT7KlkNLRq8lETed1zOmUf5cND0A=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=JUUc3yal8byLa38LSNRD4869qHimZ0g7+zk1IAn4jvy1qlePolXMNfWbHY8g+0w6r fjL7ubA4fvrBRIUdsopuEfBXZ4h+scGI9gLv+cAbAo99CXw5jsz5e5EihrXLgTKnWN YfYNQhq8bJoz8pDnywPu/KuhRcUmykuip6Shr8jY=
Received: (from warlord@localhost) by (8.15.2/8.15.2/Submit) id x6VFCK40022565; Wed, 31 Jul 2019 11:12:20 -0400
From: Derek Atkins <>
To: Michael Richardson <>
Cc:, "" <>
References: <> <> <835.1562080969@localhost>
Date: Wed, 31 Jul 2019 11:12:19 -0400
In-Reply-To: <835.1562080969@localhost> (Michael Richardson's message of "Tue, 02 Jul 2019 11:22:49 -0400")
Message-ID: <>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <>
Subject: Re: [Suit] [COSE] draft-atkins-suit-cose-walnutdsa
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 31 Jul 2019 15:12:36 -0000


Again, sorry for the delay in responding.  I've had a lot of $DAYJOB
deadlines which have taken over and some things have fallen through the
cracks.  Too many balls in the air, so to speak.

Comments are inline below..

Michael Richardson <> writes:

> Derek, looking at the IANA Considerations of
> draft-atkins-suit-cose-walnutdsa, it seems that you need a number in:
> 1) COSE Algorithms -- registry
> 2) COSE Key Types -- registry
> and several in the
> 3) COSE Key Type Parameters -- registry


> For the first, you can have:
>     Integer values greater than 65535	Expert Review
> And the other two are Expert Review anyway, no specification required!
> You are even listed as one of the experts for COSE Key Types :-)

Yes, I know I am one of the experts for these registries.  However, I
feel I must recuse myself from approval of these.

> {If my reading is correct, you can also use strings longer than 2-bytes
> without registration with IANA, but that has an operational (maintaining
> legacy code) and bytes-on-the-wire impact should you be allocated a shorter
> code later on}

Yes, which is another reason I'd rather get something right.

> You could also ask for early allocation via the COSE WG, but that probably
> requires the document to be adopted first!

Does it?  Or does the WG just need to approve of the document going
through any of the publication processes?

> That's what I would do: just ask for the values via Expert Review, and live
> for now, with the a five-bye (encoded) COSE Algorithm code, if your market
> need is urgent.

Yes, I could just request the entries in the registry.  However, I am
trying to be a good netizen; I want to have a document that people can
look at to understand what the registry items mean.

> Derek Atkins <> wrote:
>     > We have customers who are looking to use this technology today, so we
>     > would like to do it in a standard way that others could understand.
>     > Personally, I'm fine with an Informational (instead of Standards-track)
>     > publication if that would make people happier.  Even so, the RFC Editor
>     > would still require approval from this WG as it is within their (the
>     > WG's) area.
> yes, if you went ISE, which would still take awhile.

I am fine going through the ISE, however I suspect that the IESG in
their conflict review would then go and ask this WG about it.  So I
wanted to bring it up here, first.  What is your definition of "awhile"?


> Michael Richardson <>, Sandelman Software Works
>  -= IPv6 IoT consulting =-

       Derek Atkins                 617-623-3745   
       Computer and Internet Security Consultant