References

1. Manual pages: octetstring(3snmp), oid(3snmp), smux_api(3snmp), smux_pdu(3snmp), smux_util(3snmp), snmp_authentication(3snmp), snmp_pdu(3snmp), varbind(3snmp), mosy(1Msnmp), post_mosy(1Msnmp), snmpd.peers(4snmp), snmpd.comm(4snmp)

2. ``Configuring the Simple Network Management Protocol (SNMP)''

3. Rose, Marshall T. (1991) The Simple Book; Prentice Hall, Englewood Cliffs NJ. ISBN: 0-13-812611-9.

4. RFC 1155, ``Structure and Identification of Management Information for TCP/IP-based Internets''; Marshall Rose and K. McCloghrie.

5. RFC 1156, ``Management Information Base for Network Management of TCP/IP-based Internets'' K. McCloghrie and M. Rose.

6. RFC 1157, ``A Simple Network Management Protocol (SNMP)'' J. Case, M. Fedor, H. Schoffstall, and J. Davin.

7. RFC 1212, ``Concise MIB Definitions'' Marshall Rose and K. McCloghrie.

8. RFC 1213, ``Management Information Base for Network Management of TCP/IP-based Internets: MIB-II'' K. McCloghrie and M. Rose.

9. RFC 1227, ``SNMP MUX Protocol and MIB'' M. Rose.

• Paper copies of all RFCs are available either individually or on a subscription basis (for more information contact nisc@nisc.sri.com or call 1-415-859-6387).

• Online copies are available via FTP from ftp.nisc.sri.com as rfc/rfc####.txt or rfc/rfc####.ps (####  is the RFC number without leading zeroes).

• Additionally, RFCs may be requested through electronic mail from SRI's automated mail server by sending a message to mail-server@nisc.sri.com. In the body of the message, indicate the RFC to be sent, e.g. ``send rfcNNNN'' where NNNN is the number of the RFC. For PostScript RFCs, specify the extension, e.g. ``send rfcNNNN.ps''. Multiple requests can be sent in a single message by specifying each request on a separate line. The RFC Index can be requested by typing ``send rfc-index''.

or Keith Sklower:

sklower@vangogh.cs.berkeley.edu