RFC 2366: Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2417.
Current version: RFC 2417 — Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
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 for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2366
- Published
- July 1998
- Authors
- C. Chung; M. Greene
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 76
- Also known as
- —
- Obsoleted by:
- RFC 2417
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 1695Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2Obsoleted
August 1994
- RFC 2837Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardObsoleted
May 2000
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 1650Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2Obsoleted
August 1994
- RFC 1623Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
May 1994
- RFC 2358Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
June 1998
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2249Mail Monitoring MIBObsoleted
January 1998
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?