[netmod] Re: Mike Bishop's No Objection on draft-ietf-netmod-rfc8407bis-25: (with COMMENT)

[[e-mail]]

Hi Mike, 

Thanks for the review. The changes made so far to address your comments can be seen at: https://author-tools.ietf.org/api/iddiff?url_1=https://netmod-wg.github.io/rfc8407bis/draft-ietf-netmod-rfc8407bis.txt&url_2=https://netmod-wg.github.io/rfc8407bis/mike-review/draft-ietf-netmod-rfc8407bis.txt. 

Please see inline. 

Cheers,
Med (as editor)

> -----Message d'origine-----
> De : Mike Bishop via Datatracker <[e-mail]>
> Envoyé : lundi 2 juin 2025 20:03
> À : The IESG <[e-mail]>
> Cc : [e-mail]; [e-mail];
> [e-mail]; [e-mail]; [e-mail];
> [e-mail]
> Objet : Mike Bishop's No Objection on draft-ietf-netmod-rfc8407bis-
> 25: (with COMMENT)
> 
> 
> Mike Bishop has entered the following ballot position for
> draft-ietf-netmod-rfc8407bis-25: 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.)
> 
> 
> -------------------------------------------------------------------
> COMMENT:
> -------------------------------------------------------------------
> 
> I also share Gunter's initial reaction.
> 
> While fine in this document, as it doesn't deal directly with the
> DNS, I would
> consider using a replacement token other than "AAAA" in future
> work, since this
> is a token that occurs somewhat frequently in IETF documents.
> (RFCAAAA is fine.)
> 
> I was surprised by the change in 4.1 from RFC7950 to RFC6020, since
> the latter
> is older than the reference it replaces. However, the content looks
> correct in
> 6020, so I'm guessing this is deliberate and a fix to an error in
> RFC8407.

[Med] I confirm. For some reason, this bug seems to be inherited from draft-ietf-netmod-rfc6087bis-04.

 I
> didn't find anything in the list of changes to reflect this,
> however;

[Med] This is covered by this point: 

CURRENT:
  *  Fixed a reference bug in Section 4.1.

 was there
> an erratum filed for this?
> 
> In Section 5, the current practice is to list the IETF, rather than
> the IESG,
> as the change controller for our registrations.

[Med] Fair point. Note however that YANG specs have always listed IESG in their IANA requests (https://www.iana.org/assignments/xml-registry/xml-registry.xhtml shows that other registrations followed that pattern as well). I guess this is rooted in this part from RFC3688:

   Registrant Contact
      The individual/organization that is the registration contact for
      the component being registered.  Ideally, this will be the name
      and pertinent physical and network contact information.  In the
      case of IETF developed standards, the Registrant will be the IESG.

I will double check with IANA.

 IANA isn't
> revisiting old
> registrations to make this change proactively, but while you're
> updating these,
> consider updating that field as well.
> 
> This may be excessive, but just for clarity, does Appendix B need a
> note to the
> RFC Editor clarifying that the notes to the RFC Editor in the
> template are part
> of the template and should not be acted upon during the processing
> of this
> document?

[Med] No sure we need that note. 

> 
> ===NITS FOLLOW===
> 
> Section 2, "Some of the templates defined in the document uses" =>
> "Some of the
> templates defined in the document use"

[Med] OK

> 
> Section 3.5, "noted following [RFC8792]" could be parsed as placing
> the note
> after RFC8792; consider "indicated with a reference to [RFC8792]"

[Med] Went with "indicated per the guidance in [RFC8792]"

> 
> Section 3.7, "define exclusively modules following" => "exclusively
> define
> modules that follow"

[Med] Fixed.

> 
> Section 3.7.1, consider "have to use" => "require" x2

[Med] Left the current text.

> 
> Section 3.7.1, "as normative references." => "as a normative
> reference."
> 

[Med] Fixed.


____________________________________________________________________________________________________________
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.