idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-mcm-01.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 document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 6 instances of lines with control characters in the document. ** The abstract seems to contain references ([RFCXXXX]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Unrecognized Status in 'Category: Internet Draft', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 (February 2004) is 7377 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: 'DSLFXXXXXX' is mentioned on line 89, but not defined == Unused Reference: 'DSLFTR057' is defined on line 894, but no explicit reference was found in the text == Unused Reference: 'ETSI2701' is defined on line 897, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 902, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 907, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 910, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 913, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 932, but no explicit reference was found in the text == Unused Reference: 'RFC3593' is defined on line 936, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 948, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 953, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 957, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFTR057' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2701' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2702' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9931' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9971' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCXXXX' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) Summary: 5 errors (**), 0 flaws (~~), 15 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group M. Dodge 2 Category: Internet Draft Infineon Technologies 3 Document: draft-ietf-adslmib-vdsl-ext-mcm-01.txt B. Ray 4 PESA Switching Systems 5 February 2004 7 Definitions of Managed Object Extensions 8 for Very High Speed Digital Subscriber Lines (VDSL) Using 9 Multiple Carrier Modulation (MCM) Line Coding. 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at: 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at: 30 http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The Internet Society (2004). All Rights Reserved. 36 Abstract 38 This document defines a portion of the Management Information Base 39 (MIB) module for use with network management protocols in the 40 Internet community. In particular, it describes objects used for 41 managing the Line Code Specific parameters of Very High Speed 42 Digital Subscriber Line (VDSL) interfaces using Multiple Carrier 43 Modulation (MCM) Line Coding. It is an optional extension to the 44 VDSL-LINE CORE MIB RFC XXXX [RFCXXXX] which handles the line code 45 independent objects. 47 Table of Contents 49 1. The Internet-Standard Management Framework .................... 2 50 2. Overview ...................................................... 2 51 2.1 Relationship of this MIB Module to other MIB Modules . 2 52 2.2 Conventions used in the MIB Module ............................ 3 53 2.3 Structure ..................................................... 3 54 2.4 Persistence ................................................... 4 55 3. Conformance and Compliance .................................... 5 56 4. Definitions ................................................... 5 57 5. Intellectual Property ......................................... 19 58 6. Normative References .......................................... 19 59 7. Informative References ........................................ 20 60 8. Security Considerations ....................................... 21 61 9. Acknowledgements .............................................. 21 62 10. Authors' Addresses ............................................ 22 63 11. Full Copyright Statement ...................................... 22 65 1. The Internet-Standard Management Framework 67 For a detailed overview of the documents that describe the current 68 Internet-Standard Management Framework, please refer to section 7 of 69 RFC 3410 [RFC3410]. 71 Managed objects are accessed via a virtual information store, termed 72 the Management Information Base or MIB. MIB objects are generally 73 accessed through the Simple Network Management Protocol (SNMP). 74 Objects in the MIB are defined using the mechanisms defined in the 75 Structure of Management Information (SMI). This memo specifies a 76 MIB module that is compliant to the SMIv2, which is described in STD 77 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 78 2580 [RFC2580]. 80 2. Overview 82 This document describes an SNMP MIB module for managing the line 83 code dependent (Physical Medium Dependent) Layer of MCM VDSL Lines. 84 These definitions are based upon the specifications for VDSL as 85 defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, 86 T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the 87 protocol-dependent (and line-code dependent) management framework 88 for VDSL lines specified by DSLF has been taken into consideration 89 [DSLFXXXXXX]. 91 The MIB module is located in the MIB tree under MIB 2 transmission, 92 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section 93 of this document. 95 2.1 Relationship of this MIB Module to other MIB Modules 97 The relationship of the VDSL Line MIB to other MIBS and in particular 98 to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in 99 the VDSL-LINE CORE MIB RFC XXXX [RFCXXXX]. This section outlines the 100 relationship of this VDSL Line Extension MIB to the VDSL-LINE CORE 101 MIB RFC XXXX [RFCXXXX]. 103 2.2 Conventions used in the MIB Module 105 2.2.1 Naming Conventions 107 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 108 B. Vtur -- (VTUR) transceiver at Remote end of line 109 C. Vtu -- One of either Vtuc or Vtur 110 D. Curr -- Current 111 E. Prev -- Previous 112 F. Atn -- Attenuation 113 G. ES -- Errored Second 114 H. SES -- Severely Errored Second 115 I. UAS -- Unavailable Second 116 J. LCS -- Line Code Specific 117 K. Lof -- Loss of Frame 118 L. Lol -- Loss of Link 119 M. Los -- Loss of Signal 120 N. Lpr -- Loss of Power 121 O. xxxs -- Sum of Seconds in which xxx has occurs (e.g., xxx=Lof, 122 Los, Lpr, Lol) 123 P. Max -- Maximum 124 Q. Mgn -- Margin 125 R. Min -- Minimum 126 S. Psd -- Power Spectral Density 127 T. Snr -- Signal to Noise Ratio 128 U. Tx -- Transmit 129 V. Blks -- Blocks 131 2.3 Structure 133 The MCM VDSL Line Extension MIB contains the following MIB group: 135 o vdslMCMGroup : 137 This group supports MIB objects for defining configuration profiles 138 and for montioring individual bands of Multiple Carrier Modulation 139 (MCM) VDSL modems. It contains the following tables: 141 - vdslLineMCMConfProfileTable 142 - vdslLineMCMConfProfileTxBandTable 143 - vdslLineMCMConfProfileRxBandTable 144 - vdslLineMCMConfProfileTxPSDTable 145 - vdslLineMCMConfProfileMaxTxPSDTable 146 - vdslLineMCMConfProfileMaxRxPSDTable 148 Either none, some or all of the objects in this group MAY be 149 implemented for MCM VDSL lines. 151 Figure 1, below, displays the relationship of the tables in the 152 vdslMCMGroup to the vdslGroup and to the ifEntry: 154 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 156 vdslLineTableEntry (vdslLineCoding=MCM) 158 vdslLineConfProfileEntry(vdslLineConfProfileName) 159 ----> vdslLineMCMConfProfileTable 1:(0..1) 160 ----> vdslLineMCMConfProfileTxBandTable 1:(0..1) 161 ----> vdslLineMCMConfProfileRxBandTable 1:(0..1) 162 ----> vdslLineMCMConfProfileTxPSDTable 1:(0..1) 163 ----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..1) 164 ----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..1) 166 Figure 1: Table Relationships 168 When the vdslLineCoding is set to MCM, the vdslLineConfProfileName 169 which is the index of the vdslLineConfProfileEntry is also used as 170 the index to the vdslLineMCMConfProfileTxBandTable of the 171 vdslMCMGroup. The existence of an entry in any of the tables of 172 the vdslMCMGroup is optional. Either none, some or all of the 173 vdslMCMGroup tables MAY be implemented for a particular VDSL line 174 entity using MCM line coding. 176 2.4 Persistence 178 All read-write and read-create objects defined in this MIB module 179 SHOULD be stored persistently. Following is an exhaustive list of 180 these persistent objects: 182 vdslMCMConfProfileTxWindowLength 183 vdslMCMConfProfileRowStatus 184 vdslMCMConfProfileTxBandNumber 185 vdslMCMConfProfileTxBandStart 186 vdslMCMConfProfileTxBandStop 187 vdslMCMConfProfileTxBandRowStatus 188 vdslMCMConfProfileRxBandStart 189 vdslMCMConfProfileRxBandStop 190 vdslMCMConfProfileRxBandRowStatus 191 vdslMCMConfProfileTxPSDTone 192 vdslMCMConfProfileTxPSDPSD 193 vdslMCMConfProfileTxPSDRowStatus 194 vdslMCMConfProfileMaxTxPSDTone 195 vdslMCMConfProfileMaxTxPSDPSD 196 vdslMCMConfProfileMaxTxPSDRowStatus 197 vdslMCMConfProfileMaxRxPSDTone 198 vdslMCMConfProfileMaxRxPSDPSD 199 vdslMCMConfProfileMaxRxPSDRowStatus 201 It SHOULD also be noted that interface indices in this MIB are 202 maintained persistently. VACM data relating to these SHOULD be 203 stored persistently as well [RFC2575]. 205 3. Conformance and Compliance 207 For MCM VDSL lines, the following group is optional: 209 - vdslMCMGroup 210 4. Definitions 212 VDSL-LINE-EXT-MCM MIB DEFINITIONS ::= BEGIN 214 IMPORTS 216 MODULE-IDENTITY, 217 OBJECT-TYPE, 218 Counter64, 219 Gauge32, 220 Integer32, 221 Unsigned32, 222 NOTIFICATION-TYPE, 223 transmission FROM SNMPv2-SMI 224 TEXTUAL-CONVENTION, 225 RowStatus, 226 TruthValue FROM SNMPv2-TC 227 HCPerfValidIntervals, 228 HCPerfInvalidIntervals, 229 HCPerfTimeElapsed, 230 HCPerfIntervalThreshold, 231 HCPerfCurrentCount, 232 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 233 MODULE-COMPLIANCE, 234 OBJECT-GROUP, 235 NOTIFICATION-GROUP FROM SNMPv2-CONF 236 ifIndex FROM IF-MIB 237 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 238 vdslLineConfProfileName FROM VDSL-LINE-MIB; 240 vdslExtMCMMIB MODULE-IDENTITY 241 LAST-UPDATED "200402120000Z" -- February 12, 2004 242 ORGANIZATION "ADSLMIB Working Group" 243 CONTACT-INFO "WG-email: adslmib@ietf.org 244 Info: https://www1.ietf.org/mailman/listinfo/adslmib 246 Chair: Mike Sneed 247 Sand Channel Systems 248 Postal: P.O. Box 37324 249 Raleigh NC 27627-732 250 Email: sneedmike@hotmail.com 251 Phone: +1 206 600 7022 252 co-editor: Menachem Dodge 253 Infineon Technologies Savan Ltd. 254 6 Hagavish St. 255 Postal: Poleg Industrial Area, 256 Netanya 42504, 257 Israel. 258 Email: menachem.dodge@infineon.com 259 Phone: +972 9 892 4116 261 Co-editor: Bob Ray 262 PESA Switching Systems, Inc. 263 Postal: 330-A Wynn Drive 264 Huntsville, AL 35805 265 USA 266 Email: rray@pesa.com 267 Phone: +1 256 726 9200 ext. 142 268 " 269 DESCRIPTION 270 "The VDSL Line core MIB found in RFC XXXX defines objects for 271 the management of a pair of VDSL transceivers at each end of 272 the VDSL line. The core MIB configures and monitors the line 273 code independent parameters (TC layer) of the VDSL line. 274 This MIB module is an optional extension of the core MIB and 275 defines objects for configuration and monitoring of the line 276 code specific (LCS) elements (PMD layer) for VDSL lines using 277 MCM coding. The objects in this extension MIB MUST NOT be used 278 for VDSL lines using SCM line coding. 280 Naming Conventions: 281 Vtuc -- (VTUC) transceiver at near (Central) end of line 282 Vtur -- (VTUR) transceiver at Remote end of line 283 Vtu -- One of either Vtuc or Vtur 284 Curr -- Current 285 Prev -- Previous 286 Atn -- Attenuation 287 ES -- Errored Second. 288 SES -- Severely Errored Second 289 UAS -- Unavailable Second 290 LCS -- Line Code Specific 291 Lof -- Loss of Frame 292 Lol -- Loss of Link 293 Los -- Loss of Signal 294 Lpr -- Loss of Power 295 xxxs -- Interval of Seconds in which xxx occurs 296 (e.g., xxx=Lof, Los, Lpr) 297 Max -- Maximum 298 Mgn -- Margin 299 Min -- Minimum 300 Psd -- Power Spectral Density 301 Snr -- Signal to Noise Ratio 302 Tx -- Transmit 303 Blks -- Blocks 305 Copyright (C) The Internet Society (2004). This version 306 of this MIB module is part of RFC XXXX: see the RFC 307 itself for full legal notices." 308 -- RFC Ed.: replace XXXX with assigned number & remove this note 309 REVISION "200402120000Z" -- February 12, 2004 310 DESCRIPTION "Initial version, published as RFC XXXX." 311 -- RFC Ed.: replace XXXX with assigned number & remove this note 312 ::= { vdslMIB XX } -- To be assigned by IANA 313 -- RFC Ed.: we suggest to put it under { vdslMIB 3 } because 314 -- vdslMIB 1 is the VDSL core MIB, vdslMIB 2 is the SCM 315 -- extension MIB, while vdslMIB 3 is the MCM extension MIB. 317 vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 } 318 vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1} 320 -- 321 -- Multiple carrier modulation (MCM) configuration profile tables 322 -- 324 vdslLineMCMConfProfileTable OBJECT-TYPE 325 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "This table contains additional information on 330 multiple carrier VDSL lines. One entry in this table 331 reflects a profile defined by a manager which can be used 332 to configure the VDSL line. 334 The entries in this table MUST NOT be used for single 335 carrier (SCM) VDSL lines." 336 ::= { vdslLineExtMCMMibObjects 1 } 338 vdslLineMCMConfProfileEntry OBJECT-TYPE 339 SYNTAX VdslLineMCMConfProfileEntry 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "Each entry consists of a list of parameters that 344 represents the configuration of a multiple carrier 345 modulation VDSL modem. 347 A default profile with an index of 'DEFVAL', will always 348 exist and its parameters will be set to vendor specific 349 values, unless otherwise specified in this document." 350 INDEX { vdslLineConfProfileName } 351 ::= { vdslLineMCMConfProfileTable 1 } 353 VdslLineMCMConfProfileEntry ::= 354 SEQUENCE 355 { 356 vdslLineMCMConfProfileTxWindowLength Unsigned32, 357 vdslLineMCMConfProfileRowStatus RowStatus 358 } 360 vdslLineMCMConfProfileTxWindowLength OBJECT-TYPE 361 SYNTAX Unsigned32 (1..255) 362 UNITS "samples" 363 MAX-ACCESS read-create 364 STATUS current 365 DESCRIPTION 366 "Specifies the length of the transmit window, counted 367 in samples at the sampling rate corresponding to the 368 negotiated value of N." 369 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 370 ::= { vdslLineMCMConfProfileEntry 1 } 372 vdslLineMCMConfProfileRowStatus OBJECT-TYPE 373 SYNTAX RowStatus 374 MAX-ACCESS read-create 375 STATUS current 376 DESCRIPTION 377 "This object is used to create a new row or modify or 378 delete an existing row in this table. 380 A profile activated by setting this object to `active'. 381 When `active' is set, the system will validate the profile. 383 Before a profile can be deleted or taken out of 384 service, (by setting this object to `destroy' or 385 `outOfService') it must be first unreferenced 386 from all associated lines." 387 ::= { vdslLineMCMConfProfileEntry 2 } 389 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 390 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 391 MAX-ACCESS not-accessible 392 STATUS current 393 DESCRIPTION 394 "This table contains transmit band descriptor configuration 395 information for a VDSL line. Each entry in this table 396 reflects the configuration for one of possibly many bands 397 with a multiple carrier modulation (MCM) VDSL line. 398 These entries are defined by a manager and can be used to 399 configure the VDSL line. 401 The entries in this table MUST NOT be used for single 402 carrier (SCM) VDSL lines." 403 ::= { vdslLineExtMCMMibObjects 2 } 405 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 406 SYNTAX VdslLineMCMConfProfileTxBandEntry 407 MAX-ACCESS not-accessible 408 STATUS current 409 DESCRIPTION 410 "Each entry consists of a transmit band descriptor, which 411 is defined by a start and a stop tone index. 412 A default profile with an index of 'DEFVAL', will 413 always exist and its parameters will be set to vendor 414 specific values, unless otherwise specified in this 415 document." 416 INDEX { vdslLineConfProfileName, 417 vdslLineMCMConfProfileTxBandNumber } 418 ::= { vdslLineMCMConfProfileTxBandTable 1 } 420 VdslLineMCMConfProfileTxBandEntry ::= 421 SEQUENCE 422 { 423 vdslLineMCMConfProfileTxBandNumber Unsigned32, 424 vdslLineMCMConfProfileTxBandStart Unsigned32, 425 vdslLineMCMConfProfileTxBandStop Unsigned32, 426 vdslLineMCMConfProfileTxBandRowStatus RowStatus 427 } 429 vdslLineMCMConfProfileTxBandNumber OBJECT-TYPE 430 SYNTAX Unsigned32 431 MAX-ACCESS not-accessible 432 STATUS current 433 DESCRIPTION 434 "The index for this band descriptor entry." 435 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 437 vdslLineMCMConfProfileTxBandStart OBJECT-TYPE 438 SYNTAX Unsigned32 439 MAX-ACCESS read-create 440 STATUS current 441 DESCRIPTION 442 "Start tone index for this band." 443 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 444 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 446 vdslLineMCMConfProfileTxBandStop OBJECT-TYPE 447 SYNTAX Unsigned32 448 MAX-ACCESS read-create 449 STATUS current 450 DESCRIPTION 451 "Stop tone index for this band." 452 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 453 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 455 vdslLineMCMConfProfileTxBandRowStatus OBJECT-TYPE 456 SYNTAX RowStatus 457 MAX-ACCESS read-create 458 STATUS current 459 DESCRIPTION 460 "This object is used to create a new row or modify or 461 delete an existing row in this table. 462 A profile activated by setting this object to `active'. 463 When `active' is set, the system will validate the profile. 465 Before a profile can be deleted or taken out of 466 service, (by setting this object to `destroy' or 467 `outOfService') it must be first unreferenced 468 from all associated lines." 469 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 471 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 472 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 473 MAX-ACCESS not-accessible 474 STATUS current 475 DESCRIPTION 476 "This table contains receive band descriptor configuration 477 information for a VDSL line. Each entry in this table 478 reflects the configuration for one of possibly many bands 479 with a multiple carrier modulation (MCM) VDSL line. 480 These entries are defined by a manager and can be used to 481 configure the VDSL line. 483 The entries in this table MUST NOT be used for single 484 carrier (SCM) VDSL lines." 485 ::= { vdslLineExtMCMMibObjects 3 } 487 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 488 SYNTAX VdslLineMCMConfProfileRxBandEntry 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "Each entry consists of a transmit band descriptor, which 493 is defined by a start and a stop tone index. 495 A default profile with an index of 'DEFVAL', will 496 always exist and its parameters will be set to vendor 497 specific values, unless otherwise specified in this 498 document." 499 INDEX { vdslLineConfProfileName, 500 vdslLineMCMConfProfileRxBandNumber } 501 ::= { vdslLineMCMConfProfileRxBandTable 1 } 503 VdslLineMCMConfProfileRxBandEntry ::= 504 SEQUENCE 505 { 506 vdslLineMCMConfProfileRxBandNumber Unsigned32, 507 vdslLineMCMConfProfileRxBandStart Unsigned32, 508 vdslLineMCMConfProfileRxBandStop Unsigned32, 509 vdslLineMCMConfProfileRxBandRowStatus RowStatus 510 } 512 vdslLineMCMConfProfileRxBandNumber OBJECT-TYPE 513 SYNTAX Unsigned32 514 MAX-ACCESS not-accessible 515 STATUS current 516 DESCRIPTION 517 "The index for this band descriptor entry." 518 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 520 vdslLineMCMConfProfileRxBandStart OBJECT-TYPE 521 SYNTAX Unsigned32 522 MAX-ACCESS read-create 523 STATUS current 524 DESCRIPTION 525 "Start tone index for this band." 526 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 527 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 529 vdslLineMCMConfProfileRxBandStop OBJECT-TYPE 530 SYNTAX Unsigned32 531 MAX-ACCESS read-create 532 STATUS current 533 DESCRIPTION 534 "Stop tone index for this band." 535 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 536 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 538 vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE 539 SYNTAX RowStatus 540 MAX-ACCESS read-create 541 STATUS current 542 DESCRIPTION 543 "This object is used to create a new row or modify or 544 delete an existing row in this table. 546 A profile activated by setting this object to `active'. 547 When `active' is set, the system will validate the profile. 549 Before a profile can be deleted or taken out of 550 service, (by setting this object to `destroy' or 551 `outOfService') it must be first unreferenced 552 from all associated lines." 553 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 555 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "This table contains transmit PSD mask descriptor 561 configuration information for a VDSL line. Each entry in 562 this table reflects the configuration for one tone within 563 a multiple carrier modulation (MCM) VDSL line. These 564 entries are defined by a manager and can be used to 565 configure the VDSL line. 567 The entries in this table MUST NOT be used for single 568 carrier (SCM) VDSL lines." 569 ::= { vdslLineExtMCMMibObjects 4 } 571 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 572 SYNTAX VdslLineMCMConfProfileTxPSDEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "Each entry consists of a transmit PSD mask descriptor, 577 which defines the power spectral density (PSD) for a tone. 579 A default profile with an index of 'DEFVAL', will 580 always exist and its parameters will be set to vendor 581 specific values, unless otherwise specified in this 582 document." 583 INDEX { vdslLineConfProfileName, 584 vdslLineMCMConfProfileTxPSDNumber } 585 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 587 VdslLineMCMConfProfileTxPSDEntry ::= 588 SEQUENCE 589 { 590 vdslLineMCMConfProfileTxPSDNumber Unsigned32, 591 vdslLineMCMConfProfileTxPSDTone Unsigned32, 592 vdslLineMCMConfProfileTxPSDPSD Unsigned32, 593 vdslLineMCMConfProfileTxPSDRowStatus RowStatus 594 } 596 vdslLineMCMConfProfileTxPSDNumber OBJECT-TYPE 597 SYNTAX Unsigned32 598 MAX-ACCESS not-accessible 599 STATUS current 600 DESCRIPTION 601 "The index for this mask descriptor entry." 602 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 604 vdslLineMCMConfProfileTxPSDTone OBJECT-TYPE 605 SYNTAX Unsigned32 606 MAX-ACCESS read-create 607 STATUS current 608 DESCRIPTION 609 "The tone index for which the PSD is being specified." 610 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 611 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 613 vdslLineMCMConfProfileTxPSDPSD OBJECT-TYPE 614 SYNTAX Unsigned32 615 UNITS "0.5dBm" 616 MAX-ACCESS read-create 617 STATUS current 618 DESCRIPTION 619 "Power Spectral Density level in steps of 0.5dB with 620 an offset of -140dbm/Hz." 621 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 622 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 624 vdslLineMCMConfProfileTxPSDRowStatus OBJECT-TYPE 625 SYNTAX RowStatus 626 MAX-ACCESS read-create 627 STATUS current 628 DESCRIPTION 629 "This object is used to create a new row or modify or 630 delete an existing row in this table. 632 A profile activated by setting this object to `active'. 633 When `active' is set, the system will validate the profile. 635 Before a profile can be deleted or taken out of 636 service, (by setting this object to `destroy' or 637 `outOfService') it must be first unreferenced 638 from all associated lines." 639 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 641 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 642 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 643 MAX-ACCESS not-accessible 644 STATUS current 645 DESCRIPTION 646 "This table contains transmit maximum PSD mask descriptor 647 configuration information for a VDSL line. Each entry in 648 this table reflects the configuration for one tone within 649 a multiple carrier modulation (MCM) VDSL modem. These 650 entries are defined by a manager and can be used to 651 configure the VDSL line. 653 The entries in this table MUST NOT be used for single 654 carrier (SCM) VDSL lines." 655 ::= { vdslLineExtMCMMibObjects 5 } 657 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 658 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "Each entry consists of a transmit PSD mask descriptor, 663 which defines the maximum power spectral density (PSD) 664 for a tone. 666 A default profile with an index of 'DEFVAL', will 667 always exist and its parameters will be set to vendor 668 specific values, unless otherwise specified in this 669 document." 670 INDEX { vdslLineConfProfileName, 671 vdslLineMCMConfProfileMaxTxPSDNumber } 672 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 674 VdslLineMCMConfProfileMaxTxPSDEntry ::= 675 SEQUENCE 676 { 677 vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32, 678 vdslLineMCMConfProfileMaxTxPSDTone Unsigned32, 679 vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32, 680 vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus 681 } 683 vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 684 SYNTAX Unsigned32 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "The index for this band descriptor entry." 689 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 691 vdslLineMCMConfProfileMaxTxPSDTone OBJECT-TYPE 692 SYNTAX Unsigned32 693 MAX-ACCESS read-create 694 STATUS current 695 DESCRIPTION 696 "The tone index for which the PSD is being specified." 697 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 698 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 700 vdslLineMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 701 SYNTAX Unsigned32 702 UNITS "0.5dBm" 703 MAX-ACCESS read-create 704 STATUS current 705 DESCRIPTION 706 "Power Spectral Density level in steps of 0.5dB with 707 an offset of -140dbm/Hz." 708 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 709 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 711 vdslLineMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 712 SYNTAX RowStatus 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "This object is used to create a new row or modify or 717 delete an existing row in this table. 719 A profile activated by setting this object to `active'. 720 When `active' is set, the system will validate the profile. 722 Before a profile can be deleted or taken out of 723 service, (by setting this object to `destroy' or 724 `outOfService') it must be first unreferenced 725 from all associated lines." 726 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 728 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 729 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 730 MAX-ACCESS not-accessible 731 STATUS current 732 DESCRIPTION 733 "This table contains maximum receive PSD mask descriptor 734 configuration information for a VDSL line. Each entry in 735 this table reflects the configuration for one tone within 736 a multiple carrier modulation (MCM) VDSL modem. These 737 entries are defined by a manager and can be used to 738 configure the VDSL line. 740 The entries in this table MUST NOT be used for single 741 carrier (SCM) VDSL lines." 742 ::= { vdslLineExtMCMMibObjects 6 } 744 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 745 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "Each entry consists of a transmit PSD mask descriptor, 750 which defines the power spectral density (PSD) for a 751 tone. 753 A default profile with an index of 'DEFVAL', will 754 always exist and its parameters will be set to vendor 755 specific values, unless otherwise specified in this 756 document." 757 INDEX { vdslLineConfProfileName, 758 vdslLineMCMConfProfileMaxRxPSDNumber } 759 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 761 VdslLineMCMConfProfileMaxRxPSDEntry ::= 762 SEQUENCE 763 { 764 vdslLineMCMConfProfileMaxRxPSDNumber Unsigned32, 765 vdslLineMCMConfProfileMaxRxPSDTone Unsigned32, 766 vdslLineMCMConfProfileMaxRxPSDPSD Unsigned32, 767 vdslLineMCMConfProfileMaxRxPSDRowStatus RowStatus 768 } 770 vdslLineMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 771 SYNTAX Unsigned32 772 MAX-ACCESS not-accessible 773 STATUS current 774 DESCRIPTION 775 "The index for this band descriptor entry." 776 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 778 vdslLineMCMConfProfileMaxRxPSDTone OBJECT-TYPE 779 SYNTAX Unsigned32 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "The tone index for which the PSD is being specified." 784 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 785 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 787 vdslLineMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 788 SYNTAX Unsigned32 789 UNITS "0.5dBm" 790 MAX-ACCESS read-create 791 STATUS current 792 DESCRIPTION 793 "Power Spectral Density level in steps of 0.5dB with 794 an offset of -140dbm/Hz." 795 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 796 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 798 vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 799 SYNTAX RowStatus 800 MAX-ACCESS read-create 801 STATUS current 802 DESCRIPTION 803 "This object is used to create a new row or modify or 804 delete an existing row in this table. 806 A profile activated by setting this object to `active'. 807 When `active' is set, the system will validate the profile. 809 Before a profile can be deleted or taken out of 810 service, (by setting this object to `destroy' or 811 `outOfService') it must be first unreferenced 812 from all associated lines." 813 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 815 -- conformance information 817 vdslLineExtMCMConformance OBJECT IDENTIFIER ::= 818 {vdslLineExtMCMMib 2} 819 vdslLineExtMCMGroups OBJECT IDENTIFIER ::= 820 { vdslLineExtMCMConformance 1 } 821 vdslLineExtMCMCompliances OBJECT IDENTIFIER ::= 822 { vdslLineExtMCMConformance 2 } 824 vdslLineExtMCMMibCompliance MODULE-COMPLIANCE 825 STATUS current 826 DESCRIPTION 827 "The compliance statement for SNMP entities which 828 manage VDSL interfaces." 830 MODULE -- this module 831 GROUP vdslLineExtMCMGroup 832 DESCRIPTION 833 "This group is an optional extension for VDSL lines which 834 utilize Multiple Carrier Modulation (MCM)." 836 ::= { vdslLineExtMCMCompliances 1 } 838 -- units of conformance 840 vdslLineExtMCMGroup OBJECT-GROUP 841 OBJECTS 842 { 843 vdslLineMCMConfProfileTxWindowLength, 844 vdslLineMCMConfProfileRowStatus, 845 vdslLineMCMConfProfileTxBandStart, 846 vdslLineMCMConfProfileTxBandStop, 847 vdslLineMCMConfProfileTxBandRowStatus, 848 vdslLineMCMConfProfileRxBandStart, 849 vdslLineMCMConfProfileRxBandStop, 850 vdslLineMCMConfProfileRxBandRowStatus, 851 vdslLineMCMConfProfileTxPSDTone, 852 vdslLineMCMConfProfileTxPSDPSD, 853 vdslLineMCMConfProfileTxPSDRowStatus, 854 vdslLineMCMConfProfileMaxTxPSDTone, 855 vdslLineMCMConfProfileMaxTxPSDPSD, 856 vdslLineMCMConfProfileMaxTxPSDRowStatus, 857 vdslLineMCMConfProfileMaxRxPSDTone, 858 vdslLineMCMConfProfileMaxRxPSDPSD, 859 vdslLineMCMConfProfileMaxRxPSDRowStatus 860 } 861 STATUS current 862 DESCRIPTION 863 "A collection of objects providing configuration 864 information for a VDSL line based upon multiple 865 carrier modulation modem." 866 ::= { vdslLineExtMCMGroup 1 } 868 END 870 5. Intellectual Property Notice 872 The IETF takes no position regarding the validity or scope of any 873 intellectual property or other rights that might be claimed to 874 pertain to the implementation or use of the technology described in 875 this document or the extent to which any license under such rights 876 might or might not be available; neither does it represent that it 877 has made any effort to identify any such rights. Information on the 878 IETF's procedures with respect to rights in standards-track and 879 standards-related documentation can be found in BCP-11. Copies of 880 claims of rights made available for publication and any assurances 881 of licenses to be made available, or the result of an attempt made 882 to obtain a general license or permission for the use of such 883 proprietary rights by implementors or users of this specification 884 can be obtained from the IETF Secretariat. 886 The IETF invites any interested party to bring to its attention any 887 copyrights, patents or patent applications, or other proprietary 888 rights which may cover technology that may be required to practice 889 this standard. Please address the information to the IETF Executive 890 Director. 892 6. Normative References 894 [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", 895 February 2003. 897 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 898 (TM); Access transmission systems on metallic access 899 cables; Very high speed Digital Subscriber Line (VDSL); 900 Part 1: Functional requirements", October 1999. 902 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 903 (TM); Access transmission systems on metallic access 904 cables; Very high speed Digital Subscriber Line (VDSL); 905 Part 1: Transceiver specification", February 2001. 907 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 908 foundation", November 2001. 910 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 911 Subscriber Line (DSL) Transceivers", July 1999. 913 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 914 Requirement Levels", BCP 14, RFC 2119, March 1997. 916 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 917 J., Rose, M. and S. Waldbusser, "Structure of 918 Management Information Version 2 (SMIv2)", STD 58, RFC 919 2578, April 1999. 921 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 922 J., Rose, M. and S. Waldbusser, "Textual Conventions 923 for SMIv2", STD 58, RFC 2579, April 1999. 925 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 926 J., Rose, M. and S. Waldbusser, "Conformance 927 Statements for SMIv2", STD 58, RFC 2580, April 1999. 929 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 930 Group MIB", RFC 2863, June 2000. 932 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 933 Simple Network Management Protocol (SNMP)", STD 62, RFC 934 3418, December 2002. 936 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 937 Performance History Based on 15 Minute Intervals", RFC 938 3593, September 2003. 940 [RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions 941 for MIB Modules Using Performance History Based on 942 15 Minute Intervals", RFC XXXX, YYYY 2003. 944 [RFCXXXX] Ray, B. and R. Abbi, "Definitions of Managed Objects for 945 Very High Speed Digital Subscriber Lines (VDSL)",RFC XXXX, 946 YYYY 2003. 948 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 949 Subscriber Line (VDSL) Metallic Interface, Part 1: 950 Functional Requirements and Common Specification", 951 February 2001. 953 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 954 2: Technical Specification for a Single-Carrier 955 Modulation (SCM) Transceiver", November 2001. 957 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 958 3: Technical Specification for a Multi-Carrier 959 Modulation (MCM) Transceiver", November 2000. 961 7. Informative References 963 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 964 Access Control Model (VACM) for the Simple Network 965 Management Protocol (SNMP)", RFC 2575, April 1999. 967 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 968 "Introduction and Applicability Statements for Internet- 969 Standard Management Framework", RFC 3410, December 2002. 971 8. Security Considerations 973 There are a number of management objects defined in this MIB that 974 have a MAX-ACCESS clause of read-write and/or read-create. Such 975 objects may be considered sensitive or vulnerable in some network 976 environments. The support for SET operations in a non-secure 977 environment without proper protection can have a negative effect on 978 network operations. 980 VDSL layer connectivity from the Vtur will permit the subscriber 981 to manipulate both the VDSL link directly and the VDSL embedded 982 operations channel (EOC) for their own loop. For example, unchecked 983 or unfiltered fluctuations initiated by the subscriber could 984 generate sufficient notifications to potentially overwhelm either 985 the management interface to the network or the element manager. 987 For this reason, there are a number of managed objects in this MIB 988 that may contain sensitive information. 990 It is thus important to control even GET access to these objects and 991 possibly to even encrypt the values of these objects when sending 992 them over the network via SNMP. Not all versions of SNMP provide 993 features for such a secure environment. 995 Further, notifications generated by agents implementing this MIB 996 will contain the above threshold information. 998 SNMP versions prior to SNMPv3 did not include adequate security. 999 Even if the network itself is secure (for example by using IPSec), 1000 even then, there is no control as to who on the secure network is 1001 allowed to access and GET/SET (read/change/create/delete) objects 1002 which utilize the textual conventions defined in this MIB module. 1004 It is RECOMMENDED that implementers consider the security features 1005 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1006 including full support for the SNMPv3 cryptographic mechanisms (for 1007 authentication and privacy). 1009 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1010 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1011 enable cryptographic security. It is then a customer/operator 1012 responsibility to ensure that the SNMP entity giving access to an 1013 instance of a MIB module which utilizes the textual conventions 1014 defined in this MIB module is properly configured to give access to 1015 the objects only to those principals (users) that have legitimate 1016 rights to indeed GET or SET (change/create/delete) them. 1018 9. Acknowledgments 1020 This document contains many definitions taken from 1021 draft-ietf-adslmib-vdsl-07.txt. As such, any credit for the text 1022 found within should be fully attributed to the authors of that 1023 document. 1025 10. Authors' Addresses 1027 Menachem Dodge 1028 Infineon Technologies Savan Ltd. 1029 6 Hagavish St. 1030 Poleg Industrial Area, 1031 Netanya 42504, 1032 Israel. 1034 Phone: +972 9 892 4116 1035 Fax: +972 9 865 8756 1036 Email: menachem.dodge@infineon.com 1038 Bob Ray 1039 PESA Switching Systems, Inc. 1040 330-A Wynn Drive 1041 Huntsville, AL 35805 1042 USA 1044 Phone: +1 256 726 9200 ext. 142 1045 Fax: +1 256 726 9271 1046 EMail: rray@pesa.com 1048 11. Full Copyright Statement 1050 Copyright (C) The Internet Society (2003). All Rights Reserved. 1051 This document and translations of it may be copied and furnished to 1052 others, and derivative works that comment on or otherwise explain it 1053 or assist in its implementation may be prepared, copied, published 1054 and distributed, in whole or in part, without restriction of any 1055 kind, provided that the above copyright notice and this paragraph 1056 are included on all such copies and derivative works. However, this 1057 document itself may not be modified in any way, such as by removing 1058 the copyright notice or references to the Internet Society or other 1059 Internet organizations, except as needed for the purpose of 1060 developing Internet standards in which case the procedures for 1061 copyrights defined in the Internet Standards process must be 1062 followed, or as required to translate it into languages other than 1063 English. 1065 The limited permissions granted above are perpetual and will not be 1066 revoked by the Internet Society or its successors or assigns. 1068 This document and the information contained herein is provided on an 1069 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1070 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1071 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1072 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1073 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.