[rfc-dist] RFC 5592 on Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Jun 30 16:55:33 PDT 2009

A new Request for Comments is now available in online RFC libraries.

        RFC 5592

        Title:      Secure Shell Transport Model for 
                    the Simple Network Management Protocol (SNMP) 
        Author:     D. Harrington, J. Salowey,
                    W. Hardaker
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    ietfdbh at comcast.net, 
                    jsalowey at cisco.com, 
                    ietf at hardakers.net
        Pages:      36
        Characters: 82822
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isms-secshell-18.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5592.txt

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

This memo also defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets.  In particular, it defines objects for monitoring and
managing the Secure Shell Transport Model for SNMP.  [STANDARDS TRACK]

This document is a product of the Integrated Security Model for SNMP Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute

More information about the rfc-dist mailing list