Re-,

Thanks, Carlos. That’s indeed an item to explore.

One comment though, for opsdir, my current take is to have a simplified 
template (not frozen in an RFC) with key topics. Let me not tease too much here 
:-) Hope we will have some thing to share SOON.

Cheers,
Med

De : Carlos Pignataro <cmpig...@ncsu.edu>
Envoyé : vendredi 28 mars 2025 14:34
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>
Cc : ops-...@ietf.org; opsawg@ietf.org; adr...@olddog.co.uk
Objet : Re: RFC5706 (Refresh): Guidelines for Considering Operations and 
Management

Hi, Med,

Thanks for starting this conversation -- I think this is timely and useful.

One suggestion (that I made implicitly but to explore explicitly), I feel it 
would be useful to elevate Appendix A to its own Section, and format it in a 
sort-of template that can be used in OpsDir reviews directly.

I think the terminology does need a brush up and update.
I do like that the mail sections are "Ops" and "Management".

Thanks!

Carlos.

On Fri, Mar 28, 2025 at 3:09 AM 
<mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> wrote:
Hi all,

15 years after the publication of this important document, I think that it is 
time to consider a refresh.

I’m sending this note to gauge interest and hopefully find volunteers to 
explore this path with the aim to produce a bis. Areas that can be easily 
revisited are:


  *   More clarity on the terminology and leverage the work led by Adrian in 
NMOP
  *   IM part
  *   More guidance on the importance of DMs
  *   Soften the MIB part
  *   Add more YANG
  *   Consider if we can generalize the approach in RFC6123 (edited by Adrian)

Suggestions/thoughts are welcome.

Cheers,
Med

PS: Thanks Carlos for planting the seed in my head.

____________________________________________________________________________________________________________

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.
____________________________________________________________________________________________________________
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.
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org

Reply via email to