Hi Med, Please count me as a contributor as well.
Samier Barguil From: thomas.g...@swisscom.com <thomas.g...@swisscom.com> Sent: Tuesday, April 1, 2025 12:15 PM To: mohamed.boucad...@orange.com; jclarke=40cisco....@dmarc.ietf.org; ops-...@ietf.org; opsawg@ietf.org; adr...@olddog.co.uk Cc: cmpig...@ncsu.edu Subject: [OPS-DIR]Re: RFC5706 (Refresh): Guidelines for Considering Operations and Management CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Dear Med, We definitely need a refresh. Good catch. Count me as a document contributor and reviewer. This matches well with what I have already contributed here: https://datatracker.ietf.org/doc/html/draft-boucadair-nmop-rfc3535-20years-later-07#section-4.10 Best wishes Thomas From: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Sent: Monday, March 31, 2025 9:40 AM To: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org<mailto:jclarke=40cisco....@dmarc.ietf.org>>; ops-...@ietf.org<mailto:ops-...@ietf.org>; opsawg@ietf.org<mailto:opsawg@ietf.org>; adr...@olddog.co.uk<mailto:adr...@olddog.co.uk> Cc: Carlos Pignataro <cmpig...@ncsu.edu<mailto:cmpig...@ncsu.edu>> Subject: [OPSAWG]Re: RFC5706 (Refresh): Guidelines for Considering Operations and Management Be aware: This is an external email. Hi Joe, Good points. Looking forward to see how this will be elaborated in the bis. Will share by the end of the week the final list of volunteers and a plan to conduct this project. Thanks. Cheers, Med De : Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org<mailto:jclarke=40cisco....@dmarc.ietf.org>> Envoyé : dimanche 30 mars 2025 01:00 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>>; ops-...@ietf.org<mailto:ops-...@ietf.org>; opsawg@ietf.org<mailto:opsawg@ietf.org>; adr...@olddog.co.uk<mailto:adr...@olddog.co.uk> Cc : Carlos Pignataro <cmpig...@ncsu.edu<mailto:cmpig...@ncsu.edu>> Objet : [OPS-DIR]Re: RFC5706 (Refresh): Guidelines for Considering Operations and Management After the recent erratum, I was thinking the same thing. I would be interested in helping with this, but I think, as with the security considerations boilerplate, something more "organic" that be updated with less process. One thing missing from 5706 that might be a useful add (based on NEMOPS) is recommendations about tooling. Even if this is just a mention that sample code or Hackathon projects are useful to help those adopt a new protocol would be useful. Joe From: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Date: Friday, March 28, 2025 at 03:09 To: ops-...@ietf.org<mailto:ops-...@ietf.org> <ops-...@ietf.org<mailto:ops-...@ietf.org>>, opsawg@ietf.org<mailto:opsawg@ietf.org> <opsawg@ietf.org<mailto:opsawg@ietf.org>>, adr...@olddog.co.uk<mailto:adr...@olddog.co.uk> <adr...@olddog.co.uk<mailto:adr...@olddog.co.uk>> Cc: Carlos Pignataro <cmpig...@ncsu.edu<mailto:cmpig...@ncsu.edu>> Subject: [OPS-DIR]RFC5706 (Refresh): Guidelines for Considering Operations and Management 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
