RFC 2457: Definitions of Managed Objects for Extended Border Node
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 monitoring and controlling network devices with APPN (Advanced Peer-to-Peer Network) EBN (Extended Border Node) capabilities. This memo identifies managed objects for the EBN architecture. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2457
- Published
- November 1998
- Authors
- B. Clouston; B. Moore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2456Definitions of Managed Objects for APPN TRAPSCurrent
November 1998
- RFC 2455Definitions of Managed Objects for APPNCurrent
November 1998
- RFC 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 2238Definitions of Managed Objects for HPR using SMIv2Current
November 1997
- RFC 2232Definitions of Managed Objects for DLUR using SMIv2Current
November 1997
- RFC 2787Definitions of Managed Objects for the Virtual Router Redundancy ProtocolObsoleted
March 2000
- RFC 2932IPv4 Multicast Routing MIBObsoleted
October 2000
- RFC 2933Internet Group Management Protocol MIBObsoleted
October 2000
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?