idnits 2.17.1 draft-beili-hubmib-efm-cu-mib-00.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: ---------------------------------------------------------------------------- == 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 54 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** There are 109 instances of lines with control characters in the document. == There are 12 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 455: '...ange this object MUST be rejected with...' RFC 2119 keyword, line 511: '...ange this object MUST be rejected with...' RFC 2119 keyword, line 598: '...ange this object MUST be rejected with...' RFC 2119 keyword, line 620: '...ange this object MUST be rejected with...' RFC 2119 keyword, line 646: '...ange this object MUST be rejected with...' (7 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (October 20, 2003) is 7487 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: 'ITU-T G.991.2' is mentioned on line 593, but not defined == Missing Reference: 'IF-MIB' is mentioned on line 785, but not defined == Missing Reference: 'RFC3410' is mentioned on line 1012, but not defined == Unused Reference: 'RFC2460' is defined on line 1040, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) -- Obsolete informational reference (is this intentional?): RFC 3636 (Obsoleted by RFC 4836) Summary: 6 errors (**), 0 flaws (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Beili 3 Internet-Draft Actelis Networks 4 Expires: April 19, 2004 October 20, 2003 6 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB 7 draft-beili-hubmib-efm-cu-mib-00.txt 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at http:// 24 www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This Internet-Draft will expire on April 19, 2004. 31 Copyright Notice 33 Copyright (C) The Internet Society (2003). All Rights Reserved. 35 Abstract 37 This document defines a portion of the Management Information Base 38 (MIB) for use with network management protocols in TCP/IP based 39 Internets. This document proposes an extension to the Ethernet-like 40 Interfaces MIB and MAU MIB with a set of objects for managing an 41 Ethernet in the First Mile Copper (EFMCu) interfaces 10PassTS and 42 2BaseTL defined in IEEE 802.3ah. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. The Internet-Standard Management Framework . . . . . . . . . . 3 48 3. Relation to Interfaces MIB . . . . . . . . . . . . . . . . . . 3 49 3.1 Layering Model . . . . . . . . . . . . . . . . . . . . . . . . 3 50 3.2 PMI Aggregation Function (PAF) . . . . . . . . . . . . . . . . 4 51 3.3 Discovery Operation . . . . . . . . . . . . . . . . . . . . . 4 52 3.4 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . . . 5 53 3.5 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . . . 6 54 3.6 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . . . 6 55 3.7 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . . . 6 56 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 22 58 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 59 Normative References . . . . . . . . . . . . . . . . . . . . . 23 60 Informative References . . . . . . . . . . . . . . . . . . . . 24 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 24 62 Intellectual Property and Copyright Statements . . . . . . . . 25 64 1. Introduction 66 New Ethernet like interfaces have been defined in the IEEE 802.3ah 67 project Ethernet in the First Mile (EFM). In particular 2BaseTL and 68 10PassTS interfaces defined over voice-grade copper pairs have been 69 specified. These interfaces, collectively called EFMCu, support 70 variable rates and optional PMI aggregation (multi-pair bonding). 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet community 74 to manage EFMCu interfaces. 76 2. The Internet-Standard Management Framework 78 For a detailed overview of the documents that describe the current 79 Internet-Standard Management Framework, please refer to section 7 of 80 RFC 3410 . 82 Managed objects are accessed via a virtual information store, termed 83 the Management Information Base or MIB. MIB objects are generally 84 accessed through the Simple Network Management Protocol (SNMP). 85 Objects in the MIB are defined using the mechanisms defined in the 86 Structure of Management Information (SMI). This memo specifies a MIB 87 module that is compliant to the SMIv2, which is described in STD 58, 88 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 89 [RFC2580]. 91 3. Relation to Interfaces MIB 93 This section specifies how the ifStackTable, as defined in [RFC2863] 94 and ifInvStackTable, as defined in [RFC2864] are used for the EFMCu 95 application. 97 3.1 Layering Model 99 An EFMCu interface can aggregate up to 32 PMDs (modems) using so 100 called PMI Aggregation Function (PAF). 102 An generic EFMCu device can have a number of MII/PCS ports 103 cross-connected to a number of PMDs, with a single PCS per PMD 104 relationship. 106 Each PMD comprising an aggregated EFMCu port is represented in the 107 Interface table as a separate port with ifType of shdsl (169) for 108 2BaseTL or vdsl(97) for 10PassTS. The ifType values are defined in 109 IANAifType-MIB. ifSpeed for each PMD shall return an actual bitrate 110 of the active PMD or a configured bitrate for pre-activated modems 111 (note that unassigned PMD has its default bitrate). 113 The ifStackTable is indexed by the ifIndex values of the aggregated 114 EFMCu port (PCS) and the PMDs connected to it. ifStackTable allows a 115 Network Management application to determine which PMDs are connected 116 to a particular PCS and change connections. The ifInvStackTable, 117 being an inverted version of the ifStackTable, provides an efficient 118 means for a Network Management application to read a subset of the 119 ifStackTable and thereby determine which PCS runs on top of a 120 particular PMD. 122 A new table efmCuAvailableStackTable defined in this MIB, specifies 123 for each PCS a list of PMDs, which can possibly be cross-connected to 124 that PCS, determined by the cross-connect capability of the device. 125 This table, modeled after ifStackTable, is read only. 127 Editor's Note: An alternative would be to use ifStackTable to 128 describe cross-connect capability and efmCuAvailableStackTable to 129 describe actual connections, so that the cross-connect action would 130 be done in the EFM-CU-MIB by modifying the efmCuAvailableStackTable 131 (and not in IF-MIB). 133 3.2 PMI Aggregation Function (PAF) 135 aPAFSupported is mandatory for all EFMCu ports (2BASE-TL and 136 10PASS-TS). 138 3.3 Discovery Operation 140 This MIB allows a Network Management application to control EFM 141 Discovery mechanism and query its results. Note that the Discovery 142 mechanism can work only if PAF is supported and enabled. 144 Two tables are used by Discovery mechanism: ifStackTable and 145 efmCuAvailableStackTable defined. The following pseudo-code defines 146 an example of Discovery for a generic PAF enabled multi-PCS EFMCu 147 device, located at Central Office (CO): 149 foreach PCS[i] in Device 150 { if ( PCS[i].PAFSupported ) // Discover only on ports supporting PAF 151 { dc = PCS[i].DiscoveryCode = MAC[i]; // unique 6 byte code per PCS 152 // go over all currently disconnected PMDs, which can 153 // pottentially be connected to PCS[i] 154 foreach PMD[j] in efmCuAvailableStackTable[PCS[i]] and 155 not in ifStackTable[PCS[i]] 156 { PMD[j].RemoteDiscoveryCode = dc; // Set if Clear 157 r = PMD[j].RemoteDiscoveryCode; // Get 158 if ( r == dc ) 159 { // Remote CPE connected via PMD[j] is/was a peer for 160 // PCS[i]. Connect this PMD to the PCS 161 Add PMD[j] to ifStackTable[PCS[i]]; 162 // Discover all other currently disconnected PMDs, 163 // attached to the same CPE and connect them to the PCS 164 foreach PMD[k] in efmCuAvailableStackTable[PCS[i]] and 165 not in ifStackTable[PCS[i]] 166 { r = PMD[k].RemoteDiscoveryCode; // Get 167 if ( r == dc ) 168 Add PMD[k] to ifStackTable[PCS[i]]; 169 } 170 } 171 // Discovered all PMDs which lead to the same CPE and 172 // connected them to PCS[i]. Go to the next PCS. 173 break; 174 } 175 } 176 } 178 The SNMP Agent builds efmCuStackTable according to the information 179 contained in the Clause 45 PMI_Available_register (see [802.3ah] 180 61.1.5.3 and 45.2.3.20). 182 Adding a PMD to the ifStackTable row for a specific PCS involve 183 actual connection of the PCS and PMD, which can be done by modifying 184 Clause 45 PMI_Aggregate_register (see [802.3ah] 61.1.5.3 and 185 45.2.3.21). 187 3.4 Relation to SHDSL MIB 189 PMD(s) comprising a 2BaseTL port are described in 190 HDSL2-SHDSL-LINE-MIB . Note that HDSL2-SHDSL-LINE-MIB describes 191 standard G.SHDSL modems according to ITU-T G.991.2, while IEEE 192 802.3ah uses so called G.SHDSL.bis spec, extended to support higher 193 constellations and rates. In cases where G.SHDSL and 802.3ah differ, 194 the definitions in 802.3ah take precedence. 196 3.5 Relation to VDSL MIB 198 PMD(s) comprising a 10PassTS port are described in VDSL-LINE-MIB 199 [draft-ietf-adslmib-vdsl]. In cases where VDSL-LINE-MIB and 802.3ah 200 differ, the definitions in 802.3ah take precedence 202 3.6 Relation to Ethernet-Like and MAU MIBs 204 EFMCu interfaces require implementation of ETHERIF-MIB 205 [draft-ietf-hubmib-etherif-mib] and MAU-MIB [RFC3636]. As such EFMCu 206 interfaces 2BaseTL/10PassTS shall return an ifType of 207 ethernetCsmacd(6). Information on the particular flavor of EFMCu that 208 an interface is running is available from ifSpeed in the Interfaces 209 Group MIB [RFC2863], and ifMauType in the MAU MIB [RFC3636]. 211 3.7 Mapping of IEEE 802.3ah Managed Objects 213 This section contains the mapping between oMAU managed objects 214 defined in [802.3ah] and managed objects defined in this document and 215 in associated MIB modules, i.e., the IF-MIB [RFC2863], the 216 HDSL2-SHDSL-LINE-MIB , and the MAU-MIB [RFC3636]. 218 IEEE 802.3 Managed Object Corresponding SNMP Object 220 4. Definitions 222 EFM-CU-MIB DEFINITIONS ::= BEGIN 224 IMPORTS 225 MODULE-IDENTITY, OBJECT-TYPE, 226 Gauge32, Integer32, transmission 227 FROM SNMPv2-SMI 228 TruthValue, RowStatus, PhysAddress 229 FROM SNMPv2-TC 230 ifIndex, InterfaceIndexOrZero 231 FROM IF-MIB 232 MODULE-COMPLIANCE, OBJECT-GROUP 233 FROM SNMPv2-CONF 234 ; 236 efmCuMIB MODULE-IDENTITY 237 LAST-UPDATED "200310200000Z" -- October 20, 2003 238 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 239 Working Group" 240 CONTACT-INFO 241 "WG charter: 242 http://www.ietf.org/html.charters/hubmib-charter.html 244 Mailing Lists: 245 General Discussion: hubmib@ietf.org 246 To Subscribe: hubmib-request@ietf.org 247 In Body: subscribe your_email_address 249 Chair: Dan Romascanu 250 Postal: Avaya Inc. 251 Atidim Technology Park, Bldg. 3 252 Tel Aviv 61131 253 Israel 254 Tel: +972 3 645 8414 255 E-mail: dromasca@avaya.com 257 Editor: Edward Beili 258 Postal: Actelis Networks Inc. 259 25 Bazel St., P.O.B. 10173 260 Petach-Tikva 10173 261 Israel 262 Tel: +972-3-924-3491 263 E-mail: edward.beili@actelis.com" 265 DESCRIPTION 266 "The objects in this MIB module are used to manage 267 the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 268 2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D2.1. 270 The following reference is used throughout this MIB module: 272 [802.3ah] refers to: 273 IEEE Draft P802.3ah/D2.1: 'Draft amendment to - 274 Information technology - Telecommunications and 275 information exchange between systems - Local and 276 metropolitan area networks - Specific requirements - 277 Part 3: Carrier sense multiple access with collision 278 detection (CSMA/CD) access method and physical layer 279 specifications - Media Access Control Parameters, Physical 280 Layers and Management Parameters for subscriber access 281 networks', 07 October 2003. 283 Of particular interest are Clause 61, 'Physical Coding 284 Sublayer (PCS) and common specifications, type 10PASS-TS and 285 type 2BASE-TL', Clause 30, 'Management', and Clause 45, 286 'Management Data Input/Output (MDIO) Interface'. 288 Copyright (C) The Internet Society (2003). This version 289 of this MIB module is part of XXXX see the RFC 290 itself for full legal notices." 292 -- Editor's Note: Replace XXXX with the actual RFC number 293 -- assigned by RFC Editor and remove this note 295 REVISION "200310200000Z" -- October 20, 2003 296 DESCRIPTION "Initial version, published as RFC XXXX." 298 ::= { transmission 135 } 300 -- Editor's Note: Replace 135 with a real OID once it is 301 -- assigned by IANA and remove this note. 302 -- This OID is temporary so that compilation does not to fail. 304 -- Sections of the module 306 efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } 308 efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } 310 -- Groups in the module 312 efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } 314 efmCuPmd OBJECT IDENTIFIER ::= { efmCuObjects 2 } 316 -- The PCS Port group 318 efmCuPortTable OBJECT-TYPE 319 SYNTAX SEQUENCE OF EfmCuPortEntry 320 MAX-ACCESS not-accessible 321 STATUS current 322 DESCRIPTION 323 "Table for EFMCu 2BaseTL/10PassTS (PCS) Ports." 324 ::= { efmCuPort 1 } 326 efmCuPortEntry OBJECT-TYPE 327 SYNTAX EfmCuPortEntry 328 MAX-ACCESS not-accessible 329 STATUS current 330 DESCRIPTION 331 "An entry in the EFMCu Port table." 332 INDEX { ifIndex } 333 ::= { efmCuPortTable 1 } 335 EfmCuPortEntry ::= 336 SEQUENCE { 337 efmCuPortSidesSupported INTEGER, 338 efmCuPortSide INTEGER, 339 efmCuPAFSupported TruthValue, 340 efmCuPAFAdminState INTEGER, 341 efmCuPAFDiscoveryCode PhysAddress 342 } 344 efmCuPortSidesSupported OBJECT-TYPE 345 SYNTAX INTEGER { 346 subscriber(1), 347 office(2), 348 both(3) 349 } 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "EFM port supported mode of operation (subtype). 354 The value of 'subscriber' indicates that the port supports 355 'CPE' or '-R' subtype. 356 The value of 'office' indicates that the port supports 357 'CO' or '-O' subtype. 358 The value of 'both' indicates that the port supports both 359 'CO' and 'CPE' subtypes. 360 An actual mode of operation is determined by ifPhySide. 362 If a Clause 45 MDIO Interface to the PCS is present, then this 363 attribute will map to the CO supported and CPE supported 364 bits in the 10P/2B capability register" 365 REFERENCE 366 "[802.3ah] 61.1, 45.2.3.18.2, 45.2.3.18.3" 367 ::= { efmCuPortEntry 1 } 369 efmCuPortSide OBJECT-TYPE 370 SYNTAX INTEGER { 371 subscriber(1), 372 office(2) 373 } 374 MAX-ACCESS read-write 375 STATUS current 376 DESCRIPTION 377 "EFM port mode of operation (subtype). 378 The value of 'subscriber' indicates the port is designated as 379 the 'CPE' or '-R' subtype. 380 The value of the 'office' indicates that the port is 381 designated as the 'CO' or '-O' subtype. 382 Attempts to change this object to an unsupported subtype shall 383 be ignored. 385 If a Clause 45 MDIO Interface to the PCS is present, then this 386 attribute will map to the Port sub-type select bit in the 387 10P/2B capability register" 388 REFERENCE 389 "[802.3ah] 61.1, 45.2.3.18.1" 390 ::= { efmCuPortEntry 2 } 392 efmCuPAFSupported OBJECT-TYPE 393 SYNTAX TruthValue 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "PMI Aggregation Function (PAF) Capability of the EFMCu port 398 (PCS). 399 This object has a value of true(1) when the PCS can perform 400 PMI aggregation on the available PMDs. 401 Ports incapable of PAF shall return a value of false(2). 403 If a Clause 45 MDIO Interface to the PCS is present, 404 then this attribute will map to the PAF supported bit in the 405 10P/2B capability register." 406 REFERENCE 407 "[802.3ah] 61.2.2, 45.2.3.18.4" 408 ::= { efmCuPortEntry 3 } 410 efmCuPAFAdminState OBJECT-TYPE 411 SYNTAX INTEGER { 412 enabled(1), 413 disabled(2) 414 } 415 MAX-ACCESS read-write 416 STATUS current 417 DESCRIPTION 418 "Administrative (desired) state of the PAF of the EFMCu port 419 (PCS). 420 When 'disabled', PMI Aggregation will not be performed by the 421 PCS. 422 When 'enabled', PAF will be performed by the PCS when the link 423 is Up, even on a single PMD, if PAF is supported. 424 PCS ports incapable of supporting PAF shall return a value of 425 'disabled'. Attempts to 'enable' such port shall be ignored. 427 Changing PAFAdminState is a traffic disruptive operation and 428 as such shall be done when the link is Down. Attempts to 429 change this object shall be ignored if the link is Up or 430 Initializing. 432 If a Clause 45 MDIO Interface to the PCS is present, then this 433 attribute will map to the PAF enable bit in the 10P/2B 434 capability register" 435 REFERENCE 436 "[802.3ah] 61.2.2, 45.2.3.18.4" 437 ::= { efmCuPortEntry 4 } 439 efmCuPAFDiscoveryCode OBJECT-TYPE 440 SYNTAX PhysAddress 441 MAX-ACCESS read-write 442 STATUS current 443 DESCRIPTION 444 "PAF Discovery Code of the EFMCu port (PCS). 445 A unique 6 Byte long code used by the Discovery function. 446 This object must be instantiated for the CO subtype PCS before 447 writing operations on the PAFRemoteDiscoveryCode 448 (Set_if_Clear and Clear_if_Same) are performed by PMDs 449 associated with the PCS. 450 The value of this object is read-only for CPE port subtypes. 451 (The initial value of this object for CPE ports after reset 452 is 0). 454 Discovery must be performed when the link is Down. 455 Attempts to change this object MUST be rejected with the error 456 inconsistentValue if the link is Up or Initializing. 458 If a Clause 45 MDIO Interface to the PCS is present, then this 459 attribute will map to the Aggregaion Discovery Code registers" 460 REFERENCE 461 "[802.3ah] 61.2.2.8.3, 45.2.1.12, 45.2.1.13" 462 ::= { efmCuPortEntry 5 } 464 -- The PMD group 466 efmCuPmdTable OBJECT-TYPE 467 SYNTAX SEQUENCE OF EfmCuPmdEntry 468 MAX-ACCESS not-accessible 469 STATUS current 470 DESCRIPTION 471 "Table for EFMCu 2BaseTL/10PassTS PMDs (modems). Common part" 472 ::= { efmCuPmd 1 } 474 efmCuPmdEntry OBJECT-TYPE 475 SYNTAX EfmCuPmdEntry 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "An entry in the EFMCu PMD Common table." 480 INDEX { ifIndex } 481 ::= { efmCuPmdTable 1 } 483 EfmCuPmdEntry ::= 484 SEQUENCE { 485 efmCuPAFRemoteDiscoveryCode PhysAddress, 486 efmCuPmdRxSnrMgn Integer32, 487 efmCuPmdRemoteRxSnrMgn Integer32 488 } 490 efmCuPAFRemoteDiscoveryCode OBJECT-TYPE 491 SYNTAX PhysAddress 492 MAX-ACCESS read-write 493 STATUS current 494 DESCRIPTION 495 "PAF Remote Discovery Code of the PMD port at CO. 496 A 6 Byte long Discovery Code of the peer PCS connected via 497 the PMD. 498 Reading this object results in a Discovery Get operation. 499 Writing a zero to this object results in a Discovery 500 Clear_if_Same operation (the value of the ifPAFDiscoveryCode 501 at the peer PCS shall be the same as ifPAFDiscoveryCode of 502 the local PCS associated with the PMD for the operation to 503 succeed). 504 Writing a non-zero value to this object reslults in a 505 Discovery Set_if_Clear operation. 506 This object does not exist in CPE port subtypes. A zero length 507 octet string shall be returned for CPE port subtypes and also 508 when PAF aggregation is not enabled. 510 Discovery must be performed when the link is Down. 511 Attempts to change this object MUST be rejected with the error 512 inconsistentValue, if the link is Up or Initializing. 514 If a Clause 45 MDIO Interface to the PCS is present, then this 515 attribute is a function of Aggregation Discovery Operation, 516 Code and Operation result registers" 517 REFERENCE 518 "[802.3ah] 61.2.2.8.3, 45.2.1.12.1" 519 ::= { efmCuPmdEntry 1 } 521 efmCuPmdRxSnrMgn OBJECT-TYPE 522 SYNTAX Integer32(-127..128) 523 UNITS "dB" 524 MAX-ACCESS read-only 525 STATUS current 526 DESCRIPTION 527 "The current Signal-to-Noise Ratio (SNR) margin with respect 528 to the received signal, for the PMD. 530 If a Clause 45 MDIO Interface is present, then this 531 attribute will map to the Rx SNR Margin register" 532 REFERENCE 533 "[802.3ah] 45.2.1.17" 534 ::= { efmCuPmdEntry 2 } 536 efmCuPmdRemoteRxSnrMgn OBJECT-TYPE 537 SYNTAX Integer32(-127..128) 538 UNITS "dB" 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "The current SNR margin with respect 543 to the received signal, for the CO PMD's link partner 544 (CPE PMD). 546 This object is not supported by CPE port subtypes. 548 If a Clause 45 MDIO Interface is present, then this 549 attribute will map to the Remote Rx SNR Margin register" 550 REFERENCE 551 "[802.3ah] 45.2.1.17" 552 ::= { efmCuPmdEntry 3 } 554 -- 2BaseTL specific PMD group 556 efmCuPmd2BTable OBJECT-TYPE 557 SYNTAX SEQUENCE OF EfmCuPmd2BEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "Table for EFMCu 2BaseTL PMDs (modems)." 562 ::= { efmCuPmd 2 } 564 efmCuPmd2BEntry OBJECT-TYPE 565 SYNTAX EfmCuPmd2BEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "An entry in the EFMCu 2BaseTL PMD table." 570 AUGMENTS { efmCuPmdEntry } 571 ::= { efmCuPmd2BTable 1 } 573 EfmCuPmd2BEntry ::= 574 SEQUENCE { 575 efmCuPmd2BRegion INTEGER, 576 efmCuPmd2BPower Integer32, 577 efmCuPmd2BDataRate Integer32, 578 efmCuPmd2BConstellation INTEGER, 579 efmCuPmd2BLoopAtnThreshold Integer32, 580 efmCuPmd2BSnrMgnThreshold Integer32 581 } 583 efmCuPmd2BRegion OBJECT-TYPE 584 SYNTAX INTEGER { 585 annexA(1), -- region 1 586 annexB(2), -- region 2 587 annexC(3) -- region 3 588 } 589 MAX-ACCESS read-write 590 STATUS current 591 DESCRIPTION 592 "Desired Power Spectral Density (PSD) Regional setting as specified 593 in Regional Annex of [ITU-T G.991.2] to operate under. 594 This object is writable for the CO subtype PMDs (2BaseTL-O). 595 It is read-only for the CPE subtype (2BaseTL-R). 597 Changing Regional Annex must be performed when the link is 598 Down. Attempts to change this object MUST be rejected with 599 the error inconsistentValue, if the link is Up or 600 Initializing. 602 If a Clause 45 MDIO Interface to the PMD is present, then this 603 attribute will map to the Region bits in the 2B general 604 parameter register" 605 REFERENCE 606 "[802.3ah] 45.2.1.34" 607 ::= { efmCuPmd2BEntry 1 } 609 efmCuPmd2BPower OBJECT-TYPE 610 SYNTAX Integer32(0..15) 611 UNITS "dBm" 612 MAX-ACCESS read-write 613 STATUS current 614 DESCRIPTION 615 "Desired Signal Transmit Power. Multiple of 0.5dBm. 616 This object is writable for the CO subtype PMDs (2BaseTL-O). 617 It is read-only for the CPE subtype (2BaseTL-R). 619 Changing of the Signal Transmit Power must be performed when the 620 link is Down. Attempts to change this object MUST be rejected with 621 the error inconsistentValue, if the link is Up or 622 Initializing. 624 If a Clause 45 MDIO Interface to the PMD is present, then this 625 attribute will map to the Power bits in the 2B PMD 626 parameters register" 627 REFERENCE 628 "[802.3ah] 45.2.1.35" 629 ::= { efmCuPmd2BEntry 2 } 631 efmCuPmd2BDataRate OBJECT-TYPE 632 SYNTAX Integer32(0..5696) 633 UNITS "Kbps" 634 MAX-ACCESS read-write 635 STATUS current 636 DESCRIPTION 637 "Desired 2BaseTL PMD Data Rate. 638 The rate is fixed when the value is n x 64Kbps, where n=3..60 for 639 16-TCPAM and n=12..89 for 32-TCPAM. The value of 0 means 640 that data rate is not fixed but is adaptive and should be set to 641 the maximum attainable rate during line probing. 642 This object is writable for the CO subtype PMDs (2BaseTL-O). 643 It is read-only for the CPE subtype (2BaseTL-R). 645 Changing of the Data Rate must be performed when the 646 link is Down. Attempts to change this object MUST be rejected with 647 the error inconsistentValue, if the link is Up or 648 Initializing. 650 If a Clause 45 MDIO Interface to the PMD is present, then this 651 attribute will map to the Data Rate bits in the 2B PMD 652 parameters register" 653 REFERENCE 654 "[802.3ah] 45.2.1.35" 655 ::= { efmCuPmd2BEntry 3 } 657 efmCuPmd2BConstellation OBJECT-TYPE 658 SYNTAX INTEGER { 659 tcpam16(1), -- 16-TCPAM 660 tcpam32(2) -- 32-TCPAM 661 } 662 MAX-ACCESS read-write 663 STATUS current 664 DESCRIPTION 665 "Desired TCPAM Constellation of the 2BaseTL PMD. 666 This object is writable for the CO subtype PMDs (2BaseTL-O). 667 It is read-only for the CPE subtype (2BaseTL-R). 669 Changing Constellation must be performed when the link is 670 Down. Attempts to change this object MUST be rejected with 671 the error inconsistentValue, if the link is Up or 672 Initializing. 674 If a Clause 45 MDIO Interface to the PMD is present, then this 675 attribute will map to the Constellation bits in the 2B general 676 parameter register" 677 REFERENCE 678 "[802.3ah] 45.2.1.34" 679 ::= { efmCuPmd2BEntry 4 } 681 efmCuPmd2BLoopAtnThreshold OBJECT-TYPE 682 SYNTAX Integer32(-127..128) 683 UNITS "dB" 684 MAX-ACCESS read-write 685 STATUS current 686 DESCRIPTION 687 "Desired Loop Attenuation Threshold for the 2BaseTL PMD. 688 This object configures the loop attenuation alarm threshold. 689 When the current value of Loop Attenuation reaches 690 or exceeds this threshold, a efmCuPmd2BLoopAttnDefect 691 notification MAY be generated. 693 This object is writable for the CO subtype PMDs (2BaseTL-O). 694 It is read-only for the CPE subtype (2BaseTL-R). 696 Changing of the Loop Attenuation Threshold must be performed when the 697 link is Down. Attempts to change this object MUST be rejected with 698 the error inconsistentValue, if the link is Up or 699 Initializing. 701 If a Clause 45 MDIO Interface to the PMD is present, then this 702 attribute will map to the Loop attenuation threshold bits in the 703 2B PMD line quality thresholds register" 704 REFERENCE 705 "[802.3ah] 45.2.1.36" 706 ::= { efmCuPmd2BEntry 5 } 708 efmCuPmd2BSnrMgnThreshold OBJECT-TYPE 709 SYNTAX Integer32(-127..128) 710 UNITS "dB" 711 MAX-ACCESS read-write 712 STATUS current 713 DESCRIPTION 714 "Desired SNR Margin Threshold for the 2BaseTL PMD. 715 This object configures the SNR margin alarm threshold. 716 When the current value of SNR Margin reaches 717 or exceeds this threshold, a efmCuPmd2BSnrMgnDefect 718 notification MAY be generated. 720 This object is writable for the CO subtype PMDs (2BaseTL-O). 721 It is read-only for the CPE subtype (2BaseTL-R). 723 Changing of the SNR Margin Threshold must be performed when the 724 link is Down. Attempts to change this object MUST be rejected with 725 the error inconsistentValue, if the link is Up or 726 Initializing. 728 If a Clause 45 MDIO Interface to the PMD is present, then this 729 attribute will map to the SNR margin threshold bits in the 730 2B PMD line quality thresholds register" 731 REFERENCE 732 "[802.3ah] 45.2.1.36" 733 ::= { efmCuPmd2BEntry 6 } 735 -- 10PassTS specific PMD group 737 efmCuPmd10PTable OBJECT-TYPE 738 SYNTAX SEQUENCE OF EfmCuPmd10PEntry 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "Table for EFMCu 10PassTS PMDs (modems)." 743 ::= { efmCuPmd 3 } 745 efmCuPmd10PEntry OBJECT-TYPE 746 SYNTAX EfmCuPmd10PEntry 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "An entry in the EFMCu 10PassTS PMD table." 751 AUGMENTS { efmCuPmdEntry } 752 ::= { efmCuPmd10PTable 1 } 754 EfmCuPmd10PEntry ::= 755 SEQUENCE { 756 efmCuPmd10PElectricalLength Integer32 757 -- To be continued 758 } 760 efmCuPmd10PElectricalLength OBJECT-TYPE 761 SYNTAX Integer32(0..1024) 762 UNITS "m" 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "Electrical Length in meters as perceived by the 10PassTS PMD 767 after the link is established. 768 The value of 0 is returned if the link is Down or Initializing 770 or the PMD is unable to estimate the Electrical Length. 772 If a Clause 45 MDIO Interface to the PMD is present, then this 773 attribute will map to the 10P Electrical Length register" 774 REFERENCE 775 "[802.3ah] 45.2.1.21" 776 ::= { efmCuPmd10PEntry 1 } 778 -- efmCuAvailableStackTable for use in Discovery 780 efmCuAvailableStackTable OBJECT-TYPE 781 SYNTAX SEQUENCE OF EfmCuAvailableStackEntry 782 MAX-ACCESS not-accessible 783 STATUS current 784 DESCRIPTION 785 "This table, modeled after ifStackTable from [IF-MIB], 786 contains information on the possible 'on-top-of' 787 relationships between the multiple sub-layers of network 788 interfaces (as opposed to actual relationships in 789 ifStackTable). In particular, it contains information on 790 which PCS ports (sub-layers) can possible run 'on top of' 791 which PMDs (sublayers), as determined by cross-connect 792 capability of the EFMCu device, where each sub-layer 793 corresponds to a conceptual row in the ifTable. For example, 794 when the PCS port with ifIndex value x can be connected 795 to run on top of the PMD with ifIndex value y, then this table 796 contains: 798 efmCuAvailableStackStatus.x.y=active 800 For each ifIndex value, I, which identifies a PCS or PMD 801 interface, there are always at least two instantiated rows 802 in this table associated with I. For one of these rows, I 803 is the value of efmCuAvailableStackHigherLayer; for the other, 804 I is the value of efmCuAvailableStackLowerLayer. 805 Note that there's always at least on PCS for each PMD and at 806 least one PMD for each PCS in the EFMCu devices. 807 This table is ready only as it describes device capability" 808 REFERENCE 809 "ifStackTable of RFC 2863" 810 ::= { efmCuObjects 3 } 812 efmCuAvailableStackEntry OBJECT-TYPE 813 SYNTAX EfmCuAvailableStackEntry 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "Information on a particular relationship between two sub- 818 layers, specifying that one sub-layer runs on 'top' of the 819 other sub-layer. Each sub-layer corresponds to a conceptual 820 row in the ifTable." 821 INDEX { 822 efmCuAvailableStackHigherLayer, 823 efmCuAvailableStackLowerLayer 824 } 825 ::= { efmCuAvailableStackTable 1 } 827 EfmCuAvailableStackEntry ::= 828 SEQUENCE { 829 efmCuAvailableStackHigherLayer InterfaceIndexOrZero, 830 efmCuAvailableStackLowerLayer InterfaceIndexOrZero, 831 efmCuAvailableStackStatus RowStatus 832 } 834 efmCuAvailableStackHigherLayer OBJECT-TYPE 835 SYNTAX InterfaceIndexOrZero 836 MAX-ACCESS not-accessible 837 STATUS current 838 DESCRIPTION 839 "The value of ifIndex corresponding to the higher sub-layer 840 of the relationship, i.e., the sub-layer which runs on 'top' 841 of the sub-layer identified by the corresponding instance of 842 ifStackLowerLayer. If there is no higher sub-layer (below 843 the internetwork layer), then this object has the value 0." 844 ::= { efmCuAvailableStackEntry 1 } 846 efmCuAvailableStackLowerLayer OBJECT-TYPE 847 SYNTAX InterfaceIndexOrZero 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "The value of ifIndex corresponding to the lower sub-layer 852 of the relationship, i.e., the sub-layer which runs 'below' 853 the sub-layer identified by the corresponding instance of 854 ifStackHigherLayer. If there is no lower sub-layer, then 855 this object has the value 0." 856 ::= { efmCuAvailableStackEntry 2 } 858 efmCuAvailableStackStatus OBJECT-TYPE 859 SYNTAX RowStatus 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The status of the relationship between two sub-layers. 865 This object is read only, unlike ifStackStatus, as it 866 describes the device capability." 867 ::= { efmCuAvailableStackEntry 3 } 869 -- 870 -- Conformance Statements 871 -- 873 efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } 875 efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } 877 -- Object Groups 879 efmCuPortGroupBasic OBJECT-GROUP 880 OBJECTS { 881 efmCuPortSidesSupported, 882 efmCuPortSide, 883 efmCuPAFSupported 884 } 885 STATUS current 886 DESCRIPTION 887 "A collection of objects required for all EFMCu ports." 888 ::= { efmCuGroups 1 } 890 efmCuGroupPAF OBJECT-GROUP 891 OBJECTS { 892 efmCuPAFAdminState, 893 efmCuPAFDiscoveryCode, 894 efmCuPAFRemoteDiscoveryCode, 895 efmCuAvailableStackTable 896 } 897 STATUS current 898 DESCRIPTION 899 "A collection of objects that support 900 optional Aggregation features on EFMCu ports." 901 ::= { efmCuGroups 2 } 903 efmCuPmdGroupCommon OBJECT-GROUP 904 OBJECTS { 905 efmCuPmdRxSnrMgn, 906 efmCuPmdRemoteRxSnrMgn 907 } 908 STATUS current 909 DESCRIPTION 910 "A collection of objects that provide 911 required information about a 2BaseTL/10PassTS PMD." 913 ::= { efmCuGroups 3 } 915 efmCu2BGroup OBJECT-GROUP 916 OBJECTS { 917 efmCuPmd2BRegion, 918 efmCuPmd2BPower, 919 efmCuPmd2BDataRate, 920 efmCuPmd2BConstellation, 921 efmCuPmd2BLoopAtnThreshold, 922 efmCuPmd2BSnrMgnThreshold 923 } 924 STATUS current 925 DESCRIPTION 926 "A collection of objects that provide 927 required information about a 2BaseTL PMD." 928 ::= { efmCuGroups 4 } 930 efmCu10PGroup OBJECT-GROUP 931 OBJECTS { 932 efmCuPmd10PElectricalLength 933 } 934 STATUS current 935 DESCRIPTION 936 "A collection of objects that provide required 937 information about a 10PassTS PMD." 938 ::= { efmCuGroups 5 } 940 -- Compliance Statements 942 efmCuCompliance MODULE-COMPLIANCE 943 STATUS current 944 DESCRIPTION 945 "The compliance statement for 2BaseTL/10PassTS interfaces. 946 Compliance with the following external compliance statements 947 is prerequisite: 949 MIB Module Compliance Statement 950 ---------- -------------------- 951 IF-MIB ifCompliance3 952 IF-INVERTED-STACK-MIB ifInvCompliance 953 EtherLike-MIB dot3Compliance2 954 MAU-MIB mauModIfCompl3" 956 MODULE -- this module 957 MANDATORY-GROUPS { 958 efmCuPortGroupBasic, 959 efmCuPmdGroupCommon, 960 efmCuPmd2BGroup, 961 efmCuPmd10PGroup 962 } 964 OBJECT efmCuPortSidesSupported 965 SYNTAX INTEGER { 966 subscriber(1), 967 office(2), 968 } 969 DESCRIPTION 970 "Support for values other than subscriber(1), 971 and office(2) is not required." 973 OBJECT efmCuPortSide 974 MIN-ACCESS read-only 975 DESCRIPTION 976 "Write access is not required (needed only for ports 977 supporting both subscriber and office sides)" 979 -- Editor's Note: To be Continued 981 ::= { efmCuCompliances 1 } 983 END 985 5. Security Considerations 987 There are number of managed objects defined in this MIB module that 988 have a MAX-ACCESS clause of read-write. Most objects are writeable 989 only when the link is Down. Writing to these objects can have the 990 following potentially disruptive effects on network operation: 991 o TBD 993 The user of this MIB module must therefore be aware that support for 994 SET operations in a non-secure environment without proper protection 995 can have a negative effect on network operations. 997 The readable objects in this MIB module (i.e., those with MAX-ACCESS 998 other than not-accessible) may be considered sensitive in some 999 environments since, collectively, they provide information about the 1000 performance of network interfaces and can reveal some aspects of 1001 their configuration. In such environments it is important to control 1002 even GET and NOTIFY access to these objects and possibly even to 1003 encrypt their values when sending them over the network via SNMP. 1005 SNMP versions prior to SNMPv3 did not include adequate security. Even 1006 if the network itself is secure (for example by using IPSec), even 1007 then, there is no control as to who on the secure network is allowed 1008 to access and GET/SET (read/change/create/delete) the objects in this 1009 MIB module. 1011 It is RECOMMENDED that implementers consider the security features as 1012 provided by the SNMPv3 framework (see [RFC3410], section 8), 1013 including full support for the SNMPv3 cryptographic mechanisms (for 1014 authentication and privacy). 1016 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1017 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1018 enable cryptographic security. It is then a customer/operator 1019 responsibility to ensure that the SNMP entity giving access to an 1020 instance of this MIB module is properly configured to give access to 1021 the objects only to those principals (users) that have legitimate 1022 rights to indeed GET or SET (change/create/delete) them. 1024 6. Acknowledgments 1026 Not yet. 1028 Normative References 1030 [802.3ah] IEEE, "IEEE Draft P802.3ah/D2.1: 'Draft amendment to - 1031 Information technology - Telecommunications and 1032 information exchange between systems - Local and 1033 metropolitan area networks - Specific requirements - Part 1034 3: Carrier sense multiple access with collision detection 1035 (CSMA/CD) access method and physical layer specifications 1036 - Media Access Control Parameters, Physical Layers and 1037 Management Parameters for subscriber access networks', 07 1038 October 2003.", October 2003. 1040 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1041 (IPv6) Specification", RFC 2460, December 1998. 1043 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1044 McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 1045 Management Information Version 2 (SMIv2)", STD 58, RFC 1046 2578, April 1999. 1048 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1049 McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 1050 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 1052 [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, 1053 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1054 April 1999. 1056 Informative References 1058 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1059 MIB", RFC 2863, June 2000. 1061 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 1062 Extension to the Interfaces Group MIB", RFC 2864, June 1063 2000. 1065 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1066 Medium Attachment Units (MAUs)", RFC 3636, September 2003. 1068 Author's Address 1070 Edward Beili 1071 Actelis Networks 1072 Bazel 25 1073 Petach-Tikva 1074 Israel 1076 Phone: +972-3-924-3491 1077 EMail: edward.beili@actelis.com 1079 Intellectual Property Statement 1081 The IETF takes no position regarding the validity or scope of any 1082 intellectual property or other rights that might be claimed to 1083 pertain to the implementation or use of the technology described in 1084 this document or the extent to which any license under such rights 1085 might or might not be available; neither does it represent that it 1086 has made any effort to identify any such rights. Information on the 1087 IETF's procedures with respect to rights in standards-track and 1088 standards-related documentation can be found in BCP-11. Copies of 1089 claims of rights made available for publication and any assurances of 1090 licenses to be made available, or the result of an attempt made to 1091 obtain a general license or permission for the use of such 1092 proprietary rights by implementors or users of this specification can 1093 be obtained from the IETF Secretariat. 1095 The IETF invites any interested party to bring to its attention any 1096 copyrights, patents or patent applications, or other proprietary 1097 rights which may cover technology that may be required to practice 1098 this standard. Please address the information to the IETF Executive 1099 Director. 1101 Full Copyright Statement 1103 Copyright (C) The Internet Society (2003). All Rights Reserved. 1105 This document and translations of it may be copied and furnished to 1106 others, and derivative works that comment on or otherwise explain it 1107 or assist in its implementation may be prepared, copied, published 1108 and distributed, in whole or in part, without restriction of any 1109 kind, provided that the above copyright notice and this paragraph are 1110 included on all such copies and derivative works. However, this 1111 document itself may not be modified in any way, such as by removing 1112 the copyright notice or references to the Internet Society or other 1113 Internet organizations, except as needed for the purpose of 1114 developing Internet standards in which case the procedures for 1115 copyrights defined in the Internet Standards process must be 1116 followed, or as required to translate it into languages other than 1117 English. 1119 The limited permissions granted above are perpetual and will not be 1120 revoked by the Internet Society or its successors or assignees. 1122 This document and the information contained herein is provided on an 1123 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1124 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1125 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1126 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1127 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1129 Acknowledgment 1131 Funding for the RFC Editor function is currently provided by the 1132 Internet Society.