The internet network management framework consists of three main components: MIB (Management Information Base), SMI (Structure of Management Information), and SNMP (Simple Network Management Protocol). While SMI defines the operations and variables related to MIB objects, ASN.1 (Abstract Syntax Notation One) is not included in the framework because of deviations in its implementation for SNMP, making it incompatible with general ASN.1 tools. Overall, the document argues that the existing components are sufficient for effective network management.

1. Internet network management framework as consisting of three major parts: MIB, SMI, SNMP.
To what extent do you believe this constitutes a framework? Are additional parts needed? Why
isn’t ASN.1 considered part of the framework?
Solution
In my opinion there major parts of the network management framework can be considered a
framework because each serves as a component within the network itself, with this said there are
no other parts needed. ASN.1, or abstract syntax notation 1, serves as a base for the SMI, SMI
has an ample amount of data types to be thought of as a separate entity.
SMI(structure of management Information) This is a format used to define operations and
variables related to objects in the MIB. SMI is more of a language then a structure and it is a
language used to define the management information. A cogent language is needed to ensure that
data is not vague. SNMP(Simple Network Management Protocol.) SNMP is a protocol used to
manage the management communications between devices. This is the short version of SNMP in
any case
ASN.1(Abstract Syntax Notation One) Is ". ..a standard and notation that describes rules and
structures for representing, encoding, transmitting, and decoding data in telecommunications and
computer networking
ASN.1 not considered part of the framework:
ASN.1 for SNMP, the group responsible for SNMP deviated from ASN.1 in various ways which
make it impossible for general purpose ASN.1 Tools to fully handle SNMP MIBs. They not only
use the withdrawn ASN.1 MACRO notation, but use it in such a way that even ASN.1 Tools
which still support the obsolete ASN.1 MACRO notation cannot properly handle the MIB
definitions. You need a special tool created specifically for SNMP MIBs to fully parse and
handle them properly