idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-scm-02.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 3978, Section 5.5 on line 780. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 791. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 798. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 804. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 772), 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. ** 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. 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 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([RFC3728]), 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 134: '...ts in this group MAY be implemented fo...' RFC 2119 keyword, line 155: '...lSCMGroup tables MAY be implemented fo...' RFC 2119 keyword, line 160: '...ed in this MIB module SHOULD be stored...' RFC 2119 keyword, line 182: '... It SHOULD also be noted that interf...' RFC 2119 keyword, line 183: '... 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 (March 2004) is 7345 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: 'ETSI2701' is defined on line 662, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 667, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 672, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 675, but no explicit reference was found in the text == Unused Reference: 'RFC2493' is defined on line 678, but no explicit reference was found in the text == Unused Reference: 'RFC2856' is defined on line 695, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 702, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 707, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 715, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 720, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 724, 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. '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: 13 errors (**), 0 flaws (~~), 13 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 March 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-02.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 Abstract 39 This document defines a portion of the Management Information Base 40 (MIB) module for use with network management protocols in the 41 Internet community. In particular, it describes objects used for 42 managing the Line Code Specific parameters of Very High Speed 43 Digital Subscriber Line (VDSL) interfaces using Single Carrier 44 Modulation (SCM) Line Coding. It is an optional extension to the 45 VDSL-LINE-MIB, RFC 3728 [RFC3728], which handles line code 46 independent objects. 48 Table of Contents 50 1. The Internet-Standard Management Framework .................... 2 51 2. Overview ...................................................... 2 52 2.1 Relationship of this MIB Module to other MIB Modules . 2 53 2.2 Conventions used in the MIB Module ............................ 3 54 2.3 Structure ..................................................... 3 55 2.4 Persistence ................................................... 4 56 3. Conformance and Compliance .................................... 4 57 4. Definitions ................................................... 4 58 5. Security Considerations ....................................... 13 59 6. References .................................................... 14 60 6.1 Normative References .......................................... 14 61 6.2 Informative References ........................................ 15 62 7. Acknowledgements .............................................. 15 63 8. Authors' Addresses ............................................ 15 64 9. Full Copyright Statement ...................................... 16 66 1. The Internet-Standard Management Framework 68 For a detailed overview of the documents that describe the current 69 Internet-Standard Management Framework, please refer to section 7 of 70 RFC 3410 [RFC3410]. 72 Managed objects are accessed via a virtual information store, termed 73 the Management Information Base or MIB. MIB objects are generally 74 accessed through the Simple Network Management Protocol (SNMP). 75 Objects in the MIB are defined using the mechanisms defined in the 76 Structure of Management Information (SMI). This memo specifies a 77 MIB module that is compliant to the SMIv2, which is described in STD 78 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 79 2580 [RFC2580]. 81 2. Overview 83 This document describes an SNMP MIB module for managing the line 84 code dependent (Physical Medium Dependent) Layer of SCM VDSL Lines. 85 These definitions are based upon the specifications for VDSL as 86 defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, 87 T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. Additionally the 88 protocol-dependent (and line-code dependent) management framework 89 for VDSL lines specified by DSLF has been taken into consideration 90 [DSLFTR057] and [DSLFWT096]. 92 The MIB module is located in the MIB tree under MIB 2 transmission, 93 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section 94 of this document. 96 2.1 Relationship of this MIB Module to other MIB Modules 98 The relationship of the VDSL Line MIB to other MIBS and in particular 99 to the IF-MIB, as presented in RFC 2863 [RFC2863], is discussed in 100 the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section outlines the 101 relationship of this VDSL Line Extension MIB to the VDSL-LINE-MIB, 102 RFC 3728 [RFC3728]. 104 2.2 Conventions used in the MIB Module 106 2.2.1 Naming Conventions 108 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 109 B. Vtur -- (VTUR) transceiver at Remote end of line 110 C. Vtu -- One of either Vtuc or Vtur 111 D. Curr -- Current 112 F. Atn -- Attenuation 113 J. LCS -- Line Code Specific 114 K. Max -- Maximum 115 Q. Mgn -- Margin 116 S. PSD -- Power Spectral Density 117 T. Rx -- Receive 118 T. Snr -- Signal to Noise Ratio 119 U. Tx -- Transmit 121 2.3 Structure 123 The SCM VDSL Line Extension MIB contains the following MIB group: 125 o vdslSCMGroup : 127 This group supports MIB objects for defining configuration profiles 128 and for montioring individual bands of Single Carrier Modulation 129 (SCM) VDSL modems. It contains the following tables: 131 - vdslLineSCMConfProfileTxBandTable 132 - vdslSCMPhysBandTable 134 None, one or both objects in this group MAY be implemented for 135 SCM VDSL lines. 137 Figure 1, below, displays the relationship of the tables in the 138 vdslSCMGroup to the vdslGroup and to the ifEntry: 140 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 142 vdslLineTableEntry (vdslLineCoding=SCM) 143 ----> vdslPhysTableEntry 1:(0..2) 144 ----> vdslSCMPhysBandTable 1:(0..6) 146 vdslLineConfProfileEntry(vdslLineConfProfileName) 147 ----> vdslLineSCMConfProfileBandTable 1:(0..6) 149 Figure 1: Table Relationships 151 When the object vdslLineCoding is set to SCM, 152 vdslLineConfProfileName is used as the index to 153 vdslLineSCMConfProfileBandTable. The existence of an entry in 154 any of the tables of the vdslSCMGroup is optional. None, some or 155 all of the vdslSCMGroup tables MAY be implemented for a particular 156 VDSL line entity using SCM line coding. 158 2.4 Persistence 160 All read-create objects defined in this MIB module SHOULD be stored 161 persistently. Following is an exhaustive list of these persistent 162 objects: 164 vdslSCMConfProfileBandId 165 vdslSCMConfProfileBandUsage 166 vdslSCMConfProfileBandCenterFrequency 167 vdslSCMConfProfileBandSymbolRate 168 vdslSCMConfProfileBandConstellationSize 169 vdslSCMConfProfileBandTransmitPSDLevel 170 vdslSCMConfProfileBandRowStatus 171 vdslSCMPhysBandId 172 vdslSCMPhysBandUsage 173 vdslSCMPhysBandCurrPSDLevel 174 vdslSCMPhysBandCurrSymbolRate 175 vdslSCMPhysBandCurrConstellationSize 176 vdslSCMPhysBandCurrCenterFrequency 177 vdslSCMPhysBandPerformanceBandId 178 vdslSCMPhysBandPerformanceBandUsage 179 vdslSCMPhysBandPerformanceBandSnrMgn 180 vdslSCMPhysBandPerformanceBandAtn 182 It SHOULD also be noted that interface indices in this MIB are 183 maintained persistently. VACM data relating to these SHOULD be 184 stored persistently as well [RFC2575]. 186 3. Conformance and Compliance 188 For SCM VDSL lines, the following group is optional: 190 - vdslSCMGroup 192 4. Definitions 194 VDSL-LINE-EXT-SCM-MIB DEFINITIONS ::= BEGIN 196 IMPORTS 198 MODULE-IDENTITY, 199 OBJECT-TYPE, 200 Integer32, 201 Unsigned32 FROM SNMPv2-SMI -- [RFC2578] 202 RowStatus FROM SNMPv2-TC -- [RFC2579] 203 MODULE-COMPLIANCE, 204 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 205 ifIndex FROM IF-MIB -- [RFC2863] 206 vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] 208 vdslExtSCMMIB MODULE-IDENTITY 209 LAST-UPDATED "200403140000Z" -- March 14, 2004 210 ORGANIZATION "ADSLMIB Working Group" 211 CONTACT-INFO "WG-email: adslmib@ietf.org 212 Info: https://www1.ietf.org/mailman/listinfo/adslmib 214 Chair: Mike Sneed 215 Sand Channel Systems 216 Postal: P.O. Box 37324 217 Raleigh NC 27627-732 218 Email: sneedmike@hotmail.com 219 Phone: +1 206 600 7022 221 co-editor: Menachem Dodge 222 Infineon Technologies Savan Ltd. 223 6 Hagavish St. 224 Postal: Poleg Industrial Area, 225 Netanya 42504, 226 Israel. 227 Email: menachem.dodge@infineon.com 228 Phone: +972 9 892 4116 230 Co-editor: Bob Ray 231 PESA Switching Systems, Inc. 232 Postal: 330-A Wynn Drive 233 Huntsville, AL 35805 234 USA 235 Email: rray@pesa.com 236 Phone: +1 256 726 9200 ext. 142 237 " 238 DESCRIPTION 239 "The VDSL-LINE-MIB found in RFC 3728 defines objects for 240 the management of a pair of VDSL transceivers at each end of 241 the VDSL line. The VDSL-LINE-MIB configures and monitors the line 242 code independent parameters (TC layer) of the VDSL line. 243 This MIB module is an optional extension of the VDSL-LINE-MIB and 244 defines objects for configuration and monitoring of the line 245 code specific (LCS) elements (PMD layer) for VDSL lines using 246 SCM coding. The objects in this extension MIB MUST NOT be used 247 for VDSL lines using MCM line coding. 249 Naming Conventions: 250 Vtuc -- (VTUC) transceiver at near (Central) end of line 251 Vtur -- (VTUR) transceiver at Remote end of line 252 Vtu -- One of either Vtuc or Vtur 253 Curr -- Current 254 Atn -- Attenuation 255 LCS -- Line Code Specific 256 Max -- Maximum 257 Mgn -- Margin 258 PSD -- Power Spectral Density 259 Rx -- Receive 260 Snr -- Signal to Noise Ratio 261 Tx -- Transmit 263 Copyright (C) The Internet Society (2004). This version 264 of this MIB module is part of RFC XXXX: see the RFC 265 itself for full legal notices." 266 -- RFC Ed.: replace XXXX with assigned number & remove this note 267 REVISION "200403140000Z" -- March 14, 2004 268 DESCRIPTION "Initial version, published as RFC XXXX." 269 -- RFC Ed.: replace XXXX with assigned number & remove this note 270 ::= { vdslMIB XX } -- To be assigned by IANA 271 -- RFC Ed.: we suggest to put it under { vdslMIB 2 } because 272 -- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is this SCM 273 -- extension MIB, while vdslMIB 3 is the MCM extension MIB. 275 vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } 276 vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= 277 { vdslLineExtSCMMib 1 } 279 -- 280 -- Single carrier modulation (SCM) configuration profile tables 281 -- 283 vdslLineSCMConfProfileBandTable OBJECT-TYPE 284 SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "This table contains transmit band descriptor configuration 289 information for a VDSL line. Each entry in this table 290 reflects the configuration for one of possibly many bands 291 of a single carrier modulation (SCM) VDSL line. 292 These entries are defined by a manager and can be used to 293 configure the VDSL line." 294 ::= { vdslLineExtSCMMibObjects 1 } 296 vdslLineSCMConfProfileBandEntry OBJECT-TYPE 297 SYNTAX VdslLineSCMConfProfileBandEntry 298 MAX-ACCESS not-accessible 299 STATUS current 300 DESCRIPTION 301 "Each entry consists of a list of parameters that 302 represents the configuration of a single carrier 303 modulation VDSL modem transmit band. 305 A default profile with an index of 'DEFVAL', will 306 always exist and its parameters will be set to vendor 307 specific values, unless otherwise specified in this 308 document." 310 INDEX { vdslLineConfProfileName, 311 vdslLineSCMConfProfileBandId } 312 ::= { vdslLineSCMConfProfileBandTable 1 } 314 VdslLineSCMConfProfileBandEntry ::= 315 SEQUENCE 316 { 317 vdslLineSCMConfProfileBandId INTEGER, 318 vdslLineSCMConfProfileBandUsage INTEGER, 319 vdslLineSCMConfProfileBandCenterFrequency Unsigned32, 320 vdslLineSCMConfProfileBandSymbolRate Unsigned32, 321 vdslLineSCMConfProfileBandConstellationSize Unsigned32, 322 vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, 323 vdslLineSCMConfProfileBandRowStatus RowStatus 324 } 326 vdslLineSCMConfProfileBandId OBJECT-TYPE 327 SYNTAX INTEGER 328 MAX-ACCESS not-accessible 329 STATUS current 330 DESCRIPTION 331 "The BandId for this entry, which specifies which band 332 is being referred to. Specified as an INTEGER, the five 333 possible values are: 334 optionalBand(1), 335 1D(2), 336 1U(3), 337 2D(4), 338 2U(5)" 339 ::= { vdslLineSCMConfProfileBandEntry 1 } 341 vdslLineSCMConfProfileBandUsage OBJECT-TYPE 342 SYNTAX INTEGER 343 MAX-ACCESS not-accessible 344 STATUS current 345 DESCRIPTION 346 "Indicates whether this band is in use. 347 Specified as an INTEGER, the two 348 possible values are: 349 Unused(1), 350 InUse(2)" 352 ::= { vdslLineSCMConfProfileBandEntry 2 } 354 vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE 355 SYNTAX Unsigned32 356 UNITS "Hz" 357 MAX-ACCESS read-create 358 STATUS current 359 DESCRIPTION 360 "Specifies the center frequency in Hz" 361 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 362 ::= { vdslLineSCMConfProfileBandEntry 3 } 364 vdslLineSCMConfProfileBandSymbolRate OBJECT-TYPE 365 SYNTAX Unsigned32 366 UNITS "baud" 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION 370 "The requested symbol rate in baud." 371 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 372 ::= { vdslLineSCMConfProfileBandEntry 4 } 374 vdslLineSCMConfProfileBandConstellationSize OBJECT-TYPE 375 SYNTAX Unsigned32 (0..16) 376 UNITS "log2" 377 MAX-ACCESS read-create 378 STATUS current 379 DESCRIPTION 380 "Specifies the constellation size." 381 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 382 ::= { vdslLineSCMConfProfileBandEntry 5 } 384 vdslLineSCMConfProfileBandTransmitPSDLevel OBJECT-TYPE 385 SYNTAX Unsigned32 386 UNITS "-0.25 dBm/Hz" 387 MAX-ACCESS read-create 388 STATUS current 389 DESCRIPTION 390 "The requested transmit power spectral density for the VDSL 391 modem. The Actual value in -0.25 dBm/Hz." 392 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 393 ::= { vdslLineSCMConfProfileBandEntry 6 } 395 vdslLineSCMConfProfileBandRowStatus OBJECT-TYPE 396 SYNTAX RowStatus 397 MAX-ACCESS read-create 398 STATUS current 399 DESCRIPTION 400 "This object is used to create a new row or modify or 401 delete an existing row in this table. 403 A profile activated by setting this object to `active'. 404 When `active' is set, the system will validate the profile. 406 Before a profile can be deleted or taken out of 407 service, (by setting this object to `destroy' or 408 `outOfService') it must be first unreferenced 409 from all associated lines." 410 ::= { vdslLineSCMConfProfileBandEntry 7 } 412 -- 413 -- SCM physical band 414 -- 416 vdslLineSCMPhysBandTable OBJECT-TYPE 417 SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry 418 MAX-ACCESS not-accessible 419 STATUS current 420 DESCRIPTION 421 "This table provides one row for each SCM Vtu band. This 422 table is read only as it reflects the current physical 423 parameters of each band." 424 ::= { vdslLineExtSCMMibObjects 2 } 426 vdslLineSCMPhysBandEntry OBJECT-TYPE 427 SYNTAX VdslLineSCMPhysBandEntry 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "An entry in the vdslLineSCMPhysBandTable." 433 INDEX { ifIndex, 434 vdslLineSCMPhysBandId } 435 ::= { vdslLineSCMPhysBandTable 1 } 437 VdslLineSCMPhysBandEntry ::= 438 SEQUENCE 439 { 440 vdslLineSCMPhysBandId INTEGER, 441 vdslLineSCMPhysBandUsage INTEGER, 442 vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, 443 vdslLineSCMPhysBandCurrSymbolRate Unsigned32, 444 vdslLineSCMPhysBandCurrConstellationSize Unsigned32, 445 vdslLineSCMPhysBandCurrPSDLevel Unsigned32, 446 vdslLineSCMPhysBandCurrSnrMgn Integer32, 447 vdslLineSCMPhysBandCurrAtn Unsigned32 449 } 451 vdslLineSCMPhysBandId OBJECT-TYPE 452 SYNTAX INTEGER 453 MAX-ACCESS not-accessible 454 STATUS current 455 DESCRIPTION 456 "The BandId for this entry, which specifies which band 457 is being referred to. Specified as an INTEGER, the five 458 possible values are: 459 optionalBand(1), 460 1D(2), 461 1U(3), 462 2D(4), 463 2U(5)" 464 ::= { vdslLineSCMPhysBandEntry 1 } 466 vdslLineSCMPhysBandUsage OBJECT-TYPE 467 SYNTAX INTEGER 468 MAX-ACCESS not-accessible 469 STATUS current 470 DESCRIPTION 471 "Indicates whether this band is in use. 472 Specified as an INTEGER, the two 473 possible values are: 474 Unused(1), 475 InUse(2)" 477 ::= { vdslLineSCMPhysBandEntry 2 } 479 vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE 480 SYNTAX Unsigned32 481 UNITS "Hz" 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "The current center frequency in Hz for this band." 486 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 487 ::= { vdslLineSCMPhysBandEntry 3 } 489 vdslLineSCMPhysBandCurrSymbolRate OBJECT-TYPE 490 SYNTAX Unsigned32 491 UNITS "baud" 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "The current value of the symbol rate in baud for this 496 band." 497 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 498 ::= { vdslLineSCMPhysBandEntry 4 } 500 vdslLineSCMPhysBandCurrConstellationSize OBJECT-TYPE 501 SYNTAX Unsigned32 (0..16) 502 UNITS "log2" 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The current constellation size on this band." 507 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 508 ::= { vdslLineSCMPhysBandEntry 5 } 510 vdslLineSCMPhysBandCurrPSDLevel OBJECT-TYPE 511 SYNTAX Unsigned32 512 UNITS "- 0.25 dBm/Hz" 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "The transmit power spectral density for the 517 VDSL modem." 518 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 519 ::= { vdslLineSCMPhysBandEntry 6 } 521 vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE 522 SYNTAX Integer32 523 UNITS "0.25 dBm" 524 MAX-ACCESS read-only 525 STATUS current 526 DESCRIPTION 527 "Noise margin as seen by this Vtu and band with respect 528 to its received signal in 0.25 dB." 529 ::= { vdslLineSCMPhysBandEntry 7 } 531 vdslLineSCMPhysBandCurrAtn OBJECT-TYPE 532 SYNTAX Unsigned32 (0..255) 533 UNITS "0.25 dBm" 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "Measured difference in the total power transmitted by 538 the peer Vtu on this band and the total power received 539 by this Vtu on this band in 0.25 dB." 540 ::= { vdslLineSCMPhysBandEntry 8 } 542 -- conformance information 544 vdslLineExtSCMConformance OBJECT IDENTIFIER ::= 545 { vdslLineExtSCMMib 2 } 546 vdslLineExtSCMGroups OBJECT IDENTIFIER ::= 547 { vdslLineExtSCMConformance 1 } 548 vdslLineExtSCMCompliances OBJECT IDENTIFIER ::= 549 { vdslLineExtSCMConformance 2 } 551 vdslLineExtSCMMibCompliance MODULE-COMPLIANCE 552 STATUS current 553 DESCRIPTION 554 "The compliance statement for SNMP entities which 555 manage VDSL interfaces." 557 MODULE -- this module 559 MANDATORY-GROUPS 560 { 561 vdslLineExtSCMGroup 562 } 564 ::= { vdslLineExtSCMCompliances 1 } 566 -- units of conformance 568 vdslLineExtSCMGroup OBJECT-GROUP 569 OBJECTS 570 { 571 vdslLineSCMConfProfileBandId, 572 vdslLineSCMConfProfileBandUsage, 573 vdslLineSCMConfProfileBandTransmitPSDLevel, 574 vdslLineSCMConfProfileBandSymbolRate, 575 vdslLineSCMConfProfileBandConstellationSize, 576 vdslLineSCMConfProfileBandCenterFrequency, 577 vdslLineSCMConfProfileBandRowStatus, 578 vdslLineSCMPhysBandId, 579 vdslLineSCMPhysBandUsage, 580 vdslLineSCMPhysBandCurrPSDLevel, 581 vdslLineSCMPhysBandCurrSymbolRate, 582 vdslLineSCMPhysBandCurrConstellationSize, 583 vdslLineSCMPhysBandCurrCenterFrequency, 584 vdslLineSCMPhysBandCurrSnrMgn, 585 vdslLineSCMPhysBandCurrAtn 587 } 588 STATUS current 589 DESCRIPTION 590 "A collection of objects providing configuration 591 information for a VDSL line based upon single carrier 592 modulation modem." 593 ::= { vdslLineExtSCMGroups 1 } 595 END 597 5. Security Considerations 599 There are a number of management objects defined in this MIB that 600 have a MAX-ACCESS clause of read-create. Such 601 objects may be considered sensitive or vulnerable in some network 602 environments. The support for SET operations in a non-secure 603 environment without proper protection can have a negative effect on 604 network operations. 606 Some of the readable objects in this MIB module (i.e., objects with a 607 MAX-ACCESS other than not-accessible) may be considered sensitive or 608 vulnerable in some network environments. 610 VDSL layer connectivity from the Vtur will permit the subscriber to 611 manipulate both the VDSL link directly and the VDSL embedded 612 operations channel (EOC) for their own loop. For example, unchecked 613 or unfiltered fluctuations initiated by the subscriber could generate 614 sufficient notifications to potentially overwhelm either the 615 management interface to the network or the element manager. 617 Additionally, allowing write access to configuration data may allow 618 an end-user to increase their service levels or affect other end- 619 users in either a positive or negative manner. For this reason, the 620 following tables should be considered to contain sensitive 621 information: 623 - vdslLineSCMConfProfileTxBandTable 624 - vdslSCMPhysBandTable 626 It is thus important to control even GET access to these objects and 627 possibly to even encrypt the values of these objects when sending 628 them over the network via SNMP. Not all versions of SNMP provide 629 features for such a secure environment. 631 SNMP versions prior to SNMPv3 did not include adequate security. 632 Even if the network itself is secure (for example by using IPSec), 633 even then, there is no control as to who on the secure network is 634 allowed to access and GET/SET (read/change/create/delete) the objects 635 in this MIB module. 637 It is RECOMMENDED that implementers consider the security features 638 as provided by the SNMPv3 framework (see [RFC3410], section 8), 639 including full support for the SNMPv3 cryptographic mechanisms (for 640 authentication and privacy). 642 Further, deployment of SNMP versions prior to SNMPv3 is NOT 643 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 644 enable cryptographic security. It is then a customer/operator 645 responsibility to ensure that the SNMP entity giving access to an 646 instance of a MIB module which utilizes the textual conventions 647 defined in this MIB module is properly configured to give access to 648 the objects only to those principals (users) that have legitimate 650 rights to indeed GET or SET (change/create/delete) them. 652 6. References 654 6.1. Normative References 656 [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", 657 February 2003. 659 [DSLFWT096] DSL Forum WT-096, "SCM Specific Managed Objects In 660 VDSL Network Elements". 662 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 663 (TM); Access transmission systems on metallic access 664 cables; Very high speed Digital Subscriber Line (VDSL); 665 Part 1: Functional requirements", October 1999. 667 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 668 (TM); Access transmission systems on metallic access 669 cables; Very high speed Digital Subscriber Line (VDSL); 670 Part 1: Transceiver specification", February 2001. 672 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 673 foundation", November 2001. 675 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 676 Subscriber Line (DSL) Transceivers", July 1999. 678 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 679 Performance History Based on 15 Minute Intervals", RFC 680 2493, January 1999. 682 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 683 Rose, M. and S. Waldbusser, "Structure of Management 684 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 685 1999. 687 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 688 Rose, M. and S. Waldbusser, "Textual Conventions for 689 SMIv2", STD 58, RFC 2579, April 1999. 691 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 692 Rose, M. and S. Waldbusser, "Conformance Statements for 693 SMIv2", STD 58, RFC 2580, April 1999. 695 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 696 Conventions for Additional High Capacity Data Types", 697 RFC 2856, June 2000. 699 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 700 MIB", RFC 2863, June 2000. 702 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 703 Architecture for Describing Simple Network Management 704 Protocol (SNMP) Management Frameworks", RFC 3411, 705 December 2002. 707 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 708 Simple Network Management Protocol (SNMP)", STD 62, RFC 709 3418, December 2002. 711 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 712 Very High Speed Digital Subscriber Lines (VDSL)", RFC 713 3728, February 2004. 715 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 716 Subscriber Line (VDSL) Metallic Interface, Part 1: 717 Functional Requirements and Common Specification", 718 February 2001. 720 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 721 Technical Specification for a Single-Carrier Modulation 722 (SCM) Transceiver", November 2001. 724 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 725 Technical Specification for a Multi-Carrier Modulation 726 (MCM) Transceiver", November 2000. 728 6.2. Informative References 730 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 731 Access Control Model (VACM) for the Simple Network 732 Management Protocol (SNMP)", RFC 2575, April 1999. 734 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 735 "Introduction and Applicability Statements for Internet- 736 Standard Management Framework", RFC 3410, December 2002. 738 7. Acknowledgments 740 This document contains many definitions taken from 741 draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text 742 found within should be full attributed to the authors of that 743 document. 745 8. Authors' Addresses 747 Menachem Dodge 748 Infineon Technologies Savan Ltd. 749 6 Hagavish St. 750 Poleg Industrial Area, 751 Netanya 42504, 752 Israel. 754 Phone: +972 9 892 4116 755 Fax: +972 9 865 8756 756 Email: menachem.dodge@infineon.com 758 Bob Ray 759 PESA Switching Systems, Inc. 760 330-A Wynn Drive 761 Huntsville, AL 35805 762 USA 764 Phone: +1 256 726 9200 ext. 142 765 Fax: +1 256 726 9271 766 EMail: rray@pesa.com 768 9. Full Copyright Statement 770 Copyright (C) The Internet Society (2004). This document is subject 771 to the rights, licenses and restrictions contained in BCP 78 and 772 except as set forth therein, the authors retain all their rights. 774 This document and the information contained herein are provided on an 775 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 776 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 777 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 778 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 779 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 780 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 782 Intellectual Property 784 The IETF takes no position regarding the validity or scope of any 785 Intellectual Property Rights or other rights that might be claimed to 786 pertain to the implementation or use of the technology described in 787 this document or the extent to which any license under such rights 788 might or might not be available; nor does it represent that it has 789 made any independent effort to identify any such rights. Information 790 on the procedures with respect to rights in RFC documents can be 791 found in BCP 78 and BCP 79. 793 Copies of IPR disclosures made to the IETF Secretariat and any 794 assurances of licenses to be made available, or the result of an 795 attempt made to obtain a general license or permission for the use of 796 such proprietary rights by implementers or users of this 797 specification can be obtained from the IETF on-line IPR repository at 798 http://www.ietf.org/ipr. 800 The IETF invites any interested party to bring to its attention any 801 copyrights, patents or patent applications, or other proprietary 802 rights that may cover technology that may be required to implement 803 this standard. Please address the information to the IETF at ietf- 804 ipr@ietf.org. 806 Acknowledgement 808 Funding for the RFC Editor function is currently provided by the 809 Internet Society.