Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Thomas's Part of the review comments addressed

Co-authored-by: Thomas Fossati <[email protected]>
  • Loading branch information
yogeshbdeshpande and thomas-fossati authored Feb 24, 2025
1 parent 09f4f16 commit 5ac4b44
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions draft-ietf-rats-corim.md
Original file line number Diff line number Diff line change
Expand Up @@ -292,17 +292,17 @@ The CDDL definitions in this document follows the naming conventions illustrated

A CoRIM is a collection of tags and related metadata in a concise CBOR {{-cbor}} encoding.
A CoRIM can be digitally signed with a COSE {{-cose}} signature.
A tag is a structured, machine-readable metadata format used to uniquely identify, describe, and manage modules or components of a system.
A tag is a structured, machine-readable data format used to uniquely identify, describe, and manage modules or components of a system.

Tags can be of different types:

* Concise Module ID (CoMID) tags ({{sec-comid}}) contain metadata and claims about the hardware and firmware modules.

* Concise Software ID (CoSWID) tags ({{-coswid}}) uniquely identify, describe, and manage software components.
* Concise Software ID (CoSWID) tags ({{-coswid}}) are used to uniquely identify, describe and manage software components.

* Concise Tag List (CoTL) tags ({{sec-cotl}}) contain the list of CoMID and CoSWID tags that the Verifier should consider as "active" at a certain point in time.

The collection of tags is extensible so that future specifications can add new types of tags.
CoRIM allows for new types of tags to be added in future specifications.
For example, Concise Trust Anchor Stores (CoTS) ({{-ta-store}}) is currently being defined as a standard CoRIM extension.

Each CoRIM contains a unique identifier to distinguish a CoRIM from other CoRIMs.
Expand Down

0 comments on commit 5ac4b44

Please sign in to comment.