Re: [COSE] Last Call: <draft-ietf-cose-rfc8152bis-algs-08.txt> (CBOR Object Signing and Encryption (COSE): Initial Algorithms) to Informational RFC

tom petch <daedulus@btconnect.com> Fri, 22 May 2020 09:25 UTC

Return-Path: <daedulus@btconnect.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 74BC03A08FC; Fri, 22 May 2020 02:25:44 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 wMKkPIaTpIw5; Fri, 22 May 2020 02:25:42 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30121.outbound.protection.outlook.com [40.107.3.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02C503A08AF; Fri, 22 May 2020 02:25:41 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aL64EB7brhC5LMC1G4JaV4MPH/v+18vr1mpaMzR42FdTgz/8GynHoEgrUSL9s4RQ2tOaHxS3jf25el/jEHQeas/ouwhS2ckM0+okvTHbi5pg9EyG3J2aR3oWiD3BVQZOTSt5MvQjlHCaybyy2yTeFZsmyxRdmjAu/3myNvrUyGehVpBth6psxNSNzQyr0yXIged7/0EyZX0f/BE2BjICAfZUQ9EriQyxDWU2hFv1O6u4IvC9tEjzbfyQKax3PGYilKBlXNA3xslmE4UG0kPSR9blAwCXTIBSLu7mjm00X8AEMy9rbmp3MY5XUpkE3uRrJLR+YkQdGPpHcTF7d/znPA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZSkkI7GOuaoC530KDmBnxzKcB3DwRckzQhifFauwNv8=; b=OzeygE5lp5qb08NbTo2lzdU7B3AequWyZxc+3p759O3lFcQ3WwAIg8s86EOr2AhE80aSRorsxHAJx3JtN+fU1GleTbbykaISQHnbvpPo3MvqxQscNCMU8Wc0Mc5/Z3+DV+vbhsBd1gZiQS8+KEJq0m2BTzefWpoHA8svO+ZtzejJG/EBKn/Qy+4C3bg9pGX2P2LZ2N93uVxgwp3YNT8uMmHTqaUIyPlwHXf+RxzTlGKabb2jB7AB8cGg3bDnHt7VYBxc5OftCyBiBxokEDpGJBzuFlNiX29QIBg7vzYL41YtktzXBVcAAKGhc8KprwajVvGnWlhePW6V81SxspuF+g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZSkkI7GOuaoC530KDmBnxzKcB3DwRckzQhifFauwNv8=; b=LbBo5df4OLgzMDTxIAfBlv7NhrAUqiJUNCSAfsRcrq3PqjOXI9LKs/GICUN/xz0AJMyULk2ldj2ZJrKQbgrX/QCtbif4ltfJWXvLE4d+TLA1S6jhtZvVjnhYrUiQal0T9Ul0AUHOr7brjQEzCtQTzVFLTqQoDFkqDoWkFDgAu0o=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR0701MB6976.eurprd07.prod.outlook.com (2603:10a6:800:17d::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.8; Fri, 22 May 2020 09:25:39 +0000
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176]) by VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176%11]) with mapi id 15.20.3021.019; Fri, 22 May 2020 09:25:39 +0000
To: Last Call <last-call@ietf.org>
Cc: draft-ietf-cose-rfc8152bis-algs@ietf.org, cose-chairs@ietf.org, barryleiba@gmail.com, cose@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <5EC79A8E.50508@btconnect.com>
Date: Fri, 22 May 2020 10:25:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO2P265CA0175.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::19) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (81.131.229.108) by LO2P265CA0175.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3021.27 via Frontend Transport; Fri, 22 May 2020 09:25:38 +0000
X-Originating-IP: [81.131.229.108]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 328e28ff-1d90-4ccc-fd86-08d7fe32171c
X-MS-TrafficTypeDiagnostic: VI1PR0701MB6976:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB69765A78314385B5B08C44DCC6B40@VI1PR0701MB6976.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 04111BAC64
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 182w6LsNiG8TB2t3ONCj4ekY3ze2PvD68PsNlHv0pqjz1VrWTk4jVEeyB5rx8Kj2qWoDztYTc2T9X/dQhfOgQQeglU1+X2GUswSYaPBn+RuzfR3brNwoLfsnZaLgmwIBo+hsVEBUfqCus5EQmTFLYn1jJ8FKg5ZqlBVjXb6JgKiFdJh8+AFzO7d0sDwKhfj8ooHxbHBlxvlweBzqKw+3DJ4eTetkhR/QOL7I+/y06fasRJa+oPXko1BCx/bIZdpPQOKFhO8fyMdFsQdVJVPwnhWISoI5dJg+G1tI30UpaPjKJ6a41F8ly5p4LELBUv1K4qtdAeF7oyDbopEoH33MQuB3YmJiQi14E+Y+MOIDlHi3QfZE6bRqM1OSZOJ7f8iZW0RSEWHsViK40eM4YTZbhldt9SHnVlJqgyu21kWWI9hHmxXA6V5TxXA/m2gSadP+8rjyixLjPudiYITgBp5qag==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR0701MB2480.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(396003)(376002)(346002)(136003)(366004)(39860400002)(956004)(2616005)(2906002)(8936002)(8676002)(66476007)(6486002)(66556008)(4326008)(66946007)(33656002)(6916009)(16526019)(52116002)(478600001)(966005)(16576012)(316002)(6666004)(26005)(86362001)(36756003)(186003)(66574014)(5660300002)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: mf1pdccs3zVtd19Qwod1Ge1D6mf2whr1U88TJGBuBXPFV2SaowPvEwYjq5QCxbzarBqtsbDXDLjgBUhsy5amrTXt0/3/rj8yhnEAd0yRZpzDX+m8r1KB1XstqtvmHKtjtWdXsI+PGPZYlZd8poT6l/SQooRrQEgvSJ+r4+9p1w9i9mdmRk5x19UBl+w2wN9AN22r6Z1BBKYhcAmmQNuCNBy9YTiRjCmouuSDJS6qFpLXsLcBXNZMBqEaeMgw37AnPIPhyEPdNsgA9itmCueQyIY5zjewgGZfhjvyJy2TYFbp8Zccbno0fi38NAdicHtxQ9LsdaQcQi4sZwEgUE0uIrn/2Rs9MAw55zy2KMlM0UNTWkQNkLeCC7Cl61M2pJP05u2ENJK44bAnshgEbG9DJ1hF16QnWcmYIa1/EcMIoMQGHRpI6kddK4EP0no1Y2tZZcTopcipQOyqRfmy9GQ32sH9Dw9MVt5ipHicxaZIAuw=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 328e28ff-1d90-4ccc-fd86-08d7fe32171c
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 May 2020 09:25:39.4856 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: JDavXb0Pq7yY+fRkb16KzzlFms7UxzR0disvr7U9GdVhlN5W/UEFMNSgOHhV9/TTdso/Grtp91PXT5Gk+GD/qw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB6976
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/WFT6E-lZAkGVTB0vVhzypZK7JAc>
Subject: Re: [COSE] Last Call: <draft-ietf-cose-rfc8152bis-algs-08.txt> (CBOR Object Signing and Encryption (COSE): Initial Algorithms) to Informational RFC
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: Fri, 22 May 2020 09:25:45 -0000

This I-D obsoletes RFC8152, which set up the IANA Registry 'COSE
Algorithms', and adds a new column to the registry but otherwise
contains no details thereof so that, in future, a user will need to
study the obsoleted RFC8152 and this I-D to understand the specification
of the registry.

In fact, it is more complicated than that since RFC8152 defines the
permitted values in a column while the Informational I-D
draft-ietf-cose-hash-algs, currently in IETF Last Call, introduces a new
permitted value 'Filter Only '; to me, this is an update to RFC8152 (the
author disagrees), obsolete or not.  A future user wanting to understand
the registry will need to look at
- the obsoleted RFC8152
- this obsoleting I-D
- the informational draft-ietf-cose-hash-algs

Could be simpler for a future user.

Tom Petch

> ----- Original Message -----
> From: <internet-drafts@ietf.org>
> To: <IETF-Announce>
> Cc: <draft-ietf-cose-rfc8152bis-algs@ietf.org>; <cose-chairs@ietf.org>;
> <barryleiba@gmail.com>; <cose@ietf.org>
> Sent: Friday, May 15, 2020 2:35 PM
>
>> The IESG has received a request from the CBOR Object Signing and
> Encryption
>> WG (cose) to consider the following document: - 'CBOR Object Signing
> and
>> Encryption (COSE): Initial Algorithms'
>>    <draft-ietf-cose-rfc8152bis-algs-08.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
> final
>> comments on this action. Please send substantive comments to the
>> last-call@ietf.org mailing lists by 2020-05-29. Exceptionally,
> comments may
>> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning
>> of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     Concise Binary Object Representation (CBOR) is a data format
> designed
>>     for small code size and small message size.  There is a need for
> the
>>     ability to have basic security services defined for this data
> format.
>>     This document defines the CBOR Object Signing and Encryption (COSE)
>>     protocol.  This specification describes how to create and process
>>     signatures, message authentication codes, and encryption using CBOR
>>     for serialization.  COSE additionally describes how to represent
>>     cryptographic keys using CBOR.
>>
>>     In this specification the conventions for the use of a number of
>>     cryptographic algorithms with COSE.  The details of the structure
> of
>>     COSE are defined in [I-D.ietf-cose-rfc8152bis-struct].
>>
>>     This document along with [I-D.ietf-cose-rfc8152bis-struct]
> obsoletes
>>     RFC8152.
>>
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-algs/
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> .