Hi Gorry,

Thanks for the review!

The -12 revision should address your comments.

Answers inline.


On Mon, May 25, 2026 at 4:59 PM Gorry Fairhurst via Datatracker
<[email protected]> wrote:
>
> Gorry Fairhurst has entered the following ballot position for
> draft-ietf-netmod-yang-module-filename-11: No Record
>
> 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-netmod-yang-module-filename/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Please consider these comments when preparing the next revision of this
> document:
>
> I think the abstract ought to explain this defines the method, not describes
> it, e.g.g: /This document presents YANG module file name convention/This
> document defines the YANG module file name convention/

Taken.


> I couldn't decide if this ought to be lower case or upper case 'RECOMMENDED',
> please rephrase to avoid this comment: /In short, the YANG semantic version
> file name scheme is recommended/

Put "RECOMMENDED" in upper case and stated that it is acceptable to
not use the YANG file name convention if tooling can't handle it.


> I don't understand the requirement in section 4 that states:
> /It MUST be ensured that the files' contents are identical./

Clarified that it should be byte-for-byte identical.


> NiTs:
> /withouth/without/
> /that use/that uses/
> /MAY be created as well/MAY be created./

Taken, thanks!


--
Per


> Best wishes,
> Gorry
>
>
>

_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to