1 / 8

Operator Requirements for Infrastructure Management

Operator Requirements for Infrastructure Management. Steve Feldman NANOG 24 – Feb. 12, 2002 - Miami. Introduction. IETF Operations/Network Management area outreach to network operators Find out what operators really use and want Help set agenda for future IETF work

aretha-rivera
Download Presentation

Operator Requirements for Infrastructure Management

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. Operator Requirementsfor Infrastructure Management Steve Feldman NANOG 24 – Feb. 12, 2002 - Miami

  2. Introduction • IETF Operations/Network Management area outreach to network operators • Find out what operators really use and want • Help set agenda for future IETF work • Recommendations to vendors

  3. Meetings • May 2001: NANOG – Scottsdale, AZ • August 2001: IETF – London, UK • October 2001: RIPE – Prague, CZ • November 2001: USENIX LISA - San Diego, CA • December 2001: IETF – Salt Lake City, UT

  4. Current Internet-Draft • http://www.ietf.org/internet-drafts/draft-ops-operator-req-mgmt-01.txt • Author: Bill Woodcock • New revision “real soon now” • revise document structure • latest thinking on requirements • Goal: IETF last call and publication as Informational RFC

  5. Some Proposed Requirements • ASCII communications. • One syntax and vocabulary for all common functions. • Secure and authenticated in-band interactive and batch communications must be available. • Devices must support a configuration display mode which makes all assumed and default values visible.

  6. Some Open Issues • Text vs. machine readable output • Automation for “large” networks • Bulk commit

  7. Please Help! • Read the draft • Join the mailing list: ops-nm-request@ops.ietf.org • Contribute your opinions!

  8. Contacts • Chair: Steve Feldman – feldman@twincreeks.net • Document Editor: Bill Woodcock – woody@pch.net • Area Directors: Randy Bush and Bert Wijnen • Mailing List: ops-nm-request@ops.ietf.org • List archive: http://ops.ietf.org/lists/ops-nm/

More Related