draft-ietf-sacm-coswid-12.txt   draft-ietf-sacm-coswid-13.txt 
SACM Working Group H. Birkholz SACM Working Group H. Birkholz
Internet-Draft Fraunhofer SIT Internet-Draft Fraunhofer SIT
Intended status: Standards Track J. Fitzgerald-McKay Intended status: Standards Track J. Fitzgerald-McKay
Expires: January 26, 2020 Department of Defense Expires: May 20, 2020 Department of Defense
C. Schmidt C. Schmidt
The MITRE Corporation The MITRE Corporation
D. Waltermire D. Waltermire
NIST NIST
July 25, 2019 November 17, 2019
Concise Software Identification Tags Concise Software Identification Tags
draft-ietf-sacm-coswid-12 draft-ietf-sacm-coswid-13
Abstract Abstract
ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an
extensible XML-based structure to identify and describe individual extensible XML-based structure to identify and describe individual
software components, patches, and installation bundles. SWID tag software components, patches, and installation bundles. SWID tag
representations can be too large for devices with network and storage representations can be too large for devices with network and storage
constraints. This document defines a concise representation of SWID constraints. This document defines a concise representation of SWID
tags: Concise SWID (CoSWID) tags. CoSWID supports the same features tags: Concise SWID (CoSWID) tags. CoSWID supports the same features
as SWID tags, as well as additional semantics that allow CoSWIDs to as SWID tags, as well as additional semantics that allow CoSWIDs to
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 26, 2020. This Internet-Draft will expire on May 20, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 13 skipping to change at page 3, line 13
5.2.7. SWID/CoSWID Link Relationship Value Registry . . . . 51 5.2.7. SWID/CoSWID Link Relationship Value Registry . . . . 51
5.2.8. SWID/CoSWID Link Use Value Registry . . . . . . . . . 53 5.2.8. SWID/CoSWID Link Use Value Registry . . . . . . . . . 53
5.3. swid+cbor Media Type Registration . . . . . . . . . . . . 54 5.3. swid+cbor Media Type Registration . . . . . . . . . . . . 54
5.4. CoAP Content-Format Registration . . . . . . . . . . . . 55 5.4. CoAP Content-Format Registration . . . . . . . . . . . . 55
5.5. CBOR Tag Registration . . . . . . . . . . . . . . . . . . 55 5.5. CBOR Tag Registration . . . . . . . . . . . . . . . . . . 55
5.6. URI Scheme Registrations . . . . . . . . . . . . . . . . 55 5.6. URI Scheme Registrations . . . . . . . . . . . . . . . . 55
5.6.1. "swid" URI Scheme Registration . . . . . . . . . . . 56 5.6.1. "swid" URI Scheme Registration . . . . . . . . . . . 56
5.6.2. "swidpath" URI Scheme Registration . . . . . . . . . 56 5.6.2. "swidpath" URI Scheme Registration . . . . . . . . . 56
5.7. CoSWID Model for use in SWIMA Registration . . . . . . . 57 5.7. CoSWID Model for use in SWIMA Registration . . . . . . . 57
6. Security Considerations . . . . . . . . . . . . . . . . . . . 58 6. Security Considerations . . . . . . . . . . . . . . . . . . . 58
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 59
8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 60 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 60
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 64 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 64
9.1. Normative References . . . . . . . . . . . . . . . . . . 64 9.1. Normative References . . . . . . . . . . . . . . . . . . 64
9.2. Informative References . . . . . . . . . . . . . . . . . 66 9.2. Informative References . . . . . . . . . . . . . . . . . 66
Appendix A. Signed Concise SWID Tags using COSE . . . . . . . . 67 Appendix A. Signed Concise SWID Tags using COSE . . . . . . . . 67
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 68
1. Introduction 1. Introduction
SWID tags, as defined in ISO-19770-2:2015 [SWID], provide a SWID tags, as defined in ISO-19770-2:2015 [SWID], provide a
skipping to change at page 6, line 17 skipping to change at page 6, line 17
* Software Installation. A primary tag will be installed with * Software Installation. A primary tag will be installed with
the software component (or subsequently created) to uniquely the software component (or subsequently created) to uniquely
identify and describe the software component. Supplemental identify and describe the software component. Supplemental
tags are created to augment primary tags with additional site- tags are created to augment primary tags with additional site-
specific or extended information. While not illustrated in the specific or extended information. While not illustrated in the
figure, patch tags can also be installed during software figure, patch tags can also be installed during software
installation to provide information about software fixes installation to provide information about software fixes
deployed along with the base software installation. deployed along with the base software installation.
* Software Patching. When a new patch is applied to the software * Software Patching. A new patch tag is provided, when a patch
component a new patch tag is provided, supplying details about is applied to the software component, supplying details about
the patch and its dependencies. While not illustrated in the the patch and its dependencies. While not illustrated in the
figure, a corpus tag can also provide information about the figure, a corpus tag can also provide information about the
patch installer and patching dependencies that need to be patch installer and patching dependencies that need to be
installed before the patch. installed before the patch.
* Software Upgrading. As a software component is upgraded to a * Software Upgrading. As a software component is upgraded to a
new version, new primary and supplemental tags replace existing new version, new primary and supplemental tags replace existing
tags, enabling timely and accurate tracking of updates to tags, enabling timely and accurate tracking of updates to
software inventory. While not illustrated in the figure, a software inventory. While not illustrated in the figure, a
corpus tag can also provide information about the upgrade corpus tag can also provide information about the upgrade
skipping to change at page 8, line 46 skipping to change at page 8, line 46
The following subsections describe the different parts of the CoSWID The following subsections describe the different parts of the CoSWID
model. model.
2.1. Character Encoding 2.1. Character Encoding
The CDDL "text" type is represented in CBOR as a major type 3, which The CDDL "text" type is represented in CBOR as a major type 3, which
represents "a string of Unicode characters that [are] encoded as represents "a string of Unicode characters that [are] encoded as
UTF-8 [RFC3629]" (see [RFC7049] section 2.1). Thus both SWID and UTF-8 [RFC3629]" (see [RFC7049] section 2.1). Thus both SWID and
CoSWID use UTF-8 for the encoding of characters in text strings. CoSWID use UTF-8 for the encoding of characters in text strings.
To ensure that UTF-8 character strings are able to be encodes/decoded To ensure that UTF-8 character strings are able to be encoded/decoded
and exchanged interoperably, text strings in CoSWID MUST be encoded and exchanged interoperably, text strings in CoSWID MUST be encoded
consistent with the Net-Unicode definition defined in [RFC5198]. consistent with the Net-Unicode definition defined in [RFC5198].
All names registered with IANA according to requirements in section All names registered with IANA according to requirements in section
Section 5.2 also need to be valid according to the XML Schema NMToken Section 5.2 also need to be valid according to the XML Schema NMToken
data type (see [W3C.REC-xmlschema-2-20041028] section 3.3.4) to data type (see [W3C.REC-xmlschema-2-20041028] section 3.3.4) to
ensure compatibility with the SWID specification where these names ensure compatibility with the SWID specification where these names
are used. are used.
2.2. Concise SWID Extensions 2.2. Concise SWID Extensions
skipping to change at page 13, line 15 skipping to change at page 13, line 15
o global-attributes: A list of items including an optional language o global-attributes: A list of items including an optional language
definition to support the processing of text-string values and an definition to support the processing of text-string values and an
unbounded set of any-attribute items. Described in Section 2.5. unbounded set of any-attribute items. Described in Section 2.5.
o tag-id (index 0): A 16 byte binary string or textual identifier o tag-id (index 0): A 16 byte binary string or textual identifier
uniquely referencing a software component. The tag identifier uniquely referencing a software component. The tag identifier
MUST be globally unique. If represented as a 16 byte binary MUST be globally unique. If represented as a 16 byte binary
string, the identifier MUST be a valid universally unique string, the identifier MUST be a valid universally unique
identifier as defined by [RFC4122]. There are no strict identifier as defined by [RFC4122]. There are no strict
guidelines on how this identifier is structured, but examples guidelines on how this identifier is structured, but examples
include a 16 byte GUID (e.g. class 4 UUID) [RFC4122], or a text include a 16 byte GUID (e.g. class 4 UUID) [RFC4122], or a text
string appended to a DNS domain name to ensure uniqueness across string appended to a DNS domain name to ensure uniqueness across
organizations. organizations.
o tag-version (index 12): An integer value that indicate the o tag-version (index 12): An integer value that indicate the
specific release revision of the tag. Typically, the initial specific release revision of the tag. Typically, the initial
value of this field is set to 0 and the value is monotonically value of this field is set to 0 and the value is monotonically
increased for subsequent tags produced for the same software increased for subsequent tags produced for the same software
component release. This value allows a CoSWID tag producer to component release. This value allows a CoSWID tag producer to
correct an incorrect tag previously released without indicating a correct an incorrect tag previously released without indicating a
change to the underlying software component the tag represents. change to the underlying software component the tag represents.
skipping to change at page 15, line 10 skipping to change at page 15, line 10
communities. Described in Section 2.8. communities. Described in Section 2.8.
o entity (index 2): Provides information about one or more o entity (index 2): Provides information about one or more
organizations responsible for producing the CoSWID tag, and organizations responsible for producing the CoSWID tag, and
producing or releasing the software component referenced by this producing or releasing the software component referenced by this
CoSWID tag. Described in Section 2.6. CoSWID tag. Described in Section 2.6.
o link (index 4): Provides a means to establish relationship arcs o link (index 4): Provides a means to establish relationship arcs
between the tag and another items. A given link can be used to between the tag and another items. A given link can be used to
establish the relationship between tags or to reference another establish the relationship between tags or to reference another
resource that is related to the CoSWID tag, e.g. vulnerability resource that is related to the CoSWID tag, e.g. vulnerability
database association, ROLIE feed [RFC8322], MUD resource database association, ROLIE feed [RFC8322], MUD resource
[RFC8520], software download location, etc). This is modeled [RFC8520], software download location, etc). This is modeled
after the HTML "link" element. Described in Section 2.7. after the HTML "link" element. Described in Section 2.7.
o payload (index 6): This item represents a collection of software o payload (index 6): This item represents a collection of software
artifacts (described by child items) that compose the target artifacts (described by child items) that compose the target
software. For example, these artifacts could be the files software. For example, these artifacts could be the files
included with an installer for a corpus tag or installed on an included with an installer for a corpus tag or installed on an
endpoint when the software component is installed for a primary or endpoint when the software component is installed for a primary or
patch tag. The artifacts listed in a payload may be a superset of patch tag. The artifacts listed in a payload may be a superset of
skipping to change at page 15, line 47 skipping to change at page 15, line 47
Section 2.2. Section 2.2.
2.4. concise-swid-tag Co-constraints 2.4. concise-swid-tag Co-constraints
The following co-constraints apply to the information provided in the The following co-constraints apply to the information provided in the
concise-swid-tag group. concise-swid-tag group.
o The patch and supplemental items MUST NOT both be set to "true". o The patch and supplemental items MUST NOT both be set to "true".
o If the patch item is set to "true", the tag SHOULD contain at o If the patch item is set to "true", the tag SHOULD contain at
least one link item (see section Section 2.7) with both the least one link item (see section Section 2.7) with both the rel
rel(ation) item value of "patches" and an href item specifying an item value of "patches" and an href item specifying an association
association with the software that was patched. with the software that was patched.
o If the supplemental item is set to "true", the tag SHOULD contain o If the supplemental item is set to "true", the tag SHOULD contain
at least one link item with both the rel(ation) item value of at least one link item with both the rel item value of
"supplements" and an href item specifying an association with the "supplemental" and an href item specifying an association with the
software that is supplemented. software that is supplemented.
o If all of the corpus, patch, and supplemental items are "false", o If all of the corpus, patch, and supplemental items are "false",
or if the corpus item is set to "true", then a software-version or if the corpus item is set to "true", then a software-version
item MUST be included with a value set to the version of the item MUST be included with a value set to the version of the
software component. This ensures that primary and corpus tags software component. This ensures that primary and corpus tags
have an identifiable software version. have an identifiable software version.
2.5. The global-attributes Group 2.5. The global-attributes Group
skipping to change at page 36, line 23 skipping to change at page 36, line 23
ancestor=1 ancestor=1
component=2 component=2
feature=3 feature=3
installationmedia=4 installationmedia=4
packageinstaller=5 packageinstaller=5
parent=6 parent=6
patches=7 patches=7
requires=8 requires=8
see-also=9 see-also=9
supersedes=10 supersedes=10
supplemental=11 ; supplemental=11 ; this is already defined earlier
; "use" integer indexes ; "use" integer indexes
optional=1 optional=1
required=2 required=2
recommended=3 recommended=3
3. Determining the Type of CoSWID 3. Determining the Type of CoSWID
The operational model for SWID and CoSWID tags was introduced in The operational model for SWID and CoSWID tags was introduced in
Section 1.1, which described four different CoSWID tag types. The Section 1.1, which described four different CoSWID tag types. The
skipping to change at page 43, line 14 skipping to change at page 43, line 14
The values above are registered in the IANA "SWID/CoSWID Link Use The values above are registered in the IANA "SWID/CoSWID Link Use
Value" registry defined in section Section 5.2.8. Additional values Value" registry defined in section Section 5.2.8. Additional values
will likely be registered over time. Additionally, the index values will likely be registered over time. Additionally, the index values
128 through 255 and the name prefix "x_" have been reserved for 128 through 255 and the name prefix "x_" have been reserved for
private use. private use.
5. IANA Considerations 5. IANA Considerations
This document has a number of IANA considerations, as described in This document has a number of IANA considerations, as described in
the following subsections. the following subsections. In summary, 6 new registries are
established with this request, with initial entries provided for each
registry. New values for 5 other registries are also requested.
5.1. CoSWID Items Registry 5.1. CoSWID Items Registry
This document uses integer values as index values in CBOR maps. This registry uses integer values as index values in CBOR maps.
This document defines a new registry titled "CoSWID Items". Future This document defines a new registry titled "CoSWID Items". Future
registrations for this registry are to be made based on [RFC8126] as registrations for this registry are to be made based on [RFC8126] as
follows: follows:
+------------------+-------------------------+ +------------------+-------------------------+
| Range | Registration Procedures | | Range | Registration Procedures |
+------------------+-------------------------+ +------------------+-------------------------+
| 0-32767 | Standards Action | | 0-32767 | Standards Action |
| | | | | |
skipping to change at page 46, line 47 skipping to change at page 46, line 49
5.2.2. Private Use of Index and Name Values 5.2.2. Private Use of Index and Name Values
The integer-based index values in the private use range (-1 to -256) The integer-based index values in the private use range (-1 to -256)
are intended for testing purposes and closed environments; values in are intended for testing purposes and closed environments; values in
other ranges SHOULD NOT be assigned for testing. other ranges SHOULD NOT be assigned for testing.
For names that correspond to private use index values, an For names that correspond to private use index values, an
Internationalized Domain Name prefix MUST be used to prevent name Internationalized Domain Name prefix MUST be used to prevent name
conflicts using the form: conflicts using the form:
"domain.prefix-name " " domain.prefix-name "
Where "domain.prefix" MUST be a valid Internationalized Domain Name Where "domain.prefix" MUST be a valid Internationalized Domain Name
as defined by [RFC5892], and "name" MUST be a unique name within the as defined by [RFC5892], and "name" MUST be a unique name within the
namespace defined by the "domain.prefix". Use of a prefix in this namespace defined by the "domain.prefix". Use of a prefix in this
way allows for a name to be used initially in the private use range, way allows for a name to be used initially in the private use range,
and to be registered at a future point in time. This is consistent and to be registered at a future point in time. This is consistent
with the guidance in [BCP178]. with the guidance in [BCP178].
5.2.3. Expert Review Guidelines 5.2.3. Expert Review Guidelines
Designated experts MUST ensure that new registration requests meet Designated experts MUST ensure that new registration requests meet
skipping to change at page 47, line 46 skipping to change at page 47, line 49
NMTOKEN data type (see [W3C.REC-xmlschema-2-20041028] section NMTOKEN data type (see [W3C.REC-xmlschema-2-20041028] section
3.3.4). This ensures that registered names are compatible with 3.3.4). This ensures that registered names are compatible with
the SWID format [SWID] where they are used. the SWID format [SWID] where they are used.
o Registration of vanity names SHOULD be discouraged. The o Registration of vanity names SHOULD be discouraged. The
requesting specification MUST provide a description of how a requesting specification MUST provide a description of how a
requested name will allow for use by multiple stakeholders. requested name will allow for use by multiple stakeholders.
5.2.4. SWID/CoSWID Version Scheme Value Registry 5.2.4. SWID/CoSWID Version Scheme Value Registry
This document defines a new a new registry titled "SWID/CoSWID This document establishes a new registry titled "SWID/CoSWID Version
Version Scheme Values". This registry provides index values for use Scheme Values". This registry provides index values for use as
as version-scheme item values in this document and version scheme version-scheme item values in this document and version scheme names
names for use in [SWID]. for use in [SWID].
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid] location: https://www.iana.org/assignments/swid]
This registry uses the registration proceedures defined in This registry uses the registration proceedures defined in
Section 5.2.1 with the following associated ranges: Section 5.2.1 with the following associated ranges:
+-------------+-------------------------+ +-------------+-------------------------+
| Range | Registration Procedures | | Range | Registration Procedures |
+-------------+-------------------------+ +-------------+-------------------------+
skipping to change at page 49, line 14 skipping to change at page 49, line 17
Designated experts MUST also ensure that newly requested entries Designated experts MUST also ensure that newly requested entries
define a value space for the corresponding version item that is define a value space for the corresponding version item that is
unique from other previously registered entries. Note: The inital unique from other previously registered entries. Note: The inital
registrations violate this requirement, but are included for registrations violate this requirement, but are included for
backwards compatibility with [SWID]. Guidelines on how to deconflict backwards compatibility with [SWID]. Guidelines on how to deconflict
these value spaces are defined in section Section 4.1. these value spaces are defined in section Section 4.1.
5.2.5. SWID/CoSWID Entity Role Value Registry 5.2.5. SWID/CoSWID Entity Role Value Registry
This document defines a new a new registry titled "SWID/CoSWID Entity This document establishes a new registry titled "SWID/CoSWID Entity
Role Values". This registry provides index values for use as entity- Role Values". This registry provides index values for use as entity-
entry role item values in this document and entity role names for use entry role item values in this document and entity role names for use
in [SWID]. in [SWID].
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid] location: https://www.iana.org/assignments/swid]
This registry uses the registration proceedures defined in This registry uses the registration proceedures defined in
Section 5.2.1 with the following associated ranges: Section 5.2.1 with the following associated ranges:
skipping to change at page 50, line 30 skipping to change at page 50, line 30
| 6-255 | Unassigned | | | 6-255 | Unassigned | |
+-------+-----------------+-----------------+ +-------+-----------------+-----------------+
Table 13: CoSWID Entity Role Inital Registrations Table 13: CoSWID Entity Role Inital Registrations
Registrations MUST conform to the expert review guidlines defined in Registrations MUST conform to the expert review guidlines defined in
Section 5.2.3. Section 5.2.3.
5.2.6. SWID/CoSWID Link Ownership Value Registry 5.2.6. SWID/CoSWID Link Ownership Value Registry
This document defines a new a new registry titled "SWID/CoSWID Link This document establishes a new registry titled "SWID/CoSWID Link
Ownership Values". This registry provides index values for use as Ownership Values". This registry provides index values for use as
link-entry ownership item values in this document and link ownership link-entry ownership item values in this document and link ownership
names for use in [SWID]. names for use in [SWID].
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid] location: https://www.iana.org/assignments/swid]
This registry uses the registration proceedures defined in This registry uses the registration proceedures defined in
Section 5.2.1 with the following associated ranges: Section 5.2.1 with the following associated ranges:
skipping to change at page 51, line 30 skipping to change at page 51, line 30
| 4-255 | Unassigned | | | 4-255 | Unassigned | |
+-------+---------------------+-----------------+ +-------+---------------------+-----------------+
Table 15: CoSWID Link Ownership Inital Registrations Table 15: CoSWID Link Ownership Inital Registrations
Registrations MUST conform to the expert review guidlines defined in Registrations MUST conform to the expert review guidlines defined in
Section 5.2.3. Section 5.2.3.
5.2.7. SWID/CoSWID Link Relationship Value Registry 5.2.7. SWID/CoSWID Link Relationship Value Registry
This document defines a new a new registry titled "SWID/CoSWID Link This document establishes a new registry titled "SWID/CoSWID Link
Relationship Values". This registry provides index values for use as Relationship Values". This registry provides index values for use as
link-entry rel item values in this document and link ownership names link-entry rel item values in this document and link ownership names
for use in [SWID]. for use in [SWID].
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid] location: https://www.iana.org/assignments/swid]
This registry uses the registration proceedures defined in This registry uses the registration proceedures defined in
Section 5.2.1 with the following associated ranges: Section 5.2.1 with the following associated ranges:
skipping to change at page 53, line 7 skipping to change at page 53, line 7
Designated experts MUST also ensure that a newly requested entry Designated experts MUST also ensure that a newly requested entry
documents the URI schemes allowed to be used in an href associated documents the URI schemes allowed to be used in an href associated
with the link relationship and the expected resolution behavior of with the link relationship and the expected resolution behavior of
these URI schemes. This will help to ensure that SWID/CoSWID these URI schemes. This will help to ensure that SWID/CoSWID
applications are able to interoperate when resolving resources applications are able to interoperate when resolving resources
referenced by a link of a given type. referenced by a link of a given type.
5.2.8. SWID/CoSWID Link Use Value Registry 5.2.8. SWID/CoSWID Link Use Value Registry
This document defines a new a new registry titled "SWID/CoSWID Link This document establishes a new registry titled "SWID/CoSWID Link Use
Use Values". This registry provides index values for use as link- Values". This registry provides index values for use as link-entry
entry use item values in this document and link use names for use in use item values in this document and link use names for use in
[SWID]. [SWID].
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid] location: https://www.iana.org/assignments/swid]
This registry uses the registration proceedures defined in This registry uses the registration proceedures defined in
Section 5.2.1 with the following associated ranges: Section 5.2.1 with the following associated ranges:
+---------+-------------------------+ +---------+-------------------------+
| Range | Registration Procedures | | Range | Registration Procedures |
skipping to change at page 56, line 7 skipping to change at page 56, line 7
The ISO 19770-2:2015 SWID specification describes use of the "swid" The ISO 19770-2:2015 SWID specification describes use of the "swid"
and "swidpath" URI schemes, which are currently in use in and "swidpath" URI schemes, which are currently in use in
implementations. This document continues this use for CoSWID. The implementations. This document continues this use for CoSWID. The
following subsections provide registrations for these schemes in to following subsections provide registrations for these schemes in to
ensure that a permanent registration exists for these schemes that is ensure that a permanent registration exists for these schemes that is
suitable for use in the SWID and CoSWID specifications. suitable for use in the SWID and CoSWID specifications.
5.6.1. "swid" URI Scheme Registration 5.6.1. "swid" URI Scheme Registration
SWID or CoSWID by the referenced tag's tag-id. This URI needs to be
resolved in the context of the endpoint by software that can lookup
other SWID or CoSWID tags. For example, "swid:2df9de35-0aff-
4a86-ace6-f7dddd1ade4c" references the tag with the tag-id value
"2df9de35-0aff-4a86-ace6-f7dddd1ade4c".
There is a need for a scheme name that can be used in URIs that point There is a need for a scheme name that can be used in URIs that point
to a specific SWID/CoSWID tag by that tag's tag-id, such as the use to a specific SWID/CoSWID tag by that tag's tag-id, such as the use
of the link entry as described in section Section 2.7) of this of the link entry as described in section Section 2.7) of this
document. Since this scheme is used in a standards track document document. Since this scheme is used in a standards track document
and an ISO standard, this scheme needs to be used without fear of and an ISO standard, this scheme needs to be used without fear of
conflicts with current or future actual schemes. The scheme "swid" conflicts with current or future actual schemes. The scheme "swid"
is hereby registered as a 'permanent' scheme for that purpose. is hereby registered as a 'permanent' scheme for that purpose.
The "swid" scheme is specified as follows: The "swid" scheme is specified as follows:
skipping to change at page 57, line 20 skipping to change at page 57, line 13
2.1. 2.1.
Scheme semantics: URIs in the "swidpath" scheme are to be used Scheme semantics: URIs in the "swidpath" scheme are to be used
specify the data that must be found in a given SWID/CoSWID tag for specify the data that must be found in a given SWID/CoSWID tag for
that tag to be considered a matching tag to be included in the that tag to be considered a matching tag to be included in the
identified tag collection. Tags to be evaluated include all tags in identified tag collection. Tags to be evaluated include all tags in
the context of where the tag is referenced from. For example, when a the context of where the tag is referenced from. For example, when a
tag is installed on a given device, that tag can reference related tag is installed on a given device, that tag can reference related
tags on the same device using this URI scheme. A tag is matching if tags on the same device using this URI scheme. A tag is matching if
the XPath evaluation result value has an effective boolean value of the XPath evaluation result value has an effective boolean value of
"true" according to [W3C.REC-xpath20-20101214] section 2.4.3. rence "true" according to [W3C.REC-xpath20-20101214] section 2.4.3. rence
related tags on the same device using this URI scheme. related tags on the same device using this URI scheme.
Encoding considerations: See Section 2.5 of [RFC3986] for guidelines. Encoding considerations: See Section 2.5 of [RFC3986] for guidelines.
Interoperability considerations: None. Interoperability considerations: None.
Security considerations: None. Security considerations: None.
5.7. CoSWID Model for use in SWIMA Registration 5.7. CoSWID Model for use in SWIMA Registration
skipping to change at page 60, line 17 skipping to change at page 60, line 9
This document draws heavily on the concepts defined in the ISO/IEC This document draws heavily on the concepts defined in the ISO/IEC
19770-2:2015 specification. The authors of this document are 19770-2:2015 specification. The authors of this document are
grateful for the prior work of the 19770-2 contributors. grateful for the prior work of the 19770-2 contributors.
We are also grateful to the careful reviews provided by ... We are also grateful to the careful reviews provided by ...
8. Change Log 8. Change Log
[THIS SECTION TO BE REMOVED BY THE RFC EDITOR.] [THIS SECTION TO BE REMOVED BY THE RFC EDITOR.]
Changes in version 12:
o Addressed a bunch of minor editorial issues based on WGLC
feedback.
o Added text about the use of UTF-8 in CoSWID.
o Adjusted tag-id to allow for a UUID to be provided as a bstr.
o Cleaned up descriptions of index ranges throughout the document,
removing discussion of 8 bit, 16 bit, etc.
o Adjusted discussion of private use ranges to use negative integer
values and to be more clear throughout the document.
o Added discussion around resolving overlapping value spaces for
version schemes.
o Added a set of expert review guidelines for new IANA registries
created by this document.
o Added new registrations for the "swid" and "swidpath" URI schemes,
and for using CoSWID with SWIMA.
Changes from version 03 to version 11: Changes from version 03 to version 11:
o Reduced representation complexity of the media-entry type and o Reduced representation complexity of the media-entry type and
removed the section describing the older data structure. removed the section describing the older data structure.
o Added more signature schemes from COSE o Added more signature schemes from COSE
o Included a minimal required set of normative language o Included a minimal required set of normative language
o Reordering of attribute name to integer label by priority o Reordering of attribute name to integer label by priority
skipping to change at page 62, line 20 skipping to change at page 62, line 39
19770-2:2015 19770-2:2015
o Added value registry request o Added value registry request
o Added media type registration request o Added media type registration request
o Added content format registration request o Added content format registration request
o Added CBOR tag registration request o Added CBOR tag registration request
o Removed RIM appedix to be addressed in complementary draft o Removed RIM appendix to be addressed in complementary draft
o Removed CWT appendix o Removed CWT appendix
o Flagged firmware resource colletion appendix for revision o Flagged firmware resource collection appendix for revision
o Made use of terminology more consistent o Made use of terminology more consistent
o Better defined use of extension points in the CDDL o Better defined use of extension points in the CDDL
o Added definitions for indexed values o Added definitions for indexed values
o Added IANA registry for Link use indexed values o Added IANA registry for Link use indexed values
Changes from version 05 to version 06: Changes from version 05 to version 06:
o Improved quantities o Improved quantities
o Included proposals for implicet enumerations that were NMTOKENS o Included proposals for implicit enumerations that were NMTOKENS
o Added extension points o Added extension points
o Improved exemplary firmware-resource extension o Improved exemplary firmware-resource extension
Changes from version 04 to version 05: Changes from version 04 to version 05:
o Clarified language around SWID and CoSWID to make more consistent o Clarified language around SWID and CoSWID to make more consistent
use of these terms. use of these terms.
skipping to change at page 66, line 8 skipping to change at page 66, line 25
[SEMVER] Preston-Werner, T., "Semantic Versioning 2.0.0", n.d., [SEMVER] Preston-Werner, T., "Semantic Versioning 2.0.0", n.d.,
<https://semver.org/spec/v2.0.0.html>. <https://semver.org/spec/v2.0.0.html>.
[SWID] "Information technology - Software asset management - Part [SWID] "Information technology - Software asset management - Part
2: Software identification tag", ISO/IEC 19770-2:2015, 2: Software identification tag", ISO/IEC 19770-2:2015,
October 2015. October 2015.
[W3C.REC-css3-mediaqueries-20120619] [W3C.REC-css3-mediaqueries-20120619]
Rivoal, F., "Media Queries", World Wide Web Consortium Rivoal, F., "Media Queries", World Wide Web Consortium
Recommendation REC-css3-mediaqueries-20120619, June 2012, Recommendation REC-css3-mediaqueries-20120619, June 2012,
<http://www.w3.org/TR/2012/ <http://www.w3.org/TR/2012/REC-css3-mediaqueries-
REC-css3-mediaqueries-20120619>. 20120619>.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium Recommendation Second Edition", World Wide Web Consortium Recommendation
REC-xmlschema-2-20041028, October 2004, REC-xmlschema-2-20041028, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
[W3C.REC-xpath20-20101214] [W3C.REC-xpath20-20101214]
Berglund, A., Boag, S., Chamberlin, D., Fernandez, M., Berglund, A., Boag, S., Chamberlin, D., Fernandez, M.,
Kay, M., Robie, J., and J. Simeon, "XML Path Language Kay, M., Robie, J., and J. Simeon, "XML Path Language
skipping to change at page 66, line 36 skipping to change at page 67, line 8
9.2. Informative References 9.2. Informative References
[CamelCase] [CamelCase]
"UpperCamelCase", August 2014, "UpperCamelCase", August 2014,
<http://wiki.c2.com/?CamelCase>. <http://wiki.c2.com/?CamelCase>.
[I-D.birkholz-rats-tuda] [I-D.birkholz-rats-tuda]
Fuchs, A., Birkholz, H., McDonald, I., and C. Bormann, Fuchs, A., Birkholz, H., McDonald, I., and C. Bormann,
"Time-Based Uni-Directional Attestation", draft-birkholz- "Time-Based Uni-Directional Attestation", draft-birkholz-
rats-tuda-00 (work in progress), March 2019. rats-tuda-01 (work in progress), September 2019.
[KebabCase] [KebabCase]
"KebabCase", December 2014, "KebabCase", December 2014,
<http://wiki.c2.com/?KebabCase>. <http://wiki.c2.com/?KebabCase>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005, DOI 10.17487/RFC4122, July 2005,
<https://www.rfc-editor.org/info/rfc4122>. <https://www.rfc-editor.org/info/rfc4122>.
 End of changes. 29 change blocks. 
44 lines changed or deleted 62 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/