Re: [COSE] Benjamin Kaduk's Discuss on draft-ietf-cose-hash-sig-07: (with DISCUSS and COMMENT)

Russ Housley <housley@vigilsec.com> Wed, 04 December 2019 22:50 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA8112004E for <cose@ietfa.amsl.com>; Wed, 4 Dec 2019 14:50:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KARQz47EgUj5 for <cose@ietfa.amsl.com>; Wed, 4 Dec 2019 14:50:37 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1449120046 for <cose@ietf.org>; Wed, 4 Dec 2019 14:50:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4DAD2300ADB for <cose@ietf.org>; Wed, 4 Dec 2019 17:50:35 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dT_4fn6ZjT-a for <cose@ietf.org>; Wed, 4 Dec 2019 17:50:33 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id 3092C3004B0; Wed, 4 Dec 2019 17:50:33 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <157539486101.24700.12161503456212968239.idtracker@ietfa.amsl.com>
Date: Wed, 4 Dec 2019 17:50:33 -0500
Cc: IESG <iesg@ietf.org>, cose-chairs@ietf.org, cose <cose@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <53448421-CFA3-49D1-88CE-92D759E8D825@vigilsec.com>
References: <157539486101.24700.12161503456212968239.idtracker@ietfa.amsl.com>
To: Ben Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/BqCW9cp3AvmcpWzdK_paH7YoFz0>
Subject: Re: [COSE] Benjamin Kaduk's Discuss on draft-ietf-cose-hash-sig-07: (with DISCUSS and COMMENT)
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2019 22:50:39 -0000

Ben:

> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I do see the previous discussion in
> https://mailarchive.ietf.org/arch/msg/cose/E6ApKPKlESQQSZwySJAVF1l27OE
> but I am still unclear on where exactly we can represent the octet
> string that is the HMS-LMS public key.  Do we not need to define a COSE
> Key Type Parameter (i.e., label) that maps to the public key value?  For
> reference, the examples in Appendix C.7.1 of RFC 8152 include key/value
> pairs with the negative map labels from
> https://www.iana.org/assignments/cose/cose.xhtml#key-type-parameters
> corresponding to the key type in question.
> Hopefully I'm just confused and missing where this is already done, but
> marking as a Discuss point in case I'm not.  (The linked
> cose-wg/Examples seem to be using a JSON structure to describe the input
> to the example generation, with the "public" and "private" members of
> the "key" that do not seem to correspond to anything that I can find at
> https://www.iana.org/assignments/jose/jose.xhtml#web-key-parameters, and
> which would in any case not directly apply to the *COSE* usage.)

I suggest:

6.3.  COSE Key Type Parameters Registry Entry

  The new entry in the "COSE Key Type Parameters" registry [IANA] has
  the following columns:

     Key Type:  TBD  (Value to be assigned above by IANA)

     Name:  pub

     Label:  TBD (Value to be assigned by IANA)

     CBOR Type:  bstr

     Description:  Public key for HSS/LMS hash-based digital signature

     Reference:  This document (Number to be assigned by RFC Editor)

Russ