blank.gif (43 bytes)

Church Of The
Swimming Elephant

Search:
3.1. Generating a Request 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:

      Its authInfo component is constructed according to the authentication protocol specified for the originating party.

      In particular, if the authentication protocol for the originating SNMPv2 party is identified as noAuth, then this component corresponds to the OCTET STRING value of zero length.

      Its authData component is the constructed SnmpMgmtCom value.

  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:

      Its privDst component identifies the receiving SNMPv2 party.

      Its privData component is the (possibly encrypted) serialization of the SnmpAuthMsg value according to the conventions of [5].

      In particular, if the privacy protocol for the receiving SNMPv2 party is identified as noPriv, then the privData component is unencrypted. Otherwise, the privData component is processed according to the privacy protocol.

  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

Cotse.Net

Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!

Service Details

 
.
www.cotse.com
Have you gone to church today?
.
All pages ©1999, 2000, 2001, 2002, 2003 Church of the Swimming Elephant unless otherwise stated
Church of the Swimming Elephant©1999, 2000, 2001, 2002, 2003 Cotse.com.
Cotse.com is a wholly owned subsidiary of Packetderm, LLC.

Packetderm, LLC
210 Park Ave #308
Worcester, MA 01609