Re: [netconf] Lars Eggert's No Objection on draft-ietf-netconf-trust-anchors-23: (with COMMENT)

Hi Lars,

Thank you for your valuable comments.
Please find responses below.

Kent

> On Feb 1, 2024, at 6:38 AM, Lars Eggert via Datatracker <noreply@ietf.org> wrote:
> 
> Lars Eggert has entered the following ballot position for
> draft-ietf-netconf-trust-anchors-23: 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.org/about/groups/iesg/statements/handling-ballot-positions/ 
> 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/doc/draft-ietf-netconf-trust-anchors/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> # GEN AD review of draft-ietf-netconf-trust-anchors-23
> 
> CC @larseggert
> 
> Thanks to Paul Kyzivat for the General Area Review Team (Gen-ART) review
> (https://mailarchive.ietf.org/arch/msg/gen-art/hI2a8vgOBaDljK3k37xmQaUMB0Y).
> 
> ## Nits
> 
> All comments below are about very minor potential issues that you may choose to
> address in some way - or ignore - as you see fit. Some were flagged by
> automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
> will likely be some false positives. There is no need to let me know what you
> did with these suggestions.
> 
> ### Grammar/style
> 
> #### Section 1.1, paragraph 5
> ```
> placeholder value for binary data has has been base64 encoded. This placeho
>                                   ^^^^^^^
> ```
> Possible typo: you repeated a word.

s/has has/that has/

> #### Section 2.1.3.4, paragraph 5
> ```
> f [I-D.ietf-netconf-crypto-types]. Thus the "cert-data" node is a CMS struct
>                                   ^^^^
> ```
> A comma may be missing after the conjunctive/linking adverb "Thus".

Replaced “Thus the” with just “The”

> #### Section 2.1.3.4, paragraph 6
> ```
> f [I-D.ietf-netconf-crypto-types]. Thus the "public-key" node can be one of
>                                   ^^^^
> ```
> A comma may be missing after the conjunctive/linking adverb "Thus".

Replaced “Thus the” with just “The”

> #### Section 2.3, paragraph 32
> ```
> any name, be used for any purpose and etc., subject to constraints imposed b
>                                   ^^^^^^^
> ```
> Write the name of the item after "and" or use only "etc".

Removed "and etc."

Thanks again,
Kent

> ## Notes
> 
> This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
> [`ietf-comments` tool][ICT] to automatically convert this review into
> individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].
> 
> [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
> [ICT]: https://github.com/mnot/ietf-comments
> [IRT]: https://github.com/larseggert/ietf-reviewtool
> 
> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf