Hi,
Thanks for the responses, this all sounds fine to me.
I'm happy for you to go with what you think is best.
Best,
Reese
On 10/13/25 01:39, Scott Mansfield wrote:
I am ok with Mahesh’s modification of my response related to the first
sentence in the Security Considerations Section.
I would suggest that I leave the sentence and put in a not to the RFC
editor to either add a pointer to the draft, or the RFC depending on
whether or not RFC8407bis is finished or not. I am hoping that to
avoid the intf-ext-yang module to be blocked by the publication of
RFC8407bis.
Regards,
-scott.
*From:*Mahesh Jethanandani <[email protected]>
*Sent:* Sunday, October 12, 2025 1:29 PM
*To:* Scott Mansfield <[email protected]>
*Cc:* Reese Enghardt <[email protected]>; [email protected];
[email protected]; [email protected];
[email protected]
*Subject:* Re: draft-ietf-netmod-intf-ext-yang-17 ietf last call
Genart review
Hi Scott,
Just one suggestion to address Reese’s comments. See inline with [mj]
On Oct 12, 2025, at 5:46 AM, Scott Mansfield
<[email protected]> wrote:
Hello, and thank you for the review!
Please see my responses and suggested actions marked by
<scott></scott> in-line below. Let me know if the resolutions are
acceptable, and I will re-spin the draft.
Regards and Thanks,
-scott.
Snip...
Minor issues:
Section 9 (Security Considerations) has RFC AAAA, but I don't see
where that reference is defined. Please double-check that this
reference is clear.
<scott>
This is from the Security Considerations template found in
draft-ietf-netmod-rfc8407bis. I suggest that I simply take out
the first sentence of that section since
draft-ietf-netmod-rfc8407bis isn't an RFC yet. Leave the rest of
the section because the new template is easy to read and use.
</scott>
[mj] I would just refer to the I-D itself or add a “Note to the RFC
Editor”.
You can say - “This section is modeled after the template described in
Section 3.7 of [I-D.ietf-netmod-rfc8407bis]” and let the editor insert
the right RFC number when it is assigned (possibly before this
document gets to publication state).
Alternatively, you can add a “Note to the RFC Editor” and mention that
AAAA should be the number that will be assigned to
I-D.ietf-netmod-rfc8407bis.
Thanks
Mahesh Jethanandani
[email protected]
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
