ies of the agent implementation. The macro OBJECT-TYPE is used to provide the syntax and semantics for defining an object. The macro NOTIFICATION-TYPE is used to describe a notification. A notification is issued as confirmation for an event. Some new terms that have been introduced in RFC 1902 for SNMPv2. These include: BITS: Enumeration of named bits Unsigned32: Unsigned integer MAX-ACCESS: Maximum level of access allowed for an object Counter64: For keeping count UNITS: Textual units of measurements associated with an object AUGMENTS: Gives the object instance identification in a table. It is an alternative to the index clause. IMPLIED: For objects with a variable-length syntax In the hierarchy tree SnmpV2 has many subtrees. Some of these subtrees are: snmpDomains(1): It is for the domains used in transport mapping snmpProxys(2): It is used for giving the proxies used in SNMP transport snmpModules(3): It is used for defining the module identities. Under the snmpModules there is again three subtrees: snmpMIB(1): This is the agent-to-manager interaction MIB - snmpM2M(2): This is the manager-to-manager MIB partyMIB(3): This has been removed from the SNMPv2 MIB in RFC 1907. There are subtrees below the above levels also and further levels below these subtrees. "snmpMIB" under snmpModules, has snmpMIBObjects and snmp- MIBConformance subtrees. Below the snmpMIBObjects, we have snmpTrap(4), snmpTraps(5), and snmpSet(6). Management Information Base (MIB) 16.6 SNMPv3 MIB SNMPv3 has many additional objects introduced to account for the new security features that were introduced like the user-based security model and view-based access control model. Some of the MIB modules present in the object hierarchy of SNMPv3 are: snmpFrameworkMIB: This is used to define the MIB module for SNMPv3 architecture. The subtrees under it in addition to snmpFrameworkConfor- mance are: snmpFrameworkAdmin: This is used for the registration of SNMPv3 authentication and privacy protocol objects. snmpFrameworkMIBObjects: This is used to define S