> I'd like to see an extensible model that can be partially implemented,
> based on your choice. So maybe syslog (for example) is a
[...]
>
> So, one other thing that I'm trying to absorb from other posts - what are
> the pros and cons for (1) let the network elements/devices specify the
> model - which would be different for different devices/vendors, or (2)
> make a general model into which all devices/vendors can be fit. I think
The "extensible model" that you really want makes the difference
between 1 and 2 irrelevent. A "good extensible model" is a sufficient
tool to relate models to one another. If your vendor gives you a
model, cool! They just make your job much easier.
In general, a good extensible model encourages you to produce a
lightweight "your version of theirs" if the vendor doen't give you
anything reasonable. This is easier than trying to smash something
with too much irrelevant information directly into the correct form.
If the vendor gives you something reasonable, assimilate it.
Follow-Ups:
References:
|
|
