RFC 9393: Concise Software Identification Tags
In plain English — editorial summary, not part of the RFC
ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an extensible XML-based structure to identify and describe individual software components, patches, and installation bundles. SWID tag representations can be too large for devices with network and storage constraints. This document defines a concise representation of SWID tags: Concise SWID (CoSWID) tags. CoSWID supports a set of semantics and features that are similar to those for SWID tags, as well as new semantics that allow CoSWIDs to describe additional types of information, all in a more memory-efficient format.
Document record
- Document ID
- RFC9393
- Published
- June 2023
- Authors
- H. Birkholz; J. Fitzgerald-McKay; C. Schmidt; D. Waltermire
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 61
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9395Deprecation of the Internet Key Exchange Version 1 (IKEv1) Protocol and Obsoleted AlgorithmsCurrent
April 2023
- RFC 9396OAuth 2.0 Rich Authorization RequestsCurrent
May 2023
- RFC 9397Trusted Execution Environment Provisioning (TEEP) ArchitectureCurrent
July 2023
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
- RFC 9387Use Cases for DDoS Open Threat Signaling (DOTS) TelemetryCurrent
April 2023
- RFC 9370Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2023
- RFC 9420The Messaging Layer Security (MLS) ProtocolCurrent
July 2023
- RFC 9362Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block TransmissionCurrent
February 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?