RFC 5592: Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)

This memo describes a Transport Model for the Simple Network Management Protocol (SNMP), using the Secure Shell (SSH) protocol. This memo also defines a…

Read RFC 5592 on the RFC Editor

Outgoing relationships (26 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2578: Structure of Management Information Version 2 (SMIv2)
Normative reference — RFC 2579: Textual Conventions for SMIv2
Normative reference — RFC 2580: Conformance Statements for SMIv2
Normative reference — RFC 3411: An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks
Normative reference — RFC 3490: Internationalizing Domain Names in Applications (IDNA)
Normative reference — RFC 3414: User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
Normative reference — RFC 4252: The Secure Shell (SSH) Authentication Protocol
Normative reference — RFC 4251: The Secure Shell (SSH) Protocol Architecture
Normative reference — RFC 4253: The Secure Shell (SSH) Transport Layer Protocol
Normative reference — RFC 3418: Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
Normative reference — RFC 3413: Simple Network Management Protocol (SNMP) Applications
Normative reference — RFC 4254: The Secure Shell (SSH) Connection Protocol
Normative reference — RFC 1033: Domain Administrators Operations Guide
Normative reference — RFC 3584: Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
Normative reference — RFC 5590: Transport Subsystem for the Simple Network Management Protocol (SNMP)
Informative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Informative reference — RFC 3410: Introduction and Applicability Statements for Internet-Standard Management Framework
Informative reference — RFC 2865: Remote Authentication Dial In User Service (RADIUS)
Informative reference — RFC 3588: Diameter Base Protocol
Informative reference — RFC 5591: Transport Security Model for the Simple Network Management Protocol (SNMP)
Informative reference — RFC 1994: PPP Challenge Handshake Authentication Protocol (CHAP)
Informative reference — RFC 4742: Using the NETCONF Configuration Protocol over Secure SHell (SSH)
Informative reference — RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol
Informative reference — RFC 5090: RADIUS Extension for Digest Authentication
Informative reference — RFC 4256: Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)

Incoming relationships (27 related RFCs)

Normatively referenced by — RFC 6933: Entity MIB (Version 4)
Normatively referenced by — RFC 7460: Monitoring and Control MIB for Power and Energy
Normatively referenced by — RFC 7461: Energy Object Context MIB
Normatively referenced by — RFC 7659: Definitions of Managed Objects for Network Address Translators (NATs)
Normatively referenced by — RFC 6850: Definitions of Managed Objects for Routing Bridges (RBridges)
Normatively referenced by — RFC 7184: Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2
Normatively referenced by — RFC 7577: Definition of Managed Objects for Battery Monitoring
Normatively referenced by — RFC 7784: Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIB
Normatively referenced by — RFC 7939: Definition of Managed Objects for the Neighborhood Discovery Protocol
Normatively referenced by — RFC 9349: Definitions of Managed Objects for IP Traffic Flow Security
Normatively referenced by — RFC 7147: Definitions of Managed Objects for the Internet Small Computer System Interface (iSCSI)
Normatively referenced by — RFC 7856: Softwire Mesh Management Information Base (MIB)
Normatively referenced by — RFC 7870: Dual-Stack Lite (DS-Lite) Management Information Base (MIB) for Address Family Transition Routers (AFTRs)
Informatively referenced by — RFC 6353: Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)
Informatively referenced by — RFC 6615: Definitions of Managed Objects for IP Flow Information Export
Informatively referenced by — RFC 5590: Transport Subsystem for the Simple Network Management Protocol (SNMP)
Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
Informatively referenced by — RFC 6779: Definition of Managed Objects for the Neighborhood Discovery Protocol
Informatively referenced by — RFC 5608: Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models
Informatively referenced by — RFC 6475: Proxy Mobile IPv6 Management Information Base
Informatively referenced by — RFC 6825: Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS
Informatively referenced by — RFC 8038: Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol
Informatively referenced by — RFC 6945: Definitions of Managed Objects for the Resource Public Key Infrastructure (RPKI) to Router Protocol
Informatively referenced by — RFC 7124: Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
Informatively referenced by — RFC 7453: MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)
Informatively referenced by — RFC 8173: Precision Time Protocol Version 2 (PTPv2) Management Information Base
Informatively referenced by — RFC 9675: Delay-Tolerant Networking Management Architecture (DTNMA)