ill provide partial results. Inform: This operation was introduced to facilitate interaction between net- work managers. In a distributed environment where one manager wants to send a message to another manager, then the Inform operation can be used. It is also used for sending notifications similar to a trap. Inform is a "confirmed trap" operation. The PDUs GetRequest, GetNextRequest, SetRequest, Trap, Inform, and GetResponse have the format shown below: PDU Type Request ID Error Status Error Index Variable Bindings PDU type is used to identify the type of PDU, whether it is a GetRequest, SetRequest, GetResponse, and SO on. Request ID will associate an SNMP response with its corresponding request. Error Status and Error Index is used to describe the error scenario for an operation similar to SNMPv1 PDU. Variable bindings serves the same purpose as in SNMPvl to give variable- value pairs. The GetBulk PDU in SNMPv2 has a different format to handle bulks of data: Request Nonrepeaters Variable Repetitions Bindings PDU Type always corresponds to GetBulk PDU. Request ID is to associate a bulk response with the correct request. Nonrepeaters (N) and Max Repetitions (M): Before we explain these two fields it should be clear that the GetBulk operation is similar to perform- ing the GetNext operation multiple times. While GetNext operation just returns the next object, the GetBulk performs the GetNext multiple times based on N and M values to get a bulk of data. The first N elements of the variable binding list are treated as a normal GetNext operation and the next elements are considered as consisting of M number of repeated GetNext operation. Variable bindings serves the same purpose as in SNMPvl to give variable- value pairs. SNMPv2 also introduced "Report PDU." The intent of the report PDU is to account for administrative requirements. A report PDU could be used for faster recovery by sending information for time synchronization. It is not defined in SNMPv2 PDU definitions listed in RFC 1905. Implementers can define th