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 Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it defines objects for managing the frame relay service. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2954
- Published
- October 2000
- Authors
- K. Rehbehn; D. Fowler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 76
- 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 2955Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking FunctionUpdated
October 2000
- RFC 3019IP Version 6 Management Information Base for The Multicast Listener Discovery ProtocolObsoleted
January 2001
- RFC 3020Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay FunctionUpdated
December 2000
- RFC 2864The Inverted Stack Table Extension to the Interfaces Group MIBCurrent
June 2000
- RFC 3201Definitions of Managed Objects for Circuit to Interface TranslationUpdated
January 2002
- RFC 3202Definitions of Managed Objects for Frame Relay Service Level DefinitionsUpdated
January 2002
- RFC 2677Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)Current
August 1999
- RFC 2494Definitions of Managed Objects for the DS0 and DS0 Bundle Interface TypeCurrent
January 1999
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?