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 specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2417
- Published
- September 1998
- Authors
- C. Chung; M. Greene
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 76
- Also known as
- —
- Obsoletes:
- RFC 2366
Topics
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 3606Definitions of Supplemental Managed Objects for ATM InterfaceCurrent
November 2003
- RFC 2512Accounting Information for ATM NetworksCurrent
February 1999
- RFC 2514Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM ManagementCurrent
February 1999
- RFC 2515Definitions of Managed Objects for ATM ManagementCurrent
February 1999
- RFC 2758Definitions of Managed Objects for Service Level Agreements Performance MonitoringCurrent
February 2000
- RFC 2786Diffie-Helman USM Key Management Information Base and Textual ConventionCurrent
March 2000
- RFC 2790Host Resources MIBCurrent
March 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?