Question

Read Request for Comment IETF RFC 1155 and 1157 specifying the network management protocol standard and for each document provide a 2-page summary of its contents.

Answer 1

First we will discuss about IETF RFC 1155

For NETWORK MANAGEMENT PROTOCOL first we have to disscuss THE NETWORK ADDRESS of IETF RFC 1155

NETWORK ADDRESS

THIS CHOICE REPRESENT AN ADDRESS FROM one of possibly several protocol families. Currently, only one protocol family, the Internet family, is present in this CHOICE.

IP-ADDRESS

This application-wide type represents a 32-bit internet address.  It
is represented as an OCTET STRING type of length 4 unit in network bite order

  this ASN.1 type is encoded using the ASN.1 basic encoding rules,

only the primitive encoding from shall be used.

  now we will disscuss about the management process of IEFT RFC 1155

Managed Objects

this application wide type represents a non-negative type integer which counts the time in hundredths of second since some epoch. when object type are defined in the MTB which use in ASN1. type so from this we can understand that the description of the object type identifies the refference epoch. although it is not the purpose of this memo to define objects in the MIB, this memo specifies a format to be used by other memos which define these objects. An object type definition consists of five fields: OBJECT: ------- A textual name, termed the OBJECT DESCRIPTOR, for the object type, along with its corresponding OBJECT IDENTIFIER. Syntax: The abstract syntax for the object type. This must resolve to an instance of the ASN.1 type ObjectSyntax (defined below). Definition: A textual description of the semantics of the object type. Implementations should ensure that their instance of the object fulfills this definition since this MIB is intended for use in multi-vendor environments. As such it is vital that objects have consistent meaning across all machines. Access: One of read-only, read-write, write-only, or not-accessible. Status: One of mandatory, optional, or obsolete. Future memos may also specify other fields for the objects which they define.

Thus we will under stand the total managerial concept of IETF RFC 1155

Now we will discuss about the protocol standard of IETF 1157

It is very instrasting to know that the protocal standered of IETF 1157 and the application of it.

here we going to brife summary of 1157 specification of protocol. a system language is needed to use for this .

The protocol entity then performs a rudimentary parse on
             the ASN.1 object returned from the authentication service
             to build an ASN.1 object corresponding to an ASN.1 PDUs
             object.  If the parse fails, it discards the datagram and
             performs no further actions.  Otherwise, using the named
             SNMP community, the appropriate profile is selected, and
             the PDU is processed accordingly.  If, as a result of
             this processing, a message is returned then the source
             transport address that the response message is sent from
             shall be identical to the destination transport address
             that the original request message was sent to.

NOTE -- UNDER LINE ARE DORE FOR BETTER UNDERSTANDING OF THE SYSYEM PROGRAMME.

The network management protocol is an application protocol by which
   the variables of an agent's MIB may be inspected or altered.

   Communication among protocol entities is accomplished by the exchange
   of messages, each of which is entirely and independently represented
   within a single UDP datagram using the basic encoding rules of ASN.1
   (as discussed in Section 3.2.2).  A message consists of a version
   identifier, an SNMP community name, and a protocol data unit (PDU).
   A protocol entity receives messages at UDP port 161 on the host with
   which it is associated for all messages except for those which report
   traps (i.e., all messages except those which contain the Trap-PDU).
   Messages which report traps should be received on UDP port 162 for
   further processing.  An implementation of this protocol need not
   accept messages whose length exceeds 484 octets.  However, it is
   recommended that implementations support larger datagrams whenever
   feasible.

   It is mandatory that all implementations of the SNMP support the five
   PDUs:  GetRequest-PDU, GetNextRequest-PDU, GetResponse-PDU,
   SetRequest-PDU, and Trap-PDU.

    RFC1157-SNMP DEFINITIONS ::= BEGIN

     IMPORTS
          ObjectName, ObjectSyntax, NetworkAddress, IpAddress, TimeTicks
                  FROM RFC1155-SMI;


     -- top-level message

             Message ::=
                     SEQUENCE {
                          version        -- version-1 for this RFC
                             INTEGER {
                                 version-1(0)
                             },

                         community      -- community name
                             OCTET STRING,

                         data           -- e.g., PDUs if trivial
                             ANY        -- authentication is being used
                     }






Case, Fedor, Schoffstall, & Davin 
RFC 1157 SNMP May 1990


     -- protocol data units

             PDUs ::=
                     CHOICE {
                         get-request
                             GetRequest-PDU,

                         get-next-request
                             GetNextRequest-PDU,

                         get-response
                             GetResponse-PDU,

                         set-request
                             SetRequest-PDU,

                         trap
                             Trap-PDU
                          }

     -- the individual PDUs and commonly used
     -- data types will be defined later

So the protocol type are discuss brifely with the help of the system programming