metasystema.org
UpdatedINTERNET STANDARDIETF streamSTD78

RFC 6353: Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)

Still current, but amended. Parts of this document are changed or extended by RFC 8996, RFC 9456. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6353
Published
July 2011
Authors
W. Hardaker
Status
INTERNET STANDARD
Stream
IETF
Area
app
Pages
65
Also known as
STD78
Obsoletes:
RFC 5953
Updated by:
RFC 8996, RFC 9456

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6353-transport-layer-security-tls-transport-model-for-the-simple-network-management-p