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