RFC 2514: Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management
In plain English — editorial summary, not part of the RFC
This memo describes Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2514
- Published
- February 1999
- Authors
- M. Noto; E. Spiegel; K. Tesink
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2515Definitions of Managed Objects for ATM ManagementCurrent
February 1999
- RFC 3606Definitions of Supplemental Managed Objects for ATM InterfaceCurrent
November 2003
- RFC 2955Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking FunctionUpdated
October 2000
- RFC 2513Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented NetworksCurrent
February 1999
- RFC 2512Accounting Information for ATM NetworksCurrent
February 1999
- RFC 2417Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksCurrent
September 1998
- RFC 2613Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0Current
June 1999
- RFC 2618RADIUS Authentication Client MIBObsoleted
June 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?