1 / 6

Ops Area Discussion Management Interface Refinement

Explore the need to update RFC1052 and evolve management requirements for Working Groups (WGs) in the era of SNMP, NETCONF, YANG, and more. This discussion highlights the challenges and proposed solutions for efficient internet management. Enhance your understanding of operational toolsets and multiprotocol approaches for improved WG evolution.

theta
Télécharger la présentation

Ops Area Discussion Management Interface Refinement

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. Ops Area DiscussionManagement Interface Refinement Thomas Nadeau Dan Romascanu IETF 84 - Vancouver

  2. Motivation • Management Interface Requirements for WGs Evolution • Evolve Guidance to and assistance for WGs • Update to RFC1052

  3. What Are The Issues? • Management requirements for WGs have not evolved for some time. • SNMP writes • Need to evolve for all relevant interfaces • A need of per-workgroup tailoring • Ops “assistant” when relevant • Adjust charter to meet needs of WG and have sufficient OPS work items.

  4. Update to RFC1052 • history - 1052 has a historical introduction of its own, hot it is itself (ancient) history, • What happened since (demise of CMIP, evolution of SNMP), RFC 3535, NETCONF and YANG • 1052 had the concept of a 'short term' solution (SNMP) migrating to a 'long term solution' (CMI) using the same MIB. Why does not this work?

  5. Rfc1052 con’t • No one 'protocol fits all' solution is possible. No one data model can efficiently support multiple protocols. • ‘It’s not only about SNMP and MIBs any longer’ • Risk - 'Short term' becomes 'permanently' as the Internet permanently expands and needs to be managed as a collection of autonomous systems deployed at different layers Internet management

  6. Conclusions/Next Steps • Update 1052 • Clean the historical balast • Adopt the an operational toolset/multiprotocol approach • Include broader architectural view • Goals and Interaction between management protocols and OAM protocols • IESG discussion with WGs

More Related