idnits 2.17.1 draft-ietf-hubmib-efm-cu-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 3388. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3365. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3372. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3378. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to 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 : ---------------------------------------------------------------------------- == There are 29 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. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: These default entries SHALL be created during agent initialization and MUST not be deleted. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BProfileRowStatus. If an active entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST not be removed." INDEX { efmCuPme2BProfileIndex } ::= { efmCuPme2BProfileTable 1 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: These default entries SHALL be created by during agent initialization and MUST not be deleted. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme10PProfileRowStatus. If an 'active' entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST not be removed." INDEX { efmCuPme10PProfileIndex } ::= { efmCuPme10PProfileTable 1 } -- 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 24, 2005) is 6758 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: 'IF-MIB' is mentioned on line 2795, but not defined == Unused Reference: 'I-D.ietf-hubmib-efm-mib' is defined on line 3314, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-epon-mib-03 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-mib-03 == Outdated reference: A later version (-05) exists of draft-ietf-hubmib-rfc3636bis-02 Summary: 4 errors (**), 0 flaws (~~), 13 warnings (==), 7 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 27, 2006 October 24, 2005 6 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB 7 draft-ietf-hubmib-efm-cu-mib-04.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on April 27, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This document defines a Management Information Base (MIB) module for 41 use with network management protocols in TCP/IP based internets. 42 This document proposes an extension to the Ethernet-like Interfaces 43 MIB and MAU MIB modules with a set of objects for managing an 44 Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 45 2BASE-TL, defined in IEEE Std 802.3ah-2004. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 52 3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4 53 3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4 54 3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 6 55 3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 6 56 3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 8 57 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 58 3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9 59 3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 60 3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 10 61 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 62 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 63 4.2. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11 64 4.3. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 65 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . 67 67 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 68 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 70 9.1. Normative References . . . . . . . . . . . . . . . . . . . 69 71 9.2. Informative References . . . . . . . . . . . . . . . . . . 70 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 72 73 Intellectual Property and Copyright Statements . . . . . . . . . . 73 75 1. Introduction 77 New Ethernet-like interfaces have been defined in the Institute of 78 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 79 [802.3ah], a.k.a. Ethernet in the First Mile (EFM). In particular 80 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 81 voice-grade copper pairs, have been specified for the long and short 82 reach respectively. These interfaces, collectively called EFMCu, are 83 based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications 84 and support variable rates and optional Physical Medium Entity (PME) 85 aggregation (a.k.a. multi-pair bonding). 87 2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long 88 single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using 89 5dB target noise margin). 91 10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 92 single copper pair with a mean BER of 10^-7 (using 6dB target noise 93 margin). 95 This memo defines a Management Information Base (MIB) module for use 96 with network management protocols in the Internet community to manage 97 EFMCu interfaces. 99 Note that managed objects for Operation, Administration and 100 Management (OAM) and Ethernet over Passive Optical Networks (EPON) 101 clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf- 102 hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib] 103 respectively. 105 2. The Internet-Standard Management Framework 107 For a detailed overview of the documents that describe the current 108 Internet-Standard Management Framework, please refer to section 7 of 109 RFC 3410 [RFC3410]. 111 Managed objects are accessed via a virtual information store, termed 112 the Management Information Base or MIB. MIB objects are generally 113 accessed through the Simple Network Management Protocol (SNMP). 114 Objects in the MIB are defined using the mechanisms defined in the 115 Structure of Management Information (SMI). This memo specifies a MIB 116 module that is compliant to the SMIv2, which is described in STD 58, 117 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 118 [RFC2580]. 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 122 document are to be interpreted as described in RFC 2119 [RFC2119]. 124 3. Relation to other MIB modules 126 This section outlines the relationship of this MIB with other MIB 127 modules described in the relevant RFCs. Specifically, Interfaces 128 Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), 129 SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are 130 discussed. 132 3.1. Relation to Interfaces Group MIB module 134 2BASE-TL and 10PASS-TS PHY's specified in this MIB module are stacked 135 Ethernet interfaces and as such are managed using generic interface 136 management objects defined in the IF-MIB [RFC2863]. The stack 137 management is done via the ifStackTable, as defined in the IF-MIB 138 [RFC2863] and ifInvStackTable, as defined in the IF-INVERTED-STACK- 139 MIB [RFC2864]. 141 3.1.1. Layering Model 143 An EFMCu interface can aggregate up to 32 Physical Medium Entity 144 (PME) sub-layer devices (modems), using so called PME Aggregation 145 Function (PAF). 147 A generic EFMCu device can have a number of Physical Coding Sublayer 148 (PCS) ports, connected to a MAC via Medium Independent Interface 149 (MII) at the upper layer, and cross-connected to a number of 150 underlying PMEs, with a single PCS per PME relationship, see clause 151 61.1 of [802.3ah] for more details. 153 Each PME in the aggregated EFMCu port is represented in the Interface 154 table (ifTable) as a separate port with ifType of shdsl(169) for 155 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 156 [IANAifType-MIB]. 158 ifSpeed for each PME SHALL return the actual data bitrate of the 159 active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero 160 value SHALL be returned when PME is initializing or down. 162 The ifSpeed of the PCS is the sum of the current operating data rates 163 of all PMEs in the aggregation group, without the 64/65B 164 encapsulation overhead and PAF overhead, but acounting for the Inter- 165 Frame Gaps (IFG). 167 When using the stated definition of ifSpeed for the PCS, there would 168 be no frame loss in the following configuration (the test-sets are 169 configured to generate 100% of back to back traffic, i.e. minimal 170 IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM 171 interfaces are obviously aggregated): 173 [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] 174 ifSpeed= 10Mbps 10Mbps 10Mbps 176 [testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset] 177 ifSpeed= 100Mbps 100Mbps 100Mbps 179 Figure 1: Example configuration with no frame loss 181 The following figure shows the layering diagram and corresponding use 182 of ifTable and ifMauTable: 184 _________________________ _ 185 | LLC | | 186 +-------------------------+ | 1 ifEntry 187 | MAC | | ifType: ethernetCsmacd(6) 188 +-------------------------+ > ifMauEntry 189 | Reconsiliation | | ifMauType: dot3MauType2BaseTL or 190 +-------------------------+ | dot3MauType10PassTS 191 | PCS | | 192 +-------------+---+-------+ + 193 | TC \ | | | | 194 +-----\ | | | | 195 | PMA > PME 1 |...| PME N | > N ifEntry (N=1..32) 196 +-----/ | | | | ifType: shdsl(169) or vdsl(97) 197 | PMD/ | | | | 198 -------------+---+------- - 200 Figure 2: Use of ifTable and ifMauTable for EFMCu ports 202 The ifStackTable is indexed by the ifIndex values of the aggregated 203 EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a 204 Network Management application to determine which PMEs are connected 205 to a particular PCS and change connections (if supported by the 206 application). The ifInvStackTable, being an inverted version of the 207 ifStackTable, provides an efficient means for a Network Management 208 application to read a subset of the ifStackTable and thereby 209 determine which PCS runs on top of a particular PME. 211 A new table ifAvailableStackTable defined in this MIB module, 212 specifies for each PCS a list of PMEs, which can possibly be cross- 213 connected to that PCS, determined by the cross-connect capability of 214 the device. This table, modeled after ifStackTable, is read only, 215 reflecting current cross-connect capability, which can be dynamic in 216 some implementations (e.g. if PMEs are located on a pluggable module 217 and the module is pulled out). Note that PME availability per PCS, 218 described by ifAvailableStackTable, can be constrained by other 219 parameters, for example by aggregation capacity of a PCS or by the 220 PME in question being already connected to another PCS. So, in order 221 to ensure that a particular PME can be connected to the PCS, all 222 respective parameters (e.g. ifAvailableStackTable, ifStackTable and 223 efmCuPAFCapacity) SHALL be inspected. 225 3.1.2. PME Aggregation Function (PAF) 227 The PME Aggregation Function (PAF) allows a number of PMEs to be 228 aggregated onto a PCS port, by fragmenting the Ethernet frames, 229 transmitting the fragments over multiple PMEs and assembling the 230 original frames at the remote port. PAF is OPTIONAL, meaning that a 231 device with a single PME MAY perform fragmentation and re-assembly if 232 this function is supported by the device. Note however that the 233 agent is REQUIRED to report on the PAF capability for all EFMCu ports 234 (2BASE-TL and 10PASS-TS). 236 This MIB module allows a Network Management application to query PAF 237 capability and enable/disable it if supported. Note that enabling 238 PAF effectively turns on fragmentation and re-assembly, even on a 239 single-PME port. 241 3.1.3. Discovery Operation 243 The EFMCu ports may optionally support discovery operation, whereby 244 PMEs, during initialization, exchange information about their 245 respective aggregation groups (PCS). This information can then be 246 used to detect copper missconnections or for an automatic assignment 247 of the local PMEs into aggregation groups instead of fixed pre- 248 configuration. 250 This MIB module allows a Network Management application to control 251 EFM Discovery mechanism and query its results. Note that the 252 Discovery mechanism can work only if PAF is supported and enabled. 254 Two tables are used by Discovery mechanism: ifStackTable and 255 ifAvailableStackTable defined. The following pseudo-code defines an 256 example of Discovery and automatic PME assignment for a generic PAF 257 enabled multi-PCS EFMCu device, located at Central Office (CO), using 258 objects defined in this MIB module. [Note that automatic PME 259 assignment is only shown here for the purposes of the example. Fixed 260 PME pre-assignment, manual assignment or auto-assignment by an 261 alternative internal algorithm may be chosen by a particular 262 implementation]: 264 FOREACH pcs[i] IN co_device 265 { // Discover only on PAF enabled ports with room for more PMEs 266 IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) 267 { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS 268 // go over all currently disconnected PMEs, which can 269 // pottentially be connected to PCS[i] 270 FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] AND 271 NOT IN ifInvStackTable[pme[j]] // unassigned 272 { pme[j].RemoteDiscoveryCode = dc; // Set if Clear 273 r = pme[j].RemoteDiscoveryCode; // Get 274 IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) 275 { // Remote CPE connected via PME[j] is/was a peer for 276 // PCS[i]. Connect this PME to the PCS (there's room) 277 ADD pme[j] TO ifStackTable[pcs[i]]; 278 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 279 // Discover all other currently disconnected PMEs, 280 // attached to the same CPE and connect them to the PCS 281 // provided there is enough room for more PMEs. 282 FOREACH pme[k] IN ifAvailableStackTable[pcs[i]] and 283 NOT IN ifInvStackTable[pme[k]] 284 { r = pme[k].RemoteDiscoveryCode; // Get 285 IF ( r == dc AND 286 pcs[i].NumPMEs < pcs[i].PAFCapacity) 287 { ADD pme[k] TO ifStackTable[pcs[i]]; 288 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 289 } 290 } 291 } 292 // Discovered all PMEs which lead to the same CPE and 293 // connected them to PCS[i]. Go to the next PCS. 294 BREAK; 295 } 296 } 297 } 299 The SNMP Agent builds efmCuStackTable according to the information 300 contained in the Clause 45 PME_Available_register (see [802.3ah] 301 61.1.5.3 and 45.2.3.20). 303 Adding a PME to the ifStackTable row for a specific PCS, involves 304 actual connection of the PME to the PCS, which can be done by 305 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 306 and 45.2.3.21). 308 Note that PCS port does not have to be operationally 'down' for the 309 connection to succeed. In fact, a dynamic PME addition (and removal) 310 MAY be implemented whith an available PME being initialized first (by 311 setting its ifAdminStatus to 'up') and then added to an operationally 312 'up' PCS port, by modifying a respective ifStackTable entry. 314 It is RECOMMENDED that a removal of the last operationally 'up' PME 315 from an operationally 'up' PCS would be rejected by the 316 implementation, as this action would completely drop the link. 318 3.1.4. EFMCu ports initialization 320 EFMCu ports being built on top of xDSL technology, require a lengthy 321 initialization or 'training' process, before any data can pass. 322 During this initialization both ends of a link (peers) work 323 cooperatively to achieve required data rate on a particular copper 324 pair. Sometimes, when the copper line is too long or the noise 325 environment on the line is too high, that 'training' process may fail 326 to achieve a specific target rate with required characteristics. 328 The ifAdminStatus object from the IF-MIB, controls the desired state 329 of a PCS and a PME port. Setting this object to 'up' instructs a 330 particular PCS or PME to start initialization process, which may take 331 tens of seconds for EFMCu ports, especially if PAF is involved. The 332 ifOperStatus object shows the operational state of an interface 333 (extended by efmCuPmeOperStatus defined in this MIB module for PME 334 interfaces). 336 A disconnected PME may be initialized by changing the ifAdminState 337 from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS 338 initializes all PMEs connected to that particular PCS. Note that in 339 case of PAF some interfaces may fail to initialize while others 340 succeed. The PCS is considered operationally 'up' if at least one 341 PME aggregated by its PAF is operationally 'up'. When all PMEs 342 connected to the PCS are 'down' the PCS SHALL be considered 343 operationally 'lowerLayerDown'. The PCS SHALL be considered 344 operationally 'notPresent' if it is not connected to any PME. The 345 PCS/PME interface SHALL remain operationally 'down' during 346 initialization. 348 The efmCuPmeOperStatus defined in this MIB module expands PME's 349 ifOperStatus value of 'down' to 'downReady', 'downNotReady' and 350 'init' values, indicating various EFMCu PME specific states. 352 3.1.5. Usage of ifTable 354 Both PME and PCS interfaces of the EFMCu PHY are managed using 355 interface specific management objects defined in this MIB module and 356 generic interface objects from the ifTable of IF-MIB, with all 357 management table entries referenced by the interface index ifIndex. 359 The following table summarizes EFMCu specific interpretations for 360 some of the ifTable objects specified by the mandatory 361 ifGeneralInformationGroup: 363 +---------------+---------------------------------------------------+ 364 | IF-MIB object | EFMCu interpretation | 365 +---------------+---------------------------------------------------+ 366 | ifIndex | Interface index. Note that each PME and each PCS | 367 | | in the EFMCu PHY MUST have a unique index, as | 368 | | there some PCS and PME specific attributes | 369 | | accessible only on the PCS or PME level. | 370 | ifType | ethernetCsmacd(6) for PCS, shdsl(169) for | 371 | | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME | 372 | ifSpeed | Operating data rate for the PME. For the PCS it | 373 | | is the sum of the current operating data rates of | 374 | | all PMEs in the aggregation group, without the | 375 | | 64/65B encapsulation overhead and PAF overhead, | 376 | | but acounting for the Inter-Frame Gaps (IFG) | 377 | ifAdminStatus | Setting this object to 'up' instructs a | 378 | | particular PCS (with all PMEs connected to it) or | 379 | | PME to start initialization process | 380 | ifOperStatus | efmCuPmeOperStatus supplements the 'down' value | 381 | | of ifOperStatus for PMEs. | 382 +---------------+---------------------------------------------------+ 384 Table 1 386 3.2. Relation to SHDSL MIB module 388 G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are 389 described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note 390 that not all attributes of G.SHDSL modems reflected in HDSL2-SHDSL- 391 LINE-MIB have adequate management objects (Clause 30 attributes and 392 Clause 45 registers) in the EFM standard. 394 Because of these differences and for the purposes of simplicity, 395 unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs 396 and name consistency (e.g. prefixing the 2BASE-TL PME related objects 397 with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to 398 reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant 399 objects in this MIB module. 401 However, if some functionality, not available in this MIB module, is 402 required and supported by the PME, e.g. performance monitoring, 403 relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for 404 PMEs of 2BASE-TL subtype. 406 3.3. Relation to VDSL MIB module 408 VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, 409 are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all 410 attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have 411 adequate management objects (Clause 30 attributes and Clause 45 412 registers) in the EFM standard. 414 Because of these differences and for the purposes of simplicity, 415 unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs 416 and name consistency, it was decided not to reference VDSL-LINE-EXT- 417 MCM-MIB objects, but define all the relevant objects in this MIB 418 module. 420 However, if some functionality, not available in this MIB module, is 421 required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB 422 groups MAY be included and applied for PMEs of 10PASS-TS subtype. 424 3.4. Relation to Ethernet-Like and MAU MIB modules 426 The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf- 427 hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. 429 Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and 430 corresponding bit definitions of ifMauTypeListBits 431 (IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB 432 [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: 434 o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU 436 o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU 438 As an EtherLike interface every EFMCu port (an ifEntry representing a 439 consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType 440 of ethernetCsmacd(6). While most of the MAU characteristics are not 441 applicable to the EFMCu ports (no auto-negotiation, media available, 442 false carriers or jabber), they SHALL return an appropriate ifMauType 443 (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the 444 management software to look in the EFM-CU-MIB for the desired 445 information. For example the information on the particular EFMCu 446 flavor that an EFMCu port is running is available from 447 efmCuOperSubType, defined in this MIB module. 449 Since EFMCu PMEs are not EtherLike interfaces, they cannot be 450 instantiated as MAU interface objects. 452 4. MIB Structure 454 4.1. Overview 456 The main management objects defined in this MIB module are split into 457 2 groups: 459 o efmCuPort - containing objects for configuration, capabilities, 460 status and notifications, common to all EFMCu PHYs. 462 o efmCuPme - containing objects for configuration, capabilities, 463 status and notifications of EFMCu PMEs. 465 In addition the ifAvailableStackTable is defined at the same level. 467 The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P 468 groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS 469 PMEs respectively, as well as PME specific status information. 471 4.2. PME Profiles 473 Since a managed node can have a large number of EFMCu PHYs, 474 provisioning every parameter on every EFMCu PHY may become 475 burdensome. Moreover, most PMEs are provisioned identically with the 476 same set of parameters. To simplify the provisioning process, this 477 MIB module makes use of configuration profiles, similar to HDSL2- 478 SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set of 479 parameters, used either for configuration or representation of a PME. 480 The same profile can be shared by multiple PME ports, using the same 481 configuration. 483 The PME profiles are defined in efmCuPme2BProfileTable and 484 efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. 485 There are 12 predefined standard profiles for 2BASE-TL and 22 486 standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for 487 rapid provisioning of EFMCu PHYs in most scenarios. In addition this 488 MIB defines two additional predefined profiles for "best-effort" 489 provisioning of 2BASE-TL PMEs. An ability to define new 490 configuration profiles is also provided to allow for EFMCu deployment 491 tailored to specific copper environment and spectral regulations. 493 A specific configuration or administrative profile is assigned to a 494 specific PME via efmCuPmeAdminProfile object. If 495 efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the 496 PCS port, connected to the PME, determines the configuration profile 497 (or a list of possible profiles) for that PME. This mechanism allows 498 to specify a common profile(s) for all PMEs connected to the PCS 499 port, with an ability to change individual PME profiles by setting 500 efmCuPmeAdminProfile object, which overwrites profile set by 501 efmCuAdminProfile. 503 A current operating PME profile is pointed to by efmCuPmeOperProfile 504 object. Note that this profile entry, can be created automatically, 505 to reflect achieved parameters in adaptive (not fixed) 506 initialization. 508 4.3. Mapping of IEEE 802.3ah Managed Objects 510 This section contains the mapping between managed objects 511 (attributes) defined in [802.3ah] Clause 30, and managed objects 512 defined in this document and in associated MIB modules, i.e., the IF- 513 MIB [RFC2863]. 515 Note that majority of the objects defined in this MIB module do not 516 have direct counterparts in Clause 30 and instead refer to Clause 45 517 registers. 519 +---------------------------------+---------------------------------+ 520 | IEEE 802.3 Managed Object | Corresponding SNMP Object | 521 +---------------------------------+---------------------------------+ 522 | oPAF - Basic Package | | 523 | (Mandatory) | | 524 | aPAFID | ifIndex (IF-MIB) | 525 | aPhyEnd | efmCuPhySide | 526 | aPHYCurrentStatus | efmCuStatus | 527 | aPAFSupported | efmCuPAFSupported | 528 | oPAF - PME Aggregation Package | | 529 | (Optional) | | 530 | aPAFAdminState | efmCuPAFAdminState | 531 | aLocalPAFCapacity | efmCuPAFCapacity | 532 | aLocalPMEAvailable | ifAvailableStackTable | 533 | aLocalPMEAggregate | ifStackTable (IF-MIB) | 534 | aRemotePAFSupported | efmCuRemotePAFSupported | 535 | aRemotePAFCapacity | efmCuRemotePAFCapacity | 536 | aRemotePMEAggregate | | 537 | oPME - 10P/2B Package | | 538 | (Mandatory) | | 539 | aPMEID | ifIndex (IF-MIB) | 540 | aPMEAdminState | ifAdminState (IF-MIB) | 541 | aPMEStatus | efmCuPmeStatus | 542 | aPMESNRMgn | efmCuPmeSnrMgn | 543 | aTCCodingViolations | efmCuPmeTCCodingErrors | 544 | aTCCRCErrors | efmCuPmeTCCrcErrors | 545 | aProfileSelect | efmCuAdminProfile, | 546 | | efmCuPmeAdminProfile | 547 | aOperatingProfile | efmCuPmeOperProfile | 548 | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | 549 | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | 550 +---------------------------------+---------------------------------+ 552 Table 2 554 5. Definitions 556 EFM-CU-MIB DEFINITIONS ::= BEGIN 558 IMPORTS 559 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, 560 Unsigned32, Counter32, mib-2 561 FROM SNMPv2-SMI -- RFC 2578 562 TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress 563 FROM SNMPv2-TC -- RFC 2579 564 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 565 FROM SNMPv2-CONF -- RFC 2580] 566 SnmpAdminString 567 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 568 ifIndex, ifSpeed, InterfaceIndex 569 FROM IF-MIB -- RFC 2863 570 ; 572 efmCuMIB MODULE-IDENTITY 573 LAST-UPDATED "200510240000Z" -- October 24, 2005 574 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" 575 CONTACT-INFO 576 "WG charter: 577 http://www.ietf.org/html.charters/hubmib-charter.html 579 Mailing Lists: 580 General Discussion: hubmib@ietf.org 581 To Subscribe: hubmib-request@ietf.org 582 In Body: subscribe your_email_address 584 Chair: Dan Romascanu 585 Postal: Avaya 586 Atidim Technology Park, Bldg. 3 587 Tel Aviv 61131 588 Israel 589 Tel: +972 3 645 8414 590 E-mail: dromasca@avaya.com 592 Editor: Edward Beili 593 Postal: Actelis Networks Inc. 595 25 Bazel St., P.O.B. 10173 596 Petach-Tikva 10173 597 Israel 598 Tel: +972-3-924-3491 599 E-mail: edward.beili@actelis.com" 601 DESCRIPTION 602 "The objects in this MIB module are used to manage 603 the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 604 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004. 606 The following reference is used throughout this MIB module: 608 [802.3ah] refers to: 609 IEEE Std 802.3ah-2004: 'IEEE Standard for Information 610 technology - Telecommunications and information exchange 611 between systems - Local and metropolitan area networks - 612 Specific requirements - 613 Part 3: Carrier Sense Multiple Access with Collision 614 Detection (CSMA/CD) Access Method and Physical Layer 615 Specifications - 616 Amendment: Media Access Control Parameters, Physical 617 Layers and Management Parameters for Subscriber Access 618 Networks', 07 September 2004. 620 Of particular interest are Clause 61, 'Physical Coding 621 Sublayer (PCS) and common specifications, type 10PASS-TS and 622 type 2BASE-TL', Clause 30, 'Management', Clause 45, 623 'Management Data Input/Output (MDIO) Interface', Annex 62A, 624 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 625 2BASE-TL'. 627 Naming Conventions: 628 Atn - Attenuation 629 CO - Central Office 630 CPE - Customer Premises Equipment 631 EFM - Ethernet in the First Mile 632 EFMCu - EFM Copper 633 MDIO - Management Data Input/Output 634 Mgn - Margin 635 PAF - PME Aggregation Function 636 PCS - Physical Coding Sublayer 637 PMD - Physical Medium Dependent 638 PME - Physical Medium Entity 639 PSD - Power Spectral Density 640 SNR - Signal to Noise Ratio 641 TCPAM - Trellis Coded Pulse Amplitude Modulation 643 Copyright (C) The Internet Society (2004). This version 644 of this MIB module is part of RFC XXXX; see the RFC 645 itself for full legal notices." 647 REVISION "200510240000Z" -- October 24, 2005 648 DESCRIPTION "Initial version, published as RFC XXXX." 650 -- EdNote: Replace XXXX with the actual RFC number & 651 -- remove this note 653 ::= { mib-2 YYY } 655 -- EdNote: Replace YYY with a real OID once it is 656 -- allocated & remove this note. 658 -- Sections of the module 660 efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } 662 efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } 664 -- Groups in the module 666 efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } 668 efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } 670 -- Textual Conventions 672 ProfileIndex ::= TEXTUAL-CONVENTION 673 DISPLAY-HINT "d" 674 STATUS current 675 DESCRIPTION 676 "A unique value, greater than zero, for each PME configuration 677 profile in the managed EFMCu port. It is recommended that 678 values are assigned contiguously starting from 1. The value 679 for each profile must remain constant at least from one 680 re-initialization of the entity's network management system 681 to the next re-initialization." 682 SYNTAX Unsigned32 (1..255) 684 ProfileIndexOrZero ::= TEXTUAL-CONVENTION 685 DISPLAY-HINT "d" 686 STATUS current 687 DESCRIPTION 688 "This textual convention is an extension of the ProfileIndex 689 convention. The latter defines a greater than zero value used 690 to identify a PME profile in the managed EFMCu port. This 691 extension permits the additional value of zero. The value of 692 zero is object-specific and must therefore be defined as part 693 of the description of any object which uses this syntax. 694 Examples of the usage of zero value migh include situations 695 where current operational profile is unknown." 696 SYNTAX Unsigned32 (0..255) 698 ProfileIndexList ::= TEXTUAL-CONVENTION 699 DISPLAY-HINT "1d:" 700 STATUS current 701 DESCRIPTION 702 "Represents a list of up to 6 ProfileIndex's. 703 The ProfileIndex textual convention defines a greater than 704 zero value used to identify a PME profile in the managed EFMCu 705 port. The value of this object is a concatenation of one or 706 more (up to 6) octets, where each octet contains an 8-bit 707 ProfileIndex value. 708 The ProfileIndexList specifies a list of alternative 709 profiles, any of which can be chosen for configuration of an 710 PME." 711 SYNTAX OCTET STRING (SIZE(1..6)) 713 TruthValueOrUnknown ::= TEXTUAL-CONVENTION 714 STATUS current 715 DESCRIPTION 716 "This textual convention is an extension of the TruthValue 717 convention. The latter defines a boolean value with 718 possible values of true(1) and false(2). This 719 extension permits the additional value of unknown(0), which 720 can be returned as a result of GET operation, when an exact 721 true or false value of the object cannot be determined." 722 SYNTAX INTEGER { unknown(0), true(1), false(2) } 724 -- Port Notifications Group 726 efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } 728 efmCuLowBandwidth NOTIFICATION-TYPE 729 OBJECTS { 730 -- ifIndex is not needed here since we are under specific PCS 731 ifSpeed, 732 efmCuThreshLowBandwidth 733 } 734 STATUS current 735 DESCRIPTION 736 "This notification indicates that EFMCu port's data rate 737 reached or dropped below a Low Bandwidth Threshold 738 (i.e. bandwidth degradation happening in case of PAF when one 739 or more PMEs drop)." 740 -- EdNote: add throttling limitations here 741 ::= { efmCuPortNotifications 1 } 743 -- PCS Port group 745 efmCuPortConfTable OBJECT-TYPE 746 SYNTAX SEQUENCE OF EfmCuPortConfEntry 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) 751 Ports. Entries in this table MUST be maintained in a 752 persistent manner" 753 ::= { efmCuPort 1 } 755 efmCuPortConfEntry OBJECT-TYPE 756 SYNTAX EfmCuPortConfEntry 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "An entry in the EFMCu Port Configuration table. 761 Each entry represents an EFMCu port indexed by the ifIndex. 762 Note that an EFMCu PCS port runs on top of a single 763 or multiple PME port(s), which are also indexed by ifIndex." 764 INDEX { ifIndex } 765 ::= { efmCuPortConfTable 1 } 767 EfmCuPortConfEntry ::= 768 SEQUENCE { 769 efmCuPAFAdminState INTEGER, 770 efmCuPAFDiscoveryCode PhysAddress, 771 efmCuAdminProfile ProfileIndexList, 772 efmCuTargetDataRate Unsigned32, 773 efmCuTargetSnrMgn Unsigned32, 774 efmCuThreshLowBandwidth Unsigned32, 775 efmCuLowBandwidthEnable TruthValue 776 } 778 efmCuPAFAdminState OBJECT-TYPE 779 SYNTAX INTEGER { 780 enabled(1), 781 disabled(2) 782 } 783 MAX-ACCESS read-write 784 STATUS current 785 DESCRIPTION 786 "Administrative (desired) state of the PAF of the EFMCu port 787 (PCS). 788 When 'disabled', PME Aggregation will not be performed by the 789 PCS. No more than a single PME can be assigned to this PCS in 790 this case. 791 When 'enabled', PAF will be performed by the PCS when the link 792 is Up, even on a single attached PME, if PAF is supported. 794 PCS ports incapable of supporting PAF SHALL return a value of 795 'disabled'. Attempts to 'enable' such ports SHALL be ignored. 797 PAF 'enabled' port with multiple PMEs assigned cannot be 798 'disabled'. Attempts to 'disable' such port SHALL be rejected, 799 until at most one PME is left assigned. 801 Changing PAFAdminState is a traffic disruptive operation and 802 as such SHALL be done when the link is Down. Attempts to 803 change this object SHALL be ignored if the link is Up or 804 Initializing. 806 This object maps to the Clause 30 attribute aPAFAdminState. 808 If a Clause 45 MDIO Interface to the PCS is present, then this 809 object maps to the PAF enable bit in the 10P/2B PCS control 810 register. 812 This object MUST be maintained in a persistent manner." 813 REFERENCE 814 "[802.3ah] 61.2.2, 45.2.3.18.3" 815 ::= { efmCuPortConfEntry 1 } 817 efmCuPAFDiscoveryCode OBJECT-TYPE 818 SYNTAX PhysAddress 819 MAX-ACCESS read-write 820 STATUS current 821 DESCRIPTION 822 "PAF Discovery Code of the EFMCu port (PCS). 823 A unique 6 Byte long code used by the Discovery function, when 824 PAF is supported. 825 PCS ports incapable of supporting PAF SHALL return a value of 826 all zeroes. Attempts to change this object SHALL be ignored in 827 this case. 828 This object MUST be instantiated for the -O subtype PCS before 829 writing operations on the efmCuPAFRemoteDiscoveryCode 830 (Set_if_Clear and Clear_if_Same) are performed by PMEs 831 associated with the PCS. 832 The value of this object is read-only for -R port subtypes. 833 The initial value of this object for -R ports after reset 834 is 0. This value may be changed as a result of writing 835 operation on efmCuPAFRemoteDiscoveryCode variable of remote 836 PME of -O subtype, connected to one of the local PMEs 837 associated with the PCS. 839 Discovery MUST be performed when the link is Down. 840 Attempts to change this object MUST be rejected with the error 841 inconsistentValue if the link is Up or Initializing. 843 The PAF Discovery code maps to the local Discovery code 844 variable in PAF (note that it does not have a corresponding 845 Clause 45 register)" 846 REFERENCE 847 "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1" 848 ::= { efmCuPortConfEntry 2 } 850 efmCuAdminProfile OBJECT-TYPE 851 SYNTAX ProfileIndexList 852 MAX-ACCESS read-write 853 STATUS current 854 DESCRIPTION 855 "Desired configuration Profile(s), common for all PMEs in the 856 EFMCu port. This object is a list of pointers to entries in 857 either efmCuPme2BProfileTable or 858 efmCuPme10PProfileTable, depending on the current 859 operating SubType of the EFMCu port as indicated by 860 efmCuPortSide. 861 The value of this object is a list of up to 6 indices of 862 Profiles. If this list consists of a single Profile index, 863 then all PMEs assigned to this EFMCu port SHALL be configured 864 according to the Profile referenced by that index, unless it 865 is overwritten by corresponding non-zero efmCuPmeAdminProfile, 866 which takes precedence over efmCuAdminProfile. 867 The list, consisting of more than one index, allows each PME 868 in the port to be configured according to any Profile 869 specified in the list. 870 By default this object has a value of 0x01, referencing 1st 871 entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. 873 This object is writable and readable for the -O subtype 874 (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for 875 the -R subtype (2BaseTL-R or 10PassTS-R) ports. 877 Note that current operational Profile value is available via 878 efmCuPmeOperProfile object. 880 Modification of this object must be performed when the link is 881 Down. Attempts to change this object MUST be rejected, if the 882 link is Up or Initializing. 884 Attempts to set this object to a list with a member 885 value, that is not the value of the index for an active entry 886 in the corresponding profile table, MUST be rejected. 888 This object MUST be maintained in a persistent manner." 889 REFERENCE 890 "[802.3ah] 30.11.2.1.6" 891 DEFVAL { '01'H } 892 ::= { efmCuPortConfEntry 3 } 894 efmCuTargetDataRate OBJECT-TYPE 895 SYNTAX Unsigned32(1..100000|999999) 896 UNITS "Kbps" 897 MAX-ACCESS read-write 898 STATUS current 899 DESCRIPTION 900 "Desired EFMCu port 'net' (as seen across MII) Data Rate in 901 Kbps, to be achieved during initialization, under spectral 902 restrictions placed on each PME via efmCuAdminProfile or 903 efmCuPmeAdminProfile, with the desired SNR Margin specified by 904 efmCuTargetSnrMgn. 905 In case of PAF, this object represents a sum of individual PME 906 data rates, modified to compensate for fragmentation and 907 64/65B framing overhead (e.g. target data rate of 10Mbps 908 shall allow lossless transmission of full-duplex 10Mbps 909 Ethernet frame stream with minimal inter-frame gap). 911 The value is limited above by 100Mbps as this is the max 912 burst rate across MII for EFMCu ports. 914 The value between 1 and 100000 indicates that the total data 915 rate (ifSpeed) of the EFMCu port after initialization should 916 be equal to the target data rate or less, if the target data 917 rate cannot be achieved under spectral restrictions specified 918 by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR 919 margin. In case the copper environment allows to achieve 920 higher total data rate than specified by the target, the 921 excess capability SHALL be converted to additional SNR margin 922 and spread evenly across all active PMEs assigned to the (PCS) 923 port. 925 The value of 999999 means that the target data rate is not 926 fixed and should be set to the maximum attainable rate during 927 initialization (Best Effort), under specified spectral 928 restrictions and with desired SNR Margin. 930 This object is read-write for the -O subtype EFMCu ports 931 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 933 Changing of the Target Data Rate MUST be performed when the 934 link is Down. Attempts to change this object MUST be rejected 935 with the error inconsistentValue, if the link is Up or 936 Initializing. 938 Note that current Data Rate of the EFMCu port is represented 939 by ifSpeed object of IF-MIB. 941 This object MUST be maintained in a persistent manner." 942 ::= { efmCuPortConfEntry 4 } 944 efmCuTargetSnrMgn OBJECT-TYPE 945 SYNTAX Unsigned32(0..21) 946 UNITS "dB" 947 MAX-ACCESS read-write 948 STATUS current 949 DESCRIPTION 950 "Desired EFMCu port SNR Margin to be achieved on all PMEs 951 assigned to the port, during initializiation. (The SNR margin 952 is the difference between the desired SNR and the actual SNR). 954 Note that 802.3ah recommends using default Target SNR Margin 955 of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order 956 to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA 957 service interface. 959 This object is read-write for the -O subtype EFMCu ports 960 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 962 Changing of the Target SNR Margin MUST be performed when the 963 link is Down. Attempts to change this object MUST be rejected 964 with the error inconsistentValue, if the link is Up or 965 Initializing. 967 Note that current SNR Margin of the PMEs comprising the EFMCu 968 port is represented by efmCuPmeSnrMgn. 970 This object MUST be maintained in a persistent manner." 971 REFERENCE 972 "[802.3ah] 61.1.2" 973 ::= { efmCuPortConfEntry 5 } 975 efmCuThreshLowBandwidth OBJECT-TYPE 976 SYNTAX Unsigned32(400..100000) 977 UNITS "Kbps" 978 MAX-ACCESS read-write 979 STATUS current 980 DESCRIPTION 981 "This object configures the EFMCu port Low Bandwidth alarm 982 threshold. When the current value of ifSpeed for this port 983 reaches or drops below this threshold, an 984 efmCuLowBandwidth notification MAY be generated if enabled by 985 efmCuLowBandwidthEnable. 987 This object is read-write for the -O subtype EFMCu ports 988 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 990 This object MUST be maintained in a persistent manner." 991 ::= { efmCuPortConfEntry 6 } 993 efmCuLowBandwidthEnable OBJECT-TYPE 994 SYNTAX TruthValue 995 MAX-ACCESS read-write 996 STATUS current 997 DESCRIPTION 998 "Indicates whether efmCuLowBandwidth notifications should be 999 generated for this interface. 1001 Value of true(1) indicates that efmCuLowBandwidth 1002 notification is enabled. Value of false(2) indicates that 1003 the notification is disabled. 1005 This object MUST be maintained in a persistent manner." 1006 ::= { efmCuPortConfEntry 7 } 1008 efmCuPortCapabilityTable OBJECT-TYPE 1009 SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry 1010 MAX-ACCESS not-accessible 1011 STATUS current 1012 DESCRIPTION 1013 "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) 1014 Ports. Entries in this table MUST be maintained in a 1015 persistent manner" 1016 ::= { efmCuPort 2 } 1018 efmCuPortCapabilityEntry OBJECT-TYPE 1019 SYNTAX EfmCuPortCapabilityEntry 1020 MAX-ACCESS not-accessible 1021 STATUS current 1022 DESCRIPTION 1023 "An entry in the EFMCu Port Capability table. 1024 Each entry represents an EFMCu port indexed by the ifIndex. 1025 Note that an EFMCu PCS port runs on top of a single 1026 or multiple PME port(s), which are also indexed by ifIndex." 1027 INDEX { ifIndex } 1028 ::= { efmCuPortCapabilityTable 1 } 1030 EfmCuPortCapabilityEntry ::= 1031 SEQUENCE { 1032 efmCuPAFSupported TruthValue, 1033 efmCuPeerPAFSupported TruthValueOrUnknown, 1034 efmCuPAFCapacity Unsigned32, 1035 efmCuPeerPAFCapacity Unsigned32 1036 } 1038 efmCuPAFSupported OBJECT-TYPE 1039 SYNTAX TruthValue 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "PME Aggregation Function (PAF) Capability of the EFMCu port 1044 (PCS). 1045 This object has a value of true(1) when the PCS can perform 1046 PME aggregation on the available PMEs. 1047 Ports incapable of PAF SHALL return a value of false(2). 1049 This object maps to the Clause 30 attribute aPAFSupported. 1051 If a Clause 45 MDIO Interface to the PCS is present, 1052 then this object maps to the PAF available bit in the 1053 10P/2B capability register." 1054 REFERENCE 1055 "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1" 1056 ::= { efmCuPortCapabilityEntry 1 } 1058 efmCuPeerPAFSupported OBJECT-TYPE 1059 SYNTAX TruthValueOrUnknown 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "PME Aggregation Function (PAF) Capability of the EFMCu port 1064 (PCS) link partner. 1065 This object has a value of true(1) when the remote PCS can 1066 perform PME aggregation on its available PMEs. 1067 Ports whose peers are incapable of PAF, SHALL return a value 1068 of false(2). 1069 Ports whose peers cannot be reached because of the link 1070 state, SHALL return a value if unknown(0). 1072 This object maps to the Clause 30 attribute 1073 aRemotePAFSupported. 1075 If a Clause 45 MDIO Interface to the PCS is present, then 1076 this object maps to the Remote PAF supported bit in the 1077 10P/2B capability register." 1078 REFERENCE 1079 "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" 1080 ::= { efmCuPortCapabilityEntry 2 } 1082 efmCuPAFCapacity OBJECT-TYPE 1083 SYNTAX Unsigned32 (1..32) 1084 MAX-ACCESS read-only 1085 STATUS current 1086 DESCRIPTION 1087 "Number of PMEs that can be aggregated by the local PAF. 1088 The number of PMEs currently assigned to a particular 1089 EFMCu port (efmCuNumPMEs) is never greater than 1090 efmCuPAFCapacity. 1092 This object maps to the Clause 30 attribute 1093 aLocalPAFCapacity." 1094 REFERENCE 1095 "[802.3ah] 61.2.2, 30.11.1.1.6" 1096 ::= { efmCuPortCapabilityEntry 3 } 1098 efmCuPeerPAFCapacity OBJECT-TYPE 1099 SYNTAX Unsigned32 (0|1..32) 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "Number of PMEs that can be aggregated by the PAF of the peer 1104 Phy (PCS port). 1105 Value of 0 is returned when peer PAF Capacity is unknown 1106 (peer cannot be reached). 1108 This object maps to the Clause 30 attribute 1109 aRemotePAFCapacity." 1110 REFERENCE 1111 "[802.3ah] 61.2.2, 30.11.1.1.10" 1112 ::= { efmCuPortCapabilityEntry 4 } 1114 efmCuPortStatusTable OBJECT-TYPE 1115 SYNTAX SEQUENCE OF EfmCuPortStatusEntry 1116 MAX-ACCESS not-accessible 1117 STATUS current 1118 DESCRIPTION 1119 "This table provides overall status information of EFMCu 1120 2BASE-TL/10PASS-TS ports. This table contains live data from 1121 the equipment. As such, it is NOT persistent." 1122 ::= { efmCuPort 3 } 1124 efmCuPortStatusEntry OBJECT-TYPE 1125 SYNTAX EfmCuPortStatusEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "An entry in the EFMCu Port Status table. 1130 Each entry represents an EFMCu port indexed by the ifIndex. 1131 Note that an EFMCu PCS port runs on top of a single 1132 or multiple PME port(s), which are also indexed by ifIndex." 1133 INDEX { ifIndex } 1134 ::= { efmCuPortStatusTable 1 } 1136 EfmCuPortStatusEntry ::= 1137 SEQUENCE { 1138 efmCuFltStatus BITS, 1139 efmCuPortSide INTEGER, 1140 efmCuNumPMEs Unsigned32, 1141 efmCuPAFInErrors Counter32, 1142 efmCuPAFInSmallFragments Counter32, 1143 efmCuPAFInLargeFragments Counter32, 1144 efmCuPAFInBadFragments Counter32, 1145 efmCuPAFInLostFragments Counter32, 1146 efmCuPAFInLostStarts Counter32, 1147 efmCuPAFInLostEnds Counter32, 1148 efmCuPAFInOverflows Counter32 1149 } 1151 efmCuFltStatus OBJECT-TYPE 1152 SYNTAX BITS { 1153 noPeer(0), 1154 pmeSubTypeMismatch(1), 1155 lowBandwidth(2) 1156 } 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION 1160 "EFMCu (PCS) port Fault Status. This is a bitmap of possible 1161 conditions. The various bit positions are: 1162 noPeer - peer PHY cannot be reached (e.g. 1163 no PMEs attached, all PMEs are Down 1164 etc.) More info is available in 1165 efmCuPmeFltStatus. 1166 pmeSubTypeMismatch - local PMEs in the aggregation group 1167 are not of the same sub-type, e.g. 1168 some PMEs in the local device are -O 1169 while others are -R subtype. 1170 lowBandwidth - ifSpeed of the port reached or droped 1171 below efmCuThreshLowBandwidth 1173 This object is intended to supplement ifOperStatus object 1174 in IF-MIB. 1175 Additional information is available via efmCuPmeFltStatus 1176 object for each PME in the aggregation group (single PME if 1177 PAF is disabled)." 1178 REFERENCE 1179 "ifOperStatus in IF-MIB; efmCuPmeFltStatus" 1180 ::= { efmCuPortStatusEntry 1 } 1182 efmCuPortSide OBJECT-TYPE 1183 SYNTAX INTEGER { 1184 subscriber(1), 1185 office(2), 1186 unknown(3) 1187 } 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "EFM port mode of operation (subtype). 1192 The value of 'subscriber' indicates the port is designated as 1193 '-R' subtype (all PMEs assigned to this port are of subtype 1194 '-R'). 1195 The value of the 'office' indicates that the port is 1196 designated as '-O' subtype (all PMEs assigned to this port are 1197 of subtype '-O'). 1198 The value of 'unknown' indicates that the port has no assigned 1199 PMEs yet or that the assigned PMEs are not of the same side 1200 (subTypePMEMismatch). 1202 This object partially maps to the Clause 30 attribute 1203 aPhyEnd" 1204 REFERENCE 1205 "[802.3ah] 61.1, 30.11.1.1.2" 1206 ::= { efmCuPortStatusEntry 2 } 1208 efmCuNumPMEs OBJECT-TYPE 1209 SYNTAX Unsigned32 (0..32) 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "Number of PMEs that is currently aggregated by the local PAF 1214 (assigned to the EFMCu port using ifStackTable). 1215 This number is never greater than efmCuPAFCapacity. 1217 This object SHALL be automatically incremented or decremented 1218 when a PME is added or deleted to/from the EFMCu port using 1219 ifStackTable." 1220 REFERENCE 1221 "[802.3ah] 61.2.2, 30.11.1.1.6" 1222 ::= { efmCuPortStatusEntry 3 } 1224 efmCuPAFInErrors OBJECT-TYPE 1225 SYNTAX Counter32 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "A number of fragments that have been received across the 1230 gamma interface with RxErr asserted and discarded. 1231 This read-only counter is inactive (not incremented) when the 1232 PAF is unsupported or disabled. Upon disabling the PAF, the 1233 counter retains its previous value. 1235 If a Clause 45 MDIO Interface to the PCS is present, then 1236 this object maps to the 10P/2B PAF RX error register." 1237 REFERENCE 1238 "[802.3ah] 45.2.3.21" 1239 ::= { efmCuPortStatusEntry 4 } 1241 efmCuPAFInSmallFragments OBJECT-TYPE 1242 SYNTAX Counter32 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "A number of fragments smaller than minFragmentSize 1247 (64 Bytes), that have been received across the gamma interface 1248 and discarded. 1249 This read-only counter is inactive when the PAF is 1250 unsupported or disabled. Upon disabling the PAF, the counter 1251 retains its previous value. 1253 If a Clause 45 MDIO Interface to the PCS is present, then 1254 this object maps to the 10P/2B PAF small fragments 1255 register." 1256 REFERENCE 1257 "[802.3ah] 45.2.3.22" 1258 ::= { efmCuPortStatusEntry 5 } 1260 efmCuPAFInLargeFragments OBJECT-TYPE 1261 SYNTAX Counter32 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "A number of fragments larger than maxFragmentSize 1266 (512 Bytes), that have been received across the gamma 1267 interface and discarded. 1268 This read-only counter is inactive when the PAF is 1269 unsupported or disabled. Upon disabling the PAF, the counter 1270 retains its previous value. 1272 If a Clause 45 MDIO Interface to the PCS is present, then 1273 this object maps to the 10P/2B PAF large fragments 1274 register." 1275 REFERENCE 1276 "[802.3ah] 45.2.3.23" 1277 ::= { efmCuPortStatusEntry 6 } 1279 efmCuPAFInBadFragments OBJECT-TYPE 1280 SYNTAX Counter32 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "A number of fragments which do not fit into the sequence 1285 expected by the frame assembly function, that have been 1286 received across the gamma interface and discarded (the 1287 frame buffer is flushed to the next valid frame start). 1288 This read-only counter is inactive when the PAF is 1289 unsupported or disabled. Upon disabling the PAF, the counter 1290 retains its previous value. 1292 If a Clause 45 MDIO Interface to the PCS is present, then 1293 this object maps to the 10P/2B PAF bad fragments 1294 register." 1295 REFERENCE 1296 "[802.3ah] 45.2.3.25" 1297 ::= { efmCuPortStatusEntry 7 } 1299 efmCuPAFInLostFragments OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "A number of gaps in the sequence of fragments, that have been 1305 received across the gamma interface (the frame buffer is 1306 flushed to the next valid frame start, when fragment/fragments 1307 expected by the frame assembly function is/are not received). 1308 This read-only counter is inactive when the PAF is 1309 unsupported or disabled. Upon disabling the PAF, the counter 1310 retains its previous value. 1312 If a Clause 45 MDIO Interface to the PCS is present, then 1313 this object maps to the 10P/2B PAF lost fragment 1314 register." 1315 REFERENCE 1316 "[802.3ah] 45.2.3.26" 1318 ::= { efmCuPortStatusEntry 8 } 1320 efmCuPAFInLostStarts OBJECT-TYPE 1321 SYNTAX Counter32 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "A number of missing StartOfPacket indicators expected by the 1326 frame assembly function. 1327 This read-only counter is inactive when the PAF is 1328 unsupported or disabled. Upon disabling the PAF, the counter 1329 retains its previous value. 1331 If a Clause 45 MDIO Interface to the PCS is present, then 1332 this object maps to the 10P/2B PAF lost start of fragment 1333 register." 1334 REFERENCE 1335 "[802.3ah] 45.2.3.27" 1336 ::= { efmCuPortStatusEntry 9 } 1338 efmCuPAFInLostEnds OBJECT-TYPE 1339 SYNTAX Counter32 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "A number of missing EndOfPacket indicators expected by the 1344 frame assembly function. 1345 This read-only counter is inactive when the PAF is 1346 unsupported or disabled. Upon disabling the PAF, the counter 1347 retains its previous value. 1349 If a Clause 45 MDIO Interface to the PCS is present, then 1350 this object maps to the 10P/2B PAF lost start of fragment 1351 register." 1352 REFERENCE 1353 "[802.3ah] 45.2.3.28" 1354 ::= { efmCuPortStatusEntry 10 } 1356 efmCuPAFInOverflows OBJECT-TYPE 1357 SYNTAX Counter32 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "A number of fragements, received accross the gamma interface 1362 and discarded, which would have caused the frame assembly 1363 buffer to overflow. 1364 This read-only counter is inactive when the PAF is 1365 unsupported or disabled. Upon disabling the PAF, the counter 1366 retains its previous value. 1368 If a Clause 45 MDIO Interface to the PCS is present, then 1369 this object maps to the 10P/2B PAF overflow register." 1370 REFERENCE 1371 "[802.3ah] 45.2.3.24" 1372 ::= { efmCuPortStatusEntry 11 } 1374 -- PME Notifications Group 1376 efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 } 1378 -- EdNote: Should I add more notifications here, for example 1379 -- efmCuPmePerfES, 1380 -- efmCuPmePerfSES, 1381 -- efmCuPmePerfCRCanomalies, 1382 -- efmCuPmePerfLOSWS, 1383 -- efmCuPmePerfUAS, 1384 -- efmCuPmeDeviceFault, 1385 -- efmCuPmeLocalPowerLoss 1386 -- Another option would be to reference HDSL2-SHDSL-LINE-MIB 1387 -- or VDSL-LINE-EXT-MCM-MIB, reusing notifications defined there. 1389 efmCuPmeLineAtnCrossing NOTIFICATION-TYPE 1390 OBJECTS { 1391 efmCuPmeLineAtn, 1392 efmCuPmeThreshLineAtn 1393 } 1394 STATUS current 1395 DESCRIPTION 1396 "This notification indicates that the loop attenuation 1397 threshold (as per the efmCuPmeThreshLineAtn 1398 value) has been reached/exceeded for the 2BASE-TL/10PASS-TS 1399 PME. This notification MAY be send on the crossing event in 1400 both directions: from normal to exceeded and from exceeded 1401 to normal. 1403 Generation of this notification is controlled by the 1404 efmCuPmeLineAtnCrossingEnable object." 1405 -- EdNote: add throttling limitations here, with 10 sec 1406 -- debouncing on clear to prevenmt intermittent alarms 1407 ::= { efmCuPmeNotifications 1 } 1409 efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE 1410 OBJECTS { 1411 efmCuPmeSnrMgn, 1412 efmCuPmeThreshSnrMgn 1413 } 1414 STATUS current 1415 DESCRIPTION 1416 "This notification indicates that the SNR margin threshold 1417 (as per the efmCuPmeThreshSnrMgn value) has been 1418 reached/exceeded for the 2BASE-TL/10PASS-TS PME. 1419 This notification MAY be send on the crossing event in 1420 both directions: from normal to exceeded and from exceeded 1421 to normal. 1423 Generation of this notification is controlled by the 1424 efmCuPmeSnrMgnCrossingEnable object." 1425 -- EdNote: add throttling limitations here, with 10 sec 1426 -- debouncing on clear to prevenmt intermittent alarms 1427 ::= { efmCuPmeNotifications 2 } 1429 efmCuPmeDeviceFault NOTIFICATION-TYPE 1430 OBJECTS { 1431 efmCuPmeFltStatus 1432 } 1433 STATUS current 1434 DESCRIPTION 1435 "This notification indicates that a fault in the PME has been 1436 detected by a vendor specific diagnostic or a self-test. 1438 Generation of this notification is controlled by the 1439 efmCuPmeDeviceFaultEnable object." 1440 ::= { efmCuPmeNotifications 3 } 1442 efmCuPmeConfigInitFailure NOTIFICATION-TYPE 1443 OBJECTS { 1444 efmCuPmeFltStatus, 1445 efmCuAdminProfile, 1446 efmCuPmeAdminProfile 1447 } 1448 STATUS current 1449 DESCRIPTION 1450 "This notification indicates that PME initialization has 1451 failed, due to inability of the PME link to achieve requested 1452 configuration profile. 1454 Generation of this notification is controlled by the 1455 efmCuPmeConfigInitFailEnable object." 1456 ::= { efmCuPmeNotifications 4 } 1458 efmCuPmeProtocolInitFailure NOTIFICATION-TYPE 1459 OBJECTS { 1460 efmCuPmeFltStatus, 1461 efmCuPmeOperSubType 1463 } 1464 STATUS current 1465 DESCRIPTION 1466 "This notification indicates that peer PME was using 1467 incompatible protocol during initialization. 1469 Generation of this notification is controlled by the 1470 efmCuPmeProtocolInitFailEnable object." 1471 ::= { efmCuPmeNotifications 5 } 1473 -- The PME group 1475 efmCuPmeConfTable OBJECT-TYPE 1476 SYNTAX SEQUENCE OF EfmCuPmeConfEntry 1477 MAX-ACCESS not-accessible 1478 STATUS current 1479 DESCRIPTION 1480 "Table for Configuration of common aspects for EFMCu 1481 2BASE-TL/10PASS-TS PME ports (modems). Configuration of 1482 aspects specific to 2BASE-TL or 10PASS-TS PME types is 1483 represented in efmCuPme2BConfTable and efmCuPme10PConfTable 1484 respectively. 1486 Entries in this table MUST be maintained in a persistent 1487 manner." 1488 ::= { efmCuPme 1 } 1490 efmCuPmeConfEntry OBJECT-TYPE 1491 SYNTAX EfmCuPmeConfEntry 1492 MAX-ACCESS not-accessible 1493 STATUS current 1494 DESCRIPTION 1495 "An entry in the EFMCu PME Configuration table. 1496 Each entry represents common aspects of an EFMCu PME port 1497 indexed by the ifIndex. Note that an EFMCu PME port can be 1498 stacked below a single PCS port, also indexed by ifIndex, 1499 possibly together with other PME ports if PAF is enabled." 1500 INDEX { ifIndex } 1501 ::= { efmCuPmeConfTable 1 } 1503 EfmCuPmeConfEntry ::= 1504 SEQUENCE { 1505 efmCuPmeAdminSubType INTEGER, 1506 efmCuPmeAdminProfile ProfileIndexOrZero, 1507 efmCuPAFRemoteDiscoveryCode PhysAddress, 1508 efmCuPmeThreshLineAtn Integer32, 1509 efmCuPmeThreshSnrMgn Integer32, 1510 efmCuPmeLineAtnCrossingEnable TruthValue, 1511 efmCuPmeSnrMgnCrossingEnable TruthValue, 1512 efmCuPmeDeviceFaultEnable TruthValue, 1513 efmCuPmeConfigInitFailEnable TruthValue, 1514 efmCuPmeProtocolInitFailEnable TruthValue 1515 } 1517 efmCuPmeAdminSubType OBJECT-TYPE 1518 SYNTAX INTEGER { 1519 ieee2BaseTLO(1), 1520 ieee2BaseTLR(2), 1521 ieee10PassTSO(3), 1522 ieee10PassTSR(4), 1523 ieee2BaseTLor10PassTSR(5), 1524 ieee2BaseTLor10PassTSO(6), 1525 ieee10PassTSor2BaseTLO(7) 1526 } 1527 MAX-ACCESS read-write 1528 STATUS current 1529 DESCRIPTION 1530 "Administrative (desired) sub-type of the PME. 1531 Possible values are: 1532 ieee2BaseTLO - PME shall operate as 2BaseTL-O 1533 ieee2BaseTLR - PME shall operate as 2BaseTL-R 1534 ieee10PassTSO - PME shall operate as 10PassTS-O 1535 ieee10PassTSR - PME shall operate as 10PassTS-R 1536 ieee2BaseTLor10PassTSR - PME shall operate as 2BaseTL-R or 1537 10PassTS-R. Actual value will be 1538 set by -O link partner during 1539 initialization (handshake). 1540 ieee2BaseTLor10PassTSO - PME shall operate as 2BaseTL-O 1541 (preferred) or 10PassTS-O. Actual 1542 value will be set during 1543 initialization depending on -R 1544 link partner capability (i.e. if 1545 -R is incapable of the preferred 1546 2BaseTL mode, 10PassTS will be 1547 used). 1548 ieee10PassTSor2BaseTLO - PME shall operate as 10PassTS-O 1549 (preferred) or 2BaseTL-O. Actual 1550 value will be set during 1551 initialization depending on -R 1552 link partner capability (i.e. if 1553 -R is incapable of the preferred 1554 10PassTS mode, 2BaseTL will be 1555 used). 1557 Changing efmCuPmeAdminSubType is a traffic disruptive 1558 operation and as such SHALL be done when the link is Down. 1560 Attempts to change this object SHALL be ignored if the link 1561 is Up or Initializing. 1562 Attempts to change this object to an unsupported subtype 1563 (see efmCuPmeSubTypesSupported) SHALL be rejected. 1565 The current operational sub type is indicated by 1566 efmCuPmeOperSubType variable. 1568 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1569 this object combines values of the Port sub-type select 1570 bits and the PMA/PMD type selection bits in the 10P/2B 1571 PMA/PMD control register" 1572 REFERENCE 1573 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7" 1574 ::= { efmCuPmeConfEntry 1 } 1576 efmCuPmeAdminProfile OBJECT-TYPE 1577 SYNTAX ProfileIndexOrZero 1578 MAX-ACCESS read-write 1579 STATUS current 1580 DESCRIPTION 1581 "Desired PME configuration Profile. This object is a pointer 1582 to an entry in either efmCuPme2BProfileTable or 1583 efmCuPme10PProfileTable, depending on the current 1584 operating SubType of the PME. The value of this object is the 1585 index of the referenced profile. 1586 The value of zero (default) indicates that the PME is 1587 configured via efmCuAdminProfile object for the PCS port, 1588 to which this PME is assigned. That is, the profile referenced 1589 by efmCuPmeAdminProfile takes precedence over the profile(s) 1590 referenced by efmCuAdminProfile. 1592 This object is writable and readable for the CO subtype PMEs 1593 (2BaseTL-O or 10PassTS-O). It is unavailable for the CPE 1594 subtype (2BaseTL-R or 10PassTS-R). 1596 Note that current operational Profile value is available via 1597 efmCuPmeOperProfile object. 1599 Modification of this object must be performed when the link is 1600 Down. Attempts to change this object MUST be rejected, if the 1601 link is Up or Initializing. 1602 Attempts to set this object to a value that is not the 1603 value of the index for an active entry in the corresponding 1604 profile table, MUST be rejected." 1605 REFERENCE 1606 "[802.3ah] 30.11.2.1.6" 1607 DEFVAL { 0 } 1608 ::= { efmCuPmeConfEntry 2 } 1610 efmCuPAFRemoteDiscoveryCode OBJECT-TYPE 1611 SYNTAX PhysAddress 1612 MAX-ACCESS read-write 1613 STATUS current 1614 DESCRIPTION 1615 "PAF Remote Discovery Code of the PME port at CO. 1616 A 6 Byte long Discovery Code of the peer PCS connected via 1617 the PME. 1618 Reading this object results in a Discovery Get operation. 1619 Writing a zero to this object results in a Discovery 1620 Clear_if_Same operation (the value of efmCuPAFDiscoveryCode 1621 at the peer PCS shall be the same as efmCuPAFDiscoveryCode of 1622 the local PCS associated with the PME for the operation to 1623 succeed). 1624 Writing a non-zero value to this object results in a 1625 Discovery Set_if_Clear operation. 1626 This object does not exist in CPE port subtypes. A zero length 1627 octet string SHALL be returned for CPE port subtypes and also 1628 when PAF aggregation is not enabled. 1630 Discovery MUST be performed when the link is Down. 1631 Attempts to change this object MUST be rejected with the error 1632 inconsistentValue, if the link is Up or Initializing. 1634 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1635 this object is a function of 10P/2B aggregation discovery 1636 control register, Discovery operation result bits in 10P/2B 1637 aggregation and discovery status register and 1638 10P/2B aggregation discovery code register" 1639 REFERENCE 1640 "[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8" 1641 ::= { efmCuPmeConfEntry 3 } 1643 efmCuPmeThreshLineAtn OBJECT-TYPE 1644 SYNTAX Integer32(-127..128) 1645 UNITS "dB" 1646 MAX-ACCESS read-write 1647 STATUS current 1648 DESCRIPTION 1649 "Desired Line Attenuation Threshold for the 2B/10P PME. 1650 This object configures the line attenuation alarm threshold. 1651 When the current value of Line Attenuation reaches or 1652 exceeds this threshold, a efmCuPmeLineAtnCrossing 1653 notification MAY be generated, if enabled by 1654 efmCuPmeLineAtnCrossingEnable. 1656 This object is writable for the CO subtype PMEs (-O). 1657 It is read-only for the CPE subtype (-R). 1659 Changing of the Line Attenuation Threshold must be performed 1660 when the link is Down. Attempts to change this object MUST be 1661 rejected with the error inconsistentValue, if the link is Up 1662 or Initializing. 1664 If a Clause 45 MDIO Interface to the PME is present, then this 1665 object will map to the Loop attenuation threshold bits in 1666 the 2B PMD line quality thresholds register" 1667 REFERENCE 1668 "[802.3ah] 45.2.1.36" 1669 ::= { efmCuPmeConfEntry 4 } 1671 efmCuPmeThreshSnrMgn OBJECT-TYPE 1672 SYNTAX Integer32(-127..128) 1673 UNITS "dB" 1674 MAX-ACCESS read-write 1675 STATUS current 1676 DESCRIPTION 1677 "Desired SNR Margin Threshold for the 2B/10P PME. 1678 This object configures the SNR margin alarm threshold. 1679 When the current value of SNR Margin reaches 1680 or exceeds this threshold, a efmCuPmeSnrMgnCrossing 1681 notification MAY be generated, if enabled by 1682 efmCuPmeSnrMgnCrossingEnable. 1684 This object is writable for the CO subtype PMEs 1685 (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype 1686 (2BaseTL-R/10PassTS-R). 1688 Changing of the SNR Margin Threshold must be performed when 1689 the link is Down. Attempts to change this object MUST be 1690 rejected with the error inconsistentValue, if the link is Up 1691 or Initializing. 1693 If a Clause 45 MDIO Interface to the PME is present, then this 1694 object will map to the SNR margin threshold bits in the 1695 2B PMD line quality thresholds register" 1696 REFERENCE 1697 "[802.3ah] 45.2.1.36" 1698 ::= { efmCuPmeConfEntry 5 } 1700 efmCuPmeLineAtnCrossingEnable OBJECT-TYPE 1701 SYNTAX TruthValue 1702 MAX-ACCESS read-write 1703 STATUS current 1704 DESCRIPTION 1705 "Indicates whether efmCuPmeLineAtnCrossing notifications 1706 should be generated for this interface. 1708 Value of true(1) indicates that efmCuPmeLineAtnCrossing 1709 notification is enabled. Value of false(2) indicates that 1710 the notification is disabled." 1711 ::= { efmCuPmeConfEntry 6 } 1713 efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE 1714 SYNTAX TruthValue 1715 MAX-ACCESS read-write 1716 STATUS current 1717 DESCRIPTION 1718 "Indicates whether efmCuPmeSnrMgnCrossing notifications 1719 should be generated for this interface. 1721 Value of true(1) indicates that efmCuPmeSnrMgnCrossing 1722 notification is enabled. Value of false(2) indicates that 1723 the notification is disabled." 1724 ::= { efmCuPmeConfEntry 7 } 1726 efmCuPmeDeviceFaultEnable OBJECT-TYPE 1727 SYNTAX TruthValue 1728 MAX-ACCESS read-write 1729 STATUS current 1730 DESCRIPTION 1731 "Indicates whether efmCuPmeDeviceFault notifications 1732 should be generated for this interface. 1734 Value of true(1) indicates that efmCuPmeDeviceFault 1735 notification is enabled. Value of false(2) indicates that 1736 the notification is disabled." 1737 ::= { efmCuPmeConfEntry 8 } 1739 efmCuPmeConfigInitFailEnable OBJECT-TYPE 1740 SYNTAX TruthValue 1741 MAX-ACCESS read-write 1742 STATUS current 1743 DESCRIPTION 1744 "Indicates whether efmCuPmeConfigInitFailure notifications 1745 should be generated for this interface. 1747 Value of true(1) indicates that efmCuPmeConfigInitFailure 1748 notification is enabled. Value of false(2) indicates that 1749 the notification is disabled." 1750 ::= { efmCuPmeConfEntry 9 } 1752 efmCuPmeProtocolInitFailEnable OBJECT-TYPE 1753 SYNTAX TruthValue 1754 MAX-ACCESS read-write 1755 STATUS current 1756 DESCRIPTION 1757 "Indicates whether efmCuPmeProtocolInitFailure notifications 1758 should be generated for this interface. 1760 Value of true(1) indicates that efmCuPmeProtocolInitFailure 1761 notification is enabled. Value of false(2) indicates that 1762 the notification is disabled." 1763 ::= { efmCuPmeConfEntry 10 } 1765 efmCuPmeCapabilityTable OBJECT-TYPE 1766 SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry 1767 MAX-ACCESS not-accessible 1768 STATUS current 1769 DESCRIPTION 1770 "Table for Configuration of common aspects for EFMCu 1771 2BASE-TL/10PASS-TS PME ports (modems). Configuration of 1772 aspects specific to 2BASE-TL or 10PASS-TS PME types is 1773 represented in efmCuPme2BConfTable and efmCuPme10PConfTable 1774 respectively. 1776 Entries in this table MUST be maintained in a persistent 1777 manner." 1778 ::= { efmCuPme 2 } 1780 efmCuPmeCapabilityEntry OBJECT-TYPE 1781 SYNTAX EfmCuPmeCapabilityEntry 1782 MAX-ACCESS not-accessible 1783 STATUS current 1784 DESCRIPTION 1785 "An entry in the EFMCu PME Capability table. 1786 Each entry represents common aspects of an EFMCu PME port 1787 indexed by the ifIndex. Note that an EFMCu PME port can be 1788 stacked below a single PCS port, also indexed by ifIndex, 1789 possibly together with other PME ports if PAF is enabled." 1790 INDEX { ifIndex } 1791 ::= { efmCuPmeCapabilityTable 1 } 1793 EfmCuPmeCapabilityEntry ::= 1794 SEQUENCE { 1795 efmCuPmeSubTypesSupported BITS 1796 } 1798 efmCuPmeSubTypesSupported OBJECT-TYPE 1799 SYNTAX BITS { 1800 ieee2BaseTLO(0), 1801 ieee2BaseTLR(1), 1802 ieee10PassTSO(2), 1803 ieee10PassTSR(3) 1804 } 1805 MAX-ACCESS read-only 1806 STATUS current 1807 DESCRIPTION 1808 "PME supported sub-types. This is a bitmap of possible 1809 sub-types. The various bit positions are: 1810 ieee2BaseTLO - PME is capable of operating as 2BaseTL-O 1811 ieee2BaseTLR - PME is capable of operating as 2BaseTL-R 1812 ieee10PassTSO - PME is capable of operating as 10PassTS-O 1813 ieee10PassTSR - PME is capable of operating as 10PassTS-R 1815 An desired mode of operation is determined by 1816 efmCuPmeAdminSubType, while efmCuPmeOperSubType relects the 1817 current operating mode. 1819 If a Clause 45 MDIO Interface to the PCS is present, then this 1820 object combines the 10PASS-TS capable and 2BASE-TL capable 1821 bits in the 10P/2B PMA/PMD speed ability register and the 1822 CO supported and CPE supported bits in the 10P/2B PMA/PMD 1823 status register" 1824 REFERENCE 1825 "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, 1826 45.2.1.12.3" 1827 ::= { efmCuPmeCapabilityEntry 1 } 1829 efmCuPmeStatusTable OBJECT-TYPE 1830 SYNTAX SEQUENCE OF EfmCuPmeStatusEntry 1831 MAX-ACCESS not-accessible 1832 STATUS current 1833 DESCRIPTION 1834 "This table provides common status information of EFMCu 1835 2BASE-TL/10PASS-TS PME ports. Status information specific 1836 to 10PASS-TS PME is represented in efmCuPme10PStatusTable. 1838 This table contains live data from the equipment. As such, 1839 it is NOT persistent." 1840 ::= { efmCuPme 3 } 1842 efmCuPmeStatusEntry OBJECT-TYPE 1843 SYNTAX EfmCuPmeStatusEntry 1844 MAX-ACCESS not-accessible 1845 STATUS current 1846 DESCRIPTION 1847 "An entry in the EFMCu PME Status table. 1848 Each entry represents common aspects of an EFMCu PME port 1849 indexed by the ifIndex. Note that an EFMCu PME port can be 1850 stacked below a single PCS port, also indexed by ifIndex, 1851 possibly together with other PME ports if PAF is enabled." 1852 INDEX { ifIndex } 1853 ::= { efmCuPmeStatusTable 1 } 1855 EfmCuPmeStatusEntry ::= 1856 SEQUENCE { 1857 efmCuPmeOperStatus INTEGER, 1858 efmCuPmeFltStatus BITS, 1859 efmCuPmeOperSubType INTEGER, 1860 efmCuPmeOperProfile ProfileIndexOrZero, 1861 efmCuPmeSnrMgn Integer32, 1862 efmCuPmePeerSnrMgn Integer32, 1863 efmCuPmeLineAtn Integer32, 1864 efmCuPmePeerLineAtn Integer32, 1865 efmCuPmeTCCodingErrors Counter32, 1866 efmCuPmeTCCrcErrors Counter32 1867 } 1869 efmCuPmeOperStatus OBJECT-TYPE 1870 SYNTAX INTEGER { 1871 up(1), 1872 downNotReady(2), 1873 downReady(3), 1874 init(4) 1875 } 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "Current PME link Operational Status. Possible values are: 1880 up(1) - link is Up and ready to pass 64/65B 1881 encoded frames or fragments. 1882 downNotReady(2) - link is Down and the PME does not detect 1883 Handshake tones from its peer. This value 1884 may indicate a possible problem with 1885 the peer PME. 1886 downReady(3) - link is Down and the PME detects Handshake 1887 tones from its peer. 1888 init(4) - link is initializing, as a result of 1889 ifAdminStatus being set to 'up' for a 1890 particular PME or a PCS the PME is 1891 connected to. 1893 This object is intended to supplement Down state of 1894 ifOperStatus. 1896 This object partially maps to the Clause 30 attribute 1897 aPMEStatus. 1899 If a Clause 45 MDIO Interface to the PME is present, then this 1900 object partially maps to PMA/PMD link status bits in 10P/2B 1901 PMA/PMD status register." 1902 REFERENCE 1903 "[802.3ah] 30.11.2.1.3, 45.2.1.12.4" 1904 ::= { efmCuPmeStatusEntry 1 } 1906 efmCuPmeFltStatus OBJECT-TYPE 1907 SYNTAX BITS { 1908 lossOfFraming(0), 1909 snrMgnDefect(1), 1910 lineAtnDefect(2), 1911 deviceFault(3), 1912 configInitFailure(4), 1913 protocolInitFailure(5) 1914 } 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "Current/Last PME link Fault Status. This is a bitmap of 1919 possible conditions. The various bit positions are: 1921 lossOfFraming - Loss of Framing for 10P or 1922 Loss of Sync word for 2B PMD or 1923 Loss of 64/65B Framing 1924 snrMgnDefect - SNR Margin dropped below the Threshold 1925 lineAtnDefect - Line Attenuation exceeds the Threshold 1926 deviceFault - Indicates a vendor-dependent 1927 diagnostic or self-test fault 1928 has been detected. 1929 configInitFailure - Configuration initialization failure, 1930 due to inability of the PME link to 1931 support configuration profile, 1932 requested during initialization. 1933 protocolInitFailure - Protocol initialization failure, 1934 due to incompatible protocol used by 1935 the Peer PME during init (that could 1936 happen if a peer PMD is G.SDHSL/VDSL 1937 modem for 2BASE-TL/10PASS-TS PME 1938 respectively). 1940 This object is intended to supplement ifOperStatus in IF-MIB. 1942 The indications hold information about the last fault. 1943 efmCuPmeFltStatus is cleared by the device restart. 1944 In addition lossOfFraming, configInitFailure and 1945 protocolInitFailure are cleared by PME init. 1946 deviceFault is cleared by successful diagnostics/test. 1947 snrMgnDefect and lineAtnDefect are cleared by SNR Margin 1948 and line Attenuation respectively returning to norm and by 1949 PME init. 1951 This object partially maps to the Clause 30 attribute 1952 aPMEStatus. 1954 If a Clause 45 MDIO Interface to the PME is present, then this 1955 object consolidates information from various PMA/PMD 1956 registers, namely: Fault bit in PMA/PMD status 1 register, 1957 10P/2B PMA/PMD link loss register, 1958 10P outgoing indicator bits status register, 1959 10P incoming indicator bits status register, 1960 2B state defects register." 1961 REFERENCE 1962 "[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38, 1963 45.2.1.39, 45.2.1.54" 1964 ::= { efmCuPmeStatusEntry 2 } 1966 efmCuPmeOperSubType OBJECT-TYPE 1967 SYNTAX INTEGER { 1968 ieee2BaseTLO(1), 1969 ieee2BaseTLR(2), 1970 ieee10PassTSO(3), 1971 ieee10PassTSR(4) 1972 } 1973 MAX-ACCESS read-only 1974 STATUS current 1975 DESCRIPTION 1976 "Current operational sub-type of the PME. 1977 Possible values are: 1978 ieee2BaseTLO - PME operates as 2BaseTL-O 1979 ieee2BaseTLR - PME operates as 2BaseTL-R 1980 ieee10PassTSO - PME operates as 10PassTS-O 1981 ieee10PassTSR - PME operates as 10PassTS-R 1983 The operational sub type of the PME can be configured via 1984 efmCuPmeAdminSubType variable. 1986 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1987 this object combines values of the Port sub-type select 1988 bits, the PMA/PMD type selection bits in the 10P/2B 1989 PMA/PMD control register and the PMA/PMD link status bits in 1990 the 10P/2B PMA/PMD status register." 1991 REFERENCE 1992 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4" 1993 ::= { efmCuPmeStatusEntry 3 } 1995 efmCuPmeOperProfile OBJECT-TYPE 1996 SYNTAX ProfileIndexOrZero 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "PME current operating Profile. This object is a pointer to 2001 an entry in either efmCuPme2BProfileTable or 2002 efmCuPme10PProfileTable, depending on the current 2003 operating SubType of the PME as indicated by 2004 efmCuPmeOperSubType. 2005 Note that a profile entry, to which efmCuPmeOperProfile is 2006 pointing to, can be created automatically, to reflect achieved 2007 parameters in adaptive (not fixed) initialization, 2008 i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or 2009 efmCuPmeAdminProfile MAY differ. 2010 The value of zero indicates that PME is down or initializing. 2012 This object partially maps to the aOperatingProfile 2013 attribute in Clause 30." 2014 REFERENCE 2015 "[802.3ah] 30.11.2.1.7" 2016 ::= { efmCuPmeStatusEntry 4 } 2018 efmCuPmeSnrMgn OBJECT-TYPE 2019 SYNTAX Integer32(-127..128|65535) 2020 UNITS "dB" 2021 MAX-ACCESS read-only 2022 STATUS current 2023 DESCRIPTION 2024 "The current Signal-to-Noise Ratio (SNR) margin with respect 2025 to the received signal as perceived by the local PME. 2026 The value of 65535 is returned when PME is down or 2027 initializing. 2029 This object maps to the aPMESNRMgn attribute in Clause 30. 2031 If a Clause 45 MDIO Interface is present, then this 2032 object maps to the 10P/2B RX SNR margin register." 2033 REFERENCE 2034 "[802.3ah] 30.11.2.1.4, 45.2.1.16" 2035 ::= { efmCuPmeStatusEntry 5 } 2037 efmCuPmePeerSnrMgn OBJECT-TYPE 2038 SYNTAX Integer32(-127..128|65535) 2039 UNITS "dB" 2040 MAX-ACCESS read-only 2041 STATUS current 2042 DESCRIPTION 2043 "The current SNR margin in dB with respect to the received 2044 signal, as perceived by the remote (link partner) PME. 2045 The value of 65535 is returned when PME is down or 2046 initializing. 2048 This object is not supported by -R PME subtypes. 2050 If a Clause 45 MDIO Interface is present, then this 2051 object maps to the 10P/2B link partner RX SNR margin 2052 register." 2053 REFERENCE 2054 "[802.3ah] 45.2.1.17" 2055 ::= { efmCuPmeStatusEntry 6} 2057 efmCuPmeLineAtn OBJECT-TYPE 2058 SYNTAX Integer32(-127..128|65535) 2059 UNITS "dB" 2060 MAX-ACCESS read-only 2061 STATUS current 2062 DESCRIPTION 2063 "The current Line Attenuation in dB as perceived by the local 2064 PME. 2065 The value of 65535 is returned when PME is down or 2066 initializing. 2068 If a Clause 45 MDIO Interface is present, then this 2069 object maps to the Line Attenuation register" 2070 REFERENCE 2071 "[802.3ah] 45.2.1.18" 2072 ::= { efmCuPmeStatusEntry 7 } 2074 efmCuPmePeerLineAtn OBJECT-TYPE 2075 SYNTAX Integer32(-127..128|65535) 2076 UNITS "dB" 2077 MAX-ACCESS read-only 2078 STATUS current 2079 DESCRIPTION 2080 "The current Line Attenuation in dB as perceived by the remote 2081 (link partner) PME. 2082 The value of 65535 is returned when PME is down or 2083 initializing. 2085 This object is not supported by CPE port subtypes. 2087 If a Clause 45 MDIO Interface is present, then this 2088 object maps to the 20P/2B link partner Line Attenuation 2089 register." 2090 REFERENCE 2091 "[802.3ah] 45.2.1.19" 2092 ::= { efmCuPmeStatusEntry 8 } 2094 efmCuPmeTCCodingErrors OBJECT-TYPE 2095 SYNTAX Counter32 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "A number of 64/65-octet encapsulation errors. This counter is 2100 incremented for each 64/65-octet encapsulation error detected 2101 by the 64/65-octet receive function. 2102 The value of zero SHALL be returned when PME is down or 2103 initializing. 2105 If a Clause 45 MDIO Interface to the PME TC is present, then 2106 this object maps to the TC coding violations register 2107 (see 45.2.6.12)." 2108 REFERENCE 2109 "[802.3ah] 61.3.3.1, 45.2.6.12" 2110 ::= { efmCuPmeStatusEntry 9 } 2112 efmCuPmeTCCrcErrors OBJECT-TYPE 2113 SYNTAX Counter32 2114 MAX-ACCESS read-only 2115 STATUS current 2116 DESCRIPTION 2117 "A number of TC-CRC errors. This counter is incremented for 2118 each TC-CRC error detected by the 64/65-octet receive function 2119 (see 61.3.3.3 and Figure 61-19). 2120 The value of zero SHALL be returned when PME is down or 2121 initializing. 2123 If a Clause 45 MDIO Interface to the PCME TC is present, then 2124 this object maps to the TC CRC error register 2125 (see 45.2.6.11)." 2126 REFERENCE 2127 "[802.3ah] 61.3.3.3, 45.2.6.11" 2128 ::= { efmCuPmeStatusEntry 10 } 2130 -- 2BASE-TL specific PME group 2132 efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } 2134 efmCuPme2BProfileTable OBJECT-TYPE 2135 SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry 2136 MAX-ACCESS not-accessible 2137 STATUS current 2138 DESCRIPTION 2139 "This table supports definitions of administrative and 2140 operating Profiles for 2BASE-TL PMEs. 2141 First 14 entries in this table SHALL always be defined as 2142 follows (see 802.3ah Annex 63A): 2143 -------+------+-----+--------+------------------ 2144 Profile Rate Power Region Constellation 2145 index (Kbps) (dBm) (G.991.2) 2146 -------+------+-----+--------+------------------ 2147 1 5696 13.5 1 32-TCPAM (default) 2148 2 3072 13.5 1 32-TCPAM 2149 3 2048 13.5 1 16-TCPAM 2150 4 1024 13.5 1 16-TCPAM 2151 5 704 13.5 1 16-TCPAM 2152 6 512 13.5 1 16-TCPAM 2153 7 5696 14.5 2 32-TCPAM 2154 8 3072 14.5 2 32-TCPAM 2155 9 2048 14.5 2 16-TCPAM 2156 10 1024 13.5 2 16-TCPAM 2157 11 704 13.5 2 16-TCPAM 2158 12 512 13.5 2 16-TCPAM 2159 13 0 0 1 0 (best effort) 2160 14 0 0 2 0 (best effort) 2162 These default entries SHALL be created during agent 2163 initialization and MUST not be deleted. 2165 Entries following the first 14, can be dynamically created and 2166 deleted, to provide custom administrative (configuration) 2167 profiles and automatic operating profiles. 2169 This table MUST be maintained in a persistent manner." 2170 REFERENCE 2171 "[802.3ah] Annex 63A, 30.11.2.1.6" 2172 ::= { efmCuPme2B 2 } 2174 efmCuPme2BProfileEntry OBJECT-TYPE 2175 SYNTAX EfmCuPme2BProfileEntry 2176 MAX-ACCESS not-accessible 2177 STATUS current 2178 DESCRIPTION 2179 "Each entry corresponds to a single 2BASE-TL PME profile. 2180 Each profile contains a set of parameters, used either for 2181 configuration or representation of a 2BASE-TL PME. 2182 In case a particular profile is referenced via 2183 efmCuPmeAdminProfile object (or efmCuAdminProfile if 2184 efmCuPmeAdminProfile is zero), it represent the desired 2185 parameters the 2BaseTL-O PME initialization. 2186 If a profile is referenced via efmCuPmeOperProfile object, 2187 it represents current operating parameters of the 2188 operational PME. 2190 Profiles may be created/deleted using the row creation/ 2191 deletion mechanism via efmCuPme2BProfileRowStatus. If an 2192 active entry is referenced, the entry MUST remain 'active' 2193 until all references are removed. 2194 Default entries MUST not be removed." 2195 INDEX { efmCuPme2BProfileIndex } 2196 ::= { efmCuPme2BProfileTable 1 } 2198 EfmCuPme2BProfileEntry ::= 2199 SEQUENCE { 2200 efmCuPme2BProfileIndex ProfileIndex, 2201 efmCuPme2BProfileDescr SnmpAdminString, 2202 efmCuPme2BRegion INTEGER, 2203 efmCuPme2BDataRate Unsigned32, 2204 efmCuPme2BPower Unsigned32, 2205 efmCuPme2BConstellation INTEGER, 2206 efmCuPme2BProfileRowStatus RowStatus 2207 } 2209 efmCuPme2BProfileIndex OBJECT-TYPE 2210 SYNTAX ProfileIndex 2211 MAX-ACCESS not-accessible 2212 STATUS current 2213 DESCRIPTION 2214 "2BASE-TL PME Profile index. 2215 This object is the unique index associated with this profile. 2216 Entries in this table are referenced via efmCuAdminProfile 2217 or efmCuPmeAdminProfile objects." 2218 ::= { efmCuPme2BProfileEntry 1 } 2220 efmCuPme2BProfileDescr OBJECT-TYPE 2221 SYNTAX SnmpAdminString (SIZE(0..255)) 2222 MAX-ACCESS read-create 2223 STATUS current 2224 DESCRIPTION 2225 "A textual string containing information about 2BASE-TL PME 2226 Profile. The string MAY include information about data rate 2227 and spectral limitations of this particular profile." 2228 ::= { efmCuPme2BProfileEntry 2 } 2230 efmCuPme2BRegion OBJECT-TYPE 2231 SYNTAX INTEGER { 2232 region1(1), 2233 region2(2) 2234 } 2235 MAX-ACCESS read-create 2236 STATUS current 2237 DESCRIPTION 2238 "Power Spectral Density (PSD) Regional settings as 2239 specified in the relevant Regional Annex of [G.991.2]. 2240 Regional settings place limitations on the max allowed 2241 data rate, power and constellation. 2243 Possible values for this object are: 2244 region1 -- Annexes A and F (e.g. North America) 2245 region2 -- Annexes B and G (e.g. Europe) 2247 Changing of the Region must be performed when the link is 2248 Down. 2249 Attempts to change this object MUST be rejected with 2250 the error inconsistentValue, if the link is Up or 2251 Initializing. 2253 If a Clause 45 MDIO Interface to the PME is present, then this 2254 object maps to the Region bits in the 2B general 2255 parameter register." 2256 REFERENCE 2257 "[802.3ah] 45.2.1.42" 2258 ::= { efmCuPme2BProfileEntry 3 } 2260 efmCuPme2BDataRate OBJECT-TYPE 2261 SYNTAX Unsigned32(0..5696) 2262 UNITS "Kbps" 2263 MAX-ACCESS read-create 2264 STATUS current 2265 DESCRIPTION 2266 "2BASE-TL PME Data Rate. 2267 The rate is fixed when the value of this object is n x 64Kbps, 2268 where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM. 2269 The value of 0 in the administrative profile means that data 2270 rate is not fixed but is adaptive and should be set to the 2271 maximum attainable rate during line probing, under the 2272 spectral limitations placed by the efmCuPme2BRegion. 2274 If a Clause 45 MDIO Interface to the PME is present, then this 2275 object maps to the Min/Max Data Rate1 bits in the 2B PMD 2276 parameters register. 2278 This object MUST be maintained in a persistent manner." 2280 REFERENCE 2281 "[802.3ah] 45.2.1.43" 2282 ::= { efmCuPme2BProfileEntry 4 } 2284 efmCuPme2BPower OBJECT-TYPE 2285 SYNTAX Unsigned32(0|10..42) 2286 UNITS "0.5 dBm" 2287 MAX-ACCESS read-create 2288 STATUS current 2289 DESCRIPTION 2290 "Signal Transmit Power. Multiple of 0.5dBm. 2291 The value of 0 in the administrative profile means that the 2292 signal transmit power is not fixed and should be set to 2293 maximize the attainable rate, under the spectral limitations 2294 placed by the efmCuPme2BRegion. 2296 Changing of the Signal Transmit Power must be performed when 2297 the link is Down. Attempts to change this object MUST be 2298 rejected with the error inconsistentValue, if the link is Up 2299 or Initializing. 2301 If a Clause 45 MDIO Interface to the PME is present, then this 2302 object will map to the Power1 bits in the 2B PMD 2303 parameters register" 2304 REFERENCE 2305 "[802.3ah] 45.2.1.43" 2306 ::= { efmCuPme2BProfileEntry 5 } 2308 efmCuPme2BConstellation OBJECT-TYPE 2309 SYNTAX INTEGER { 2310 adaptive(0), 2311 tcpam16(1), 2312 tcpam32(2) 2313 } 2314 MAX-ACCESS read-create 2315 STATUS current 2316 DESCRIPTION 2317 "TCPAM Constellation of the 2BASE-TL PME. 2318 The possible values are: 2319 adaptive(0) - either 16- or 32-TCPAM 2320 tcpam16(1) - 16-TCPAM 2321 tcpam32(2) - 32-TCPAM 2323 The value of adaptive(0) in the administrative profile means 2324 that the constellation is not fixed and should be set to 2325 maximize the attainable rate, under the spectral limitations 2326 placed by the efmCuPme2BRegion. 2328 If a Clause 45 MDIO Interface to the PME is present, then this 2329 object map to the Constellation1 bits in the 2B general 2330 parameter register." 2331 REFERENCE 2332 "[802.3ah] 45.2.1.43" 2333 ::= { efmCuPme2BProfileEntry 6 } 2335 efmCuPme2BProfileRowStatus OBJECT-TYPE 2336 SYNTAX RowStatus 2337 MAX-ACCESS read-create 2338 STATUS current 2339 DESCRIPTION 2340 "This object controls creation/deletion of the associated 2341 entry in efmCuPme2BProfileTable per the semantics of 2342 RowStatus. 2343 If an 'active' entry is referenced via efmCuAdminProfile or 2344 efmCuPmeAdminProfile, the entry MUST remain 'active' until all 2345 references are removed." 2346 ::= { efmCuPme2BProfileEntry 7 } 2348 -- 10PASS-TS specific PME group 2350 efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } 2352 efmCuPme10PProfileTable OBJECT-TYPE 2353 SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry 2354 MAX-ACCESS not-accessible 2355 STATUS current 2356 DESCRIPTION 2357 "This table supports definitions of configuration profiles for 2358 10PassTL PMEs. 2359 First 22 entries in this table SHALL always be defined as 2360 follows (see 802.3ah Annex 62B.3): 2361 -------+--------+----+---------+-----+------------ 2362 Profile Bandplan UPBO BandNotch DRate URate 2363 Index PSDMask# p# p# p# p# 2364 -------+--------+----+---------+-----+------------ 2365 1 1 3 2,6,10,11 20 20(default) 2366 2 13 5 0 20 20 2367 3 1 1 0 20 20 2368 4 16 0 0 100 100 2369 5 16 0 0 70 50 2370 6 6 0 0 50 10 2371 7 17 0 0 30 30 2372 8 8 0 0 30 5 2373 9 4 0 0 25 25 2374 10 4 0 0 15 15 2375 11 23 0 0 10 10 2376 12 23 0 0 5 5 2377 13 16 0 2,5,9,11 100 100 2378 14 16 0 2,5,9,11 70 50 2379 15 6 0 2,6,10,11 50 10 2380 16 17 0 2,5,9,11 30 30 2381 17 8 0 2,6,10,11 30 5 2382 18 4 0 2,6,10,11 25 25 2383 19 4 0 2,6,10,11 15 15 2384 20 23 0 2,5,9,11 10 10 2385 21 23 0 2,5,9,11 5 5 2386 22 30 0 0 200 50 2388 These default entries SHALL be created by during agent 2389 initialization and MUST not be deleted. 2391 Entries following the first 22, can be dynamically created and 2392 deleted, to provide custom administrative (configuration) 2393 profiles and automatic operating profiles. 2395 This table MUST be maintained in a persistent manner." 2396 REFERENCE 2397 "[802.3ah] Annex 62B.3, 30.11.2.1.6" 2398 ::= { efmCuPme10P 1 } 2400 efmCuPme10PProfileEntry OBJECT-TYPE 2401 SYNTAX EfmCuPme10PProfileEntry 2402 MAX-ACCESS not-accessible 2403 STATUS current 2404 DESCRIPTION 2405 "Each entry corresponds to a single 10PASS-TS PME 2406 profile. 2407 Each profile contains a set of parameters, used either for 2408 configuration or representation of a 10PASS-TS PME. 2409 In case a particular profile is referenced via 2410 efmCuPmeAdminProfile object (or efmCuAdminProfile if 2411 efmCuPmeAdminProfile is zero), it represent the desired 2412 parameters the 10PassTS-O PME initialization. 2413 If a profile is referenced via efmCuPmeOperProfile object, 2414 it represents current operating parameters of the PME. 2416 Profiles may be created/deleted using the row creation/ 2417 deletion mechanism via efmCuPme10PProfileRowStatus. If an 2418 'active' entry is referenced, the entry MUST remain 'active' 2419 until all references are removed. 2420 Default entries MUST not be removed." 2421 INDEX { efmCuPme10PProfileIndex } 2422 ::= { efmCuPme10PProfileTable 1 } 2424 EfmCuPme10PProfileEntry ::= 2425 SEQUENCE { 2426 efmCuPme10PProfileIndex ProfileIndex, 2427 efmCuPme10PProfileDescr SnmpAdminString, 2428 efmCuPme10PBandplanPSDMskProfile INTEGER, 2429 efmCuPme10PUPBOReferenceProfile INTEGER, 2430 efmCuPme10PBandNotchProfiles BITS, 2431 efmCuPme10PPayloadURateProfile INTEGER, 2432 efmCuPme10PPayloadDRateProfile INTEGER, 2433 efmCuPme10PProfileRowStatus RowStatus 2434 } 2436 efmCuPme10PProfileIndex OBJECT-TYPE 2437 SYNTAX ProfileIndex 2438 MAX-ACCESS not-accessible 2439 STATUS current 2440 DESCRIPTION 2441 "10PASS-TS PME Profile Index. 2442 This object is the unique index associated with this profile. 2443 Entries in this table are referenced via efmCuAdminProfile or 2444 efmCuPmeAdminProfile." 2445 ::= { efmCuPme10PProfileEntry 1 } 2447 efmCuPme10PProfileDescr OBJECT-TYPE 2448 SYNTAX SnmpAdminString (SIZE(0..255)) 2449 MAX-ACCESS read-create 2450 STATUS current 2451 DESCRIPTION 2452 "A textual string containing information about 10PASS-TS PME 2453 Profile. The string MAY include information about data rate 2454 and spectral limitations of this particular profile." 2455 ::= { efmCuPme10PProfileEntry 2 } 2457 efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE 2458 SYNTAX INTEGER { 2459 profile1(1), 2460 profile2(2), 2461 profile3(3), 2462 profile4(4), 2463 profile5(5), 2464 profile6(6), 2465 profile7(7), 2466 profile8(8), 2467 profile9(9), 2468 profile10(10), 2469 profile11(11), 2470 profile12(12), 2471 profile13(13), 2472 profile14(14), 2473 profile15(15), 2474 profile16(16), 2475 profile17(17), 2476 profile18(18), 2477 profile19(19), 2478 profile20(20), 2479 profile21(21), 2480 profile22(22), 2481 profile23(23), 2482 profile24(24), 2483 profile25(25), 2484 profile26(26), 2485 profile27(27), 2486 profile28(28), 2487 profile29(29) 2488 } 2489 MAX-ACCESS read-create 2490 STATUS current 2491 DESCRIPTION 2492 "10PASS-TS PME Bandplan and PSD Mask profile, 2493 as specified in 802.3ah Annex 62A. Possible values are: 2494 --------------+------------------------+-----------+--------- 2495 Profile Name PSD Mask Bands Bandplan 2496 --------------+------------------------+-----------+--------- 2497 profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A 2498 profile2(2) - T1.424/T-U P1 FTTEx.M1 2499 profile3(3) - T1.424/T-U P1 FTTCab.M2 2500 profile4(4) - T1.424/T-U P1 FTTEx.M2 2501 profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U 2502 profile6(6) - T1.424/T-U P1 FTTEx.M1 2503 profile7(7) - T1.424/T-U P1 FTTCab.M2 2504 profile8(8) - T1.424/T-U P1 FTTEx.M2 2505 profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x 2506 profile10(10) - T1.424/T-U P1 FTTEx.M1 2507 profile11(11) - T1.424/T-U P1 FTTCab.M2 2508 profile12(12) - T1.424/T-U P1 FTTEx.M2 2509 profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B 2510 profile14(14) - TS1 101 270-1 Pcab.M1.B 2511 profile15(15) - TS1 101 270-1 Pex.P1.M1 2512 profile16(16) - TS1 101 270-1 Pex.P2.M1 2513 profile17(17) - TS1 101 270-1 Pcab.M2 2514 profile18(18) - TS1 101 270-1 Pex.P1.M2 2515 profile19(19) - TS1 101 270-1 Pex.P2.M2 2516 profile20(20) - TS1 101 270-1 Pcab.M1.A U/D/U/D/x 2517 profile21(21) - TS1 101 270-1 Pcab.M1.B 2518 profile22(22) - TS1 101 270-1 Pex.P1.M1 2519 profile23(23) - TS1 101 270-1 Pex.P2.M1 2520 profile24(24) - TS1 101 270-1 Pcab.M2 2521 profile25(25) - TS1 101 270-1 Pex.P1.M2 2522 profile26(26) - TS1 101 270-1 Pex.P2.M2 2523 profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F 2524 profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN) 2525 profile29(29) - G.993.1 F.1.2.3 (PSD reduction) 2527 This object maps to the aBandplanPSDMaskProfile attribute 2528 in Clause 30." 2529 REFERENCE 2530 "[802.3ah] Annex 62A, 30.5.1.1.22" 2531 ::= { efmCuPme10PProfileEntry 3 } 2533 efmCuPme10PUPBOReferenceProfile OBJECT-TYPE 2534 SYNTAX INTEGER { 2535 profile1(1), 2536 profile2(2), 2537 profile3(3), 2538 profile4(4), 2539 profile5(5), 2540 profile6(6), 2541 profile7(7), 2542 profile8(8), 2543 profile9(9) 2544 } 2545 MAX-ACCESS read-create 2546 STATUS current 2547 DESCRIPTION 2548 "10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD 2549 Profile, as specified in 802.3ah Annex 62A. Possible values 2550 are: 2551 profile1(1) - T1.424/T-U Noise A M1 2552 profile2(2) - T1.424/T-U Noise A M2 2553 profile3(3) - T1.424/T-U Noise F M1 2554 profile4(4) - T1.424/T-U Noise F M2 2555 profile5(5) - ETSI TS 101 270-1 Noise A&B 2556 profile6(6) - ETSI TS 101 270-1 Noise C 2557 profile7(7) - ETSI TS 101 270-1 Noise D 2558 profile8(8) - ETSI TS 101 270-1 Noise E 2559 profile9(9) - ETSI TS 101 270-1 Noise F 2561 This object maps to the aUPBOReferenceProfile attribute 2562 in Clause 30." 2563 REFERENCE 2564 "[802.3ah] Annex 62A.3.4, 30.5.1.1.23" 2565 ::= { efmCuPme10PProfileEntry 4 } 2567 efmCuPme10PBandNotchProfiles OBJECT-TYPE 2568 SYNTAX BITS { 2569 profile0(0), 2570 profile1(1), 2571 profile2(2), 2572 profile3(3), 2573 profile4(4), 2574 profile5(5), 2575 profile6(6), 2576 profile7(7), 2577 profile8(8), 2578 profile9(9), 2579 profile10(10), 2580 profile11(11) 2581 } 2582 MAX-ACCESS read-create 2583 STATUS current 2584 DESCRIPTION 2585 "10PASS-TS PME Egress Control Band Notch Profile bitmap, 2586 as specified in 802.3ah Annex 62A. Possible values are: 2587 --------------+---------+----------+-----------+------+----- 2588 Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF 2589 Table Table Table (MHz) (MHz) 2590 --------------+---------+----------+-----------+------+----- 2591 profile0(0) - no profile 2592 profile1(1) - F-5 #01 - - 1.810 1.825 2593 profile2(2) - 6-2 15-1 17 1.810 2.000 2594 profile3(3) - F-5 #02 - - 1.907 1.912 2595 profile4(4) - F-5 #03 - - 3.500 3.575 2596 profile5(5) - 6-2 - 17 3.500 3.800 2597 profile6(6) - - 15-1 - 3.500 4.000 2598 profile7(7) - F-5 #04 - - 3.747 3.754 2599 profile8(8) - F-5 #05 - - 3.791 3.805 2600 profile9(9) - 6-2 - 17 7.000 7.100 2601 profile10(10) - F-5 #06 15-1 - 7.000 7.300 2602 profile11(11) - 6-2 15-1 1 10.100 10.150 2604 Any combination of profiles can be specified by ORing 2605 individual profiles, for example value of 0x0622 selects 2606 profiles 2,6,10 and 11. 2608 This object maps to the aBandNotchProfile attribute 2609 in Clause 30." 2610 REFERENCE 2611 "[802.3ah] Annex 62A.3.5, 30.5.1.1.19" 2612 ::= { efmCuPme10PProfileEntry 5 } 2614 efmCuPme10PPayloadURateProfile OBJECT-TYPE 2615 SYNTAX INTEGER { 2616 profile5(5), 2617 profile10(10), 2618 profile15(15), 2619 profile20(20), 2620 profile25(25), 2621 profile30(30), 2622 profile50(50), 2623 profile70(70), 2624 profile100(100) 2625 } 2626 MAX-ACCESS read-create 2627 STATUS current 2628 DESCRIPTION 2629 "10PASS-TS PME Upstream Payload Rate Profile, 2630 as specified in 802.3ah Annex 62A. Possible values are: 2631 profile5(5) - 2.5 Mbps 2632 profile10(10) - 5 Mbps 2633 profile15(15) - 7.5 Mbps 2634 profile20(20) - 10 Mbps 2635 profile25(25) - 12.5 Mbps 2636 profile30(30) - 15 Mbps 2637 profile50(50) - 25 Mbps 2638 profile70(70) - 35 Mbps 2639 profile100(100) - 50 Mbps 2641 Each value represents a target for the PME's Upstream Payload 2642 Bitrate as seen at the MII. If the payload rate of the 2643 selected profile cannot be achieved based on the loop 2644 environment, bandplan and PSD mask, the PME initialization 2645 SHALL fail. 2647 This object maps to the aPayloadRateProfileUpstream 2648 attribute in Clause 30." 2649 REFERENCE 2650 "[802.3ah] Annex 62A.3.6, 30.5.1.1.20" 2651 ::= { efmCuPme10PProfileEntry 6 } 2653 efmCuPme10PPayloadDRateProfile OBJECT-TYPE 2654 SYNTAX INTEGER { 2655 profile5(5), 2656 profile10(10), 2657 profile15(15), 2658 profile20(20), 2659 profile25(25), 2660 profile30(30), 2661 profile50(50), 2662 profile70(70), 2663 profile100(100), 2664 profile140(140), 2665 profile200(200) 2666 } 2667 MAX-ACCESS read-create 2668 STATUS current 2669 DESCRIPTION 2670 "10PASS-TS PME Downstream Payload Rate Profile, 2671 as specified in 802.3ah Annex 62A. Possible values are: 2672 profile5(5) - 2.5 Mbps 2673 profile10(10) - 5 Mbps 2674 profile15(15) - 7.5 Mbps 2675 profile20(20) - 10 Mbps 2676 profile25(25) - 12.5 Mbps 2677 profile30(30) - 15 Mbps 2678 profile50(50) - 25 Mbps 2679 profile70(70) - 35 Mbps 2680 profile100(100) - 50 Mbps 2681 profile140(140) - 70 Mbps 2682 profile200(200) - 100 Mbps 2684 Each value represents a target for the PME's Downstream 2685 Payload Bitrate as seen at the MII. If the payload rate of 2686 the selected profile cannot be achieved based on the loop 2687 environment, bandplan and PSD mask, the PME initialization 2688 SHALL fail. 2690 This object maps to the aPayloadRateProfileDownstream 2691 attribute in Clause 30." 2692 REFERENCE 2693 "[802.3ah] Annex 62A.3.6, 30.5.1.1.21" 2694 ::= { efmCuPme10PProfileEntry 7 } 2696 efmCuPme10PProfileRowStatus OBJECT-TYPE 2697 SYNTAX RowStatus 2698 MAX-ACCESS read-create 2699 STATUS current 2700 DESCRIPTION 2701 "This object controls creation/deletion of the associated 2702 entry in efmCuPme10PProfileTable per the semantics of 2703 RowStatus. 2704 If an active entry is referenced via efmCuAdminProfile or 2705 efmCuPmeAdminProfile, the entry MUST remain 'active' until 2706 all references are removed." 2707 ::= { efmCuPme10PProfileEntry 8 } 2709 efmCuPme10PStatusTable OBJECT-TYPE 2710 SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry 2711 MAX-ACCESS not-accessible 2712 STATUS current 2713 DESCRIPTION 2714 "Table reflecting status of EFMCu 10PASS-TS PMEs (modems)." 2715 ::= { efmCuPme10P 2 } 2717 efmCuPme10PStatusEntry OBJECT-TYPE 2718 SYNTAX EfmCuPme10PStatusEntry 2719 MAX-ACCESS not-accessible 2720 STATUS current 2721 DESCRIPTION 2722 "An entry in the EFMCu 10PASS-TS PME Status table." 2723 AUGMENTS { efmCuPmeStatusEntry } 2724 ::= { efmCuPme10PStatusTable 1 } 2726 EfmCuPme10PStatusEntry ::= 2727 SEQUENCE { 2728 efmCuPme10PElectricalLength Integer32, 2729 efmCuPme10PFECCorrectedBlocks Counter32, 2730 efmCuPme10PFECUncorrectedBlocks Counter32 2731 -- EdNote: To be continued 2732 } 2734 efmCuPme10PElectricalLength OBJECT-TYPE 2735 SYNTAX Integer32(0..8192|65535) 2736 UNITS "m" 2737 MAX-ACCESS read-only 2738 STATUS current 2739 DESCRIPTION 2740 "Electrical Length in meters as perceived by the 10PASS-TS PME 2741 after the link is established. 2742 The value of 65535 is returned if the link is Down or 2743 Initializing or the PME is unable to estimate the Electrical 2744 Length. 2746 If a Clause 45 MDIO Interface to the PME is present, then this 2747 object maps to the 10P Electrical Length register" 2748 REFERENCE 2749 "[802.3ah] 45.2.1.21" 2750 ::= { efmCuPme10PStatusEntry 1 } 2752 efmCuPme10PFECCorrectedBlocks OBJECT-TYPE 2753 SYNTAX Counter32 2754 MAX-ACCESS read-only 2755 STATUS current 2756 DESCRIPTION 2757 "A count of received and corrected FEC codewords in 10PASS-TS 2758 PME. 2760 This object maps to aPMEFECCorrectedBlocks attribute in 2761 clause 30. 2763 If a Clause 45 MDIO Interface to the PMA/PMD is present, 2764 then this object maps to the 10P FEC correctable errors 2765 register" 2766 REFERENCE 2767 "[802.3ah] 45.2.1.22" 2768 ::= { efmCuPme10PStatusEntry 2 } 2770 efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE 2771 SYNTAX Counter32 2772 MAX-ACCESS read-only 2773 STATUS current 2774 DESCRIPTION 2775 "A count of received FEC codewords in 10PASS-TS PME, which are 2776 uncorrectable. 2778 This object maps to aPMEFECUncorrectableBlocks attribute in 2779 clause 30. 2781 If a Clause 45 MDIO Interface to the PMA/PMD is present, 2782 then this object maps to the 10P FEC uncorrectable errors 2783 register" 2784 REFERENCE 2785 "[802.3ah] 45.2.1.23" 2786 ::= { efmCuPme10PStatusEntry 3 } 2788 -- ifAvailableStackTable for use in Discovery 2790 ifAvailableStackTable OBJECT-TYPE 2791 SYNTAX SEQUENCE OF IfAvailableStackEntry 2792 MAX-ACCESS not-accessible 2793 STATUS current 2794 DESCRIPTION 2795 "This table, modeled after ifStackTable from [IF-MIB], 2796 contains information on the possible 'on-top-of' 2797 relationships between the multiple sub-layers of network 2798 interfaces (as opposed to actual relationships in 2799 ifStackTable). In particular, it contains information on 2800 which PCS ports (sublayers) can possibly run 'on top of' 2801 which PMEs (sublayers), as determined by cross-connect 2802 capability of the EFMCu device, where each sub-layer 2803 corresponds to a conceptual row in the ifTable. For example, 2804 when the PCS port with ifIndex value x can be connected 2805 to run on top of the PME with ifIndex value y, then this table 2806 contains: 2808 ifAvailableStackStatus.x.y=capable 2810 Note that there's always at least on PCS for each PME and at 2811 least one PME for each PCS in the EFMCu devices, with 2812 efmCuPAFCapacity and efmCuPeerPAFCapacity indicating 2813 maximum number of PMEs which can be aggregated by local and 2814 remote PCS port respectively. 2815 This table is read only as it describes device capability" 2816 REFERENCE 2817 "ifStackTable of RFC 2863" 2818 ::= { efmCuObjects 3 } 2820 ifAvailableStackEntry OBJECT-TYPE 2821 SYNTAX IfAvailableStackEntry 2822 MAX-ACCESS not-accessible 2823 STATUS current 2824 DESCRIPTION 2825 "Information on a particular relationship between two 2826 sub-layers, specifying that one sub-layer (PCS) runs on 'top' 2827 of the other sub-layer (PME). Each sub-layer corresponds to a 2828 conceptual row in the ifTable (interface index for PCS and 2829 PME respectively)." 2830 INDEX { 2831 ifAvailableStackHigherLayer, 2832 ifAvailableStackLowerLayer 2833 } 2834 ::= { ifAvailableStackTable 1 } 2836 IfAvailableStackEntry ::= 2837 SEQUENCE { 2838 ifAvailableStackHigherLayer InterfaceIndex, 2839 ifAvailableStackLowerLayer InterfaceIndex, 2840 ifAvailableStackStatus INTEGER 2841 } 2843 ifAvailableStackHigherLayer OBJECT-TYPE 2844 SYNTAX InterfaceIndex 2845 MAX-ACCESS not-accessible 2846 STATUS current 2847 DESCRIPTION 2848 "The value of ifIndex corresponding to the higher sub-layer 2849 of the 'cross-connect capability' relationship, i.e., the 2850 PCS sub-layer which MAY run on 'top' of the PME sub-layer 2851 identified by the corresponding instance of 2852 ifAvailableStackLowerLayer." 2853 ::= { ifAvailableStackEntry 1 } 2855 ifAvailableStackLowerLayer OBJECT-TYPE 2856 SYNTAX InterfaceIndex 2857 MAX-ACCESS not-accessible 2858 STATUS current 2859 DESCRIPTION 2860 "The value of ifIndex corresponding to the lower sub-layer 2861 of the 'cross-connect capability' relationship, i.e., the 2862 PME sub-layer which MAY run 'below' the PCS sub-layer 2863 identified by the corresponding instance of 2864 ifAvailableStackHigherLayer." 2865 ::= { ifAvailableStackEntry 2 } 2867 ifAvailableStackStatus OBJECT-TYPE 2868 SYNTAX INTEGER { 2869 capable(1), 2870 outOfService(2) 2871 } 2872 MAX-ACCESS read-only 2873 STATUS current 2874 DESCRIPTION 2875 "The status of the 'cross-connect capability' relationship 2876 between two sub-layers. The following values are defined: 2877 capable(1) - the PME sub-layer interface, identified by 2878 the ifAvailableStackLowerLayer MAY be 2879 connected to run 'below' the PCS sub-layer 2880 interface, identified by the 2881 ifAvailableStackLowerLayer. 2882 outOfService(2) - the PME sub-layer interface cannot be 2883 connected due to unavailability of the 2884 interface. 2886 Note that PME availability per PCS, indicated by 'capable' 2887 value, can be constrained by other parameters, 2888 for example by aggregation capacity of a PCS or by the PME in 2889 question being already connected to another PCS. So, in 2890 order to ensure that a particular PME can be connected to the 2891 PCS, all respective parameters (e.g. ifAvailableStackTable, 2892 ifStackTable and efmCuPAFCapacity) SHALL be inspected. 2894 This object is read only, unlike ifStackStatus, as it 2895 describes the device capability." 2896 ::= { ifAvailableStackEntry 3 } 2898 -- 2899 -- Conformance Statements 2900 -- 2901 efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } 2903 efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } 2905 -- Object Groups 2907 efmCuBasicGroup OBJECT-GROUP 2908 OBJECTS { 2909 efmCuPAFSupported, 2910 efmCuAdminProfile, 2911 efmCuTargetDataRate, 2912 efmCuTargetSnrMgn, 2913 efmCuPortSide, 2914 efmCuFltStatus 2915 } 2916 STATUS current 2917 DESCRIPTION 2918 "A collection of objects required for all of EFMCu ports." 2919 ::= { efmCuGroups 1 } 2921 efmCuPAFGroup OBJECT-GROUP 2922 OBJECTS { 2923 efmCuPeerPAFSupported, 2924 efmCuPAFCapacity, 2925 efmCuPeerPAFCapacity, 2926 efmCuPAFAdminState, 2927 efmCuPAFDiscoveryCode, 2928 efmCuPAFRemoteDiscoveryCode, 2929 efmCuNumPMEs, 2930 ifAvailableStackStatus 2931 } 2932 STATUS current 2933 DESCRIPTION 2934 "A collection of objects required for optional PME 2935 Aggregation Function (PAF) and PAF discovery in EFMCu ports." 2936 ::= { efmCuGroups 2 } 2938 ifStackCapabilityGroup OBJECT-GROUP 2939 OBJECTS { 2940 ifAvailableStackStatus 2941 } 2942 STATUS current 2943 DESCRIPTION 2944 "A collection of objects providing information on 2945 the stacking capability of MIB-II interfaces." 2946 ::= { efmCuGroups 3 } 2948 efmCuPAFErrorsGroup OBJECT-GROUP 2949 OBJECTS { 2950 efmCuPAFInErrors, 2951 efmCuPAFInSmallFragments, 2952 efmCuPAFInLargeFragments, 2953 efmCuPAFInBadFragments, 2954 efmCuPAFInLostFragments, 2955 efmCuPAFInLostStarts, 2956 efmCuPAFInLostEnds, 2957 efmCuPAFInOverflows 2958 } 2959 STATUS current 2960 DESCRIPTION 2961 "A collection of objects supporting optional error counters 2962 of PAF on EFMCu ports." 2963 ::= { efmCuGroups 4 } 2965 efmCuPmeGroup OBJECT-GROUP 2966 OBJECTS { 2967 efmCuPmeAdminProfile, 2968 efmCuPmeOperStatus, 2969 efmCuPmeFltStatus, 2970 efmCuPmeSubTypesSupported, 2971 efmCuPmeAdminSubType, 2972 efmCuPmeOperSubType, 2973 efmCuPAFRemoteDiscoveryCode, 2974 efmCuPmeOperProfile, 2975 efmCuPmeSnrMgn, 2976 efmCuPmePeerSnrMgn, 2977 efmCuPmeLineAtn, 2978 efmCuPmePeerLineAtn, 2979 efmCuPmeTCCodingErrors, 2980 efmCuPmeTCCrcErrors, 2981 efmCuPmeThreshLineAtn, 2982 efmCuPmeThreshSnrMgn 2983 } 2984 STATUS current 2985 DESCRIPTION 2986 "A collection of objects providing information about 2987 a 2BASE-TL/10PASS-TS PME." 2988 ::= { efmCuGroups 5 } 2990 efmCuAlarmConfGroup OBJECT-GROUP 2991 OBJECTS { 2992 efmCuThreshLowBandwidth, 2993 efmCuLowBandwidthEnable, 2994 efmCuPmeThreshLineAtn, 2995 efmCuPmeLineAtnCrossingEnable, 2996 efmCuPmeThreshSnrMgn, 2997 efmCuPmeSnrMgnCrossingEnable, 2998 efmCuPmeLineAtnCrossingEnable, 2999 efmCuPmeDeviceFaultEnable, 3000 efmCuPmeConfigInitFailEnable, 3001 efmCuPmeProtocolInitFailEnable 3002 -- efmCuPmeThreshES, 3003 -- efmCuPmethreshSES, 3004 -- efmCuPmeThreshCRCanomalies, 3005 -- efmCuPmeThreshLOSWS, 3006 -- efmCuPmeThreshUAS 3007 } 3008 STATUS current 3009 DESCRIPTION 3010 "A collection of objects required for configuration of alarm 3011 thresholds and notifications in EFMCu ports." 3012 ::= { efmCuGroups 6 } 3014 efmCuNotificationGroup NOTIFICATION-GROUP 3015 NOTIFICATIONS { 3016 efmCuLowBandwidth, 3017 efmCuPmeLineAtnCrossing, 3018 efmCuPmeSnrMgnCrossing, 3019 efmCuPmeDeviceFault, 3020 efmCuPmeConfigInitFailure, 3021 efmCuPmeProtocolInitFailure 3022 -- efmCuPmePerfES, 3023 -- efmCuPmePerfSES, 3024 -- efmCuPmePerfCRCanomalies, 3025 -- efmCuPmePerfLOSWS, 3026 -- efmCuPmePerfUAS, 3027 -- efmCuPmeDeviceFault, 3028 -- efmCuPmeLocalPowerLoss 3029 } 3030 STATUS current 3031 DESCRIPTION 3032 "This group supports notifications of significant conditions 3033 associated with EFMCu ports." 3034 ::= { efmCuGroups 7 } 3036 efmCuPme2BProfileGroup OBJECT-GROUP 3037 OBJECTS { 3038 efmCuPme2BProfileDescr, 3039 efmCuPme2BRegion, 3040 efmCuPme2BDataRate, 3041 efmCuPme2BPower, 3042 efmCuPme2BConstellation, 3043 efmCuPme2BProfileRowStatus 3044 } 3045 STATUS current 3046 DESCRIPTION 3047 "A collection of objects that constitute a configuration 3048 profile for configuration of 2BASE-TL ports." 3049 ::= { efmCuGroups 8 } 3051 efmCuPme10PProfileGroup OBJECT-GROUP 3052 OBJECTS { 3053 efmCuPme10PProfileDescr, 3054 efmCuPme10PBandplanPSDMskProfile, 3055 efmCuPme10PUPBOReferenceProfile, 3056 efmCuPme10PBandNotchProfiles, 3057 efmCuPme10PPayloadURateProfile, 3058 efmCuPme10PPayloadDRateProfile, 3059 efmCuPme10PProfileRowStatus 3060 } 3061 STATUS current 3062 DESCRIPTION 3063 "A collection of objects that constitute a configuration 3064 profile for configuration of 10PASS-TS ports." 3065 ::= { efmCuGroups 9 } 3067 efmCuPme10PStatusGroup OBJECT-GROUP 3068 OBJECTS { 3069 efmCuPme10PElectricalLength, 3070 efmCuPme10PFECCorrectedBlocks, 3071 efmCuPme10PFECUncorrectedBlocks 3072 } 3073 STATUS current 3074 DESCRIPTION 3075 "A collection of objects providing status information 3076 specific to 10PASS-TS PMEs." 3077 ::= { efmCuGroups 10 } 3079 -- Compliance Statements 3081 efmCuCompliance MODULE-COMPLIANCE 3082 STATUS current 3083 DESCRIPTION 3084 "The compliance statement for 2BASE-TL/10PASS-TS interfaces. 3085 Compliance with the following external compliance statements 3086 is prerequisite: 3088 MIB Module Compliance Statement 3089 ---------- -------------------- 3090 IF-MIB ifCompliance3 3091 IF-INVERTED-STACK-MIB ifInvCompliance 3092 EtherLike-MIB dot3Compliance2 3093 MAU-MIB mauModIfCompl3" 3095 MODULE -- this module 3096 MANDATORY-GROUPS { 3097 efmCuBasicGroup, 3098 efmCuPmeGroup, 3099 efmCuAlarmConfGroup, 3100 efmCuNotificationGroup 3101 } 3103 GROUP efmCuPme2BProfileGroup 3104 DESCRIPTION 3105 "Support for this group is only required for implementations 3106 supporting 2BASE-TL Phy." 3108 GROUP efmCuPme10PProfileGroup 3109 DESCRIPTION 3110 "Support for this group is only required for implementations 3111 supporting 10PASS-TS Phy." 3113 GROUP efmCuPAFGroup 3114 DESCRIPTION 3115 "Support for this group is only required for 3116 implementations supporting PME Aggregation Function (PAF)." 3118 GROUP ifStackCapabilityGroup 3119 DESCRIPTION 3120 "Support for this group is optional for implementations 3121 supporting layered interfaces architecture with 3122 flexible cross-connect between the layers." 3124 GROUP efmCuPAFErrorsGroup 3125 DESCRIPTION 3126 "Support for this group is optional for implementations 3127 supporting PME Aggregation Function (PAF)." 3129 GROUP efmCuPme10PStatusGroup 3130 DESCRIPTION 3131 "Support for this group is optional for implementations 3132 supporting 10PASS-TS Phy." 3134 OBJECT efmCuPmeSubTypesSupported 3135 SYNTAX BITS { 3136 ieee2BaseTLO(0), 3137 ieee2BaseTLR(1), 3138 ieee10PassTSO(2), 3139 ieee10PassTSR(3) 3140 } 3141 DESCRIPTION 3142 "Support for all subtypes is not required. However at least 3143 one value SHALL be supported" 3145 OBJECT efmCuPmeAdminSubType 3146 MIN-ACCESS read-only 3147 DESCRIPTION 3148 "Write access is not required (needed only for PMEs 3149 supporting more than a single subtype, e.g. 3150 ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and 3151 ieee10PassTSR)" 3153 OBJECT efmCuTargetSnrMgn 3154 MIN-ACCESS read-only 3155 DESCRIPTION 3156 "Write access is optional. For PHYs without write access 3157 the target SNR margin SHALL be fixed at 5dB for 2BASE-TL 3158 and 6dB for 10PASS-TS." 3160 -- EdNote: To be Continued 3162 ::= { efmCuCompliances 1 } 3163 END 3165 6. Security Considerations 3167 There is a number of managed objects defined in this MIB module that 3168 have a MAX-ACCESS clause of read-write or read-create. Most objects 3169 are writeable only when the link is Down. Writing to these objects 3170 can have potentially disruptive effects on network operation, for 3171 example: 3173 o Changing of efmCuPmeAdminSubType MAY lead to a potential locking 3174 of the link, as peer PMEs of the same sub-type cannot exchange 3175 handshake messages. 3177 o Changing of efmCuPAFAdminState to enabled MAY lead to a potential 3178 locking of the link, if the peer Phy does not support PAF. 3180 o Changing of efmCuPAFDiscoveryCode, before the discovery operation, 3181 MAY lead to a wrongful discovery, for example when two -O ports 3182 are connected to the same multi-PME -R port and both -O ports have 3183 the same Discovery register value. 3185 o Changing PCS or PME configuration parameters (e.g. profile of a 3186 PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead 3187 to anything from link quality and rate degradation to a complete 3188 link initialization failure, as ability of an EFMCu port to 3189 support a particular configuration depends on the copper 3190 environment. 3192 o Activation of a PME can cause a severe degradation of service for 3193 another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk 3194 from the newly activated PME. 3196 o Removal of a PME from an operationally 'up' EFMCu port, 3197 aggregating several PMEs, MAY cause port's rate degradation 3199 The user of this MIB module must therefore be aware that support for 3200 SET operations in a non-secure environment without proper protection 3201 can have a negative effect on network operations. 3203 The readable objects in this MIB module (i.e., those with MAX-ACCESS 3204 other than not-accessible) may be considered sensitive in some 3205 environments since, collectively, they provide information about the 3206 performance of network interfaces and can reveal some aspects of 3207 their configuration. In particular since EFMCu can be carried over 3208 Unshielded Twisted Pair (UTP) voice grade copper in a bundle with 3209 other pairs belonging to another operator/customer, it is 3210 theoretically possible to evasdrop to an EFMCu transmission simply by 3211 "listening" to a cross-talk from an EFMCu pair, especially if the 3212 parameters of the EFMCu link in question are known. In such 3213 environments it is important to control even GET and NOTIFY access to 3214 these objects and possibly even to encrypt their values when sending 3215 them over the network via SNMP. 3217 SNMP versions prior to SNMPv3 did not include adequate security. 3218 Even if the network itself is secure (for example by using IPSec), 3219 even then, there is no control as to who on the secure network is 3220 allowed to access and GET/SET (read/change/create/delete) the objects 3221 in this MIB module. 3223 It is RECOMMENDED that implementers consider the security features as 3224 provided by the SNMPv3 framework (see [RFC3410], section 8), 3225 including full support for the SNMPv3 cryptographic mechanisms (for 3226 authentication and privacy). 3228 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3229 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3230 enable cryptographic security. It is then a customer/operator 3231 responsibility to ensure that the SNMP entity giving access to an 3232 instance of this MIB module is properly configured to give access to 3233 the objects only to those principals (users) that have legitimate 3234 rights to indeed GET or SET (change/create/delete) them. 3236 7. IANA Considerations 3238 The two new values of dot3MauType (dot3MauType2BaseTL and 3239 dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit 3240 definitions (b2BaseTL and b10PassTS) SHALL be defined by the IANA in 3241 the IANA-MAU-TC-MIB module (see [I-D.ietf-hubmib-rfc3636bis]) before 3242 this document is published as an RFC. 3244 8. Acknowledgments 3246 This document was produced by the IETF Ethernet Interfaces and Hub 3247 MIB Working Group, whose efforts were greatly advanced by the 3248 contributions of the following people (in alphabetical order): 3250 Dan Romascanu 3252 Mathias Riess 3254 Matt Squire 3256 Mike Heard 3258 Udi Ashkenazi 3260 9. References 3262 9.1. Normative References 3264 [802.3ah] IEEE, "IEEE Standard for Information technology - 3265 Telecommunications and information exchange between 3266 systems - Local and metropolitan area networks - Specific 3267 requirements - Part 3: Carrier Sense Multiple Access with 3268 Collision Detection (CSMA/CD) Access Method and Physical 3269 Layer Specifications - Amendment: Media Access Control 3270 Parameters, Physical Layers and Management Parameters for 3271 Subscriber Access Networks", IEEE Std 802.3ah-2004, 3272 September 2004. 3274 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3275 Requirement Levels", BCP 14, RFC 2119, March 1997. 3277 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3278 McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of 3279 Management Information Version 2 (SMIv2)", STD 58, 3280 RFC 2578, April 1999. 3282 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3283 McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 3284 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 3286 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3287 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3288 April 1999. 3290 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3291 "Introduction and Applicability Statements for Internet- 3292 Standard Management Framework", RFC 3410, December 2002. 3294 9.2. Informative References 3296 [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line 3297 (SHDSL) transceivers", ITU-T Recommendation G.991.2, 3298 December 2003. 3300 [G.993.1] ITU-T, "Very High speed Digital Subscriber Line 3301 transceivers", ITU-T Recommendation G.993.1, June 2004. 3303 [I-D.ietf-adslmib-gshdslbis] 3304 Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed 3305 Objects for G.shdsl.bis Lines", 3306 draft-ietf-adslmib-gshdslbis-11 (work in progress), 3307 May 2005. 3309 [I-D.ietf-hubmib-efm-epon-mib] 3310 Khermosh, L., "Managed Objects for the Ethernet Passive 3311 Optical Networks", draft-ietf-hubmib-efm-epon-mib-03 (work 3312 in progress), March 2005. 3314 [I-D.ietf-hubmib-efm-mib] 3315 Squire, M., "Ethernet in the First Mile (EFM) Common MIB", 3316 draft-ietf-hubmib-efm-mib-03 (work in progress), 3317 March 2005. 3319 [I-D.ietf-hubmib-rfc3636bis] 3320 Beili, E., "Definitions of Managed Objects for IEEE 802.3 3321 Medium Attachment Units (MAUs)", 3322 draft-ietf-hubmib-rfc3636bis-02 (work in progress), 3323 October 2005. 3325 [IANAifType-MIB] 3326 Internet Assigned Numbers Authority (IANA), "IANAifType 3327 Textual Convention definition", 3328 http://www.iana.org/assignments/ianaiftype-mib. 3330 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3331 MIB", RFC 2863, June 2000. 3333 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 3334 Extension to the Interfaces Group MIB", RFC 2864, 3335 June 2000. 3337 [RFC3635] Flick, J., "Definitions of Managed Objects for the 3338 Ethernet-like Interface Types", RFC 3635, September 2003. 3340 [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object 3341 Extensions for Very High Speed Digital Subscriber Lines 3342 (VDSL) Using Multiple Carrier Modulation (MCM) Line 3343 Coding", RFC 4070, May 2005. 3345 Author's Address 3347 Edward Beili 3348 Actelis Networks 3349 Bazel 25 3350 Petach-Tikva 3351 Israel 3353 Phone: +972-3-924-3491 3354 Email: edward.beili@actelis.com 3356 Intellectual Property Statement 3358 The IETF takes no position regarding the validity or scope of any 3359 Intellectual Property Rights or other rights that might be claimed to 3360 pertain to the implementation or use of the technology described in 3361 this document or the extent to which any license under such rights 3362 might or might not be available; nor does it represent that it has 3363 made any independent effort to identify any such rights. Information 3364 on the procedures with respect to rights in RFC documents can be 3365 found in BCP 78 and BCP 79. 3367 Copies of IPR disclosures made to the IETF Secretariat and any 3368 assurances of licenses to be made available, or the result of an 3369 attempt made to obtain a general license or permission for the use of 3370 such proprietary rights by implementers or users of this 3371 specification can be obtained from the IETF on-line IPR repository at 3372 http://www.ietf.org/ipr. 3374 The IETF invites any interested party to bring to its attention any 3375 copyrights, patents or patent applications, or other proprietary 3376 rights that may cover technology that may be required to implement 3377 this standard. Please address the information to the IETF at 3378 ietf-ipr@ietf.org. 3380 Disclaimer of Validity 3382 This document and the information contained herein are provided on an 3383 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3384 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3385 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3386 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3387 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3388 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3390 Copyright Statement 3392 Copyright (C) The Internet Society (2005). This document is subject 3393 to the rights, licenses and restrictions contained in BCP 78, and 3394 except as set forth therein, the authors retain all their rights. 3396 Acknowledgment 3398 Funding for the RFC Editor function is currently provided by the 3399 Internet Society.