idnits 2.17.1 draft-ietf-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 195 instances of too long lines in the document, the longest one being 11 characters in excess of 72. ** There are 4 instances of lines with control characters in the document. == There are 15 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 == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document 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 (January 14, 2004) is 7408 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 1016, but not defined == Missing Reference: 'IF-MIB' is mentioned on line 1408, but not defined ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-epon-mib-00 -- Obsolete informational reference (is this intentional?): RFC 3276 (Obsoleted by RFC 4319) -- Obsolete informational reference (is this intentional?): RFC 3636 (Obsoleted by RFC 4836) Summary: 6 errors (**), 0 flaws (~~), 7 warnings (==), 4 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: July 14, 2004 January 14, 2004 6 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB 7 draft-ietf-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 July 14, 2004. 31 Copyright Notice 33 Copyright (C) The Internet Society (2004). 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 10Pass-TS and 42 2Base-TL defined in IEEE standard 802.3ah. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. The Internet-Standard Management Framework . . . . . . . . . . 3 48 3. Relation to Interfaces Group MIB . . . . . . . . . . . . . . . 3 49 3.1 Layering Model . . . . . . . . . . . . . . . . . . . . . . . . 4 50 3.2 PMI Aggregation Function (PAF) . . . . . . . . . . . . . . . . 4 51 3.3 Discovery Operation . . . . . . . . . . . . . . . . . . . . . 5 52 3.4 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . 7 56 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 36 58 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 59 Normative References . . . . . . . . . . . . . . . . . . . . . 37 60 Informative References . . . . . . . . . . . . . . . . . . . . 38 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 39 62 Intellectual Property and Copyright Statements . . . . . . . . 40 64 1. Introduction 66 New Ethernet like interfaces have been defined in the Institute of 67 Electrical and Electronics Engineers (IEEE) 802.3ah project a.k.a. 68 Ethernet in the First Mile (EFM) [802.3ah]. In particular 2Base-TL 69 and 10Pass-TS physical interfaces (PHYs), defined over voice-grade 70 copper pairs, have been specified for the long and short reach 71 respectively. These interfaces, collectively called EFMCu, support 72 variable rates and optional Physical Medium Instance (PMI) 73 aggregation (multi-pair bonding). 75 This memo defines a portion of the Management Information Base (MIB) 76 for use with network management protocols in the Internet community 77 to manage EFMCu interfaces. 79 Note that managed objects for Operation, Administration and 80 Management (OAM) and Ethernet over Passive Optical Networks (EPON) 81 clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB 82 [I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB 83 [I-D.ietf-hubmib-efm-epon-mib] respectively. 85 2. The Internet-Standard Management Framework 87 For a detailed overview of the documents that describe the current 88 Internet-Standard Management Framework, please refer to section 7 of 89 RFC 3410 [RFC3410]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. MIB objects are generally 93 accessed through the Simple Network Management Protocol (SNMP). 94 Objects in the MIB are defined using the mechanisms defined in the 95 Structure of Management Information (SMI). This memo specifies a MIB 96 module that is compliant to the SMIv2, which is described in STD 58, 97 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 98 [RFC2580]. A detailed introduction to the current SNMP Management 99 Framework can be found in RFC 2570 [RFC2570]. 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in RFC 2119 [RFC2119]. 105 3. Relation to Interfaces Group MIB 107 This section specifies how the ifStackTable, as defined in the IF-MIB 108 [RFC2863] and ifInvStackTable, as defined in the 109 IF-INVERTED-STACK-MIB [RFC2864] are used for the EFMCu application. 111 3.1 Layering Model 113 An EFMCu interface can aggregate up to 32 Physical Medium Instance 114 (PMI) sublayer devices (modems), using so called PMI Aggregation 115 Function (PAF). 117 *EdNote: Change all occurrences of PMI to PME after 802.3ah/D3.1 is 118 out as per resolution of comment 160.* 120 An generic EFMCu device can have a number of Physical Coding Sublayer 121 (PCS) ports, connected to a MAC via Medium Independent Interface 122 (MII) at the upper layer, and cross-connected to a number of 123 underlying PMIs, with a single PCS per PMI relationship, see clause 124 61.1 of [802.3ah] for more details. 126 Each PMI comprising an aggregated EFMCu port is represented in the 127 Interface table as a separate port with ifType of shdsl(169) for 128 2Base-TL or vdsl(97) for 10Pass-TS. The ifType values are defined in 129 IANAifType-MIB. ifSpeed for each PMI shall return an actual bitrate 130 of the active PMI or a configured bitrate for pre-activated modems 131 (note that unassigned PMI has its default bitrate). 133 The ifStackTable is indexed by the ifIndex values of the aggregated 134 EFMCu port (PCS) and the PMIs connected to it. ifStackTable allows a 135 Network Management application to determine which PMIs are connected 136 to a particular PCS and change connections (if supported by the 137 application). The ifInvStackTable, being an inverted version of the 138 ifStackTable, provides an efficient means for a Network Management 139 application to read a subset of the ifStackTable and thereby 140 determine which PCS runs on top of a particular PMI. 142 A new table efmCuAvailableStackTable defined in this MIB, specifies 143 for each PCS a list of PMIs, which can possibly be cross-connected to 144 that PCS, determined by the cross-connect capability of the device. 145 This table, modeled after ifStackTable, is read only. 147 *EdNote: An alternative would be to use ifStackTable to describe 148 cross-connect capability and efmCuAvailableStackTable to describe 149 actual connections, so that the cross-connect action would be done in 150 the EFM-CU-MIB by modifying the efmCuAvailableStackTable (and not in 151 IF-MIB).* 153 3.2 PMI Aggregation Function (PAF) 155 The PMI Aggregation Function (PAF) is optional and may not be 156 supported. Note however that it is mandatory for the agent to report 157 on the PAF capability for all EFMCu ports (2BASE-TL and 10PASS-TS). 159 *EdNote: Add more info.* 161 3.3 Discovery Operation 163 This MIB allows a Network Management application to control EFM 164 Discovery mechanism and query its results. Note that the Discovery 165 mechanism can work only if PAF is supported and enabled. 167 Two tables are used by Discovery mechanism: ifStackTable and 168 efmCuAvailableStackTable defined. The following pseudo-code defines 169 an example of Discovery for a generic PAF enabled multi-PCS EFMCu 170 device, located at Central Office (CO): 172 foreach PCS[i] in Device 173 { if ( PCS[i].PAFSupported ) // Discover only on ports supporting PAF 174 { dc = PCS[i].DiscoveryCode = MAC[i]; // unique 6 byte code per PCS 175 // go over all currently disconnected PMIs, which can 176 // pottentially be connected to PCS[i] 177 foreach PMI[j] in efmCuAvailableStackTable[PCS[i]] and 178 not in ifStackTable[PCS[i]] 179 { PMI[j].RemoteDiscoveryCode = dc; // Set if Clear 180 r = PMI[j].RemoteDiscoveryCode; // Get 181 if ( r == dc ) 182 { // Remote CPE connected via PMI[j] is/was a peer for 183 // PCS[i]. Connect this PMI to the PCS 184 Add PMI[j] to ifStackTable[PCS[i]]; 185 // Discover all other currently disconnected PMIs, 186 // attached to the same CPE and connect them to the PCS 187 foreach PMI[k] in efmCuAvailableStackTable[PCS[i]] and 188 not in ifStackTable[PCS[i]] 189 { r = PMI[k].RemoteDiscoveryCode; // Get 190 if ( r == dc ) 191 Add PMI[k] to ifStackTable[PCS[i]]; 192 } 193 } 194 // Discovered all PMIs which lead to the same CPE and 195 // connected them to PCS[i]. Go to the next PCS. 196 break; 197 } 198 } 199 } 201 The SNMP Agent builds efmCuStackTable according to the information 202 contained in the Clause 45 PMI_Available_register (see [802.3ah] 203 61.1.5.3 and 45.2.3.20). 205 Adding a PMI to the ifStackTable row for a specific PCS, involves 206 actual connection of the PMI to the PCS, which can be done by 207 modifying Clause 45 PMI_Aggregate_register (see [802.3ah] 61.1.5.3 208 and 45.2.3.21). 210 3.4 Relation to SHDSL MIB 212 SHDSL modems, similar to PMI(s) comprising a 2BaseTL port are 213 described in HDSL2-SHDSL-LINE-MIB [RFC3276]. While 214 HDSL2-SHDSL-LINE-MIB describes standard G.SHDSL modems according to 215 ITU-T G.991.2, IEEE 802.3ah uses soon to be approved G.SHDSL.bis 216 spec, extended to support higher constellations and rates. In 217 addition not all attributes of G.SHDSL modems reflected in 218 HDSL2-SHDSL-LINE-MIB have adequate management objects in the EFM 219 standards. 221 Because of these differences and for the purposes of simplicity and 222 name consistency it was decided not to reference HDSL2-SHDSL-LINE-MIB 223 objects, but define all the relevant objects in this MIB. 225 3.5 Relation to VDSL MIB 227 PMI(s) comprising a 10PassTS port are described in VDSL-LINE-MIB 228 [I-D.ietf-adslmib-vdsl]. In cases where VDSL-LINE-MIB and 802.3ah 229 differ, the definitions in 802.3ah take precedence. 231 Because of these differences and for the purposes of simplicity and 232 name consistency it was decided not to reference VDSL-LINE-MIB 233 objects, but define all the relevant objects in this MIB. 235 3.6 Relation to Ethernet-Like and MAU MIBs 237 The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [RFC3636] 238 is REQUIRED for the EFMCu interfaces. As such EFMCu interfaces 239 2Base-TL/10Pass-TS SHALL return an ifType of ethernetCsmacd(6). 240 Information on the particular flavor of EFMCu that an interface is 241 running is available from ifSpeed in the IF-MIB [RFC2863], and 242 ifMauType in the MAU-MIB. 244 The MAU-MIB shall be augmented to include the following new values 245 for ifMauType (instances of dot2MauType): 247 o dot3MauType2BaseTL - voice grade UTP Phy specified in Clause 61 248 and 63 250 o dot3MauType10PassTS - voice grade UTP Phy specified in Clause 61 251 and 62 253 o *EdNote: Should we also include -O/-R subtypes?* 255 3.7 Mapping of IEEE 802.3ah Managed Objects 257 This section contains the mapping between managed objects defined in 258 [802.3ah] Clause 30, and managed objects defined in this document and 259 in associated MIB modules, i.e., the IF-MIB [RFC2863] and the MAU-MIB 260 [RFC3636]. 262 IEEE 802.3 Managed Object Corresponding SNMP Object 264 *EdNote: Add the table here.* 266 4. Definitions 268 EFM-CU-MIB DEFINITIONS ::= BEGIN 270 IMPORTS 271 MODULE-IDENTITY, OBJECT-TYPE, 272 Gauge32, Integer32, transmission 273 FROM SNMPv2-SMI 274 TruthValue, RowStatus, PhysAddress 275 FROM SNMPv2-TC 276 ifIndex, InterfaceIndexOrZero 277 FROM IF-MIB 278 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 279 FROM SNMPv2-CONF 280 ; 282 efmCuMIB MODULE-IDENTITY 283 LAST-UPDATED "200401130000Z" -- January 13, 2004 284 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 285 Working Group" 286 CONTACT-INFO 287 "WG charter: 288 http://www.ietf.org/html.charters/hubmib-charter.html 290 Mailing Lists: 291 General Discussion: hubmib@ietf.org 292 To Subscribe: hubmib-request@ietf.org 293 In Body: subscribe your_email_address 295 Chair: Dan Romascanu 296 Postal: Avaya Inc. 297 Atidim Technology Park, Bldg. 3 298 Tel Aviv 61131 299 Israel 300 Tel: +972 3 645 8414 301 E-mail: dromasca@avaya.com 302 Editor: Edward Beili 303 Postal: Actelis Networks Inc. 304 25 Bazel St., P.O.B. 10173 305 Petach-Tikva 10173 306 Israel 307 Tel: +972-3-924-3491 308 E-mail: edward.beili@actelis.com" 310 DESCRIPTION 311 "The objects in this MIB module are used to manage 312 the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 313 2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D3.0. 315 The following reference is used throughout this MIB module: 317 [802.3ah] refers to: 318 IEEE Draft P802.3ah/D3.0: 'Draft amendment to - 319 Information technology - Telecommunications and 320 information exchange between systems - Local and 321 metropolitan area networks - Specific requirements - 322 Part 3: Carrier sense multiple access with collision 323 detection (CSMA/CD) access method and physical layer 324 specifications - Media Access Control Parameters, Physical 325 Layers and Management Parameters for subscriber access 326 networks', 05 December 2003. 328 Of particular interest are Clause 61, 'Physical Coding 329 Sublayer (PCS) and common specifications, type 10PASS-TS and 330 type 2BASE-TL', Clause 30, 'Management', and Clause 45, 331 'Management Data Input/Output (MDIO) Interface'. 333 Naming Conventions: 334 Atn - Attenuation 335 CO - Central Office 336 CPE - Customer Premises Equipment 337 EFM - Ethernet in the First Mile 338 EFMCu - EFM Copper 339 MDIO - Management Data Input/Output 340 Mgn - Margin 341 PAF - PMI Aggregation Function 342 PCS - Physical Coding Sublayer 343 PMD - Physical Medium Dependent 344 PMI - Physical Medium Instance 345 PSD - Power Spectral Density 346 SNR - Signal to Noise Ratio 348 Copyright (C) The Internet Society (2004). This version 349 of this MIB module is part of RFC XXXX; see the RFC 350 itself for full legal notices." 352 -- EdNote: Replace XXXX with the actual RFC number & 353 -- remove this note 355 REVISION "200401130000Z" -- January 13, 2004 356 DESCRIPTION "Initial version, published as RFC XXXX." 358 ::= { mib-2 YYY } 360 -- EdNote: Replace YYY with a real OID once it is 361 -- allocated & remove this note. 363 -- Sections of the module 365 efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } 367 efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } 369 -- Groups in the module 371 efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } 373 efmCuPmi OBJECT IDENTIFIER ::= { efmCuObjects 2 } 375 -- PCS Port group 377 efmCuPortTable OBJECT-TYPE 378 SYNTAX SEQUENCE OF EfmCuPortEntry 379 MAX-ACCESS not-accessible 380 STATUS current 381 DESCRIPTION 382 "Table for EFMCu 2BaseTL/10PassTS (PCS) Ports." 383 ::= { efmCuPort 1 } 385 efmCuPortEntry OBJECT-TYPE 386 SYNTAX EfmCuPortEntry 387 MAX-ACCESS not-accessible 388 STATUS current 389 DESCRIPTION 390 "An entry in the EFMCu Port table." 391 INDEX { ifIndex } 392 ::= { efmCuPortTable 1 } 394 EfmCuPortEntry ::= 395 SEQUENCE { 396 efmCuStatus BITS, 397 efmCuPortSidesSupported INTEGER, 398 efmCuPortSide INTEGER, 399 efmCuPAFSupported TruthValue, 400 efmCuRemotePAFSupported TruthValue, 401 efmCuPAFAdminState INTEGER, 402 efmCuPAFDiscoveryCode PhysAddress 403 } 405 efmCuStatus OBJECT-TYPE 406 SYNTAX BITS { 407 noPmi(0), -- no PMI has been assigned to the PCS 408 noRemotePMI(1), -- no peer PMI present 409 lossOfSignal(2), -- Loss of Signal 410 lossOfPower (3), -- Loss of Power 411 lossOfFraming(4), -- Loss of Framing 412 lossOfRemoteFraming(5), -- Remote Loss of Framing 413 snrMgnDefect(6), -- SNR Margin Violation 414 snrMgnRemoteDefect(7), -- Remote SNR Margin Violation 415 lineAtnDefect(8), -- Loop Attenuation Violation 416 lineAtnRemoteDefect(9), -- Remote Loop Attenuation Violation 417 deviceFault(10), -- vendor-dependent diag fault 418 configInitFailure(11), -- configuration initialization failure 419 protocolInitFailure(12), -- protocol initialization failure 420 pafDefect(13) -- PAF related defect 421 } 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "EFMCu (PCS) port Status. This is a bitmap of possible conditions. 426 The various bit positions are: 427 noPmi - no PMI has been assigned to the PCS 428 (in case of PAF) 429 noRemotePMI - one or more PMIs in the aggregation group 430 indicate no peer PMI present 431 lossOfSignal - one or more PMIs in the aggregation group 432 indicate Loss of Signal 433 lossOfPower - one or more PMIs in the aggregation group 434 indicate Loss of Power 435 lossOfFraming - one or more PMIs in the aggregation group 436 indicate Loss of Framing 437 lossOfRemoteFraming - one or more PMIs in the aggregation group 438 indicate Remote Loss of Framing 439 snrMgnDefect - one or more PMIs in the aggregation group 440 indicate SNR Margin Violation 441 snrMgnRemoteDefect - one or more PMIs in the aggregation group 442 indicate Remote SNR Margin Violation 443 lineAtnDefect - one or more PMIs in the aggregation group 444 indicate Loop Attenuation Violation 445 lineAtnRemoteDefect - one or more PMIs in the aggregation group 446 indicate Remote Loop Attenuation Violation 447 deviceFault - one or more PMIs in the aggregation group 448 indicate vendor-dependent diag fault. 449 configInitFailure - one or more PMIs in the aggregation group 450 indicate configuration initialization failure. 451 (e.g. the Peer PMI could not support 452 configuration requested during init). 453 protocolInitFailure - one or more PMIs in the aggregation group 454 indicate protocol initialization failure. 455 pafDefect - PAF related defect 456 -- EdNote: Do we need that? When do we clear 457 -- this bit? 459 This is intended to supplement ifOperStatus. 461 If a Clause 45 MDIO Interface to the PMI is present, then this 462 attribute will consolidate various PMA/PMD registers, namely 463 TBD" 464 -- EdNote: Add relevant registers to Clauses 45,30. Reference them 465 -- instead of TBD. 466 REFERENCE 467 "[802.3ah] " 468 ::= { efmCuPortEntry 1 } 470 efmCuPortSidesSupported OBJECT-TYPE 471 SYNTAX INTEGER { 472 subscriber(1), 473 office(2), 474 both(3) 475 } 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "EFM port supported mode of operation (subtype). 480 The value of 'subscriber' indicates that the port supports 481 'CPE' or '-R' subtype. 482 The value of 'office' indicates that the port supports 483 'CO' or '-O' subtype. 484 The value of 'both' indicates that the port supports both 485 'CO' and 'CPE' subtypes. 486 An actual mode of operation is determined by ifPhySide. 488 If a Clause 45 MDIO Interface to the PCS is present, then this 489 attribute will map to the CO supported and CPE supported 490 bits in the 10P/2B capability register" 491 REFERENCE 492 "[802.3ah] 61.1, 45.2.3.17.2, 45.2.3.17.3" 493 ::= { efmCuPortEntry 2 } 495 efmCuPortSide OBJECT-TYPE 496 SYNTAX INTEGER { 497 subscriber(1), 498 office(2) 499 } 500 MAX-ACCESS read-write 501 STATUS current 502 DESCRIPTION 503 "EFM port mode of operation (subtype). 504 The value of 'subscriber' indicates the port is designated as 505 the 'CPE' or '-R' subtype. 506 The value of the 'office' indicates that the port is 507 designated as the 'CO' or '-O' subtype. 509 Changing efmCuPortSide is a traffic disruptive operation and 510 as such shall be done when the link is Down. Attempts to 511 change this object shall be ignored if the link is Up or 512 Initializing. 513 Attempts to change this object to an unsupported subtype shall 514 be ignored. 516 If a Clause 45 MDIO Interface to the PCS is present, then this 517 attribute will map to the Port sub-type select bit in the 518 10P/2B capability register" 519 REFERENCE 520 "[802.3ah] 61.1, 45.2.3.17.1" 521 ::= { efmCuPortEntry 3 } 523 efmCuPAFSupported OBJECT-TYPE 524 SYNTAX TruthValue 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "PMI Aggregation Function (PAF) Capability of the EFMCu port 529 (PCS). 530 This object has a value of true(1) when the PCS can perform 531 PMI aggregation on the available PMIs. 532 Ports incapable of PAF shall return a value of false(2). 534 If a Clause 45 MDIO Interface to the PCS is present, 535 then this attribute will map to the PAF available bit in the 536 10P/2B capability register." 537 REFERENCE 538 "[802.3ah] 61.2.2, 45.2.3.17.4" 539 ::= { efmCuPortEntry 4 } 541 efmCuRemotePAFSupported OBJECT-TYPE 542 SYNTAX TruthValue 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "PMI Aggregation Function (PAF) Capability of the EFMCu port 547 (PCS) link partner. 548 This object has a value of true(1) when the remote PCS can perform 549 PMI aggregation on the available PMIs. 550 Ports incapable of PAF shall return a value of false(2). 552 If a Clause 45 MDIO Interface to the PCS is present, 553 then this attribute will map to the Remote PAF supported bit in the 554 10P/2B capability register." 555 REFERENCE 556 "[802.3ah] 61.2.2, 45.2.3.17.5" 557 ::= { efmCuPortEntry 5 } 559 efmCuPAFAdminState OBJECT-TYPE 560 SYNTAX INTEGER { 561 enabled(1), 562 disabled(2) 563 } 564 MAX-ACCESS read-write 565 STATUS current 566 DESCRIPTION 567 "Administrative (desired) state of the PAF of the EFMCu port 568 (PCS). 569 When 'disabled', PMI Aggregation will not be performed by the 570 PCS. 571 When 'enabled', PAF will be performed by the PCS when the link 572 is Up, even on a single PMI, if PAF is supported. 573 PCS ports incapable of supporting PAF shall return a value of 574 'disabled'. Attempts to 'enable' such port shall be ignored. 576 Changing PAFAdminState is a traffic disruptive operation and 577 as such shall be done when the link is Down. Attempts to 578 change this object shall be ignored if the link is Up or 579 Initializing. 581 If a Clause 45 MDIO Interface to the PCS is present, then this 582 attribute will map to the PAF enable bit in the 10P/2B 583 capability register" 584 REFERENCE 585 "[802.3ah] 61.2.2, 45.2.3.17.6" 586 ::= { efmCuPortEntry 6 } 588 efmCuPAFDiscoveryCode OBJECT-TYPE 589 SYNTAX PhysAddress 590 MAX-ACCESS read-write 591 STATUS current 592 DESCRIPTION 593 "PAF Discovery Code of the EFMCu port (PCS). 594 A unique 6 Byte long code used by the Discovery function. 595 This object must be instantiated for the CO subtype PCS before 596 writing operations on the PAFRemoteDiscoveryCode 597 (Set_if_Clear and Clear_if_Same) are performed by PMIs 598 associated with the PCS. 599 The value of this object is read-only for CPE port subtypes. 600 (The initial value of this object for CPE ports after reset 601 is 0). 603 Discovery must be performed when the link is Down. 604 Attempts to change this object MUST be rejected with the error 605 inconsistentValue if the link is Up or Initializing. 607 If a Clause 45 MDIO Interface to the PCS is present, then this 608 attribute will map to the Aggregaion Discovery Code registers" 609 REFERENCE 610 "[802.3ah] 61.2.2.8.3, 45.2.1.13" 611 ::= { efmCuPortEntry 7 } 613 -- The PMI group 615 efmCuPmiTable OBJECT-TYPE 616 SYNTAX SEQUENCE OF EfmCuPmiEntry 617 MAX-ACCESS not-accessible 618 STATUS current 619 DESCRIPTION 620 "Table for EFMCu 2BaseTL/10PassTS PMIs (modems). Common part" 621 ::= { efmCuPmi 1 } 623 efmCuPmiEntry OBJECT-TYPE 624 SYNTAX EfmCuPmiEntry 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "An entry in the EFMCu PMI Common table." 629 INDEX { ifIndex } 630 ::= { efmCuPmiTable 1 } 632 EfmCuPmiEntry ::= 633 SEQUENCE { 634 efmCuPmiStatus BITS, 635 efmCuPAFRemoteDiscoveryCode PhysAddress, 636 efmCuPmiSnrMgn Integer32, 637 efmCuPmiRemoteSnrMgn Integer32, 638 efmCuPmiLineAtn Integer32, 639 efmCuPmiRemoteLineAtn Integer32, 640 efmCuPmiThreshLineAtn Integer32, 641 efmCuPmiThreshSnrMgn Integer32 642 } 644 efmCuPmiStatus OBJECT-TYPE 645 SYNTAX BITS { 646 unassigned(0), -- detached from PCS in case of PAF 647 noRemotePmi(1), -- no peer PMI present 648 lossOfSignal(2), -- Loss of Signal 649 lossOfPower(3), -- Loss of Power 650 lossOfFraming(4), -- Loss of Framing 651 lossOfRemoteFraming(5), -- Loss of Framing at peer PMD 652 snrMgnDefect(6), -- SNR Margin dropped below Threshold 653 snrMgnRemoteDefect(7), -- Peer SNR Margin dropped below Threshold 654 -- at the peer PMI 655 lineAtnDefect(8), -- Line Attenuation exceeds Threshold 656 lineAtnRemoteDefect(9), -- Remote Line Attenuation exceeds Threshold 657 deviceFault(10), -- Vendor-dependent diag or self-test fault 658 configInitFailure(11), -- configuration initialization failure 659 protocolInitFailure(12) -- protocol initialization failure 660 } 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "Current PMI link Status. This is a bitmap of possible conditions. 665 The various bit positions are: 666 unassigned - disconnected from PCS in case of PAF 667 noRemotePmi - no peer PMI present, the PMI didn't 668 detect Handshake tones from its peer 669 during initialization. 670 lossOfSignal - Loss of Signal 671 lossOfPower - Loss of Power 672 lossOfFraming - Loss of Framing for 10P or 673 Loss of Sync word for 2B PMD or 674 Loss of 64/65B Framing 675 lossOfRemoteFraming - Loss of Synchronization word at the peer PMD 676 snrMgnDefect - SNR Margin dropped below the Threshold 677 snrMgnRemoteDefect - SNR Margin dropped below the Threshold 678 at the peer PMI 679 lineAtnDefect - Line Attenuation exceeds the Threshold 680 lineAtnRemoteDefect - Line Attenuation exceeds the Threshold 681 at the peer PMI 682 deviceFault - Indicates a vendor-dependent 683 diagnostic or self-test fault 684 has been detected. 685 configInitFailure - configuration initialization failure. 687 the Peer PMI could not support 688 configuration requested during init. 689 protocolInitFailure - protocol initialization failure. 690 due to incompatible protocol used by 691 the Peer PMI during init (that could happen 692 if a peer PMD is G.SDHSL/VDSL modem for 693 2BaseTL/10PassTS PMI respectivelly). 695 This is intended to supplement ifOperStatus. Note that there 696 is a 1-1 relationship between the status bits defined in this 697 object and the notification thresholds defined elsewhere in 698 this MIB. 700 If a Clause 45 MDIO Interface to the PMI is present, then this 701 attribute will consolidate various PMA/PMD registers, namely 702 PMA/PMD status 1 register, 10P incoming indicator bits status 703 register, 2B state defects register" 704 -- EdNote: Add relevant registers to Clause 45/30. Reference them. 705 REFERENCE 706 "[802.3ah] 45.2.1.2, 45.2.1.33, 45.2.1.42" 707 ::= { efmCuPmiEntry 1 } 709 efmCuPAFRemoteDiscoveryCode OBJECT-TYPE 710 SYNTAX PhysAddress 711 MAX-ACCESS read-write 712 STATUS current 713 DESCRIPTION 714 "PAF Remote Discovery Code of the PMI port at CO. 715 A 6 Byte long Discovery Code of the peer PCS connected via 716 the PMI. 717 Reading this object results in a Discovery Get operation. 718 Writing a zero to this object results in a Discovery 719 Clear_if_Same operation (the value of the ifPAFDiscoveryCode 720 at the peer PCS shall be the same as ifPAFDiscoveryCode of 721 the local PCS associated with the PMI for the operation to 722 succeed). 723 Writing a non-zero value to this object reslults in a 724 Discovery Set_if_Clear operation. 725 This object does not exist in CPE port subtypes. A zero length 726 octet string shall be returned for CPE port subtypes and also 727 when PAF aggregation is not enabled. 729 Discovery must be performed when the link is Down. 730 Attempts to change this object MUST be rejected with the error 731 inconsistentValue, if the link is Up or Initializing. 733 If a Clause 45 MDIO Interface to the PCS is present, then this 734 attribute is a function of Aggregation Discovery Operation, 735 Code and Operation result registers" 736 REFERENCE 737 "[802.3ah] 61.2.2.8.3, 45.2.1.12.1" 738 ::= { efmCuPmiEntry 2 } 740 efmCuPmiSnrMgn OBJECT-TYPE 741 SYNTAX Integer32(-127..128) 742 UNITS "dB" 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "The current Signal-to-Noise Ratio (SNR) margin with respect 747 to the received signal as perceived by the local PMI. 749 If a Clause 45 MDIO Interface is present, then this 750 attribute will map to the Rx SNR Margin register" 751 REFERENCE 752 "[802.3ah] 45.2.1.18" 753 ::= { efmCuPmiEntry 3 } 755 efmCuPmiRemoteSnrMgn OBJECT-TYPE 756 SYNTAX Integer32(-127..128) 757 UNITS "dB" 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "The current SNR margin in dB with respect to the received signal, 762 as perceived by the remote (link partner) PMI. 764 This object is not supported by CPE port subtypes. 766 If a Clause 45 MDIO Interface is present, then this 767 attribute will map to the Rx SNR Margin register for link partner" 768 REFERENCE 769 "[802.3ah] 45.2.1.18" 770 ::= { efmCuPmiEntry 4 } 772 efmCuPmiLineAtn OBJECT-TYPE 773 SYNTAX Integer32(-127..128) 774 UNITS "dB" 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The current Line Attenuation in dB as perceived by the local PMI. 780 If a Clause 45 MDIO Interface is present, then this 781 attribute will map to the Line Attenuation register" 782 REFERENCE 783 "[802.3ah] 45.2.1.21" 784 ::= { efmCuPmiEntry 5 } 786 efmCuPmiRemoteLineAtn OBJECT-TYPE 787 SYNTAX Integer32(-127..128) 788 UNITS "dB" 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "The current Line Attenuation in dB as perceived by the remote 793 (link partner) PMI. 795 This object is not supported by CPE port subtypes. 797 If a Clause 45 MDIO Interface is present, then this 798 attribute will map to the Line Attenuation register for link partner" 799 REFERENCE 800 "[802.3ah] 45.2.1.21" 801 ::= { efmCuPmiEntry 6 } 803 efmCuPmiThreshLineAtn OBJECT-TYPE 804 SYNTAX Integer32(-127..128) 805 UNITS "dB" 806 MAX-ACCESS read-write 807 STATUS current 808 DESCRIPTION 809 "Desired Line Attenuation Threshold for the 2B/10P PMI. 810 This object configures the line attenuation alarm threshold. 811 When the current value of Line Attenuation reaches 812 or exceeds this threshold, a efmCuPmiLineAtnCrossing 813 notification MAY be generated. 815 This object is writable for the CO subtype PMIs (-O). 816 It is read-only for the CPE subtype (-R). 818 Changing of the Line Attenuation Threshold must be performed when the 819 link is Down. Attempts to change this object MUST be rejected with 820 the error inconsistentValue, if the link is Up or 821 Initializing. 823 If a Clause 45 MDIO Interface to the PMI is present, then this 824 attribute will map to the Loop attenuation threshold bits in the 825 2B PMD line quality thresholds register" 826 REFERENCE 827 "[802.3ah] 45.2.1.36" 828 ::= { efmCuPmiEntry 7 } 830 efmCuPmiThreshSnrMgn OBJECT-TYPE 831 SYNTAX Integer32(-127..128) 832 UNITS "dB" 833 MAX-ACCESS read-write 834 STATUS current 835 DESCRIPTION 836 "Desired SNR Margin Threshold for the 2B/10P PMI. 837 This object configures the SNR margin alarm threshold. 838 When the current value of SNR Margin reaches 839 or exceeds this threshold, a efmCuPmiSnrMgnCrossing 840 notification MAY be generated. 842 This object is writable for the CO subtype PMIs 843 (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype 844 (2BaseTL-R/10PassTS-R). 846 Changing of the SNR Margin Threshold must be performed when the 847 link is Down. Attempts to change this object MUST be rejected with 848 the error inconsistentValue, if the link is Up or 849 Initializing. 851 If a Clause 45 MDIO Interface to the PMI is present, then this 852 attribute will map to the SNR margin threshold bits in the 853 2B PMD line quality thresholds register" 854 REFERENCE 855 "[802.3ah] 45.2.1.36" 856 ::= { efmCuPmiEntry 8 } 858 -- PMI Notifications Group 860 efmCuPmiNotifications OBJECT IDENTIFIER ::= { efmCuPmi 2 } 862 -- EdNote: Add more notificatoins here, for example 863 -- efmCuPmiPerfES, 864 -- efmCuPmiPerfSES, 865 -- efmCuPmiPerfCRCanomalies, 866 -- efmCuPmiPerfLOSWS, 867 -- efmCuPmiPerfUAS, 868 -- efmCuPmiDeviceFault, 869 -- efmCuPmiLocalPowerLoss 871 efmCuPmiLinkDefect NOTIFICATION-TYPE 872 OBJECTS { 873 -- ifINdex is not needed here since we are under specific PMI 874 efmCuPmiStatus 875 -- EdNote: should I add anything else here 876 } 877 STATUS current 878 DESCRIPTION 879 "This notification indicates that a link defect has been detected 880 by the PMI, preventing it from been operational. 881 Note that in case of PAF, PMI link defect may not cause 882 the whole PHY to go down, it will just cause bandwidth degradation. 883 -- EdNote: add throttling limitations here" 884 ::= { efmCuPmiNotifications 1 } 886 efmCuPmiLineAtnCrossing NOTIFICATION-TYPE 887 OBJECTS { 888 efmCuPmiLineAtn, 889 efmCuPmiThreshLineAtn 890 } 891 STATUS current 892 DESCRIPTION 893 "This notification indicates that the loop attenuation 894 threshold (as per the efmCuPmiThreshLineAtn 895 value) has been reached/exceeded for the 2Base-TL/10Pass-TS 896 PMI. 897 -- EdNote: add throttling limitations here" 898 ::= { efmCuPmiNotifications 2 } 900 efmCuPmiRemoteLineAtnCrossing NOTIFICATION-TYPE 901 OBJECTS { 902 efmCuPmiRemoteLineAtn, 903 efmCuPmiThreshLineAtn 904 } 905 STATUS current 906 DESCRIPTION 907 "This notification indicates that the loop attenuation 908 threshold (as per the efmCuPmiThreshLineAtn 909 value) has been reached/exceeded for the 2Base-TL/10Pass-TS 910 PMI link partner. 911 -- EdNote: add throttling limitations here" 912 ::= { efmCuPmiNotifications 3 } 914 efmCuPmiSnrMgnCrossing NOTIFICATION-TYPE 915 OBJECTS { 916 efmCuPmiSnrMgn, 917 efmCuPmiThreshSnrMgn 918 } 919 STATUS current 920 DESCRIPTION 921 "This notification indicates that the SNR margin threshold (as 922 per the efmCuPmiThreshSnrMgn value) has been 923 reached/exceeded for the 2Base-TL/10Pass-TS PMI. 924 -- EdNote: add throttling limitations here" 925 ::= { efmCuPmiNotifications 4 } 927 efmCuPmiRemoteSnrMgnCrossing NOTIFICATION-TYPE 928 OBJECTS { 929 efmCuPmiRemoteSnrMgn, 930 efmCuPmiThreshSnrMgn 931 } 932 STATUS current 933 DESCRIPTION 934 "This notification indicates that the SNR margin threshold (as 935 per the efmCuPmiThreshSnrMgn value) has been 936 reached/exceeded for the 2Base-TL/10Pass-TS PMI link partner. 937 -- EdNote: add throttling limitations here" 938 ::= { efmCuPmiNotifications 5 } 940 -- 2BaseTL specific PMI group 942 efmCuPmi2BTable OBJECT-TYPE 943 SYNTAX SEQUENCE OF EfmCuPmi2BEntry 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "Table for EFMCu 2BaseTL PMIs (modems)." 948 ::= { efmCuPmi 3 } 950 efmCuPmi2BEntry OBJECT-TYPE 951 SYNTAX EfmCuPmi2BEntry 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION 955 "An entry in the EFMCu 2BaseTL PMI table." 956 AUGMENTS { efmCuPmiEntry } 957 ::= { efmCuPmi2BTable 1 } 959 EfmCuPmi2BEntry ::= 960 SEQUENCE { 961 efmCuPmi2BProfile INTEGER, 962 efmCuPmi2BRegion INTEGER, 963 efmCuPmi2BPower Integer32, 964 efmCuPmi2BDataRate Integer32, 965 efmCuPmi2BConstellation INTEGER 966 } 968 efmCuPmi2BProfile OBJECT-TYPE 969 SYNTAX INTEGER { -- Rate Power Region Constellation 970 -- (Kbps) (dBm) 971 profile0(0), -- Undefined (individual PMI params are used) 972 profile1(1), -- 3072 13.5 Annex A 32-TCPAM 973 profile2(2), -- 2048 13.5 Annex A 16-TCPAM 974 profile3(3), -- 1024 13.5 Annex A 16-TCPAM 975 profile4(4), -- 704 13.5 Annex A 16-TCPAM 976 profile5(5), -- 512 13.5 Annex A 16-TCPAM 977 profile6(6), -- 3072 14.5 Annex B 32-TCPAM 978 profile7(7), -- 2048 14.5 Annex B 16-TCPAM 979 profile8(8), -- 1024 13.5 Annex B 16-TCPAM 980 profile9(9), -- 704 13.5 Annex B 16-TCPAM 981 profile10(10) -- 512 13.5 Annex B 16-TCPAM 982 } 983 MAX-ACCESS read-write 984 STATUS current 985 DESCRIPTION 986 "2BaseTL PMI complete Profile, instantiating 987 individual PMI parameters: efmCuPmi2BRegion, efmCuPmi2BPower, 988 efmCuPmi2BDataRate and efmCuPmi2BConstellation as specified in 989 802.3ah Annex 63A. 990 The value of profile0 is returned, when any of the individual 991 PMI parameters are modidifed directly by modifying a corresponding 992 variable. 993 This object is writable for the CO subtype PMIs (2BaseTL-O). 994 It is read-only for the CPE subtype (2BaseTL-R). 996 Changing PMI profile must be performed when the link is 997 Down. Attempts to change this object MUST be rejected with 998 the error inconsistentValue, if the link is Up or 999 Initializing. 1001 This attribute maps to the aProfileSelect variable in Clause 30." 1002 REFERENCE 1003 "[802.3ah] Annex 63A, 30.5.1.1.8" 1004 ::= { efmCuPmi2BEntry 1 } 1006 efmCuPmi2BRegion OBJECT-TYPE 1007 SYNTAX INTEGER { 1008 regionA(1), -- Annex A 1009 regionB(2), -- Annex B 1010 regionC(3) -- Annex C 1011 } 1012 MAX-ACCESS read-write 1013 STATUS current 1014 DESCRIPTION 1015 "Desired Power Spectral Density (PSD) Regional setting as specified 1016 in Regional Annex of [ITU-T G.991.2] to operate under. 1017 This object is writable for the CO subtype PMIs (2BaseTL-O). 1018 It is read-only for the CPE subtype (2BaseTL-R). 1020 Changing Regional Annex must be performed when the link is 1021 Down. Attempts to change this object MUST be rejected with 1022 the error inconsistentValue, if the link is Up or 1023 Initializing. 1025 If a Clause 45 MDIO Interface to the PMI is present, then this 1026 attribute will map to the Region bits in the 2B general 1027 parameter register" 1028 REFERENCE 1029 "[802.3ah] 45.2.1.34" 1030 ::= { efmCuPmi2BEntry 2 } 1032 efmCuPmi2BPower OBJECT-TYPE 1033 SYNTAX Integer32(0..15) 1034 UNITS "dBm" 1035 MAX-ACCESS read-write 1036 STATUS current 1037 DESCRIPTION 1038 "Desired Signal Transmit Power. Multiple of 0.5dBm. 1039 This object is writable for the CO subtype PMIs (2BaseTL-O). 1040 It is read-only for the CPE subtype (2BaseTL-R). 1042 Changing of the Signal Transmit Power must be performed when the 1043 link is Down. Attempts to change this object MUST be rejected with 1044 the error inconsistentValue, if the link is Up or 1045 Initializing. 1047 If a Clause 45 MDIO Interface to the PMI is present, then this 1048 attribute will map to the Power bits in the 2B PMD 1049 parameters register" 1050 REFERENCE 1051 "[802.3ah] 45.2.1.35" 1052 ::= { efmCuPmi2BEntry 3 } 1054 efmCuPmi2BDataRate OBJECT-TYPE 1055 SYNTAX Integer32(0..5696) 1056 UNITS "Kbps" 1057 MAX-ACCESS read-write 1058 STATUS current 1059 DESCRIPTION 1060 "Desired 2BaseTL PMI Data Rate. 1061 The rate is fixed when the value is n x 64Kbps, where n=3..60 for 1062 16-TCPAM and n=12..89 for 32-TCPAM. The value of 0 means 1063 that data rate is not fixed but is adaptive and should be set to 1064 the maximum attainable rate during line probing. 1065 This object is writable for the CO subtype PMIs (2BaseTL-O). 1066 It is read-only for the CPE subtype (2BaseTL-R). 1068 Changing of the Data Rate must be performed when the 1069 link is Down. Attempts to change this object MUST be rejected with 1070 the error inconsistentValue, if the link is Up or 1071 Initializing. 1073 If a Clause 45 MDIO Interface to the PMI is present, then this 1074 attribute will map to the Data Rate bits in the 2B PMD 1075 parameters register" 1076 REFERENCE 1077 "[802.3ah] 45.2.1.35" 1078 ::= { efmCuPmi2BEntry 4 } 1080 efmCuPmi2BConstellation OBJECT-TYPE 1081 SYNTAX INTEGER { 1082 tcpam16(1), -- 16-TCPAM 1083 tcpam32(2) -- 32-TCPAM 1084 } 1085 MAX-ACCESS read-write 1086 STATUS current 1087 DESCRIPTION 1088 "Desired TCPAM Constellation of the 2BaseTL PMI. 1089 This object is writable for the CO subtype PMIs (2BaseTL-O). 1090 It is read-only for the CPE subtype (2BaseTL-R). 1092 Changing Constellation must be performed when the link is 1093 Down. Attempts to change this object MUST be rejected with 1094 the error inconsistentValue, if the link is Up or 1095 Initializing. 1097 If a Clause 45 MDIO Interface to the PMI is present, then this 1098 attribute will map to the Constellation bits in the 2B general 1099 parameter register" 1100 REFERENCE 1101 "[802.3ah] 45.2.1.34" 1102 ::= { efmCuPmi2BEntry 5 } 1104 -- 10PassTS specific PMI group 1106 efmCuPmi10PTable OBJECT-TYPE 1107 SYNTAX SEQUENCE OF EfmCuPmi10PEntry 1108 MAX-ACCESS not-accessible 1109 STATUS current 1110 DESCRIPTION 1111 "Table for EFMCu 10PassTS PMIs (modems)." 1112 ::= { efmCuPmi 4 } 1114 efmCuPmi10PEntry OBJECT-TYPE 1115 SYNTAX EfmCuPmi10PEntry 1116 MAX-ACCESS not-accessible 1117 STATUS current 1118 DESCRIPTION 1119 "An entry in the EFMCu 10PassTS PMI table." 1120 AUGMENTS { efmCuPmiEntry } 1121 ::= { efmCuPmi10PTable 1 } 1123 EfmCuPmi10PEntry ::= 1124 SEQUENCE { 1125 efmCuPmi10PProfile INTEGER, 1126 efmCuPmi10PBandplanPSDMaskProfile INTEGER, 1127 efmCuPmi10PUPBOReferenceProfile INTEGER, 1128 efmCuPmi10PBandNotchProfiles BITS, 1129 efmCuPmi10PPayloadURateProfile INTEGER, 1130 efmCuPmi10PPayloadDRateProfile INTEGER, 1131 efmCuPmi10PElectricalLength Integer32 1132 -- EdNote: To be continued 1133 } 1135 efmCuPmi10PProfile OBJECT-TYPE 1136 SYNTAX INTEGER { -- BandplanPSDMask UPBO BandNotch URate DRate 1137 profile0(0), -- Undefined (individual PMI Params are used) 1138 profile1(1), -- p1 p3 p2,6,10,11 p20 p20 1139 -- default profile 1140 profile2(2), -- TBD 1141 profile3(3), -- TBD 1142 profile4(4), -- TBD 1143 profile5(5), -- TBD 1144 profile6(6), -- TBD 1145 profile7(7), -- TBD 1146 profile8(8), -- TBD 1147 profile9(9), -- TBD 1148 profile10(10) -- TBD 1149 profile10(11) -- TBD 1150 profile10(12) -- TBD 1151 profile10(13) -- TBD 1152 profile10(14) -- TBD 1153 profile10(15) -- TBD 1154 profile10(16) -- TBD 1155 profile10(17) -- TBD 1156 profile10(18) -- TBD 1157 profile10(19) -- TBD 1158 profile10(20) -- TBD 1159 profile10(21) -- TBD 1160 } 1161 -- EdNote: replace TBD with values from table 62B-1 after 802.3ah/D3.1 1162 -- is released, as per comment resolution #160. 1163 MAX-ACCESS read-write 1164 STATUS current 1165 DESCRIPTION 1166 "10PassTS PMI complete profile, instantiating 1167 individual PMI parameters: efmCuPmi10PBandplanPSDMaskProfile, 1168 efmCuPmi10PUPBOReferenceProfile, efmCuPmi10PBandNotchProfile, 1169 efmCuPmi10PUDataRateProfile and efmCuPmi10PDRateProfile as follows: 1170 -- EdNote: put a table here. 1171 The value of profile0 is returned, when any of the individual 1172 PMI parameters are modidifed directly by modifying a corresponding 1173 variable. 1174 This object is writable for the CO subtype PMIs (10PassTS-O). 1175 It is read-only for the CPE subtype (10PassTS-R). 1177 Changing PMI profile must be performed when the link is 1178 Down. Attempts to change this object MUST be rejected with 1179 the error inconsistentValue, if the link is Up or 1180 Initializing. 1182 This attribute maps to the XXX variable in Clause 30." 1183 -- EdNote: Define a variable in Clause 30 with relevant profiles 1184 -- defined. Put a reference to it. 1185 REFERENCE 1186 "[802.3ah] TBD" 1187 ::= { efmCuPmi10PEntry 1 } 1189 efmCuPmi10PBandplanPSDMaskProfile OBJECT-TYPE 1190 SYNTAX INTEGER { -- PSD Mask Bands Bandplan 1191 profile1(1), -- T1.424/Trial-Use P1 FTTCab.M1 x/D/U/D/U A 1192 profile2(2), -- T1.424/Trial-Use P1 FTTEx.M1 1193 profile3(3), -- T1.424/Trial-Use P1 FTTCab.M2 1194 profile4(4), -- T1.424/Trial-Use P1 FTTEx.M2 1195 profile5(5), -- T1.424/Trial-Use P1 FTTCab.M1 D/D/U/D/U 1196 profile6(6), -- T1.424/Trial-Use P1 FTTEx.M1 1197 profile7(7), -- T1.424/Trial-Use P1 FTTCab.M2 1198 profile8(8), -- T1.424/Trial-Use P1 FTTEx.M2 1199 profile9(9), -- T1.424/Trial-Use P1 FTTCab.M1 U/D/U/D/x 1200 profile10(10) -- T1.424/Trial-Use P1 FTTEx.M1 1201 profile11(11), -- T1.424/Trial-Use P1 FTTCab.M2 1202 profile12(12), -- T1.424/Trial-Use P1 FTTEx.M2 1203 profile13(13), -- TS1 101 270-1 Pcab.M1.A x/D/U/D/U B 1204 profile14(14), -- TS1 101 270-1 Pcab.M1.B 1205 profile15(15), -- TS1 101 270-1 Pex.P1.M1 1206 profile16(16), -- TS1 101 270-1 Pex.P2.M1 1207 profile17(17), -- TS1 101 270-1 Pcab.M2 1208 profile18(18), -- TS1 101 270-1 Pex.P1.M2 1209 profile19(19), -- TS1 101 270-1 Pex.P2.M2 1210 profile20(20) -- TS1 101 270-1 Pcab.M1.A U/D/U/D/x 1211 profile21(21), -- TS1 101 270-1 Pcab.M1.B 1212 profile22(22), -- TS1 101 270-1 Pex.P1.M1 1213 profile23(23), -- TS1 101 270-1 Pex.P2.M1 1214 profile24(24), -- TS1 101 270-1 Pcab.M2 1215 profile25(25), -- TS1 101 270-1 Pex.P1.M2 1216 profile26(26), -- TS1 101 270-1 Pex.P2.M2 1217 profile27(27), -- G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F 1218 profile28(28), -- G.993.1 F.1.2.2 (VDSLoTCM-ISDN) 1219 profile29(29) -- G.993.1 F.1.2.3 (PSD reduction) 1220 } 1221 MAX-ACCESS read-write 1222 STATUS current 1223 DESCRIPTION 1224 "10PassTS PMI Bandplan and PSD Mask profile, 1225 as specified in 802.3ah Annex 62A. 1226 This object is writable for the CO subtype PMIs (10PassTS-O). 1227 It is read-only for the CPE subtype (10PassTS-R). 1229 Changing PMI Bandplan and PSD MAsk profile must be performed 1230 when the link is Down. Attempts to change this object MUST be 1231 rejected with the error inconsistentValue, if the link is Up or 1232 Initializing. 1234 This attribute maps to the aBandplanPSDMaskProfile variable 1235 in Clause 30." 1236 REFERENCE 1237 "[802.3ah] Annex 62A, 30.5.1.1.22" 1238 ::= { efmCuPmi10PEntry 2 } 1240 efmCuPmi10PUPBOReferenceProfile OBJECT-TYPE 1241 SYNTAX INTEGER { -- Reference PSD 1242 profile1(1), -- T1.424/Trial-Use Noise A M1 1243 profile2(2), -- T1.424/Trial-Use Noise A M2 1244 profile3(3), -- T1.424/Trial-Use Noise F M1 1245 profile4(4), -- T1.424/Trial-Use Noise F M2 1246 profile5(5), -- ETSI TS 101 270-1 Noise A&B 1247 profile6(6), -- ETSI TS 101 270-1 Noise C 1248 profile7(7), -- ETSI TS 101 270-1 Noise D 1249 profile8(8), -- ETSI TS 101 270-1 Noise E 1250 profile9(9) -- ETSI TS 101 270-1 Noise F 1251 } 1252 MAX-ACCESS read-write 1253 STATUS current 1254 DESCRIPTION 1255 "10PassTS PMI Upstream Power Back-Off (UPBO) Reference PSD Profile, 1256 as specified in 802.3ah Annex 62A. 1257 This object is writable for the CO subtype PMIs (10PassTS-O). 1258 It is read-only for the CPE subtype (10PassTS-R). 1260 Changing UPBO Reference profile must be performed 1261 when the link is Down. Attempts to change this object MUST be 1262 rejected with the error inconsistentValue, if the link is Up or 1263 Initializing. 1265 This attribute maps to the aUPBOReferenceProfile variable 1266 in Clause 30." 1267 REFERENCE 1268 "[802.3ah] Annex 62A.3.4, 30.5.1.1.23" 1269 ::= { efmCuPmi10PEntry 3 } 1271 efmCuPmi10PBandNotchProfiles OBJECT-TYPE 1272 SYNTAX BITS { -- G.991.3 T1.424/T-U TS 101 270-1 StartF EndF 1273 -- Table Table Table (MHz) (MHz) 1274 profile0(0), -- no profile 1275 profile1(1), -- F-5 #01 - - 1.810 1.825 1276 profile2(2), -- 6-2 15-1 17 1.810 2.000 1277 profile3(3), -- F-5 #02 - - 1.907 1.912 1278 profile4(4), -- F-5 #03 - - 3.500 3.575 1279 profile5(5), -- 6-2 - 17 3.500 3.800 1280 profile6(6), -- - 15-1 - 3.500 4.000 1281 profile7(7), -- F-5 #04 - - 3.747 3.754 1282 profile8(8), -- F-5 #05 - - 3.791 3.805 1283 profile9(9), -- 6-2 - 17 7.000 7.100 1284 profile10(10), -- F-5 #06 15-1 - 7.000 7.300 1285 profile11(11) -- 6-2 15-1 17 10.100 10.150 1286 } 1287 MAX-ACCESS read-write 1288 STATUS current 1289 DESCRIPTION 1290 "10PassTS PMI Egress Control Band Notch Profile bitmap, 1291 as specified in 802.3ah Annex 62A. 1292 This object is writable for the CO subtype PMIs (10PassTS-O). 1293 It is read-only for the CPE subtype (10PassTS-R). 1294 Any combination of profiles can be specified by ORing individual 1295 profiles, for example value of 0x0622 selects profiles 1296 2,6,10 and 11. 1298 Changing Band Notch profiles must be performed 1299 when the link is Down. Attempts to change this object MUST be 1300 rejected with the error inconsistentValue, if the link is Up or 1301 Initializing. 1303 This attribute maps to the aBandNotchProfile variable 1304 in Clause 30." 1305 REFERENCE 1306 "[802.3ah] Annex 62A.3.5, 30.5.1.1.19" 1307 ::= { efmCuPmi10PEntry 4 } 1309 efmCuPmi10PPayloadURateProfile OBJECT-TYPE 1310 SYNTAX INTEGER { -- Upstream Payload Rate (Mbps) 1311 profile100(100), -- 50 1312 profile70(70), -- 35 1313 profile50(50), -- 25 1314 profile30(30), -- 15 1315 profile25(25), -- 12.5 1316 profile20(20), -- 10 1317 profile15(15), -- 7.5 1318 profile10(10), -- 5 1319 profile5(5) -- 2.5 1320 } 1321 MAX-ACCESS read-write 1322 STATUS current 1323 DESCRIPTION 1324 "10PassTS PMI Upstream Payload Rate Profile, 1325 as specified in 802.3ah Annex 62A. 1326 This object is writable for the CO subtype PMIs (10PassTS-O). 1327 It is read-only for the CPE subtype (10PassTS-R). 1329 The SET operation sets a target for the PHY's Upstream Payload 1330 Bitrate as seen at the MII. If the payload rate of the selected 1331 profile cannot be achieved based on the loop environment, 1332 bandplan and PSD mask, the PHY shall drop the link. 1334 Changing Upstream Payload Rate Profile must be performed 1335 when the link is Down. Attempts to change this object MUST be 1336 rejected with the error inconsistentValue, if the link is Up or 1337 Initializing. 1339 This attribute maps to the aPayloadRateProfileUpstream variable 1340 in Clause 30." 1341 REFERENCE 1342 "[802.3ah] Annex 62A.3.6, 30.5.1.1.20" 1343 ::= { efmCuPmi10PEntry 5 } 1345 efmCuPmi10PPayloadDRateProfile OBJECT-TYPE 1346 SYNTAX INTEGER { -- Downstream Payload Rate (Mbps) 1347 profile200(200), -- 100 1348 profile140(140), -- 70 1349 profile100(100), -- 50 1350 profile70(70), -- 35 1351 profile50(50), -- 25 1352 profile30(30), -- 15 1353 profile25(25), -- 12.5 1354 profile20(20), -- 10 1355 profile15(15), -- 7.5 1356 profile10(10), -- 5 1357 profile5(5) -- 2.5 1358 } 1360 MAX-ACCESS read-write 1361 STATUS current 1362 DESCRIPTION 1363 "10PassTS PMI Downstream Payload Rate Profile, 1364 as specified in 802.3ah Annex 62A. 1365 This object is writable for the CO subtype PMIs (10PassTS-O). 1366 It is read-only for the CPE subtype (10PassTS-R). 1368 The SET operation sets a target for the PHY's Downstream Payload 1369 Bitrate as seen at the MII. If the payload rate of the selected 1370 profile cannot be achieved based on the loop environment, 1371 bandplan and PSD mask, the PHY shall drop the link. 1373 Changing Downstream Payload Rate Profile must be performed 1374 when the link is Down. Attempts to change this object MUST be 1375 rejected with the error inconsistentValue, if the link is Up or 1376 Initializing. 1378 This attribute maps to the aPayloadRateProfileDownstream variable 1379 in Clause 30." 1380 REFERENCE 1381 "[802.3ah] Annex 62A.3.6, 30.5.1.1.21" 1382 ::= { efmCuPmi10PEntry 6 } 1384 efmCuPmi10PElectricalLength OBJECT-TYPE 1385 SYNTAX Integer32(0..8192,65535) 1386 UNITS "m" 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "Electrical Length in meters as perceived by the 10PassTS PMI 1391 after the link is established. 1392 The value of 65535 is returned if the link is Down or Initializing 1393 or the PMI is unable to estimate the Electrical Length. 1395 If a Clause 45 MDIO Interface to the PMI is present, then this 1396 attribute will map to the 10P Electrical Length register" 1397 REFERENCE 1398 "[802.3ah] 45.2.1.21" 1399 ::= { efmCuPmi10PEntry 7 } 1401 -- efmCuAvailableStackTable for use in Discovery 1403 efmCuAvailableStackTable OBJECT-TYPE 1404 SYNTAX SEQUENCE OF EfmCuAvailableStackEntry 1405 MAX-ACCESS not-accessible 1406 STATUS current 1407 DESCRIPTION 1408 "This table, modeled after ifStackTable from [IF-MIB], 1409 contains information on the possible 'on-top-of' 1410 relationships between the multiple sub-layers of network 1411 interfaces (as opposed to actual relationships in 1412 ifStackTable). In particular, it contains information on 1413 which PCS ports (sub-layers) can possible run 'on top of' 1414 which PMIs (sublayers), as determined by cross-connect 1415 capability of the EFMCu device, where each sub-layer 1416 corresponds to a conceptual row in the ifTable. For example, 1417 when the PCS port with ifIndex value x can be connected 1418 to run on top of the PMI with ifIndex value y, then this table 1419 contains: 1421 efmCuAvailableStackStatus.x.y=active 1423 For each ifIndex value, I, which identifies a PCS or PMI 1424 interface, there are always at least two instantiated rows 1425 in this table associated with I. For one of these rows, I 1426 is the value of efmCuAvailableStackHigherLayer; for the other, 1427 I is the value of efmCuAvailableStackLowerLayer. 1428 Note that there's always at least on PCS for each PMI and at 1429 least one PMI for each PCS in the EFMCu devices. 1430 This table is ready only as it describes device capability" 1431 REFERENCE 1432 "ifStackTable of RFC 2863" 1433 ::= { efmCuObjects 3 } 1435 efmCuAvailableStackEntry OBJECT-TYPE 1436 SYNTAX EfmCuAvailableStackEntry 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "Information on a particular relationship between two sub- 1441 layers, specifying that one sub-layer runs on 'top' of the 1442 other sub-layer. Each sub-layer corresponds to a conceptual 1443 row in the ifTable." 1444 INDEX { 1445 efmCuAvailableStackHigherLayer, 1446 efmCuAvailableStackLowerLayer 1447 } 1448 ::= { efmCuAvailableStackTable 1 } 1450 EfmCuAvailableStackEntry ::= 1451 SEQUENCE { 1452 efmCuAvailableStackHigherLayer InterfaceIndexOrZero, 1453 efmCuAvailableStackLowerLayer InterfaceIndexOrZero, 1454 efmCuAvailableStackStatus RowStatus 1456 } 1458 efmCuAvailableStackHigherLayer OBJECT-TYPE 1459 SYNTAX InterfaceIndexOrZero 1460 MAX-ACCESS not-accessible 1461 STATUS current 1462 DESCRIPTION 1463 "The value of ifIndex corresponding to the higher sub-layer 1464 of the relationship, i.e., the sub-layer which runs on 'top' 1465 of the sub-layer identified by the corresponding instance of 1466 ifStackLowerLayer. If there is no higher sub-layer (below 1467 the internetwork layer), then this object has the value 0." 1468 ::= { efmCuAvailableStackEntry 1 } 1470 efmCuAvailableStackLowerLayer OBJECT-TYPE 1471 SYNTAX InterfaceIndexOrZero 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "The value of ifIndex corresponding to the lower sub-layer 1476 of the relationship, i.e., the sub-layer which runs 'below' 1477 the sub-layer identified by the corresponding instance of 1478 ifStackHigherLayer. If there is no lower sub-layer, then 1479 this object has the value 0." 1480 ::= { efmCuAvailableStackEntry 2 } 1482 efmCuAvailableStackStatus OBJECT-TYPE 1483 SYNTAX RowStatus 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "The status of the relationship between two sub-layers. 1489 This object is read only, unlike ifStackStatus, as it 1490 describes the device capability." 1491 ::= { efmCuAvailableStackEntry 3 } 1493 -- 1494 -- Conformance Statements 1495 -- 1497 efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } 1499 efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } 1501 -- Object Groups 1502 efmCuPortBasicGroup OBJECT-GROUP 1503 OBJECTS { 1504 efmCuPortSidesSupported, 1505 efmCuPortSide, 1506 efmCuPAFSupported 1507 } 1508 STATUS current 1509 DESCRIPTION 1510 "A collection of objects required for all EFMCu ports." 1511 ::= { efmCuGroups 1 } 1513 efmCuPAFGroup OBJECT-GROUP 1514 OBJECTS { 1515 efmCuPAFAdminState, 1516 efmCuPAFDiscoveryCode, 1517 efmCuPAFRemoteDiscoveryCode, 1518 efmCuAvailableStackTable 1519 } 1520 STATUS current 1521 DESCRIPTION 1522 "A collection of objects that support 1523 optional Aggregation features on EFMCu ports." 1524 ::= { efmCuGroups 2 } 1526 efmCuPmiGroup OBJECT-GROUP 1527 OBJECTS { 1528 efmCuPmiSnrMgn, 1529 efmCuPmiRemoteSnrMgn, 1530 efmCuPmiLineAtn, 1531 efmCuPmiRemoteLineAtn 1532 } 1533 STATUS current 1534 DESCRIPTION 1535 "A collection of objects that provide 1536 required information about a 2BaseTL/10PassTS PMI." 1537 ::= { efmCuGroups 3 } 1539 efmCuPmiAlarmConfGroup OBJECT-GROUP 1540 OBJECTS { 1541 efmCuPmiThreshLineAtn, 1542 efmCuPmiThreshSnrMgn 1543 -- efmCuPmiThreshES, 1544 -- efmCuPmithreshSES, 1545 -- efmCuPmiThreshCRCanomalies, 1546 -- efmCuPmiThreshLOSWS, 1547 -- efmCuPmiThreshUAS 1548 } 1549 STATUS current 1550 DESCRIPTION 1551 "This group supports objects that allow configuration of alarm 1552 thresholds for various performance parameters for 2B/10P PMI." 1553 ::= { efmCuGroups 4 } 1555 efmCuPmiNotificationGroup NOTIFICATION-GROUP 1556 NOTIFICATIONS { 1557 efmCuPmiLineDefect, 1558 efmCuPmiLineAtnCrossing, 1559 efmCuPmiRemoteLineAtnCrossing, 1560 efmCuPmiSnrMgnCrossing, 1561 efmCuPmiRemoteSnrMgnCrossing 1562 -- efmCuPmiPerfES, 1563 -- efmCuPmiPerfSES, 1564 -- efmCuPmiPerfCRCanomalies, 1565 -- efmCuPmiPerfLOSWS, 1566 -- efmCuPmiPerfUAS, 1567 -- efmCuPmiDeviceFault, 1568 -- efmCuPmiLocalPowerLoss 1569 } 1570 STATUS current 1571 DESCRIPTION 1572 "This group supports notifications of significant conditions 1573 associated with EFMCu PMIs." 1574 ::= { efmCuGroups 5 } 1576 efmCu2BGroup OBJECT-GROUP 1577 OBJECTS { 1578 efmCuPmi2BRegion, 1579 efmCuPmi2BPower, 1580 efmCuPmi2BDataRate, 1581 efmCuPmi2BConstellation 1582 } 1583 STATUS current 1584 DESCRIPTION 1585 "A collection of objects that provide 1586 required information about a 2BaseTL PMI." 1587 ::= { efmCuGroups 6 } 1589 efmCu10PGroup OBJECT-GROUP 1590 OBJECTS { 1591 efmCuPmi10PBandplanPSDMaskProfile, 1592 efmCuPmi10PUPBOReferenceProfile, 1593 efmCuPmi10PBandNotchProfiles, 1594 efmCuPmi10PPayloadURateProfile, 1595 efmCuPmi10PPayloadDRateProfile, 1596 efmCuPmi10PElectricalLength 1597 } 1598 STATUS current 1599 DESCRIPTION 1600 "A collection of objects that provide required 1601 information about a 10PassTS PMI." 1602 ::= { efmCuGroups 7 } 1604 -- Compliance Statements 1606 efmCuCompliance MODULE-COMPLIANCE 1607 STATUS current 1608 DESCRIPTION 1609 "The compliance statement for 2BaseTL/10PassTS interfaces. 1610 Compliance with the following external compliance statements 1611 is prerequisite: 1613 MIB Module Compliance Statement 1614 ---------- -------------------- 1615 IF-MIB ifCompliance3 1616 IF-INVERTED-STACK-MIB ifInvCompliance 1617 EtherLike-MIB dot3Compliance2 1618 MAU-MIB mauModIfCompl3" 1620 MODULE -- this module 1621 MANDATORY-GROUPS { 1622 efmCuPortBasicGroup, 1623 efmCuPmiGroup, 1624 efmCuPmiAlarmConfGroup, 1625 efmCuPmiNotificationGroup 1626 } 1628 GROUP efmCuPmi2BGroup 1629 DESCRIPTION 1630 "Support for this group is only required for implementations 1631 supporting 2Base-TL Phy." 1633 GROUP efmCuPmi10PGroup 1634 DESCRIPTION 1635 "Support for this group is only required for implementations 1636 supporting 10Pass-TS Phy." 1638 OBJECT efmCuPortSidesSupported 1639 SYNTAX INTEGER { 1640 subscriber(1), 1641 office(2), 1642 } 1643 DESCRIPTION 1644 "Support for values other than subscriber(1), 1645 or office(2) is not required." 1647 OBJECT efmCuPortSide 1648 MIN-ACCESS read-only 1649 DESCRIPTION 1650 "Write access is not required (needed only for ports 1651 supporting both subscriber and office sides)" 1653 -- EdNote: To be Continued 1655 ::= { efmCuCompliances 1 } 1656 END 1658 5. Security Considerations 1660 There is a number of managed objects defined in this MIB module that 1661 have a MAX-ACCESS clause of read-write or read-create. Most objects 1662 are writeable only when the link is Down. Writing to these objects 1663 can have potentially disruptive effects on network operation, for 1664 example: 1666 o Changing of efmCuPortSide may lead to a potential locking of the 1667 link, as same PHYs of the same sub-type may not be able to 1668 exchange handshake messages. 1670 o Changing of efmCuPAFAdminState to enabled may lead to a potential 1671 locking of the link, if the peer Phy does not support PAF. 1673 o Changing of efmCuPAFDiscoveryCode before the discovery operation 1674 may lead to a wrongful discovery with possile multiple -O ports 1675 connecting to the same -R (both -O ports have the same Discovery 1676 register value) and similar cases. 1678 o Changing any of the efmCuPmd2* or efmCuPmd10P* configuration may 1679 lead to anything from link quality and rate degradation to a 1680 complete disabling of the link. 1682 o Finally activation of a PMI can cause a severe degradation of 1683 service for another EFMCu Phy whose PMI(s) may be affected by the 1684 cross-talk from the newly activated PMI. 1686 The user of this MIB module must therefore be aware that support for 1687 SET operations in a non-secure environment without proper protection 1688 can have a negative effect on network operations. 1690 The readable objects in this MIB module (i.e., those with MAX-ACCESS 1691 other than not-accessible) may be considered sensitive in some 1692 environments since, collectively, they provide information about the 1693 performance of network interfaces and can reveal some aspects of 1694 their configuration. In particular since EFMCu can be carried over 1695 Unshielded Twisted Pair (UTP) voice grade copper in a bundle with 1696 other pairs belonging to another operator/customer, it is 1697 theoretically possible to evasdrop to an EFMCu transmission simply by 1698 "listening" to a cross-talk from an EFMCu pair, especially if the 1699 parameters of the EFMCu link in question are known. In such 1700 environments it is important to control even GET and NOTIFY access to 1701 these objects and possibly even to encrypt their values when sending 1702 them over the network via SNMP. 1704 SNMP versions prior to SNMPv3 did not include adequate security. Even 1705 if the network itself is secure (for example by using IPSec), even 1706 then, there is no control as to who on the secure network is allowed 1707 to access and GET/SET (read/change/create/delete) the objects in this 1708 MIB module. 1710 It is RECOMMENDED that implementers consider the security features as 1711 provided by the SNMPv3 framework (see [RFC3410], section 8), 1712 including full support for the SNMPv3 cryptographic mechanisms (for 1713 authentication and privacy). 1715 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1716 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1717 enable cryptographic security. It is then a customer/operator 1718 responsibility to ensure that the SNMP entity giving access to an 1719 instance of this MIB module is properly configured to give access to 1720 the objects only to those principals (users) that have legitimate 1721 rights to indeed GET or SET (change/create/delete) them. 1723 6. Acknowledgments 1725 Not yet. 1727 Normative References 1729 [802.3ah] IEEE, "Draft amendment to - Information technology - 1730 Telecommunications and information exchange between 1731 systems - Local and metropolitan area networks - Specific 1732 requirements - Part 3: Carrier sense multiple access with 1733 collision detection (CSMA/CD) access method and physical 1734 layer specifications - Media Access Control Parameters, 1735 Physical Layers and Management Parameters for subscriber 1736 access networks", IEEE Draft P802.3ah/D3.0, December 2003. 1738 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1739 Requirement Levels", BCP 14, RFC 2119, March 1997. 1741 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 1742 "Introduction to Version 3 of the Internet-standard 1743 Network Management Framework", RFC 2570, April 1999. 1745 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1746 McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 1747 Management Information Version 2 (SMIv2)", STD 58, RFC 1748 2578, April 1999. 1750 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1751 McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 1752 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 1754 [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, 1755 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1756 April 1999. 1758 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1759 "Introduction and Applicability Statements for 1760 Internet-Standard Management Framework", RFC 3410, 1761 December 2002. 1763 Informative References 1765 [I-D.ietf-adslmib-vdsl] 1766 Ray, B. and R. Abbi, "Definitions of Managed Objects for 1767 Very High Speed Digital Subscriber Lines (VDSL)", 1768 draft-ietf-adslmib-vdsl-12 (work in progress), October 1769 2003. 1771 [I-D.ietf-hubmib-efm-epon-mib] 1772 Khermosh, L., "Managed Objects for the Ethernet Passive 1773 Optical Networks", draft-ietf-hubmib-efm-epon-mib-00 (work 1774 in progress), December 2003. 1776 [I-D.ietf-hubmib-efm-mib] 1777 Squire, M., "Ethernet in the First Mile (EFM) Common MIB", 1778 draft-squire-hubmib-efm-mib-00 (work in progress), October 1779 2003. 1781 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1782 MIB", RFC 2863, June 2000. 1784 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 1785 Extension to the Interfaces Group MIB", RFC 2864, June 1786 2000. 1788 [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for 1789 High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair 1790 High-Speed Digital Subscriber Line (SHDSL) Lines 1791 Processing", RFC 3276, May 2002. 1793 [RFC3635] Flick, J., "Definitions of Managed Objects for the 1794 Ethernet-like Interface Types", RFC 3635, September 2003. 1796 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1797 Medium Attachment Units (MAUs)", RFC 3636, September 2003. 1799 Author's Address 1801 Edward Beili 1802 Actelis Networks 1803 Bazel 25 1804 Petach-Tikva 1805 Israel 1807 Phone: +972-3-924-3491 1808 EMail: edward.beili@actelis.com 1810 Intellectual Property Statement 1812 The IETF takes no position regarding the validity or scope of any 1813 intellectual property or other rights that might be claimed to 1814 pertain to the implementation or use of the technology described in 1815 this document or the extent to which any license under such rights 1816 might or might not be available; neither does it represent that it 1817 has made any effort to identify any such rights. Information on the 1818 IETF's procedures with respect to rights in standards-track and 1819 standards-related documentation can be found in BCP-11. Copies of 1820 claims of rights made available for publication and any assurances of 1821 licenses to be made available, or the result of an attempt made to 1822 obtain a general license or permission for the use of such 1823 proprietary rights by implementors or users of this specification can 1824 be obtained from the IETF Secretariat. 1826 The IETF invites any interested party to bring to its attention any 1827 copyrights, patents or patent applications, or other proprietary 1828 rights which may cover technology that may be required to practice 1829 this standard. Please address the information to the IETF Executive 1830 Director. 1832 Full Copyright Statement 1834 Copyright (C) The Internet Society (2004). All Rights Reserved. 1836 This document and translations of it may be copied and furnished to 1837 others, and derivative works that comment on or otherwise explain it 1838 or assist in its implementation may be prepared, copied, published 1839 and distributed, in whole or in part, without restriction of any 1840 kind, provided that the above copyright notice and this paragraph are 1841 included on all such copies and derivative works. However, this 1842 document itself may not be modified in any way, such as by removing 1843 the copyright notice or references to the Internet Society or other 1844 Internet organizations, except as needed for the purpose of 1845 developing Internet standards in which case the procedures for 1846 copyrights defined in the Internet Standards process must be 1847 followed, or as required to translate it into languages other than 1848 English. 1850 The limited permissions granted above are perpetual and will not be 1851 revoked by the Internet Society or its successors or assignees. 1853 This document and the information contained herein is provided on an 1854 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1855 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1856 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1857 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1858 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1860 Acknowledgment 1862 Funding for the RFC Editor function is currently provided by the 1863 Internet Society.