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