Hi, Thanks for the clarification. I think it may be good to reflect your response in the document for completeness. Roni > -----Original Message----- > From: Stuart W. Card [mailto:stu.card@xxxxxxxxxxxxxxxx] > Sent: Wednesday, May 11, 2022 9:58 AM > To: Roni Even; gen-art@xxxxxxxx > Cc: draft-ietf-drip-arch.all@xxxxxxxx; last-call@xxxxxxxx; tm-rid@xxxxxxxx > Subject: Re: Genart last call review of draft-ietf-drip-arch-22 > > Thanks for the review! I was asked to respond to your question. I agree that > GEN-7 and GEN-10 may be conspicuous by their absence from the architecture > document. > > In the initial context of Broadcast RID, GEN-7 (QoS) is a requirement primarily on > implementations of UAS RID senders that requires no explicit architectural > support. For example: CAAs may require a minimum rate at which RID > information is refreshed; in any sender implementation intended for use in > multiple jurisdictions (or on multiple classes of > aircraft) with different rate requirements, this would thus need to be a > configurable parameter; however it need not be remotely configurable, thus > there is no need to specify a protocol or language for getting/setting the > parameter value. As Network RID matures, GEN-7 may assume broader > significance, but we don't want to embed any guesses as to that in the current > architectural overview. GEN-10 (multicast) is even more Network RID specific, > so likewise to be addressed in future DRIP documents. > > Do you feel that the above information should be reflected explicitly in the > architecture document? > > On 4/5/2022 4:07 AM, Roni Even via Datatracker wrote: > > Reviewer: Roni Even > > Review result: Ready > > > > I am the assigned Gen-ART reviewer for this draft. The General Area > > Review Team (Gen-ART) reviews all IETF documents being processed by > > the IESG for the IETF Chair. Please treat these comments just like > > any other last call comments. > > > > For more information, please see the FAQ at > > > > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. > > > > Document: draft-ietf-drip-arch-?? > > Reviewer: Roni Even > > Review Date: 2022-04-05 > > IETF LC End Date: 2022-04-06 > > IESG Telechat date: Not scheduled for a telechat > > > > Summary: > > The document is ready for publication as an informational RFC > > > > One question: I noticed that the document relates to RFC9153 requirements. I > > did not see gen-7 and gen-10 addressed . Gen-7 QoS: DRIP MUST enable > > policy-based specification of performance and reliability parameters. > > > > Major issues: > > > > Minor issues: > > > > Nits/editorial comments: > > > > > > > -- > ----------------------------------------- > Stuart W. Card, PhD, Principal Engineer > AX Enterprize, LLC www.axenterprize.com > 4947 Commercial Drive, Yorkville NY 13495 > 592 Hangar Road, Rome NY 13441 -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
