RFC 3591: Definitions of Managed Objects for the Optical Interface Type
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with Simple Network Management Protocol (SNMP) in TCP/IP-based internets. In particular, it defines objects for managing Optical Interfaces associated with WavelengthDivision Multiplexing systems or characterized by the Optical Transport Network (OTN) in accordance with the OTN architecture defined in ITU-T Recommendation G.872. The MIB module defined in this memo can be used for performance monitoring and/or configuration of such optical interface. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3591
- Published
- September 2003
- Authors
- H-K. Lam; M. Stewart; A. Huynh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 174
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
- RFC 3440Definitions of Extension Managed Objects for Asymmetric Digital Subscriber LinesCurrent
January 2003
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 4369Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)Obsoleted
January 2006
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?