Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt

[Robert Moskowitz <[e-mail]>]

I think I have addressed all of your comments and will shortly be 
posting -19.

I think I can pull out references to secure-nrid-c2 which will clean up 
draft dependencies.

Nit change in IANA considerations on TBD6.

Otherwise, everyone, please read through the soon to be posted -19...

On 4/1/22 09:07, [e-mail] wrote:
> Standard
>
> Rob,
>
> Please find below my comments to -18:
>
>   * pdf:
>     https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.pdf
>     <https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.pdf>
>   * doc:
>     https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.doc
>

BMI4:

"DRIP Requirements" comes from the title of 9153, so:

    DRIP Requirements [RFC9153] describe an Unmanned Aircraft System
    Remote Identification and tracking (UAS ID) as unique (ID-4), non-

BMI6:  Oops!  And I thought I did a find on '32'...

BMI8:  Meaning the openssl program with the rand option as in:
        openssl rand -hex 16

So what pointer should I add?



"Note to the RFC Editor: Please replace TBD6 with the assigned IPv6
prefix in Section 9.5."

Why include this?  All TDBs reference something in IANA Considerations.  
My understanding this is "the way to handle IANA assigned values".  So 
TBD1 - 5 does not have RFC editor notes.

BMI13

See 3rd para in introduction.

BMI14:

OOPS!  This was suppose to go with the addition of the 8-bit HHSI.

Thanks...

BMI17:

Another oops that is a left-over and missed.  But this goes back further 
and I did not catch it after how many read-throughs?

BMI18:  ARGH!!! which rfc?  I used 4034...

sec 4.6:  I had to read up in the FAQ how to reference 2 sections...

BMI19:  No, 8005.  Specifically how to reverse lookup HITs.  At least 
that was my intent.  I am open to other views.

BMI21: 1/2 of removing crowd-sourced-rid from this doc...