RFC 9456: Updates to the TLS Transport Model for SNMP
In plain English — editorial summary, not part of the RFC
This document updates RFC 6353 ("Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)") to reflect changes necessary to support Transport Layer Security version 1.3 (TLS 1.3) and Datagram Transport Layer Security version 1.3 (DTLS 1.3), which are jointly known as "(D)TLS 1.3". This document is compatible with (D)TLS 1.2 and is intended to be compatible with future versions of SNMP and (D)TLS. This document updates the SNMP-TLS-TM-MIB as defined in RFC 6353.
Document record
- Document ID
- RFC9456
- Published
- November 2023
- Authors
- K. Vaughn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 30
- Also known as
- —
- Updates:
- RFC 6353
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2618RADIUS Authentication Client MIBObsoleted
June 1999
- RFC 2261An Architecture for Describing SNMP Management FrameworksObsoleted
January 1998
- RFC 9185DTLS Tunnel between a Media Distributor and Key Distributor to Facilitate Key ExchangeCurrent
April 2022
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 5953Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)Obsoleted
August 2010
- RFC 9323A Profile for RPKI Signed Checklists (RSCs)Current
November 2022
- RFC 9691A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs)Current
December 2024
- RFC 9099Operational Security Considerations for IPv6 NetworksCurrent
August 2021
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?