Definitions of Managed Objects for the Optical Interface Type
RFC 3591
| Document | Type | RFC - Proposed Standard (September 2003; Errata) | |
|---|---|---|---|
| Authors | Hing-Kam Lam , An-ni Huynh , Mark Stewart | ||
| Last updated | 2015-10-14 | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 3591 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Erik Nordmark | ||
| Send notices to | <fayely98@hotmail.com> | ||
Network Working Group H-K. Lam
Request for Comments: 3591 Lucent Technologies
Category: Standards Track M. Stewart
Dorado Software
A. Huynh
Cetus Networks
September 2003
Definitions of Managed Objects for the Optical Interface Type
Status of this Memo
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.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
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.
Lam, et al. Standards Track [Page 1]
RFC 3591 Optical Interface Type MIB September 2003
Table of Contents
1. The Internet-Standard Management Framework ................. 2
2. Overview ................................................... 3
2.1. Use of the ifTable .................................. 3
2.2. Use of ifTable for OTN OTS/OMS Layer................. 8
2.3. Use of ifTable for OTN OChGroup Layer................ 9
2.4. Use of ifTable for OTN OCh Layer..................... 10
2.5. Use of ifStackTable.................................. 12
2.6. Optical Network Terminology ......................... 13
2.7. Tandem Connection Monitoring (TCM) .................. 20
3. Structure of the MIB........................................ 21
3.1. The optIfOTMn group.................................. 23
3.2. The optIfPerfMon group............................... 24
3.3. The optIfOTSn groups................................. 24
3.4. The optIfOMSn groups................................. 25
3.5. The optIfOChGroup groups............................. 26
3.6. The optIfOCh groups.................................. 27
3.7. The optIfOTUk groups................................. 28
3.8. The optIfODUk groups................................. 29
3.9. The optIfODUkT groups................................ 30
4. Object Definitions ......................................... 30
5. Security Considerations .................................... 167
6. Acknowledgments............................................. 169
7. References ................................................. 169
7.1. Normative References ................................. 169
7.2. Informative References ............................... 171
8. Intellectual Property Statement ............................ 171
9. Authors' Addresses ......................................... 172
10. Full Copyright Statement ................................... 173
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
Lam, et al. Standards Track [Page 2]
RFC 3591 Optical Interface Type MIB September 2003
2. Overview
In this document, the term OTN (Optical Transport Network) system is
used to describe devices that are compliant with the requirements
specified in the ITU-T Recommendations G.872 [ITU-T G.872], G.709
[ITU-T G.709], G.798 [ITU-T G.798], G.874 [ITU-T G.874], and G.874.1
[ITU-T G.874.1].
Show full document text