Harry Lewis
----- Forwarded by Harry Lewis ------
owner-pwg@pwg.org on 12/02/97 12:54:27 PM
Please respond to owner-pwg@pwg.org @ internet
To: don@lexmark.com @ internet, jkm@underscore.com @ internet
cc: JMP@pwg.org @ internet, pwg@pwg.org @ internet
Subject: PWG> Re: JMP> Structuring of the PWG enterprise OID tree
I started to edit the Job Monitoring MIB with the PWG standard OIDs
as proposed, even though I preferred Harry's flat OID approach.
However, when discussing how to write it in SNMP ASN.1 with Ira,
we realized that maybe the PWG ought to distinguish between
PWG experimental OIDs and PWG standard OIDs, just like with the
IETF MIBs.
So we propose the following:
Under iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
we have separate trees for PWG experimental and PWG standard:
pwg(2699) pwgstandard(1) jobmon(1)
pwg(2699) pwgexperimental(2) jobmon(1)
Our current jobmon MIB is so near to becoming a PWG standard that
we don't need this distinction. We haven't changed an OID during the
last six months of drafts. However, just to be safe, I'm going to
publish the next draft using the pwgexperimental(2) arc. Then if we
decide that the above OID scheme isn't any good, we can change it.
Experimental OIDs are free to be changed from draft to draft, but
standard ones are not.
The idea of pwgstandard OIDs is that the OIDs never change after being
published, just like the IETF. (Adding new OIDs can be done to
standards, that is NOT changing published OIDs).
We also propose NOT to asign arc to PWG projects, but to actual PWG
needs, in this case the jobmon mib. Thus a project can get one or
more arcs assigned, depending on its needs. Also OIDs can be assigned
for non-MIB purposes as well.
Another advantage to this approach, is that we don't need to decide
now what categories we might want in the future.
Ok?
Tom
=