Re: Methods in the NIM requirements

["Lakshmi Raman" <lraman@telcordia.com>]

comments in line




Keith McCloghrie <kzm@cisco.com> on 05/01/2000 07:47:26 PM

To:   WWeiss@lucentctc.com (Weiss Walter)
cc:   lraman@telcordia.com ('Lakshmi Raman'), nim@ops.ietf.org (bcc: Lakshmi
      Raman/Telcordia)
Subject:  Re: Methods in the NIM requirements




>  ...  If I understand your
> comments below, you would describe attributes as any element that is
> persistent for the life of the object.

There are attributes which do not have values for the life of an object.
For example, interval counters do not have values between the birth of
an object and the expiry of an interval timer.  Similarly, it seems
reasonable that an attribute's value could have a TTL, and you should
be able to read it while it's still valid.
<LR> No that is not what I meant. if an attribute has a zero value as in the
previous case, you
would include it as an attribute.
It is still a property that is part of the object and exists for its life time.

> Attributes can be read or written

or both.
>LR> yes

> Methods deal with cross-object interactions.

If "clear an object's counters" were allowed, wouldn't it be a method,
but have no interaction with any other object ??
<LR> yes. It can be a method and it was never meant to exclude the case
where a single object is impacted. Again that was an example as we seem
to looking for guidelines.

Keith.