idnits 2.17.1 draft-ietf-hubmib-wis-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 67 has weird spacing: '... Use of ...' == Line 71 has weird spacing: '... Use of ifTab...' == Line 75 has weird spacing: '...Objects to W...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 13, 2002) is 7803 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: 'RFCnnnn' is mentioned on line 1839, but not defined == Missing Reference: '2570bis' is mentioned on line 1842, but not defined ** Obsolete normative reference: RFC 2558 (ref. 'SONETng') (Obsoleted by RFC 3592) -- Possible downref: Non-RFC (?) normative reference: ref. 'ETHERIF' -- Possible downref: Non-RFC (?) normative reference: ref. 'MAU-MIB' -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) Summary: 4 errors (**), 0 flaws (~~), 9 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Ethernet Interfaces and Hub MIB Working Group Mike Ayers 3 INTERNET DRAFT Consultant 4 John Flick 5 Hewlett-Packard Company 6 C. M. Heard 7 Consultant 8 Kam Lam 9 Lucent Technologies 10 Kerry McDonald 11 CSU San Bernardino 12 K. C. Norseth 13 Consultant 14 Kaj Tesink 15 Telcordia Technologies 16 December 13, 2002 18 Definitions of Managed Objects 19 for the Ethernet WAN Interface Sublayer 20 22 Status of this Memo 24 This document is an Internet-Draft and is in full conformance with 25 all provisions of Section 10 of RFC2026. Internet-Drafts are working 26 documents of the Internet Engineering Task Force (IETF), its areas, 27 and its working groups. Note that other groups may also distribute 28 working documents as Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html 41 Copyright Notice 43 Copyright (C) The Internet Society (2002). All Rights Reserved. 45 Abstract 47 This document defines a portion of the Management Information Base 48 (MIB) for use with network management protocols in TCP/IP based 49 internets. In particular, it defines objects for managing the 50 Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). 52 The MIB module defined in this memo is an extension of the SONET/SDH 53 Interface MIB and is implemented in conjunction with it and with the 54 Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, 55 the Interfaces Group MIB, and the Inverted Stack Table MIB. 57 Table of Contents 59 1 Conventions ............................................... 3 60 2 The Internet-Standard Management Framework ................ 3 61 3 Overview .................................................. 3 62 3.1 Relationship to the SONET/SDH Interface MIB ............. 4 63 3.2 Relationship to the Ethernet-like Interface MIB ......... 4 64 3.3 Relationship to the 802.3 MAU MIB ....................... 5 65 3.4 Use of the ifTable ...................................... 5 66 3.4.1 Layering Model ........................................ 5 67 3.4.2 Use of ifTable for LLC Layer/MAC 68 Layer/Reconciliation Sublayer/Physical Coding 69 Sublayer ............................................... 6 70 3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 6 71 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line 72 Layer .................................................. 6 73 3.5 SONET/SDH Terminology ................................... 6 74 3.6 Mapping of IEEE 802.3 Managed Objects ................... 7 75 3.7 Mapping of SNMP Objects to WIS Station Management 76 Registers .............................................. 12 77 3.8 Structure of the MIB Module ............................. 14 78 3.8.1 etherWisDeviceTable ................................... 14 79 3.8.2 etherWisSectionCurrentTable ........................... 15 80 3.8.3 etherWisPathCurrentTable .............................. 15 81 3.8.4 etherWisFarEndPathCurrentTable ........................ 15 82 4 Object Definitions ........................................ 16 83 5 Acknowledgments ........................................... 30 84 6 Security Considerations ................................... 31 85 7 References ................................................ 32 86 7.1 Normative References .................................... 32 87 7.2 Informative References .................................. 33 88 8 Authors' Addresses ........................................ 33 89 9 Intellectual Property ..................................... 34 90 Appendix A: Collection of Performance Data Using WIS 91 MDIO Registers ......................................... 35 92 Full Copyright Statement ................................... 36 94 1. Conventions 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 98 "OPTIONAL", when they appear in this document, are to be interpreted 99 as described in RFC 2119 [RFC2119]. 101 2. The Internet-Standard Management Framework 103 For a detailed overview of the documents that describe the current 104 Internet-Standard Management Framework, please refer to section 7 of 105 RFC 2570bis [RFC2570bis]. 107 Managed objects are accessed via a virtual information store, termed 108 the Management Information Base or MIB. MIB objects are generally 109 accessed through the Simple Network Management Protocol (SNMP). 110 Objects in the MIB are defined using the mechanisms defined in the 111 Structure of Management Information (SMI). This memo specifies a MIB 112 module that is compliant to the SMIv2, which is described in STD 58, 113 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 114 [RFC2580]. 116 3. Overview 118 The objects defined in this memo are used in conjunction with objects 119 defined in the Interfaces Group MIB [RFC2863], the SONET/SDH 120 Interface MIB [SONETng], and the 802.3 MAU MIB [MAU-MIB] to manage 121 the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) defined 122 in [802.3ae]. The WIS contains functions to perform OC-192c/VC-4-64c 123 framing and scrambling. It resides between the Physical Coding 124 Sublayer (PCS) and the Physical Medium Attachment (PMA) sublayer 125 within a 10GBASE-W 10 Gb/s WAN-compatible physical layer device (PHY) 126 and may be used in conjunction with any of the PCS, PMA, and Physical 127 Medium Dependent (PMD) sublayers defined in [802.3ae] for 10GBASE-W 128 PHYs. Three types of 10GBASE-W PHYs are defined, distinguished by 129 the type of optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW. 130 The objects defined in this memo may be used to manage an Ethernet 131 interface employing any type of 10GBASE-W PHY. They do not apply to 132 any other kind of interface. In particular, they do not apply to 133 so-called Ethernet Line Terminating Equipment (ELTE) residing within 134 a SONET network element that uses the 10GBASE-W PMA/PMD sublayers but 135 otherwise acts as SONET Line Terminating Equipment (LTE). 137 The objects presented here -- along with those incorporated by 138 reference from the Interfaces Group MIB, the SONET/SDH Interface MIB, 139 and the 802.3 MAU MIB -- are intended to provide exact 140 representations of the mandatory attributes in the oWIS managed 141 object class (i.e., the members of the pWISBasic package) defined in 142 Clause 30 and Annex 30A of [802.3ae]. They are also intended to 143 provide approximate representations of the optional attributes (i.e., 144 the members of the pWISOptional package). Some objects with no 145 analogues in oWIS are defined to support WIS testing features 146 required by Clause 50 of [802.3ae]. 148 3.1. Relationship to the SONET/SDH Interface MIB 150 Since the Ethernet WAN Interface Sublayer was designed to be SONET- 151 compatible, information similar to that provided by most of the 152 members of the oWIS managed object class is available from objects 153 defined in the SONET-MIB [SONETng]. Thus, the MIB module defined in 154 this memo is a sparse augmentation of the SONET-MIB -- in other 155 words, every table defined here is an extension of some table in the 156 SONET-MIB -- and its compliance statement REQUIRES that an agent 157 implementing the objects defined in this memo also implement the 158 relevant SONET-MIB objects. That includes all objects required by 159 sonetCompliance2 as well as some that it leaves optional. 161 It should be noted that some of the objects incorporated by reference 162 from the SONET-MIB -- specifically, the threshold objects and 163 interval counter objects -- provide only approximate representations 164 of the corresponding oWIS attributes, as detailed in Section 3.6. An 165 alternative approach would have been to define new objects to exactly 166 match the oWIS definitions. That approach was rejected because the 167 SONET-MIB objects are already used in deployed systems to manage the 168 SONET sublayers of ATM over SONET and PPP over SONET interfaces, and 169 it was deemed undesirable to use a different scheme to manage the 170 SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note 171 that the approach adopted by this memo requires no hardware support 172 beyond that mandated by [802.3ae] subclause 50.3.11. 174 3.2. Relationship to the Ethernet-like Interface MIB 176 An interface which includes the Ethernet WIS is, by definition, an 177 Ethernet-like interface, and an agent implementing the objects 178 defined in this memo MUST implement the objects required by the 179 dot3Compliance2 compliance statement in the EtherLike-MIB. 181 3.3. Relationship to the 802.3 MAU MIB 183 Support for the mauModIfCompl3 compliance statement of the MAU-MIB 184 [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB 185 is needed in order to allow applications to control and/or determine 186 the media type in use. That is important for devices than can 187 support both the 10GBASE-R 10 Gb/s LAN format (which does not include 188 the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the 189 WIS). The MAU-MIB also provides the means to put a device in standby 190 mode or to reset it; the latter may be used to re-initialize the 191 WIS. 193 3.4. Use of the ifTable 195 This section specifies how the ifTable, as defined in [RFC2863], is 196 used for the Ethernet WIS application. 198 3.4.1. Layering Model 200 Ethernet interfaces that employ the WIS are layered as defined in 201 [802.3ae]. The corresponding use of the ifTable [RFC2863] is shown 202 in the figure below. 204 _____________________________ _ 205 | LLC Layer | | 206 +-----------------------------+ | 207 | MAC Layer | | 208 +-----------------------------+ > 1 ifEntry 209 | Reconciliation Sublayer | | ifType: ethernetCsmacd(6) 210 +-----------------------------+ | 211 | Physical Coding Sublayer | | 212 +-----------------------------+ + 213 | Path Layer | > 1 ifEntry 214 +-----------------------------+ + ifType: sonetPath(50) 215 | Line Layer | | 216 +-----------------------------+ | 217 | Section Layer | > 1 ifEntry 218 +-----------------------------+ | ifType: sonet(39) 219 | Physical Medium Layer | | 220 ----------------------------- - 222 Figure 1 - Use of ifTable for an Ethernet WIS port 224 The exact configuration and multiplexing of the layers is maintained 225 in the ifStackTable [RFC2863] and in the ifInvStackTable [RFC2864]. 227 3.4.2. Use of ifTable for LLC Layer/MAC Layer/Reconciliation 228 Sublayer/Physical Coding Sublayer 230 The ifTable MUST be used as specified in [ETHERIF] and [MAU-MIB] for 231 the LLC Layer/MAC Layer/Reconciliation Sublayer/Physical Coding 232 Sublayer. 234 3.4.3. Use of ifTable for SONET/SDH Path Layer 236 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 237 Path Layer. The value of ifHighSpeed is set to 9585. ifSpeed 238 reports a value of 4294967295. 240 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer 242 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 243 Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953. 244 ifSpeed reports a value of 4294967295. 246 3.5. SONET/SDH Terminology 248 The SONET/SDH terminology used in [802.3ae] is mostly the same as in 249 [SONETng], but there are a few differences. In those cases the 250 definitions in [802.3ae] take precedence. The specific differences 251 are as follows. 253 Unequipped 254 This defect is not defined by [802.3ae]. An implementation that 255 supports it SHOULD report it by setting the sonetPathUnequipped 256 bit in the appropriate instance of sonetPathCurrentStatus. 258 Signal Label Mismatch 259 This defect is called Payload Label Mismatch (PLM) in [802.3ae]. 260 It is reported by setting both the sonetPathSignalLabelMismatch 261 bit in the appropriate instance of sonetPathCurrentStatus 262 (defined in [SONETng]) and the etherWisPathPLM bit in the 263 corresponding instance of etherWisPathCurrentStatus (defined 264 below). 266 Loss of Codegroup Delineation 267 [802.3ae] defines Loss of Codegroup Delineation (LCD) as 268 occurring when the Physical Coding Sublayer is unable to locate 269 64B/66B code group boundaries. There is no analogous defect 270 defined in [SONETng]. It is reported by setting the 271 etherWisPathLCD bit in the appropriate instance of the object 272 etherWisPathCurrentStatus defined below. 274 STS-Path Remote Defect Indication 275 [802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect 276 Indication - Path) defined in [T1.231] to signal remote server 277 defects (triggered by path AIS or path LOP) and remote payload 278 defects (triggered by Payload Label Mismatch or Loss of Codegroup 279 Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect 280 Indication - Path), which signals remote server detects (i.e., 281 path AIS and path LOP) only. An implementation of the MIB module 282 defined in this memo MUST set the sonetPathSTSRDI bit in the 283 appropriate instance of sonetPathCurrentStatus when it receives 284 an ERDI-P server defect indication from the remote end. Both 285 ERDI-P payload defects and ERDI-P server defects are reported in 286 the object etherWisFarEndPathCurrentStatus defined below. 288 Path Coding Violations 289 In [802.3ae] the path layer CV count is based on block errors and 290 not BIP-8 errors, i.e., it is incremented only once for each B3 291 byte that indicates incorrect parity, regardless of the number of 292 bits in error. Note that Section 8.4.5.1 of [T1.231] allows 293 either path BIP-8 errors or path block errors to be used for the 294 path layer error count. 296 3.6. Mapping of IEEE 802.3 Managed Objects 298 This section contains the mapping between oWIS managed objects 299 defined in [802.3ae] and managed objects defined in this document and 300 in associated MIB modules, i.e., the IF-MIB [RFC2863], the SONET-MIB 301 [SONETng], and the MAU-MIB [MAU-MIB]. 303 IEEE 802.3 Managed Object Corresponding SNMP Object 305 oWIS - pWISBasic package 306 aWISID IF-MIB - ifIndex 307 aSectionStatus SONET-MIB - sonetSectionCurrentStatus 308 aLineStatus SONET-MIB - sonetLineCurrentStatus 309 aPathStatus etherWisPathCurrentStatus 310 aFarEndPathStatus etherWisFarEndPathCurrentStatus 312 oWIS - pWISOptional package 313 aSectionSESThreshold SONET-MIB - sonetSESthresholdSet 314 aSectionSESs SONET-MIB - sonetSectionCurrentSESs + 315 sonetSectionIntervalSESs 316 aSectionESs SONET-MIB - sonetSectionCurrentESs + 317 sonetSectionIntervalESs 318 aSectionSEFSs SONET-MIB - sonetSectionCurrentSEFSs + 319 sonetSectionIntervalSEFSs 320 aSectionCVs SONET-MIB - sonetSectionCurrentCVs + 321 sonetSectionIntervalCVs 323 aJ0ValueTX etherWisSectionCurrentJ0Transmitted 324 aJ0ValueRX etherWisSectionCurrentJ0Received 325 aLineSESThreshold SONET-MIB - sonetSESthresholdSet 326 aLineSESs SONET-MIB - sonetLineCurrentSESs + 327 sonetLineIntervalSESs 328 aLineESs SONET-MIB - sonetLineCurrentESs + 329 sonetLineIntervalESs 330 aLineCVs SONET-MIB - sonetLineCurrentCVs + 331 sonetLineIntervalCVs 332 aFarEndLineSESs SONET-MIB - sonetFarEndLineCurrentSESs + 333 sonetFarEndLineIntervalSESs 334 aFarEndLineESs SONET-MIB - sonetFarEndLineCurrentESs + 335 sonetFarEndLineIntervalESs 336 aFarEndLineCVs SONET-MIB - sonetFarEndLineCurrentCVs + 337 sonetFarEndLineIntervalCVs 338 aPathSESThreshold SONET-MIB - sonetSESthresholdSet 339 aPathSESs SONET-MIB - sonetPathCurrentSESs + 340 sonetPathIntervalSESs 341 aPathESs SONET-MIB - sonetPathCurrentESs + 342 sonetPathIntervalESs 343 aPathCVs SONET-MIB - sonetPathCurrentCVs + 344 sonetPathIntervalCVs 345 aJ1ValueTX etherWisPathCurrentJ1Transmitted 346 aJ1ValueRX etherWisPathCurrentJ1Received 347 aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + 348 sonetFarEndPathIntervalSESs 349 aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + 350 sonetFarEndPathIntervalESs 351 aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + 352 sonetFarEndPathIntervalCVs 354 It should be noted that the threshold and counter objects imported 355 from the SONET-MIB are not completely equivalent to the corresponding 356 IEEE 802.3 objects. The specific differences are as follows: 358 IEEE 802.3 Managed Object How Corresponding SNMP Object Differs 360 aSectionSESThreshold This object is defined in [802.3ae] 361 as an integer with one instance per 362 interface. sonetSESthresholdSet 363 is an enumerated value that has one 364 instance per network element; it 365 controls the thresholds for all layers 366 simultaneously and allows only certain 367 discrete values to be selected. 368 aSectionSESs This object is defined in [802.3ae] as 369 a generalized nonresetable counter. 370 The objects sonetSectionCurrentSESs and 371 sonetSectionIntervalSESs are 15-minute 372 interval counters. 373 aSectionESs This object is defined as a generalized 374 nonresetable counter in [802.3ae]. 375 The objects sonetSectionCurrentESs and 376 sonetSectionIntervalESs are 15-minute 377 interval counters. 378 aSectionSEFSs This object is defined as a generalized 379 nonresetable counter in [802.3ae]. 380 The objects sonetSectionCurrentSEFSs and 381 sonetSectionIntervalSEFSs are 15-minute 382 interval counters. 383 aSectionCVs This object is defined as a generalized 384 nonresetable counter in [802.3ae], and 385 it is not subject to inhibiting. The 386 objects sonetSectionCurrentCVs and 387 sonetSectionIntervalCVs are 15-minute 388 interval counters, and they are 389 inhibited (not incremented) during 390 one-second intervals that qualify as 391 severely errored seconds. 392 aLineSESThreshold This object is defined in [802.3ae] 393 as an integer with one instance per 394 interface. sonetSESthresholdSet 395 is an enumerated value that has one 396 instance per network element; it 397 controls the thresholds for all layers 398 simultaneously and allows only certain 399 discrete values to be selected. 400 aLineSESs This object is defined as a generalized 401 nonresetable counter in [802.3ae], and 402 it is not subject to inhibiting. The 403 objects sonetLineCurrentSESs and 404 sonetLineIntervalSESs are 15-minute 405 interval counters, and they are 406 inhibited (not incremented) during 407 one-second intervals that qualify as 408 unavailable seconds. 409 aLineESs This object is defined as a generalized 410 nonresetable counter in [802.3ae], and 411 it is not subject to inhibiting. The 412 objects sonetLineCurrentESs and 413 sonetLineIntervalESs are 15-minute 414 interval counters, and they are 415 inhibited (not incremented) during 416 one-second intervals that qualify as 417 unavailable seconds. 418 aLineCVs This object is defined as a generalized 419 nonresetable counter in [802.3ae], and 420 it is not subject to inhibiting. The 421 objects sonetLineCurrentCVs and 422 sonetLineIntervalCVs are 15-minute 423 interval counters, and they are 424 inhibited (not incremented) during 425 one-second intervals that qualify 426 either as severely errored seconds 427 or as unavailable seconds. 428 aFarEndLineSESs This object is defined as a generalized 429 nonresetable counter in [802.3ae], and 430 it is not subject to inhibiting. The 431 objects sonetFarEndLineCurrentSESs and 432 sonetFarEndLineIntervalSESs are 433 15-minute interval counters, and they 434 are inhibited (not incremented) during 435 one-second intervals that qualify as 436 unavailable seconds. 437 aFarEndLineESs This object is defined as a generalized 438 nonresetable counter in [802.3ae], and 439 it is not subject to inhibiting. The 440 objects sonetFarEndLineCurrentESs and 441 sonetFarEndLineIntervalESs are 15-minute 442 interval counters, and they are 443 inhibited (not incremented) during 444 one-second intervals that qualify as 445 unavailable seconds. 446 aFarEndLineCVs This object is defined as a generalized 447 nonresetable counter in [802.3ae], and 448 it is not subject to inhibiting. The 449 objects sonetFarEndLineCurrentCVs and 450 sonetFarEndLineIntervalCVs are 15-minute 451 interval counters, and they are 452 inhibited (not incremented) during 453 one-second intervals that qualify 454 either as severely errored seconds 455 or as unavailable seconds. 456 aPathSESThreshold This object is defined in [802.3ae] 457 as an integer with one instance per 458 interface. sonetSESthresholdSet 459 is an enumerated value that has one 460 instance per network element; it 461 controls the thresholds for all layers 462 simultaneously and allows only certain 463 discrete values to be selected. 464 aPathSESs This object is defined as a generalized 465 nonresetable counter in [802.3ae], and 466 it is not subject to inhibiting. The 467 objects sonetPathCurrentSESs and 468 sonetPathIntervalSESs are 15-minute 469 interval counters, and they are 470 inhibited (not incremented) during 471 one-second intervals that qualify as 472 unavailable seconds. In addition, 473 [802.3ae] includes PLM-P and LCD-P 474 defects in the criteria for declaring 475 path layer severely errored seconds, 476 while [SONETng] does not. 477 aPathESs This object is defined as a generalized 478 nonresetable counter in [802.3ae], and 479 it is not subject to inhibiting. The 480 objects sonetPathCurrentESs and 481 sonetPathIntervalESs are 15-minute 482 interval counters, and they are 483 inhibited (not incremented) during 484 one-second intervals that qualify as 485 unavailable seconds. In addition, 486 [802.3ae] includes PLM-P and LCD-P 487 defects in the criteria for declaring 488 path layer errored seconds, while 489 [SONETng] does not. 490 aPathCVs This object is defined as a generalized 491 nonresetable counter in [802.3ae], and 492 it is not subject to inhibiting. The 493 objects sonetPathCurrentCVs and 494 sonetPathIntervalCVs are 15-minute 495 interval counters, and they are 496 inhibited (not incremented) during 497 one-second intervals that qualify 498 either as severely errored seconds 499 or as unavailable seconds. 500 aFarEndPathSESs This object is defined as a generalized 501 nonresetable counter in [802.3ae], and 502 it is not subject to inhibiting. The 503 objects sonetFarEndPathCurrentSESs and 504 sonetFarEndPathIntervalSESs are 505 15-minute interval counters, and they 506 are inhibited (not incremented) during 507 one-second intervals that qualify as 508 unavailable seconds. In addition, 509 [802.3ae] includes far-end PLM-P and 510 LCD-P defects in the criteria for 511 declaring far-end path layer severely 512 errored seconds, while [SONETng] does 513 not. 514 aFarEndPathESs This object is defined as a generalized 515 nonresetable counter in [802.3ae], and 516 it is not subject to inhibiting. The 517 objects sonetFarEndPathCurrentESs and 518 sonetFarEndPathIntervalESs are 15-minute 519 interval counters, and they are 520 inhibited (not incremented) during 521 one-second intervals that qualify as 522 unavailable seconds. In addition, 523 [802.3ae] includes far-end PLM-P and 524 LCD-P defects in the criteria for 525 declaring far-end path layer errored 526 seconds, while [SONETng] does not. 527 aFarEndPathCVs This object is defined as a generalized 528 nonresetable counter in [802.3ae], and 529 it is not subject to inhibiting. The 530 objects sonetFarEndPathCurrentCVs and 531 sonetFarEndPathIntervalCVs are 15-minute 532 interval counters, and they are 533 inhibited (not incremented) during 534 one-second intervals that qualify 535 either as severely errored seconds 536 or as unavailable seconds. 538 Note: despite the semantic differences between the threshold objects 539 and counter objects imported from the SONET-MIB and the corresponding 540 IEEE 802.3 objects, the hardware support mandated by [802.3ae] 541 subclause 50.3.11 suffices for both. See Appendix A for details. 543 3.7. Mapping of SNMP Objects to WIS Station Management Registers 545 Some of the objects defined in this memo or incorporated by reference 546 from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- 547 specific hardware support. [802.3ae] subclause 50.3.11 specifies WIS 548 management interface requirements, including a required subset of the 549 WIS Management Data Input/Output (MDIO) registers defined in 550 [802.3ae] subclause 45.2.2. The table below provides a cross- 551 reference between those managed objects and the WIS MDIO registers 552 from the subset in [802.3ae] subclause 50.3.11 required to support 553 them. Note that the MDIO interface is optional; however, if it is 554 not implemented, then the capabilities of the required register 555 subset must be provided by other means. 557 SNMP Object WIS MDIO Register(s) 559 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS control 2 560 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS control 2 561 ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS test pattern 562 error counter 564 SONET-MIB - sonetMediumType none required 565 SONET-MIB - sonetMediumTimeElapsed none required 566 SONET-MIB - sonetMediumValidIntervals none required 567 SONET-MIB - sonetMediumLineCoding none required 568 SONET-MIB - sonetMediumLineType none required 569 SONET-MIB - sonetMediumCircuitIdentifier none required 570 SONET-MIB - sonetMediumInvalidIntervals none required 571 SONET-MIB - sonetMediumLoopbackConfig none required 572 SONET-MIB - sonetSESthresholdSet none required 574 ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 transmit 575 ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 receive 577 SONET-MIB - sonetSectionCurrentStatus 10G WIS status 3 578 SONET-MIB - sonetSectionCurrentESs \ 579 SONET-MIB - sonetSectionCurrentSESs \ 580 SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS status 3 581 SONET-MIB - sonetSectionCurrentCVs | + 582 SONET-MIB - sonetSectionIntervalESs | 10G WIS section 583 SONET-MIB - sonetSectionIntervalSESs | BIP error count 584 SONET-MIB - sonetSectionIntervalSEFSs / 585 SONET-MIB - sonetSectionIntervalCVs / 586 SONET-MIB - sonetSectionIntervalValidData none required 588 SONET-MIB - sonetLineCurrentStatus 10G WIS status 3 589 SONET-MIB - sonetLineCurrentESs \ 590 SONET-MIB - sonetLineCurrentSESs \ 591 SONET-MIB - sonetLineCurrentCVs | 10G WIS status 3 592 SONET-MIB - sonetLineCurrentUASs | + 593 SONET-MIB - sonetLineIntervalESs | 10G WIS line 594 SONET-MIB - sonetLineIntervalSESs | BIP errors 595 SONET-MIB - sonetLineIntervalCVs / 596 SONET-MIB - sonetLineIntervalUASs / 597 SONET-MIB - sonetLineIntervalValidData none required 599 SONET-MIB - sonetFarEndLineCurrentESs \ 600 SONET-MIB - sonetFarEndLineCurrentSESs \ 601 SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS status 3 602 SONET-MIB - sonetFarEndLineCurrentUASs | + 603 SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS far end 604 SONET-MIB - sonetFarEndLineIntervalSESs | line BIP errors 605 SONET-MIB - sonetFarEndLineIntervalCVs / 606 SONET-MIB - sonetFarEndLineIntervalUASs / 607 SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS status 3 609 ETHER-WIS - etherWisPathCurrentStatus 10G WIS status 3 610 ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 transmit 611 ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 receive 612 SONET-MIB - sonetPathCurrentWidth none required 613 SONET-MIB - sonetPathCurrentStatus 10G WIS status 3 614 SONET-MIB - sonetPathCurrentESs \ 615 SONET-MIB - sonetPathCurrentSESs \ 616 SONET-MIB - sonetPathCurrentCVs | 10G WIS status 3 617 SONET-MIB - sonetPathCurrentUASs | + 618 SONET-MIB - sonetPathIntervalESs | 10G WIS 619 SONET-MIB - sonetPathIntervalSESs | path block 620 SONET-MIB - sonetPathIntervalCVs / error count 621 SONET-MIB - sonetPathIntervalUASs / 622 SONET-MIB - sonetPathIntervalValidData none required 624 ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS status 3 626 SONET-MIB - sonetFarEndPathCurrentESs \ 627 SONET-MIB - sonetFarEndPathCurrentSESs \ 628 SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS status 3 629 SONET-MIB - sonetFarEndPathCurrentUASs | + 630 SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS far end 631 SONET-MIB - sonetFarEndPathIntervalSESs | path block 632 SONET-MIB - sonetFarEndPathIntervalCVs / error count 633 SONET-MIB - sonetFarEndPathIntervalUASs / 634 SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS status 3 636 MAU-MIB - ifMauIfIndex none required 637 MAU-MIB - ifMauIndex none required 638 MAU-MIB - ifMauType 10G WIS control 2 639 MAU-MIB - ifMauStatus WIS control 1 640 MAU-MIB - ifMauMediaAvailable \ WIS status 1 + 641 MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS status 3 642 MAU-MIB - ifMauJabberState none required 643 MAU-MIB - ifMauJabberingStateEnters none required 644 MAU-MIB - ifMauFalseCarriers none required 645 MAU-MIB - ifMauDefaultType 10G WIS control 2 646 MAU-MIB - ifMauAutoNegSupported none required 647 MAU-MIB - ifMauTypeListBits 10G WIS status 2 649 3.8. Structure of the MIB Module 651 Four tables are defined in this MIB module. 653 3.8.1. etherWisDeviceTable 655 The purpose of this table is to define managed objects to control the 656 WIS test pattern mode. These objects are required to support 657 mandatory and optional WIS test features specified in [802.3ae] 658 subclause 50.3.8. 660 The etherWisDeviceTable is a sparse augmentation of the 661 sonetMediumTable of the SONET-MIB -- in other words, for each entry 662 in the etherWisDeviceTable there MUST be an entry in the 663 sonetMediumTable and the same ifIndex value MUST be used for both 664 entries. 666 3.8.2. etherWisSectionCurrentTable 668 The purpose of this table is to define managed objects for the 669 transmitted and received section trace messages (J0 byte). 671 The etherWisSectionCurrentTable is a sparse augmentation of the 672 sonetSectionCurrentTable of the SONET-MIB -- in other words, for each 673 entry in the etherWisSectionCurrentTable there MUST be an entry in 674 the sonetSectionCurrentTable and the same ifIndex value MUST be used 675 for both entries. 677 3.8.3. etherWisPathCurrentTable 679 The purpose of this table is to define managed objects for the 680 current WIS path layer status and for the transmitted and received 681 path trace messages (J1 byte). The path layer status object is 682 provided because the WIS supports some near-end path status 683 conditions that are not reported in sonetPathCurrentStatus. 685 The etherWisPathCurrentTable is a sparse augmentation of the 686 sonetPathCurrentTable of the SONET-MIB -- in other words, for each 687 entry in the etherWisPathCurrentTable there MUST be an entry in the 688 sonetPathCurrentTable and the same ifIndex value MUST be used for 689 both entries. 691 3.8.4. etherWisFarEndPathCurrentTable 693 The purpose of this table is to define a managed object for the 694 current status of the far end of the path. This object is provided 695 because the WIS supports some far-end path status conditions that are 696 not reported in sonetPathCurrentStatus. 698 The etherWisFarEndPathCurrentTable is a sparse augmentation of the 699 sonetFarEndPathCurrentTable of the SONET-MIB -- in other words, for 700 each entry in the etherWisFarEndPathCurrentTable there MUST be an 701 entry in the sonetFarEndPathCurrentTable and the same ifIndex value 702 MUST be used for both entries. 704 4. Object Definitions 706 ETHER-WIS DEFINITIONS ::= BEGIN 708 IMPORTS 709 MODULE-IDENTITY, OBJECT-TYPE, 710 Gauge32, transmission 711 FROM SNMPv2-SMI 712 ifIndex 713 FROM IF-MIB 714 MODULE-COMPLIANCE, OBJECT-GROUP 715 FROM SNMPv2-CONF 716 sonetMediumStuff2, sonetSectionStuff2, 717 sonetLineStuff2, sonetFarEndLineStuff2, 718 sonetPathStuff2, sonetFarEndPathStuff2, 719 sonetMediumType, sonetMediumLineCoding, 720 sonetMediumLineType, sonetMediumCircuitIdentifier, 721 sonetMediumLoopbackConfig, sonetSESthresholdSet, 722 sonetPathCurrentWidth 723 FROM SONET-MIB; 725 etherWisMIB MODULE-IDENTITY 726 LAST-UPDATED "200212132358Z" -- December 13, 2002 727 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 728 Working Group" 729 CONTACT-INFO 730 "WG charter: 731 http://www.ietf.org/html.charters/hubmib-charter.html 733 Chair: Dan Romascanu 734 Postal: Avaya Inc. 735 Atidim Technology Park, Bldg. 3 736 Tel Aviv 61131 737 Israel 738 Tel: +972 3 645 8414 739 E-mail: dromasca@avaya.com 741 Editor: C. M. Heard 742 Postal: 600 Rainbow Dr. #141 743 Mountain View, CA 94041-2542 744 USA 745 Tel: +1 650-964-8391 746 E-mail: heard@pobox.com" 748 DESCRIPTION 749 "The objects in this MIB module are used in conjunction 750 with objects in the SONET-MIB and the MAU-MIB to manage 751 the Ethernet WAN Interface Sublayer (WIS). 753 The following reference is used throughout this MIB module: 755 [IEEE 802.3 Std] refers to: 756 IEEE Std 802.3, 2000 Edition: 'IEEE Standard for 757 Information technology - Telecommunications and 758 information exchange between systems - Local and 759 metropolitan area networks - Specific requirements - 760 Part 3: Carrier sense multiple access with collision 761 detection (CSMA/CD) access method and physical layer 762 specifications', as amended by IEEE Std 802.3ae-2002, 763 'IEEE Standard for Carrier Sense Multiple Access with 764 Collision Detection (CSMA/CD) Access Method and 765 Physical Layer Specifications - Media Access Control 766 (MAC) Parameters, Physical Layer and Management 767 Parameters for 10 Gb/s Operation', 30 August 2002. 769 Of particular interest are Clause 50, 'WAN Interface 770 Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 771 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 772 Aggregation Management', and Clause 45, 'Management 773 Data Input/Output (MDIO) Interface'. 775 Copyright (C) The Internet Society (2002). This version 776 of this MIB module is part of RFC yyyy; see the RFC 777 itself for full legal notices." 778 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 780 REVISION "200212132358Z" -- December 13, 2002 781 DESCRIPTION "Initial version, published as RFC yyyy." 782 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 784 ::= { transmission XXX } 785 -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 786 -- The main sections of the module 788 etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } 790 etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } 792 etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } 794 -- groups in the Ethernet WIS MIB module 796 etherWisDevice OBJECT IDENTIFIER ::= { etherWisObjects 1 } 798 etherWisSection OBJECT IDENTIFIER ::= { etherWisObjects 2 } 800 etherWisPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 1 } 802 etherWisFarEndPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 2 } 804 -- The Device group 806 -- These objects provide WIS extensions to 807 -- the SONET-MIB Medium Group. 809 etherWisDeviceTable OBJECT-TYPE 810 SYNTAX SEQUENCE OF EtherWisDeviceEntry 811 MAX-ACCESS not-accessible 812 STATUS current 813 DESCRIPTION 814 "The table for Ethernet WIS devices" 815 ::= { etherWisDevice 1 } 817 etherWisDeviceEntry OBJECT-TYPE 818 SYNTAX EtherWisDeviceEntry 819 MAX-ACCESS not-accessible 820 STATUS current 821 DESCRIPTION 822 "An entry in the Ethernet WIS device table. For each 823 instance of this object there MUST be a corresponding 824 instance of sonetMediumEntry." 825 INDEX { ifIndex } 826 ::= { etherWisDeviceTable 1 } 828 EtherWisDeviceEntry ::= 829 SEQUENCE { 830 etherWisDeviceTxTestPatternMode INTEGER, 831 etherWisDeviceRxTestPatternMode INTEGER, 832 etherWisDeviceRxTestPatternErrors Gauge32 833 } 835 etherWisDeviceTxTestPatternMode OBJECT-TYPE 836 SYNTAX INTEGER { 837 none(1), 838 squareWave(2), 839 prbs31(3), 840 mixedFrequency(4) 841 } 842 MAX-ACCESS read-write 843 STATUS current 844 DESCRIPTION 845 "This variable controls the transmit test pattern mode. 846 The value none(1) puts the the WIS transmit path into 847 the normal operating mode. The value squareWave(2) puts 848 the WIS transmit path into the square wave test pattern 849 mode described in [IEEE 802.3 Std.] subclause 50.3.8.1. 850 The value prbs31(3) puts the WIS transmit path into the 851 PRBS31 test pattern mode described in [IEEE 802.3 Std.] 852 subclause 50.3.8.2. The value mixedFrequency(4) puts the 853 WIS transmit path into the mixed frequency test pattern 854 mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. 855 Any attempt to set this object to a value other than 856 none(1) when the corresponding instance of ifAdminStatus 857 has the value up(1) MUST be rejected with the error 858 inconsistentValue, and any attempt to set the corresponding 859 instance of ifAdminStatus to the value up(1) when an 860 instance of this object has a value other than none(1) 861 MUST be rejected with the error inconsistentValue." 862 REFERENCE 863 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 864 checker, 45.2.2.6, 10G WIS control 2 register (2.7), and 865 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 866 ::= { etherWisDeviceEntry 1 } 868 etherWisDeviceRxTestPatternMode OBJECT-TYPE 869 SYNTAX INTEGER { 870 none(1), 871 prbs31(3), 872 mixedFrequency(4) 873 } 874 MAX-ACCESS read-write 875 STATUS current 876 DESCRIPTION 877 "This variable controls the receive test pattern mode. 878 The value none(1) puts the the WIS receive path into the 879 normal operating mode. The value prbs31(3) puts the WIS 880 receive path into the PRBS31 test pattern mode described 881 in [IEEE 802.3 Std.] subclause 50.3.8.2. The value 882 mixedFrequency(4) puts the WIS receive path into the mixed 883 frequency test pattern mode described in [IEEE 802.3 Std.] 884 subclause 50.3.8.3. Any attempt to set this object to a 885 value other than none(1) when the corresponding instance 886 of ifAdminStatus has the value up(1) MUST be rejected with 887 the error inconsistentValue, and any attempt to set the 888 corresponding instance of ifAdminStatus to the value up(1) 889 when an instance of this object has a value other than 890 none(1) MUST be rejected with the error inconsistentValue." 891 REFERENCE 892 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 893 checker, 45.2.2.6, 10G WIS control 2 register (2.7), and 894 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 895 ::= { etherWisDeviceEntry 2 } 897 etherWisDeviceRxTestPatternErrors OBJECT-TYPE 898 SYNTAX Gauge32 ( 0..65535 ) 899 MAX-ACCESS read-write 900 STATUS current 901 DESCRIPTION 902 "This object counts the number of errors detected when the 903 WIS receive path is operating in the PRBS31 test pattern 904 mode. It is reset to zero when the WIS receive path 905 initially enters that mode, and it increments each time 906 the PRBS pattern checker detects an error as described in 907 [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is 908 65535, in which case it remains unchanged. This object is 909 writeable so that it may be reset upon explicit request 910 of a command generator application while the WIS receive 911 path continues to operate in PRBS31 test pattern mode." 912 REFERENCE 913 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 914 checker, 45.2.2.7.2, PRBS31 pattern testing ability 915 (2.8.1), and 45.2.2.8, 10G WIS test pattern error counter 916 register (2.9)." 917 ::= { etherWisDeviceEntry 3 } 919 -- The Section group 921 -- These objects provide WIS extensions to 922 -- the SONET-MIB Section Group. 924 etherWisSectionCurrentTable OBJECT-TYPE 925 SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry 926 MAX-ACCESS not-accessible 927 STATUS current 928 DESCRIPTION 929 "The table for the current state of Ethernet WIS sections." 930 ::= { etherWisSection 1 } 932 etherWisSectionCurrentEntry OBJECT-TYPE 933 SYNTAX EtherWisSectionCurrentEntry 934 MAX-ACCESS not-accessible 935 STATUS current 936 DESCRIPTION 937 "An entry in the etherWisSectionCurrentTable. For each 938 instance of this object there MUST be a corresponding 939 instance of sonetSectionCurrentEntry." 940 INDEX { ifIndex } 941 ::= { etherWisSectionCurrentTable 1 } 943 EtherWisSectionCurrentEntry ::= 944 SEQUENCE { 945 etherWisSectionCurrentJ0Transmitted OCTET STRING, 946 etherWisSectionCurrentJ0Received OCTET STRING 947 } 949 etherWisSectionCurrentJ0Transmitted OBJECT-TYPE 950 SYNTAX OCTET STRING (SIZE (16)) 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 "This is the 16-octet section trace message that 955 is transmitted in the J0 byte. The value SHOULD 956 be '89'h followed by fifteen octets of '00'h 957 (or some cyclic shift thereof) when the section 958 trace function is not used, and the implementation 959 SHOULD use that value (or a cyclic shift thereof) 960 as a default if no other value has been set." 961 REFERENCE 962 "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." 963 ::= { etherWisSectionCurrentEntry 1 } 965 etherWisSectionCurrentJ0Received OBJECT-TYPE 966 SYNTAX OCTET STRING (SIZE (16)) 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION 970 "This is the 16-octet section trace message that 971 was most recently received in the J0 byte." 972 REFERENCE 973 "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." 974 ::= { etherWisSectionCurrentEntry 2 } 976 -- The Path group 978 -- These objects provide WIS extensions to 979 -- the SONET-MIB Path Group. 981 etherWisPathCurrentTable OBJECT-TYPE 982 SYNTAX SEQUENCE OF EtherWisPathCurrentEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "The table for the current state of Ethernet WIS paths." 987 ::= { etherWisPath 1 } 989 etherWisPathCurrentEntry OBJECT-TYPE 990 SYNTAX EtherWisPathCurrentEntry 991 MAX-ACCESS not-accessible 992 STATUS current 993 DESCRIPTION 994 "An entry in the etherWisPathCurrentTable. For each 995 instance of this object there MUST be a corresponding 996 instance of sonetPathCurrentEntry." 997 INDEX { ifIndex } 998 ::= { etherWisPathCurrentTable 1 } 1000 EtherWisPathCurrentEntry ::= 1001 SEQUENCE { 1002 etherWisPathCurrentStatus BITS, 1003 etherWisPathCurrentJ1Transmitted OCTET STRING, 1004 etherWisPathCurrentJ1Received OCTET STRING 1005 } 1007 etherWisPathCurrentStatus OBJECT-TYPE 1008 SYNTAX BITS { 1009 etherWisPathLOP(0), 1010 etherWisPathAIS(1), 1011 etherWisPathPLM(2), 1012 etherWisPathLCD(3) 1013 } 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "This variable indicates the current status of the 1018 path payload with a bit map that can indicate multiple 1019 defects at once. The bit positions are assigned as 1020 follows: 1022 etherWisPathLOP(0) 1023 This bit is set to indicate that an 1024 LOP-P (Loss of Pointer - Path) defect 1025 is being experienced. Note: when this 1026 bit is set, sonetPathSTSLOP MUST be set 1027 in the corresponding instance of 1028 sonetPathCurrentStatus. 1030 etherWisPathAIS(1) 1031 This bit is set to indicate that an 1032 AIS-P (Alarm Indication Signal - Path) 1033 defect is being experienced. Note: when 1034 this bit is set, sonetPathSTSAIS MUST be 1035 set in the corresponding instance of 1036 sonetPathCurrentStatus. 1038 etherWisPathPLM(1) 1039 This bit is set to indicate that a 1040 PLM-P (Payload Label Mismatch - Path) 1041 defect is being experienced. Note: when 1042 this bit is set, sonetPathSignalLabelMismatch 1043 MUST be set in the corresponding instance of 1044 sonetPathCurrentStatus. 1046 etherWisPathLCD(3) 1047 This bit is set to indicate that an 1048 LCD-P (Loss of Codegroup Delination - Path) 1049 defect is being experienced. Since this 1050 defect is detected by the PCS and not by 1051 the path layer itself, there is no 1052 corresponding bit in sonetPathCurrentStatus." 1053 REFERENCE 1054 "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." 1055 ::= { etherWisPathCurrentEntry 1 } 1057 etherWisPathCurrentJ1Transmitted OBJECT-TYPE 1058 SYNTAX OCTET STRING (SIZE (16)) 1059 MAX-ACCESS read-write 1060 STATUS current 1061 DESCRIPTION 1062 "This is the 16-octet path trace message that 1063 is transmitted in the J1 byte. The value SHOULD 1064 be '89'h followed by fifteen octets of '00'h 1065 (or some cyclic shift thereof) when the path 1066 trace function is not used, and the implementation 1067 SHOULD use that value (or a cyclic shift thereof) 1068 as a default if no other value has been set." 1069 REFERENCE 1070 "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." 1071 ::= { etherWisPathCurrentEntry 2 } 1073 etherWisPathCurrentJ1Received OBJECT-TYPE 1074 SYNTAX OCTET STRING (SIZE (16)) 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "This is the 16-octet path trace message that 1079 was most recently received in the J1 byte." 1080 REFERENCE 1081 "[IEEE 802.3 Std.], 30.8.1.1.24, aJ1ValueRX." 1082 ::= { etherWisPathCurrentEntry 3 } 1084 -- The Far End Path group 1086 -- These objects provide WIS extensions to 1087 -- the SONET-MIB Far End Path Group. 1089 etherWisFarEndPathCurrentTable OBJECT-TYPE 1090 SYNTAX SEQUENCE OF EtherWisFarEndPathCurrentEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "The table for the current far-end state of Ethernet WIS 1095 paths." 1096 ::= { etherWisFarEndPath 1 } 1098 etherWisFarEndPathCurrentEntry OBJECT-TYPE 1099 SYNTAX EtherWisFarEndPathCurrentEntry 1100 MAX-ACCESS not-accessible 1101 STATUS current 1102 DESCRIPTION 1103 "An entry in the etherWisFarEndPathCurrentTable. For each 1104 instance of this object there MUST be a corresponding 1105 instance of sonetFarEndPathCurrentEntry." 1106 INDEX { ifIndex } 1107 ::= { etherWisFarEndPathCurrentTable 1 } 1109 EtherWisFarEndPathCurrentEntry ::= 1110 SEQUENCE { 1111 etherWisFarEndPathCurrentStatus BITS 1112 } 1114 etherWisFarEndPathCurrentStatus OBJECT-TYPE 1115 SYNTAX BITS { 1116 etherWisFarEndPayloadDefect(0), 1117 etherWisFarEndServerDefect(1) 1118 } 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "This variable indicates the current status at the 1123 far end of the path using a bit map that can indicate 1124 multiple defects at once. The bit positions are 1125 assigned as follows: 1127 etherWisFarEndPayloadDefect(0) 1128 A far end payload defect (i.e., far end 1129 PLM-P or LCD-P) is currently being signalled 1130 in G1 bits 5-7. 1132 etherWisFarEndServerDefect(1) 1133 A far end server defect (i.e., far end 1134 LOP-P or AIS-P) is currently being signalled 1135 in G1 bits 5-7. Note: when this bit is set, 1136 sonetPathSTSRDI MUST be set in the corresponding 1137 instance of sonetPathCurrentStatus." 1138 REFERENCE 1139 "[IEEE 802.3 Std.], 30.8.1.1.25, aFarEndPathStatus." 1140 ::= { etherWisFarEndPathCurrentEntry 1 } 1142 -- 1143 -- Conformance Statements 1144 -- 1146 etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } 1148 etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } 1150 -- Object Groups 1152 etherWisDeviceGroupBasic OBJECT-GROUP 1153 OBJECTS { 1154 etherWisDeviceTxTestPatternMode, 1155 etherWisDeviceRxTestPatternMode 1156 } 1157 STATUS current 1158 DESCRIPTION 1159 "A collection of objects that support test 1160 features required of all WIS devices." 1161 ::= { etherWisGroups 1 } 1163 etherWisDeviceGroupExtra OBJECT-GROUP 1164 OBJECTS { 1165 etherWisDeviceRxTestPatternErrors 1166 } 1167 STATUS current 1168 DESCRIPTION 1169 "A collection of objects that support 1170 optional WIS device test features." 1171 ::= { etherWisGroups 2 } 1173 etherWisSectionGroup OBJECT-GROUP 1174 OBJECTS { 1175 etherWisSectionCurrentJ0Transmitted, 1176 etherWisSectionCurrentJ0Received 1177 } 1178 STATUS current 1179 DESCRIPTION 1180 "A collection of objects that provide 1181 required information about a WIS section." 1182 ::= { etherWisGroups 3 } 1184 etherWisPathGroup OBJECT-GROUP 1185 OBJECTS { 1186 etherWisPathCurrentStatus, 1187 etherWisPathCurrentJ1Transmitted, 1188 etherWisPathCurrentJ1Received 1189 } 1190 STATUS current 1191 DESCRIPTION 1192 "A collection of objects that provide 1193 required information about a WIS path." 1194 ::= { etherWisGroups 4 } 1196 etherWisFarEndPathGroup OBJECT-GROUP 1197 OBJECTS { 1198 etherWisFarEndPathCurrentStatus 1199 } 1200 STATUS current 1201 DESCRIPTION 1202 "A collection of objects that provide required 1203 information about the far end of a WIS path." 1204 ::= { etherWisGroups 5 } 1206 -- Compliance Statements 1208 etherWisCompliance MODULE-COMPLIANCE 1209 STATUS current 1210 DESCRIPTION 1211 "The compliance statement for this module." 1213 MODULE -- this module 1214 MANDATORY-GROUPS { 1215 etherWisDeviceGroupBasic, 1216 etherWisSectionGroup, 1217 etherWisPathGroup, 1218 etherWisFarEndPathGroup 1219 } 1221 OBJECT etherWisDeviceTxTestPatternMode 1222 SYNTAX INTEGER { 1223 none(1), 1224 squareWave(2), 1225 mixedFrequency(4) 1226 } 1227 DESCRIPTION 1228 "Support for values other than none(1), 1229 squareWave(2), and mixedFrequency(4) 1230 is not required. Furthermore, an 1231 implementation is not required to allow 1232 assignment of a value other than none(1) 1233 if that assignment would result in this 1234 object and etherWisDeviceRxTestPatternMode 1235 having values other than none(1) that are 1236 not the same." 1238 OBJECT etherWisDeviceRxTestPatternMode 1239 SYNTAX INTEGER { 1240 none(1), 1241 mixedFrequency(4) 1242 } 1243 DESCRIPTION 1244 "Support for values other than none(1) 1245 and mixedFrequency(4) is not required. 1246 Furthermore, an implementation is not 1247 required to allow assignment of a value 1248 other than none(1) if that assignment 1249 would result in this object and 1250 etherWisDeviceTxTestPatternMode having 1251 values other than none(1) that are 1252 not the same." 1254 GROUP etherWisDeviceGroupExtra 1255 DESCRIPTION 1256 "Implementation of this group, along with support for 1257 the value prbs31(3) for etherWisDeviceTxTestPatternMode 1258 and etherWisDeviceRxTestPatternMode, is necessary if the 1259 optional PRBS31 test pattern mode is to be supported." 1261 OBJECT etherWisDeviceRxTestPatternErrors 1262 WRITE-SYNTAX Gauge32 ( 0 ) 1263 DESCRIPTION 1264 "An implementation is not required to 1265 allow values other than zero to be 1266 written to this object." 1268 MODULE SONET-MIB 1269 MANDATORY-GROUPS { 1270 sonetMediumStuff2, 1271 sonetSectionStuff2, 1272 sonetLineStuff2, 1273 sonetFarEndLineStuff2, 1274 sonetPathStuff2, 1275 sonetFarEndPathStuff2 1276 } 1278 OBJECT sonetMediumType 1279 SYNTAX INTEGER { 1280 sonet(1) 1281 } 1282 MIN-ACCESS read-only 1283 DESCRIPTION 1284 "Write access is not required, nor is support 1285 for any value other than sonet(1)." 1287 OBJECT sonetMediumLineCoding 1288 SYNTAX INTEGER { 1289 sonetMediumNRZ(4) 1290 } 1291 MIN-ACCESS read-only 1292 DESCRIPTION 1293 "Write access is not required, nor is support 1294 for any value other than sonetMediumNRZ(4)." 1296 OBJECT sonetMediumLineType 1297 MIN-ACCESS read-only 1298 DESCRIPTION 1299 "Write access is not required." 1301 OBJECT sonetMediumCircuitIdentifier 1302 MIN-ACCESS read-only 1303 DESCRIPTION 1304 "Write access is not required." 1306 OBJECT sonetMediumLoopbackConfig 1307 SYNTAX BITS { 1308 sonetNoLoop(0), 1309 sonetFacilityLoop(1) 1310 } 1311 MIN-ACCESS read-only 1312 DESCRIPTION 1313 "Write access is not required, nor is support for values 1314 other than sonetNoLoop(0) and sonetFacilityLoop(1)." 1316 OBJECT sonetSESthresholdSet 1317 MIN-ACCESS read-only 1318 DESCRIPTION 1319 "Write access is not required, and only one 1320 of the enumerated values need be supported." 1322 OBJECT sonetPathCurrentWidth 1323 SYNTAX INTEGER { 1324 sts192cSTM64(6) 1325 } 1326 MIN-ACCESS read-only 1327 DESCRIPTION 1328 "Write access is not required, nor is support 1329 for any value other than sts192cSTM64(6)." 1331 ::= { etherWisCompliances 1 } 1333 END 1335 5. Acknowledgments 1337 This document is a product of the IETF Hubmib and AToMMIB Working 1338 Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit 1339 Ethernet Task Force. 1341 6. Security Considerations 1343 There are five managed objects defined in this MIB module that have a 1344 MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode, 1345 etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors, 1346 etherWisSectionCurrentJ0Transmitted, and 1347 etherWisPathCurrentJ1Transmitted. Writing to these objects can have 1348 the following potentially disruptive effects on network operation: 1350 o changing the transmit or receive test pattern mode or modifying 1351 the accumulated error count from a PRBS31 pattern test on an 1352 administratively disabled 10GBASE-W interface, which can 1353 interfere with an in-progress pattern test; 1355 o modifying the transmitted section trace and/or path trace 1356 message on an operational 10GBASE-W interface, which can cause 1357 connectivity alarms to be raised at the remote of the link. 1359 The user of this MIB module must therefore be aware that support for 1360 SET operations in a non-secure environment without proper protection 1361 can have a negative effect on network operations. 1363 All other managed objects in this MIB module have a MAX-ACCESS clause 1364 of read-only. The information contained in those objects may be 1365 considered sensitive in some network environments. In such 1366 environments it is important to control even GET access to those 1367 objects and possibly to even encrypt the values of these objects when 1368 sending them over the network via SNMP. 1370 SNMP versions prior to SNMPv3 did not include adequate security. 1371 Even if the network itself is secure (for example by using IPSec), 1372 even then, there is no control as to who on the secure network is 1373 allowed to access and GET/SET (read/change/create/delete) the objects 1374 in this MIB module. 1376 It is RECOMMENDED that implementers consider the security features as 1377 provided by the SNMPv3 framework (see [RFC2570bis], section 8), 1378 inluding full support for the SNMPv3 cryptographic mechanisms (for 1379 authentication and privacy). 1381 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1382 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1383 enable cryptographic security. It is a customer/operator 1384 responsibility to ensure that the SNMP entity giving access to an 1385 instance of this MIB module, is properly configured to give access to 1386 the objects only to those principals (users) that have legitimate 1387 rights to indeed GET or SET (change/create/delete) them. 1389 7. References 1391 7.1. Normative References 1393 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1394 Requirements Levels", BCP 14, RFC 2119, March 1997. 1396 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1397 Rose, M., and S. Waldbusser, "Structure of Management 1398 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1399 1999. 1401 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1402 Rose, M., and S. Waldbusser, "Textual Conventions for 1403 SMIv2", STD 58, RFC 2579, April 1999. 1405 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1406 Rose, M., and S. Waldbusser, "Conformance Statements for 1407 SMIv2", STD 58, RFC 2580, April 1999. 1409 [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1410 MIB", RFC 2863, June 2000. 1412 [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table 1413 Extension to the Interfaces Group MIB", RFC 2864, June 2000. 1415 [SONETng] Tesink, K., "Definitions of Managed Objects for the 1416 SONET/SDH Interface Type", , work in progress. 1419 [T1.231] American National Standard for Telecommunications - Digital 1420 Hierarchy - Layer 1 In-Service Digital Transmission 1421 Performance Monitoring, ANSI T1.231-1997, September 1997. 1423 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 1424 Ethernet-like Interface Types", , work in progress. 1427 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1428 Medium Attachment Units (MAUs)", , work in progress. 1431 [802.3ae] Institute of Electrical and Electronic Engineers, IEEE Std 1432 802.3ae-2002, "IEEE Standard for Carrier Sense Multiple 1433 Access with Collision Detection (CSMA/CD) Access Method and 1434 Physical Layer Specifications - Media Access Control (MAC) 1435 Parameters, Physical Layer and Management Parameters for 10 1436 Gb/s Operation", August 2002. 1438 7.2. Informative References 1440 [RFC2570bis] 1441 Case, J., Mundy, R., Partain, D., and B. Stewart, 1442 "Introduction and Applicability Statements for Internet- 1443 Standard Management Framework", , work in progress. 1446 8. Authors' Addresses 1448 Mike Ayers 1449 1204 Knox Ave. 1450 San Jose, CA 95122 1451 USA 1453 Phone: +1 408 857 6810 1454 EMail: mike.ayers@earthling.net 1456 John Flick 1457 Hewlett-Packard Company 1458 8000 Foothills Blvd. M/S 5557 1459 Roseville, CA 95747-5557 1460 USA 1462 Phone: +1 916 785 4018 1463 Fax: +1 916 785 1199 1464 EMail: johnf@rose.hp.com 1466 C. M. Heard 1467 600 Rainbow Dr. #141 1468 Mountain View, CA 94041-2542 1469 USA 1471 Phone: +1 650 964 8391 1472 EMail: heard@pobox.com 1474 Kam Lam 1475 Lucent Technologies 1476 101 Crawfords Corner Road, Room 4C-616A 1477 Holmdel, NJ 07733 1478 USA 1480 Phone: +1 732 949 8338 1481 EMail: hklam@lucent.com 1482 Kerry McDonald 1483 Institute for Applied Supercomputing 1484 California State University San Bernardino 1486 EMail: kerry_mcd@hotmail.com 1487 kmcdonal@csci.csusb.edu 1489 K. C. Norseth 1490 934 S. Palos Verdes Dr. 1491 Kaysville, Utah 84037 1492 USA 1494 Phone: +1 801 546 3316 1495 EMail: kcn@norseth.com 1497 Kaj Tesink 1498 Telcordia Technologies 1499 331 Newman Springs Road 1500 P.O. Box 7020 1501 Red Bank, NJ 07701-7020 1502 USA 1504 Phone: +1 732 758 5254 1505 EMail: kaj@research.telcordia.com 1507 9. Intellectual Property 1509 The IETF takes no position regarding the validity or scope of any 1510 intellectual property or other rights that might be claimed to 1511 pertain to the implementation or use of the technology described in 1512 this document or the extent to which any license under such rights 1513 might or might not be available; neither does it represent that it 1514 has made any effort to identify any such rights. Information on the 1515 IETF's procedures with respect to rights in standards-track and 1516 standards-related documentation can be found in BCP-11. Copies of 1517 claims of rights made available for publication and any assurances of 1518 licenses to be made available, or the result of an attempt made to 1519 obtain a general license or permission for the use of such 1520 proprietary rights by implementors or users of this specification can 1521 be obtained from the IETF Secretariat. 1523 The IETF invites any interested party to bring to its attention any 1524 copyrights, patents or patent applications, or other proprietary 1525 rights which may cover technology that may be required to practice 1526 this standard. Please address the information to the IETF Executive 1527 Director. 1529 Appendix A: Collection of Performance Data Using WIS MDIO Registers 1531 The purpose of this appendix is to illustrate how the WIS MDIO 1532 registers specified in [802.3ae] subclause 45.2.2 (and more 1533 specifically the subset required by [802.3ae] subclause 50.3.11) can 1534 be used to collect performance data either according to the 1535 conventions adopted by this document or according to the conventions 1536 specified in [802.3ae] Clause 30. 1538 For an agent implementing the SNMP managed objects required by this 1539 document the first step in collecting WIS performance data would be 1540 to poll the 10G WIS status 3 register and the various error count 1541 registers (10G WIS section BIP error count, 10G WIS line BIP errors, 1542 10G WIS far end line BIP errors, 10G WIS path block error count, and 1543 10G WIS far end path block error count) once per second. The 10G WIS 1544 status 3 register bits are all latched until read and so would 1545 indicate whether a given defect occurred any time during the previous 1546 second. The error count registers roll over modulo 2^16 or 2^32, and 1547 so to find the number of errors within the previous second the agent 1548 would need to subtract (modulo 2^16 or 2^32) the current reading from 1549 the reading taken one second ago. Armed with that information, the 1550 agent could determine for any layer whether the one second interval 1551 was an errored second, a severely errored second (that requires 1552 comparison with a threshold unless a defect is present), or a 1553 severely errored frame second. Determining whether a given second is 1554 or is not part of unavailable time requires additional logic; the 1555 most straightforward and accurate method is the delay-line approach 1556 outlined in Appendix A of [SONETng]. With that information available 1557 the agent would be able to determine by how much each current count 1558 should be incremented (including effects of inhibiting). 1559 Implementations that conform to [T1.231] would end each 15-minute 1560 interval on time-of-day clock 1/4 hour boundaries; if the delay-line 1561 approach is used then a time-of-day timestamp would accompany the 1562 one-second statistics. At the end of each interval the current 1563 registers would be pushed onto the history stack and then would be 1564 cleared. The xyxIntervalValidData flags would be set to False(2) if 1565 the number of samples was not between 890 and 910 or, in the case of 1566 far-end counts, if a near-end defect occurred during the just- 1567 completed interval (see [T1.231] Section 9.1.2.2 for details). 1569 An agent implementing the [802.3ae] Clause 30 oWIS objects could also 1570 start by polling the 10G WIS status 3 register and the various error 1571 count registers to find the defects and error counts for the previous 1572 second, and it could determine the number of errors and whether the 1573 second was an errored second, a severely errored second, or a 1574 severely errored frame second in the same manner as above. The rest 1575 of the process would simply be to increment the generalized non- 1576 resetable counters without consideration of any inhibiting rules. 1578 Full Copyright Statement 1580 Copyright (C) The Internet Society (2002). All Rights Reserved. 1582 This document and translations of it may be copied and furnished to 1583 others, and derivative works that comment on or otherwise explain it 1584 or assist in its implementation may be prepared, copied, published 1585 and distributed, in whole or in part, without restriction of any 1586 kind, provided that the above copyright notice and this paragraph are 1587 included on all such copies and derivative works. However, this 1588 document itself may not be modified in any way, such as by removing 1589 the copyright notice or references to the Internet Society or other 1590 Internet organizations, except as needed for the purpose of 1591 developing Internet standards in which case the procedures for 1592 copyrights defined in the Internet Standards process must be 1593 followed, or as required to translate it into languages other than 1594 English. 1596 The limited permissions granted above are perpetual and will not be 1597 revoked by the Internet Society or its successors or assigns. 1599 This document and the information contained herein is provided on an 1600 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1601 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1602 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1603 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1604 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1606 Revision History 1608 NOTE TO RFC Editor: this section is to be removed prior to 1609 publication as an RFC. 1611 The following changes were made to 1612 to produce : 1614 1.) Section 3.1 was updated as agreed in "WIS MIB compliance 1615 statement issue" e-mail thread, specifically to explain that the 1616 ETHER-WIS compliance statement requires all objects that required 1617 by sonetCompliance2 as well as some that it leaves optional. 1619 2.) In Section 3.5 the paragraph dealing with STS-Path Remote 1620 Defect Indication was updated to indicate that an implementation 1621 of the WIS MIB (not necessarily an arbitrary implementation of the 1622 WIS) has to set the SONET-MIB's RDI status bit when a remote 1623 server defect is detected. 1625 3.) In Section 3.6 the text introducing the table of semantic 1626 differences between IEEE GDMO and SNMP objects was wordsmithed. 1628 4.) In Section 3.7 the mapping between objects in the 1629 etherWisDeviceTable and the station management registers was 1630 updated to reflect the updated MDIO register definitions in 1631 P802.3ae/D4.01 and the corresponding updates to the MIB objects. 1633 5.) In Section 3.8.1 the text was updated to state that the 1634 purpose of the etherWisDeviceTable is to support mandatory and 1635 optional WIS test features. 1637 6.) In Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 certain instances 1638 of "SHALL" were changed to "MUST" to improve readability. 1640 7.) The LAST-UPDATED, ORGANIZATION, REVISION, and DESCRIPTION 1641 clauses of the MODULE-IDENTITY invocation were updated. 1643 8.) The lower-case "shall" in the DESCRIPTION clause of each table 1644 entry was changed to an uppercase "MUST", per RFC 2119, because it 1645 describes a requirement of the specification in the draft. 1647 9.) The etherWisDeviceTestPatternType objects was removed, and the 1648 objects etherWisDeviceTxTestPatternMode and 1649 etherWisDeviceRxTestPatternMode were changed from simple 1650 "enable/disable" flags to enumerations that reflect the specific 1651 text pattern mode in which the transmitter or receiver is 1652 operating. A new optional object called 1653 etherWisDeviceRxTestPatternErrors was added to make visible the 1654 error count MDIO register contents when the receiver is operating 1655 in the (optional) PRBS31 test pattern mode added in D4.01. 1657 10.) The SYNTAX of etherWisSectionCurrentJ0Transmitted and 1658 etherWisSectionCurrentJ0Received was changed from INTEGER (0..255) 1659 to OCTET STRING (SIZE (16)) to reflect the change from 1-byte to 1660 16-byte section trace messages in D4.01, and the DESCRIPTION 1661 clauses were rewritten along the lines for those of the 1662 corresponding path trace objects. 1664 11.) In the DESCRIPTION of etherWisPathCurrentJ0Transmitted "path 1665 message" was changes to "path trace message". 1667 12.) etherWisDeviceGroup was split into a mandatory group 1668 etherWisDeviceGroupBasic and an optional group 1669 etherWisDeviceGroupExtra. 1671 13.) The compliance name was changed from 1672 etherWisCurrentCompliance to etherWisCompliance. 1674 14.) OBJECT clauses were added to specify required values for 1675 etherWisDeviceTxTestPatternMode and 1676 etherWisDeviceRxTestPatternMode. 1678 15.) A GROUP clause was added to state that 1679 etherWisDeviceGroupExtra needs to be implemented in order to 1680 support the PRBS31 test pattern mode. The DESCRIPTION clause 1681 points out that the prbs31 enumeration is needed for 1682 etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode. 1684 16.) References [SONETng] and [P802.3ae] were updated to draft- 1685 ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01, respectively. 1687 The following changes were made to 1688 to produce : 1690 1.) The page formatting was changed to match that used in recent 1691 RFCs. 1693 2.) Heading numbering and bracketed references were removed from 1694 the abstract, and "SONET MIB" was expanded to "SONET/SDH Interface 1695 MIB". 1697 3.) RFC 2119 terminology conventions were moved from the abstract 1698 into a separate numbered "Conventions" section and were 1699 wordsmithed to match the style of recent RFCs. 1701 4.) Each occurrence of "SONET MIB" in Section 3, "Overview", was 1702 expanded to "SONET/SDH Interface MIB". 1704 5.) Each occurrence of "MAU-MIB" in Section 3, "Overview", was 1705 expanded to "802.3 MAU MIB". 1707 6.) Each occurrence of "SONET MIB" in Sections 3.1, 3.8.1, 3.8.2, 1708 3.8.3, and 3.8.4 was changed to "SONET-MIB" (this matches the 1709 usage elsewhere, specifically Sections 3.2 and 3.3). 1711 7.) All occurrences of "[P802.3ae] subclause 50.3.10" were updated 1712 to "[P802.3ae] subclause 50.3.11" in order to match the subclause 1713 numbering in P802.3ae/D4.2 (affected sections are 3.1, 3.6, 3.7, 1714 and Appendix A). 1716 8.) "Ethernet-like Interfaces MIB" was changed to "Ethernet-like 1717 Interface MIB" in Section 3.2 in order to match the usage in the 1718 abstract. 1720 9.) "mauModIfCompl2" was updated to "mauModIfCompl3" in Section 1721 3.3 in order to match . 1723 10.) An unnecessary heading was removed the table in Section 3.6 1724 that compares the semantics of IEEE threshold and counter objects 1725 with those of the corresponding objects imported from the SONET- 1726 MIB. 1728 11.) The text at the end of Section 3.6 was wordsmithed to remove 1729 unnecessary verbiage. 1731 12.) The MDIO register name spellings in Section 3.7, Section 4, 1732 and Appendix A were updated to match those in P802.3ae/D4.2 1733 subclause 45.2.2. 1735 13.) A missing comma was added to the 1736 etherWisDeviceRxTestPatternErrors REFERENCE clause. 1738 14.) DESCRIPTION clauses of etherWisSectionCurrentJ0Transmitted 1739 and etherWisPathCurrentJ1Transmitted were updates to state that 1740 the default value should be '89'h followed by 16 octets of '00'h, 1741 rather than 16 octets of '00'h followed by '89'h (this matches the 1742 resolution in P802.3ae/D4.2 of a byte ordering inconsistency). 1744 15.) The MAX-ACCESS clauses of etherWisPathCurrentStatus and 1745 etherWisPathCurrentStatus were changed from 'read-write' to 1747 16.) In Section 6, "Security Considerations", all read-write 1748 objects have been explicitly listed and mention of read-create 1749 objects has been removed. 1751 17.) References [ETHERIF], [MAU-MIB], and [P802.3ae] were updated 1752 to , , and P802.3ae/D4.2, respectively. 1755 18.) Normative and informative references were moved into separate 1756 sub-sections. 1758 19.) A "To-Do List" section was added. 1760 The following changes were made to 1761 to produce : 1763 1.) "tx" and "rx" were spelled out in the MDIO register names in 1764 Section 3.7 in order to match the usage in P802.3ae/D4.3 and 1765 P802.3ae/D5.0. 1767 2.) References [IEEE 802.3 Std] in the MIB module and [P802.3ae] 1768 in the text were updated to point to P802.3ae/D5.0. 1770 3.) Author contact information was updated. 1772 The following changes were made to 1773 to produce : 1775 1.) Gauge32 was added to the IMPORTS list. It was not being 1776 imported from SNMPv2-SMI as required by RFC 2578. 1778 2.) Enum values for etherWisDeviceTxTestPatternMode and 1779 etherWisDeviceTxTestPatternMode now start at 1 instead of 0, as 1780 recommended by RFC 2578. 1782 3.) The OBJECT clauses for etherWisDeviceTxTestPatternMode and 1783 etherWisDeviceRxTestPatternMode now state that an implementation 1784 does not have to allow value assignments that the Clause 45 MDIO 1785 registers can't support. 1787 4.) An OBJECT clause for etherWisDeviceRxTestPatternErrors was 1788 added to specify that the WRITE-SYNTAX is Gauge32(0). 1790 5.) A paragraph warning that some environments may consider the 1791 information in read-only objects to be sensitive was added to the 1792 Security Considerations section, and the entire section was 1793 updated to conform to the latest template posted to the 1794 mibs@ops.ietf.org mailing list. 1796 6.) The acronyms in Section 3 were expanded on first use. 1798 7.) All occurrences of "ifAdminState" were changed to 1799 "ifAdminStatus". 1801 8.) The DESCRIPTION clauses for etherWisPathCurrentJ1Transmitted 1802 and etherWisSectionCurrentJ0Transmitted were changed to use 1803 "transmitted" in place of "to be transmitted". 1805 9.) All remaining instances of "SHALL" were changed to "MUST" in 1806 Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 in order to improve 1807 readability. 1809 10.) The reference tag [P802.3ae] was replaced with [802.3ae], and 1810 the corresponding normative reference was updated to point to IEEE 1811 Std 802.3ae-2002, published 30 Aug 2002. The reference [IEEE 1812 802.3 Std] in the MIB module was similarly updated. 1814 11.) RFC 2119 was moved from the informative reference list to the 1815 normative reference list, in accordance with current IESG and RFC 1816 Editor policy. 1818 12.) The MIB boilerplate in Section 2 and the SMI/SNMP-related 1819 references were updated to conform to the latest template posted 1820 to the mibs@ops.ietf.org mailing list. 1822 13.) The DESCRIPTION clause of the MODULE-IDENTITY invocation was 1823 updated to include the required copyright statement. 1825 14.) The dates in the LAST-UPDATED and REVISION clauses of the 1826 MODULE-IDENTITY invocation were changed to the current date. 1828 15.) The document pagination was changed to match that expected 1829 upon publication as an RFC. 1831 To-Do List 1833 NOTE TO RFC Editor: prior to publishing this document please take 1834 care of any open items listed below and then remove this section. 1836 1.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must 1837 be updated to point to the appropriate RFCs when the respective 1838 Internet Drafts are published, and all occurrences of the 1839 reference tags must be changed to [RFCnnnn] where nnnn is the 1840 assigned RFC number. 1842 2.) Informative reference [2570bis] should be updated to point to 1843 the appropriate RFC when the corresponding Internet Draft is 1844 published, and the reference tag should be changed to match. 1846 3.) It must be determined whether members of WIS MIB design team 1847 other than editor C. M. Heard will continue to be listed in the 1848 front page as co-authors or whether they will be listed in a 1849 Contributors section with contact information, in a Contributors 1850 section without contact information, or in the Acknowledgments 1851 section.