]>

linkerfelix@gmail.com

Applications and Real-Time Digital Emblems next generation unicorn sparkling distributed ledger TODO Abstract About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Digital Emblems Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction The ADEM Core Specification specifies how a set of tokens, encoded as JSON Web Signatures (JWSs) , 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.

Conventions and Definitions 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 when, and only when, they appear in all capitals, as shown here.

DNS Distribution Given a set of tokens containing exactly one emblem and zero or more associated endorsements, issuers can distribute this set and any public keys needed to validate it via DNS TXT records , 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 or public key is distributed as its own TXT record, which includes a key and a value. For token records, the value encodes the token in JWT compact serialization. For public key records, the value encodes the public key as a JSON Web Key (JWK) . Each record's key MUST be formatted as: CHARACTER-NO-HYPEN is any printable ASCII character as specified in except for "-". If present, identifier MUST coincide with the string identifying the token set.

Security Considerations TODO Security

IANA Considerations This document has no IANA actions.

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. Informative References JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification. A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. This specification also defines a JWK Set JSON data structure that represents a set of JWKs. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and IANA registries established by that specification.

Acknowledgments TODO acknowledge.