| Internet-Draft | DIEM Use Cases and Requirements | June 2025 |
| Linker | Expires 25 December 2025 | [Page] |
TODO Abstract¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://felixlinker.github.io/diem-requirements/draft-linker-diem-requirements.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-linker-diem-requirements/.¶
Discussion of this document takes place on the Digital Emblems Working Group mailing list (mailto:diem@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/diem. Subscribe at https://www.ietf.org/mailman/listinfo/diem/.¶
Source for this draft and an issue tracker can be found at https://github.com/felixlinker/diem-requirements.¶
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 December 2025.¶
Copyright (c) 2025 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.¶
TODO Introduction¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Validators MUST be able to verify that an emblem was issued for the respective bearer, issued by the claimed issuer (where applicable), and that none of its associated data was changed.¶
Emblem issuance and authorization of issuers (where applicable) MUST be attributable to issuers and authorizing parties. Authorizing parties and emblem issuers MUST NOT be able to repudiate that they issued an emblem or authorization.¶
Emblems and authorizations (where applicable) MUST be revokable within reasonable windows of time. Depending on the design, it may suffice to rely on expiration of short-lived emblems and authorization effectively as a revocation mechanism.¶
Emblem issuers MUST NOT be able to detect whether someone is requesting or validating emblems issued by them.¶
An emblem MUST be capable of carrying a visual representation of the physical emblem it represents.¶
An emblem MUST carry an unambiguous indication of the international law or laws conferring the semantics of the emblem.¶
An emblem MUST be presentable using an in-band, proximity-based protocol such as a QR code or RFID.¶
An emblem MUST be possible to associate with physical assets, e.g., buildings, vehicles, or containers.¶
An emblem MUST be possible to associate with a range or specific quantity of associated, physical assets.¶
An emblem MUST be possible to associate with a person or group of people.¶
TODO Security¶
This document has no IANA actions.¶
TODO acknowledge.¶