| Internet-Draft | ADEM over DNS | January 2026 |
| Linker | Expires 19 July 2026 | [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://adem-wg.github.io/adem-dns-spec/draft-linker-diem-adem-dns.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-linker-diem-adem-dns/.¶
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/adem-wg/adem-dns-spec.¶
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 19 July 2026.¶
Copyright (c) 2026 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.¶
The ADEM Core Specification specifies how a set of tokens, encoded as JSON Web Signatures (JWSs) [RFC7515], can be used as a digital emblem to signal that digital assets enjoy specific protections under International Humanitarian Law (IHL). This document describes a DNS-based distribution and discovery for ADEM tokens.¶
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.¶
Given a set of tokens containing exactly one emblem and zero or more associated endorsements, issuers can distribute this set via DNS TXT records [RFC1035], as follows.¶
For each such set, issuers MAY choose a unique identifier string. If multiple sets of tokens are associated with a given domain name, issuers SHOULD choose such a string.¶
Each token is distributed as its own TXT record, which includes a key and a value. The value encodes the token in JWT compact serialization.¶
Each record's key MUST be formatted as:¶
key := "adem" [ "-" identifier ] identifier := CHARACTER-NO-HYPEN+ record := key "=" value¶
CHARACTER-NO-HYPEN is any printable ASCII character as specified in [RFC0020] except for "-".
If present, identifier MUST coincide with the string identifying the token's set.¶
TODO Security¶
This document has no IANA actions.¶
TODO acknowledge.¶