1 / 8

OPS Guidance for Non OPS Audience

This guidance discusses sharing OPS knowledge, advising on OPS tools and protocols, and making recommendations for future developments in management frameworks. It addresses the challenges faced by existing working groups and aims to provide solutions for new WG charters, emphasizing the importance of operational requirements and appropriate protocol selection. The text proposes utilizing flowcharts and a WIKI for collaborative knowledge sharing. Join the discussion to streamline OPS practices and decision-making in the evolving landscape of network management.

johannak
Download Presentation

OPS Guidance for Non OPS Audience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Benoit Claise IETF 88 OPS Guidance for Non OPS Audience

  2. Problem 1: How do we Share our OPS Knowledge? • How do we advice which OPS tools the community should be using? • OPS tools = protocols and data models • Example: NETCONF, SNMP, AAA, ping, syslog, IPFIX, etc. • We have multiple management frameworks, as opposed to only one in the past: SNMP • Audience: existing WGs • OPS advisors and OPS ADs don’t scale

  3. Problem 2: OPS Recommendations for Future Developments? • Audience: new WG charters • Message: It’s not about MIB module any longer! • Use cases and operational requirements • From there, select the right protocol and data model

  4. Pieces of Information • RFC 5706, Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions • Appendix A: interesting questions for the operational requirements (used by OPS directorate) • RFC 6632, An Overview of the IETF Network Management Standards. • It's complete, but too long • The appendices ask the right question • draft-harrington-operations-and-management-01 • RFC 1052, IAB Recommendations for the Development of Internet Network Management Standards • 25 years old • RFCbis would solve the problem 2

  5. Problem 1: How do we share our OPS knowledge? • Constraints • Must be simple • Must not too long (not a 50 pages document) • Can change on regular basis • Solution: maybe a WIKI or a flow chart?

  6. FLOWCHART

  7. Discussion • Do you agree on the two problem statements? • How to solve them? • Is it too difficult, because the answer is always « it depends »? • Could we agree on flow charts?

  8. Time for a discussion

More Related