[secdir] Secdir last call review of draft-ietf-drip-reqs-12

Linda Dunbar via Datatracker <noreply@ietf.org> Fri, 04 June 2021 22:34 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-drip-reqs.all@ietf.org, last-call@ietf.org, tm-rid@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162284607683.2810.922759741714671925@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Fri, 04 Jun 2021 15:34:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/lrAuVH-j4JSdbon231J3ZWprNPE>
Subject: [secdir] Secdir last call review of draft-ietf-drip-reqs-12

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

[secdir] Secdir last call review of draft-ietf-dr… Linda Dunbar via Datatracker
Re: [secdir] Secdir last call review of draft-iet… Stuart W. Card
Re: [secdir] Secdir last call review of draft-iet… Card, Stu