idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-scm-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 42. -- Found old boilerplate from RFC 3978, Section 5.5 on line 810. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 821. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 828. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 834. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 802), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 35. ** The document claims conformance with section 10 of RFC 2026, but uses some RFC 3978/3979 boilerplate. As RFC 3978/3979 replaces section 10 of RFC 2026, you should not claim conformance with it if you have changed to using RFC 3978/3979 boilerplate. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 11) being 60 lines 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 14 instances of lines with control characters in the document. ** The abstract seems to contain references ([RFC3728]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Unrecognized Status in 'Category: Internet Draft', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 2004) is 7286 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) == Unused Reference: 'RFC3593' is defined on line 712, but no explicit reference was found in the text == Unused Reference: 'RFC2856' is defined on line 732, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 739, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 744, 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' Summary: 12 errors (**), 0 flaws (~~), 8 warnings (==), 16 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 B. Ray 4 PESA Switching Systems 5 May 2004 7 Definitions of Managed Object Extensions 8 for Very High Speed Digital Subscriber Lines (VDSL) Using 9 Single Carrier Modulation (SCM) Line Coding 10 draft-ietf-adslmib-vdsl-ext-scm-04.txt 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet-Drafts as 25 reference material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at: 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at: 31 http://www.ietf.org/shadow.html. 33 Copyright Notice 35 Copyright (C) The Internet Society (2004). All Rights Reserved. 37 IPR Disclosure Acknowledgement 39 By submitting this Internet-Draft, I certify that any applicable 40 patent or other IPR claims of which I am aware have been disclosed, 41 and any of which I become aware will be disclosed, in accordance with 42 RFC 3668. 44 Abstract 46 This document defines a portion of the Management Information Base 47 (MIB) module for use with network management protocols in the 48 Internet community. In particular, it describes objects used for 49 managing the Line Code Specific parameters of Very High Speed 50 Digital Subscriber Line (VDSL) interfaces using Single Carrier 51 Modulation (SCM) Line Coding. It is an optional extension to the 52 VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code 53 independent objects. 55 Table of Contents 57 1. The Internet-Standard Management Framework .................... 2 58 2. Overview ...................................................... 2 59 2.1 Relationship of this MIB Module to other MIB Modules .......... 3 60 2.2 Conventions used in the MIB Module ............................ 3 61 2.3 Structure ..................................................... 3 62 2.4 Persistence ................................................... 4 63 3. Conformance and Compliance .................................... 4 64 4. Definitions ................................................... 4 65 5. Acknowledgements .............................................. 13 66 6. Security Considerations ....................................... 13 67 7. References .................................................... 14 68 7.1 Normative References .......................................... 14 69 7.2 Informative References ........................................ 15 70 Authors' Addresses ............................................ 15 71 Full Copyright Statement ...................................... 16 73 1. The Internet-Standard Management Framework 75 For a detailed overview of the documents that describe the current 76 Internet-Standard Management Framework, please refer to section 7 of 77 RFC 3410 [RFC3410]. 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. MIB objects are generally 81 accessed through the Simple Network Management Protocol (SNMP). 82 Objects in the MIB are defined using the mechanisms defined in the 83 Structure of Management Information (SMI). This memo specifies a 84 MIB module that is compliant to the SMIv2, which is described in STD 85 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 86 2580 [RFC2580]. 88 2. Overview 90 This document describes an SNMP MIB module for managing the Line 91 Code Dependent, Physical Medium Dependent (PMD) Layer of SCM VDSL 92 Lines. These definitions are based upon the specifications for VDSL 93 as defined in T1E1, European Telecommunications Standards Institute 94 (ETSI), and International Telecommunication Union (ITU) documentation 95 [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. 96 Additionally the protocol-dependent (and line-code dependent) 97 management framework for VDSL lines specified by the Digital 98 Subscriber Line Forum (DSLF) has been taken into consideration 99 [DSLFTR057] and [DSLFWT096]. 101 The MIB module is located in the MIB tree under the vdslMIB, which 102 in turn is found under MIB 2 transmission. The reader is referred to 103 RFC 3728 [RFC3728] for further discussion of this subject. 105 The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this 106 document are to be interpreted as described in [RFC2119]. 108 2.1 Relationship of this MIB Module to other MIB Modules 110 The relationship of the VDSL Line MIB module to other MIB modules 111 and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863], 112 is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section 113 outlines the relationship of this VDSL Line Extension MIB to the 114 VDSL-LINE-MIB, RFC 3728 [RFC3728]. 116 2.2 Conventions used in the MIB Module 118 2.2.1 Naming Conventions 120 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 121 B. Vtur -- (VTUR) transceiver at Remote end of line 122 C. Vtu -- One of either Vtuc or Vtur 123 D. Curr -- Current 124 F. Atn -- Attenuation 125 J. LCS -- Line Code Specific 126 K. Max -- Maximum 127 Q. Mgn -- Margin 128 S. PSD -- Power Spectral Density 129 T. Rx -- Receive 130 T. Snr -- Signal to Noise Ratio 131 U. Tx -- Transmit 133 2.3 Structure 135 The SCM VDSL Line Extension MIB contains the following MIB group: 137 o vdslSCMGroup : 139 This group supports MIB objects for defining configuration profiles 140 and for montioring individual bands of Single Carrier Modulation 141 (SCM) VDSL modems. It contains the following tables: 143 - vdslLineSCMConfProfileTxBandTable 144 - vdslSCMPhysBandTable 146 If the SCM VDSL Line Extension MIB is implemented then all of the 147 objects in this group MUST be implemented. 149 Figure 1, below, displays the relationship of the tables in the 150 vdslSCMGroup to the vdslGroup and to the ifEntry: 152 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 154 vdslLineTableEntry (vdslLineCoding=SCM) 155 ----> vdslPhysTableEntry 1:(0..2) 156 ----> vdslSCMPhysBandTable 1:(0..5) 158 vdslLineConfProfileEntry(vdslLineConfProfileName) 159 ----> vdslLineSCMConfProfileBandTable 1:(0..5) 161 Figure 1: Table Relationships 163 When the object vdslLineCoding is set to SCM, 164 vdslLineConfProfileName is used as the index to 165 vdslLineSCMConfProfileBandTable. The existence of an entry in 166 any of the tables of the vdslSCMGroup is optional. 168 2.4 Persistence 170 All read-create objects defined in this MIB module SHOULD be stored 171 persistently. Following is an exhaustive list of these persistent 172 objects: 174 vdslLineSCMConfProfileBandId 175 vdslLineSCMConfProfileBandUsage 176 vdslLineSCMConfProfileBandCenterFrequency 177 vdslLineSCMConfProfileBandSymbolRate 178 vdslLineSCMConfProfileBandConstellationSize 179 vdslLineSCMConfProfileBandTransmitPSDLevel 180 vdslLineSCMConfProfileBandRowStatus 181 vdslLineSCMPhysBandId 182 vdslLineSCMPhysBandUsage 183 vdslLineSCMPhysBandCurrPSDLevel 184 vdslLineSCMPhysBandCurrSymbolRate 185 vdslLineSCMPhysBandCurrConstellationSize 186 vdslLineSCMPhysBandCurrCenterFrequency 187 vdslLineSCMPhysBandPerformanceBandId 188 vdslLineSCMPhysBandPerformanceBandUsage 189 vdslLineSCMPhysBandPerformanceBandSnrMgn 190 vdslLineSCMPhysBandPerformanceBandAtn 192 Note also that the interface indices in this MIB are maintained 193 persistently. View-based Access Control Model (VACM) data 194 relating to these SHOULD be stored persistently as well [RFC3415]. 196 3. Conformance and Compliance 198 An SCM based VDSL agent does not have to implement this MIB to be 199 compliant with RFC 3728 [RFC3728]. If the SCM VDSL Line Extension 200 MIB is implemented then the following group is mandatory: 202 - vdslSCMGroup 204 4. Definitions 206 VDSL-LINE-EXT-SCM-MIB DEFINITIONS ::= BEGIN 208 IMPORTS 209 MODULE-IDENTITY, 210 OBJECT-TYPE, 211 Integer32, 212 Unsigned32 FROM SNMPv2-SMI -- [RFC2578] 213 RowStatus FROM SNMPv2-TC -- [RFC2579] 214 MODULE-COMPLIANCE, 215 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 216 ifIndex FROM IF-MIB -- [RFC2863] 217 vdslMIB, 218 vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] 220 vdslExtSCMMIB MODULE-IDENTITY 221 LAST-UPDATED "200405300000Z" -- May 30, 2004 222 ORGANIZATION "ADSLMIB Working Group" 223 CONTACT-INFO "WG-email: adslmib@ietf.org 224 Info: https://www1.ietf.org/mailman/listinfo/adslmib 226 Chair: Mike Sneed 227 Sand Channel Systems 228 Postal: P.O. Box 37324 229 Raleigh NC 27627-732 230 Email: sneedmike@hotmail.com 231 Phone: +1 206 600 7022 233 co-editor: Menachem Dodge 234 Infineon Technologies Savan Ltd. 235 6 Hagavish St. 236 Postal: Poleg Industrial Area, 237 Netanya 42504, 238 Israel. 239 Email: menachem.dodge@infineon.com 240 Phone: +972 9 892 4116 242 Co-editor: Bob Ray 243 PESA Switching Systems, Inc. 244 Postal: 330-A Wynn Drive 245 Huntsville, AL 35805 246 USA 247 Email: rray@pesa.com 248 Phone: +1 256 726 9200 ext. 142 249 " 250 DESCRIPTION 251 "The VDSL-LINE-MIB found in RFC 3728 defines objects for 252 the management of a pair of VDSL transceivers at each end of 253 the VDSL line. The VDSL-LINE-MIB configures and monitors the 254 line code independent parameters (TC layer) of the VDSL line. 255 This MIB module is an optional extension of the VDSL-LINE-MIB 256 and defines objects for configuration and monitoring of the 257 line code specific (LCS) elements (PMD layer) for VDSL lines 258 using SCM coding. The objects in this extension MIB MUST NOT 259 be used for VDSL lines using Multiple Carrier Modulation (MCM) 260 line coding. If an object in this extension MIB is referenced 261 by a line which does not use SCM, it has no effect on the 262 operation of that line. 264 Naming Conventions: 265 Vtuc -- (VTUC) transceiver at near (Central) end of line 266 Vtur -- (VTUR) transceiver at Remote end of line 267 Vtu -- One of either Vtuc or Vtur 268 Curr -- Current 269 Atn -- Attenuation 270 LCS -- Line Code Specific 271 Max -- Maximum 272 Mgn -- Margin 273 PSD -- Power Spectral Density 274 Rx -- Receive 275 Snr -- Signal to Noise Ratio 276 Tx -- Transmit 278 Copyright (C) The Internet Society (2004). This version 279 of this MIB module is part of RFC XXXX: see the RFC 280 itself for full legal notices." 281 -- RFC Ed.: replace XXXX with assigned number & remove this note 282 REVISION "200405300000Z" -- May 30, 2004 283 DESCRIPTION "Initial version, published as RFC XXXX." 284 -- RFC Ed.: replace XXXX with assigned number & remove this note 285 ::= { vdslMIB XX } -- To be assigned by IANA 286 -- RFC Ed.: we suggest to put it under { vdslMIB 2 } because 287 -- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM 288 -- extension MIB, while vdslMIB 3 is the MCM extension MIB. 290 vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } 291 vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= 292 { vdslLineExtSCMMib 1 } 294 -- 295 -- Single carrier modulation (SCM) configuration profile tables 296 -- 298 vdslLineSCMConfProfileBandTable OBJECT-TYPE 299 SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry 300 MAX-ACCESS not-accessible 301 STATUS current 302 DESCRIPTION 303 "This table contains transmit band descriptor configuration 304 information for a VDSL line. Each entry in this table 305 reflects the configuration for one of possibly many bands 306 of a single carrier modulation (SCM) VDSL line. For each 307 profile which is associated with a VDSL line using SCM 308 line coding, five entries in this table will exist, one for 309 each of the five bands. Bands which are not in use will be 310 marked as unused. These entries are defined by a manager 311 and can be used to configure the VDSL line. If an entry in 312 this table is referenced by a line which does not use SCM, 313 it has no effect on the operation of that line." 314 ::= { vdslLineExtSCMMibObjects 1 } 316 vdslLineSCMConfProfileBandEntry OBJECT-TYPE 317 SYNTAX VdslLineSCMConfProfileBandEntry 318 MAX-ACCESS not-accessible 319 STATUS current 320 DESCRIPTION 321 "Each entry consists of a list of parameters that 322 represents the configuration of a single carrier 323 modulation VDSL modem transmit band. 325 A default profile with an index of 'DEFVAL', will 326 always exist and its parameters will be set to vendor 327 specific values, unless otherwise specified in this 328 document." 330 INDEX { vdslLineConfProfileName, 331 vdslLineSCMConfProfileBandId } 332 ::= { vdslLineSCMConfProfileBandTable 1 } 334 VdslLineSCMConfProfileBandEntry ::= 335 SEQUENCE 336 { 337 vdslLineSCMConfProfileBandId Unsigned32, 338 vdslLineSCMConfProfileBandUsage Unsigned32, 339 vdslLineSCMConfProfileBandCenterFrequency Unsigned32, 340 vdslLineSCMConfProfileBandSymbolRate Unsigned32, 341 vdslLineSCMConfProfileBandConstellationSize Unsigned32, 342 vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, 343 vdslLineSCMConfProfileBandRowStatus RowStatus 344 } 346 vdslLineSCMConfProfileBandId OBJECT-TYPE 347 SYNTAX Unsigned32 { optionalBand(1), 348 firstDownstreamBand(2), 349 firstUpstreamBand(3), 350 secondDownstreamBand(4), 351 secondUpstreamBand(5), 352 thirdDownstreamBand(6), 353 thirdUpstreamBand(7)} 354 MAX-ACCESS read-create 355 STATUS current 356 DESCRIPTION 357 "The BandId for this entry, which specifies which band 358 is being referred to. Specified as an Unsigned32, the five 359 possible values are: 360 optionalBand(1), firstDownstreamBand(2), 361 firstUpstreamBand(3), secondDownstreamBand(4), 362 secondUpstreamBand(5), thirdDownstreamBand(6), 363 thirdUpstreamBand(7)" 364 ::= { vdslLineSCMConfProfileBandEntry 1 } 366 vdslLineSCMConfProfileBandUsage OBJECT-TYPE 367 SYNTAX unsigned32 368 MAX-ACCESS read-create 369 STATUS current 370 DESCRIPTION 371 "Indicates whether this band is in use. 372 Specified as an Unsigned32, the two 373 possible values are: 374 Unused(1), 375 InUse(2)" 376 ::= { vdslLineSCMConfProfileBandEntry 2 } 378 vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE 379 SYNTAX Unsigned32 380 UNITS "Hz" 381 MAX-ACCESS read-create 382 STATUS current 383 DESCRIPTION 384 "Specifies the center frequency in Hz" 385 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 386 ::= { vdslLineSCMConfProfileBandEntry 3 } 388 vdslLineSCMConfProfileBandSymbolRate OBJECT-TYPE 389 SYNTAX Unsigned32 390 UNITS "baud" 391 MAX-ACCESS read-create 392 STATUS current 393 DESCRIPTION 394 "The requested symbol rate in baud." 395 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 396 ::= { vdslLineSCMConfProfileBandEntry 4 } 398 vdslLineSCMConfProfileBandConstellationSize OBJECT-TYPE 399 SYNTAX Unsigned32 (0..16) 400 UNITS "log2" 401 MAX-ACCESS read-create 402 STATUS current 403 DESCRIPTION 404 "Specifies the constellation size." 405 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 406 ::= { vdslLineSCMConfProfileBandEntry 5 } 408 vdslLineSCMConfProfileBandTransmitPSDLevel OBJECT-TYPE 409 SYNTAX Unsigned32 410 UNITS "-0.25 dBm/Hz" 411 MAX-ACCESS read-create 412 STATUS current 413 DESCRIPTION 414 "The requested transmit power spectral density for the VDSL 415 modem. The Actual value in -0.25 dBm/Hz." 416 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 417 ::= { vdslLineSCMConfProfileBandEntry 6 } 419 vdslLineSCMConfProfileBandRowStatus OBJECT-TYPE 420 SYNTAX RowStatus 421 MAX-ACCESS read-create 422 STATUS current 423 DESCRIPTION 424 "This object is used to create a new row or modify or 425 delete an existing row in this table. 427 A profile activated by setting this object to `active'. 428 When `active' is set, the system will validate the profile. 430 Before a profile can be deleted or taken out of 431 service, (by setting this object to `destroy' or 432 `outOfService') it must be first unreferenced 433 from all associated lines." 434 ::= { vdslLineSCMConfProfileBandEntry 7 } 436 -- 437 -- SCM physical band 438 -- 440 vdslLineSCMPhysBandTable OBJECT-TYPE 441 SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry 442 MAX-ACCESS not-accessible 443 STATUS current 444 DESCRIPTION 445 "This table provides one row for each SCM Vtu band. This 446 table is read only as it reflects the current physical 447 parameters of each band. For each ifIndex which is 448 associated with a VDSL line using SCM line coding, five 449 entries in this table will exist, one for each of the 450 five bands. Bands which are not in use will be marked 451 as unused." 452 ::= { vdslLineExtSCMMibObjects 2 } 454 vdslLineSCMPhysBandEntry OBJECT-TYPE 455 SYNTAX VdslLineSCMPhysBandEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "An entry in the vdslLineSCMPhysBandTable." 460 INDEX { ifIndex, 461 vdslLineSCMPhysBandId } 462 ::= { vdslLineSCMPhysBandTable 1 } 464 VdslLineSCMPhysBandEntry ::= 465 SEQUENCE 466 { 467 vdslLineSCMPhysBandId Unsigned32, 468 vdslLineSCMPhysBandUsage Unsigned32, 469 vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, 470 vdslLineSCMPhysBandCurrSymbolRate Unsigned32, 471 vdslLineSCMPhysBandCurrConstellationSize Unsigned32, 472 vdslLineSCMPhysBandCurrPSDLevel Unsigned32, 473 vdslLineSCMPhysBandCurrSnrMgn Integer32, 474 vdslLineSCMPhysBandCurrAtn Unsigned32 475 } 477 vdslLineSCMPhysBandId OBJECT-TYPE 478 SYNTAX Unsigned32 { optionalBand(1), 479 firstDownstreamBand(2), 480 firstUpstreamBand(3), 481 secondDownstreamBand(4), 482 secondUpstreamBand(5), 483 thirdDownstreamBand(6), 484 thirdUpstreamBand(7) } 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "The BandId for this entry, which specifies which band 489 is being referred to. Specified as an Unsigned32, the 490 five possible values are: 491 optionalBand(1), firstDownstreamBand(2), 492 firstUpstreamBand(3), secondDownstreamBand(4), 493 secondUpstreamBand(5), thirdDownstreamBand(6), 494 thirdUpstreamBand(7)" 495 ::= { vdslLineSCMPhysBandEntry 1 } 497 vdslLineSCMPhysBandUsage OBJECT-TYPE 498 SYNTAX Unsigned32 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "Indicates whether this band is in use. 503 Specified as an Unsigned32, the two 504 possible values are: 505 Unused(1), 506 InUse(2)" 507 ::= { vdslLineSCMPhysBandEntry 2 } 509 vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE 510 SYNTAX Unsigned32 511 UNITS "Hz" 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The current center frequency in Hz for this band." 516 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 517 ::= { vdslLineSCMPhysBandEntry 3 } 519 vdslLineSCMPhysBandCurrSymbolRate OBJECT-TYPE 520 SYNTAX Unsigned32 521 UNITS "baud" 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The current value of the symbol rate in baud for this 526 band." 527 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 528 ::= { vdslLineSCMPhysBandEntry 4 } 530 vdslLineSCMPhysBandCurrConstellationSize OBJECT-TYPE 531 SYNTAX Unsigned32 (0..16) 532 UNITS "log2" 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "The current constellation size on this band." 537 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 538 ::= { vdslLineSCMPhysBandEntry 5 } 540 vdslLineSCMPhysBandCurrPSDLevel OBJECT-TYPE 541 SYNTAX Unsigned32 542 UNITS "- 0.25 dBm/Hz" 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "The transmit power spectral density for the 547 VDSL modem." 548 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 549 ::= { vdslLineSCMPhysBandEntry 6 } 551 vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE 552 SYNTAX Integer32 553 UNITS "0.25 dBm" 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "Noise margin as seen by this Vtu and band with respect 558 to its received signal in 0.25 dB." 559 ::= { vdslLineSCMPhysBandEntry 7 } 561 vdslLineSCMPhysBandCurrAtn OBJECT-TYPE 562 SYNTAX Unsigned32 (0..255) 563 UNITS "0.25 dBm" 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "Measured difference in the total power transmitted by 568 the peer Vtu on this band and the total power received 569 by this Vtu on this band in 0.25 dB." 570 ::= { vdslLineSCMPhysBandEntry 8 } 572 -- conformance information 573 vdslLineExtSCMConformance OBJECT IDENTIFIER ::= 574 { vdslLineExtSCMMib 2 } 575 vdslLineExtSCMGroups OBJECT IDENTIFIER ::= 576 { vdslLineExtSCMConformance 1 } 577 vdslLineExtSCMCompliances OBJECT IDENTIFIER ::= 578 { vdslLineExtSCMConformance 2 } 580 vdslLineExtSCMMibCompliance MODULE-COMPLIANCE 581 STATUS current 582 DESCRIPTION 583 "The compliance statement for SNMP entities which 584 manage VDSL interfaces." 586 MODULE -- this module 588 MANDATORY-GROUPS 589 { 590 vdslLineExtSCMGroup 591 } 593 ::= { vdslLineExtSCMCompliances 1 } 595 -- units of conformance 597 vdslLineExtSCMGroup OBJECT-GROUP 598 OBJECTS 599 { 600 vdslLineSCMConfProfileBandId, 601 vdslLineSCMConfProfileBandUsage, 602 vdslLineSCMConfProfileBandTransmitPSDLevel, 603 vdslLineSCMConfProfileBandSymbolRate, 604 vdslLineSCMConfProfileBandConstellationSize, 605 vdslLineSCMConfProfileBandCenterFrequency, 606 vdslLineSCMConfProfileBandRowStatus, 607 vdslLineSCMPhysBandId, 608 vdslLineSCMPhysBandUsage, 609 vdslLineSCMPhysBandCurrPSDLevel, 610 vdslLineSCMPhysBandCurrSymbolRate, 611 vdslLineSCMPhysBandCurrConstellationSize, 612 vdslLineSCMPhysBandCurrCenterFrequency, 613 vdslLineSCMPhysBandCurrSnrMgn, 614 vdslLineSCMPhysBandCurrAtn 616 } 617 STATUS current 618 DESCRIPTION 619 "A collection of objects providing configuration 620 information for a VDSL line based upon single carrier 621 modulation modem." 622 ::= { vdslLineExtSCMGroups 1 } 624 END 626 5. Acknowledgments 628 This document contains many definitions taken from 629 draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text 630 found within should be full attributed to the authors of that 631 document. 633 6. Security Considerations 635 There are a number of management objects defined in this MIB module 636 with a MAX-ACCESS clause of read-create. Such objects may be 637 considered sensitive or vulnerable in some network environments. 638 The support for SET operations in a non-secure environment without 639 proper protection can have a negative effect on network operations. 641 Some of the readable objects in this MIB module (i.e., objects with a 642 MAX-ACCESS other than not-accessible) may be considered sensitive or 643 vulnerable in some network environments. 645 VDSL layer connectivity from the Vtur will permit the subscriber to 646 manipulate both the VDSL link directly and the VDSL embedded 647 operations channel (EOC) for their own loop. For example, unchecked 648 or unfiltered fluctuations initiated by the subscriber could generate 649 sufficient notifications to potentially overwhelm either the 650 management interface to the network or the element manager. 652 Additionally, allowing write access to configuration data may allow 653 an end-user to increase their service levels or affect other end- 654 users in either a positive or negative manner. For this reason, the 655 following tables should be considered to contain sensitive 656 information: 658 - vdslLineSCMConfProfileTxBandTable 659 - vdslSCMPhysBandTable 661 It is thus important to control even GET access to the objects within 662 these tables and possibly to even encrypt the values of these objects 663 when sending them over the network via SNMP. Not all versions of 664 SNMP provide features for such a secure environment. 666 SNMP versions prior to SNMPv3 did not include adequate security. 667 Even if the network itself is secure (for example by using IPSec), 668 even then, there is no control as to who on the secure network is 669 allowed to access and GET/SET (read/change/create/delete) the objects 670 in this MIB module. 672 It is RECOMMENDED that implementers consider the security features 673 as provided by the SNMPv3 framework (see [RFC3410], section 8), 674 including full support for the SNMPv3 cryptographic mechanisms (for 675 authentication and privacy). 677 Further, deployment of SNMP versions prior to SNMPv3 is NOT 678 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 679 enable cryptographic security. It is then a customer/operator 680 responsibility to ensure that the SNMP entity giving access to an 681 instance of a MIB module which utilizes the textual conventions 682 defined in this MIB module is properly configured to give access to 683 the objects only to those principals (users) that have legitimate 684 rights to indeed GET or SET (change/create/delete) them. 686 7. References 688 7.1. Normative References 690 [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", 691 February 2003. 693 [DSLFWT096] DSL Forum WT-096, "SCM Specific Managed Objects In 694 VDSL Network Elements". 696 [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing 697 (TM); Access transmission systems on metallic access 698 cables; Very high speed Digital Subscriber Line (VDSL); 699 Part 1: Functional requirements", October 1999. 701 [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing 702 (TM); Access transmission systems on metallic access 703 cables; Very high speed Digital Subscriber Line (VDSL); 704 Part 1: Transceiver specification", February 2001. 706 [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line 707 foundation", November 2001. 709 [ITU9971] ITU-T G.997.1, "Physical layer management for Digital 710 Subscriber Line (DSL) Transceivers", July 1999. 712 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 713 Performance History Based on 15 Minute Intervals", RFC 714 3593, September 2003. 716 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 717 Requirement Levels", BCP 14, RFC 2119, March 1997. 719 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 720 Rose, M. and S. Waldbusser, "Structure of Management 721 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 722 1999. 724 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 725 Rose, M. and S. Waldbusser, "Textual Conventions for 726 SMIv2", STD 58, RFC 2579, April 1999. 728 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 729 Rose, M. and S. Waldbusser, "Conformance Statements for 730 SMIv2", STD 58, RFC 2580, April 1999. 732 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 733 Conventions for Additional High Capacity Data Types", 734 RFC 2856, June 2000. 736 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 737 MIB", RFC 2863, June 2000. 739 [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An 740 Architecture for Describing Simple Network Management 741 Protocol (SNMP) Management Frameworks", RFC 3411, 742 December 2002. 744 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 745 Simple Network Management Protocol (SNMP)", STD 62, RFC 746 3418, December 2002. 748 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 749 Very High Speed Digital Subscriber Lines (VDSL)", RFC 750 3728, February 2004. 752 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 753 Subscriber Line (VDSL) Metallic Interface, Part 1: 754 Functional Requirements and Common Specification", 755 February 2001. 757 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 758 Technical Specification for a Single-Carrier Modulation 759 (SCM) Transceiver", November 2001. 761 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 762 Technical Specification for a Multi-Carrier Modulation 763 (MCM) Transceiver", November 2000. 765 7.2. Informative References 767 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 768 Access Control Model (VACM) for the Simple Network 769 Management Protocol (SNMP)", RFC 3415, December 2002. 771 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 772 "Introduction and Applicability Statements for Internet- 773 Standard Management Framework", RFC 3410, December 2002. 775 Authors' Addresses 777 Menachem Dodge 778 Infineon Technologies Savan Ltd. 779 6 Hagavish St. 780 Poleg Industrial Area, 781 Netanya 42504, 782 Israel. 784 Phone: +972 9 892 4116 785 Fax: +972 9 865 8756 786 Email: menachem.dodge@infineon.com 788 Bob Ray 789 PESA Switching Systems, Inc. 790 330-A Wynn Drive 791 Huntsville, AL 35805 792 USA 794 Phone: +1 256 726 9200 ext. 142 795 Fax: +1 256 726 9271 796 EMail: rray@pesa.com 798 Full Copyright Statement 800 Copyright (C) The Internet Society (2004). This document is subject 801 to the rights, licenses and restrictions contained in BCP 78 and 802 except as set forth therein, the authors retain all their rights. 804 This document and the information contained herein are provided on an 805 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 806 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 807 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 808 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 809 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 810 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 812 Intellectual Property 814 The IETF takes no position regarding the validity or scope of any 815 Intellectual Property Rights or other rights that might be claimed to 816 pertain to the implementation or use of the technology described in 817 this document or the extent to which any license under such rights 818 might or might not be available; nor does it represent that it has 819 made any independent effort to identify any such rights. Information 820 on the procedures with respect to rights in RFC documents can be 821 found in BCP 78 and BCP 79. 823 Copies of IPR disclosures made to the IETF Secretariat and any 824 assurances of licenses to be made available, or the result of an 825 attempt made to obtain a general license or permission for the use of 826 such proprietary rights by implementers or users of this 827 specification can be obtained from the IETF on-line IPR repository at 828 http://www.ietf.org/ipr. 830 The IETF invites any interested party to bring to its attention any 831 copyrights, patents or patent applications, or other proprietary 832 rights that may cover technology that may be required to implement 833 this standard. Please address the information to the IETF at ietf- 834 ipr@ietf.org. 836 Acknowledgement 838 Funding for the RFC Editor function is currently provided by the 839 Internet Society.