idnits 2.17.1 draft-ietf-adslmib-adslext-09.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 36 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 11. Security Considerations' ) ** 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.) ** The document seems to lack an Authors' Addresses Section. ** There are 97 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([RFC2573], [RFC1906], [RFC1155], [21], [RFC2574], [RFC2575], [RFC1157], [RFC2580], [23], [RFC2026], [RFC2863], [RFC2028], [ITUG992.1], [RFC2578], [RFC1212], [RFC2579], [RFC1901], [RFC1215], [ITUG.992.1], [RFC2662], [ITUG.992.2], [ITUG.997.1], [RFC2570], [RFC2571], [RFC1905], [RFC2572]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 104: '... SHALL be down(2) when the ADSL line...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1124 has weird spacing: '...eshTrap notif...' -- 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 (April 23, 2002) is 8011 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 section? 'RFC2662' on line 1591 looks like a reference -- Missing reference section? 'RFC2571' on line 1494 looks like a reference -- Missing reference section? 'RFC1155' on line 1458 looks like a reference -- Missing reference section? 'RFC1212' on line 1466 looks like a reference -- Missing reference section? 'RFC1215' on line 1469 looks like a reference -- Missing reference section? 'RFC2578' on line 1513 looks like a reference -- Missing reference section? 'RFC2579' on line 1518 looks like a reference -- Missing reference section? 'RFC2580' on line 1522 looks like a reference -- Missing reference section? 'RFC1157' on line 1462 looks like a reference -- Missing reference section? 'RFC1901' on line 1472 looks like a reference -- Missing reference section? 'RFC1906' on line 1480 looks like a reference -- Missing reference section? 'RFC2572' on line 1498 looks like a reference -- Missing reference section? 'RFC2574' on line 1505 looks like a reference -- Missing reference section? 'RFC1905' on line 1476 looks like a reference -- Missing reference section? 'RFC2573' on line 1502 looks like a reference -- Missing reference section? 'RFC2575' on line 1509 looks like a reference -- Missing reference section? 'RFC2570' on line 1490 looks like a reference -- Missing reference section? 'ITU G.997.1' on line 1454 looks like a reference -- Missing reference section? 'ITU G.992.1' on line 1446 looks like a reference -- Missing reference section? 'ITU G.992.2' on line 1450 looks like a reference -- Missing reference section? 'ITU G992.1' on line 157 looks like a reference -- Missing reference section? 'RFC 2662' on line 942 looks like a reference -- Missing reference section? 'RFC2026' on line 1484 looks like a reference -- Missing reference section? 'RFC2028' on line 1487 looks like a reference -- Missing reference section? 'RFC2863' on line 1529 looks like a reference -- Missing reference section? '21' on line 1563 looks like a reference -- Missing reference section? '23' on line 1564 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 4 warnings (==), 29 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT ADSL Line Extension MIB Faye Ly 2 Pedestal Networks 3 Gregory Bathrick 4 Nokia 5 April 23, 2002 7 Definitions of Extension Managed Objects 8 for ADSL Lines 10 April 23, 2002 12 draft-ietf-adslmib-adslext-09.txt 14 1. Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that other 21 groups may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as ``work in progress.'' 28 Copyright Notice 30 Copyright (C) The Internet Society (2002). All Rights Reserved. 32 2. Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 In particular, it describes additional managed objects used for 37 managing Asymmetric Digital Subscriber Line (ADSL) interfaces not 38 covered by the ADSL Line MIB [RFC2662]. 40 3. The SNMP Network Management Framework 41 The SNMP Management Framework presently consists of five major 42 components: 44 o An overall architecture, described in RFC 2571 [RFC2571]. 46 o Mechanisms for describing and naming objects and events 47 for the purpose of management. The first version of this 48 Structure of Management Information (SMI) is called SMIv1 49 and described in STD 16, RFC 1155 [RFC1155], STD 16, 50 RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 51 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 52 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 54 o Message protocols for transferring management information. 55 The first version of the SNMP message protocol is called 56 SNMPv1 and described in STD 15, RFC 1157[RFC1157]. A second 57 version of the SNMP message protocol, which is not an Internet 58 standards track protocol, is called SNMPv2c and described in RFC 59 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 60 message protocol is called SNMPv3 and described in RFC 1906 61 [RFC1906], RFC2572 [RFC2572] and RFC 2574 [RFC2574]. 63 o Protocol operations for accessing management information. The 64 first set of protocol operations and associated PDU formats is 65 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 66 operations and associated PDU formats is described in RFC 1905 67 [RFC1905]. 69 o A set of fundamental applications described in RFC 2573 70 [RFC2573] and the view-based access control mechanism described in 71 RFC 2575 [RFC2575]. 73 A more detailed introduction to the current SNMP Management Framework 74 can be found in RFC 2570 [RFC2570]. 76 Managed objects are accessed via a virtual information store, termed 77 the Management Information Base or MIB. Objects in the MIB are 78 defined using the mechanisms defined in the SMI. 80 This memo specifies a MIB module that is compliant to the SMIv2. A 81 MIB conforming to the SMIv1 can be produced through the appropriate 82 translations. The resulting translated MIB must be semantically 83 equivalent, except where objects or events are omitted because no 84 translation is possible (use of Counter64). Some machine-readable 85 information in SMIv2 will be converted into textual descriptions in 86 SMIv1 during the translation process. However, this loss of machine 87 readable information is not considered to change the semantics of the 88 MIB. 90 4. Introduction 92 The purpose of this memo is to define a supplemental set of managed 93 objects that is not covered by ADSL Line MIB as defined in [RFC2662]. 94 This memo addresses the additional objects defined in ITU G.997.1 95 [ITU G.997.1]. 97 5. Relationship of ADSL Line Extension MIB with standard MIBs 99 This section outlines the relationship of ADSL Line Extension MIB 100 with other MIBs described in RFCs and in their various degrees 101 of standardization. In regards to these relationship, the ADSL Line 102 Extension MIB follows conventions as used by the ADSL Line MIB with 103 one exception. The value of the RFC2863 object, ifOperstatus, 104 SHALL be down(2) when the ADSL line interface is in power state L3 as 105 defined in ITU G.992.1 [ITU G.992.1], which means no power. Its value 106 shall be up(1) if the ADSL line interface is in power state L0 (power on) 107 [ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU G.992.1] is 108 not applicable. 110 6. Conventions used in the MIB 112 6.1 Structure 114 The MIB is organized to follow the same structure of the ADSL Line 115 MIB [RFC2662]. 117 6.2 Additional Managed Objects 119 Objects specific to the management of ADSL G.Lite as defined in 120 ITU G.992.2 [ITU G.992.2] are: 122 - ADSL Transceiver Unit - Central Office End (ATU-C) 123 Transmission System and Line Mode 124 - Power Management 125 - Counters for Fast Retrains and Failed Fast Retrains 126 - Counters for Severe Error Second-line and Unavailable Second 127 - Alternative profile configuration for the Dual line mode interface 129 Besides the management of G.Lite, another object has been added in 130 order to manage the ADSL line profile. The object is the line mode 131 configuration. 133 6.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 135 The adslLineConfigTable needs to be extended to cover control of the 136 ATU-C ADSL Transmission system. Three objects are defined to monitor 137 and configure the transmission mode as well as the actual line mode: 139 - Capability 140 - Configuration 141 - Actual Status 143 Transmission modes can further determine the line mode of the ADSL 144 interface. For example, if g9921PotsNonOverlapped(2) is the actual 145 value of the ADSL interface, the interface is operating in Full rate 146 ADSL. If the interface is set to g9922PotsOverlapped(9), the 147 interface is operating in G.Lite mode. 149 The transmission mode and the corresponding line mode are defined as: 151 Transmission mode Line Mode 152 ---------------------------------------------------------- 153 Regional Std. (ANSI T1.413) Full 154 [ANSI T1.413] 155 Regional Std. (ETSI DTS/TM06006) Full 156 [ETSI DTS/TM06006] 157 G.992.1 [ITU G992.1] POTS non-overlapped Full 158 G.992.1 POTS overlapped Full 159 G.992.1 Integrated Services Digital 160 Network (ISDN) non-overlapped Full 161 G.992.1 ISDN overlapped Full 162 G.992.1 TCM-ISDN non-overlapped Full 163 G.992.1 TCM-ISDN overlapped Full 164 G.992.2 POTS non-overlapped G.Lite 165 G.992.2 POTS overlapped G.Lite 166 G.992.2 with TCM-ISDN G.Lite 167 non-overlapped 168 G.992.2 with TCM-ISDN overlapped G.Lite 169 G.992.1 TCM-ISDN symmetric Full 171 Table 1: Transmission Mode and Line Mode 173 In case more than one bit is configured for an ADSL interface and 174 both Full and G.Lite modes are selected, the interface is said to 175 be configured in the dual mode. Only one bit can be set in the Actual 176 object that reflects the actual mode of transmission as well as the 177 line mode. 179 6.2.2 Power Management 181 There are three possible power states for each managed ADSL interface 182 operating in the G.Lite mode. L0 is power on, L1 is power on but 183 reduced and L3 is power off. Power state cannot be configured by an 184 operator but it can be viewed via the ifOperStatus object for the 185 managed ADSL interface. The value of the object ifOperStatus is 186 set to down(2) if the ADSL interface is in power state L3 and is set 187 to up(1) if the ADSL line interface is in power state L0 or L1. 189 An ADSL line power state, if the interface is operating in the 190 G.Lite mode, can also be monitored by the adslLineGlitePowerState 191 object defined in the ADSL Line Extension table. The value of the 192 object enumerates the three power states attainable by the managed 193 interface. 195 6.2.3 Fast Retrain Parameters 197 Section 7.4.15 [ITU G.997.1] specifies fast retrain parameters. Fast 198 retrain parameters include two counters: fast retrain count and failed 199 fast retrain count. These two counters have been added to all 200 performance tables. 202 6.2.4 Counters for Severely Errored Second-line and Unavailable 203 Seconds-line 205 ITU G.997.1 sections 6.2.1.1.7 and 6.2.1.1.9 specify two counters that 206 are not covered by the ADSL Line MIB [RFC2662]. These two counters 207 (severely errored seconds-line and unavailable seconds-line) are added 208 to all the performance tables. 210 Unavailable seconds counts cumulative number of seconds in which the 211 interface was unavailable during the measured period. This counter 212 does not include the seconds in which unavailability was caused solely 213 by fast retrains and failed fast retrains. Fast retrains and failed 214 fast retrains are considered to be part of the normal network operation 215 and thus are not counted as unavailable errors. 217 6.2.5 Counters, Interval Buckets and Thresholds 219 For physical-level events, there are counters, current 15-minute and 220 one (up to 96) 15-minute history bucket(s) of "interval-counters", as 221 well as current and previous 1-day interval-counters. Threshold 222 notification can be configured for each physical-layer current 223 15-minute bucket. 225 There is no requirement for an agent to ensure fixed relationship 226 between the start of a fifteen minute and any wall clock; however 227 some implementations may align the fifteen-minute intervals with 228 quarter hours. Likewise, an implementation may choose to align one 229 day intervals with start of a day. 231 Separate tables are provided for the 96 interval-counters. They are 232 indexed by {ifIndex, AdslAtu*IntervalNumber}. 234 Counters are not reset when an ATU-C or ATU-R is reinitialized, only 235 when the agent is reset or reinitialized (or under specific request 236 outside the scope of this MIB). 238 The 15-minute event counters are of type PerfCurrentCount and 239 PerfIntervalCount. The 1-day event counters are of type 240 AdslPerfCurrDayCount and AdslPerfPrevDayCount. Both 15-minute and 1- 241 day time elapsed counters are of type AdslPerfTimeElapsed. 243 6.2.6 Alternative profile configuration for the dual line mode 244 interface 246 The object, adslLineConfProfileDualLite, is used only when the interface 247 (the ADSL line and, if applicable, channel) is configured as dual mode, 248 that is, the object adslLineTransAtucConfig is configured with one or 249 more full-rate modes and one or more G.Lite modes. 251 The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used as 252 the primary full-rate profile. The newly added object in this MIB 253 module, adslLineConfProfileDualLite, is used to describe and configure 254 the G.Lite profile. Note that if one or more full-rate modes are 255 configured, or only G.Lite modes are configured, only the original 256 full-rate profile is needed. The dual-mode profile object is only 257 needed when both full-rate and G.Lite profiles are needed. In this 258 case, it will be set to the value of adslLineConfProfile when 'dynamic' 259 profiles are implemented. 261 When 'static' profiles are implemented, however, similar to the case 262 of the object, adslLineConfProfileName [RFC2662], this object's value 263 will need to algorithmically represent the line. In this case, the 264 value of the line's ifIndex plus a value indicating the line mode type 265 (e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name 266 is a string of the concatenation of ifIndex and one of the follow 267 values: Full or Lite. This string will be fixed-length (i.e., 14) with 268 leading zero(s). For example, the profile name for ifIndex that 269 equals '15' and is a full rate line, it will be '0000000015Full'. 271 7. Conformance and Compliance 273 See the conformance and compliance statements within the information 274 module. 276 8. Definitions 278 ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN 279 IMPORTS 280 Counter32, 281 Integer32, 282 NOTIFICATION-TYPE, 283 MODULE-IDENTITY, 284 OBJECT-TYPE FROM SNMPv2-SMI 285 MODULE-COMPLIANCE, OBJECT-GROUP, 286 NOTIFICATION-GROUP FROM SNMPv2-CONF 287 TEXTUAL-CONVENTION FROM SNMPv2-TC 288 PerfCurrentCount, 289 PerfIntervalCount FROM PerfHist-TC-MIB 290 AdslPerfCurrDayCount, 291 AdslPerfPrevDayCount FROM ADSL-TC-MIB 292 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 293 adslLineAlarmConfProfileEntry, 294 adslLineConfProfileEntry, 295 adslAturIntervalEntry, 296 adslAturPerfDataEntry, 297 adslAtucIntervalEntry, 298 adslAtucPerfDataEntry, 299 adslLineEntry, 300 adslMIB FROM ADSL-LINE-MIB 301 ; 303 adslExtMIB MODULE-IDENTITY 305 LAST-UPDATED "200204231200Z" 307 ORGANIZATION "IETF ADSL MIB Working Group" 309 CONTACT-INFO 310 " 311 Faye Ly 312 Pedestal Networks 313 3045 Park Boulevard 314 Palo Alto, CA 94306 315 Tel: +1 650-475-1274 316 Fax: +1 650-688-3119 317 E-Mail: faye@pedestalnetworks.com 319 Gregory Bathrick 320 NOKIA High Speed Access Nodes 321 1310 Redwood Way, 322 Petaluma, CA 94954 323 Tel: +1 707-793-7030 324 Fax: +1 707-792-0850 325 E-Mail: greg.bathrick@nokia.com 326 IETF ADSL MIB Working Group 327 328 " 329 DESCRIPTION 330 "This MIB Module is a supplement to the ADSL-LINE-MIB 331 [RFC2662]." 332 REVISION "200204231200Z" 333 DESCRIPTION "Initial Version, published as RFC xxxx. This MIB 334 module supplements the ADSL-LINE-MIB [RFC2662]." 335 ::= { adslMIB 3 } 337 adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 } 339 AdslTransmissionModeType ::= TEXTUAL-CONVENTION 340 STATUS current 341 DESCRIPTION 342 "A set of ADSL line transmission modes, with one bit 343 per mode. The notes (F) and (L) denote Full-Rate 344 and G.Lite respectively: 345 Bit 00 : Regional Std. (ANSI T1.413) (F) 346 Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) 347 Bit 02 : G.992.1 POTS non-overlapped (F) 348 Bit 03 : G.992.1 POTS overlapped (F) 349 Bit 04 : G.992.1 ISDN non-overlapped (F) 350 Bit 05 : G.992.1 ISDN overlapped (F) 351 Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) 352 Bit 07 : G.992.1 TCM-ISDN overlapped (F) 353 Bit 08 : G.992.2 POTS non-overlapped (L) 354 Bit 09 : G.992.2 POTS overlapped (L) 355 Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L) 356 Bit 11 : G.992.2 with TCM-ISDN overlapped (L) 357 Bit 12 : G.992.1 TCM-ISDN symmetric (F) 358 " 359 SYNTAX BITS { 360 ansit1413(0), 361 etsi(1), 362 q9921PotsNonOverlapped(2), 363 q9921PotsOverlapped(3), 364 q9921IsdnNonOverlapped(4), 365 q9921isdnOverlapped(5), 366 q9921tcmIsdnNonOverlapped(6), 367 q9921tcmIsdnOverlapped(7), 368 q9922potsNonOverlapeed(8), 369 q9922potsOverlapped(9), 370 q9922tcmIsdnNonOverlapped(10), 371 q9922tcmIsdnOverlapped(11), 372 q9921tcmIsdnSymmetric(12) 373 } 375 adslLineExtTable OBJECT-TYPE 376 SYNTAX SEQUENCE OF AdslLineExtEntry 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "This table is an extension of RFC2662. It 381 contains ADSL line configuration and 382 monitoring information. This includes the ADSL 383 line's capabilities and actual ADSL transmission 384 system." 385 ::= { adslExtMibObjects 17 } 387 adslLineExtEntry OBJECT-TYPE 388 SYNTAX AdslLineExtEntry 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "An entry extends the adslLineEntry defined in 393 [RFC2662]. Each entry corresponds to an ADSL 394 line." 395 AUGMENTS { adslLineEntry } 396 ::= { adslLineExtTable 1 } 398 AdslLineExtEntry ::= 399 SEQUENCE { 400 adslLineTransAtucCap AdslTransmissionModeType, 401 adslLineTransAtucConfig AdslTransmissionModeType, 402 adslLineTransAtucActual AdslTransmissionModeType, 403 adslLineGlitePowerState INTEGER, 404 adslLineConfProfileDualLite SnmpAdminString 405 } 407 adslLineTransAtucCap OBJECT-TYPE 408 SYNTAX AdslTransmissionModeType 409 MAX-ACCESS read-only 410 STATUS current 411 DESCRIPTION 412 "The transmission modes, represented by a 413 bitmask that the ATU-C is capable of 414 supporting. The modes available are limited 415 by the design of the equipment." 416 REFERENCE "Section 7.3.2 ITU G.997.1" 417 ::= { adslLineExtEntry 1 } 419 adslLineTransAtucConfig OBJECT-TYPE 420 SYNTAX AdslTransmissionModeType 421 MAX-ACCESS read-write 422 STATUS current 423 DESCRIPTION 424 "The transmission modes, represented by a bitmask, 425 currently enabled by the ATU-C. The manager can 426 only set those modes that are supported by the 427 ATU-C. An ATU-C's supported modes are provided by 428 AdslLineTransAtucCap." 429 REFERENCE "Section 7.3.2 ITU G.997.1" 430 ::= { adslLineExtEntry 2 } 432 adslLineTransAtucActual OBJECT-TYPE 433 SYNTAX AdslTransmissionModeType 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "The actual transmission mode of the ATU-C. 438 During ADSL line initialization, the ADSL 439 Transceiver Unit - Remote terminal end (ATU-R) 440 will determine the mode used for the link. 441 This value will be limited a single transmission 442 mode that is a subset of those modes enabled 443 by the ATU-C and denoted by adslLineTransAtucConfig. 444 After an initialization has occurred, its mode is 445 saved as the 'Current' mode and is persistence 446 should the link go down. This object returns 0 447 (i.e. BITS with no mode bit set) if the mode is 448 not known." 449 REFERENCE "Section 7.3.2 ITU G.997.1 " 450 ::= { adslLineExtEntry 3 } 452 adslLineGlitePowerState OBJECT-TYPE 453 SYNTAX INTEGER { 454 none(1), 455 l0(2), -- L0 Power on 456 l1(3), -- L1 Power on but reduced 457 l3(4) -- L3 Power off 458 } 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The value of this object specifies the power 463 state of this interface. L0 is power on, L1 is 464 power on but reduced and L3 is power off. Power 465 state cannot be configured by an operator but it 466 can be viewed via the ifOperStatus object for the 467 managed ADSL interface. The value of the object 468 ifOperStatus is set to down(2) if the ADSL interface 469 is in power state L3 and is set to up(1) if the ADSL 470 line interface is in power state L0 or L1. If the 471 object adslLineTransAtucActual is set to a G.992.2 472 (G.Lite)-type transmission mode, the value of 473 this object will be one of the valid power 474 states: L0(2), L1(3), or L3(4). Otherwise, its 475 value will be none(1)." 476 ::= { adslLineExtEntry 4 } 478 adslLineConfProfileDualLite OBJECT-TYPE 479 SYNTAX SnmpAdminString 480 MAX-ACCESS read-write 481 STATUS current 482 DESCRIPTION 483 "This object extends the definition an ADSL line and 484 associated channels (when applicable) for cases when 485 it is configured in dual mode, and operating in a 486 G.Lite-type mode as denoted by 487 adslLineTransAtucActual. Dual mode exists when the 488 object, adslLineTransAtucConfig, is configured with 489 one or more full-rate modes and one or more G.Lite 490 modes simultaneously. 492 When 'dynamic' profiles are implemented, the value of 493 object is equal to the index of the applicable row in 494 the ADSL Line Configuration Profile Table, 495 AdslLineConfProfileTable defined in ADSL-MIB 496 [RFC2662]. 498 In the case when dual-mode has not been enabled, the 499 value of the object will be equal to the value of the 500 object adslLineConfProfile [RFC2662]. 502 When `static' profiles are implemented, in much 503 like the case of the object, adslLineConfProfileName 504 [RFC2662], this object's value will need to 505 algorithmically represent the characteristics of the 506 line. In this case, the value of the line's ifIndex 507 plus a value indicating the line mode type 508 (e.g., G.Lite, Full-rate) will be used. Therefore, 509 the profile's name is a string concatenating the 510 ifIndex and one of the follow values: Full or Lite. 511 This string will be fixed-length (i.e., 14) with 512 leading zero(s). For example, the profile name for 513 ifIndex that equals '15' and is a full rate line, it 514 will be '0000000015Full'." 515 REFERENCE "Section 5.4 Profiles, RFC 2662" 516 ::= { adslLineExtEntry 5 } 518 adslAtucPerfDataExtTable OBJECT-TYPE 519 SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry 520 MAX-ACCESS not-accessible 521 STATUS current 522 DESCRIPTION 523 "This table extends adslAtucPerfDataTable [RFC2662] 524 with additional ADSL physical line counter 525 information such as unavailable seconds-line and 526 severely errored seconds-line." 527 ::= { adslExtMibObjects 18 } 529 adslAtucPerfDataExtEntry OBJECT-TYPE 530 SYNTAX AdslAtucPerfDataExtEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "An entry extends the adslAtucPerfDataEntry defined 535 in [RFC2662]. Each entry corresponds to an ADSL 536 line." 537 AUGMENTS { adslAtucPerfDataEntry } 538 ::= { adslAtucPerfDataExtTable 1 } 540 AdslAtucPerfDataExtEntry ::= 541 SEQUENCE { 542 adslAtucPerfStatFastR Counter32, 543 adslAtucPerfStatFailedFastR Counter32, 544 adslAtucPerfStatSesL Counter32, 545 adslAtucPerfStatUasL Counter32, 546 adslAtucPerfCurr15MinFastR PerfCurrentCount, 547 adslAtucPerfCurr15MinFailedFastR PerfCurrentCount, 548 adslAtucPerfCurr15MinSesL PerfCurrentCount, 549 adslAtucPerfCurr15MinUasL PerfCurrentCount, 550 adslAtucPerfCurr1DayFastR AdslPerfCurrDayCount, 551 adslAtucPerfCurr1DayFailedFastR AdslPerfCurrDayCount, 552 adslAtucPerfCurr1DaySesL AdslPerfCurrDayCount, 553 adslAtucPerfCurr1DayUasL AdslPerfCurrDayCount, 554 adslAtucPerfPrev1DayFastR AdslPerfPrevDayCount, 555 adslAtucPerfPrev1DayFailedFastR AdslPerfPrevDayCount, 556 adslAtucPerfPrev1DaySesL AdslPerfPrevDayCount, 557 adslAtucPerfPrev1DayUasL AdslPerfPrevDayCount 558 } 560 adslAtucPerfStatFastR OBJECT-TYPE 561 SYNTAX Counter32 562 UNITS "line retrains" 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The value of this object reports the count of 567 the number of fast line bs since last 568 agent reset." 569 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 570 ::= { adslAtucPerfDataExtEntry 1 } 572 adslAtucPerfStatFailedFastR OBJECT-TYPE 573 SYNTAX Counter32 574 UNITS "line retrains" 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The value of this object reports the count of 579 the number of failed fast line retrains since 580 last agent reset." 581 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 582 ::= { adslAtucPerfDataExtEntry 2 } 584 adslAtucPerfStatSesL OBJECT-TYPE 585 SYNTAX Counter32 586 UNITS "seconds" 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "The value of this object reports the count of 591 the number of severely errored seconds-line since 592 last agent reset." 593 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 594 ::= { adslAtucPerfDataExtEntry 3 } 596 adslAtucPerfStatUasL OBJECT-TYPE 597 SYNTAX Counter32 598 UNITS "seconds" 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The value of this object reports the count of 603 the number of unavailable seconds-line since 604 last agent reset." 605 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 606 ::= { adslAtucPerfDataExtEntry 4 } 608 adslAtucPerfCurr15MinFastR OBJECT-TYPE 609 SYNTAX PerfCurrentCount 610 UNITS "seconds" 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "For the current 15-minute interval, 615 adslAtucPerfCurr15MinFastR reports the current 616 number of seconds during which there have been 617 fast retrains." 618 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 619 ::= { adslAtucPerfDataExtEntry 5 } 621 adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE 622 SYNTAX PerfCurrentCount 623 UNITS "seconds" 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "For the current 15-minute interval, 628 adslAtucPerfCurr15MinFailedFastR reports the current 629 number of seconds during which there have been 630 failed fast retrains." 631 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 632 ::= { adslAtucPerfDataExtEntry 6 } 634 adslAtucPerfCurr15MinSesL OBJECT-TYPE 635 SYNTAX PerfCurrentCount 636 UNITS "seconds" 637 MAX-ACCESS read-only 638 STATUS current 639 DESCRIPTION 640 "For the current 15-minute interval, 641 adslAtucPerfCurr15MinSesL reports the current 642 number of seconds during which there have been 643 severely errored seconds-line." 644 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 645 ::= { adslAtucPerfDataExtEntry 7 } 647 adslAtucPerfCurr15MinUasL OBJECT-TYPE 648 SYNTAX PerfCurrentCount 649 UNITS "seconds" 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "For the current 15-minute interval, 654 adslAtucPerfCurr15MinUasL reports the current 655 number of seconds during which there have been 656 unavailable seconds-line." 657 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 658 ::= { adslAtucPerfDataExtEntry 8 } 660 adslAtucPerfCurr1DayFastR OBJECT-TYPE 661 SYNTAX AdslPerfCurrDayCount 662 UNITS "seconds" 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "For the current day as measured by 667 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 668 adslAtucPerfCurr1DayFastR reports the number 669 of seconds during which there have been 670 fast retrains." 671 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 672 ::= { adslAtucPerfDataExtEntry 9 } 674 adslAtucPerfCurr1DayFailedFastR OBJECT-TYPE 675 SYNTAX AdslPerfCurrDayCount 676 UNITS "seconds" 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "For the current day as measured by 681 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 682 adslAtucPerfCurr1DayFailedFastR reports the 683 number of seconds during which there have been 684 failed fast retrains." 685 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 686 ::= { adslAtucPerfDataExtEntry 10 } 688 adslAtucPerfCurr1DaySesL OBJECT-TYPE 689 SYNTAX AdslPerfCurrDayCount 690 UNITS "seconds" 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "For the current day as measured by 695 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 696 adslAtucPerfCurr1DaySesL reports the 697 number of seconds during which there have been 698 severely errored seconds-line." 699 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 700 ::= { adslAtucPerfDataExtEntry 11 } 702 adslAtucPerfCurr1DayUasL OBJECT-TYPE 703 SYNTAX AdslPerfCurrDayCount 704 UNITS "seconds" 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "For the current day as measured by 709 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 710 adslAtucPerfCurr1DayUasL reports the 711 number of seconds during which there have been 712 unavailable seconds-line." 713 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 714 ::= { adslAtucPerfDataExtEntry 12 } 716 adslAtucPerfPrev1DayFastR OBJECT-TYPE 717 SYNTAX AdslPerfPrevDayCount 718 UNITS "seconds" 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "For the previous day, adslAtucPerfPrev1DayFastR 723 reports the number of seconds during which there 724 were fast retrains." 725 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 726 ::= { adslAtucPerfDataExtEntry 13 } 728 adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE 729 SYNTAX AdslPerfPrevDayCount 730 UNITS "seconds" 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "For the previous day, adslAtucPerfPrev1DayFailedFastR 735 reports the number of seconds during which there 736 were failed fast retrains." 737 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 738 ::= { adslAtucPerfDataExtEntry 14 } 740 adslAtucPerfPrev1DaySesL OBJECT-TYPE 741 SYNTAX AdslPerfPrevDayCount 742 UNITS "seconds" 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "For the previous day, adslAtucPerfPrev1DaySesL 747 reports the number of seconds during which there 748 were severely errored seconds-line." 749 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 750 ::= { adslAtucPerfDataExtEntry 15 } 752 adslAtucPerfPrev1DayUasL OBJECT-TYPE 753 SYNTAX AdslPerfPrevDayCount 754 UNITS "seconds" 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "For the previous day, adslAtucPerfPrev1DayUasL 759 reports the number of seconds during which there 760 were unavailable seconds-line." 761 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 762 ::= { adslAtucPerfDataExtEntry 16 } 764 adslAtucIntervalExtTable OBJECT-TYPE 765 SYNTAX SEQUENCE OF AdslAtucIntervalExtEntry 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION 769 "This table provides one row for each ATU-C 770 performance data collection interval for 771 ADSL physical interfaces whose 772 IfEntries' ifType is equal to adsl(94)." 773 ::= { adslExtMibObjects 19 } 775 adslAtucIntervalExtEntry OBJECT-TYPE 776 SYNTAX AdslAtucIntervalExtEntry 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION "An entry in the 780 adslAtucIntervalExtTable." 781 AUGMENTS { adslAtucIntervalEntry } 782 ::= { adslAtucIntervalExtTable 1 } 784 AdslAtucIntervalExtEntry ::= 785 SEQUENCE { 786 adslAtucIntervalFastR PerfIntervalCount, 787 adslAtucIntervalFailedFastR PerfIntervalCount, 788 adslAtucIntervalSesL PerfIntervalCount, 789 adslAtucIntervalUasL PerfIntervalCount 790 } 792 adslAtucIntervalFastR OBJECT-TYPE 793 SYNTAX PerfIntervalCount 794 UNITS "seconds" 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "For the current interval, adslAtucIntervalFastR 799 reports the current number of seconds during which 800 there have been fast retrains." 801 ::= { adslAtucIntervalExtEntry 1 } 803 adslAtucIntervalFailedFastR OBJECT-TYPE 804 SYNTAX PerfIntervalCount 805 UNITS "seconds" 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "For the each interval, adslAtucIntervalFailedFastR 810 reports the number of seconds during which 811 there have been failed fast retrains." 812 ::= { adslAtucIntervalExtEntry 2 } 814 adslAtucIntervalSesL OBJECT-TYPE 815 SYNTAX PerfIntervalCount 816 UNITS "seconds" 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "For the each interval, adslAtucIntervalSesL 821 reports the number of seconds during which 822 there have been severely errored seconds-line." 823 ::= { adslAtucIntervalExtEntry 3 } 825 adslAtucIntervalUasL OBJECT-TYPE 826 SYNTAX PerfIntervalCount 827 UNITS "seconds" 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "For the each interval, adslAtucIntervalUasL 832 reports the number of seconds during which 833 there have been unavailable seconds-line." 834 ::= { adslAtucIntervalExtEntry 4 } 836 adslAturPerfDataExtTable OBJECT-TYPE 837 SYNTAX SEQUENCE OF AdslAturPerfDataExtEntry 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "This table contains ADSL physical line counters 842 not defined in the adslAturPerfDataTable 843 from the ADSL-LINE-MIB [RFC2662]." 844 ::= { adslExtMibObjects 20 } 846 adslAturPerfDataExtEntry OBJECT-TYPE 847 SYNTAX AdslAturPerfDataExtEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "An entry extends the adslAturPerfDataEntry defined 852 in [RFC2662]. Each entry corresponds to an ADSL 853 line." 854 AUGMENTS { adslAturPerfDataEntry } 856 ::= { adslAturPerfDataExtTable 1 } 858 AdslAturPerfDataExtEntry ::= 859 SEQUENCE { 860 adslAturPerfStatSesL Counter32, 861 adslAturPerfStatUasL Counter32, 862 adslAturPerfCurr15MinSesL PerfCurrentCount, 863 adslAturPerfCurr15MinUasL PerfCurrentCount, 864 adslAturPerfCurr1DaySesL AdslPerfCurrDayCount, 865 adslAturPerfCurr1DayUasL AdslPerfCurrDayCount, 866 adslAturPerfPrev1DaySesL AdslPerfPrevDayCount, 867 adslAturPerfPrev1DayUasL AdslPerfPrevDayCount 868 } 870 adslAturPerfStatSesL OBJECT-TYPE 871 SYNTAX Counter32 872 UNITS "seconds" 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "The value of this object reports the count of 877 severely errored second-line since the last agent 878 reset." 879 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 880 ::= { adslAturPerfDataExtEntry 1 } 882 adslAturPerfStatUasL OBJECT-TYPE 883 SYNTAX Counter32 884 UNITS "seconds" 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "The value of this object reports the count of 889 unavailable seconds-line since the last agent 890 reset." 891 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 892 ::= { adslAturPerfDataExtEntry 2 } 894 adslAturPerfCurr15MinSesL OBJECT-TYPE 895 SYNTAX PerfCurrentCount 896 UNITS "seconds" 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "For the current 15-minute interval, 901 adslAturPerfCurr15MinSesL reports the current 902 number of seconds during which there have been 903 severely errored seconds-line." 905 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 906 ::= { adslAturPerfDataExtEntry 3 } 908 adslAturPerfCurr15MinUasL OBJECT-TYPE 909 SYNTAX PerfCurrentCount 910 UNITS "seconds" 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "For the current 15-minute interval, 915 adslAturPerfCurr15MinUasL reports the current 916 number of seconds during which there have been 917 available seconds-line." 918 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 919 ::= { adslAturPerfDataExtEntry 4 } 921 adslAturPerfCurr1DaySesL OBJECT-TYPE 922 SYNTAX AdslPerfCurrDayCount 923 UNITS "seconds" 924 MAX-ACCESS read-only 925 STATUS current 926 DESCRIPTION 927 "For the current day as measured by 928 adslAturPerfCurr1DayTimeElapsed [RFC 2662], 929 adslAturPerfCurr1DaySesL reports the 930 number of seconds during which there have been 931 severely errored seconds-line." 932 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 933 ::= { adslAturPerfDataExtEntry 5 } 935 adslAturPerfCurr1DayUasL OBJECT-TYPE 936 SYNTAX AdslPerfCurrDayCount 937 UNITS "seconds" 938 MAX-ACCESS read-only 939 STATUS current 940 DESCRIPTION 941 "For the current day as measured by 942 adslAturPerfCurr1DayTimeElapsed [RFC 2662], 943 adslAturPerfCurr1DayUasL reports the 944 number of seconds during which there have been 945 unavailable seconds-line." 946 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 947 ::= { adslAturPerfDataExtEntry 6 } 949 adslAturPerfPrev1DaySesL OBJECT-TYPE 950 SYNTAX AdslPerfPrevDayCount 951 UNITS "seconds" 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "For the previous day, adslAturPerfPrev1DaySesL 956 reports the number of seconds during which there 957 were severely errored seconds-line." 958 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 959 ::= { adslAturPerfDataExtEntry 7 } 961 adslAturPerfPrev1DayUasL OBJECT-TYPE 962 SYNTAX AdslPerfPrevDayCount 963 UNITS "seconds" 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "For the previous day, adslAturPerfPrev1DayUasL 968 reports the number of seconds during which there 969 were severely errored seconds-line." 970 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 971 ::= { adslAturPerfDataExtEntry 8 } 973 adslAturIntervalExtTable OBJECT-TYPE 974 SYNTAX SEQUENCE OF AdslAturIntervalExtEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "This table provides one row for each ATU-R 979 performance data collection interval for 980 ADSL physical interfaces whose 981 IfEntries' ifType is equal to adsl(94)." 982 ::= { adslExtMibObjects 21 } 984 adslAturIntervalExtEntry OBJECT-TYPE 985 SYNTAX AdslAturIntervalExtEntry 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION "An entry in the 989 adslAturIntervalExtTable." 990 AUGMENTS { adslAturIntervalEntry } 991 ::= { adslAturIntervalExtTable 1 } 993 AdslAturIntervalExtEntry ::= 994 SEQUENCE { 995 adslAturIntervalSesL PerfIntervalCount, 996 adslAturIntervalUasL PerfIntervalCount 997 } 999 adslAturIntervalSesL OBJECT-TYPE 1000 SYNTAX PerfIntervalCount 1001 UNITS "seconds" 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "For the each interval, adslAturIntervalSesL 1006 reports the number of seconds during which 1007 there have been severely errored seconds-line." 1008 ::= { adslAturIntervalExtEntry 1 } 1010 adslAturIntervalUasL OBJECT-TYPE 1011 SYNTAX PerfIntervalCount 1012 UNITS "seconds" 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "For the each interval, adslAturIntervalUasL 1017 reports the number of seconds during which 1018 there have been unavailable seconds-line." 1019 ::= { adslAturIntervalExtEntry 2 } 1021 adslConfProfileExtTable OBJECT-TYPE 1022 SYNTAX SEQUENCE OF AdslConfProfileExtEntry 1023 MAX-ACCESS not-accessible 1024 STATUS current 1025 DESCRIPTION 1026 "The adslConfProfileExtTable extends the ADSL line 1027 profile configuration information in the 1028 adslLineConfProfileTable from the ADSL-LINE-MIB 1029 [RFC2662] by adding the ability to configure the 1030 ADSL physical line mode." 1031 ::= { adslExtMibObjects 22 } 1033 adslConfProfileExtEntry OBJECT-TYPE 1034 SYNTAX AdslConfProfileExtEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "An entry extends the adslLineConfProfileEntry defined 1039 in [RFC2662]. Each entry corresponds to an ADSL line 1040 profile." 1041 AUGMENTS { adslLineConfProfileEntry } 1042 ::= { adslConfProfileExtTable 1 } 1044 AdslConfProfileExtEntry ::= 1045 SEQUENCE { 1046 adslConfProfileLineType INTEGER 1047 } 1049 adslConfProfileLineType OBJECT-TYPE 1050 SYNTAX INTEGER { 1051 noChannel (1), -- no channels exist 1052 fastOnly (2), -- only fast channel exists 1053 interleavedOnly (3), -- only interleaved channel 1054 -- exist 1055 fastOrInterleaved (4),-- either fast or interleaved 1056 -- channels can exist, but 1057 -- only one at any time 1058 fastAndInterleaved (5)-- both the fast channel and 1059 -- the interleaved channel 1060 -- exist 1061 } 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "This object is used to configure the ADSL physical 1066 line mode. It has following valid values: 1068 noChannel(1), when no channels exist. 1069 fastOnly(2), when only fast channel exists. 1070 interleavedOnly(3), when only interleaved channel 1071 exist. 1072 fastOrInterleaved(4), when either fast or 1073 interleaved channels can exist, but only one 1074 at any time. 1075 fastAndInterleaved(5), when both the fast channel 1076 and the interleaved channel exist. 1078 In the case when no value has been set, the default 1079 Value is noChannel(1). 1080 " 1081 DEFVAL { fastOnly } 1082 ::= { adslConfProfileExtEntry 1 } 1084 adslAlarmConfProfileExtTable OBJECT-TYPE 1085 SYNTAX SEQUENCE OF AdslAlarmConfProfileExtEntry 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "This table extends the adslLineAlarmConfProfileTable 1090 and provides threshold parameters for all the 1091 counters defined in this MIB module." 1092 ::= { adslExtMibObjects 23 } 1094 adslAlarmConfProfileExtEntry OBJECT-TYPE 1095 SYNTAX AdslAlarmConfProfileExtEntry 1096 MAX-ACCESS not-accessible 1097 STATUS current 1098 DESCRIPTION 1099 "An entry extends the adslLineAlarmConfProfileTable 1100 defined in [RFC2662]. Each entry corresponds to 1101 an ADSL alarm profile." 1102 AUGMENTS { adslLineAlarmConfProfileEntry } 1103 ::= { adslAlarmConfProfileExtTable 1 } 1105 AdslAlarmConfProfileExtEntry ::= 1106 SEQUENCE { 1107 adslAtucThreshold15MinFailedFastR Integer32, 1108 adslAtucThreshold15MinSesL Integer32, 1109 adslAtucThreshold15MinUasL Integer32, 1110 adslAturThreshold15MinSesL Integer32, 1111 adslAturThreshold15MinUasL Integer32 1112 } 1114 adslAtucThreshold15MinFailedFastR OBJECT-TYPE 1115 SYNTAX Integer32(0..900) 1116 UNITS "seconds" 1117 MAX-ACCESS read-create 1118 STATUS current 1119 DESCRIPTION 1120 "The first time the value of the corresponding 1121 instance of adslAtucPerfCurr15MinFailedFastR reaches 1122 or exceeds this value within a given 15-minute 1123 performance data collection period, an 1124 adslAtucFailedFastRThreshTrap notification will 1125 be generated. The value '0' will disable the 1126 notification. The default value of this object is 1127 '0'." 1128 DEFVAL { 0 } 1129 ::= { adslAlarmConfProfileExtEntry 1 } 1131 adslAtucThreshold15MinSesL OBJECT-TYPE 1132 SYNTAX Integer32(0..900) 1133 UNITS "seconds" 1134 MAX-ACCESS read-create 1135 STATUS current 1136 DESCRIPTION 1137 "The first time the value of the corresponding instance 1138 of adslAtucPerf15MinSesL reaches or exceeds 1139 this value within a given 15-minute performance data 1140 collection period, an adslAtucSesLThreshTrap 1141 notification will be generated. The value '0' will 1142 disable the notification. The default value of this 1143 object is '0'." 1144 DEFVAL { 0 } 1146 ::= { adslAlarmConfProfileExtEntry 2 } 1148 adslAtucThreshold15MinUasL OBJECT-TYPE 1149 SYNTAX Integer32(0..900) 1150 UNITS "seconds" 1151 MAX-ACCESS read-create 1152 STATUS current 1153 DESCRIPTION 1154 "The first time the value of the corresponding instance 1155 of adslAtucPerf15MinUasL reaches or exceeds 1156 this value within a given 15-minute performance data 1157 collection period, an adslAtucUasLThreshTrap 1158 notification will be generated. The value '0' will 1159 disable the notification. The default value of this 1160 object is '0'." 1161 DEFVAL { 0 } 1162 ::= { adslAlarmConfProfileExtEntry 3 } 1164 adslAturThreshold15MinSesL OBJECT-TYPE 1165 SYNTAX Integer32(0..900) 1166 UNITS "seconds" 1167 MAX-ACCESS read-create 1168 STATUS current 1169 DESCRIPTION 1170 "The first time the value of the corresponding instance 1171 of adslAturPerf15MinSesL reaches or exceeds 1172 this value within a given 15-minute performance data 1173 collection period, an adslAturSesLThreshTrap 1174 notification will be generated. The value '0' will 1175 disable the notification. The default value of this 1176 object is '0'." 1177 DEFVAL { 0 } 1178 ::= { adslAlarmConfProfileExtEntry 4 } 1180 adslAturThreshold15MinUasL OBJECT-TYPE 1181 SYNTAX Integer32(0..900) 1182 UNITS "seconds" 1183 MAX-ACCESS read-create 1184 STATUS current 1185 DESCRIPTION 1186 "The first time the value of the corresponding instance 1187 of adslAturPerf15MinUasL reaches or exceeds 1188 this value within a given 15-minute performance data 1189 collection period, an adslAturUasLThreshTrap 1190 notification will be generated. The value '0' will 1191 disable the notification. The default value of this 1192 object is '0'." 1193 DEFVAL { 0 } 1195 ::= { adslAlarmConfProfileExtEntry 5 } 1197 -- definitions 1199 adslExtTraps OBJECT IDENTIFIER ::= { adslExtMibObjects 24 } 1201 adslExtAtucTraps OBJECT IDENTIFIER ::= { adslExtTraps 1 } 1203 adslExtAtucTrapsPrefix OBJECT IDENTIFIER ::= { adslExtAtucTraps 0 } 1205 adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE 1206 OBJECTS { adslAtucPerfCurr15MinFailedFastR } 1207 STATUS current 1208 DESCRIPTION 1209 "Failed Fast Retrains 15-minute threshold reached." 1210 ::= { adslExtAtucTrapsPrefix 1 } 1212 adslAtucSesLThreshTrap NOTIFICATION-TYPE 1213 OBJECTS { adslAtucPerfCurr15MinSesL } 1214 STATUS current 1215 DESCRIPTION 1216 "Severely errored seconds-line 15-minute threshold 1217 reached." 1218 ::= { adslExtAtucTrapsPrefix 2 } 1220 adslAtucUasLThreshTrap NOTIFICATION-TYPE 1221 OBJECTS { adslAtucPerfCurr15MinUasL } 1222 STATUS current 1223 DESCRIPTION 1224 "Unavailable seconds-line 15-minute threshold reached." 1225 ::= { adslExtAtucTrapsPrefix 3 } 1227 adslExtAturTraps OBJECT IDENTIFIER ::= { adslExtTraps 2 } 1229 adslExtAturTrapsPrefix OBJECT IDENTIFIER ::= { adslExtAturTraps 0 } 1231 adslAturSesLThreshTrap NOTIFICATION-TYPE 1232 OBJECTS { adslAturPerfCurr15MinSesL } 1233 STATUS current 1234 DESCRIPTION 1235 "Severely errored seconds-line 15-minute threshold 1236 reached." 1237 ::= { adslExtAturTrapsPrefix 1 } 1239 adslAturUasLThreshTrap NOTIFICATION-TYPE 1240 OBJECTS { adslAturPerfCurr15MinUasL } 1241 STATUS current 1242 DESCRIPTION 1243 "Unavailable seconds-line 15-minute threshold reached." 1244 ::= { adslExtAturTrapsPrefix 2 } 1246 -- conformance information 1248 adslExtConformance OBJECT IDENTIFIER ::= { adslExtMIB 2 } 1250 adslExtGroups OBJECT IDENTIFIER ::= { adslExtConformance 1 } 1251 adslExtCompliances OBJECT IDENTIFIER ::= { adslExtConformance 2 } 1253 -- ATU-C agent compliance statements 1255 adslExtLineMibAtucCompliance MODULE-COMPLIANCE 1256 STATUS current 1257 DESCRIPTION 1258 "The compliance statement for SNMP entities which 1259 represent ADSL ATU-C interfaces." 1261 MODULE -- this module 1262 MANDATORY-GROUPS 1263 { 1264 adslExtLineGroup, 1265 adslExtLineConfProfileControlGroup, 1266 adslExtLineAlarmConfProfileGroup 1267 } 1269 GROUP adslExtAtucPhysPerfCounterGroup 1270 DESCRIPTION 1271 "This group is optional. Implementations which 1272 require continuous ATU-C physical event counters 1273 should implement this group." 1275 GROUP adslExtAturPhysPerfCounterGroup 1276 DESCRIPTION 1277 "This group is optional. Implementations which 1278 require continuous ATU-R physical event counters 1279 should implement this group." 1281 GROUP adslExtNotificationsGroup 1282 DESCRIPTION 1283 "This group is optional. Implementations which 1284 support TCA (Threshold Crossing Alert) should 1285 implement this group." 1287 OBJECT adslAtucThreshold15MinFailedFastR 1288 MIN-ACCESS read-write 1289 DESCRIPTION 1290 "Read-write access is applicable only when 1291 static profiles as defined in ADSL Line MIB 1292 [RFC2662] are implemented." 1294 OBJECT adslAtucThreshold15MinSesL 1295 MIN-ACCESS read-write 1296 DESCRIPTION 1297 "Read-write access is applicable only when 1298 static profiles as defined in ADSL Line MIB 1299 [RFC2662] are implemented." 1301 OBJECT adslAtucThreshold15MinUasL 1302 MIN-ACCESS read-write 1303 DESCRIPTION 1304 "Read-write access is applicable only when 1305 static profiles as defined in ADSL Line MIB 1306 [RFC2662] are implemented." 1308 OBJECT adslAturThreshold15MinSesL 1309 MIN-ACCESS read-write 1310 DESCRIPTION 1311 "Read-write access is applicable only when 1312 static profiles as defined in ADSL Line MIB 1313 [RFC2662] are implemented." 1315 OBJECT adslAturThreshold15MinUasL 1316 MIN-ACCESS read-write 1317 DESCRIPTION 1318 "Read-write access is applicable only when 1319 static profiles as defined in ADSL Line MIB 1320 [RFC2662] are implemented." 1322 OBJECT adslLineConfProfileDualLite 1323 MIN-ACCESS read-only 1324 DESCRIPTION 1325 "Read-only access is applicable only when 1326 static profiles as defined in ADSL Line MIB 1327 [RFC2662] are implemented." 1329 ::= { adslExtCompliances 1 } 1331 -- units of conformance 1332 adslExtLineGroup OBJECT-GROUP 1333 OBJECTS { 1334 adslLineConfProfileDualLite, 1335 adslLineTransAtucCap, 1336 adslLineTransAtucConfig, 1337 adslLineTransAtucActual, 1338 adslLineGlitePowerState 1339 } 1340 STATUS current 1341 DESCRIPTION 1342 "A collection of objects providing extended 1343 configuration information about an ADSL Line." 1344 ::= { adslExtGroups 1 } 1346 adslExtAtucPhysPerfCounterGroup OBJECT-GROUP 1347 OBJECTS { 1348 adslAtucPerfStatFastR, 1349 adslAtucPerfStatFailedFastR, 1350 adslAtucPerfCurr15MinFastR, 1351 adslAtucPerfCurr15MinFailedFastR, 1352 adslAtucPerfCurr1DayFastR, 1353 adslAtucPerfCurr1DayFailedFastR, 1354 adslAtucPerfPrev1DayFastR, 1355 adslAtucPerfPrev1DayFailedFastR, 1356 adslAtucPerfStatSesL, 1357 adslAtucPerfStatUasL, 1358 adslAtucPerfCurr15MinSesL, 1359 adslAtucPerfCurr15MinUasL, 1360 adslAtucPerfCurr1DaySesL, 1361 adslAtucPerfCurr1DayUasL, 1362 adslAtucPerfPrev1DaySesL, 1363 adslAtucPerfPrev1DayUasL, 1364 adslAtucIntervalFastR, 1365 adslAtucIntervalFailedFastR, 1366 adslAtucIntervalSesL, 1367 adslAtucIntervalUasL 1368 } 1369 STATUS current 1370 DESCRIPTION 1371 "A collection of objects providing raw performance 1372 counts on an ADSL Line (ATU-C end)." 1373 ::= { adslExtGroups 2 } 1375 adslExtAturPhysPerfCounterGroup OBJECT-GROUP 1376 OBJECTS { 1377 adslAturPerfStatSesL, 1378 adslAturPerfStatUasL, 1379 adslAturPerfCurr15MinSesL, 1380 adslAturPerfCurr15MinUasL, 1381 adslAturPerfCurr1DaySesL, 1382 adslAturPerfCurr1DayUasL, 1383 adslAturPerfPrev1DaySesL, 1384 adslAturPerfPrev1DayUasL, 1385 adslAturIntervalSesL, adslAturIntervalUasL 1386 } 1387 STATUS current 1388 DESCRIPTION 1389 "A collection of objects providing raw performance 1390 counts on an ADSL Line (ATU-C end)." 1391 ::= { adslExtGroups 3 } 1393 adslExtLineConfProfileControlGroup OBJECT-GROUP 1394 OBJECTS { 1395 adslConfProfileLineType 1396 } 1397 STATUS current 1398 DESCRIPTION 1399 "A collection of objects providing profile 1400 control for the ADSL system." 1401 ::= { adslExtGroups 4 } 1403 adslExtLineAlarmConfProfileGroup OBJECT-GROUP 1404 OBJECTS { 1405 adslAtucThreshold15MinFailedFastR, 1406 adslAtucThreshold15MinSesL, 1407 adslAtucThreshold15MinUasL, 1408 adslAturThreshold15MinSesL, 1409 adslAturThreshold15MinUasL 1410 } 1411 STATUS current 1412 DESCRIPTION 1413 "A collection of objects providing alarm profile 1414 control for the ADSL system." 1415 ::= { adslExtGroups 5 } 1417 adslExtNotificationsGroup NOTIFICATION-GROUP 1418 NOTIFICATIONS { 1419 adslAtucFailedFastRThreshTrap, 1420 adslAtucSesLThreshTrap, 1421 adslAtucUasLThreshTrap, 1422 adslAturSesLThreshTrap, 1423 adslAturUasLThreshTrap 1424 } 1425 STATUS current 1426 DESCRIPTION 1427 "The collection of ADSL extension notifications." 1428 ::= { adslExtGroups 6 } 1430 END 1432 9. Acknowledgments 1433 This document is a product of the ADSL MIB Working Group. 1435 10. Normative References 1437 [ANSI T1.413] American National Standards Institute, ANSI T1.413, 1438 Issue 2, "Standards Project for Interfaces Relating 1439 to Carrier to Customer Connection of ADSL Equipment", 1440 1998. 1442 [ETSI DTS/TM06006] European Telecommunications Standards Institute 1443 "ADSL European Specific Requirements", November 1444 2000. 1446 [ITU G.992.1] ITU-T Telecommunication Standardization Sector, 1447 "Asymmetric digital subscriber line (ADSL) 1448 transceivers", June 1999. 1450 [ITU G.992.2] ITU-T Telecommunication Standardization Sector, 1451 "Splitterless asymmetric digital subscriber line 1452 (ADSL) transceivers", June 1999. 1454 [ITU G.997.1] ITU-T Telecommunication Standardization Sector, 1455 "Physical Layer Management of Digital Subscriber 1456 Transceivers", June 1999. 1458 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1459 Identification of Management Information for 1460 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 1462 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1463 "Simple Network Management Protocol", STD 15, RFC 1157, 1464 May 1990. 1466 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", 1467 STD 16, RFC 1212, March 1991. 1469 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 1470 the SNMP", RFC 1215, March 1991. 1472 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1473 "Introduction to Community-based SNMPv2", RFC 1901, 1474 January 1996. 1476 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1477 "Protocol Operations for Version 2 of the Simple Network 1478 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1480 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1481 "Transport Mappings for Version 2 of the Simple Network 1482 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1484 [RFC2026] Bradner S., "The Internet Standards Process - 1485 Revision 3", October 1996. 1487 [RFC2028] Hovey R., S. Bradner, "The Organizations Involved in 1488 the IETF Standards Process", October 1996. 1490 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1491 "Introduction to Version 3 of the Internet-standard 1492 Network Management Framework", RFC 2570, April 1999. 1494 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1495 Architecture for Describing SNMP Management Frameworks", 1496 RFC 2571, April 1999. 1498 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1499 "Message Processing and Dispatching for the Simple 1500 Network Management Protocol (SNMP)", RFC 2572, April 1999. 1502 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1503 Applications", RFC 2573, April 1999. 1505 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1506 (USM) for version 3 of the Simple Network Management 1507 Protocol (SNMPv3)", RFC 2574, April 1999. 1509 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1510 Access Control Model (VACM) for the Simple Network 1511 Management Protocol (SNMP)", RFC 2575, April 1999. 1513 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1514 Rose, M., and S. Waldbusser, "Structure of Management 1515 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1516 1999. 1518 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1519 Rose, M., and S. Waldbusser, "Textual Conventions for 1520 SMIv2", STD 58, RFC 2579, April 1999. 1522 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1523 Rose, M., and S. Waldbusser, "Conformance Statements for 1524 SMIv2", STD 58, RFC 2580, April 1999. 1526 [RFC2662] Bathrick, G. and F. Ly "Definitions of Managed Objects for 1527 the ADSL Lines", May 1999. 1529 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1530 MIB", RFC 2863, June 2000. 1532 11. Security Considerations 1534 The following security matters should be considered when implementing 1535 this MIB. 1537 1) Blocking unauthorized access to the ADSL MIB via the element 1538 management system is outside the scope of this document. It should be 1539 noted that access to the MIB permits the unauthorized entity to 1540 modify the profiles (section 6.4) such that both subscriber service 1541 and network operations can be interfered with. Subscriber service can 1542 be altered by modifying any of a number of service characteristics 1543 such as rate partitioning and maximum transmission rates. Network 1544 operations can be impacted by modification of notification thresholds 1545 such as Signal-to-Noise Ratio (SNR) margins. 1547 2) There are a number of managed objects in this MIB that may be 1548 considered to contain sensitive information. In particular, the 1549 certain objects may be considered sensitive in many environments, 1550 since it would allow an intruder to obtain information about which 1551 vendor's equipment is in use on the network. Therefore, it may be 1552 important in some environments to control read access to these 1553 objects and possibly to even encrypt the values of these object when 1554 sending them over the network via SNMP. Not all versions of SNMP 1555 provide features for such a secure environment. 1557 SNMPv1 by itself is such an insecure environment. Even if the 1558 network itself is secure (for example by using IPSec), even then, 1559 there is no control as to who on the secure network is allowed to 1560 access and GET (read) the objects in this MIB. It is recommended 1561 that the implementors consider the security features as provided by 1562 the SNMPv3 framework. Specifically, the use of the User-based 1563 Security Model RFC 2574 [21] and the View-based Access Control Model 1564 RFC 2575 [23] is recommended. 1566 It is then a customer/user responsibility to ensure that the SNMP 1567 entity giving access to an instance of this MIB, is properly 1568 configured to give access to those objects only to those principals 1569 (users) that have legitimate rights to access them. 1571 3) The profile mechanism presented in this document requires specific 1572 attention. The implementor of this MIB has a choice of implementing 1573 either 'static' or 'dynamic' profiles. This decision must be 1574 consistent with the implementation of RFC2662. 1576 In the case of 'static' profiles, the elements of the profile are 1577 read-write as opposed to read-create when 'dynamic' profiles are 1578 implemented: 1580 - adslConfProfileLineType, 1581 - adslAtucThreshold15MinFailedFastR, 1582 - adslAtucThreshold15MinSesL, 1583 - adslAtucThreshold15MinUasL, 1584 - adslAturThreshold15MinSesL, and 1585 - adslAturThreshold15MinUasL. 1587 This decision also impacts the mechanics of the index, 1588 adslLineConfProfileDualLite. When 'static' profiles are implemented, 1589 its value is algorithmically set by the system and its value is 1590 based on the ifIndex, hence not guaranteed across system reboots. 1591 Similar to the handling of adslLineConfProfile [RFC2662], the 1592 implementor of this MIB must ensure that the profile object values 1593 associated with these indices are maintained across system reboots. 1595 In the case of dynamic profiles, this object is set by the SNMP 1596 manager. The implementor of this MIB may want to provide view of the 1597 profile on a customer-by-customer standpoint, but should be cautious 1598 of the dynamic nature of these objects. 1600 4) ADSL layer connectivity from the ATU-R will permit the subscriber 1601 to manipulate both the ADSL link directly and the ADSL overhead 1602 control channel(AOC)/embedded operations channel (EOC) 1603 for their own loop. For example, unchecked or unfiltered 1604 fluctuations initiated by the subscriber could generate sufficient 1605 notifications to potentially overwhelm either the management 1606 interface to the network or the element manager. Other attacks 1607 affecting the ATU-R portions of the MIB may also be possible. 1609 12. Intellectual Property Notice 1611 The IETF takes no position regarding the validity or scope of any 1612 intellectual property or other rights that might be claimed to 1613 pertain to the implementation or use of the technology described in 1614 this document or the extent to which any license under such rights 1615 might or might not be available; neither does it represent that it 1616 has made any effort to identify any such rights. Information on the 1617 IETF's procedures with respect to rights in standards-track and 1618 standards-related documentation can be found in BCP-11 [RFC2028]. 1619 Copies of claims of rights made available for publication and any 1620 assurances of licenses to be made available, or the result of an 1621 attempt made to obtain a general license or permission for the use 1622 of such proprietary rights by implementors or users of this 1623 specification can be obtained from the IETF Secretariat. 1625 The IETF invites any interested party to bring to its attention any 1626 copyrights, patents or patent applications, or other proprietary 1627 rights that may cover technology that may be required to practice 1628 this standard. Please address the information to the IETF Executive 1629 Director. 1631 13. Authors' Addresses 1633 Faye Ly 1634 Pedestal Networks 1635 3045 Park Boulevard 1636 Palo Alto, CA 94306, USA 1638 Phone: +1 650-475-1274 1639 Fax: +1 650-688-3119 1640 EMail: faye@pedestalnetworks.com 1642 Gregory Bathrick 1643 NOKIA High Speed Access Nodes 1644 1310 Redwood Way, 1645 Petaluma, CA 94954, USA 1647 Phone: +1 707-793-7030 1648 Fax: +1 707-792-0850 1649 EMail: greg.bathrick@nokia.com 1651 14. Full Copyright Statement 1653 Copyright (C) The Internet Society (2002). All Rights Reserved. 1655 This document and translations of it may be copied and furnished to 1656 others, and derivative works that comment on or otherwise explain it 1657 or assist in its implementation may be prepared, copied, published 1658 and distributed, in whole or in part, without restriction of any 1659 kind, provided that the above copyright notice and this paragraph are 1660 included on all such copies and derivative works. However, this 1661 document itself may not be modified in any way, such as by removing 1662 the copyright notice or references to the Internet Society or other 1663 Internet organizations, except as needed for the purpose of 1664 developing Internet standards in which case the procedures for 1665 copyrights defined in the Internet Standards process must be 1666 followed, or as required to translate it into languages other than 1667 English. 1669 The limited permissions granted above are perpetual and will not be 1670 revoked by the Internet Society or its successors or assigns. 1672 This document and the information contained herein is provided on an 1673 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1674 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1675 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1676 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1677 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1679 Acknowledgement 1681 Funding for the RFC Editor function is currently provided by the 1682 Internet Society. 1684 Table of Contents 1686 1. Status of this Memo ..................................... 1 1687 2. Abstract ............................................... 1 1688 3. The SNMP Network Management Framework ................... 1 1689 4. Introduction ............................................ 2 1690 5. Relationship of ADSL LINE EXTENSION MIB with standard MIBs. 3 1691 6. Conventions used in the MIB ............................. 3 1692 7. Conformance and Compliance .............................. 5 1693 8. Definitions ............................................. 5 1694 9. Acknowledgments ......................................... 25 1695 10. References .............................................. 26 1696 11. Security Considerations ................................. 27 1697 12. Intellectual Property Notice .............................. 27 1698 13. Authors' Addresses ...................................... 28 1699 14. Full Copyright Statement ............................... 29