Good catch: not that the issue has not been addressed, but that where
(external to IETF) it has been addressed is neither cited nor explained
in our requirements; those of us more involved in UAS know it was
addressed elsewhere, so never thought even to mention it here, as we
should. Thanks!
I previously sent the above reply to a narrower distribution, but just
learned proper form in this context is to Reply to All.
On 6/4/2021 6:34 PM, Linda Dunbar via Datatracker wrote:
Reviewer: Linda Dunbar
Review result: Has Issues
Reviewer: Linda Dunbar
Review result: Has Issues
I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These
comments were written primarily for the benefit of the security area directors.
Document editors and WG chairs should treat these comments just like any other
last call comments.
This document specifies the requirements for Drone Remote Identifiers. But it
doesn't specify any Authoritative agencies to manage the Remote IDs. Section
1.2 states that the Remote IDs are "Self-reports". Does it mean anyone who
buys or deploys drones will follow the naming requirements specified by this
document? How to enforce?
Best Regards,
Linda Dunbar
--
-----------------------------------------
Stuart W. Card, PhD, Principal Engineer
AX Enterprize, LLC www.axenterprize.com
4947 Commercial Drive, Yorkville NY 13495
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
