| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 5343, STD 78 | Simple Network Management Protocol (SNMP) Context EngineID Discovery | J. Schoenwaelder | September 2008 | Updates RFC 3411 | Internet Standard (was published as Proposed Standard ) | |
| RFC 5590, STD 78 | Transport Subsystem for the Simple Network Management Protocol (SNMP) | D. Harrington, J. Schoenwaelder | June 2009 | Updates RFC 3411, RFC 3412, RFC 3414, RFC 3417 | Internet Standard (was published as Proposed Standard ) | |
| RFC 5591, STD 78 | Transport Security Model for the Simple Network Management Protocol (SNMP) | D. Harrington, W. Hardaker | June 2009 | Internet Standard (was published as Proposed Standard ) | ||
| RFC 6353, STD 78 | Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) | W. Hardaker | July 2011 | Obsoletes RFC 5953, Updated by RFC 8996, RFC 9456 | Internet Standard (was published as Draft Standard ) |
Abstract of RFC 5343
The Simple Network Management Protocol (SNMP) version three (SNMPv3) requires that an application know the identifier (snmpEngineID) of the remote SNMP protocol engine in order to retrieve or manipulate objects maintained on the remote SNMP entity.
This document introduces a well-known localEngineID and a discovery mechanism that can be used to learn the snmpEngineID of a remote SNMP protocol engine. The proposed mechanism is independent of the features provided by SNMP security models and may also be used by other protocol interfaces providing access to managed objects.
This document updates RFC 3411. [STANDARDS-TRACK]
Abstract of RFC 5590
This document defines a Transport Subsystem, extending the Simple Network Management Protocol (SNMP) architecture defined in RFC 3411. This document defines a subsystem to contain Transport Models that is comparable to other subsystems in the RFC 3411 architecture. As work is being done to expand the transports to include secure transports, such as the Secure Shell (SSH) Protocol and Transport Layer Security (TLS), using a subsystem will enable consistent design and modularity of such Transport Models. This document identifies and describes some key aspects that need to be considered for any Transport Model for SNMP. [STANDARDS-TRACK]
Abstract of RFC 5591
This memo describes a Transport Security Model for the Simple Network Management Protocol (SNMP).
This memo also defines a portion of the Management Information Base (MIB) for monitoring and managing the Transport Security Model for SNMP. [STANDARDS-TRACK]
Abstract of RFC 6353
This document describes a Transport Model for the Simple Network Management Protocol (SNMP), that uses either the Transport Layer Security protocol or the Datagram Transport Layer Security (DTLS) protocol. The TLS and DTLS protocols provide authentication and privacy services for SNMP applications. This document describes how the TLS Transport Model (TLSTM) implements the needed features of an SNMP Transport Subsystem to make this protection possible in an interoperable way.
This Transport Model is designed to meet the security and operational needs of network administrators. It supports the sending of SNMP messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of TCP's improved support for larger packet sizes and the DTLS mode provides potentially superior operation in environments where a connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS integrate well into existing public keying infrastructures.
This document also defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it defines objects for managing the TLS Transport Model for SNMP. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.