Reference models and Network Management

Craig Partridge (craig@NNSC.NSF.NET)
Mon, 12 Sep 88 09:31:51 -0400

> The only thing good about the ISORM, or the TCP/IP model, is
> that it gives us a map (no pun :-) and a glossary for conversing about
> protocols. Neither model seems entirely adequate. Network
> management, for example, seems to have broken both models. [no
> flames, please]. Thankfully, that doesn't stop the implementors or
> protocol-builders.


    I don't think network management has broken the models -- my view is
that network management has reminded us that the models are maps, not

    The key layer/model problem that I see in network management is that
management applications (at whatever layer you put them) expect to be
able to get an information in any network layer -- i.e. strict layering
in which only the N+1 and N-1 layer communicate with the N layer doesn't
hold. The other thing that network management does is force you to make
the internal workings of the layer visible. This approach distresses the
folks who liked the black-box approach to layering (well defined interface to
a box you can't peek into) -- but is hardly surprising to implementors.


This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:43:15 GMT