Hello Mohamed,

Thank you for double checking the updated version and your feedback.
I will address the remaining findings as you suggested. They were all straight 
forwards, so I did not provide separate comments.

I will put an updated version on the ANIMA git. The changes are visible via the 
diff: 
https://author-tools.ietf.org/diff?doc_1=draft-ietf-anima-brski-prm&url_2=https://raw.githubusercontent.com/anima-wg/anima-brski-prm/refs/heads/main/draft-ietf-anima-brski-prm.txt
I will wait with a new submission if further comments need to be addressed.

Best regards
Steffen


> -----Original Message-----
> From: Mohamed Boucadair via Datatracker <nore...@ietf.org>
> Sent: Thursday, April 17, 2025 8:08 AM
> To: The IESG <i...@ietf.org>
> Cc: draft-ietf-anima-brski-...@ietf.org; anima-cha...@ietf.org; 
> anima@ietf.org;
> i...@kovatsch.net; t...@cs.fau.de; i...@kovatsch.net
> Subject: Mohamed Boucadair's No Objection on draft-ietf-anima-brski-prm-19:
> (with COMMENT)
>
> Mohamed Boucadair has entered the following ballot position for
> draft-ietf-anima-brski-prm-19: No Objection
>
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
>
>
> Please refer to
> https://www.ietf.or/
> g%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-
> positions%2F&data=05%7C02%7Csteffen.fries%40siemens.com%7Cd6c13e3baf5
> 44b72e3f008dd7d76299e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%
> 7C638804668663336680%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiO
> nRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ
> %3D%3D%7C0%7C%7C%7C&sdata=N6SQ4OqFcfg7XXXBQ7%2B7rJpI8Fub%2
> B7mPE1vo1gmZOWQ%3D&reserved=0
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker/.
> ietf.org%2Fdoc%2Fdraft-ietf-anima-brski-
> prm%2F&data=05%7C02%7Csteffen.fries%40siemens.com%7Cd6c13e3baf544b7
> 2e3f008dd7d76299e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C63
> 8804668663376875%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd
> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D
> %3D%7C0%7C%7C%7C&sdata=DdMpOL%2FDH%2BOkDO%2BZjiZt7Vk5eAr3bo
> wy2abOQW6c3Uw%3D&reserved=0
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Hi Steffen, Thomas, Eliot, and Michael,
>
> Thank you for the productive discussion and for addressing almost all my 
> points
> raised in [1]. The companion discussion [2] triggered by [1] is also
> instructive.
>
> (1) As indicated in the thread, I trust Mahesh will do the right thing with 
> the
> following (used-to-be DISCUSS point):
>
> # Cluster with 8366bis
>
> CURRENT:
>
>    The JSON PVR Data MUST contain the following fields of the "ietf-
>    voucher-request" YANG module as defined in
>    [I-D.ietf-anima-rfc8366bis];
>
> I think this spec should be clustered with 8366bis. There are several
> structures that used in this document and which depend on what is defined in
> 8366bis. Changes to the bis will have implications on this one.
>
> (2) Here are some few comments found when checking 18/19 diff:
>
> * nit
>
> OLD: building automation use case mentioned in (Section 3.1.1)
>
> NEW: building automation use case mentioned in Section 3.1.1
>
> * Smells like a normative reference. Please change as follows:
>
> OLD: if it does not support a more general discovery as defined in
> [I-D.ietf-anima-brski-discovery]
>
> NEW: OLD: if it does not support a more general discovery such as defined in
> [I-D.ietf-anima-brski-discovery]
>
> * nit
>
> OLD: limiting for a requests to avoid susceptibility of the pledge
>
> NEW: limiting for requests to avoid susceptibility of the pledge
>
> * nit (many occurrences)
>
> OLD: Algorithms supported for JWS signatures MUST support
>
> NEW: Algorithms used for JWS signatures MUST support
>
> * Extra references, really?
>
> CURRENT:
>
>    Requirements to the utilized credentials authenticating and artifact
>    signatures on the registrar as outlined in Section 6.3 may have
>    operational implications when the registrar is part of a scalable
>    framework as described in Section 1.3.1 of
>    [I-D.richardson-anima-registrar-considerations].
>
>    Besides the above, also consider the existing documents on
>    operational modes for
>
>    *  BRSKI registrars in
>       [I-D.richardson-anima-registrar-considerations]
>
>    *  BRSKI MASA in [I-D.richardson-anima-masa-considerations]
>
> I-D.richardson-anima-registrar-considerations cited in "Besides the above," 
> was
> cited in the sentence right above ;-)
>
> Please update.
>
> * Commentary not intended initially to make it into the text:
>
> CURRENT:
>    Documents that define exclusively modules following the extension in
>    [RFC8971] are not required to include the security template in
>    Section 3.7.1.  Likewise, following the template is not required for
>    modules that define YANG extensions such as [RFC7952].
>
> I provided this text to motivate what you can safely remove the old paragraph.
> But, if you want to include it, then some tweaking is needed (Section 3.7.1 
> ref
> is broken in the context of this draft + we don't use 7952 here), I suggest:
>
> CURRENT:
>    Documents that define exclusively modules following the extension in
>    [RFC8971] are not required to include the YANG security template per
>    the guidance in Section 3.7 of [I-D.ietf-netmod-rfc8407bis].
>
> Many thanks again for editing such a well-written document.
>
> Cheers,
> Med
>
> [1]
> https://mailarchive/.
> ietf.org%2Farch%2Fmsg%2Fanima%2FqHRppN_6T3KBdsjOksxu8bw4byI%2F&d
> ata=05%7C02%7Csteffen.fries%40siemens.com%7Cd6c13e3baf544b72e3f008dd7
> d76299e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638804668663
> 403265%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIw
> LjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7
> C%7C%7C&sdata=s545ni2BQFGaPXQnLKMGABBs8FGqp%2B8X74qa4dQ0fH0%
> 3D&reserved=0
>
> [2]
> https://mailarchive/.
> ietf.org%2Farch%2Fmsg%2Fanima%2F8HLrJ_PLjIbf11gZjMTuXkC2Z9g%2F&dat
> a=05%7C02%7Csteffen.fries%40siemens.com%7Cd6c13e3baf544b72e3f008dd7d
> 76299e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C6388046686634
> 23485%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwL
> jAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C
> %7C%7C&sdata=xiHlZeIJmypYMhA9Lgn4G4WY3VE3mfcuijFdzwmGYW4%3D&re
> served=0
>
>

_______________________________________________
Anima mailing list -- anima@ietf.org
To unsubscribe send an email to anima-le...@ietf.org

Reply via email to