idnits 2.17.1 draft-galimbe-kunze-black-link-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([ITU.G698.2], [TEMPLATETODO]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (February 18, 2011) is 4809 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'TEMPLATE TODO' is mentioned on line 731, but not defined == Unused Reference: 'RFC2629' is defined on line 940, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 943, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G698.2' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G709' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G872' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G798' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G874' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G874.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G959.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G826' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G8201' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G694.1' -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force GMG. G.Galimberti, Ed. 3 Internet-Draft Cisco 4 Intended status: Standards Track RK. R.Kunze, Ed. 5 Expires: August 22, 2011 Deutsche Telekom 6 February 18, 2011 8 A SNMP MIB to manage the optical parameters caracteristic of a DWDM 9 Black-Link 10 draft-galimbe-kunze-black-link-mib-00 12 Abstract 14 This memo defines a portion of the Management Information Base (MIB) 15 used by Simple Network Management Protocol (SNMP) in TCP/IP- based 16 internets. In particular, it defines objects for managing Optical 17 Interfaces associated with Wavelength Division Multiplexing (WDM) 18 systems or characterized by the Optical Transport Network (OTN) in 19 accordance with the Black-Link approach defined in ITU-T 20 Recommendation G.698. [ITU.G698.2] 22 The MIB module defined in this memo can be used for Optical 23 Parameters monitoring and/or configuration of such optical interface. 25 Copyright Notice 27 Copyright (c) 2011 IETF Trust and the persons identified as the 28 document authors. All rights reserved. 30 Note to RFC Editor re: [TEMPLATE TODO] markers 32 Note to RFC Editor: When a document is developed using this template, 33 the editor of the document should replace or remove all the places 34 marked [TEMPLATE TODO] before submitting the document. If there are 35 still [TEMPLATE TODO] markers, please send the document back to the 36 editor. 38 Status of This Memo 40 This Internet-Draft is submitted in full conformance with the 41 provisions of BCP 78 and BCP 79. 43 Internet-Drafts are working documents of the Internet Engineering 44 Task Force (IETF). Note that other groups may also distribute 45 working documents as Internet-Drafts. The list of current Internet- 46 Drafts is at http://datatracker.ietf.org/drafts/current/. 48 Internet-Drafts are draft documents valid for a maximum of six months 49 and may be updated, replaced, or obsoleted by other documents at any 50 time. It is inappropriate to use Internet-Drafts as reference 51 material or to cite them other than as "work in progress." 53 This Internet-Draft will expire on August 22, 2011. 55 Copyright Notice 57 Copyright (c) 2011 IETF Trust and the persons identified as the 58 document authors. All rights reserved. 60 This document is subject to BCP 78 and the IETF Trust's Legal 61 Provisions Relating to IETF Documents 62 (http://trustee.ietf.org/license-info) in effect on the date of 63 publication of this document. Please review these documents 64 carefully, as they describe your rights and restrictions with respect 65 to this document. Code Components extracted from this document must 66 include Simplified BSD License text as described in Section 4.e of 67 the Trust Legal Provisions and are provided without warranty as 68 described in the Simplified BSD License. 70 Table of Contents 72 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 2. The Internet-Standard Management Framework . . . . . . . . . . 5 74 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 4.1. Optical Parameters Description . . . . . . . . . . . . . . 7 77 4.1.1. General . . . . . . . . . . . . . . . . . . . . . . . 7 78 4.1.2. Parameters at Ss . . . . . . . . . . . . . . . . . . . 8 79 4.1.3. Optical path from point Ss to Rs . . . . . . . . . . . 9 80 4.1.4. Interface at point Rs . . . . . . . . . . . . . . . . 10 81 4.1.5. Alarms and Threshold definition . . . . . . . . . . . 10 82 4.1.6. Performance Monitoring (PM) description . . . . . . . 12 83 4.1.7. Generic Parameter description . . . . . . . . . . . . 13 84 4.2. Use of ifTable . . . . . . . . . . . . . . . . . . . . . . 14 85 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 14 86 5.1. The optIfOTMn group . . . . . . . . . . . . . . . . . . . 15 87 5.1.1. optIfOTMnTable . . . . . . . . . . . . . . . . . . . . 15 88 5.2. The optIfOTSn groups . . . . . . . . . . . . . . . . . . . 15 89 5.2.1. optIfOTSn Configuration group . . . . . . . . . . . . 15 90 5.3. The [TEMPLATE TODO] Subtree . . . . . . . . . . . . . . . 15 91 5.4. The Notifications Subtree . . . . . . . . . . . . . . . . 15 92 6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 15 93 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 17 94 7.1. Relationship to the [TEMPLATE TODO] MIB . . . . . . . . . 17 95 7.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 17 96 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 17 97 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 98 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 99 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 100 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 101 12.1. Normative References . . . . . . . . . . . . . . . . . . . 21 102 12.2. Informative References . . . . . . . . . . . . . . . . . . 22 103 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22 104 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 23 106 1. Introduction 108 This memo defines a portion of the Management Information Base (MIB) 109 used by Simple Network Management Protocol (SNMP) in TCP/IP- based 110 internets. In particular, it defines objects for managing Optical 111 Interfaces associated with Wavelength Division Multiplexing (WDM) 112 systems or characterized by the Optical Transport Network (OTN) in 113 accordance with the Black-Link approach defined in G.698.2 114 [ITU.G698.2] 116 Black Link approach allows supporting an optical transmitter/receiver 117 pair of one vendor to inject a DWDM channel and run it over an 118 optical network composed of amplifiers, filters, add-drop 119 multiplexers from a different vendor. Whereas the standardization of 120 black link for 2.5 and 10G is settled for 40G and 100G interfaces and 121 Black Link extensions are still in progress. For carrier network 122 deployments, interoperability is a key requirement. Today it is 123 state-of-the-art to interconnect IP Routers from different vendors 124 and WDM transport systems using short-reach, grey interfaces. 125 Applying the Black Link (BL) concept, routers now get directly 126 connected to each via transport interfaces which must be 127 interoperable to each other. 129 The G.698.2 [ITU.G698.2] provides optical parameter values for 130 physical layer interfaces of Dense Wavelength Division Multiplexing 131 (DWDM) systems primarily intended for metro applications which 132 include optical amplifiers. Applications are defined using optical 133 interface parameters at the single-channel connection points between 134 optical transmitters and the optical multiplexer, as well as between 135 optical receivers and the optical demultiplexer in the DWDM system. 136 This Recommendation uses a methodology which does not specify the 137 details of the optical link, e.g. the maximum fibre length, 138 explicitly. The Recommendation currently includes unidirectional 139 DWDM applications at 2.5 and 10 Gbit/s with 100 GHz channel frequency 140 spacing and may be extended to 40 and 100 Gbit/s channels with a 141 lower channel frequency spacing. 143 The Building a SNMP MIB describing the optical parameters defined in 144 G.698 [ITU.G698.2] allow the different vendors and operator to 145 retrieve, provision and exchange information related to Optical 146 Networks in a standardized way. This ensures interworking in case of 147 using optical interfaces from different vendors at the end of the 148 link. Decoupling DWDM layer from the optical layer The Optical 149 Parameters and their values characterize the features and the 150 performances of the Network optical components and allow a reliable 151 network design in case of Multivendor Optical Networks. 153 Although RFC 3591 [RFC3591] describe and define the SNMP MIB of a 154 number of key optical parameters, alarms and Performance Monitoring, 155 a more complete description of optical parameters and processes can 156 be found in the ITU-T Recommendations. Appendix A of this document 157 provides an overview about the extensive ITU-T documentation in this 158 area. The same considerations can be applied to the RFC 4054 159 [RFC4054] 161 2. The Internet-Standard Management Framework 163 For a detailed overview of the documents that describe the current 164 Internet-Standard Management Framework, please refer to section 7 of 165 RFC 3410 [RFC3410]. 167 Managed objects are accessed via a virtual information store, termed 168 the Management Information Base or MIB. MIB objects are generally 169 accessed through the Simple Network Management Protocol (SNMP). 170 Objects in the MIB are defined using the mechanisms defined in the 171 Structure of Management Information (SMI). This memo specifies a MIB 172 module that is compliant to the SMIv2, which is described in STD 58, 173 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 174 [RFC2580]. 176 3. Conventions 178 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 179 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 180 document are to be interpreted as described in RFC 2119 [RFC2119]. 182 4. Overview 184 In this document, the term OTN (Optical Transport Network) system is 185 used to describe devices that are compliant with the requirements 186 specified in the ITU-T Recommendations G.872 [ITU.G872], G.709 187 [ITU.G709] , G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 188 [ITU.G874.1] while refer to [ITU.G698.2] for the Black Link and DWDM 189 parameter description. 191 The optical objects will be managed using the MIB II ifTable and 192 ifStackTable. Additional tables will also be supported to monitor 193 layer specific status and provide performance monitoring data. In 194 the tables, some entries are required for OTN systems only. A 195 Configuration (Config) table, Current Performance Monitoring (PM) 196 table, and Interval PM table will be maintained for the OTSn, OMSn, 197 OChGroup, and OCh layers on a source and sink trail termination 198 basis. These tables will be linked to the ifTable by using the 199 ifIndex that is associated with that layer. 201 An Alarm (Aalarm) table will be maintained for the OTSn, OMSn, 202 OChGroup, and OCh layers on a source and sink trail termination 203 basis. These tables will be linked to the ifTable by using the 204 ifIndex that is associated with that layer. 206 Figure ADD-REFERENCE shows a set of reference points, for the linear 207 "black-link" approach, for single-channel connection (Ss and Rs) 208 between transmitters (Tx) and receivers (Rx). Here the DWDM network 209 elements include an OM and an OD (which are used as a pair with the 210 opposing element), one or more optical amplifiers and may also 211 include one or more OADMs. 213 +-------------------------------------------------+ 214 Ss | DWDM Network Elements | Rs 215 +---+ | | | \ / | | | +---+ 216 Tx L1----|->| \ +------+ +------+ / |--|--->Rx L1 217 +---+ | | | | | +------+ | | | | | +---+ 218 +---+ | | | | | | | | | | | | +---+ 219 Tx L2----|->| OM |-|>|------|->| OADM |--|------|->| OD |--|--->Rx L2 220 +---+ | | | | | | | | | | | | +---+ 221 +---+ | | | | | +------+ | | | | | +---+ 222 Tx L3----|->| / | DWDM | | ^ | DWDM | \ |--|--->Rx L3 223 +---+ | | / | Link +----|--|----+ Link | \ | | +---+ 224 +-----------+ | | +----------+ 225 +--+ +--+ 226 | | 227 v | 228 +---+ +---+ 229 RxLx TxLx 230 +---+ +---+ 231 Ss = reference point at the DWDM network element tributary output 232 Rs = reference point at the DWDM network element tributary input 233 Lx = Lambda x 234 OM = Optical Mux 235 OD = Optical Demux 236 OADM = Optical Add Drop Mux 238 from Fig. 5.1/G.698.2 240 Figure 1: Linear Black Link 242 G.698.2 [ITU.G698.2] defines also Ring Black Link configurations 243 [Fig. 5.2/G.698.2] and Bidiractional Black Link configurations [Fig. 244 5.3/G.698.2] 246 These objects are used when the particular media being used to 247 realize an interface is an Optical Transport interface. At present, 248 this applies to these values of the ifType variable in the Internet- 249 standard MIB: 251 opticalChannel (195), opticalChannelGroup (219), opticalTransport 252 (196). 254 The definitions contained herein are based on the OTN specifications 255 in ITU-T G.872 [ITU.G872], G.709 [ITU.G709], G.798 [ITU.G798], G.874 256 [ITU.G874], and G.874.1 [ITU.G874.1]. 258 4.1. Optical Parameters Description 260 The terminology used in this document describes the optical 261 parameters, the states and the Alarms at the points Ss, Rs and DWDM 262 depicted in fig.1. The terms are defined in ITU-T Recommendations 263 G.698.2 [ITU.G698.2]. Those definitions are made to increase the 264 readability of the document. 266 4.1.1. General 268 Minimum channel spacing: 269 This is the minimum nominal difference in frequency between two 270 adjacent channels (G). 272 Bit rate/line coding of optical tributary signals: 273 Optical tributary signal class NRZ 2.5G or NRZ 10G nominally 2.4 274 Gbit/s to nominally 10.71 Gbit/s. 40Gbit/s and 100Gbit/s are under 275 definition (G, S). 277 Channel Modulation Format: 278 This parameter indicate what kind of modulation format is used at 279 Ss (G). 281 FEC Coding: 282 This parameter indicate what Forward Error Correction (FEC) code 283 is used at Ss and Rs (G, S). 285 Wavelenght Range (see G.694.1): [ITU.G694.1] 286 This parameter indicate minimum and maximum wavelength spectrum 287 (G) in a definite wavelenght Band (L, C and S). 289 Wavelength Value (see G.694.1): 290 This parameter indicates the wavelenght value that Ss and Rs will 291 be set to work (G, S). 293 Vendor Transceiver Class: 294 Other than specifying all the Transceiver parameter, it might be 295 convenient for the vendors to summarize a set of parameters in a 296 single proprietary parameter: the Class of transceiver. The 297 Transceiver classification will be based on the Vendor Name and 298 the main TX and RX parameters (i.e. Trunk Mode, Framing, Bit 299 rate, Trunk Type, Channel Band, Channel Grid, Modulation Format, 300 etc.). If this parameter is used, the MIB parameters specifying 301 the Transceiver characteristics may not be significant and the 302 vendor will be responsible to specify the Class contents and 303 values. The Vendor can publish the parameters of its Classes or 304 declare to be compatible with published Classes.(G) Optional for 305 compliance. 307 4.1.2. Parameters at Ss 309 Maximum and minimum mean channel output power: 310 The mean launched power at Ss is the average power of a pseudo- 311 random data sequence coupled into the DWDM link It is defined the 312 thange (Max and Min ) of the parameter (G, S) 314 Minimum and maximum central frequency: 315 The central frequency is the nominal single-channel frequency on 316 which the digital coded information of the particular optical 317 channel is modulated by use of the NRZ line code. The central 318 frequencies of all channels within an application lie on the 319 frequency grid for the minimum channel spacing of the application 320 given in ITU-T Rec. G.694.1. This parameter give the Maximum and 321 minimum frequency interval the channel must be modulated (G) 323 Maximum spectral excursion: 324 This is the maximum acceptable difference between the nominal 325 central frequency of the channel and the minus 15 dB points of the 326 transmitter spectrum furthest from the nominal central frequency 327 measured at point Ss. (G) 329 Maximum transmitter (residual) dispersion OSNR penalty (B.3/G.959.1) 330 [ITU.G959.1] 331 Lowest OSNR at Ss with worst case (residual) dispersion. Lowest 332 OSNR at Ss with no dispersion (G) 334 Electrical Signal Framing: 335 This is the indication of what framing (GE, Sonet/SDH, OTN) the Ss 336 and Rs ports are set (G, S) 338 4.1.3. Optical path from point Ss to Rs 340 Maximum and minimum (residual) chromatic dispersion: 341 These parameters define the maximum and minimum value of the 342 optical path "end to end chromatic dispersion" that the system 343 shall be able to tolerate. (G) 345 Minimum optical return loss at Ss: 346 These parameter defines minimum optical return loss of the cable 347 plant at the source reference point (Ss), including any connectors 348 (G) 350 Maximum discrete reflectance between SS and RS: 351 Optical reflectance is defined to be the ratio of the reflected 352 optical power present at a point, to the optical power incident to 353 that point. Control of reflections is discussed extensively in 354 ITU-T Rec. G.957 (G) 356 Maximum differential group delay: 357 Differential group delay (DGD) is the time difference between the 358 fractions of a pulse that are transmitted in the two principal 359 states of polarization of an optical signal. For distances 360 greater than several kilometres, and assuming random (strong) 361 polarization mode coupling, DGD in a fibre can be statistically 362 modelled as having a Maxwellian distribution. (G) 364 Maximum polarisation dependent loss: 365 The polarisation dependent loss (PDL) is the difference (in dB) 366 between the maximum and minimum values of the channel insertion 367 loss (or gain) of the black-link from point SS to RS due to a 368 variation of the state of polarization (SOP) over all SOPs. (G) 370 Maximum inter-channel crosstalk: 371 Inter-channel crosstalk is defined as the ratio of total power in 372 all of the disturbing channels to that in the wanted channel, 373 where the wanted and disturbing channels are at different 374 wavelengths. The parameter specify the isolation of a link 375 conforming to the "black-link" approach such that under the worst- 376 case operating conditions the inter-channel crosstalk at any 377 reference point RS is less than the maximum inter-channel 378 crosstalk value (G) 380 Maximum interferometric crosstalk: 381 This parameter places a requirement on the isolation of a link 382 conforming to the "black-link" approach such that under the worst 383 case operating conditions the interferometric crosstalk at any 384 reference point RS is less than the maximum interferometric 385 crosstalk value. (G) 387 Maximum optical path OSNR penalty: 388 The optical path OSNR penalty is defined as the difference between 389 the Lowest OSNR at Rs and Lowest OSNR at Ss (G) 391 4.1.4. Interface at point Rs 393 Maximum and minimum mean input power: 394 The maximum and minimum values of the average received power at 395 point Rs. (G) 397 Minimum optical signal-to-noise ratio (OSNR): 398 The minimum optical signal-to-noise ratio (OSNR) is the minimum 399 value of the ratio of the signal power in the wanted channel to 400 the highest noise power density in the range of the central 401 frequency plus and minus the maximum spectral excursion (G) 403 Receiver OSNR tolerance: 404 The receiver OSNR tolerance is defined as the minimum value of 405 OSNR at point Rs that can be tolerated while maintaining the 406 maximum BER of the application. (G) 408 Minimum maximum Chromatic Disperion (CD) : 409 This parameter define the CD range a Receiver (Rs) can tolerate in 410 order to decode the received signal (G) 412 Maximum Polarization Mode Dispersion (PMD) : 413 This parameter define the maximum PMD value a Receiver (Rs) can 414 tolerate in order to decode the received signal (G) 416 4.1.5. Alarms and Threshold definition 418 This section describes the Alarms and the Thresholds at Ss and Rs 419 points according to ITU-T Recommendations G.872 [ITU.G872], G.709 420 [ITU.G709], G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 421 [ITU.G874.1]. The SNMP MIB of the above list is already defined and 422 specified by the RFC3591 424 OTN alarms defined in RFC3591: 426 Threshold Crossing Alert (TCA Alarm) 428 LOW-TXPOWER 430 HIGH-TXPOWER 432 LOW-RXPOWER 433 HIGH-RXPOWER 435 OTUk-LOF or more generic LOF 437 Backward Defect Indication (BDI) 439 Trace Identifier Mismatch (tim) 441 Signal Degrade (sd) 443 Server Signal Failure (SSF) 445 Alarm Indication Signal (AIS) 447 Loss of Multiframe (lom) 449 OTN Thresholds (for TCA) defined in RFC3591 451 LOW-TXPOWER 453 HIGH-TXPOWER 455 LOW-RXPOWER 457 HIGH-RXPOWER 459 The list below reports the new Alarms and Thresholds not managed in 460 RFC3591 462 Laser Bias Current: 463 This parameter report the Bias current of the Laser Transmitter 464 (G) 466 Laser Bias Current Threshold: 467 This parameter is to set the Bias current Threshold of the Laser 468 Transmitter used ri rise the related Alarm (G, S) 470 Forward Defect Indication (FDI): 471 This parameter indicates a notification to the receiver that a 472 failure occurred in the network (G) 474 Backward Error Indication (BEI): 475 This parameter indicates the number of Errors occurred in the 476 opposite line direction (G) 478 4.1.6. Performance Monitoring (PM) description 480 This section describes the Performance Monitoring parameters at Ss 481 and Rs points (Near -End and Far-End)according to ITU-T 482 Recommendations G.826 [ITU.G826], G.8201 [ITU.G8201], G.709 483 [ITU.G709], G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 484 [ITU.G874.1]. 486 Failure Counts (fc) : 487 Number of Failures occurred in an observation periond (G) 489 Errored Seconds (es) : 490 It is a one-second period in which one or more bits are in error 491 or during which Loss of Signal (LOS) or Alarm Indication Signal 492 (AIS) is detected (G) 494 Severely Errored Seconds (ses) : 495 It is a one-second period which has a bit-error ratio = 496 1x10Eminus3 or during which Loss of Signal (LOS) or Alarm 497 Indication Signal (AIS) is detected (G) 499 Unavailable Seconds (uas) : 500 A period of unavailable time begins at the onset of ten 501 consecutive SES events. These ten seconds are considered to be 502 part of unavailable time. A new period of available time begins 503 at the onset of ten consecutive non-SES events. These ten seconds 504 are considered to be part of available time (G) 506 Background Block Errors (bbe) : 507 An errored block not occurring as part of an SES(G) 509 Error Seconds Ratio (esr) : 510 The ratio of ES in available time to total seconds in available 511 time during a fixed measurement interval(G) 513 Severely Errored Seconds Ratio (sesr) : 514 The ratio of SES in available time to total seconds in available 515 time during a fixed measurement interval(G) 517 Background Block Errored Seconds Ratio (bber) : 518 The ratio of Background Block Errors (BBE) to total blocks in 519 available time during a fixed measurement interval. The count of 520 total blocks excludes all blocks during SESs.(G) 522 FEC corrected Bit Error (FECcorrErr): 523 The number of bits corrected by the FEC are counted over one 524 second (G) 526 FEC un-corrected Bit Error : 527 The number of bits un-corrected by the FEC are counted over one 528 second (G) 530 Pre-FEC Bit Error : 531 The number of Errored bits at receiving side before the FEC 532 function counted over one second (G) 534 OTN Valid Intervals : 535 The number of contiguous 15 minute intervals for which valid OTN 536 performance monitoring data is available for the particular 537 interface (G) 539 FEC Valid Intervals : 540 The number of contiguous 15 minute intervals for which valid FEC 541 PM data is available for the particular interface.(G) 543 4.1.7. Generic Parameter description 545 This section describes the Generic Parameters at Ss and Rs points 546 according to ITU-T Recommendations G.872 [ITU.G872], G.709 547 [ITU.G709], G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 548 [ITU.G874.1]. 550 Interface Admin Status : 551 The Administrative Status of an Interface: Up/Down - In Service/ 552 Out of Service (can be Automatic in Service) (G/S) 554 Interface Operational Status : 555 The Operational Status of an Interface: Up/Down - In Service/Out 556 of Service (G) 558 Loopbacks : 559 The Interface loopbacks used for maintenance purposes, they are 560 Terminal or Line (may be with send AIS)(G/S) 562 Pre-FEC BER (Mantissa + Exponent) : 563 Bit Error Rate at the Rs interface before error correction (G/S) 565 Q factor : 566 (G) 568 Q margin : 569 (G) 571 4.2. Use of ifTable 573 This section specifies how the MIB II interfaces group, as defined in 574 RFC 2863 [RFC2863], is used for optical interfaces. As described in 575 the RFC 3591 figure 1 [RFC3591] Only the ifGeneralInformationGroup 576 will be supported for the ifTable and the ifStackTable to maintain 577 the relationship between the various layers. The OTN layers are 578 managed in the ifTable using IfEntries that correlate to the layers 579 depicted in Figure 1. For example, a DWDM device with an Optical 580 Network Node Interface (ONNI) will have an Optical Transmission 581 Section (OTS) physical layer, an Optical Multiplex Section (OMS) 582 layer (transports multiple optical channels), and an Optical Channel 583 (OCh) layer. There is a one to one relationship between the OMS and 584 OTS layers. The OMS layer has fixed connectivity via the OTS and 585 thus no connectivity flexibility at the OMS layer is supported. This 586 draft extend the RFC 3591 [RFC3591] as far as the OMSn and OTSn are 587 concerned. The sections 2.5 and 2.6 of RFC 3591 [RFC3591] must be 588 considered as a reference for the ifStackTable use and Optical 589 Network Terminology. 591 5. Structure of the MIB Module 593 The managed Optical Networking interface objects are arranged into 594 the following groups of tables: 596 The optIfOTMn group handles the OTM information structure of an 597 optical interface. 599 optIfOTMnTable 601 The optIfPerfMon group handles the current 15-minute and 24-hour 602 interval elapsed time, as well as the number of 15-minute intervals 603 for all layers 605 optIfPerfMonIntervalTable 607 The optIfOTSn groups handle the configuration and performance 608 monitoring information for OTS layers. 610 optIfOTSnConfigTable 612 optIfOTSnSinkCurrentTable 614 optIfOTSnSinkIntervalTable 616 optIfOTSnSinkCurDayTable 617 optIfOTSnSinkPrevDayTable 619 optIfOTSnSrcCurrentTable 621 optIfOTSnSrcIntervalTable 623 optIfOTSnSrcCurDayTable 625 optIfOTSnSrcPrevDayTable 627 5.1. The optIfOTMn group 629 5.1.1. optIfOTMnTable 631 This table contains the OTM structure information of an optical 632 interface. 634 5.2. The optIfOTSn groups 636 5.2.1. optIfOTSn Configuration group 638 5.2.1.1. optIfOTSn Configuration Table 640 This table contains information on configuration of optIfOTSn 641 interfaces, in addition to the information on such interfaces 642 contained in the ifTable. 644 5.3. The [TEMPLATE TODO] Subtree 646 5.4. The Notifications Subtree 648 6. Object Definitions 650 OPT-IF-MIB DEFINITIONS ::= BEGIN 652 IMPORTS 653 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, Integer32, 654 Unsigned32, transmission 655 FROM SNMPv2-SMI 656 TEXTUAL-CONVENTION, RowPointer, RowStatus, TruthValue 657 FROM SNMPv2-TC 658 SnmpAdminString 659 FROM SNMP-FRAMEWORK-MIB 660 MODULE-COMPLIANCE, OBJECT-GROUP 661 FROM SNMPv2-CONF 662 ifIndex 663 FROM IF-MIB; 665 -- This is the MIB module for the OTN Interface objects. 667 optIfMibModule MODULE-IDENTITY 668 LAST-UPDATED "200308130000Z" 669 ORGANIZATION "IETF AToM MIB Working Group" 670 CONTACT-INFO 671 "WG charter: 672 http://www.ietf.org/html.charters/atommib-charter.html 674 Mailing Lists: 675 General Discussion: atommib@research.telcordia.com 676 To Subscribe: atommib-request@research.telcordia.com 677 Editor: Hing-Kam Lam 678 Postal: Lucent Technologies, Room 4C-616 679 101 Crawfords Corner Road 680 Holmdel, NJ 07733 681 Tel: +1 732 949 8338 682 Email: hklam@lucent.com" 683 DESCRIPTION 684 "The MIB module to describe pre-OTN and OTN interfaces. 686 Copyright (C) The Internet Society (2003). This version 687 of this MIB module is part of RFC 3591; see the RFC 688 itself for full legal notices." 689 REVISION "200308130000Z" 690 DESCRIPTION 691 "Initial version, published as RFC 3591." 692 ::={ transmission 133 } 694 OptIfBitRateK ::= TEXTUAL-CONVENTION 695 STATUS current 696 DESCRIPTION 697 "Indicates the index 'k' that is used to 698 represent a supported bit rate and the different 699 versions of OPUk, ODUk and OTUk. 700 Allowed values of k are defined in ITU-T G.709. 701 Currently allowed values in G.709 are: 702 k=1 represents an approximate bit rate of 2.5 Gbit/s, 703 k=2 represents an approximate bit rate of 10 Gbit/s, 704 k=3 represents an approximate bit rate of 40 Gbit/s." 705 SYNTAX Integer32 707 optIfOTMnBitRates OBJECT-TYPE 708 SYNTAX BITS { bitRateK1(0), bitRateK2(1), bitRateK3(2) } 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "This attribute is a bit map representing the bit 713 rate or set of bit rates supported on the interface. 714 The meaning of each bit position is as follows: 715 bitRateK1(0) is set if the 2.5 Gbit/s rate is supported 716 bitRateK2(1) is set if the 10 Gbit/s rate is supported 717 bitRateK3(2) is set if the 40 Gbit/s rate is supported 718 Note that each bit position corresponds to one possible 719 value of the type OptIfBitRateK. 720 The default value of this attribute is system specific." 721 ::= { optIfOTMnEntry 3 } 723 7. Relationship to Other MIB Modules 725 7.1. Relationship to the [TEMPLATE TODO] MIB 727 7.2. MIB modules required for IMPORTS 729 8. Definitions 731 [TEMPLATE TODO]: put your valid MIB module here. 732 A list of tools that can help automate the process of 733 checking MIB definitions can be found at 734 http://www.ops.ietf.org/mib-review-tools.html 736 9. Security Considerations 738 There are a number of management objects defined in this MIB module 739 with a MAX-ACCESS clause of read-write and/or read-create. Such 740 objects may be considered sensitive or vulnerable in some network 741 environments. The support for SET operations in a non-secure 742 environment without proper protection can have a negative effect on 743 network operations. These are the tables and objects and their 744 sensitivity/vulnerability: 746 o 748 There are no management objects defined in this MIB module that have 749 a MAX-ACCESS clause of read-write and/or read-create. So, if this 750 MIB module is implemented correctly, then there is no risk that an 751 intruder can alter or create any management objects of this MIB 752 module via direct SNMP SET operations. 754 Some of the readable objects in this MIB module (i.e., objects with a 755 MAX-ACCESS other than not-accessible) may be considered sensitive or 756 vulnerable in some network environments. It is thus important to 757 control even GET and/or NOTIFY access to these objects and possibly 758 to even encrypt the values of these objects when sending them over 759 the network via SNMP. These are the tables and objects and their 760 sensitivity/vulnerability: 762 o 764 o 766 SNMP versions prior to SNMPv3 did not include adequate security. 767 Even if the network itself is secure (for example by using IPsec), 768 even then, there is no control as to who on the secure network is 769 allowed to access and GET/SET (read/change/create/delete) the objects 770 in this MIB module. 772 It is RECOMMENDED that implementers consider the security features as 773 provided by the SNMPv3 framework (see [RFC3410], section 8), 774 including full support for the SNMPv3 cryptographic mechanisms (for 775 authentication and privacy). 777 Further, deployment of SNMP versions prior to SNMPv3 is NOT 778 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 779 enable cryptographic security. It is then a customer/operator 780 responsibility to ensure that the SNMP entity giving access to an 781 instance of this MIB module is properly configured to give access to 782 the objects only to those principals (users) that have legitimate 783 rights to indeed GET or SET (change/create/delete) them. 785 10. IANA Considerations 787 Option #1: 789 The MIB module in this document uses the following IANA-assigned 790 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 792 Descriptor OBJECT IDENTIFIER value 793 ---------- ----------------------- 795 sampleMIB { mib-2 XXX } 797 Option #2: 799 Editor's Note (to be removed prior to publication): the IANA is 800 requested to assign a value for "XXX" under the 'mib-2' subtree and 801 to record the assignment in the SMI Numbers registry. When the 802 assignment has been made, the RFC Editor is asked to replace "XXX" 803 (here and in the MIB module) with the assigned value and to remove 804 this note. 806 Note well: prior to official assignment by the IANA, an internet 807 draft MUST use placeholders (such as "XXX" above) rather than actual 808 numbers. See RFC4181 Section 4.5 for an example of how this is done 809 in an internet draft MIB module. 811 Option #3: 813 This memo includes no request to IANA. 815 11. Contributors 816 Arnold Mattheus 817 Deutsche Telekom 818 Darmstadt 819 Germany 820 Phone +49xxxxxxxxxx 821 email arnold.Mattheus@telekom.de 823 Manuel Paul 824 Deutsche Telekom 825 Berlin 826 Germany 827 phone +49xxxxxxxxxx 828 email Manuel.Paul@telekom.de 830 Frank Luennemann 831 T-Com TE14 832 Germany 833 phone +49xxxxxxxxxx 834 email Frank.Luennemann@telekom.de 836 Najam Saquib 837 Cisco 838 Ludwig-Erhard-Strasse 3 839 ESCHBORN, HESSEN 65760 840 GERMANY 841 phone +49 619 6773 9041 842 email nasaquib@cisco.com 844 Walid Wakim 845 Cisco 846 9501 Technology Blvd 847 ROSEMONT, ILLINOIS 60018 848 UNITED STATES 849 phone +1 847 678 5681 850 email wwakim@cisco.com 852 Ori Gerstel 853 Cisco 854 32 HaMelacha St., (HaSharon Bldg) 855 SOUTH NETANYA, HAMERKAZ 42504 856 ISRAEL 857 phone +972 9 864 6292 858 email ogerstel@cisco.com 860 12. References 861 12.1. Normative References 863 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 864 MIB", RFC 2863, June 2000. 866 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 867 Requirement Levels", BCP 14, RFC 2119, March 1997. 869 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 870 Schoenwaelder, Ed., "Structure of Management 871 Information Version 2 (SMIv2)", STD 58, RFC 2578, 872 April 1999. 874 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 875 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 876 STD 58, RFC 2579, April 1999. 878 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 879 "Conformance Statements for SMIv2", STD 58, RFC 2580, 880 April 1999. 882 [RFC3591] Lam, H-K., Stewart, M., and A. Huynh, "Definitions of 883 Managed Objects for the Optical Interface Type", 884 RFC 3591, September 2003. 886 [ITU.G698.2] International Telecommunications Union, "Amplified 887 multichannel dense wavelength division multiplexing 888 applications with single channel optical interfaces", 889 ITU-T Recommendation G.698.2, November 2009. 891 [ITU.G709] International Telecommunications Union, "Interface for 892 the Optical Transport Network (OTN)", ITU- 893 T Recommendation G.709, March 2003. 895 [ITU.G872] International Telecommunications Union, "Architecture 896 of optical transport networks", ITU-T Recommendation 897 G.872, November 2001. 899 [ITU.G798] International Telecommunications Union, 900 "Characteristics of optical transport network hierarchy 901 equipment functional blocks", ITU-T Recommendation 902 G.798, October 2010. 904 [ITU.G874] International Telecommunications Union, "Management 905 aspects of optical transport network elements", ITU- 906 T Recommendation G.874, July 2010. 908 [ITU.G874.1] International Telecommunications Union, "Optical 909 transport network (OTN): Protocol-neutral management 910 information model for the network element view", ITU- 911 T Recommendation G.874.1, January 2002. 913 [ITU.G959.1] International Telecommunications Union, "Optical 914 transport network physical layer interfaces", ITU- 915 T Recommendation G.959.1, November 2009. 917 [ITU.G826] International Telecommunications Union, "End-to-end 918 error performance parameters and objectives for 919 international, constant bit-rate digital paths and 920 connections", ITU-T Recommendation G.826, 921 November 2009. 923 [ITU.G8201] International Telecommunications Union, "Error 924 performance parameters and objectives for multi- 925 operator international paths within the Optical 926 Transport Network (OTN)", ITU-T Recommendation G.8201, 927 September 2003. 929 [ITU.G694.1] International Telecommunications Union, "Spectral grids 930 for WDM applications: DWDM frequency grid", ITU- 931 T Recommendation G.694.1, June 2002. 933 12.2. Informative References 935 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 936 "Introduction and Applicability Statements for 937 Internet-Standard Management Framework", RFC 3410, 938 December 2002. 940 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 941 June 1999. 943 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB 944 Documents", BCP 111, RFC 4181, September 2005. 946 [RFC4054] Strand, J. and A. Chiu, "Impairments and Other 947 Constraints on Optical Layer Routing", RFC 4054, 948 May 2005. 950 Appendix A. Change Log 952 This optional section should be removed before the internet draft is 953 submitted to the IESG for publication as an RFC. 955 Note to RFC Editor: please remove this appendix before publication as 956 an RFC. 958 Appendix B. Open Issues 960 Note to RFC Editor: please remove this appendix before publication as 961 an RFC. 963 Authors' Addresses 965 Gabriele Galimberti (editor) 966 Cisco 967 Via Philips,12 968 20052 - Monza 969 Italy 971 Phone: +390392091462 972 EMail: ggalimbe@cisco.com 974 Ruediger Kunze (editor) 975 Deutsche Telekom 976 Dddd, xx 977 Berlin 978 Germany 980 Phone: +49xxxxxxxxxx 981 EMail: RKunze@telekom.de