idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-mcm-00.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 4 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. ** 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 148: '...ll of the objects in this group MAY be...' RFC 2119 keyword, line 173: '...lMCMGroup tables MAY be implemented fo...' RFC 2119 keyword, line 179: '... SHOULD be stored persistently. Fol...' RFC 2119 keyword, line 201: '... It SHOULD also be noted that interf...' RFC 2119 keyword, line 202: '... VACM data relating to these SHOULD be...' (9 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == 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 (September 2003) is 7519 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: 'ETSI2701' is defined on line 882, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 887, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 892, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 895, but no explicit reference was found in the text == Unused Reference: 'RFC2493' is defined on line 898, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 918, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 930, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 935, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 939, but no explicit reference was found in the text -- 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' ** Obsolete normative reference: RFC 2493 (Obsoleted by RFC 3593) -- 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: 7 errors (**), 0 flaws (~~), 12 warnings (==), 11 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-00.txt B. Ray 4 PESA Switching Systems 5 September 2003 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 (2003). 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 ......................................... 18 58 6. Normative References .......................................... 18 59 7. Informative References ........................................ 19 60 8. Security Considerations ....................................... 19 61 9. Acknowledgements .............................................. 20 62 10. Authors' Addresses ............................................ 21 63 11. Full Copyright Statement ...................................... 21 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 "200309230000Z" -- September 23, 2003 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 304 " 306 vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslEXTMCMMIB 1 } 307 vdslEXTMCMMibObjects OBJECT IDENTIFIER ::= { vdslLineExtMCMMib 1 } 309 -- 310 -- Multiple carrier modulation (MCM) configuration profile tables 311 -- 313 vdslLineMCMConfProfileTable OBJECT-TYPE 314 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "This table contains additional information on 319 multiple carrier VDSL lines. One entry in this table 320 reflects a profile defined by a manager which can be used 321 to configure the VDSL line. 323 The entries in this table MUST NOT be used for single 324 carrier (SCM) VDSL lines." 325 ::= { vdslEXTMCMMibObjects 1 } 327 vdslLineMCMConfProfileEntry OBJECT-TYPE 328 SYNTAX VdslLineMCMConfProfileEntry 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "Each entry consists of a list of parameters that 333 represents the configuration of a multiple carrier 334 modulation VDSL modem. 336 A default profile with an index of 'DEFVAL', will always 337 exist and its parameters will be set to vendor specific 338 values, unless otherwise specified in this document." 339 INDEX { vdslLineConfProfileName } 340 ::= { vdslLineMCMConfProfileTable 1 } 342 VdslLineMCMConfProfileEntry ::= 343 SEQUENCE 344 { 345 vdslMCMConfProfileTxWindowLength Unsigned32, 346 vdslMCMConfProfileRowStatus RowStatus 347 } 349 vdslMCMConfProfileTxWindowLength OBJECT-TYPE 350 SYNTAX Unsigned32 (1..255) 351 UNITS "samples" 352 MAX-ACCESS read-create 353 STATUS current 354 DESCRIPTION 355 "Specifies the length of the transmit window, counted 356 in samples at the sampling rate corresponding to the 357 negotiated value of N." 358 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 359 ::= { vdslLineMCMConfProfileEntry 1 } 361 vdslMCMConfProfileRowStatus OBJECT-TYPE 362 SYNTAX RowStatus 363 MAX-ACCESS read-create 364 STATUS current 365 DESCRIPTION 366 "This object is used to create a new row or modify or 367 delete an existing row in this table. 369 A profile activated by setting this object to `active'. 370 When `active' is set, the system will validate the profile. 372 Before a profile can be deleted or taken out of 373 service, (by setting this object to `destroy' or 374 `outOfService') it must be first unreferenced 375 from all associated lines." 376 ::= { vdslLineMCMConfProfileEntry 2 } 378 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 379 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 380 MAX-ACCESS not-accessible 381 STATUS current 382 DESCRIPTION 383 "This table contains transmit band descriptor configuration 384 information for a VDSL line. Each entry in this table 385 reflects the configuration for one of possibly many bands 386 with a multiple carrier modulation (MCM) VDSL line. 387 These entries are defined by a manager and can be used to 388 configure the VDSL line. 390 The entries in this table MUST NOT be used for single 391 carrier (SCM) VDSL lines." 392 ::= { vdslEXTMCMMibObjects 2 } 394 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 395 SYNTAX VdslLineMCMConfProfileTxBandEntry 396 MAX-ACCESS not-accessible 397 STATUS current 398 DESCRIPTION 399 "Each entry consists of a transmit band descriptor, which 400 is defined by a start and a stop tone index. 401 A default profile with an index of 'DEFVAL', will 402 always exist and its parameters will be set to vendor 403 specific values, unless otherwise specified in this 404 document." 405 INDEX { vdslLineConfProfileName, 406 vdslMCMConfProfileTxBandNumber } 407 ::= { vdslLineMCMConfProfileTxBandTable 1 } 409 VdslLineMCMConfProfileTxBandEntry ::= 410 SEQUENCE 411 { 412 vdslMCMConfProfileTxBandNumber Unsigned32, 413 vdslMCMConfProfileTxBandStart Unsigned32, 414 vdslMCMConfProfileTxBandStop Unsigned32, 415 vdslMCMConfProfileTxBandRowStatus RowStatus 416 } 418 vdslMCMConfProfileTxBandNumber OBJECT-TYPE 419 SYNTAX Unsigned32 420 MAX-ACCESS not-accessible 421 STATUS current 422 DESCRIPTION 423 "The index for this band descriptor entry." 424 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 426 vdslMCMConfProfileTxBandStart OBJECT-TYPE 427 SYNTAX Unsigned32 428 MAX-ACCESS read-create 429 STATUS current 430 DESCRIPTION 431 "Start tone index for this band." 432 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 433 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 435 vdslMCMConfProfileTxBandStop OBJECT-TYPE 436 SYNTAX Unsigned32 437 MAX-ACCESS read-create 438 STATUS current 439 DESCRIPTION 440 "Stop tone index for this band." 441 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 442 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 444 vdslMCMConfProfileTxBandRowStatus OBJECT-TYPE 445 SYNTAX RowStatus 446 MAX-ACCESS read-create 447 STATUS current 448 DESCRIPTION 449 "This object is used to create a new row or modify or 450 delete an existing row in this table. 451 A profile activated by setting this object to `active'. 452 When `active' is set, the system will validate the profile. 454 Before a profile can be deleted or taken out of 455 service, (by setting this object to `destroy' or 456 `outOfService') it must be first unreferenced 457 from all associated lines." 458 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 460 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 461 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "This table contains receive band descriptor configuration 466 information for a VDSL line. Each entry in this table 467 reflects the configuration for one of possibly many bands 468 with a multiple carrier modulation (MCM) VDSL line. 469 These entries are defined by a manager and can be used to 470 configure the VDSL line. 472 The entries in this table MUST NOT be used for single 473 carrier (SCM) VDSL lines." 474 ::= { vdslEXTMCMMibObjects 3 } 476 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 477 SYNTAX VdslLineMCMConfProfileRxBandEntry 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "Each entry consists of a transmit band descriptor, which 482 is defined by a start and a stop tone index. 484 A default profile with an index of 'DEFVAL', will 485 always exist and its parameters will be set to vendor 486 specific values, unless otherwise specified in this 487 document." 488 INDEX { vdslLineConfProfileName, 489 vdslMCMConfProfileRxBandNumber } 490 ::= { vdslLineMCMConfProfileRxBandTable 1 } 492 VdslLineMCMConfProfileRxBandEntry ::= 493 SEQUENCE 494 { 495 vdslMCMConfProfileRxBandNumber Unsigned32, 496 vdslMCMConfProfileRxBandStart Unsigned32, 497 vdslMCMConfProfileRxBandStop Unsigned32, 498 vdslMCMConfProfileRxBandRowStatus RowStatus 499 } 501 vdslMCMConfProfileRxBandNumber OBJECT-TYPE 502 SYNTAX Unsigned32 503 MAX-ACCESS not-accessible 504 STATUS current 505 DESCRIPTION 506 "The index for this band descriptor entry." 507 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 509 vdslMCMConfProfileRxBandStart OBJECT-TYPE 510 SYNTAX Unsigned32 511 MAX-ACCESS read-create 512 STATUS current 513 DESCRIPTION 514 "Start tone index for this band." 515 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 516 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 518 vdslMCMConfProfileRxBandStop OBJECT-TYPE 519 SYNTAX Unsigned32 520 MAX-ACCESS read-create 521 STATUS current 522 DESCRIPTION 523 "Stop tone index for this band." 524 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 525 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 527 vdslMCMConfProfileRxBandRowStatus OBJECT-TYPE 528 SYNTAX RowStatus 529 MAX-ACCESS read-create 530 STATUS current 531 DESCRIPTION 532 "This object is used to create a new row or modify or 533 delete an existing row in this table. 535 A profile activated by setting this object to `active'. 536 When `active' is set, the system will validate the profile. 538 Before a profile can be deleted or taken out of 539 service, (by setting this object to `destroy' or 540 `outOfService') it must be first unreferenced 541 from all associated lines." 542 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 544 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 545 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "This table contains transmit PSD mask descriptor 550 configuration information for a VDSL line. Each entry in 551 this table reflects the configuration for one tone within 552 a multiple carrier modulation (MCM) VDSL line. These 553 entries are defined by a manager and can be used to 554 configure the VDSL line. 556 The entries in this table MUST NOT be used for single 557 carrier (SCM) VDSL lines." 558 ::= { vdslEXTMCMMibObjects 4 } 560 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 561 SYNTAX VdslLineMCMConfProfileTxPSDEntry 562 MAX-ACCESS not-accessible 563 STATUS current 564 DESCRIPTION 565 "Each entry consists of a transmit PSD mask descriptor, 566 which defines the power spectral density (PSD) for a tone. 568 A default profile with an index of 'DEFVAL', will 569 always exist and its parameters will be set to vendor 570 specific values, unless otherwise specified in this 571 document." 572 INDEX { vdslLineConfProfileName, 573 vdslMCMConfProfileTxPSDNumber } 574 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 576 VdslLineMCMConfProfileTxPSDEntry ::= 577 SEQUENCE 578 { 579 vdslMCMConfProfileTxPSDNumber Unsigned32, 580 vdslMCMConfProfileTxPSDTone Unsigned32, 581 vdslMCMConfProfileTxPSDPSD Unsigned32, 582 vdslMCMConfProfileTxPSDRowStatus RowStatus 583 } 585 vdslMCMConfProfileTxPSDNumber OBJECT-TYPE 586 SYNTAX Unsigned32 587 MAX-ACCESS not-accessible 588 STATUS current 589 DESCRIPTION 590 "The index for this mask descriptor entry." 591 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 593 vdslMCMConfProfileTxPSDTone OBJECT-TYPE 594 SYNTAX Unsigned32 595 MAX-ACCESS read-create 596 STATUS current 597 DESCRIPTION 598 "The tone index for which the PSD is being specified." 599 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 600 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 602 vdslMCMConfProfileTxPSDPSD OBJECT-TYPE 603 SYNTAX Unsigned32 604 UNITS "0.5dBm" 605 MAX-ACCESS read-create 606 STATUS current 607 DESCRIPTION 608 "Power Spectral Density level in steps of 0.5dB with 609 an offset of -140dbm/Hz." 610 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 611 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 613 vdslMCMConfProfileTxPSDRowStatus OBJECT-TYPE 614 SYNTAX RowStatus 615 MAX-ACCESS read-create 616 STATUS current 617 DESCRIPTION 618 "This object is used to create a new row or modify or 619 delete an existing row in this table. 621 A profile activated by setting this object to `active'. 622 When `active' is set, the system will validate the profile. 624 Before a profile can be deleted or taken out of 625 service, (by setting this object to `destroy' or 626 `outOfService') it must be first unreferenced 627 from all associated lines." 628 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 630 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 631 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "This table contains transmit maximum PSD mask descriptor 636 configuration information for a VDSL line. Each entry in 637 this table reflects the configuration for one tone within 638 a multiple carrier modulation (MCM) VDSL modem. These 639 entries are defined by a manager and can be used to 640 configure the VDSL line. 642 The entries in this table MUST NOT be used for single 643 carrier (SCM) VDSL lines." 644 ::= { vdslEXTMCMMibObjects 5 } 646 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 647 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "Each entry consists of a transmit PSD mask descriptor, 652 which defines the maximum power spectral density (PSD) 653 for a tone. 655 A default profile with an index of 'DEFVAL', will 656 always exist and its parameters will be set to vendor 657 specific values, unless otherwise specified in this 658 document." 659 INDEX { vdslLineConfProfileName, 660 vdslMCMConfProfileMaxTxPSDNumber } 661 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 663 VdslLineMCMConfProfileMaxTxPSDEntry ::= 664 SEQUENCE 665 { 666 vdslMCMConfProfileMaxTxPSDNumber Unsigned32, 667 vdslMCMConfProfileMaxTxPSDTone Unsigned32, 668 vdslMCMConfProfileMaxTxPSDPSD Unsigned32, 669 vdslMCMConfProfileMaxTxPSDRowStatus RowStatus 670 } 672 vdslMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 673 SYNTAX Unsigned32 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "The index for this band descriptor entry." 678 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 680 vdslMCMConfProfileMaxTxPSDTone OBJECT-TYPE 681 SYNTAX Unsigned32 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "The tone index for which the PSD is being specified." 686 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 687 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 689 vdslMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 690 SYNTAX Unsigned32 691 UNITS "0.5dBm" 692 MAX-ACCESS read-create 693 STATUS current 694 DESCRIPTION 695 "Power Spectral Density level in steps of 0.5dB with 696 an offset of -140dbm/Hz." 697 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 698 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 700 vdslMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 701 SYNTAX RowStatus 702 MAX-ACCESS read-create 703 STATUS current 704 DESCRIPTION 705 "This object is used to create a new row or modify or 706 delete an existing row in this table. 708 A profile activated by setting this object to `active'. 709 When `active' is set, the system will validate the profile. 711 Before a profile can be deleted or taken out of 712 service, (by setting this object to `destroy' or 713 `outOfService') it must be first unreferenced 714 from all associated lines." 715 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 717 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 718 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 719 MAX-ACCESS not-accessible 720 STATUS current 721 DESCRIPTION 722 "This table contains maximum receive PSD mask descriptor 723 configuration information for a VDSL line. Each entry in 724 this table reflects the configuration for one tone within 725 a multiple carrier modulation (MCM) VDSL modem. These 726 entries are defined by a manager and can be used to 727 configure the VDSL line. 729 The entries in this table MUST NOT be used for single 730 carrier (SCM) VDSL lines." 731 ::= { vdslEXTMCMMibObjects 6 } 733 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 734 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "Each entry consists of a transmit PSD mask descriptor, 739 which defines the power spectral density (PSD) for a 740 tone. 742 A default profile with an index of 'DEFVAL', will 743 always exist and its parameters will be set to vendor 744 specific values, unless otherwise specified in this 745 document." 746 INDEX { vdslLineConfProfileName, 747 vdslMCMConfProfileMaxRxPSDNumber } 748 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 750 VdslLineMCMConfProfileMaxRxPSDEntry ::= 751 SEQUENCE 752 { 753 vdslMCMConfProfileMaxRxPSDNumber Unsigned32, 754 vdslMCMConfProfileMaxRxPSDTone Unsigned32, 755 vdslMCMConfProfileMaxRxPSDPSD Unsigned32, 756 vdslMCMConfProfileMaxRxPSDRowStatus RowStatus 757 } 759 vdslMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 760 SYNTAX Unsigned32 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "The index for this band descriptor entry." 765 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 767 vdslMCMConfProfileMaxRxPSDTone OBJECT-TYPE 768 SYNTAX Unsigned32 769 MAX-ACCESS read-create 770 STATUS current 771 DESCRIPTION 772 "The tone index for which the PSD is being specified." 773 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 774 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 776 vdslMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 777 SYNTAX Unsigned32 778 UNITS "0.5dBm" 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "Power Spectral Density level in steps of 0.5dB with 783 an offset of -140dbm/Hz." 784 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 785 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 787 vdslMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 788 SYNTAX RowStatus 789 MAX-ACCESS read-create 790 STATUS current 791 DESCRIPTION 792 "This object is used to create a new row or modify or 793 delete an existing row in this table. 795 A profile activated by setting this object to `active'. 796 When `active' is set, the system will validate the profile. 798 Before a profile can be deleted or taken out of 799 service, (by setting this object to `destroy' or 800 `outOfService') it must be first unreferenced 801 from all associated lines." 802 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 804 -- conformance information 806 vdslExtMCMConformance OBJECT IDENTIFIER ::= { vdslLineExtMCMMib 2 } 807 vdslExtMCMGroups OBJECT IDENTIFIER ::= { vdslExtMCMConformance 1 } 808 vdslExtMCMCompliances OBJECT IDENTIFIER ::= 809 { vdslExtMCMConformance 2 } 811 vdslLineExtMCMMibCompliance MODULE-COMPLIANCE 812 STATUS current 813 DESCRIPTION 814 "The compliance statement for SNMP entities which 815 manage VDSL interfaces." 817 MODULE -- this module 819 GROUP vdslMCMGroup 820 DESCRIPTION 821 "This group is an optional extension for VDSL lines which 822 utilize Multiple Carrier Modulation (MCM)." 824 ::= { vdslCompliances 1 } 826 -- units of conformance 828 vdslMCMGroup OBJECT-GROUP 829 OBJECTS 830 { 831 vdslMCMConfProfileTxWindowLength, 832 vdslMCMConfProfileRowStatus, 833 vdslMCMConfProfileTxBandStart, 834 vdslMCMConfProfileTxBandStop, 835 vdslMCMConfProfileTxBandRowStatus, 836 vdslMCMConfProfileRxBandStart, 837 vdslMCMConfProfileRxBandStop, 838 vdslMCMConfProfileRxBandRowStatus, 839 vdslMCMConfProfileTxPSDTone, 840 vdslMCMConfProfileTxPSDPSD, 841 vdslMCMConfProfileTxPSDRowStatus, 842 vdslMCMConfProfileMaxTxPSDTone, 843 vdslMCMConfProfileMaxTxPSDPSD, 844 vdslMCMConfProfileMaxTxPSDRowStatus, 845 vdslMCMConfProfileMaxRxPSDTone, 846 vdslMCMConfProfileMaxRxPSDPSD, 847 vdslMCMConfProfileMaxRxPSDRowStatus 848 } 849 STATUS current 850 DESCRIPTION 851 "A collection of objects providing configuration 852 information for a VDSL line based upon multiple 853 carrier modulation modem." 854 ::= { vdslGroups 1 } 856 END 858 5. Intellectual Property Notice 860 The IETF takes no position regarding the validity or scope of any 861 intellectual property or other rights that might be claimed to 862 pertain to the implementation or use of the technology described in 863 this document or the extent to which any license under such rights 864 might or might not be available; neither does it represent that it 865 has made any effort to identify any such rights. Information on the 866 IETF's procedures with respect to rights in standards-track and 867 standards-related documentation can be found in BCP-11. Copies of 868 claims of rights made available for publication and any assurances 869 of licenses to be made available, or the result of an attempt made 870 to obtain a general license or permission for the use of such 871 proprietary rights by implementors or users of this specification 872 can be obtained from the IETF Secretariat. 874 The IETF invites any interested party to bring to its attention any 875 copyrights, patents or patent applications, or other proprietary 876 rights which may cover technology that may be required to practice 877 this standard. Please address the information to the IETF Executive 878 Director. 880 6. Normative References 882 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 883 (TM); Access transmission systems on metallic access 884 cables; Very high speed Digital Subscriber Line (VDSL); 885 Part 1: Functional requirements", October 1999. 887 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 888 (TM); Access transmission systems on metallic access 889 cables; Very high speed Digital Subscriber Line (VDSL); 890 Part 1: Transceiver specification", February 2001. 892 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 893 foundation", November 2001. 895 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 896 Subscriber Line (DSL) Transceivers", July 1999. 898 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 899 Performance History Based on 15 Minute Intervals", RFC 900 2493, January 1999. 902 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 903 Rose, M. and S. Waldbusser, "Structure of Management 904 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 905 1999. 907 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 908 Rose, M. and S. Waldbusser, "Textual Conventions for 909 SMIv2", STD 58, RFC 2579, April 1999. 911 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 912 Rose, M. and S. Waldbusser, "Conformance Statements for 913 SMIv2", STD 58, RFC 2580, April 1999. 915 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 916 MIB", RFC 2863, June 2000. 918 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 919 Simple Network Management Protocol (SNMP)", STD 62, RFC 920 3418, December 2002. 922 [RFCXXXX] Ray, B. and R. Abbi, "Definitions of Managed Objects for 923 Very High Speed Digital Subscriber Lines (VDSL)", RFC XXXX, 924 YYYY 2003. 926 [RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions 927 for MIB Modules Using Performance History Based on 928 15 Minute Intervals", RFC XXXX, YYYY 2003. 930 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 931 Subscriber Line (VDSL) Metallic Interface, Part 1: 932 Functional Requirements and Common Specification", 933 February 2001. 935 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 936 Technical Specification for a Single-Carrier Modulation 937 (SCM) Transceiver", November 2001. 939 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 940 Technical Specification for a Multi-Carrier Modulation 941 (MCM) Transceiver", November 2000. 943 7. Informative References 945 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 946 Access Control Model (VACM) for the Simple Network 947 Management Protocol (SNMP)", RFC 2575, April 1999. 949 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 950 "Introduction and Applicability Statements for Internet- 951 Standard Management Framework", RFC 3410, December 2002. 953 8. Security Considerations 955 There are a number of management objects defined in this MIB that 956 have a MAX-ACCESS clause of read-write and/or read-create. Such 957 objects may be considered sensitive or vulnerable in some network 958 environments. The support for SET operations in a non-secure 959 environment without proper protection can have a negative effect on 960 network operations. 962 VDSL layer connectivity from the Vtur will permit the subscriber 963 to manipulate both the VDSL link directly and the VDSL embedded 964 operations channel (EOC) for their own loop. For example, unchecked 965 or unfiltered fluctuations initiated by the subscriber could 966 generate sufficient notifications to potentially overwhelm either 967 the management interface to the network or the element manager. 969 For this reason, there are a number of managed objects in this MIB 970 that may contain sensitive information. 972 It is thus important to control even GET access to these objects and 973 possibly to even encrypt the values of these objects when sending 974 them over the network via SNMP. Not all versions of SNMP provide 975 features for such a secure environment. 977 Further, notifications generated by agents implementing this MIB 978 will contain the above threshold information. 980 SNMP versions prior to SNMPv3 did not include adequate security. 981 Even if the network itself is secure (for example by using IPSec), 982 even then, there is no control as to who on the secure network is 983 allowed to access and GET/SET (read/change/create/delete) objects 984 which utilize the textual conventions defined in this MIB module. 986 It is RECOMMENDED that implementers consider the security features 987 as provided by the SNMPv3 framework (see [RFC3410], section 8), 988 including full support for the SNMPv3 cryptographic mechanisms (for 989 authentication and privacy). 991 Further, deployment of SNMP versions prior to SNMPv3 is NOT 992 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 993 enable cryptographic security. It is then a customer/operator 994 responsibility to ensure that the SNMP entity giving access to an 995 instance of a MIB module which utilizes the textual conventions 996 defined in this MIB module is properly configured to give access to 997 the objects only to those principals (users) that have legitimate 998 rights to indeed GET or SET (change/create/delete) them. 1000 9. Acknowledgments 1002 This document contains many definitions taken from 1003 draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text 1004 found within should be full attributed to the authors of that 1005 document. 1007 10. Authors' Addresses 1009 Menachem Dodge 1010 Infineon Technologies Savan Ltd. 1011 6 Hagavish St. 1012 Poleg Industrial Area, 1013 Netanya 42504, 1014 Israel. 1016 Phone: +972 9 892 4116 1017 Fax: +972 9 865 8756 1018 Email: menachem.dodge@infineon.com 1020 Bob Ray 1021 PESA Switching Systems, Inc. 1022 330-A Wynn Drive 1023 Huntsville, AL 35805 1024 USA 1026 Phone: +1 256 726 9200 ext. 142 1027 Fax: +1 256 726 9271 1028 EMail: rray@pesa.com 1030 11. Full Copyright Statement 1032 Copyright (C) The Internet Society (2003). All Rights Reserved. 1033 This document and translations of it may be copied and furnished to 1034 others, and derivative works that comment on or otherwise explain it 1035 or assist in its implementation may be prepared, copied, published 1036 and distributed, in whole or in part, without restriction of any 1037 kind, provided that the above copyright notice and this paragraph 1038 are included on all such copies and derivative works. However, this 1039 document itself may not be modified in any way, such as by removing 1040 the copyright notice or references to the Internet Society or other 1041 Internet organizations, except as needed for the purpose of 1042 developing Internet standards in which case the procedures for 1043 copyrights defined in the Internet Standards process must be 1044 followed, or as required to translate it into languages other than 1045 English. 1047 The limited permissions granted above are perpetual and will not be 1048 revoked by the Internet Society or its successors or assigns. 1050 This document and the information contained herein is provided on an 1051 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1052 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1053 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1054 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1055 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.