Subject: [Tm-rid] Shuai's Review of draft-ietf-drip-reqs-01.txt

From: <[email-masked]>
Date: Tue, 30 Jun 2020 05:02:46 +0000

Hi Shuai, all,

Thank you for the review. I’m forwarding it to the list, fwiw.

Cheers,
Med

De : shuaiizhao(Shuai Zhao) [mailto:[email-masked]]
Envoyé : mardi 30 juin 2020 00:04
À : Card, Stu; BOUCADAIR Mohamed TGI/OLN
Cc : [email-masked]; [email-masked]; [email-masked]; Andrei Gurtov; shuaiizhao(Shuai Zhao)
Objet : Re: OFFLIST RE: [Tm-rid] I-D Action: draft-ietf-drip-reqs-01.txt(Internet mail)

Hi Med and Stu,

Here is my preliminary review on the req-01 draft.

In general, I feel this version has addressed or at least mentioned the most important aspects regarding UA RID and key takeaway for people to understand and I quote is “An (R)ID is not an end in itself; it exists to enable lookups and provision of services complementing mere identification.”

With that in mind, I believe authors have explained well in the problem space, and what they are trying to solve, which has been categorized in different requirement space.

Few suggestions:

  *   Mark introduction section as “informative” due to regulations might change in details overtime and this draft might not be able to keep updated to reflect the changes
  *   Item 3 for sec 3.3: I believe there are more than just UA’s location needs to be verified or vetted and we should not limit our capability to location only. F3411 listed more than a dozen parameters w.r.t UA’s operation which I am not going to list here. I would propose to update this text to the following:

“by facilitating independent reports of UA’s aeronautical data such as GPS coordinate location, speed, flight path and etc, to confirm or refute the operator self-reports upon which UAS RID and UTM tracking are based”

  *   ID-3: The name of “Entity” borrowed from ASTM? I understand this is to enable the lookup for UAS associated data. I am wondering if this is necessary to be listed here.  Is this to propose two different IDs such as “registry ID” vs “Entity ID”?   if not, I’d suggest to remove it and update the “Registry ID” to the following:

“Registry ID: The DRIP identifier MUST be sufficient to identify a registry and the data lookups in which the [UAS] entity identified therewith is listed.”

Suggest items to be removed:

  *   2.2: ABDAA, MSL, GRAIN, GBDAA, IATF, BLOS, BVLOS

Nit:

  *   I would think “Link&#246” and “&#228; are encoding errors?

Best,
Shuai Zhao

.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.