RFC 3535: Overview of the 2002 IAB Network Management Workshop
In plain English — editorial summary, not part of the RFC
This document provides an overview of a workshop held by the Internet Architecture Board (IAB) on Network Management. The workshop was hosted by CNRI in Reston, VA, USA on June 4 thru June 6, 2002. The goal of the workshop was to continue the important dialog started between network operators and protocol developers, and to guide the IETFs focus on future work regarding network management. This report summarizes the discussions and lists the conclusions and recommendations to the Internet Engineering Task Force (IETF) community. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3535
- Published
- May 2003
- Authors
- J. Schoenwaelder
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3869IAB Concerns and Recommendations Regarding Internet Research and EvolutionCurrent
August 2004
- RFC 4052IAB Processes for Management of IETF Liaison RelationshipsCurrent
April 2005
- RFC 4089IAB and IESG Recommendation for IETF Administrative RestructuringCurrent
May 2005
- RFC 2826IAB Technical Comment on the Unique DNS RootCurrent
May 2000
- RFC 4417Report of the 2004 IAB Messaging WorkshopCurrent
February 2006
- RFC 4440IAB Thoughts on the Role of the Internet Research Task Force (IRTF)Current
March 2006
- RFC 3777IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
June 2004
- RFC 5078IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees TimelineObsoleted
October 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?