| Internet-Draft | COSE Registration Principles | July 2023 |
| Bormann | Expires 25 January 2024 | [Page] |
COSE (STD 96, RFC 9052 and RFC 9338) defines a number of registries that allow registrants to exercise the numerous extension points defined in COSE. Section 11.6 of RFC 9052 gives the Designated Experts for these registries considerable leeway in deciding about registration requests.¶
The present document is intended to collect information that has been the basis for initial population of and further registration in these registries. It is intended to be shaped by the Designated Experts and serve them as a collective memorandum and a checklist. As a secondary function, it is also intended to help registrants create registrations that are acceptable to the Designated Experts.¶
Revision -00 of this draft is an early skeleton that should allow us to decide whether such a collection of information is useful and whether we want to flesh out this document.¶
This note is to be removed before publishing as an RFC.¶
Status information for this document may be found at https://datatracker.ietf.org/doc/draft-bormann-cose-registration-principles/.¶
Discussion of this document takes place on the CBOR Object Signing and Encryption (COSE) Working Group mailing list (mailto:[email protected]), which is archived at https://mailarchive.ietf.org/arch/browse/cose/. Subscribe at https://www.ietf.org/mailman/listinfo/cose/.¶
Source for this draft and an issue tracker can be found at https://github.com/cabo/cose-regprin.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 25 January 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
COSE (STD 96, RFC 9052 and RFC 9338) defines a number of registries that allow registrants to exercise the numerous extension points defined in COSE. Section 11.6 of RFC 9052 gives the Designated Experts for these registries considerable leeway in deciding about registration requests.¶
Specifically, Section 11.6 of [RFC9052] says:¶
11.6. Expert Review Instructions¶
All the IANA registries established by [RFC8152] are, at least in part, defined as Expert Review [RFC8126]. This section gives some general guidelines for what the experts should be looking for, but they are being designated as experts for a reason, so they should be given substantial latitude.¶
([RFC8152] is the previous edition of what is now RFC9052 and [RFC9053]; this document established the registries being discussed, which together make up the [IANA.cose] registry group.)¶
The further text of Section 11.6 of [RFC9052] gives instructions about the general operations of the registries, but does not discuss the architectural and structural principles that might go into a registration decision.¶
The present document is intended to collect information that has been the basis for initial population of and further registration in these registries. It is intended to be shaped by the Designated Experts and serve them as a collective memorandum and a checklist. As a secondary function, it is also intended to help registrants create registrations that are acceptable to the Designated Experts.¶
Revision -00 of this draft is an early skeleton that should allow us to decide whether such a collection of information is useful and whether we want to flesh out this document.¶
This section is a skeleton and needs to be fleshed out.¶
At the time of writing, some 172 registrations have been made in the COSE registry group [IANA.cose]. These can serve as a body of examples how to make registrations. Unfortunately, not all registrations in this set demonstrate outstanding consistency in decision-making, so this section will also collect information about where existing registration decisions turned out to be suboptimal or at least different in structure than registrations of a similar nature.¶
COSE is designed to work in environments where at least some of the devices have limited resources; curation of codepoints so that the ones that are most frequently used with such constrained devices receive the codepoints with the shortest representation (and can continue to do so over a number of decades) is always an objective.¶
Algorithm identifiers in these registrations have a Recommended Tag, which indicates (Section 16.4 of [RFC8152]):¶
- Recommended:
Does the IETF have a consensus recommendation to use the algorithm? The legal values are 'Yes', 'No', and 'Deprecated'.¶
Note that an algorithm can be deprecated already at registration time. This value was used in the registration of the [I-D.ietf-cose-aes-ctr-and-cbc] values which only can be used under very specific conditions.¶
Algorithm identifiers are usually assigned so that a single identifier stands for a collection of underlying algorithms, with main parameters such as key or hash length chosen, so that a single algorithm identifier suffices to fully characterize the cryptographic operations. A key is the obvious exception, but also parameters that go with a key such as its curve type.¶
Where a certain underlying algorithm has a small number of possible parameter sets, all registrations for the use of that underlying algorithm in a COSE Algorithm are made at the same time. For instance: A128GCM (AES-GCM mode w/ 128-bit key, 128-bit tag) we registered together with A192GCM (AES-GCM mode w/ 192-bit key, 128-bit tag) and A256GCM (AES-GCM mode w/ 256-bit key, 128-bit tag). The expert (in this case the author of [RFC9053]) did not make separate assessments how useful or desirable the individual parameter sets were going to be, but registered them all at once. When the collection of AES-CCM-16-64-128, AES-CCM-16-64-256, AES-CCM-64-64-128, and AES-CCM-64-64-256, as well as AES-CCM-16-128-128, AES-CCM-16-128-256, AES-CCM-64-128-128, and AES-CCM-64-128-256 were registered, these were also registered all at once, but grouped into two groups with different representation sizes of the algorithm identifier.¶
...¶
This registry is governed by similar principles as the COSE Algorithms registry (Section 2.4). Curve types identify all parameters of a curve and are registered all at once where natural groups of such types exist.¶
This document is about registrations in registries that have direct security impact; security considerations that require discussion beyond that are mentioned in the discussions above.¶
This document has no IANA actions.¶
This document was motivated by a discussion at IETF 117 Hackathon. The author is grateful to the many contributors to the discussions on the mailing lists that build the basis for this document.¶