[COSE] Inconsistencies in COSE registry names
Mike Jones <Michael.Jones@microsoft.com> Wed, 30 November 2016 23:42 UTC
Return-Path: <Michael.Jones@microsoft.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 3F6AD129BC8 for <cose@ietfa.amsl.com>; Wed, 30 Nov 2016 15:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 4uckeH5NuEGs for <cose@ietfa.amsl.com>; Wed, 30 Nov 2016 15:42:01 -0800 (PST)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0132.outbound.protection.outlook.com [104.47.41.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1F0D129BBC for <cose@ietf.org>; Wed, 30 Nov 2016 15:42:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=28YL5kvv+1wbo5J0ySm1I1mbvL/W9pzmy1iJw0TZBbI=; b=GciFlyo7KFz6+ZDLR87QTkhfwroXLfXjh/ADoXk/wDoXs5RcRfHzFX1O1omommeHhPDbzLBLLvae8x2Sny1Wk5jJ6jn9GHRE1ZjAw5izPmPFE5Asc6Ol4GQQhO3nz8vKrvOo9rKzFXkZhUQ+jU+vFCukSuDYiV+L2s111cyu0NY=
Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2354.namprd03.prod.outlook.com (10.166.74.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.747.13; Wed, 30 Nov 2016 23:41:59 +0000
Received: from BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) by BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) with mapi id 15.01.0747.018; Wed, 30 Nov 2016 23:41:59 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "cose@ietf.org" <cose@ietf.org>
Thread-Topic: Inconsistencies in COSE registry names
Thread-Index: AdJLW99SlzMLCIrmQwmmIG2x2VFJ3g==
Date: Wed, 30 Nov 2016 23:41:58 +0000
Message-ID: <BN3PR03MB23557F3466DD41466B6EFF98F58C0@BN3PR03MB2355.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com;
x-originating-ip: [2001:4898:80e8:1::650]
x-ms-office365-filtering-correlation-id: 33456984-78ca-424a-8aae-08d4197a7a16
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR03MB2354;
x-microsoft-exchange-diagnostics: 1; BN3PR03MB2354; 7:DHNXjBlg0wu+07UqEypCUzBhANFXI2riwe7zDji2TFlJSTA/d0N9uVnqluRgyJjfHua4I9C5y8SezgtmfuZdCfJv69x9i0CGbUsKLH8ZDnDDDuhVpajfHRHpYhInaoXzFRWZSk4K8M2mH2GzK3PuXSdGO/4AdjJnCYc3hA/v5YOXy5u1dTT9/2kSfbiPdhMZPDkx7+OvsoE5pr2BbhQHLW8JFb0EI//TW943cPtY/huu2yMy6bJcJ1mFmoUP0i2x0Ai0tWAWE3UqD1PXTvWzlmHt18lUsGi/KUKxZJkdPy5XWtBnXxcRX7ni0AuuQ3p5M2Clc6A0diD9bTkhgSN7IsOAenjgK/r8704BB9ecOAomVk54yOVZd/kf53xOxXuL4lmzXGPGQcRBXr9N+gzxPMhHcYJSQnbthzryCg/6w5CMoIAYV/1AjMtN6Gqk8ZQ3BqsO1inPi8hC+3ugiRoN+pcTVyqMtPXrbbZYerlCbdc=
x-microsoft-antispam-prvs: <BN3PR03MB2354079D174B7F370D622530F58C0@BN3PR03MB2354.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123560025)(20161123564025)(20161123555025)(20161123562025)(6042181)(6047074)(6072148); SRVR:BN3PR03MB2354; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2354;
x-forefront-prvs: 0142F22657
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(199003)(189002)(77096006)(33656002)(76576001)(99286002)(5660300001)(3280700002)(2900100001)(4326007)(5005710100001)(68736007)(7696004)(106356001)(189998001)(92566002)(10290500002)(9686002)(105586002)(10090500001)(3660700001)(8936002)(5001770100001)(2501003)(7736002)(74316002)(86362001)(8990500004)(97736004)(6116002)(81166006)(39060400001)(7846002)(86612001)(2906002)(81156014)(54356999)(6506003)(101416001)(8676002)(50986999)(606004)(7906003)(790700001)(122556002)(38730400001)(102836003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2354; H:BN3PR03MB2355.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR03MB23557F3466DD41466B6EFF98F58C0BN3PR03MB2355namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Nov 2016 23:41:58.8352 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2354
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/RYQcccxumwg8z8JkDzKTau2HHrs>
Cc: Jim Schaad <ietf@augustcellars.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Subject: [COSE] Inconsistencies in COSE registry names
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.17
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, 30 Nov 2016 23:42:09 -0000
While working on another spec using COSE https://tools.ietf.org/html/draft-ietf-cose-msg-24, I noticed that multiple inconsistent names are used for the same registries in some cases. I hope that this can be addressed by the RFC Editor (included in this communication) before publication. 1. Where multiple names appear on the same line below, I believe they refer to the same registry. What I believe to be the correct name is first: "COSE Header Parameters", "COSE Header Labels" "COSE Algorithms", "COSE Algorithm Value", "COSE Algorithm Values" "COSE Key Type Parameters", "COSE Key Type Parameter Labels" 2. The registry name "COSE Curves" is used in the table in 13.1.1 (Double Coordinate Curves) but doesn't refer to any registry I'm aware of. 3. I believe that the name "COSE Key Type" should be changed to "COSE Key Types" for consistency sake, since all the other registry names use plurals. 4. There are several places in the running text in which the word "Registry" is included in the registry name in quotation marks, rather than being placed outside the quotation marks. For instance, I believe these changes should be made in the body text: "COSE Key Type Registry" -> "COSE Key Type" registry "COSE Key Common Parameters Registry" -> "COSE Key Common Parameters" registry For completeness, I believe these registry names and their usages are fine: "COSE Header Algorithm Parameters" "COSE Key Common Parameters" "COSE Elliptic Curve Parameters" -- Mike