Skip to main content

Definitions of Managed Objects for the Optical Interface Type

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3591.
Authors Hing-Kam Lam , An-ni Huynh , Mark Stewart
Last updated 2015-10-14 (Latest revision 2003-01-16)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3591 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Erik Nordmark
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3591

        Title:      Definitions of Managed Objects for the Optical
                    Interface Type
        Author(s):  H-K. Lam, M. Stewart, A. Huynh
        Status:     Standards Track
        Date:       September 2003
        Pages:      173
        Characters: 310815
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-atommib-opticalmib-08.txt


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.

This document is a product of the AToM MIB Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.