PROPOSED ENSEMBLE DEFINITION PROCESS
Subject: PROPOSED ENSEMBLE DEFINITION PROCESS
From: <NM Forum>
Permission to use, copy, modify, and distribute this material for
any purpose and without fee is hereby granted, provided that
this permission notice appears in all
copies, and that this material is not sold or distributed
commercially.
THE NMF MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR
SUITABILITY OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS
IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
NETWORK MANAGEMENT FORUM
BULLETIN BOARD
ENSEMBLE PROCESS DOCUMENT
CONTENTS
1. Introduction
2. Structure
2.1 Email exploder list
2.2 Directory System
2.2.1 Translated Internet MIBs
3. Process
4. Appendix A
Bulletin Board Ensemble Summary Template
Bulletin Board Object Library File Summary
Template
5. Appendix B
Part 1 - Instructions for using the NMF Objects
Email list
Part 2 - Instructions for using the Forum/Objects
Filestore
6. Appendix C
Bulletin Board Copyright Waiver Form
7. Appendix D
Patent Disclosure Form
PROPOSED ENSEMBLE DEFINITION PROCESS 11th March 1994
1. INTRODUCTION
The Network Management Forum (NMF) has set up a process to
encourage the development of openly available ensemble
definitions. The objective is to enable the industry to move
forward quickly, to define sets of managed object definitions
(ensembles) that meet the business needs of users and vendors.
The NMF wishes to encourage the industry to either carry out the
work openly and by consensus, or to make work already completed
available in the public domain. Either approach is likely to
reduce the number of duplicate and/or overlapping ensembles and
thus should enhance the goal of open interoperability between
management systems.
The NMF's goal is to enable the process and to provide 'light'
guidance on best practice, thus allowing groups to form, achieve
objectives and disband quickly. This requires that some process
and rules be defined to ensure that a minimum of formality and
bureaucracy is required, while enabling maximum participation and
review by interested parties.
To achieve this an email system has been set up , with the kind
assistance of Bellcore, which will facilitate easy communication
and access to relevant information. The Bulletin Board (see
appendix B for detailed description) will contain two types of
facility:-
- a developers/users email exploder. This facility will
enable dialogue between individuals on the list so that problems,
information, feedback, and general communication can take place
on a conversational basis. Anyone will be able to register and
anything sent to this list will be automatically distributed to
everyone registered. Registration and de-registration are
accomplished by sending an email message to the list
administrator.
- a directory structure for file download (via FTP). A
complete set of files will be maintained for all object related
work, either completed or in progress. This will include:
- the object library of definitions (all
OMNIPoint sources)
- the Management Information Catalogue (v2)
- ensemble definitions
- documents relevant to the process
To ensure that vendors/users understand the source and 'status'
of objects/ensembles lodged on the Bulletin Board, it is proposed
to:
- hold summary abstracts for each ensemble and object library
file held in the directory structure. (See appendix A)
- identify within the directory structure separate repositories
for 'registered' and 'draft' material.
- include the main sponsoring organisations' name within the file
naming conventions for the ensemble or objects file.
- maintain an online list, correlating individual object usage
with the ensemble(s) within which they are used. This list will
be updated when both the object and the ensemble are formally
registered.
2. STRUCTURE
2.1 Email exploder list: - this is a normal exploder list
enabling free form conversation between users who have a common
interest, are seeking expert advice or, are seeking information.
The charter and instructions for use are contained in Appendix B
and will also be held online in the Bulletin Board README file.
2.2 Directory System: - this is currently sub-divided into
three directory areas, covering objects, ensembles and
miscellaneous. As above, detailed information can be found in
Appendix B and in the Bulletin Board README file.
Both the Ensembles and Objects directories are further sub-
divided into 'draft' and 'registered' sub directories, reflecting
the state of the contents. For each file in both of these
directories there will be a copy of a summary abstract held
within the same directory. Note that no files will be mounted on
the system without a summary abstract, which must be submitted at
the same time.
Other useful information is also contained within the Objects
directory structure which is further explained in Appendix B.
2.2.1. Translated Internet MIBs: - Internet MIBS are held
online within other Bulletin Board facilities and are thus not
replicated here. However, the NMF, in conjunction with other
groups, has defined mechanisms for translating those MIBs into
GDMO format. GDMO versions of complete Internet MIBs will be
held in the Objects directory to help developers gain access to
this material, and to lower the risk of two different
translations of the same material. Because of the slightly
different mechanisms used to derive the GDMO object definitions
from Internet macros, special procedures are proposed to handle
draft translated MIBs.
Registered, RFC-defined Internet MIBs translated into GDMO format
using the IIMC procedures specified by
/pub/forum/objects/reg/iimcimib.* are assigned tentative object
identifiers during translation. Upon submission to the NMF
Office, draft MIB translations are checked for duplication and
syntax. Drafts which pass this check are posted in a separate
subdirectory (obj/iimcdrft) for a fixed-length review period of
four months. The purpose of the review period is to ensure the
translation is correct; defects (if any) identified by any
reviewer should be returned to the submitter directly. After the
review period completes, the original submitter is responsible
for re-submitting an updated MIB, which corrects any defects
found, to the NMF Office. The tentative object identifiers
assigned during translation are considered registered only after
this process is successfully completed, at which time the final
translated MIB is posted in the /obj/reg subdirectory.
Submitters should note that the Summary Abstract should be sent
in for both submission to 'iimcdrft' and submission to 'reg'
directories.
3. PROCESS
It is the intention that groups of companies should be encouraged
to work together as satellite teams of the NMF's O Team. Each
satellite team sets its own objectives, plan of action and method
of working (i.e. via email, meeting schedules, etc.) For work to
be adopted as 'open', an outline of the group's activities (see
below) must be lodged within the Bulletin Board very early in the
process. Other experts (developers or users) who wish to take
part in comment and review of the ongoing work should be
encouraged to participate. Comments made by any participant
should be resolved to their satisfaction. If a group of
companies wish to 'fast-track' a work item (let people know it is
happening, but maintain a 'closed' group) that is also allowable.
The output of a closed group will be so identified. A 'closed'
group is defined as a company or group of companies who define
objects or ensembles which are not open to public comment in a
timely manner prior to registration. For the avoidance of doubt
at least three months should be allowed for open comment on
definition material, initially developed by 'closed' process,
placed on the Bulletin Board for the first time prior to intended
registration, for it to be subsequently adopted as 'open'. This
is regarded as a minimum, with the intention that the definition
material should be placed within the BB as early as possible
during development.
Material developed by recognised standards organisations or
industry consortia which have 'open membership' rules are not
subject to the above rules. However, for the purposes of making
their work more visible, they are encouraged to submit work to
the Bulletin Board during the development process.
To take advantage of the 'open' process, companies should adhere
to the following steps:-
Step 1 Formation
- The formation of a group, who have an interest in a
common topic area. Such groups should ideally be drawn from
across the supply chain (User + Service Provider + Equipment
vendor). The O Team should be the focus for a new group that
wishes to set up and will help to facilitate the process.
Step 2 Plan
- A plan of action should be drawn up by each group such
that the Summary Template (appendix A) can be filled in as far as
possible. The plan should outline the next key milestone for the
progression of the work from initial draft proposal to registered
(agreed) documents. This should be forwarded to the NMF office
so that it can be lodged on an open Bulletin Board of 'work in
progress'. This will help members of the industry to identify
early, any initiatives in which they may have an interest. Note
that the Summary Template can be lodged on the Bulletin Board in
advance of any initial definition work. The underlying purpose
for this is to give early visibility of work that is starting and
thus try to avoid unnecessary duplication of work.
Step 3 Development/Progression
- As the work of each group progresses, drafts of the
specifications should be lodged within the Bulletin Board
Directory Structure, so that interested parties may review and
comment on the work. It will be the team editor's responsibility
to ensure that these drafts are lodged, and notification to the
developers' email exploder is made, in a timely manner. Each
update should ensure that the status and next comment date are
identified within the summary template. Both the definition
information and the updated Summary Template should be lodged by
forwarding the information over email, if possible, to the NMF
office.
Step 4 Validation
When the group and any reviewers are satisfied that the ensemble
meets their needs a technical validation should be undertaken
against the criteria defined.
- The NMF O team will define the documents to be utilised at
any given point in the definition/technical validation process.
This will include at least:-
*The Technical Validation Criteria(NMF TR111)
*The Ensembles Concept and Format (NMF006)
*The Omnipoint 1 Libraries
*The Management Information Catalogue (for reference)
*The J Team Report(NMF TR102)
*Current documents on good modelling practices(TBA)
- The technical validation process would be one of 'self
certification' by the group. It is anticipated that the
validation process should include a syntax check (both ASN.1
and GDMO) on the managed objects submitted, a check to ensure
that the MOCS are consistent with the Managed Object definitions,
as well as a formal Quality Assurance audit prior to finalising
the submission, registration and forwarding to NMF. It may be
necessary to occasionally 'audit' some of the work to police
'good practice'. Essentially though, it is down to members'
reputation that they 'do a good job'.
Step 5 Submission.
Once validated the work, contained in separate emails, or on
floppy disc, should be submitted to NMF office for inclusion in
the appropriate directory file (see detailed instructions in
Appendix B)
Submission should include:-
* the completed Summary Template (Appendix A)
* the ensemble document, to the template prescribed in
NMF025, detailing the ensemble, the scenario, the objects which
the ensemble uses and any new objects that have been defined in
order that the ensemble meets user needs. If the ensemble has
been defined by open process within NMF, it should become an NMF
document and thus be in NMF format. If the ensemble has been
developed by another organisation, then that organisation's
document standards should apply, provided the document's template
conforms to NMF025. Please remember to insert the copyright
waiver notice (see Appendix C) at the beginning of the file.
* the object definitions not already included in the
Bulletin Board Directory system. Again remember to insert the
copyright waiver notice at the beginning of the file.
* a completed copyright waiver form, if the work is not
carried out within NMF. (see Appendix C).
* a patent declaration (see Appendix D) to declare whether
any patent or licence conditions apply to the submitted material.
As part of the ensemble submission process, the completed Summary
Template will be lodged in the appropriate Directory file by the
NMF. (See step 6)
Note, it is likely that ensembles that use dejure standards only
will gain wider take up and acceptance within the industry.
Ensembles containing new 'non-standardised' object definitions,
or object definitions not previously used in other ensembles, are
likely to meet with more scrutiny and are more likely to be
subject to audit than those using already available object
definitions.
Step 6 Publication.
NMF will manage within the Bulletin Board, the set of Directories
which hold information on completed and registered work, and work
in progress. NMF will lodge submission documents in the
appropriate Directory files and send out a message on the email
exploder when completed.
Appendix B shows the structure of the information that will be
held within the Bulletin Board.
DISCLAIMER:
-----------
The Network Management Forum does not make any effort to
determine whether or not the contents of the Bulletin Board
Directory files are accurate. Due to the inherent complexity in
the design and implementation of Managed Objects and ensembles,
no liability is accepted for any errors or omissions or for
consequences of any use made of the contents of these files.
Under no circumstances will the Network Management Forum, or
anyone acting on its behalf, be liable for direct, indirect,
special, incidental, consequential, or other damages or any costs
or losses resulting from access to, or use of the Bulletin Board.
Implementors are advised that they should obtain formal copies of
the documentation from the originating organisation and
appropriate releases for specific uses. Further, any
distribution of the information contained within this Bulletin
Board may not be for sale.
The information contained within the Bulletin Board Directory
files may involve a claim of patent rights and/or other
intellectual property rights by one or more of the contributors
of that information or by others. Inquiries should be directed to
the Network Management Forum office at 1201 Mt. Kemble Avenue,
Morristown, NJ USA 07960-6628, +1 201 425 1900.
Appendix A 3/94
Bulletin Board ENSEMBLE Summary Template (Abstract)
(Used while work in progress AND when completed)
Ensemble developers are expected to keep this summary as up to
date as possible during the development process. They should
give as much information as possible, even if tentative (which
should be acknowledged) in order that others can gain maximum
insight into the scope of the activity.
Ensemble Name:-
Date of last summary update: (dd/mm/yy)
Name/Email ID of person responsible for the summary update:
Status
(Initial proposal, draft, registered).
Next comment closing date (dd/mm/yy)
BB Directory name and File Name:
('N/A' if not yet lodged on the system)
Name of Group/Organisation/Companies defining the Ensemble:
Is/Was the Ensemble work carried out by open process?:Yes / No
Contact name/email id for further information:
Description of Ensemble scope:-
Business Reference Point addressed:
(Customer, Technology, Inter Service Provider)
Management Level:
(Element, Sub Network, Network/System, Service.
See ITU-T TMN M3010.)
Management Functions Employed:
(ISP's, NMF Functions, etc. Document Reference)
Resources Managed:
(Freeform description, of the actual resources being modelled)
Managed Object Classes employed: Names
(complete when definition completed)
Ensemble registered object ID:
(complete when definition complete)
Does the completed Ensemble include any objects not currently
registered AND held on the Bulletin Board?:Yes / No
Relationship to other Ensembles:
Names:
Description of relationship:
Date of (expected) completion:(dd/mm/yy)
Ensemble Document External Reference Label:
Which OMNIPoint is the Ensemble compatible with?:
(OP0, OP1)
Companies actively supporting the definition process:
Has the Ensemble been implemented? Yes / No
(State whether in prototype, beta product or purchasable product)
Is there a public domain implementation?: Yes / No
Contact Name/tel no/email id :
Has technical validation been completed yet?: Yes / No
Did this include an automated syntax check?
ASN.1 Yes / No
GDMO Yes / No
Was this validation undertaken by open or closed process?
Open/Closed
Do the supporting companies state that to the best of their
judgement the Ensemble meets the technical validation criteria?:
Yes / No
Names of companies/personnel making this statement:
Have you completed, signed and forwarded the Copyright Waiver
template? Yes / No / Not Required
(NR only if an NMF document)
Is any of the material submitted with this application the
subject of Patent Rights or Intellectual Property Rights such
that its public usage may be restricted, or subject to licence?
Yes/No/Not known
Have you completed, signed and forwarded the Patent Certification
template? Yes / No
Bulletin Board OBJECT LIBRARY Summary Template (Abstract) 3/94
(Used while work in progress AND when completed)
Object developers are expected to keep this summary as up to date
as possible during the development process. They should give as
much information as possible, even if tentative (which should be
acknowledged) in order that others can gain maximum insight into
the scope of the activity.
Object Library Name:-
Date of last summary update: (dd/mm/yy)
Name/Email ID of person responsible for the summary update:
Status
(Initial proposal, draft, registered).
Next comment closing date.(dd/mm/yy)
BB Directory name and File Name:
('N/A' if not yet lodged on the system)
Name of Group/Organisation/Companies defining the Object Library:
Is/Was the Object work carried out by open process?:Yes / No
Contact name/email id for further information:
Description of Object Library scope:-
Resources Managed:
(Freeform description, of the actual resources being modelled)
Managed Object Classes employed: Names
(complete when definition completed)
Date of (expected) completion:(dd/mm/yy)
Object Library Document External Reference Label:
(By which the document will be used in an object definition
reference)
Which OMNIPoint are the Objects compatible with?:
(OP0, OP1)
Companies actively supporting the definition process:
Have any of the Objects been implemented? Yes / No
(State whether in prototype, beta product or purchasable product)
Is there a public domain implementation?: Yes / No
Contact Name/tel no/email id :
Has technical validation been completed yet?: Yes / No
Did this include an automated syntax check?
ASN.1 Yes / No
GDMO Yes / No
Was this validation undertaken by open or closed process?
Open/Closed
Do the supporting companies state that to the best of their
judgement the Objects meet the technical validation criteria?:
Yes / No
Names of companies/personnel making this statement:
Have you completed, signed and forwarded the Copyright Waiver
template? Yes / No / Not Required
(NR only if an NMF document)
Is any of the material submitted with this application the
subject of Patent Rights or Intellectual Property Rights such
that its public usage may be restricted, or subject to licence?
Yes/No/Not known
Have you completed, signed and forwarded the Patent Certification
template? Yes / No
Appendix B: 3/94
INSTRUCTIONS FOR USING THE FORUM OBJECTS BULLETIN
BOARD
---------------------------------------------------------
PART 1: INSTRUCTIONS FOR USING THE NMF-OBJECTS EMAIL LIST
---------------------------------------------------------
The Network Management Forum (NMF) has established an email
exploder list known as "nmf-objects". This email list is
intended to enable dialogue between developers and users of
managed objects and ensembles specified using the OMNIPoint
process.
CHARTER:
--------
Problems, information, feedback, and general communication can
take place on a conversational basis using this email list.
Announcement messages and abstracts will be posted to this list
when new object/ensemble specification efforts are initiated, and
when new draft specifications are posted to the forum/objects
filestore. Lengthy, detailed discussion of specific
objects/ensembles should be taken off-line between interested
parties, although you are encouraged to use the general nmf-
objects email list to initiate such discussions. Refer to the
file /pub/forum/objects/misc/process.txt for additional
information regarding the object/ensemble specification process.
EMAIL SUBMISSION:
-----------------
To post a message to the email list, simply send an email message
to nmf-objects@thumper.bellcore.com. From within ATTMail, use the
address "internet!thumper.bellcore.com!nmf-objects".
This email list is not moderated; anything mailed to nmf-
objects@thumper.bellcore.com will get forwarded to the entire
email list. When posting messages, please keep in mind that
there may be many people on this email list, using a variety of
email access programs. As a courtesy to others, please do not
email object/ensemble specifications to the list; object/ensemble
specifications can be posted in the forum/objects filestore (see
instructions below). Email messages should be composed of flat
ASCII text, and should not contain binary attachments.
EMAIL ADMINISTRATION:
---------------------
Anyone can be added to or removed from this email list by sending
a message to nmf-objects-request@thumper.bellcore.com. Please
include your name, email address, organization, postal address,
and telephone number in the text of the subscribe/unsubscribe
message. Use only the nmf-objects-request address for list
administration requests; do not send administration request
messages to the nmf-objects email list.
----------------------------------------------------------
PART 2: INSTRUCTIONS FOR USING THE FORUM/OBJECTS FILESTORE
----------------------------------------------------------
The Network Management Forum (NMF) is maintaining a library of
documents on-line from a number of the organizations involved in
the development of managed object and ensemble modeling, using
the OMNIPoint process. These documents are available by
anonymous FTP from thumper.bellcore.com (128.96.41.1) in the
directory /pub/forum/objects. You must have FTP to access these
documents.
FILE RETRIEVAL:
---------------
To retrieve documents, establish an FTP connection to
thumper.bellcore.com and log in with the username "anonymous".
Enter your own email address as the password. After logging in,
type "cd /pub/forum/objects". At this point, you will have access
to all files stored in this directory and its subdirectories.
For those of you unfamiliar with FTP, here are a few basic
commands (a complete list of commands can be obtained by typing
"help"):
- The command "ls" lists all file and
subdirectory names in the current directory.
The command "ls -l" can be used to find out
when the files/directories were last updated.
- The command "cd dirname" can be used to
move to the subdirectory called "dirname".
The command "cd .." can be used to move back
up to the parent directory. The command
"cd/pub/forum/objects" can always be used
to return to top directory in the
forum/objects filestore.
- The command "get filename" retrieves the
file called "filename" from the current
directory. If you want the target file to
be named something else, supply a second
filename (i.e., "get sourcename targetname").
- The command "file type binary" should be
used before trying to retrieve files which
are in binary format (such as Word For
Windows documents).
- When you are done, type "quit" to logout.
Please check the file called "README" if it has been updated
since your last access of the filestore. The README file may
contain hints regarding recent changes or instructions on the use
of the filestore.
DIRECTORY ORGANIZATION:
-----------------------
The pub/forum/objects directory is organized as follows:
README Instructions on the use of the filestore
INDEX Current list of file and subdirectory names
obj-ens.lis Current list of objects and ensembles
and the filenames in which they are located
template.txt Template for object and ensemble abstracts
copyrite.wvr Blank copyright waiver form
notice.txt Template for "permission to distribute" notice
obj Subdirectory of object definitions (libraries)
ens Subdirectory of ensemble documents
misc Subdirectory of miscellaneous related
documents
OBJECTS (obj) AND ENSEMBLES (ens) SUBDIRECTORIES:
-------------------------------------------------
The pub/forum/objects/obj and /ens subdirectories are further
organized as follows:
draft Subdirectory containing draft
unregistered) material
reg Subdirectory containing registered material
The pub/forum/objects/obj subdirectory contains additional
information, as follows:
regxref.txt Cross-reference for all registered objects
regitree.txt Inheritance tree for all registered objects
regntree.txt Naming (containment) tree for all registered
objects
iimcdrft Subdirectory containing draft GDMO MIBs which
have been translated from Internet MIBs using
IIMC procedures. After review, these drafts
progress to registered status and are moved
to the obj/reg subdirectory. See
/pub/forum/objects/misc/process.txt
for more information on this process.
FILENAME CONVENTIONS:
---------------------
Files which contain Objects and Ensembles are named by
convention:
<organization name><document name>.<type>
2-4 chars 4+ chars 2-3c
The first 2-4 characters of the filename identify the sponsoring
organization, as shown below (additional orgs will be added as
needed):
nmf - Network Management Forum
oiw - OSE Implementors Workshop
osf - Open Software Foundation
ieee - IEEE
ansi - ANSI
iimc - NMF ISO/Internet Management Coexistence
iso - International Standards Organization
itu - International Telecommuncation Union(formerly CCITT)
The next series of characters identify the object or ensemble
document name. The first 4 characters of the document name must
be unique; additional characters can be used if desired but are
discouraged.
A 2-3 character filename extension indicates the file type:
txt - flat ASCII document
w51 - WordPerfect 5.1 document
doc - Word for Windows document
rtf - Rich Text Format document
ps - Postscript document
zip - Compressed file using MS-DOS Zip
Z - Compressed file using UNIX compress
tar - Archived file using UNIX tar
gdm - GDMO templates & ASN.1 syntax (in flat ASCII)
abs - Object or Ensemble Abstract (in flat ASCII)
For example:
obj/reg/isodmi.txt ISO 10165-2 DMI object
specification in
flat ASCII text format.
ens/draft/nmfcadm.zip Draft Customer Administration
Ensemble under development by
the NMF, compressed with MS-DOS
Zip. When unzipped, explodes
into nmfcadm.doc, a Word For
Windows binary.
ens/reg/nmfrcsc.abs Abstract describing the NM Forum
RCS Configuration Ensemble. The
ensemble document itself can be
found in other nmfrcsc.* files.
An abstract must exist for every
object and ensemble document.
obj/reg/nmfvol4.gdm The GDMO templates and ASN.1 syntax
modules specified by the NM Forum
OMNIPoint 1 Library Volume 4. The
entire object library document can
be found in other nmfvol4.* files.
A GDMO template file must exist for
every registered object library.
Each object or ensemble document may be posted in a variety of
formats or only a single format, as determined by the submitter
and the NM Forum.
MISCELLANEOUS SUBDIRECTORY (misc):
----------------------------------
The pub/forum/objects/misc subdirectory contains a flat
collection of files, each of which contains a relevant document
which is neither an object library nor an ensemble. The file
naming convention used for the /obj and /ens subdirectories is
also used for the /misc subdirectory when appropriate. For
example:
process.txt The process used for specifying
objects and ensembles, in ASCII
text format.
snmpMIBs.txt Current list of Internet MIB RFCs
available for use with SNMP.
howtoget.rfc Instructions on how to obtain RFCs
from other Internet filestores.
nmfenscon.doc The NM Forum Ensemble Concepts and
Formats Specification, in Word For
Windows binary format.
FILE SUBMISSION:
----------------
In order to post a file in the forum/objects directory, send the
file(s) to the NMF Office using one of the following methods:
- Email the files to office1@attmail.com via Internet
mail, or !office1 via ATTMail
- Send an MS-DOS or Mac compatible floppy disk to:
Network Management Forum
1201 Mt. Kemble Avenue
Morristown, New Jersey USA 07960-6628
The NMF Office can be reached by phone at +1 201 425 1900 to
answer questions prior to submitting a document for posting.
Your submission must include the following information:
- Submitter's Name, Organization, Postal Address,
Telephone Number, and Email Address.
- A list of file names with a description of each (what
the file contains, the file format, the source
organization, and the status - draft or registered).
The naming conventions shown above shall be used, and
the submission should indicate the target subdirectory
for the material (if known) and any existing files
being replaced by this submission.
- A completed Abstract form. Objects and Ensembles cannot
be posted without an Abstract. A template can be found
in the file /pub/forum/objects/template.txt.
- For object library documents, a list of object class
names (including the external document reference label)
must be provided (e.g., "CCITT Rec. X.721 | ISO 10165-2:
1992":system). For ensemble documents, a list of
object class names used by the ensemble must be
provided. Refer to the file
/pub/forum/objects/obj-ens.lis for examples.
- For copyrighted material, a signed copyright waiver
form. Copyrighted material cannot be posted without a
waiver permitting unlimited electronic access. A blank
copyright waiver form can be found in
/pub/forum/objects/copyrite.wvr.
- For object/ensemble definition material that:-
- has been defined by a single company or group
of companies, not utilising an 'open' process
(see step 3 of the Process document)
- or has been defined by a company or group of
companies by 'open' process but not under the
auspices of a recognised standards body or
industry consortia having open membership rules,
The Patent Disclosure Form (Appendix D) should also be
completed appropriately and included within the submission. A
blank Patent Disclosure form can be found in
/pub/forum/objects/Patent.dis.
When your file(s) has/have been posted, the NMF will send an
announcement message to the nmf-objects email list which
identifies the file name(s) and includes the abstract.
Draft files will be posted for no longer than 4 months from date
of submission, after which they will be automatically deleted.
(Draft files may be deleted sooner if replaced by new draft or
registered files in the interim.) Registered files will remain
posted indefinitely, subject to storage space limitations, etc.
TRANSLATED MIB SUBMISSION:
--------------------------
Draft translated MIBs are subject to special procedures, as
follows. Registered, RFC-defined Internet MIBs translated into
GDMO format using the IIMC procedures specified by
/pub/forum/objects/misc/iimcimib.* are assigned tentative object
identifiers during translation. Upon submission to the NMF
Office, draft MIB translations are checked for duplication and
syntax. Drafts which pass this check are posted in a separate
subdirectory (obj/iimcdrft) for a fixed-length review period of
four months. The purpose of the review period is to ensure the
translation is correct; defects (if any) shall be returned to the
submitter directly. After the review period completes, the
original submitter is responsible for re-submitting an updated
MIB which corrects any defects found, to the NMF Office. The
tentative object identifiers assigned during translation are
considered registered only after this process is successfully
completed, at which time the final translated MIB is posted in
the /obj/reg subdirectory.
DISCLAIMER:
-----------
The Network Management Forum does not make any effort to
determine whether or not the contents of the Bulletin Board
Directory files are accurate. Due to the inherent complexity in
the design and implementation of Managed Objects and ensembles,
no liability is accepted for any errors or omissions or for
consequences of any use made of the contents of these files.
Under no circumstances will the Network Management Forum, or
anyone acting on its behalf, be liable for direct, indirect,
special, incidental, consequential, or other damages or any costs
or losses resulting from access to, or use of the Bulletin Board.
Implementors are advised that they should obtain formal copies of
the documentation from the originating organisation and
appropriate releases for specific uses. Further, any
distribution of the information contained within this Bulletin
Board may not be for sale.
The information contained within the Bulletin Board Directory
files may involve a claim of patent rights and/or other
intellectual property rights by one or more of the contributors
of that information or by others. Inquiries should be directed to
the Network Management Forum office at 1201 Mt. Kemble Avenue,
Morristown, NJ USA 07960-6628, +1 201 425 1900.
Appendix C 3/94
THE NETWORK MANAGEMENT FORUM
Bulletin Board Copyright Waiver Form
The ____________________________________(Organisation/Company)
provides to the Network Management Forum (NMF) a copy of the
document entitled ______________________________________________
and grants the right to NMF to make copies and to make the
material publicly available to the industry via electronic or
other means.
Organisation/Company represents that it has the right to grant
these rights to the NMF.
The following notice will be required to appear at the beginning
of each file of registered object/ensemble definition material
mounted within the Bulletin Board file system.
"Copyright (C) (DATE) (Organisation/Company)
Permission to use, copy, modify, and distribute this material for
any purpose and without fee is hereby granted, provided that the
above copyright notice and this permission notice appear in all
copies, and that this material is not sold or distributed
commercially.
THE NMF MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR
SUITABILITY OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS
IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES."
The NMF disclaimer will always appear.
What (DATE) should be included .............................?
The (Organisation/Company) name will be as provided at the top of
this page.
__________________________________
Signature
For:_______________________________
(Organisation/Company)
_________________________________
Date
This form must be completed, signed and forwarded by fax to the
Network Management Forum (Fax: +1 201 425 1515) for each file of
object/ensemble definition material that the requestor wishes to
have published via the electronic
bulletin board file system.
Appendix D 3/94
PATENT DISCLOSURE FORM
IMPORTANT: PLEASE COMPLETE EITHER FORM "A" or FORM "B"
The Certification applies to the following documents:
referred to as "Bulletin Board Document" in the text below.
____________________________________________________________
CERTIFICATION FORM "A" NO PATENTABLE INTEREST
On behalf of____________________________________(Organisation/
Company), I hereby certify that
(1) Organisation/Company has used its reasonable efforts to
identify and disclose existing and/or potential patent rights
which it owns or has a right to use which affect the aforesaid
"Bulletin Board Document"
(2) Organisation/Company has reviewed the Bulletin Board Document
and
(3) Organisation/Company does not at this time have knowledge of
any rights it may have to any existing patents, patent
applications, and/or inventions made prior to this date which
affect or may affect any other Organisation/Company's ability to
practice the above Bulletin Board Document.
(4) Organisation/Company has/has not conducted a patent search to
determine possible patent rights of others. If it has, indicated
results below:
____________________________________________________________
____________________________________________________________
____________________________________________________________
Signed ____________________________________
Date _____________________________________
CERTIFICATION FORM "B" DECLARATION OF PATENTABLE 3/94
INTEREST
On behalf of _____________________________________(Organisation/
Company), I hereby certify that
(1) Organisation/Company has used its reasonable efforts, to
identify and disclose existing and/or potential patent rights
which it owns or has a right to use which affect the aforesaid
"Bulletin Board Document",
(2) Organisation/Company has reviewed the Bulletin Board Document
and
(3) Organisation/Company has uncovered and discloses the
inventions and patents identified on Exhibit A hereto (Please
include copies of all patents and patent applications, and
sufficient information about other inventions to specifically
identify the invention) as items which may possibly affect other
Organisation's/Company's ability to practice the above Bulletin
Board Document, and that aside from those items identified on
Exhibit A hereto, Organisation/Company does not at this time
have knowledge of any additional rights to any existing patent
applications and/or inventions made prior to this date which
affect or may affect other Organisations'/Companies' ability to
practice the above Bulletin Board Document.
Signed ___________________________________
Date ____________________________________
This form must be completed, signed and forwarded by fax to the
Network Management Forum (Fax: +1 201 425 1515) for each file of
object/ensemble definition material that the requestor wishes to
have published via the electronic bulletin board file system.