Hi Bob, all, Please see inline for point (3). Cheers, Med > -----Message d'origine----- > De : last-call <last-call-bounces@xxxxxxxx> De la part de Robert > Moskowitz > Envoyé : mardi 12 juillet 2022 19:33 > À : Dave Thaler <dthaler@xxxxxxxxxxxxx>; int-dir@xxxxxxxx > Cc : draft-ietf-drip-arch.all@xxxxxxxx; last-call@xxxxxxxx; tm- > rid@xxxxxxxx > Objet : Re: [Last-Call] Intdir telechat review of draft-ietf-drip- > arch-24 > > > > On 6/28/22 20:51, Dave Thaler via Datatracker wrote: > > Reviewer: Dave Thaler > > Review result: Ready with Issues > > ... > > > 3. In my reading [I-D.ietf-drip-auth] and [I-D.ietf-drip- > registries] > > are used normatively in sections 5 and 8 since they are used by > way of > > limitation to those references, rather than by way of example > where > > alternatives may be applied. But they are listed as informative, > not > > normative references. I think both should be moved to be > normative > > unless the WG changes language like "as described in" to "such > as described in" or similar, to make them exemplary. > > Chairs/AD call. [Med] Both I-D.ietf-drip-registries and -auth are informative. I suggest to make the following changes to make things clear: (1) Update the terminology to indicate that "DRIP registries" is used to refer to the registries in Section 4.4 of [RFC9153]. Also, update that section to introduce "Broadcast Attestations". (2) OLD: DRIP registries [I-D.ietf-drip-registries] hold both public and private UAS information (See PRIV-1 in [RFC9153]) resulting from the DRIP identifier registration process. NEW: DRIP registries hold both public and private UAS information (See PRIV-1 in [RFC9153]) resulting from the DRIP identifier registration process. (3) OLD: On-line and off- line receivers can use a chain of received DRIP link attestations from a root of trust through the RAA and the HDA to the UA, as described in [I-D.ietf-drip-auth] and [I-D.ietf-drip-registries]. NEW: On-line and off- line receivers can use a chain of received DRIP link attestations from a root of trust through the RAA and the HDA to the UA, as described, e.g., in [I-D.ietf-drip-auth] and [I-D.ietf-drip-registries]. Thank you. _________________________________________________________________________________________________________________________ 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. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
