RFC 2932: IPv4 Multicast Routing MIB
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5132.
Current version: RFC 5132 — IP Multicast MIB
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 describes managed objects used for managing IP Multicast Routing for IPv4, independent of the specific multicast routing protocol in use. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2932
- Published
- October 2000
- Authors
- K. McCloghrie; D. Farinacci; D. Thaler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
- Obsoleted by:
- RFC 5132
Topics
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 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 3019IP Version 6 Management Information Base for The Multicast Listener Discovery ProtocolObsoleted
January 2001
- RFC 2734IPv4 over IEEE 1394Current
December 1999
- RFC 2454IP Version 6 Management Information Base for the User Datagram ProtocolObsoleted
December 1998
- RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent
March 2003
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- 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?