[Drip] Re: RFC 9886 on DRIP Entity Tags (DETs) in the Domain Name System

["Eric Vyncke (evyncke)" <[e-mail]>]

A nice present before the end of the year vacation.

And for some of us, a nice gift under the Christmas tree with a good timing !

Regards and thanks to the authors and the working group.

-éric

PS: moreover, as the IETF Secretariat and RFC Editor are on vacation, this is also probably the *last* RFC published in 2025.

From: [e-mail] <[e-mail]>
Date: Wednesday, 24 December 2025 at 20:18
To: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: RFC 9886 on DRIP Entity Tags (DETs) in the Domain Name System

A new Request for Comments is now available in online RFC libraries.


        RFC 9886

        Title:      DRIP Entity Tags (DETs) in
                    the Domain Name System
        Author:     A. Wiethuechter, Ed.,
                    J. Reid
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2025
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      33
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-drip-registries-33.txt

        URL:        https://www.rfc-editor.org/info/rfc9886

        DOI:        10.17487/RFC9886

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.

This document is a product of the Drone Remote ID Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
IETF-Announce mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]