search

ietf-wg-drip / draft-ietf-drip-arch

Other
1 stars 0 forks source link

list specific requirement numbers in section 4.1 ( UAS Remote Identifiers Problem Space, version -13) #30

Closed ShuaiZhao closed 3 years ago

ShuaiZhao commented 3 years ago

From Stu:

-arch Section 4.1

This section does 2 things: recapitulate some of what is in -reqs; and begin to introduce/justify HHITs. I would be much happier if it cited -reqs generally for the motivation, then one by one went through its specific numbered requirements and showed how HHITs, together with private and public registries (inc. DNS) satisfy them.

ShuaiZhao commented 3 years ago 
4.1.  UAS Remote Identifiers Problem Space

      Editor-note 14: Good to have: adding match requirment numbering
      from requirement document
mglt commented 3 years ago

+1 maybe in the appendix.

ShuaiZhao commented 3 years ago

not sure this is all, but see the below updated text: 

4.1.  UAS Remote Identifiers Problem Space

   A DRIP entity identifier needs to be "Trustworthy" (See DRIP
   Requirement about GEN-1, ID-4 and ID-5 in [I-D.ietf-drip-reqs]).
   This means that within the framework of the RID messages, an Observer
   can establish that the DRIP identifier uniquely belong to the UAS.
   That the only way for any other UAS to assert this DRIP identifier
   would be to steal something from within the UAS.  The DRIP identifier
   is self-generated by the UAS (either UA or GCS) and registered with
   the USS.