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