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