RFC 9886: DRIP Entity Tags (DETs) in the Domain Name System
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9886
- Published
- December 2025
- Authors
- A. Wiethuechter; J. Reid
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 33
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9915Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
January 2026
- RFC 9926Prefix Registration for IPv6 Neighbor DiscoveryCurrent
February 2026
- RFC 9927Fixing the C-Flag in the Extended Address Registration Option (EARO)Current
February 2026
- RFC 9844Entering IPv6 Zone Identifiers in User InterfacesCurrent
August 2025
- RFC 9928DHCPv4 over DHCPv6 with Relay Agent SupportCurrent
March 2026
- RFC 9837The IPv6 VPN Service Destination OptionCurrent
August 2025
- RFC 9812Clarification of IPv6 Address Allocation PolicyCurrent
October 2025
- RFC 9805Deprecation of the IPv6 Router Alert Option for New ProtocolsCurrent
June 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?