RFC 4088: Uniform Resource Identifier (URI) Scheme for the Simple Network Management Protocol (SNMP)
In plain English — editorial summary, not part of the RFC
The Simple Network Management Protocol (SNMP) and the Internet Standard Management Framework are widely used for the management of communication devices, creating a need to specify SNMP access (including access to SNMP MIB object instances) from non-SNMP management environments. For example, when out-of-band IP management is used via a separate management interface (e.g., for a device that does not support in-band IP access), a uniform way to indicate how to contact the device for management is needed. Uniform Resource Identifiers (URIs) fit this need well, as they allow a single text string to indicate a management access communication endpoint for a wide variety of IP-based protocols. This document defines a URI scheme so that SNMP can be designated as the protocol used for management. The scheme also allows a URI to designate one or more MIB object instances. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4088
- Published
- June 2005
- Authors
- D. Black; K. McCloghrie; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 2557MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)Current
March 1999
- RFC 4095Attaching Meaning to Solicitation Class KeywordsCurrent
May 2005
- RFC 4078The TV-Anytime Content Reference Identifier (CRID)Current
May 2005
- RFC 3987Internationalized Resource Identifiers (IRIs)Current
January 2005
- RFC 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
- RFC 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 3953Telephone Number Mapping (ENUM) Service Registration for Presence ServicesUpdated
January 2005
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?