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