----- Unsent message follows -----
Return-Path: <snmpv2-request(_at_)magellan(_dot_)TIS(_dot_)COM>
Received: from can02.pge.com by dns01.pge.com (4.1/SMI-4.1)
id AA25488; Fri, 24 Sep 93 05:16:07 PDT
Received: from magellan.TIS.COM by can02.pge.com (4.1/SMI-4.1)
id AA12573; Fri, 24 Sep 93 05:18:00 PDT
Received: from magellan.tis.com by magellan.TIS.COM id aa28095;
24 Sep 93 7:23 EDT
Received: from tis.com by magellan.TIS.COM id aa28091; 24 Sep 93 7:15 EDT
Received: from azalea.tis.com by TIS.COM (4.1/SUN-5.64)
id AA26827; Fri, 24 Sep 93 07:15:32 EDT
Received: by azalea.tis.com; id AA22020; Fri, 24 Sep 93 07:13:56 EDT
Received: from relay1.pipex.net/158.43.128.4 via smap
Received: from zebedee.netmgrs.co.uk by relay1.pipex.net with SMTP (PP)
id <12729-0(_at_)relay1(_dot_)pipex(_dot_)net>; Fri, 24 Sep 1993
12:15:01 +0100
Received: by netmgrs.co.uk (4.1/SMI-4.1) id AA04383; Fri, 24 Sep 93 12:14:57 BS
T
Date: Fri, 24 Sep 93 12:14:57 BST
From: Roger Booth <roger(_at_)netmgrs(_dot_)co(_dot_)uk>
Message-Id: <9309241114(_dot_)AA04383(_at_)netmgrs(_dot_)co(_dot_)uk>
To: snmp2(_at_)tis(_dot_)com
Subject: NMS Mailing list
Network and Systems Management List (NMS list)
==============================================
Apologies if some of you receive this mail twice.
Some time ago aspects of an NMS mailing list where
discussed.
Network Managers Ltd offered to set up this list.
Below is an attempt to summarise this discussion,
together with a proposed charter for the list.
Replies to this mail must be sent to nms(_at_)netmgrs(_dot_)co(_dot_)uk
To subscribe please send a mail to majordomo(_at_)netmgrs(_dot_)co(_dot_)uk
The content must be "subscribe nms"
Please, no requests for subscription to the nms list.
The Current Situation
=====================
The SNMP mail list primarily discusses all aspects of the
SNMP management protocol and SNMP MIBs. The SNMP mailing
list can be thought of as defining and discussing:
A particular network management protocol (SNMP)
A particular data description or schema language (SNMP SMI)
Many different MIBs using the SNMP SMI
In other words the SNMP list defines and discusses one way
to describe and access data which is pertinent to the management
of networks.
The work of the SNMP list generally stops at the definition of
the MIBs of devices. Very little attempt is made
to establish how a manager can use the management protocol
and MIBs to provide a system which solves a real problem.
The NMS Mailing List
====================
The NMS mailing list will be more focused on solving the
total management problem from the point of view of both
end users and developers of management systems.
Charter
=======
The following is a proposed charter for the NMS mailing
list. The charter takes the form of a series of
discussion topics, followed by a list of restrictions.
o The NMS list will take the view that the only useful
management systems are those which solve users problems.
The NMS list will consider user requirements for
management systems.
The NMS list will consider functionality arising from
those requirements.
Examples: User interface issues
Discussion of functional areas
Access policies and security
Fault diagnosis
The NMS list will consider technology which will aid
developers in the design and implementation of
management systems which provide this functionality.
Examples: Object oriented technology
The use of developers kits
The use of application design toolkits
Database design mechanisms
o The NMS list will take the view that the management
of applications, network elements, and computing
elements have common aspects.
The NMS list will consider systems, network and
desktop management issues.
o The NMS list will take the view that management applications
should be available on a variety of hardware, software
and management platforms.
The NMS list will consider issues relating to the
portability of applications across hardware, software
and management platforms.
The NMS list will consider issues relating to the use
and definition of APIs to facilitate this portability.
o The NMS list will recognise the need for management systems
to handle the wide variety of management protocols, and
schemas which exist today.
The NMS list will consider issues relating to the use
of management protocols and schema other than SNMP.
Examples : CMIP Map/Top X.25 IPX RPC DME Netview
NM Forum OmniPoint
DMTF DMI
This may include the definition of abstract models, capable
of handling any SMI, and the implementation of generic
protocol engines and their interfaces.
o The NMS list will recognise the need for management
applications to be able to interwork with
a. Other management applications
b. Other management related applications
help desk, trouble ticket, cable management
editors etc
c. Other non management applications
spread sheets, mail packages, data presentation
and manipulation tools etc.
The NMS list will consider issues relating to the definition
of protocols and data definitions to facilitate inter application
communication. This may include:
a. Network description languages
b. Manager to manager mibs
c. The exporting and presentation of useful
management information.
d. Scripting languages
e. Database interworking
f. The use of specific application communication
techniques such as: CORBA, OLE, OSI ODP,
RPC, NM Forum / AIMS Edge etc
Restrictions
============
There will be no advertising of individual products
There will be no championing of individual organisations or
companies.
The NMS list will not consider issues which are
already being handled by the SNMP lists.
------- End of Forwarded Message