idnits 2.17.1 draft-ietf-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 39 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 144: '...ts in this group MAY be implemented fo...' RFC 2119 keyword, line 166: '...lSCMGroup tables MAY be implemented fo...' RFC 2119 keyword, line 172: '... SHOULD be stored persistently. Fol...' RFC 2119 keyword, line 193: '... It SHOULD also be noted that interf...' RFC 2119 keyword, line 194: '... 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 (February 2004) is 7368 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: 'DSLF WT-096' is mentioned on line 89, but not defined == Unused Reference: 'DSLFTR057' is defined on line 655, but no explicit reference was found in the text == Unused Reference: 'DSLFWT096' is defined on line 658, but no explicit reference was found in the text == Unused Reference: 'ETSI2701' is defined on line 661, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 666, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 671, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 674, but no explicit reference was found in the text == Unused Reference: 'RFC2493' is defined on line 677, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 697, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 709, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 714, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 718, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFTR057' -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFWT096' -- 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 (~~), 14 warnings (==), 13 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-scm-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 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 (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 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 .................................... 5 56 4. Definitions ................................................... 5 57 5. Intellectual Property ......................................... 13 58 6. Normative References .......................................... 14 59 7. Informative References ........................................ 15 60 8. Security Considerations ....................................... 15 61 9. Acknowledgements .............................................. 16 62 10. Authors' Addresses ............................................ 16 63 11. Full Copyright Statement ...................................... 17 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 87 protocol-dependent (and line-code dependent) management framework 88 for VDSL lines specified by DSLF has been taken into consideration 89 [DSLF WT-096]. 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 SCM VDSL Line Extension MIB contains the following MIB group: 135 o vdslSCMGroup : 137 This group supports MIB objects for defining configuration profiles 138 and for montioring individual bands of Single Carrier Modulation 139 (SCM) VDSL modems. It contains the following tables: 141 - vdslLineSCMConfProfileTxBandTable 142 - vdslSCMPhysBandTable 144 Either none, one or both objects in this group MAY be implemented for 145 SCM VDSL lines. 147 Figure 1, below, displays the relationship of the tables in the 148 vdslSCMGroup to the vdslGroup and to the ifEntry: 150 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 152 vdslLineTableEntry (vdslLineCoding=SCM) 153 ----> vdslPhysTableEntry 1:(0..2) 154 ----> vdslSCMPhysBandTable 1:(0..6) 156 vdslLineConfProfileEntry(vdslLineConfProfileName) 157 ----> vdslLineSCMConfProfileBandTable 1:(0..6) 159 Figure 1: Table Relationships 161 When the vdslLineCoding is set to SCM, the vdslLineConfProfileName 162 which is the index of the vdslLineConfProfileEntry is also used as 163 the index to the vdslLineSCMConfProfileBandTable of the 164 vdslSCMGroup. The existence of an entry in any of the tables of 165 the vdslSCMGroup is optional. Either none, one or both of the 166 vdslSCMGroup tables MAY be implemented for a particular VDSL line 167 entity using SCM Line Coding. 169 2.4 Persistence 171 All read-write and read-create objects defined in this MIB module 172 SHOULD be stored persistently. Following is an exhaustive list of 173 these persistent objects: 175 vdslSCMConfProfileBandId 176 vdslSCMConfProfileBandUsage 177 vdslSCMConfProfileBandCenterFrequency 178 vdslSCMConfProfileBandSymbolRate 179 vdslSCMConfProfileBandConstellationSize 180 vdslSCMConfProfileBandTransmitPSDLevel 181 vdslSCMConfProfileBandRowStatus 182 vdslSCMPhysBandId 183 vdslSCMPhysBandUsage 184 vdslSCMPhysBandCurrPSDLevel 185 vdslSCMPhysBandCurrSymbolRate 186 vdslSCMPhysBandCurrConstellationSize 187 vdslSCMPhysBandCurrCenterFrequency 188 vdslSCMPhysBandPerformanceBandId 189 vdslSCMPhysBandPerformanceBandUsage 190 vdslSCMPhysBandPerformanceBandSnrMgn 191 vdslSCMPhysBandPerformanceBandAtn 193 It SHOULD also be noted that interface indices in this MIB are 194 maintained persistently. VACM data relating to these SHOULD be 195 stored persistently as well [RFC2575]. 197 3. Conformance and Compliance 199 For SCM VDSL lines, the following group is optional: 200 - vdslSCMGroup 202 4. Definitions 204 VDSL-LINE-EXT-SCM MIB DEFINITIONS ::= BEGIN 206 IMPORTS 208 MODULE-IDENTITY, 209 OBJECT-TYPE, 210 Counter64, 211 Gauge32, 212 Integer32, 213 Unsigned32, 214 NOTIFICATION-TYPE, 215 transmission FROM SNMPv2-SMI 216 TEXTUAL-CONVENTION, 217 RowStatus, 218 TruthValue FROM SNMPv2-TC 219 HCPerfValidIntervals, 220 HCPerfInvalidIntervals, 221 HCPerfTimeElapsed, 222 HCPerfIntervalThreshold, 223 HCPerfCurrentCount, 224 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 225 MODULE-COMPLIANCE, 226 OBJECT-GROUP, 227 NOTIFICATION-GROUP FROM SNMPv2-CONF 228 ifIndex FROM IF-MIB 229 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 230 vdslLineConfProfileName FROM VDSL-LINE-MIB; 232 vdslExtSCMMIB MODULE-IDENTITY 233 LAST-UPDATED "200402120000Z" --February 12, 2004 234 ORGANIZATION "ADSLMIB Working Group" 235 CONTACT-INFO "WG-email: adslmib@ietf.org 236 Info: https://www1.ietf.org/mailman/listinfo/adslmib 238 Chair: Mike Sneed 239 Sand Channel Systems 240 Postal: P.O. Box 37324 241 Raleigh NC 27627-732 242 Email: sneedmike@hotmail.com 243 Phone: +1 206 600 7022 244 co-editor: Menachem Dodge 245 Infineon Technologies Savan Ltd. 246 6 Hagavish St. 247 Postal: Poleg Industrial Area, 248 Netanya 42504, 249 Israel. 250 Email: menachem.dodge@infineon.com 251 Phone: +972 9 892 4116 253 Co-editor: Bob Ray 254 PESA Switching Systems, Inc. 255 Postal: 330-A Wynn Drive 256 Huntsville, AL 35805 257 USA 258 Email: rray@pesa.com 259 Phone: +1 256 726 9200 ext. 142 260 " 261 DESCRIPTION 262 "The VDSL Line core MIB found in RFC XXXX defines objects for 263 the management of a pair of VDSL transceivers at each end of 264 the VDSL line. The core MIB configures and monitors the line 265 code independent parameters (TC layer) of the VDSL line. 266 This MIB module is an optional extension of the core MIB and 267 defines objects for configuration and monitoring of the line 268 code specific (LCS) elements (PMD layer) for VDSL lines using 269 SCM coding. The objects in this extension MIB MUST NOT be used 270 for VDSL lines using MCM line coding. 272 Naming Conventions: 273 Vtuc -- (VTUC) transceiver at near (Central) end of line 274 Vtur -- (VTUR) transceiver at Remote end of line 275 Vtu -- One of either Vtuc or Vtur 276 Curr -- Current 277 Prev -- Previous 278 Atn -- Attenuation 279 ES -- Errored Second. 280 SES -- Severely Errored Second 281 UAS -- Unavailable Second 282 LCS -- Line Code Specific 283 Lof -- Loss of Frame 284 Lol -- Loss of Link 285 Los -- Loss of Signal 286 Lpr -- Loss of Power 287 xxxs -- Interval of Seconds in which xxx occurs 288 (e.g., xxx=Lof, Los, Lpr) 289 Max -- Maximum 290 Mgn -- Margin 291 Min -- Minimum 292 Psd -- Power Spectral Density 293 Snr -- Signal to Noise Ratio 294 Tx -- Transmit 295 Blks -- Blocks 297 Copyright (C) The Internet Society (2004). This version 298 of this MIB module is part of RFC XXXX: see the RFC 299 itself for full legal notices." 300 -- RFC Ed.: replace XXXX with assigned number & remove this note 301 REVISION "200402120000Z" --February 12, 2004 302 DESCRIPTION "Initial version, published as RFC XXXX." 303 -- RFC Ed.: replace XXXX with assigned number & remove this note 304 ::= { vdslMIB XX } -- To be assigned by IANA 305 -- RFC Ed.: we suggest to put it under { vdslMIB 2 } because 306 -- vdslMIB 1 is the VDSL core MIB, vdslMIB 2 is this SCM 307 -- extension MIB, while vdslMIB 3 is the MCM extension MIB. 309 vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } 310 vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= 311 { vdslLineExtSCMMib 1 } 313 -- 314 -- Single carrier modulation (SCM) configuration profile tables 315 -- 317 vdslLineSCMConfProfileBandTable OBJECT-TYPE 318 SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry 319 MAX-ACCESS not-accessible 320 STATUS current 321 DESCRIPTION 322 "This table contains transmit band descriptor configuration 323 information for a VDSL line. Each entry in this table 324 reflects the configuration for one of possibly many bands 325 of a single carrier modulation (SCM) VDSL line. 326 These entries are defined by a manager and can be used to 327 configure the VDSL line." 328 ::= { vdslLineExtSCMMibObjects 1 } 330 vdslLineSCMConfProfileBandEntry OBJECT-TYPE 331 SYNTAX VdslLineSCMConfProfileBandEntry 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "Each entry consists of a list of parameters that 336 represents the configuration of a single carrier 337 modulation VDSL modem transmit band. 339 A default profile with an index of 'DEFVAL', will 340 always exist and its parameters will be set to vendor 341 specific values, unless otherwise specified in this 342 document." 344 INDEX { vdslLineConfProfileName, 345 vdslLineSCMConfProfileBandId } 346 ::= { vdslLineSCMConfProfileBandTable 1 } 348 VdslLineSCMConfProfileBandEntry ::= 349 SEQUENCE 350 { 351 vdslLineSCMConfProfileBandId INTEGER, 352 vdslLineSCMConfProfileBandUsage INTEGER, 353 vdslLineSCMConfProfileBandCenterFrequency Unsigned32, 354 vdslLineSCMConfProfileBandSymbolRate Unsigned32, 355 vdslLineSCMConfProfileBandConstellationSize Unsigned32, 356 vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, 357 vdslLineSCMConfProfileBandRowStatus RowStatus 358 } 360 vdslLineSCMConfProfileBandId OBJECT-TYPE 361 SYNTAX INTEGER 362 MAX-ACCESS not-accessible 363 STATUS current 364 DESCRIPTION 365 "The BandId for this entry, which specifies which band 366 is being referred to. Specified as an INTEGER, the five 367 possible values are: 368 optionalBand(1), 369 1D(2), 370 1U(3), 371 2D(4), 372 2U(5)" 373 ::= { vdslLineSCMConfProfileBandEntry 1 } 375 vdslLineSCMConfProfileBandUsage OBJECT-TYPE 376 SYNTAX INTEGER 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "Indicates whether this band is in use. 381 Specified as an INTEGER, the two 382 possible values are: 383 Unused(1), 384 InUse(2)" 386 ::= { vdslLineSCMConfProfileBandEntry 2 } 388 vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE 389 SYNTAX Unsigned32 390 UNITS "Hz" 391 MAX-ACCESS read-create 392 STATUS current 393 DESCRIPTION 394 "Specifies the center frequency in Hz" 395 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 396 ::= { vdslLineSCMConfProfileBandEntry 3 } 398 vdslLineSCMConfProfileBandSymbolRate OBJECT-TYPE 399 SYNTAX Unsigned32 400 UNITS "baud" 401 MAX-ACCESS read-create 402 STATUS current 403 DESCRIPTION 404 "The requested symbol rate in baud." 405 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 406 ::= { vdslLineSCMConfProfileBandEntry 4 } 408 vdslLineSCMConfProfileBandConstellationSize OBJECT-TYPE 409 SYNTAX Unsigned32 (0..16) 410 UNITS "log2" 411 MAX-ACCESS read-create 412 STATUS current 413 DESCRIPTION 414 "Specifies the constellation size." 415 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 416 ::= { vdslLineSCMConfProfileBandEntry 5 } 418 vdslLineSCMConfProfileBandTransmitPSDLevel OBJECT-TYPE 419 SYNTAX Unsigned32 420 UNITS "-0.25 dBm/Hz" 421 MAX-ACCESS read-create 422 STATUS current 423 DESCRIPTION 424 "The requested transmit power spectral density for the VDSL 425 modem. The Actual value in -0.25 dBm/Hz." 426 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 427 ::= { vdslLineSCMConfProfileBandEntry 6 } 429 vdslLineSCMConfProfileBandRowStatus OBJECT-TYPE 430 SYNTAX RowStatus 431 MAX-ACCESS read-create 432 STATUS current 433 DESCRIPTION 434 "This object is used to create a new row or modify or 435 delete an existing row in this table. 437 A profile activated by setting this object to `active'. 438 When `active' is set, the system will validate the profile. 440 Before a profile can be deleted or taken out of 441 service, (by setting this object to `destroy' or 442 `outOfService') it must be first unreferenced 443 from all associated lines." 444 ::= { vdslLineSCMConfProfileBandEntry 7 } 446 -- 447 -- SCM physical band 448 -- 450 vdslLineSCMPhysBandTable OBJECT-TYPE 451 SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry 452 MAX-ACCESS not-accessible 453 STATUS current 454 DESCRIPTION 455 "This table provides one row for each SCM Vtu band. This 456 table is read only as it reflects the current physical 457 parameters of each band." 458 ::= { vdslLineExtSCMMibObjects 2 } 460 vdslLineSCMPhysBandEntry OBJECT-TYPE 461 SYNTAX VdslLineSCMPhysBandEntry 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "An entry in the vdslLineSCMPhysBandTable." 467 INDEX { ifIndex, 468 vdslLineSCMPhysBandId } 469 ::= { vdslLineSCMPhysBandTable 1 } 471 VdslLineSCMPhysBandEntry ::= 472 SEQUENCE 473 { 474 vdslLineSCMPhysBandId INTEGER, 475 vdslLineSCMPhysBandUsage INTEGER, 476 vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, 477 vdslLineSCMPhysBandCurrSymbolRate Unsigned32, 478 vdslLineSCMPhysBandCurrConstellationSize Unsigned32, 479 vdslLineSCMPhysBandCurrPSDLevel Unsigned32, 480 vdslLineSCMPhysBandCurrSnrMgn Integer32, 481 vdslLineSCMPhysBandCurrAtn Unsigned32 483 } 485 vdslLineSCMPhysBandId OBJECT-TYPE 486 SYNTAX INTEGER 487 MAX-ACCESS not-accessible 488 STATUS current 489 DESCRIPTION 490 "The BandId for this entry, which specifies which band 491 is being referred to. Specified as an INTEGER, the five 492 possible values are: 493 optionalBand(1), 494 1D(2), 495 1U(3), 496 2D(4), 497 2U(5)" 498 ::= { vdslLineSCMPhysBandEntry 1 } 500 vdslLineSCMPhysBandUsage OBJECT-TYPE 501 SYNTAX INTEGER 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION 505 "Indicates whether this band is in use. 506 Specified as an INTEGER, the two 507 possible values are: 508 Unused(1), 509 InUse(2)" 511 ::= { vdslLineSCMPhysBandEntry 2 } 513 vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE 514 SYNTAX Unsigned32 515 UNITS "Hz" 516 MAX-ACCESS read-only 517 STATUS current 518 DESCRIPTION 519 "The current center frequency in Hz for this band." 520 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 521 ::= { vdslLineSCMPhysBandEntry 3 } 523 vdslLineSCMPhysBandCurrSymbolRate OBJECT-TYPE 524 SYNTAX Unsigned32 525 UNITS "baud" 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "The current value of the symbol rate in baud for this 530 band." 531 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 532 ::= { vdslLineSCMPhysBandEntry 4 } 534 vdslLineSCMPhysBandCurrConstellationSize OBJECT-TYPE 535 SYNTAX Unsigned32 (0..16) 536 UNITS "log2" 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "The current constellation size on this band." 541 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 542 ::= { vdslLineSCMPhysBandEntry 5 } 544 vdslLineSCMPhysBandCurrPSDLevel OBJECT-TYPE 545 SYNTAX Unsigned32 546 UNITS "- 0.25 dBm/Hz" 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "The transmit power spectral density for the 551 VDSL modem." 552 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 553 ::= { vdslLineSCMPhysBandEntry 6 } 555 vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE 556 SYNTAX Integer32 557 UNITS "0.25 dBm" 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "Noise margin as seen by this Vtu and band with respect 562 to its received signal in 0.25 dB." 563 ::= { vdslLineSCMPhysBandEntry 7 } 565 vdslLineSCMPhysBandCurrAtn OBJECT-TYPE 566 SYNTAX Unsigned32 (0..255) 567 UNITS "0.25 dBm" 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "Measured difference in the total power transmitted by 572 the peer Vtu on this band and the total power received 573 by this Vtu on this band in 0.25 dB." 574 ::= { vdslLineSCMPhysBandEntry 8 } 576 -- conformance information 578 vdslLineExtSCMConformance OBJECT IDENTIFIER ::= 579 { vdslLineExtSCMMib 2 } 580 vdslLineExtSCMGroups OBJECT IDENTIFIER ::= 581 { vdslLineExtSCMConformance 1 } 582 vdslLineExtSCMCompliances OBJECT IDENTIFIER ::= 583 { vdslLineExtSCMConformance 2 } 585 vdslLineExtSCMMibCompliance MODULE-COMPLIANCE 586 STATUS current 587 DESCRIPTION 588 "The compliance statement for SNMP entities which 589 manage VDSL interfaces." 591 MODULE -- this module 593 MANDATORY-GROUPS 594 { 595 vdslLineExtSCMGroup 596 } 598 ::= { vdslLineExtSCMCompliances 1 } 600 -- units of conformance 602 vdslLineExtSCMGroup OBJECT-GROUP 603 OBJECTS 604 { 605 vdslLineSCMConfProfileBandId, 606 vdslLineSCMConfProfileBandUsage, 607 vdslLineSCMConfProfileBandTransmitPSDLevel, 608 vdslLineSCMConfProfileBandSymbolRate, 609 vdslLineSCMConfProfileBandConstellationSize, 610 vdslLineSCMConfProfileBandCenterFrequency, 611 vdslLineSCMConfProfileBandRowStatus, 612 vdslLineSCMPhysBandId, 613 vdslLineSCMPhysBandUsage, 614 vdslLineSCMPhysBandCurrPSDLevel, 615 vdslLineSCMPhysBandCurrSymbolRate, 616 vdslLineSCMPhysBandCurrConstellationSize, 617 vdslLineSCMPhysBandCurrCenterFrequency, 618 vdslLineSCMPhysBandCurrSnrMgn, 619 vdslLineSCMPhysBandCurrAtn 621 } 622 STATUS current 623 DESCRIPTION 624 "A collection of objects providing configuration 625 information for a VDSL line based upon single carrier 626 modulation modem." 627 ::= { vdslLineExtSCMGroups 1 } 629 END 631 5. Intellectual Property Notice 633 The IETF takes no position regarding the validity or scope of any 634 intellectual property or other rights that might be claimed to 635 pertain to the implementation or use of the technology described in 636 this document or the extent to which any license under such rights 637 might or might not be available; neither does it represent that it 638 has made any effort to identify any such rights. Information on the 639 IETF's procedures with respect to rights in standards-track and 640 standards-related documentation can be found in BCP-11. Copies of 641 claims of rights made available for publication and any assurances 642 of licenses to be made available, or the result of an attempt made 643 to obtain a general license or permission for the use of such 644 proprietary rights by implementors or users of this specification 645 can be obtained from the IETF Secretariat. 647 The IETF invites any interested party to bring to its attention any 648 copyrights, patents or patent applications, or other proprietary 649 rights which may cover technology that may be required to practice 650 this standard. Please address the information to the IETF Executive 651 Director. 653 6. Normative References 655 [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", 656 February 2003. 658 [DSLFWT096] DSL Forum WT-096, "SCM Specific Managed Objects In 659 VDSL Network Elements". 661 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 662 (TM); Access transmission systems on metallic access 663 cables; Very high speed Digital Subscriber Line (VDSL); 664 Part 1: Functional requirements", October 1999. 666 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 667 (TM); Access transmission systems on metallic access 668 cables; Very high speed Digital Subscriber Line (VDSL); 669 Part 1: Transceiver specification", February 2001. 671 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 672 foundation", November 2001. 674 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 675 Subscriber Line (DSL) Transceivers", July 1999. 677 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 678 Performance History Based on 15 Minute Intervals", RFC 679 2493, January 1999. 681 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 682 Rose, M. and S. Waldbusser, "Structure of Management 683 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 684 1999. 686 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 687 Rose, M. and S. Waldbusser, "Textual Conventions for 688 SMIv2", STD 58, RFC 2579, April 1999. 690 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 691 Rose, M. and S. Waldbusser, "Conformance Statements for 692 SMIv2", STD 58, RFC 2580, April 1999. 694 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 695 MIB", RFC 2863, June 2000. 697 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 698 Simple Network Management Protocol (SNMP)", STD 62, RFC 699 3418, December 2002. 701 [RFCXXXX] Ray, B. and R. Abbi, "Definitions of Managed Objects for 702 Very High Speed Digital Subscriber Lines (VDSL)", 703 RFC XXXX, YYYY 2003. 705 [RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions 706 for MIB Modules Using Performance History Based on 707 15 Minute Intervals", RFC XXXX, YYYY 2003. 709 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 710 Subscriber Line (VDSL) Metallic Interface, Part 1: 711 Functional Requirements and Common Specification", 712 February 2001. 714 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 715 Technical Specification for a Single-Carrier Modulation 716 (SCM) Transceiver", November 2001. 718 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 719 Technical Specification for a Multi-Carrier Modulation 720 (MCM) Transceiver", November 2000. 722 7. Informative References 724 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 725 Access Control Model (VACM) for the Simple Network 726 Management Protocol (SNMP)", RFC 2575, April 1999. 728 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 729 "Introduction and Applicability Statements for Internet- 730 Standard Management Framework", RFC 3410, December 2002. 732 8. Security Considerations 734 There are a number of management objects defined in this MIB that 735 have a MAX-ACCESS clause of read-write and/or read-create. Such 736 objects may be considered sensitive or vulnerable in some network 737 environments. The support for SET operations in a non-secure 738 environment without proper protection can have a negative effect on 739 network operations. 741 VDSL layer connectivity from the Vtur will permit the subscriber 742 to manipulate both the VDSL link directly and the VDSL embedded 743 operations channel (EOC) for their own loop. For example, unchecked 744 or unfiltered fluctuations initiated by the subscriber could 745 generate sufficient notifications to potentially overwhelm either 746 the management interface to the network or the element manager. 748 For this reason, there are a number of managed objects in this MIB 749 that may contain sensitive information. 751 It is thus important to control even GET access to these objects and 752 possibly to even encrypt the values of these objects when sending 753 them over the network via SNMP. Not all versions of SNMP provide 754 features for such a secure environment. 756 Further, notifications generated by agents implementing this MIB 757 will contain the above threshold information. 759 SNMP versions prior to SNMPv3 did not include adequate security. 760 Even if the network itself is secure (for example by using IPSec), 761 even then, there is no control as to who on the secure network is 762 allowed to access and GET/SET (read/change/create/delete) objects 763 which utilize the textual conventions defined in this MIB module. 765 It is RECOMMENDED that implementers consider the security features 766 as provided by the SNMPv3 framework (see [RFC3410], section 8), 767 including full support for the SNMPv3 cryptographic mechanisms (for 768 authentication and privacy). 770 Further, deployment of SNMP versions prior to SNMPv3 is NOT 771 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 772 enable cryptographic security. It is then a customer/operator 773 responsibility to ensure that the SNMP entity giving access to an 774 instance of a MIB module which utilizes the textual conventions 775 defined in this MIB module is properly configured to give access to 776 the objects only to those principals (users) that have legitimate 777 rights to indeed GET or SET (change/create/delete) them. 779 9. Acknowledgments 781 This document contains many definitions taken from 782 draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text 783 found within should be full attributed to the authors of that 784 document. 786 10. Authors' Addresses 788 Menachem Dodge 789 Infineon Technologies Savan Ltd. 790 6 Hagavish St. 791 Poleg Industrial Area, 792 Netanya 42504, 793 Israel. 795 Phone: +972 9 892 4116 796 Fax: +972 9 865 8756 797 Email: menachem.dodge@infineon.com 799 Bob Ray 800 PESA Switching Systems, Inc. 801 330-A Wynn Drive 802 Huntsville, AL 35805 803 USA 805 Phone: +1 256 726 9200 ext. 142 806 Fax: +1 256 726 9271 807 EMail: rray@pesa.com 809 11. Full Copyright Statement 811 Copyright (C) The Internet Society (2004). All Rights Reserved. 812 This document and translations of it may be copied and furnished to 813 others, and derivative works that comment on or otherwise explain it 814 or assist in its implementation may be prepared, copied, published 815 and distributed, in whole or in part, without restriction of any 816 kind, provided that the above copyright notice and this paragraph 817 are included on all such copies and derivative works. However, this 818 document itself may not be modified in any way, such as by removing 819 the copyright notice or references to the Internet Society or other 820 Internet organizations, except as needed for the purpose of 821 developing Internet standards in which case the procedures for 822 copyrights defined in the Internet Standards process must be 823 followed, or as required to translate it into languages other than 824 English. 826 The limited permissions granted above are perpetual and will not be 827 revoked by the Internet Society or its successors or assigns. 828 This document and the information contained herein is provided on an 829 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 830 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 831 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 832 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 833 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.