idnits 2.17.1 draft-dodge-adslmib-vdsl-ext-scm-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 5 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** There are 8 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 143: '...ts in this group MAY be implemented fo...' RFC 2119 keyword, line 165: '...lSCMGroup tables MAY be implemented fo...' RFC 2119 keyword, line 171: '... SHOULD be stored persistently. Fol...' RFC 2119 keyword, line 190: '... It SHOULD also be noted that interf...' RFC 2119 keyword, line 191: '... VACM data relating to these SHOULD be...' (3 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 (July 2003) is 7591 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 88, but not defined == Unused Reference: 'ETSI2701' is defined on line 592, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 597, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 602, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 605, but no explicit reference was found in the text == Unused Reference: 'RFC2493' is defined on line 608, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 628, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 640, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 645, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 649, 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: 8 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-dodge-adslmib-vdsl-ext-scm-01.txt B. Ray 4 PESA Switching Systems 5 July 2003 7 Definitions of Managed Object Extensions 8 for Very High Speed Digital Subscriber Lines (VDSL) Using 9 Single Carrier Modulation (SCM) 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 Single Carrier 43 Modulation (SCM) 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 .................................... 4 56 4. Definitions ................................................... 5 57 5. Intellectual Property ......................................... 12 58 6. Normative References .......................................... 12 59 7. Informative References ........................................ 13 60 8. Security Considerations ....................................... 14 61 9. Acknowledgements .............................................. 15 62 10. Authors' Addresses ............................................ 15 63 11. Full Copyright Statement ...................................... 15 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 SCM 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 protocol- 87 dependent (and line-code dependent) management framework for VDSL 88 lines specified by DSLF has been taken into consideration [DSLFXXXXXX]. 90 The MIB module is located in the MIB tree under MIB 2 transmission, 91 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section 92 of this document. 94 2.1 Relationship of this MIB Module to other MIB Modules 96 The relationship of the VDSL Line MIB to other MIBS and in particular 97 to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in the 98 VDSL-LINE CORE MIB RFC XXXX [RFCXXXX]. This section outlines the 99 relationship of this VDSL Line Extension MIB to the VDSL-LINE CORE MIB 100 RFC XXXX [RFCXXXX]. 102 2.2 Conventions used in the MIB Module 104 2.2.1 Naming Conventions 106 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 107 B. Vtur -- (VTUR) transceiver at Remote end of line 108 C. Vtu -- One of either Vtuc or Vtur 109 D. Curr -- Current 110 E. Prev -- Previous 111 F. Atn -- Attenuation 112 G. ES -- Errored Second 113 H. SES -- Severely Errored Second 114 I. UAS -- Unavailable Second 115 J. LCS -- Line Code Specific 116 K. Lof -- Loss of Frame 117 L. Lol -- Loss of Link 118 M. Los -- Loss of Signal 119 N. Lpr -- Loss of Power 120 O. xxxs -- Sum of Seconds in which xxx has occurs (e.g., xxx=Lof, 121 Los, Lpr, Lol) 122 P. Max -- Maximum 123 Q. Mgn -- Margin 124 R. Min -- Minimum 125 S. Psd -- Power Spectral Density 126 T. Snr -- Signal to Noise Ratio 127 U. Tx -- Transmit 128 V. Blks -- Blocks 130 2.3 Structure 132 The SCM VDSL Line Extension MIB contains the following MIB group: 134 o vdslSCMGroup : 136 This group supports MIB objects for defining configuration profiles 137 and for montioring individual bands of Single Carrier Modulation (SCM) 138 VDSL modems. It contains the following tables: 140 - vdslLineSCMConfProfileTxBandTable 141 - vdslSCMPhysBandTable 143 Either none, one or both objects in this group MAY be implemented for 144 SCM VDSL lines. 146 Figure 1, below, displays the relationship of the tables in the 147 vdslSCMGroup to the vdslGroup and to the ifEntry: 149 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 151 vdslLineTableEntry (vdslLineCoding=SCM) 152 ----> vdslPhysTableEntry 1:(0..2) 153 ----> vdslSCMPhysBandTable 1:(0..1) 155 vdslLineConfProfileEntry(vdslLineConfProfileName) 156 ----> vdslLineSCMConfProfileTxBandTable 1:(0..1) 158 Figure 1: Table Relationships 160 When the vdslLineCoding is set to SCM, the vdslLineConfProfileName 161 which is the index of the vdslLineConfProfileEntry is also used as 162 the index to the vdslLineSCMConfProfileTxBandTable of the 163 vdslSCMGroup. The existence of an entry in any of the tables of 164 the vdslSCMGroup is optional. Either none, one or both of the 165 vdslSCMGroup tables MAY be implemented for a particular VDSL line 166 entity using SCM Line Coding. 168 2.4 Persistence 170 All read-write and read-create objects defined in this MIB module 171 SHOULD be stored persistently. Following is an exhaustive list of 172 these persistent objects: 174 vdslSCMConfProfileTxBandSide 175 vdslSCMConfProfileTxBandNumber 176 vdslSCMConfProfileTxBandCenterFrequency 177 vdslSCMConfProfileTxBandSymbolRate 178 vdslSCMConfProfileTxBandConstellationSize 179 vdslSCMConfProfileTxBandTransmitPSDLevel 180 vdslSCMConfProfileTxBandRowStatus 181 vdslSCMPhysBandSide 182 vdslSCMPhysBandNumber 183 vdslSCMPhysBandCurrSnrMgn 184 vdslSCMPhysBandCurrAtn 185 vdslSCMPhysBandCurrPSDLevel 186 vdslSCMPhysBandCurrSymbolRate 187 vdslSCMPhysBandCurrConstellationSize 188 vdslSCMPhysBandCurrCenterFrequency 190 It SHOULD also be noted that interface indices in this MIB are 191 maintained persistently. VACM data relating to these SHOULD be 192 stored persistently as well [RFC2575]. 194 3. Conformance and Compliance 196 For SCM VDSL lines, the following group is optional: 197 - vdslSCMGroup 199 4. Definitions 201 VDSL-LINE-EXT-SCM MIB DEFINITIONS ::= BEGIN 203 IMPORTS 205 MODULE-IDENTITY, 206 OBJECT-TYPE, 207 Counter64, 208 Gauge32, 209 Integer32, 210 Unsigned32, 211 NOTIFICATION-TYPE, 212 transmission FROM SNMPv2-SMI 213 TEXTUAL-CONVENTION, 214 RowStatus, 215 TruthValue FROM SNMPv2-TC 216 HCPerfValidIntervals, 217 HCPerfInvalidIntervals, 218 HCPerfTimeElapsed, 219 HCPerfIntervalThreshold, 220 HCPerfCurrentCount, 221 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 222 MODULE-COMPLIANCE, 223 OBJECT-GROUP, 224 NOTIFICATION-GROUP FROM SNMPv2-CONF 225 ifIndex FROM IF-MIB 226 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 227 vdslLineConfProfileName FROM VDSL-LINE-MIB 228 vdslPhysSide FROM VDSL-LINE-MIB 229 vdslLineEntity FROM VDSL-LINE-MIB 231 vdslExtSCMMIB MODULE-IDENTITY 232 LAST-UPDATED "200307270000Z" -- July 21, 2003 233 ORGANIZATION "ADSLMIB Working Group" 234 CONTACT-INFO "WG-email: adslmib@ietf.org 235 Info: https://www1.ietf.org/mailman/listinfo/adslmib 237 Chair: Mike Sneed 238 Sand Channel Systems 239 Postal: P.O. Box 37324 240 Raleigh NC 27627-732 241 Email: sneedmike@hotmail.com 242 Phone: +1 206 600 7022 243 co-editor: Menachem Dodge 244 Infineon Technologies Savan Ltd. 245 6 Hagavish St. 246 Postal: Poleg Industrial Area, 247 Netanya 42504, 248 Israel. 249 Email: menachem.dodge@infineon.com 250 Phone: +972 9 892 4116 252 Co-editor: Bob Ray 253 PESA Switching Systems, Inc. 254 Postal: 330-A Wynn Drive 255 Huntsville, AL 35805 256 USA 257 Email: rray@pesa.com 258 Phone: +1 256 726 9200 ext. 142 259 " 260 DESCRIPTION 261 "The VDSL Line core MIB found in RFC XXXX defines objects for 262 the management of a pair of VDSL transceivers at each end of 263 the VDSL line. The core MIB configures and monitors the line 264 code independent parameters (TC layer) of the VDSL line. 265 This MIB module is an optional extension of the core MIB and 266 defines objects for configuration and monitoring of the line 267 code specific (LCS) elements (PMD layer) for VDSL lines using 268 SCM coding. The objects in this extension MIB MUST NOT be used 269 for VDSL lines using MCM line coding. 271 Naming Conventions: 272 Vtuc -- (VTUC) transceiver at near (Central) end of line 273 Vtur -- (VTUR) transceiver at Remote end of line 274 Vtu -- One of either Vtuc or Vtur 275 Curr -- Current 276 Prev -- Previous 277 Atn -- Attenuation 278 ES -- Errored Second. 279 SES -- Severely Errored Second 280 UAS -- Unavailable Second 281 LCS -- Line Code Specific 282 Lof -- Loss of Frame 283 Lol -- Loss of Link 284 Los -- Loss of Signal 285 Lpr -- Loss of Power 286 xxxs -- Interval of Seconds in which xxx occurs 287 (e.g., xxx=Lof, Los, Lpr) 288 Max -- Maximum 289 Mgn -- Margin 290 Min -- Minimum 291 Psd -- Power Spectral Density 292 Snr -- Signal to Noise Ratio 293 Tx -- Transmit 294 Blks -- Blocks 295 " 297 vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslEXTSCMMIB 1 } 298 vdslEXTSCMMibObjects OBJECT IDENTIFIER ::= { vdslLineExtSCMMib 1 } 300 -- 301 -- Single carrier modulation (SCM) configuration profile tables 302 -- 304 vdslLineSCMConfProfileTxBandTable OBJECT-TYPE 305 SYNTAX SEQUENCE OF VdslLineSCMConfProfileTxBandEntry 306 MAX-ACCESS not-accessible 307 STATUS current 308 DESCRIPTION 309 "This table contains transmit band descriptor configuration 310 information for a VDSL line. Each entry in this table 311 reflects the configuration for one of possibly many bands 312 or sub-bands of a single carrier modulation (SCM) VDSL line. 313 These entries are defined by a manager and can be used to 314 configure the VDSL line." 315 ::= { vdslEXTSCMMibObjects 1 } 317 vdslLineSCMConfProfileTxBandEntry OBJECT-TYPE 318 SYNTAX VdslLineSCMConfProfileTxBandEntry 319 MAX-ACCESS not-accessible 320 STATUS current 321 DESCRIPTION 322 "Each entry consists of a list of parameters that 323 represents the configuration of a single carrier 324 modulation VDSL modem transmit band. 326 A default profile with an index of 'DEFVAL', will 327 always exist and its parameters will be set to vendor 328 specific values, unless otherwise specified in this 329 document." 331 INDEX { vdslLineConfProfileName, 332 vdslSCMConfProfileTxBandSide, 333 vdslSCMConfProfileTxBandNumber } 334 ::= { vdslLineSCMConfProfileTxBandTable 1 } 336 VdslLineSCMConfProfileTxBandEntry ::= 337 SEQUENCE 338 { 339 vdslSCMConfProfileTxBandSide VdslLineEntity, 340 vdslSCMConfProfileTxBandNumber INTEGER, 341 vdslSCMConfProfileTxBandCenterFrequency Unsigned32, 342 vdslSCMConfProfileTxBandSymbolRate Unsigned32, 343 vdslSCMConfProfileTxBandConstellationSize Unsigned32, 344 vdslSCMConfProfileTxBandTransmitPSDLevel Unsigned32, 345 vdslSCMConfProfileTxBandRowStatus RowStatus 346 } 348 vdslSCMConfProfileTxBandSide OBJECT-TYPE 349 SYNTAX VdslLineEntity 350 MAX-ACCESS not-accessible 351 STATUS current 352 DESCRIPTION 353 "Identifies whether this band entry describes 354 downstream or upstream transmission." 355 ::= { vdslLineSCMConfProfileTxBandEntry 1 } 357 vdslSCMConfProfileTxBandNumber OBJECT-TYPE 358 SYNTAX INTEGER 359 MAX-ACCESS not-accessible 360 STATUS current 361 DESCRIPTION 362 "The transmit band or sub-band number for this entry." 363 ::= { vdslLineSCMConfProfileTxBandEntry 2 } 365 vdslSCMConfProfileTxBandSymbolRate OBJECT-TYPE 366 SYNTAX Unsigned32 367 UNITS "kbaud" 368 MAX-ACCESS read-create 369 STATUS current 370 DESCRIPTION 371 "The requested symbol rate in kbaud." 372 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 373 ::= { vdslLineSCMConfProfileTxBandEntry 3 } 375 vdslSCMConfProfileTxBandConstellationSize OBJECT-TYPE 376 SYNTAX Unsigned32 (0..16) 377 UNITS "log2" 378 MAX-ACCESS read-create 379 STATUS current 380 DESCRIPTION 381 "Specifies the constellation size." 382 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 383 ::= { vdslLineSCMConfProfileTxBandEntry 4 } 385 vdslSCMConfProfileTxBandCenterFrequency OBJECT-TYPE 386 SYNTAX Unsigned32 387 UNITS "kHz" 388 MAX-ACCESS read-create 389 STATUS current 390 DESCRIPTION 391 "Specifies the center frequency in Khz" 392 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 393 ::= { vdslLineSCMConfProfileTxBandEntry 5 } 395 vdslSCMConfProfileTxBandTransmitPSDLevel OBJECT-TYPE 396 SYNTAX INTEGER 397 UNITS "-dBm/Hz" 398 MAX-ACCESS read-create 399 STATUS current 400 DESCRIPTION 401 "The requested transmit power spectral density for the VDSL 402 modem. The Actual value in dBm/Hz." 403 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 404 ::= { vdslLineSCMConfProfileTxBandEntry 6 } 406 vdslSCMConfProfileTxBandRowStatus OBJECT-TYPE 407 SYNTAX RowStatus 408 MAX-ACCESS read-create 409 STATUS current 410 DESCRIPTION 411 "This object is used to create a new row or modify or 412 delete an existing row in this table. 414 A profile activated by setting this object to `active'. 415 When `active' is set, the system will validate the profile. 417 Before a profile can be deleted or taken out of 418 service, (by setting this object to `destroy' or 419 `outOfService') it must be first unreferenced 420 from all associated lines." 421 ::= { vdslLineSCMConfProfileTxBandEntry 7 } 423 -- 424 -- SCM physical band status 425 -- 427 vdslSCMPhysBandTable OBJECT-TYPE 428 SYNTAX SEQUENCE OF VdslSCMPhysBandEntry 429 MAX-ACCESS not-accessible 430 STATUS current 431 DESCRIPTION 432 "This table provides one row for each SCM Vtu band." 433 ::= { vdslEXTSCMMibObjects 2 } 435 vdslSCMPhysBandEntry OBJECT-TYPE 436 SYNTAX VdslSCMPhysBandEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "An entry in the vdslSCMPhysBandTable." 442 INDEX { ifIndex, 443 vdslPhysSide, 444 vdslSCMPhysBandNumber } 445 ::= { vdslSCMPhysBandTable 1 } 447 VdslSCMPhysBandEntry ::= 448 SEQUENCE 449 { 450 vdslSCMPhysBandNumber INTEGER, 451 vdslSCMPhysBandCurrSnrMgn Integer32, 452 vdslSCMPhysBandCurrAtn Unsigned32, 453 vdslSCMPhysBandCurrPSDLevel Unsigned32, 454 vdslSCMPhysBandCurrSymbolRate Unsigned32, 455 vdslSCMPhysBandCurrConstellationSize Unsigned32, 456 vdslSCMPhysBandCurrCenterFrequency Unsigned32, 458 } 460 vdslSCMPhysBandNumber OBJECT-TYPE 461 SYNTAX INTEGER 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "The SCM transmit band number for this entry." 466 ::= { vdslSCMPhysBandEntry 1 } 468 vdslSCMPhysBandCurrSnrMgn OBJECT-TYPE 469 SYNTAX Integer32 470 UNITS "0.25 dBm" 471 MAX-ACCESS read-only 472 STATUS current 473 DESCRIPTION 474 "Noise margin as seen by this Vtu and band with respect 475 to its received signal in 0.25 dB." 476 ::= { vdslSCMPhysBandEntry 2 } 478 vdslSCMPhysBandCurrAtn OBJECT-TYPE 479 SYNTAX Unsigned32 (0..255) 480 UNITS "0.25 dBm" 481 MAX-ACCESS read-only 482 STATUS current 483 DESCRIPTION 484 "Measured difference in the total power transmitted by 485 the peer Vtu on this band and the total power received 486 by this Vtu on this band in 0.25 dB." 487 ::= { vdslSCMPhysBandEntry 3 } 489 vdslSCMPhysBandCurrSymbolRate OBJECT-TYPE 490 SYNTAX Unsigned32 491 UNITS "kbaud" 492 MAX-ACCESS read-create 493 STATUS current 494 DESCRIPTION 495 "The current value of the symbol rate in kbaud for this 496 band." 497 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 498 ::= { vdslSCMPhysBandEntry 4 } 500 vdslSCMPhysBandCurrConstellationSize OBJECT-TYPE 501 SYNTAX Unsigned32 (0..16) 502 UNITS "log2" 503 MAX-ACCESS read-create 504 STATUS current 505 DESCRIPTION 506 "The current constellation size on this band." 507 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 508 ::= { vdslSCMPhysBandEntry 5 } 510 vdslSCMPhysBandCurrCenterFrequency OBJECT-TYPE 511 SYNTAX Unsigned32 512 UNITS "kHz" 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "The current center frequency in kHz for this band." 517 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 518 ::= { vdslSCMPhysBandEntry 6 } 520 -- conformance information 522 vdslExtSCMConformance OBJECT IDENTIFIER ::= { vdslLineExtSCMMib 2 } 523 vdslExtSCMGroups OBJECT IDENTIFIER ::= { vdslExtSCMConformance 1 } 524 vdslExtSCMCompliances OBJECT IDENTIFIER ::= 525 { vdslExtSCMConformance 2 } 527 vdslLineExtSCMMibCompliance MODULE-COMPLIANCE 528 STATUS current 529 DESCRIPTION 530 "The compliance statement for SNMP entities which 531 manage VDSL interfaces." 533 MODULE -- this module 535 GROUP vdslSCMGroup 536 DESCRIPTION 537 "This group is an optional extension for VDSL lines which 538 utilize single carrier modulation (SCM)." 540 ::= { vdslCompliances 1 } 542 -- units of conformance 544 vdslSCMGroup OBJECT-GROUP 545 OBJECTS 546 { 547 vdslSCMPhysBandCurrSnrMgn, 548 vdslSCMPhysBandCurrAtn, 549 vdslSCMPhysBandCurrPSDLevel, 550 vdslSCMPhysBandCurrSymbolRate, 551 vdslSCMPhysBandCurrConstellationSize, 552 vdslSCMPhysBandCurrCenterFrequency, 553 vdslSCMConfProfileTxBandTransmitPSDLevel, 554 vdslSCMConfProfileTxBandSymbolRate, 555 vdslSCMConfProfileTxBandConstellationSize, 556 vdslSCMConfProfileTxBandCenterFrequency, 557 vdslSCMConfProfileTxBandRowStatus 558 } 559 STATUS current 560 DESCRIPTION 561 "A collection of objects providing configuration 562 information for a VDSL line based upon single carrier 563 modulation modem." 564 ::= { vdslGroups 1 } 566 END 568 5. Intellectual Property Notice 570 The IETF takes no position regarding the validity or scope of any 571 intellectual property or other rights that might be claimed to 572 pertain to the implementation or use of the technology described in 573 this document or the extent to which any license under such rights 574 might or might not be available; neither does it represent that it 575 has made any effort to identify any such rights. Information on the 576 IETF's procedures with respect to rights in standards-track and 577 standards-related documentation can be found in BCP-11. Copies of 578 claims of rights made available for publication and any assurances 579 of licenses to be made available, or the result of an attempt made 580 to obtain a general license or permission for the use of such 581 proprietary rights by implementors or users of this specification 582 can be obtained from the IETF Secretariat. 584 The IETF invites any interested party to bring to its attention any 585 copyrights, patents or patent applications, or other proprietary 586 rights which may cover technology that may be required to practice 587 this standard. Please address the information to the IETF Executive 588 Director. 590 6. Normative References 592 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 593 (TM); Access transmission systems on metallic access 594 cables; Very high speed Digital Subscriber Line (VDSL); 595 Part 1: Functional requirements", October 1999. 597 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 598 (TM); Access transmission systems on metallic access 599 cables; Very high speed Digital Subscriber Line (VDSL); 600 Part 1: Transceiver specification", February 2001. 602 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 603 foundation", November 2001. 605 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 606 Subscriber Line (DSL) Transceivers", July 1999. 608 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 609 Performance History Based on 15 Minute Intervals", RFC 610 2493, January 1999. 612 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 613 Rose, M. and S. Waldbusser, "Structure of Management 614 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 615 1999. 617 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 618 Rose, M. and S. Waldbusser, "Textual Conventions for 619 SMIv2", STD 58, RFC 2579, April 1999. 621 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 622 Rose, M. and S. Waldbusser, "Conformance Statements for 623 SMIv2", STD 58, RFC 2580, April 1999. 625 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 626 MIB", RFC 2863, June 2000. 628 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 629 Simple Network Management Protocol (SNMP)", STD 62, RFC 630 3418, December 2002. 632 [RFCXXXX] Ray, B. and R. Abbi, "Definitions of Managed Objects for 633 Very High Speed Digital Subscriber Lines (VDSL)", RFC XXXX, 634 YYYY 2003. 636 [RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions 637 for MIB Modules Using Performance History Based on 638 15 Minute Intervals", RFC XXXX, YYYY 2003. 640 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 641 Subscriber Line (VDSL) Metallic Interface, Part 1: 642 Functional Requirements and Common Specification", 643 February 2001. 645 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 646 Technical Specification for a Single-Carrier Modulation 647 (SCM) Transceiver", November 2001. 649 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 650 Technical Specification for a Multi-Carrier Modulation 651 (MCM) Transceiver", November 2000. 653 7. Informative References 655 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 656 Access Control Model (VACM) for the Simple Network 657 Management Protocol (SNMP)", RFC 2575, April 1999. 659 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 660 "Introduction and Applicability Statements for Internet- 661 Standard Management Framework", RFC 3410, December 2002. 663 8. Security Considerations 665 There are a number of management objects defined in this MIB that 666 have a MAX-ACCESS clause of read-write and/or read-create. Such 667 objects may be considered sensitive or vulnerable in some network 668 environments. The support for SET operations in a non-secure 669 environment without proper protection can have a negative effect on 670 network operations. 672 VDSL layer connectivity from the Vtur will permit the subscriber 673 to manipulate both the VDSL link directly and the VDSL embedded 674 operations channel (EOC) for their own loop. For example, unchecked 675 or unfiltered fluctuations initiated by the subscriber could 676 generate sufficient notifications to potentially overwhelm either 677 the management interface to the network or the element manager. 679 For this reason, there are a number of managed objects in this MIB 680 that may contain sensitive information. 682 It is thus important to control even GET access to these objects and 683 possibly to even encrypt the values of these objects when sending 684 them over the network via SNMP. Not all versions of SNMP provide 685 features for such a secure environment. 687 Further, notifications generated by agents implementing this MIB 688 will contain the above threshold information. 690 SNMP versions prior to SNMPv3 did not include adequate security. 691 Even if the network itself is secure (for example by using IPSec), 692 even then, there is no control as to who on the secure network is 693 allowed to access and GET/SET (read/change/create/delete) objects 694 which utilize the textual conventions defined in this MIB module. 696 It is RECOMMENDED that implementers consider the security features 697 as provided by the SNMPv3 framework (see [RFC3410], section 8), 698 including full support for the SNMPv3 cryptographic mechanisms (for 699 authentication and privacy). 701 Further, deployment of SNMP versions prior to SNMPv3 is NOT 702 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 703 enable cryptographic security. It is then a customer/operator 704 responsibility to ensure that the SNMP entity giving access to an 705 instance of a MIB module which utilizes the textual conventions 706 defined in this MIB module is properly configured to give access to 707 the objects only to those principals (users) that have legitimate 708 rights to indeed GET or SET (change/create/delete) them. 710 9. Acknowledgments 712 This document contains many definitions taken from 713 draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text 714 found within should be full attributed to the authors of that 715 document. 717 10. Authors' Addresses 719 Menachem Dodge 720 Infineon Technologies Savan Ltd. 721 6 Hagavish St. 722 Poleg Industrial Area, 723 Netanya 42504, 724 Israel. 726 Phone: +972 9 892 4116 727 Fax: +972 9 865 8756 728 Email: menachem.dodge@infineon.com 730 Bob Ray 731 PESA Switching Systems, Inc. 732 330-A Wynn Drive 733 Huntsville, AL 35805 734 USA 736 Phone: +1 256 726 9200 ext. 142 737 Fax: +1 256 726 9271 738 EMail: rray@pesa.com 740 11. Full Copyright Statement 742 Copyright (C) The Internet Society (2003). All Rights Reserved. 743 This document and translations of it may be copied and furnished to 744 others, and derivative works that comment on or otherwise explain it 745 or assist in its implementation may be prepared, copied, published 746 and distributed, in whole or in part, without restriction of any 747 kind, provided that the above copyright notice and this paragraph 748 are included on all such copies and derivative works. However, this 749 document itself may not be modified in any way, such as by removing 750 the copyright notice or references to the Internet Society or other 751 Internet organizations, except as needed for the purpose of 752 developing Internet standards in which case the procedures for 753 copyrights defined in the Internet Standards process must be 754 followed, or as required to translate it into languages other than 755 English. 757 The limited permissions granted above are perpetual and will not be 758 revoked by the Internet Society or its successors or assigns. 760 This document and the information contained herein is provided on an 761 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 762 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 763 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 764 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 765 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.