figure description

[mglt]

1.2.2. Network RID
"""
specifying airspace volumes of interest. Network RID depends upon
connectivity, in several segments, via the Internet, from the UAS to
the Observer.
"""

I believe that listing the segments may be helpful. In particular, I have the impression that the UAS is the (UA + GCS) which makes Net-RID being transmitted by the GCS or the UA. If that is correct, i believe that could be clarifying if explicitly mentioned. I am reading the various segments being UA - SP, or GCS - SP, SP - DP, Observer - DP. However, in these case the link UA - GCS is not necessarily involving the Internet. It seems to me that the text needs to avoid such confusion.

[ShuaiZhao]

@mglt This is one of those things, at least from Bob's vision, DRIP can solve. The link usage between UA and GCS, between UAS and SP and DP and observers.

There are texts below addressing your concern:

"
{{F3411-19}} prescribes the protocols only between the Net-RID SP, Net-RID DP, and the Discovery and Synchronization Service (DSS). DRIP may also address standardization of protocols between the UA and GCS, between the UAS and the Net-RID SP, and/or between the Net-RID DP and Observer devices."

[boucadair]

Re-, This was a comment from Daniel, which I share BTW. I’m afraid that the excerpt you cited below (especially, “DRIP may also address standardization of protocols …”) raises another issue which is: how this is planned to be solved by DRIP? I guess you had in mind things such as cs-rid. As this is an architectural document, I’d expect us to be more explicit. Having flow examples to illustrate how this can be solved by drip would be helpful. Thank you. Cheers, Med De : Shuai Zhao ***@***.*** Envoyé : samedi 26 juin 2021 01:12 À : ietf-wg-drip/draft-ietf-drip-arch ***@***.***> Cc : BOUCADAIR Mohamed INNOV/NET ***@***.***>; Mention ***@***.***> Objet : Re: [ietf-wg-drip/draft-ietf-drip-arch] figure description (#8) @boucadair<https://github.com/boucadair> This is one of those things, at least from Bob's vision, DRIP can solve. The link usage between UA and GCS, between UAS and SP and DP and observers. There are texts below addressing your concern: " {{F3411-19}} prescribes the protocols only between the Net-RID SP, Net-RID DP, and the Discovery and Synchronization Service (DSS). DRIP may also address standardization of protocols between the UA and GCS, between the UAS and the Net-RID SP, and/or between the Net-RID DP and Observer devices." — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#8 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADXR6V6K35UE27ZXOZJZJGTTUUELVANCNFSM46H3LUKA>.

…

_________________________________________________________________________________________________________________________ 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.

[mglt]

I believe the text needs to be very explicit about the basic use case we are addressing. That the usage or RID might be extended in the future to other interfaces is left for future work. The architecture document should not be vague in order to remain compatible with hypothetical cases, it should clarify the basic use of RID we are focused on. Eventually, we can mention that in the future, the use of RID may be extended to XXXXX.

[cardsw]

The segments are as Daniel described them. The new Figure 4 created by Adam may help.

[ShuaiZhao]

added the following editor-note, to be discussed during IETF 111

> Editor-note 1: 
+ list all the segments mentioned above
+ specify how DRIP provide solutions for each segment

[ShuaiZhao]

implemented based on comments:

### Network RID ### {#nrid}

A RID data dictionary and data flow for Network RID are defined in {{F3411-19}}.
This data flow is emitted from an UAS via unspecified means (but at least in part over the Internet)
to a Network Remote ID Service Provider (Net-RID SP).
A Net-RID SP provides the RID data to Network Remote ID Display Providers (Net-RID DP). 
It is the Net-RID DP that responds to queries from Network Remote ID Observers  (expected typically, but not specified exclusively, to be web-based) specifying airspace
volumes of interest. Network RID depends upon internet connectivity to fulfill Observers the RID data query to the NET-RID DP.  The summary of network RID data flows work as follows: 

+ The UA’s RID data is generated from a UAS which consists of UAs and GCSs.
+ The RID data is transferred from the UA to the GCS via a RF (Radio Frequency) link.
+ The GCS provides UA’s RID data to a NET_RID_SP via a secure internet connection.
+ NET_RID_DP as a NET_RID_SP subscriber and satisfies the Observer’s query request also via a secure internet connection.

[boucadair]

Some nits:

• I'm not sure to parse "..RID depends upon internet connectivity to fulfill Observers the RID data query to the NET-RID DP"
• NET_RID_DP and NET_RID_SP not defined in the text. You can use Net-RID SP and Net-RID DP, instead. You can also update the figure
• s/internet/Internet (2 occurences)
• s/a RF (Radio Frequency) link/an RF (Radio Frequency) link
• s/network RID/Network RID