idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-scm-08.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.1.a on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 827. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 837. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 844. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 850. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 818), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 39. ** 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. ** 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: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 : ---------------------------------------------------------------------------- No issues found here. 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 (January 2005) is 7040 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) -- 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: 8 errors (**), 0 flaws (~~), 3 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 ECI Telecom 3 B. Ray 4 PESA Switching Systems 5 January 2005 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-08.txt 12 Status of this Memo 14 This document is an Internet-Draft and is subject to all provisions 15 of section 3 of RFC 3667. By submitting this Internet-Draft, each 16 author represents that any applicable patent or other IPR claims of 17 which he or she is aware have been or will be disclosed, and any of 18 which he or she becomes aware will be disclosed, in accordance with 19 RFC 3668. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other documents 28 at any time. It is inappropriate to use Internet-Drafts as 29 reference material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at: 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at: 35 http://www.ietf.org/shadow.html. 37 Copyright Notice 39 Copyright (C) The Internet Society (2004). All Rights Reserved. 41 Abstract 43 This document defines a portion of the Management Information Base 44 (MIB) module for use with network management protocols in the 45 Internet community. In particular, it describes objects used for 46 managing the Line Code Specific parameters of Very High Speed 47 Digital Subscriber Line (VDSL) interfaces using Single Carrier 48 Modulation (SCM) Line Coding. It is an optional extension to the 49 VDSL-LINE-MIB, RFC 3728, which handles line code independent 50 objects. 52 Table of Contents 54 1. The Internet-Standard Management Framework .................... 2 55 2. Overview ...................................................... 2 56 2.1 Relationship of this MIB Module to other MIB Modules .......... 3 57 2.2 Conventions used in the MIB Module ............................ 3 58 2.3 Structure ..................................................... 3 59 2.4 Persistence ................................................... 4 60 3. Conformance and Compliance .................................... 4 61 4. Definitions ................................................... 4 62 5. Acknowledgements .............................................. 13 63 6. Security Considerations ....................................... 14 64 7. IANA Considerations ........................................... 15 65 8. References .................................................... 15 66 8.1 Normative References .......................................... 15 67 8.2 Informative References ........................................ 16 68 Authors' Addresses ............................................ 16 69 Full Copyright Statement ...................................... 17 71 1. The Internet-Standard Management Framework 73 For a detailed overview of the documents that describe the current 74 Internet-Standard Management Framework, please refer to section 7 of 75 RFC 3410 [RFC3410]. 77 Managed objects are accessed via a virtual information store, termed 78 the Management Information Base or MIB. MIB objects are generally 79 accessed through the Simple Network Management Protocol (SNMP). 80 Objects in the MIB are defined using the mechanisms defined in the 81 Structure of Management Information (SMI). This memo specifies a 82 MIB module that is compliant to the SMIv2, which is described in STD 83 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 84 2580 [RFC2580]. 86 2. Overview 88 This document describes an SNMP MIB module for managing the Line 89 Code Dependent, Physical Medium Dependent (PMD) Layer of SCM VDSL 90 Lines. These definitions are based upon the specifications for VDSL 91 as defined in T1E1, European Telecommunications Standards Institute 92 (ETSI), and International Telecommunication Union (ITU) documentation 93 [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. 94 Additionally the protocol-dependent (and line-code dependent) 95 management framework for VDSL lines specified by the Digital 96 Subscriber Line Forum (DSLF) has been taken into consideration 97 [DSLFTR57] and [DSLFWT96]. 99 The MIB module is located in the MIB tree under MIB-2 transmission. 101 The key words "MUST", "MUST NOT", "RECOMMENDED", and "SHOULD" in this 102 document are to be interpreted as described in [RFC2119]. 104 2.1 Relationship of this MIB Module to other MIB Modules 106 The relationship of the VDSL Line MIB module to other MIB modules 107 and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863], 108 is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section 109 outlines the relationship of this VDSL Line Extension MIB to the 110 VDSL-LINE-MIB, RFC 3728 [RFC3728]. 112 2.2 Conventions used in the MIB Module 114 2.2.1 Naming Conventions 116 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 117 B. Vtur -- (VTUR) transceiver at Remote end of line 118 C. Vtu -- One of either Vtuc or Vtur 119 D. Curr -- Current 120 F. Atn -- Attenuation 121 J. LCS -- Line Code Specific 122 K. Max -- Maximum 123 Q. Mgn -- Margin 124 S. PSD -- Power Spectral Density 125 T. Rx -- Receive 126 T. Snr -- Signal to Noise Ratio 127 U. Tx -- Transmit 129 2.3 Structure 131 The SCM VDSL Line Extension MIB contains the following MIB group: 133 o vdslSCMGroup : 135 This group supports MIB objects for defining configuration profiles 136 and for monitoring individual bands of Single Carrier Modulation 137 (SCM) VDSL modems. It contains the following tables: 139 - vdslLineSCMConfProfileTxBandTable 140 - vdslSCMPhysBandTable 142 If the SCM VDSL Line Extension MIB is implemented then all of the 143 objects in this group MUST be implemented. 145 Figure 1, below, displays the relationship of the tables in the 146 vdslSCMGroup to the vdslGroup and to the ifEntry: 148 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 150 vdslLineTableEntry (vdslLineCoding=SCM) 151 ----> vdslPhysTableEntry 1:(0..2) 152 ----> vdslSCMPhysBandTable 1:(0..5) 154 vdslLineConfProfileEntry(vdslLineConfProfileName) 155 ----> vdslLineSCMConfProfileBandTable 1:(0..5) 157 Figure 1: Table Relationships 159 When the object vdslLineCoding is set to SCM, 160 vdslLineConfProfileName is used as the index to 161 vdslLineSCMConfProfileBandTable. The existence of an entry in 162 any of the tables of the vdslSCMGroup is optional. 164 2.4 Persistence 166 All read-create objects defined in this MIB module SHOULD be stored 167 persistently. Following is an exhaustive list of these persistent 168 objects: 170 vdslLineSCMConfProfileBandId 171 vdslLineSCMConfProfileBandUsage 172 vdslLineSCMConfProfileBandCenterFrequency 173 vdslLineSCMConfProfileBandSymbolRate 174 vdslLineSCMConfProfileBandConstellationSize 175 vdslLineSCMConfProfileBandTransmitPSDLevel 176 vdslLineSCMConfProfileBandRowStatus 177 vdslLineSCMPhysBandId 178 vdslLineSCMPhysBandUsage 179 vdslLineSCMPhysBandCurrPSDLevel 180 vdslLineSCMPhysBandCurrSymbolRate 181 vdslLineSCMPhysBandCurrConstellationSize 182 vdslLineSCMPhysBandCurrCenterFrequency 183 vdslLineSCMPhysBandPerformanceBandId 184 vdslLineSCMPhysBandPerformanceBandUsage 185 vdslLineSCMPhysBandPerformanceBandSnrMgn 186 vdslLineSCMPhysBandPerformanceBandAtn 188 Note also that the interface indices in this MIB are maintained 189 persistently. View-based Access Control Model (VACM) data 190 relating to these SHOULD be stored persistently as well [RFC3415]. 192 3. Conformance and Compliance 194 An SCM based VDSL agent does not have to implement this MIB to be 195 compliant with RFC 3728 [RFC3728]. If the SCM VDSL Line Extension 196 MIB is implemented then the following group is mandatory: 198 - vdslSCMGroup 200 4. Definitions 202 VDSL-LINE-EXT-SCM-MIB DEFINITIONS ::= BEGIN 204 IMPORTS 205 MODULE-IDENTITY, 206 OBJECT-TYPE, 207 Integer32, 208 transmission, 209 Unsigned32 FROM SNMPv2-SMI -- [RFC2578] 210 TEXTUAL-CONVENTION, 211 TruthValue, 212 RowStatus FROM SNMPv2-TC -- [RFC2579] 213 MODULE-COMPLIANCE, 214 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 215 ifIndex FROM IF-MIB -- [RFC2863] 216 vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] 218 vdslExtSCMMIB MODULE-IDENTITY 219 LAST-UPDATED "200501160000Z" -- January 16, 2005 220 ORGANIZATION "ADSLMIB Working Group" 221 CONTACT-INFO "WG-email: adslmib@ietf.org 222 Info: https://www1.ietf.org/mailman/listinfo/adslmib 224 Chair: Mike Sneed 225 Sand Channel Systems 226 Postal: P.O. Box 37324 227 Raleigh NC 27627-732 228 Email: sneedmike@hotmail.com 229 Phone: +1 206 600 7022 231 Co-Chair: Bob Ray 232 PESA Switching Systems, Inc. 233 Postal: 330-A Wynn Drive 234 Huntsville, AL 35805 235 USA 236 Email: rray@pesa.com 237 Phone: +1 256 726 9200 ext. 142 239 Co-editor: Menachem Dodge 240 ECI Telecom Ltd. 241 Postal: 30 hasivim St. 242 Petach Tikva 49517, 243 Israel. 244 Email: mbdodge@ieee.org 245 Phone: +972 3 926 8421 247 Co-editor: Bob Ray 248 PESA Switching Systems, Inc. 249 Postal: 330-A Wynn Drive 250 Huntsville, AL 35805 251 USA 252 Email: rray@pesa.com 253 Phone: +1 256 726 9200 ext. 142 254 " 256 DESCRIPTION 257 "The VDSL-LINE-MIB found in RFC 3728 defines objects for 258 the management of a pair of VDSL transceivers at each end of 259 the VDSL line. The VDSL-LINE-MIB configures and monitors the 260 line code independent parameters (TC layer) of the VDSL line. 261 This MIB module is an optional extension of the VDSL-LINE-MIB 262 and defines objects for configuration and monitoring of the 263 line code specific (LCS) elements (PMD layer) for VDSL lines 264 using SCM coding. The objects in this extension MIB MUST NOT 265 be used for VDSL lines using Multiple Carrier Modulation (MCM) 266 line coding. If an object in this extension MIB is referenced 267 by a line which does not use SCM, it has no effect on the 268 operation of that line. 270 Naming Conventions: 271 Vtuc -- (VTUC) transceiver at near (Central) end of line 272 Vtur -- (VTUR) transceiver at Remote end of line 273 Vtu -- One of either Vtuc or Vtur 274 Curr -- Current 275 Atn -- Attenuation 276 LCS -- Line Code Specific 277 Max -- Maximum 278 Mgn -- Margin 279 PSD -- Power Spectral Density 280 Rx -- Receive 281 Snr -- Signal to Noise Ratio 282 Tx -- Transmit 284 Copyright (C) The Internet Society (2004). This version 285 of this MIB module is part of RFC XXXX: see the RFC 286 itself for full legal notices." 287 -- RFC Ed.: replace XXXX with assigned number & remove this note 288 REVISION "200501160000Z" -- January 16, 2005 289 DESCRIPTION "Initial version, published as RFC XXXX." 290 -- RFC Ed.: replace XX with assigned number & remove this note 291 ::= { transmission XX } -- To be assigned by IANA 292 -- RFC Ed.: we suggest to put it under { transmission 227 } because 293 -- this is the first available number, transmission 228 294 -- would be used for the MCM MIB. 295 vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } 296 vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= 297 { vdslLineExtSCMMib 1 } 298 -- 299 -- textual conventions used in this MIB 300 -- 302 VdslSCMBandId ::= TEXTUAL-CONVENTION 303 STATUS current 304 DESCRIPTION 305 "This data type is used as the syntax for the VDSL SCM Band 306 Identity. Attributes with this syntax identify the SCM Band 307 referred to. Specified as an INTEGER, the possible values 309 are: 311 optionalBand (1) -- the optional Band range [25kHz - 138kHz] 312 firstDownstreamBand (2) -- first Downstream Band 313 firstUpstreamBand (3) -- first Upstream Band 314 secondDownstreamBand (4) -- second Downstream Band 315 secondUpstreamBand (5) -- second Upstream Band 316 thirdDownstreamBand (6) -- third Downstream Band 317 thirdUpstreamBand (7) -- third Upstream Band" 319 SYNTAX INTEGER { optionalBand (1), 320 firstDownstreamBand (2), 321 firstUpstreamBand (3), 322 secondDownstreamBand (4), 323 secondUpstreamBand (5), 324 thirdDownstreamBand (6), 325 thirdUpstreamBand(7) } 327 -- 328 -- Single carrier modulation (SCM) configuration profile tables 329 -- 331 vdslLineSCMConfProfileBandTable OBJECT-TYPE 332 SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "This table contains transmit band descriptor configuration 337 information for a VDSL line. Each entry in this table 338 reflects the configuration for one of possibly many bands 339 of a single carrier modulation (SCM) VDSL line. For each 340 profile which is associated with a VDSL line using SCM 341 line coding, five entries in this table will exist, one for 342 each of the five bands. Bands which are not in use will be 343 marked as unused. These entries are defined by a manager 344 and can be used to configure the VDSL line. If an entry in 345 this table is referenced by a line which does not use SCM, 346 it has no effect on the operation of that line." 347 ::= { vdslLineExtSCMMibObjects 1 } 349 vdslLineSCMConfProfileBandEntry OBJECT-TYPE 350 SYNTAX VdslLineSCMConfProfileBandEntry 351 MAX-ACCESS not-accessible 352 STATUS current 353 DESCRIPTION 354 "Each entry consists of a list of parameters that 355 represents the configuration of a single carrier 356 modulation VDSL modem transmit band. 358 A default profile with an index of 'DEFVAL', will 359 always exist and its parameters will be set to vendor 360 specific values, unless otherwise specified in this 361 document. 363 All read-create objects defined in this MIB module SHOULD be 364 stored persistently." 366 INDEX { vdslLineConfProfileName, 367 vdslLineSCMConfProfileBandId } 368 ::= { vdslLineSCMConfProfileBandTable 1 } 370 VdslLineSCMConfProfileBandEntry ::= 371 SEQUENCE 372 { 373 vdslLineSCMConfProfileBandId VdslSCMBandId, 374 vdslLineSCMConfProfileBandInUse TruthValue, 375 vdslLineSCMConfProfileBandCenterFrequency Unsigned32, 376 vdslLineSCMConfProfileBandSymbolRate Unsigned32, 377 vdslLineSCMConfProfileBandConstellationSize Unsigned32, 378 vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, 379 vdslLineSCMConfProfileBandRowStatus RowStatus 380 } 382 vdslLineSCMConfProfileBandId OBJECT-TYPE 383 SYNTAX VdslSCMBandId 384 MAX-ACCESS not-accessible 385 STATUS current 386 DESCRIPTION 387 "The BandId for this entry, which specifies which band 388 is being referred to." 389 ::= { vdslLineSCMConfProfileBandEntry 1 } 391 vdslLineSCMConfProfileBandInUse OBJECT-TYPE 392 SYNTAX TruthValue 393 MAX-ACCESS read-create 394 STATUS current 395 DESCRIPTION 396 "Indicates whether this band is in use. 397 If set to True this band is in use." 398 ::= { vdslLineSCMConfProfileBandEntry 2 } 400 vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE 401 SYNTAX Unsigned32 402 UNITS "Hz" 403 MAX-ACCESS read-create 404 STATUS current 405 DESCRIPTION 406 "Specifies the center frequency in Hz" 407 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 408 ::= { vdslLineSCMConfProfileBandEntry 3 } 410 vdslLineSCMConfProfileBandSymbolRate OBJECT-TYPE 411 SYNTAX Unsigned32 412 UNITS "baud" 413 MAX-ACCESS read-create 414 STATUS current 415 DESCRIPTION 416 "The requested symbol rate in baud." 417 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 418 ::= { vdslLineSCMConfProfileBandEntry 4 } 420 vdslLineSCMConfProfileBandConstellationSize OBJECT-TYPE 421 SYNTAX Unsigned32 (0..16) 422 UNITS "log2" 423 MAX-ACCESS read-create 424 STATUS current 425 DESCRIPTION 426 "Specifies the constellation size." 427 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 428 ::= { vdslLineSCMConfProfileBandEntry 5 } 430 vdslLineSCMConfProfileBandTransmitPSDLevel OBJECT-TYPE 431 SYNTAX Unsigned32 432 UNITS "-0.25 dBm/Hz" 433 MAX-ACCESS read-create 434 STATUS current 435 DESCRIPTION 436 "The requested transmit power spectral density for the VDSL 437 modem. The Actual value in -0.25 dBm/Hz." 438 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 439 ::= { vdslLineSCMConfProfileBandEntry 6 } 441 vdslLineSCMConfProfileBandRowStatus OBJECT-TYPE 442 SYNTAX RowStatus 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "This object is used to create a new row or modify or 447 delete an existing row in this table. 449 A profile activated by setting this object to `active'. 450 When `active' is set, the system will validate the profile. 452 None of the columns in this row may be modified while the 453 row is in the 'active' state. 455 Before a profile can be deleted or taken out of 456 service, (by setting this object to `destroy' or 457 `notInService') it must be first unreferenced 458 from all associated lines." 459 ::= { vdslLineSCMConfProfileBandEntry 7 } 461 -- 462 -- SCM physical band 463 -- 465 vdslLineSCMPhysBandTable OBJECT-TYPE 466 SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "This table provides one row for each SCM Vtu band. This 471 table is read only as it reflects the current physical 472 parameters of each band. For each ifIndex which is 473 associated with a VDSL line using SCM line coding, five 474 entries in this table will exist, one for each of the 475 five bands. Bands which are not in use will be marked 476 as unused." 477 ::= { vdslLineExtSCMMibObjects 2 } 479 vdslLineSCMPhysBandEntry OBJECT-TYPE 480 SYNTAX VdslLineSCMPhysBandEntry 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "An entry in the vdslLineSCMPhysBandTable." 485 INDEX { ifIndex, 486 vdslLineSCMPhysBandId } 487 ::= { vdslLineSCMPhysBandTable 1 } 489 VdslLineSCMPhysBandEntry ::= 490 SEQUENCE 491 { 492 vdslLineSCMPhysBandId VdslSCMBandId, 493 vdslLineSCMPhysBandInUse TruthValue, 494 vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, 495 vdslLineSCMPhysBandCurrSymbolRate Unsigned32, 496 vdslLineSCMPhysBandCurrConstellationSize Unsigned32, 497 vdslLineSCMPhysBandCurrPSDLevel Unsigned32, 498 vdslLineSCMPhysBandCurrSnrMgn Integer32, 499 vdslLineSCMPhysBandCurrAtn Unsigned32 500 } 502 vdslLineSCMPhysBandId OBJECT-TYPE 503 SYNTAX VdslSCMBandId 504 MAX-ACCESS not-accessible 505 STATUS current 506 DESCRIPTION 507 "The BandId for this entry, which specifies which band 508 is being referred to." 509 ::= { vdslLineSCMPhysBandEntry 1 } 511 vdslLineSCMPhysBandInUse OBJECT-TYPE 512 SYNTAX TruthValue 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "Indicates whether this band is in use. 517 If set to True this band is in use." 518 ::= { vdslLineSCMPhysBandEntry 2 } 520 vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE 521 SYNTAX Unsigned32 522 UNITS "Hz" 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "The current center frequency in Hz for this band." 527 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 528 ::= { vdslLineSCMPhysBandEntry 3 } 530 vdslLineSCMPhysBandCurrSymbolRate OBJECT-TYPE 531 SYNTAX Unsigned32 532 UNITS "baud" 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "The current value of the symbol rate in baud for this 537 band." 538 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 539 ::= { vdslLineSCMPhysBandEntry 4 } 541 vdslLineSCMPhysBandCurrConstellationSize OBJECT-TYPE 542 SYNTAX Unsigned32 (0..16) 543 UNITS "log2" 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The current constellation size on this band." 548 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 549 ::= { vdslLineSCMPhysBandEntry 5 } 551 vdslLineSCMPhysBandCurrPSDLevel OBJECT-TYPE 552 SYNTAX Unsigned32 553 UNITS "- 0.25 dBm/Hz" 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The transmit power spectral density for the 558 VDSL modem." 559 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 560 ::= { vdslLineSCMPhysBandEntry 6 } 562 vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE 563 SYNTAX Integer32 564 UNITS "0.25 dB" 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "Noise margin as seen by this Vtu and band with respect 569 to its received signal in 0.25 dB." 570 ::= { vdslLineSCMPhysBandEntry 7 } 572 vdslLineSCMPhysBandCurrAtn OBJECT-TYPE 573 SYNTAX Unsigned32 (0..255) 574 UNITS "0.25 dB" 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "Measured difference in the total power transmitted by 579 the peer Vtu on this band and the total power received 580 by this Vtu on this band in 0.25 dB." 581 ::= { vdslLineSCMPhysBandEntry 8 } 583 -- conformance information 584 vdslLineExtSCMConformance OBJECT IDENTIFIER ::= 585 { vdslLineExtSCMMib 2 } 586 vdslLineExtSCMGroups OBJECT IDENTIFIER ::= 587 { vdslLineExtSCMConformance 1 } 588 vdslLineExtSCMCompliances OBJECT IDENTIFIER ::= 589 { vdslLineExtSCMConformance 2 } 591 vdslLineExtSCMMibCompliance MODULE-COMPLIANCE 592 STATUS current 593 DESCRIPTION 594 "The compliance statement for SNMP entities which 595 manage VDSL interfaces." 597 MODULE -- this module 599 MANDATORY-GROUPS 600 { 601 vdslLineExtSCMGroup 602 } 604 ::= { vdslLineExtSCMCompliances 1 } 606 -- units of conformance 608 vdslLineExtSCMGroup OBJECT-GROUP 609 OBJECTS 610 { 611 vdslLineSCMConfProfileBandInUse, 612 vdslLineSCMConfProfileBandTransmitPSDLevel, 613 vdslLineSCMConfProfileBandSymbolRate, 614 vdslLineSCMConfProfileBandConstellationSize, 615 vdslLineSCMConfProfileBandCenterFrequency, 616 vdslLineSCMConfProfileBandRowStatus, 617 vdslLineSCMPhysBandInUse, 618 vdslLineSCMPhysBandCurrPSDLevel, 619 vdslLineSCMPhysBandCurrSymbolRate, 620 vdslLineSCMPhysBandCurrConstellationSize, 621 vdslLineSCMPhysBandCurrCenterFrequency, 622 vdslLineSCMPhysBandCurrSnrMgn, 623 vdslLineSCMPhysBandCurrAtn 625 } 627 STATUS current 628 DESCRIPTION 629 "A collection of objects providing configuration 630 information for a VDSL line based upon single carrier 631 modulation modem." 632 ::= { vdslLineExtSCMGroups 1 } 634 END 636 5. Acknowledgments 638 This document contains many definitions taken from an earlier 639 draft of the VDSL MIB [RFC3728]. As such any credit for the text 640 found within should be fully attributed to the authors of that 641 document. 643 6. Security Considerations 645 There are a number of management objects defined in this MIB module 646 with a MAX-ACCESS clause of read-create. Such objects may be 647 considered sensitive or vulnerable in some network environments. 648 The support for SET operations in a non-secure environment without 649 proper protection can have a negative effect on network operations. 650 These are the tables and objects and their sensitivity/vulnerability: 652 vdslLineSCMConfProfileBandTable 653 vdslLineSCMConfProfileBandInUse, 654 vdslLineSCMConfProfileBandTransmitPSDLevel, 655 vdslLineSCMConfProfileBandSymbolRate, 656 vdslLineSCMConfProfileBandConstellationSize, 657 vdslLineSCMConfProfileBandCenterFrequency, 658 vdslLineSCMConfProfileBandRowStatus 660 VDSL layer connectivity from the Vtur will permit the subscriber to 661 manipulate both the VDSL link directly and the VDSL embedded 662 operations channel (EOC) for their own loop. For example, unchecked 663 or unfiltered fluctuations initiated by the subscriber could generate 664 sufficient notifications to potentially overwhelm either the 665 management interface to the network or the element manager. 667 Additionally, allowing write access to configuration data may allow 668 an end-user to increase their service levels or affect other 669 end-users in either a positive or negative manner. For this reason, 670 the tables and objects listed above should be considered to contain 671 sensitive information. 673 Some of the readable objects in this MIB module (i.e., objects with a 674 MAX-ACCESS other than not-accessible) may be considered sensitive or 675 vulnerable in some network environments. It is thus important to 676 control even GET and/or NOTIFY access to these objects and possibly 677 to even encrypt the values of these objects when sending them over 678 the network via SNMP. These are the tables and objects and their 679 sensitivity/vulnerability: 681 vdslLineSCMPhysBandInUse, 682 vdslLineSCMPhysBandCurrPSDLevel, 683 vdslLineSCMPhysBandCurrSymbolRate, 684 vdslLineSCMPhysBandCurrConstellationSize, 685 vdslLineSCMPhysBandCurrCenterFrequency, 686 vdslLineSCMPhysBandCurrSnrMgn, 687 vdslLineSCMPhysBandCurrAtn 689 Read access of the physical band parameters may provide knowledge 690 to an end-user that would allow malicious behavior, for example 691 the application of an intentional interference on one or all of 692 the physical bands in use. 694 SNMP versions prior to SNMPv3 did not include adequate security. 695 Even if the network itself is secure (for example by using IPSec), 696 even then, there is no control as to who on the secure network is 697 allowed to access and GET/SET (read/change/create/delete) the objects 698 in this MIB module. 700 It is RECOMMENDED that implementers consider the security features 701 as provided by the SNMPv3 framework (see [RFC3410], section 8), 702 including full support for the SNMPv3 cryptographic mechanisms (for 703 authentication and privacy). 705 Further, deployment of SNMP versions prior to SNMPv3 is NOT 706 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 707 enable cryptographic security. It is then a customer/operator 708 responsibility to ensure that the SNMP entity giving access to an 709 instance of a MIB module is properly configured to give access to 710 the objects only to those principals (users) that have legitimate 711 rights to indeed GET or SET (change/create/delete) them. 713 7. IANA Considerations 714 The IANA is kindly requested to assign the value of the 715 MODULE-IDENTITY. The authors suggest transmission 227, 716 see section 4. 718 8. References 720 8.1. Normative References 722 [DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management", 723 February 2003. 725 [DSLFWT96] DSL Forum WT-096, "SCM Specific Managed Objects In 726 VDSL Network Elements". 728 [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing 729 (TM); Access transmission systems on metallic access 730 cables; Very high speed Digital Subscriber Line (VDSL); 731 Part 1: Functional requirements", October 1999. 733 [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing 734 (TM); Access transmission systems on metallic access 735 cables; Very high speed Digital Subscriber Line (VDSL); 736 Part 1: Transceiver specification", February 2001. 738 [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line 739 foundation", November 2001. 741 [ITU9971] ITU-T G.997.1, "Physical layer management for Digital 742 Subscriber Line (DSL) Transceivers", July 1999. 744 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 745 Requirement Levels", BCP 14, RFC 2119, March 1997. 747 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 748 Rose, M. and S. Waldbusser, "Structure of Management 749 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 750 1999. 752 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 753 Rose, M. and S. Waldbusser, "Textual Conventions for 754 SMIv2", STD 58, RFC 2579, April 1999. 756 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 757 Rose, M. and S. Waldbusser, "Conformance Statements for 758 SMIv2", STD 58, RFC 2580, April 1999. 760 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 761 MIB", RFC 2863, June 2000. 763 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 764 Very High Speed Digital Subscriber Lines (VDSL)", RFC 765 3728, February 2004. 767 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 768 Subscriber Line (VDSL) Metallic Interface, Part 1: 769 Functional Requirements and Common Specification", 770 February 2001. 772 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 773 Technical Specification for a Single-Carrier Modulation 774 (SCM) Transceiver", November 2001. 776 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 777 Technical Specification for a Multi-Carrier Modulation 778 (MCM) Transceiver", November 2000. 780 8.2. Informative References 782 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 783 Access Control Model (VACM) for the Simple Network 784 Management Protocol (SNMP)", RFC 3415, December 2002. 786 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 787 "Introduction and Applicability Statements for 788 Internet-Standard Management Framework", RFC 3410, 789 December 2002. 791 Authors' Addresses 793 Menachem Dodge 794 ECI Telecom Ltd. 795 30 Hasivim St. 797 Petach Tikva 49517, 798 Israel. 800 Phone: +972 3 926 8421 801 Fax: +972 3 928 7342 802 Email: mbdodge@ieee.org 804 Bob Ray 805 PESA Switching Systems, Inc. 806 330-A Wynn Drive 807 Huntsville, AL 35805 808 USA 810 Phone: +1 256 726 9200 ext. 142 811 Fax: +1 256 726 9271 812 EMail: rray@pesa.com 814 Full Copyright Statement 816 Copyright (C) The Internet Society (2004). This document is subject 817 to the rights, licenses and restrictions contained in BCP 78 and 818 except as set forth therein, the authors retain all their rights. 820 This document and the information contained herein are provided 821 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 822 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 823 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 824 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 825 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 826 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 827 PARTICULAR PURPOSE. 829 Intellectual Property 830 The IETF takes no position regarding the validity or scope of any 831 Intellectual Property Rights or other rights that might be claimed to 832 pertain to the implementation or use of the technology described in 833 this document or the extent to which any license under such rights 834 might or might not be available; nor does it represent that it has 835 made any independent effort to identify any such rights. Information 836 on the procedures with respect to rights in RFC documents can be 837 found in BCP 78 and BCP 79. 839 Copies of IPR disclosures made to the IETF Secretariat and any 840 assurances of licenses to be made available, or the result of an 841 attempt made to obtain a general license or permission for the use of 842 such proprietary rights by implementers or users of this 843 specification can be obtained from the IETF on-line IPR repository at 844 http://www.ietf.org/ipr. 846 The IETF invites any interested party to bring to its attention any 847 copyrights, patents or patent applications, or other proprietary 848 rights that may cover technology that may be required to implement 849 this standard. Please address the information to the IETF at 850 ietf-ipr@ietf.org. 852 Acknowledgement 854 Funding for the RFC Editor function is currently provided by the 855 Internet Society.