RFC 1724: RIP Version 2 MIB Extension
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 TCP/IP-based internets. In particular, it defines objects for managing RIP Version 2. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1724
- Published
- November 1994
- Authors
- G. Malkin; F. Baker
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
- Obsoletes:
- RFC 1389
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- RFC 1657Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2Obsoleted
July 1994
- RFC 2024Definitions of Managed Objects for Data Link Switching using SMIv2Current
October 1996
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 1743IEEE 802.5 MIB using SMIv2Obsoleted
December 1994
- RFC 1749IEEE 802.5 Station Source Routing MIB using SMIv2Current
December 1994
- RFC 1695Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2Obsoleted
August 1994
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
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?