[COSE] [Technical Errata Reported] RFC8152 (6597)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 03 June 2021 12:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 941123A0D2D for <cose@ietfa.amsl.com>; Thu, 3 Jun 2021 05:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 Qmjb2VNQXEDO for <cose@ietfa.amsl.com>; Thu, 3 Jun 2021 05:20:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22203A0D39 for <cose@ietf.org>; Thu, 3 Jun 2021 05:20:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5BB49F406F3; Thu, 3 Jun 2021 05:19:38 -0700 (PDT)
To: ietf@augustcellars.com, rdd@cert.org, kaduk@mit.edu, ivaylo@ackl.io, linuxwolf+ietf@outer-planes.net, michael.jones@microsoft.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: anders.rundgren.net@gmail.com, cose@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210603121938.5BB49F406F3@rfc-editor.org>
Date: Thu, 03 Jun 2021 05:19:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/WohJXCnCZlss9P-OHzu6xJqIB0E>
Subject: [COSE] [Technical Errata Reported] RFC8152 (6597)
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: Thu, 03 Jun 2021 12:20:10 -0000

The following errata report has been submitted for RFC8152,
"CBOR Object Signing and Encryption (COSE)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6597

--------------------------------------
Type: Technical
Reported by: Anders Rundgren <anders.rundgren.net@gmail.com>

Section: 12.5.1.

Original Text
-------------
The RFC is unclear to whether Concat KDF or HKDF is to be used:

In table 20 there is an entry:
ECDH-ES +  -31   | HKDF -  | yes        | A256KW | ECDH ES w/    |
   | A256KW    |       | SHA-256 |            |        | Concat KDF    |
   |           |       |         |            |        | and AES Key   |
   |           |       |         |            |        | Wrap w/       |
   |           |       |         |            |        | 256-bit key  

That is, the table talks both about Concat and HKDF.

The IANA registry for this algorithm says Concat KDF

Jim's sample code for algorithm -31 says HKDF.

Corrected Text
--------------
I have no corrected text to offer since I don't have the answer to the question raised.

Concat is referred to once and without any external references.  In JOSE, Concat denotes a NIST standard which is quite different to HKDF.

Notes
-----
It is pretty vital for interoperability knowing if Concat KDF or HKDF is to be used.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8152 (draft-ietf-cose-msg-24)
--------------------------------------
Title               : CBOR Object Signing and Encryption (COSE)
Publication Date    : July 2017
Author(s)           : J. Schaad
Category            : PROPOSED STANDARD
Source              : CBOR Object Signing and Encryption
Area                : Security
Stream              : IETF
Verifying Party     : IESG