| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 06 Oct 2025 21:45:20 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=UmRrHnDfoRv_CUBkhIuzOubWdaaviBPuXM4fMLYzaK0-1759787120-1.0.1.1-3eH5CKt1WgFzXL59s5ba_j_UUINjRZSCJGWPN_OVF24HhaKPldGfLN878QXfy8DSs8Q7DamCQ_Z1V5qT5y4McyljEACyvMTkiQCKhcHRBDg; path=/; expires=Mon, 06-Oct-25 22:15:20 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98a85856eb7ac143-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5591 » RFC Editor
Search RFCs
STD 78
RFC 5591
Transport Security Model for the Simple Network Management Protocol (SNMP), June 2009
- File formats:
- Status:
- INTERNET STANDARD (changed from PROPOSED STANDARD)
- Authors:
- D. Harrington
W. Hardaker - Stream:
- IETF
- Source:
- isms (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5591
Discuss this RFC: Send questions or comments to the mailing list isms@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5591
Abstract
This memo describes a Transport Security Model for the Simple Network Management Protocol (SNMP).
This memo also defines a portion of the Management Information Base (MIB) for monitoring and managing the Transport Security Model for SNMP. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us