IAB Workshop on Network Management (netmanws)
Team | Name | IAB Workshop on Network Management | |
---|---|---|---|
Acronym | netmanws | ||
State | Active | ||
Additional resources | RFC 3535: Overview of the 2002 IAB Network Management Workshop |
Group description
As part of its activities, the Internet Architecture Board holds workshops from time to time on topics of relevance and interest to the technical evolution of the Internet. We are planning to hold a workshop in June 2002 on the topic of Network Management. The workshop is being organized by Ran Atkinson, Steve Bellovin, Randy Bush and Bert Wijnen.
This particular workshop will address Network Management Architecture for the global Internet. In particular, the workshop should provide a written report (Informational RFC) of any conclusions. It is hoped that the workshop will be able to reach rough consensus on architectural directions for Internet network management and make corresponding architectural recommendations to the IETF's Operations & Management Area.
The workshop will be held over 2 and 1/2 days, from 9am on Tuesday June 4, 2002 through Noon on Thursday June 6, 2002. It will be hosted at the Corporation for National Research Initiatives (CNRI), on Preston White Drive in Reston, Virginia in the US. The nearest airport is Washington/Dulles (IAD), which is about 15 minutes away.
In order to ensure that the meeting is as productive as possible, and to ensure that the meeting will fit within the venue, this is an invitation-only meeting with a total attendance of no more than 30.
IAB Network Management Workshop Objectives
- Make recommendations to narrow the set of competing approaches to network management that the IETF will continue to develop on the standards track. Define a recommended evolutionary path for network management standards.
- Solicit operator input on their most significant unresolved problem areas. Then, try to identify which existing IETF standards-track protocols might be enhanced/modified to address those problem areas.
- Avoid creating yet more protocol choices during the workshop. Avoid creating any sort of licence for random non-essential changes to existing standards-track protocols.
- Foster additional protocol developer and operator interaction, so as to continue existing O&M Area efforts to get those groups more in touch with each other.