Connected: An Internet Encyclopedia
3.1. Generating a Request

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1445
Up: 3. Elements of Procedure
Prev: 3. Elements of Procedure
Next: 3.2. Processing a Received Communication

3.1. Generating a Request

3.1. Generating a Request

This section describes the procedure followed by a SNMPv2 entity whenever either a management request or a trap notification is to be transmitted by a SNMPv2 party.

  1. A SnmpMgmtCom value is constructed for which the srcParty component identifies the originating party, for which the dstParty component identifies the receiving party, for which the context component identifies the desired SNMPv2 context, and for which the pdu component represents the desired management operation.

  2. The local database of party information is consulted to determine the authentication protocol and other relevant information for the originating and receiving SNMPv2 parties.

  3. A SnmpAuthMsg value is constructed with the following properties:

  4. The local database of party information is consulted to determine the privacy protocol and other relevant information for the receiving SNMPv2 party.

  5. A SnmpPrivMsg value is constructed with the following properties:

  6. The constructed SnmpPrivMsg value is serialized according to the conventions of [5].

  7. The serialized SnmpPrivMsg value is transmitted using the transport address and transport domain for the receiving SNMPv2 party.

Note that the above procedure does not include any application of any SNMPv2 access control policy (see section 2.13).


Next: 3.2. Processing a Received Communication

Connected: An Internet Encyclopedia
3.1. Generating a Request