[MBONED]Re: AD Review of draft-ietf-mboned-amt-yang-05

[[e-mail]]

Hi Changwang, all,

Thank you for preparing this revised version and for addressing ALL my comments.

I will put this version in the IETF LC.

Cheers,
Med

De : linchangwang <[e-mail]>
Envoyé : mercredi 25 mars 2026 06:02
À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>; [e-mail]; MBONED WG <[e-mail]>
Objet : Re: AD Review of draft-ietf-mboned-amt-yang-05


Hi Med,

Thank you for your review.
We appreciate your thoughtful comments and suggestions.

All your comments have been addressed in latest version.
Link: https://datatracker.ietf.org/doc/draft-ietf-mboned-amt-yang/06/

Pls check and let us know if there are any further comments.

Thanks,
Changwang

发件人: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
发送时间: 2026年2月26日 18:37
收件人: [e-mail]<mailto:[e-mail]>; MBONED WG <[e-mail]<mailto:[e-mail]>>
主题: AD Review of draft-ietf-mboned-amt-yang-05


Hi Yisong , Changwang, Zheng, Xuesong, and Vinod,

Thank you for the effort put into this specification.

FWIW, you can find the full review at:


  *   pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2026/draft-ietf-mboned-amt-yang-05-rev%20Med.pdf
  *   doc: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2026/draft-ietf-mboned-amt-yang-05-rev%20Med.doc

I’m listing below some key points:

# Narrative

Overall, I think that we need to work a bit the narrative part of the spec to explain how the module is supposed to be used.

# Features

As the module covers two distinct components, I think that we need to use features to conditionally trim part of the module that applies to specific components.

# Operational considerations

There are some operational considerations that we flag when using the module (detect anomalies based on mismatching address families, track discontinuity time for the counters, etc.). These should be called out in the module itself per the guidance in draft-ietf-opsawg-rfc5706bis, which says:

   Data Models (e.g., YANG) and other schema artifacts (JSON schema,
   YAML, CDDL, etc.) may be consumed out of the RFCs that specify them.
   As such, it is recommended that operational aspects for a data model
   (and similar artifacts) are documented as part of the model itself.
   Such considerations should not be duplicated in the narrative part of
   a specification that includes such artifacts.

# Types & Restrictions

There are some issues with some enum nodes as this doe sot allow for extensibility. A check is needed that is intended. Please refer to draft-ietf-netmod-rfc8407bis on more guidance.

Likewise, there is a limitation to provide one single address per address family. Please check.

# Reusable types

Address-family identities and UDP grouping can be reused from existing specs. We don’t need to repeat those here.

# Clarify what is out of scope

For example, private key provisioning.

Please let me know if any clarification is needed for any of the points.

Cheers,
Med

____________________________________________________________________________________________________________

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.
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出的个人或群组。
禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。
如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited.
If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
____________________________________________________________________________________________________________
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.