This is a multi-part message in MIME format.
--------------1A5744DE2F45
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Some of you have probably already seen this...but for those that
haven't, here is some IETF news.
--------------1A5744DE2F45
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-Path: <ietf-request at ietf.org>
Received: from gatekeeper.sharplabs.com by sla5c.enet.sharplabs.com.sharplabs.com (SMI-8.6/SMI-SVR4)
id LAA10633; Mon, 11 Nov 1996 11:24:48 -0800
Received: from ietf.org (ietf.org [132.151.1.19]) by gatekeeper.sharplabs.com (SMI-8.6/8.7.3) with SMTP id LAA22065 for <rturner at sharplabs.com>; Mon, 11 Nov 1996 11:20:27 -0800
Received: from ietf.org by ietf.org id aa19774; 11 Nov 96 14:05 EST
Received: from nacho.cisco.com by ietf.org id aa19664; 11 Nov 96 14:03 EST
Received: from fred-axel-fr.cisco.com (fred-axel-fr.cisco.com [171.69.128.115]) by nacho.cisco.com (8.6.12/CISCO.SERVER.1.1) with ESMTP id LAA01182 for <ietf at ietf.org>; Mon, 11 Nov 1996 11:01:44 -0800
Received: from [171.69.128.114] (fred-mac-fr.cisco.com [171.69.128.114]) by fred-axel-fr.cisco.com (8.6.8+c/CISCO.WS.1.1) with SMTP id LAA22391 for <ietf at ietf.org>; Mon, 11 Nov 1996 11:01:41 -0800
X-Sender: fred at stilton.cisco.com
Message-Id: <v02140b00aea995443639@[171.69.128.114]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 11 Nov 1996 11:00:04 -0800
To: ietf at ietf.org
Sender: ietf-request at ietf.org
From: Fred Baker <fred at cisco.com>
Subject: Changes in the IETF Organization
Source-Info: From (or Sender) name not authenticated.
Permit me to take this opportunity to inform you of some changes in the
organization of the IETF, effective with the Memphis IETF meeting. At the
recent IESG Retreat (October 21-22) in Santa Barbara, we discussed the
direction of the Operations (formerly Operational Requirements) and the
Network Management Areas. We decided to merge them into a common Operations
and Management (O&M) Area. Mike O'Dell, the continuing Operations Area
Director, will be one of the Area Directors for O&M; the other is to be
determined by the Nominations Committee.
The purpose of this change is, as much as anything, to ensure a closer
liaison between the Network Management and the Operations communities. We
want to make very certain that network management is more than "making SNMP
work well"; it needs to be "SNMP and whatever else manages networks well" -
a strong operational focus.
All work which is currently being done in the Operations Area will be in
the O&M Area. This includes benchmarking, peformance analysis, management
of deployments and transitions, route policy, and some other issues.
Over the years, the Network Management community has developed a pool of
expertise in MIB development, embodied in the Network Management
Directorate. This important group will continue to exist in the O&M area,
and will continue to provide expertise in MIB development as a service to
their own and other areas.
Much of what has happened in the SNMP area is the development of MIBs. The
policy has been for some time that MIBs should really be developed by the
working group handling the protocol or other entity being managed.
Nonetheless, some MIB development has occurred in the Network Management
Area. The IESG will review these working groups during the transition; some
of will move to other areas, such as Internet or Applications. Those groups
that are closely tied to the evolution of management itself, like AgentX,
will move with the SNMP work to O&M. Groups that don't have a natural home
will be evaluated on a case by
case basis.
The development of SNMP itself, including the SNMP V2 Advisory Group
chaired by Russ Mundy, will be in the O&M Area. We expect that the work
identified and agreed to will be chartered in O&M, and will be carried out
with strong support from the Security community.
Thanks are due to Chuck Davin, Marshall Rose, and Deirdre Kostick for their
leadership of the area over the years, and to the many who have worked in
it. We hope that with this refocusing of vision, future network management
developments will build and improve on the groundwork that has been laid.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Fred Baker | While one person hesitates because
Cisco Systems | he feels inferior, the other is
519 Lado Drive | busy making mistakes and becoming
Santa Barbara, California 93111 | superior.
VOICE +1 408 526 4257 |
FAX +1 805 681-0115 | -- Henry C. Link
--------------1A5744DE2F45--