File formats: **Also available: **XML file for editing **Status:**PROPOSED STANDARD **Authors:**A. Wiethuechter, Ed. J. Reid Stream:IETF Source:drip (int)

Cite this RFC: TXT | XML | BibTeX

DOI: https://doi.org/10.17487/RFC9886

Discuss this RFC: Send questions or comments to the mailing list [tm-rid@ietf.org](mailto:tm-rid@ietf.org?subject=Question regarding RFC 9886)

Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9886

Abstract

This document defines the Domain Name System (DNS) functionality of a Drone Remote Identification Protocol (DRIP) Identity Management Entity (DIME). It is built around DRIP Entity Tags (DETs) to standardize a hierarchical registry structure and associated processes to facilitate trustable and scalable registration and lookup of information related to Unmanned Aircraft Systems (UAS). The registry system supports issuance, discovery, and verification of DETs, enabling secure identification and association of UAS and their operators. It also defines the interactions between different classes of registries (root, organizational, and individual) and their respective roles in maintaining the integrity of the registration data. This architecture enables decentralized, federated operation while supporting privacy, traceability, and regulatory compliance requirements in the context of UAS Remote Identification and other services.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.