RFC 1604: Definitions of Managed Objects for Frame Relay Service
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2954.
Current document in this lineage: RFC 2954 — Definitions of Managed Objects for Frame Relay Service
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1604
- Published
- March 1994
- Authors
- T. Brown
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 46
- 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 1596 (1994)
- RFC 1604 (1994)
- RFC 2954 (2000) ✓
Read the full history of Definitions of Managed Objects for Frame Relay Service →
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 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 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 3638Applicability Statement for Reclassification of RFC 1643 to Historic StatusCurrent
October 2003
- RFC 1595Definitions of Managed Objects for the SONET/SDH Interface TypeObsoleted
March 1994
- RFC 1658Definitions of Managed Objects for Character Stream Devices using SMIv2Current
July 1994
- RFC 1659Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2Current
July 1994
- RFC 1660Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2Current
July 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?