**Session Date/Time:** 28 Mar 2023 06:30

# drip

## Summary

This IETF drip working group meeting covered several key topics, including updates on external activities influencing the group's work, progress on the authentication and registry documents, discussions on DNS Apex considerations, and the potential creation of a new DNS resource record type. The meeting addressed dependencies on external organizations like ICAO and IANA and highlighted the need for broader international participation in the working group.

## Key Discussion Points

*   **External Activities:**
    *   FAA contract awarded to On Technologies for broadcast grid implementation.
    *   ICAO's work on device-to-device certificate-based security framework (A2X).
    *   ANSI's updated gaps report on UAS standards.
    *   Field testing of drip receiver application.
    *   Presentation of drip at ICAO trust framework panel.
*   **Authentication Document:**
    *   Cleaned up and made more standalone, reducing hard references to the registry document.
    *   Changes reflected in the -30 version, available on GitHub (AtW branch).
*   **Registry Document:**
    *   Added a new section (2.1) outlining supported registration scenarios.
    *   Detailed discussion of serial number formats (Bare, Linked, Generated) based on ANSI CTA 2063-A and RFC 9374.
    *   Apex: The group agreed on using `ip6.arpa` for debt addresses. The discussion of sn.icao.arpa Apex format for serial numbers resulted in a few important questions needing wider discussion within the IAB and further coordination with IANA, and especially ICAO.
*   **New Resource Record Type:**
    *   Consideration of creating a new DNS resource record type (potentially based on hip) to simplify DNS lookups and avoid multiple queries. A recommendation to create one was inserted to the new version.
*   **Endorsements:**
    *   Discussion on whether the endorsement section should be a separate document and alignment with x509 structures being used by ICAO.

## Decisions and Action Items

*   **Action Item:** Adam to coordinate sending registry document (dash 09) to DNS directorate for early review.
*   **Action Item:** Address the point that identifiers will probably end up being a matter of nash law a national regulation, not necessarily something that here can decree for everybody, in further versions of the document.
*   **Action Item:** Revisit whether or not the section about endorsements in the drip registry architecture document benefits from being a separate document after a more mature version of the documents exists.
*   **Decision:** The group is open to the idea of a new DNS Resource Record Type (potentially a form of HIP).
*   **Decision:** The group wants to ensure alignment of endorsements with the trust framework work for ICAO.

## Next Steps

*   Clean up Section 6 (use case processes) and Section 7 (differential access) in the registry document.
*   Develop and allocate the new resource record type (potentially create a separate draft).
*   Re-evaluate breaking out endorsements into a separate document.
*   Backport x509 work from ICAO into the registry document (potentially separate draft).
*   Address the need to consider national delegation regarding putting identifiers for devices in the domain namespace in the document.
*   Schedule interim meetings to progress on the registry document.
*   Working group last call for the Registry document is targeted for 2024-01-18, if possible.