RFC 1503: Algorithms for Automating Administration in SNMPv2 Managers
In plain English — editorial summary, not part of the RFC
When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1503
- Published
- August 1993
- Authors
- K. McCloghrie; M. Rose
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1604Definitions of Managed Objects for Frame Relay ServiceObsoleted
March 1994
- RFC 1643Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
July 1994
- RFC 1666Definitions of Managed Objects for SNA NAUs using SMIv2Current
August 1994
- RFC 1748IEEE 802.5 MIB using SMIv2Updated
December 1994
- RFC 1514Host Resources MIBObsoleted
September 1993
- RFC 1515Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)Obsoleted
September 1993
- RFC 1516Definitions of Managed Objects for IEEE 802.3 Repeater DevicesObsoleted
September 1993
- RFC 1525Definitions of Managed Objects for Source Routing BridgesCurrent
September 1993
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?