RFC 5590: Transport Subsystem for the Simple Network Management Protocol (SNMP)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC5590
- Published
- June 2009
- Authors
- D. Harrington; J. Schoenwaelder
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 34
- Also known as
- STD78
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5591Transport Security Model for the Simple Network Management Protocol (SNMP)Current
June 2009
- RFC 5592Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)Current
June 2009
- RFC 5607Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) ManagementCurrent
July 2009
- RFC 5675Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG MessagesCurrent
October 2009
- RFC 5676Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) NotificationsCurrent
October 2009
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 6765xDSL Multi-Pair Bonding (G.Bond) MIBCurrent
February 2013
- RFC 6766xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIBCurrent
February 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?