RFC 1757: Remote Network Monitoring Management Information Base
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2819.
Current document in this lineage: RFC 2819 — Remote Network Monitoring Management Information Base
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 remote network monitoring devices. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1757
- Published
- February 1995
- Authors
- S. Waldbusser
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 91
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1271 (1991)
- RFC 1757 (1995)
- RFC 2819 (2000) ✓
Read the full history of Remote Network Monitoring Management Information Base →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2021Remote Network Monitoring Management Information Base Version 2 using SMIv2Obsoleted
January 1997
- RFC 4502Remote Network Monitoring Management Information Base Version 2Current
May 2006
- RFC 2074Remote Network Monitoring MIB Protocol IdentifiersObsoleted
January 1997
- RFC 3273Remote Network Monitoring Management Information Base for High Capacity NetworksUpdated
July 2002
- RFC 3287Remote Monitoring MIB Extensions for Differentiated ServicesCurrent
July 2002
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3737IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modulesCurrent
April 2004
- RFC 1695Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2Obsoleted
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?