[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Another SMIv2 question
I have this discussed with the SMIv2 editors and with
several other people when the Diffserv MIB was reviewed
(not by just one MIB doctor, but by quite a few).
Discussion actually took place on the diffserv mailing
list. In retrospect, I should have at least alerted the
mibs mailing list... oh well... that is too late now.
Other WGs have asked for permission to just use
Counter64 as well.
I am collecting a number of rules/guidelines and the
results of some discussions with the SMIv2 editors and
other mib doctors. I intend to collect them into an
I-D that we can then discuss. That discussion then will
be to see if we have rough IETF consensus to relax
the rules/guidelines we've been using.
So... formally I guess the rules as per SMIv2 are still
in effect. Hope this helps/explains
Bert
> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
> Sent: Tuesday, November 06, 2001 9:33 PM
> To: remoore@us.ibm.com
> Cc: mibs@ops.ietf.org
> Subject: Re: Another SMIv2 question
>
>
>
> >>>>> Robert Moore writes:
>
> [...]
>
> Robert> Second, while I have no objections at all to this new way of
> Robert> using Counter64's, I do worry about these silent, de facto
> Robert> amendments to the SMI. We can say we'll "get it all right" in
> Robert> sming, but meanwhile, how is someone supposed to know what the
> Robert> rules are for defining a semantically valid MIB module?
>
> I hope that SMIng will not have these kind of rules at all. This rule
> is an example of an IETF policy rule which should be defined in a
> guidelines document rather than being hard-wired in the language
> itself. Note that nothing breaks in terms of interoperability or
> Counter semantics if you change or remove this rule. So moving these
> IETF policy rules out of the SMI into a guidelines document allows to
> adapt these rules over time.
>
> Not sure what we do until we have SMIng in place. Perhaps we need a
> guidelines document for SMIv2 as well which says "this is the policy
> rule defined in 1999 as part of SMIv2 but this how we now look at the
> issue and this is the new policy rule".
>
> /js
>
> --
> Juergen Schoenwaelder Technical University Braunschweig
> <schoenw@ibr.cs.tu-bs.de> Dept. Operating Systems & Computer Networks
> Phone: +49 531 391 3289 Muehlenpfordtstr. 23, 38106
> Braunschweig, Germany
> Fax: +49 531 391 5936 <http://www.ibr.cs.tu-bs.de/~schoenw/>
>
>
>