Skip to main content

Transport Mappings for the Simple Network Management Protocol (SNMP)

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3417.
Author Randy Presuhn
Last updated 2015-10-14 (Latest revision 2001-10-16)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Internet Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3417 (Internet Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Randy Bush
IESG note
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        STD 62
        RFC 3417
        Title:      Transport Mappings for the Simple Network
                    Management Protocol (SNMP)
        Author(s):  R. Presuhn, Ed.
        Status:     Standards Track
        Date:       December 2002
        Pages:      19
        Characters: 38650
        Obsoletes:  1906
        See Also:   STD 62
        I-D Tag:    draft-ietf-snmpv3-update-transmap-08.txt


This document defines the transport of Simple Network Management
Protocol (SNMP) messages over various protocols.  This document
obsoletes RFC 1906.

This document is a product of the SNMPv3 Working Gr oup of the IETF.

This is now a Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.