RFC 2051: Definitions of Managed Objects for APPC using SMIv2
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and controlling of network devices with APPC (Advanced Program-to-Program Communications) capabilities. This memo identifies managed objects for the SNA LU6.2 protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2051
- Published
- October 1996
- Authors
- M. Allen; B. Clouston; Z. Kielczewski; W. Kwan; B. Moore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 124
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2024Definitions of Managed Objects for Data Link Switching using SMIv2Current
October 1996
- RFC 2080RIPng for IPv6Current
January 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 2091Triggered Extensions to RIP to Support Demand CircuitsCurrent
January 1997
- RFC 2092Protocol Analysis for Triggered RIPCurrent
January 1997
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 2102Multicast Support for Nimrod : Requirements and Solution ApproachesCurrent
February 1997
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?