RFC 5343: Simple Network Management Protocol (SNMP) Context EngineID Discovery
In plain English — editorial summary, not part of the RFC
The Simple Network Management Protocol (SNMP) version three (SNMPv3) requires that an application know the identifier (snmpEngineID) of the remote SNMP protocol engine in order to retrieve or manipulate objects maintained on the remote SNMP entity. This document introduces a well-known localEngineID and a discovery mechanism that can be used to learn the snmpEngineID of a remote SNMP protocol engine. The proposed mechanism is independent of the features provided by SNMP security models and may also be used by other protocol interfaces providing access to managed objects. This document updates RFC 3411. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5343
- Published
- September 2008
- Authors
- J. Schoenwaelder
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- STD78
- Updates:
- RFC 3411
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3410Introduction and Applicability Statements for Internet-Standard Management FrameworkCurrent
December 2002
- RFC 2265View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)Obsoleted
January 1998
- RFC 2262Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)Obsoleted
January 1998
- RFC 2261An Architecture for Describing SNMP Management FrameworksObsoleted
January 1998
- RFC 9456Updates to the TLS Transport Model for SNMPCurrent
November 2023
- RFC 5357A Two-Way Active Measurement Protocol (TWAMP)Updated
October 2008
- RFC 5358Preventing Use of Recursive Nameservers in Reflector AttacksCurrent
October 2008
- RFC 5324MIB for Fibre-Channel Security Protocols (FC-SP)Current
September 2008
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?