(registered 2022-10-19, last updated 2024-02-08) Media type name: application Media subtype name: vnd.ipld.dag-cbor Required parameters: N/A Optional parameters: N/A Encoding considerations: binary Security considerations: The media type inherits the security considerations for (see Section 10 of RFC 8949) and introduces additional limitations listed at . DAG-CBOR requires that there exist a single, canonical way of encoding any given set of data, and that encoded forms contain no superfluous data that may be ignored or lost in a round-trip decode/encode. When used in IPFS context, all processors should rigorously verify data integrity based on CID links (CBOR Tag 42). Invalid links must be discarded. Interoperability considerations: DAG-CBOR is a strict subset of defined by RFC 8949. Every can be parsed or interpreted as a valid , but the opposite may not be true. CBOR tag 42 (registered at https://www.iana.org/assignments/cbor-tags) can be used for indicating CID links to other DAG-CBOR documents, or arbitrary IPFS content. Published specification: Applications which use this media: DAG-CBOR allows for creating deterministic CBOR documents that produce a stable hash, which in turns allows for use in content-addressed contexts, such as Directed Acyclic Graphs (DAGs) and Merkle tree-like structures based on DAGs. These properties are used extensively in: IPLD IPFS Fragment identifier considerations: N/A Restrictions on usage: N/A Additional information: 1. Deprecated alias names for this type: N/A 2. Magic number(s): N/A 3. File extension(s): cbor 4. Macintosh file type code: N/A 5. Object Identifiers: N/A Person to contact for further information: 1. Name: Marcin Rataj 2. Email: lidel&ipshipyard.com Intended usage: COMMON Author/Change controller: IPFS Project