idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-scm-06.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 833. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 843. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 850. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 856. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 824), 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 (October 2004) is 7133 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'DSLFTR057' is mentioned on line 97, but not defined == Missing Reference: 'DSLFWT096' is mentioned on line 97, but not defined == Unused Reference: 'DSLFTR57' is defined on line 724, but no explicit reference was found in the text == Unused Reference: 'DSLFWT96' is defined on line 727, but no explicit reference was found in the text == Unused Reference: 'RFC2856' is defined on line 762, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFTR57' -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFWT96' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2701' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2702' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9931' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9971' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' Summary: 8 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 October 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-06.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 [DSLFTR057] and [DSLFWT096]. 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 montioring 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 Unsigned32 FROM SNMPv2-SMI -- [RFC2578] 209 RowStatus FROM SNMPv2-TC -- [RFC2579] 210 MODULE-COMPLIANCE, 211 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 212 ifIndex FROM IF-MIB -- [RFC2863] 213 vdslMIB, 214 vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] 216 vdslExtSCMMIB MODULE-IDENTITY 217 LAST-UPDATED "200410130000Z" -- October 13, 2004 218 ORGANIZATION "ADSLMIB Working Group" 219 CONTACT-INFO "WG-email: adslmib@ietf.org 220 Info: https://www1.ietf.org/mailman/listinfo/adslmib 222 Chair: Mike Sneed 223 Sand Channel Systems 224 Postal: P.O. Box 37324 225 Raleigh NC 27627-732 226 Email: sneedmike@hotmail.com 227 Phone: +1 206 600 7022 229 co-editor: Menachem Dodge 230 Infineon Technologies Savan Ltd. 231 6 Hagavish St. 232 Postal: Poleg Industrial Area, 233 Netanya 42504, 234 Israel. 235 Email: mbdodge@ieee.org 236 Phone: +972 9 892 4116 238 Co-editor: Bob Ray 239 PESA Switching Systems, Inc. 240 Postal: 330-A Wynn Drive 241 Huntsville, AL 35805 242 USA 243 Email: rray@pesa.com 244 Phone: +1 256 726 9200 ext. 142 245 " 246 DESCRIPTION 247 "The VDSL-LINE-MIB found in RFC 3728 defines objects for 248 the management of a pair of VDSL transceivers at each end of 249 the VDSL line. The VDSL-LINE-MIB configures and monitors the 250 line code independent parameters (TC layer) of the VDSL line. 251 This MIB module is an optional extension of the VDSL-LINE-MIB 252 and defines objects for configuration and monitoring of the 253 line code specific (LCS) elements (PMD layer) for VDSL lines 254 using SCM coding. The objects in this extension MIB MUST NOT 255 be used for VDSL lines using Multiple Carrier Modulation (MCM) 256 line coding. If an object in this extension MIB is referenced 257 by a line which does not use SCM, it has no effect on the 258 operation of that line. 260 Naming Conventions: 261 Vtuc -- (VTUC) transceiver at near (Central) end of line 262 Vtur -- (VTUR) transceiver at Remote end of line 263 Vtu -- One of either Vtuc or Vtur 264 Curr -- Current 265 Atn -- Attenuation 266 LCS -- Line Code Specific 267 Max -- Maximum 268 Mgn -- Margin 269 PSD -- Power Spectral Density 270 Rx -- Receive 271 Snr -- Signal to Noise Ratio 272 Tx -- Transmit 274 Copyright (C) The Internet Society (2004). This version 275 of this MIB module is part of RFC XXXX: see the RFC 276 itself for full legal notices." 277 -- RFC Ed.: replace XXXX with assigned number & remove this note 278 REVISION "200410130000Z" -- October 13, 2004 279 DESCRIPTION "Initial version, published as RFC XXXX." 280 -- RFC Ed.: replace XX with assigned number & remove this note 281 ::= { transmission XX } -- To be assigned by IANA 282 -- RFC Ed.: we suggest to put it under { transmission 98 } because 283 -- transmission 97 is the VDSL-LINE-MIB, transmission 98 284 -- would be this SCM MIB and transmission 99 the MCM MIB. 286 vdslLineExtSCMMib OBJECT IDENTIFIER ::= { vdslExtSCMMIB 1 } 287 vdslLineExtSCMMibObjects OBJECT IDENTIFIER ::= 288 { vdslLineExtSCMMib 1 } 290 -- 291 -- textual conventions used in this MIB 292 -- 294 VdslSCMBandId ::= TEXTUAL-CONVENTION 295 STATUS current 296 DESCRIPTION 297 "This data type is used as the syntax for the VDSL SCM Band 298 Identity. Attributes with this syntax identify the SCM Band 299 referred to. Specified as an INTEGER, the possible values 300 are: 302 optionalBand (1) -- the optional Band range [25kHz - 138kHz] 303 firstDownstreamBand (2) -- first Downstream Band 304 firstUpstreamBand (3) -- first Upstream Band 305 secondDownstreamBand (4) -- second Downstream Band 306 secondUpstreamBand (5) -- second Upstream Band 307 thirdDownstreamBand (6) -- third Downstream Band 308 thirdUpstreamBand (7) -- third Upstream Band" 310 SYNTAX INTEGER { optionalBand (1), 311 firstDownstreamBand (2), 312 firstUpstreamBand (3), 313 secondDownstreamBand (4), 314 secondUpstreamBand (5), 315 thirdDownstreamBand (6), 316 thirdUpstreamBand (7) } 318 VdslSCMBandUsage ::= TEXTUAL-CONVENTION 319 STATUS current 320 DESCRIPTION 321 "This data type is used to indicate whether the SCM Band 322 is in use or not. The two possible values are: 323 unUsed (1), 324 inUse (2)" 326 SYNTAX INTEGER { 327 unUsed (1), 328 inUse (2) } 330 -- 331 -- Single carrier modulation (SCM) configuration profile tables 332 -- 334 vdslLineSCMConfProfileBandTable OBJECT-TYPE 335 SYNTAX SEQUENCE OF VdslLineSCMConfProfileBandEntry 336 MAX-ACCESS not-accessible 337 STATUS current 338 DESCRIPTION 339 "This table contains transmit band descriptor configuration 340 information for a VDSL line. Each entry in this table 341 reflects the configuration for one of possibly many bands 342 of a single carrier modulation (SCM) VDSL line. For each 343 profile which is associated with a VDSL line using SCM 344 line coding, five entries in this table will exist, one for 345 each of the five bands. Bands which are not in use will be 346 marked as unused. These entries are defined by a manager 347 and can be used to configure the VDSL line. If an entry in 348 this table is referenced by a line which does not use SCM, 349 it has no effect on the operation of that line." 350 ::= { vdslLineExtSCMMibObjects 1 } 352 vdslLineSCMConfProfileBandEntry OBJECT-TYPE 353 SYNTAX VdslLineSCMConfProfileBandEntry 354 MAX-ACCESS not-accessible 355 STATUS current 356 DESCRIPTION 357 "Each entry consists of a list of parameters that 358 represents the configuration of a single carrier 359 modulation VDSL modem transmit band. 361 A default profile with an index of 'DEFVAL', will 362 always exist and its parameters will be set to vendor 363 specific values, unless otherwise specified in this 364 document. 366 All read-create objects defined in this MIB module SHOULD be 367 stored persistently." 369 INDEX { vdslLineConfProfileName, 370 vdslLineSCMConfProfileBandId } 371 ::= { vdslLineSCMConfProfileBandTable 1 } 373 VdslLineSCMConfProfileBandEntry ::= 374 SEQUENCE 375 { 376 vdslLineSCMConfProfileBandId VdslSCMBandId, 377 vdslLineSCMConfProfileBandUsage VdslSCMBandUsage, 378 vdslLineSCMConfProfileBandCenterFrequency Unsigned32, 379 vdslLineSCMConfProfileBandSymbolRate Unsigned32, 380 vdslLineSCMConfProfileBandConstellationSize Unsigned32, 381 vdslLineSCMConfProfileBandTransmitPSDLevel Unsigned32, 382 vdslLineSCMConfProfileBandRowStatus RowStatus 383 } 385 vdslLineSCMConfProfileBandId OBJECT-TYPE 386 SYNTAX VdslSCMBandId 387 MAX-ACCESS not-accessible 388 STATUS current 389 DESCRIPTION 390 "The BandId for this entry, which specifies which band 391 is being referred to. Specified as an INTEGER, the 392 possible values are: 393 optionalBand (1), firstDownstreamBand (2), 394 firstUpstreamBand (3), secondDownstreamBand (4), 395 secondUpstreamBand (5), thirdDownstreamBand (6), 396 thirdUpstreamBand (7)" 397 ::= { vdslLineSCMConfProfileBandEntry 1 } 399 vdslLineSCMConfProfileBandUsage OBJECT-TYPE 400 SYNTAX VdslSCMBandUsage 401 MAX-ACCESS read-create 402 STATUS current 403 DESCRIPTION 404 "Indicates whether this band is in use. 405 Specified as an INTEGER, the possible values are: 406 unUsed(1), 407 inUse(2)" 408 ::= { vdslLineSCMConfProfileBandEntry 2 } 410 vdslLineSCMConfProfileBandCenterFrequency OBJECT-TYPE 411 SYNTAX Unsigned32 412 UNITS "Hz" 413 MAX-ACCESS read-create 414 STATUS current 415 DESCRIPTION 416 "Specifies the center frequency in Hz" 417 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 418 ::= { vdslLineSCMConfProfileBandEntry 3 } 420 vdslLineSCMConfProfileBandSymbolRate OBJECT-TYPE 421 SYNTAX Unsigned32 422 UNITS "baud" 423 MAX-ACCESS read-create 424 STATUS current 425 DESCRIPTION 426 "The requested symbol rate in baud." 427 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 428 ::= { vdslLineSCMConfProfileBandEntry 4 } 430 vdslLineSCMConfProfileBandConstellationSize OBJECT-TYPE 431 SYNTAX Unsigned32 (0..16) 432 UNITS "log2" 433 MAX-ACCESS read-create 434 STATUS current 435 DESCRIPTION 436 "Specifies the constellation size." 437 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 438 ::= { vdslLineSCMConfProfileBandEntry 5 } 440 vdslLineSCMConfProfileBandTransmitPSDLevel OBJECT-TYPE 441 SYNTAX Unsigned32 442 UNITS "-0.25 dBm/Hz" 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "The requested transmit power spectral density for the VDSL 447 modem. The Actual value in -0.25 dBm/Hz." 448 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 449 ::= { vdslLineSCMConfProfileBandEntry 6 } 451 vdslLineSCMConfProfileBandRowStatus OBJECT-TYPE 452 SYNTAX RowStatus 453 MAX-ACCESS read-create 454 STATUS current 455 DESCRIPTION 456 "This object is used to create a new row or modify or 457 delete an existing row in this table. 459 A profile activated by setting this object to `active'. 460 When `active' is set, the system will validate the profile. 462 None of the columns in this row may be modified while the 463 row is in the 'active' state. 465 Before a profile can be deleted or taken out of 466 service, (by setting this object to `destroy' or 467 `notInService') it must be first unreferenced 468 from all associated lines." 469 ::= { vdslLineSCMConfProfileBandEntry 7 } 471 -- 472 -- SCM physical band 473 -- 475 vdslLineSCMPhysBandTable OBJECT-TYPE 476 SYNTAX SEQUENCE OF VdslLineSCMPhysBandEntry 477 MAX-ACCESS not-accessible 478 STATUS current 479 DESCRIPTION 480 "This table provides one row for each SCM Vtu band. This 481 table is read only as it reflects the current physical 482 parameters of each band. For each ifIndex which is 483 associated with a VDSL line using SCM line coding, five 484 entries in this table will exist, one for each of the 485 five bands. Bands which are not in use will be marked 486 as unused." 487 ::= { vdslLineExtSCMMibObjects 2 } 489 vdslLineSCMPhysBandEntry OBJECT-TYPE 490 SYNTAX VdslLineSCMPhysBandEntry 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION 494 "An entry in the vdslLineSCMPhysBandTable." 495 INDEX { ifIndex, 496 vdslLineSCMPhysBandId } 497 ::= { vdslLineSCMPhysBandTable 1 } 499 VdslLineSCMPhysBandEntry ::= 500 SEQUENCE 501 { 502 vdslLineSCMPhysBandId VdslSCMBandId, 503 vdslLineSCMPhysBandUsage VdslSCMBandUsage, 504 vdslLineSCMPhysBandCurrCenterFrequency Unsigned32, 505 vdslLineSCMPhysBandCurrSymbolRate Unsigned32, 507 vdslLineSCMPhysBandCurrConstellationSize Unsigned32, 508 vdslLineSCMPhysBandCurrPSDLevel Unsigned32, 509 vdslLineSCMPhysBandCurrSnrMgn Integer32, 510 vdslLineSCMPhysBandCurrAtn Unsigned32 511 } 513 vdslLineSCMPhysBandId OBJECT-TYPE 514 SYNTAX VdslSCMBandId 515 MAX-ACCESS read-only 516 STATUS current 517 DESCRIPTION 518 "The BandId for this entry, which specifies which band 519 is being referred to. Specified as an Unsigned32, the 520 possible values are: 521 optionalBand (1), firstDownstreamBand (2), 522 firstUpstreamBand (3), secondDownstreamBand (4), 523 secondUpstreamBand (5), thirdDownstreamBand (6), 524 thirdUpstreamBand (7)" 525 ::= { vdslLineSCMPhysBandEntry 1 } 527 vdslLineSCMPhysBandUsage OBJECT-TYPE 528 SYNTAX VdslSCMBandUsage 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "Indicates whether this band is in use. 533 Specified as an Unsigned32, the two 534 possible values are: 535 Unused(1), 536 InUse(2)" 537 ::= { vdslLineSCMPhysBandEntry 2 } 539 vdslLineSCMPhysBandCurrCenterFrequency OBJECT-TYPE 540 SYNTAX Unsigned32 541 UNITS "Hz" 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The current center frequency in Hz for this band." 546 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 547 ::= { vdslLineSCMPhysBandEntry 3 } 549 vdslLineSCMPhysBandCurrSymbolRate OBJECT-TYPE 550 SYNTAX Unsigned32 551 UNITS "baud" 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "The current value of the symbol rate in baud for this 556 band." 557 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 558 ::= { vdslLineSCMPhysBandEntry 4 } 560 vdslLineSCMPhysBandCurrConstellationSize OBJECT-TYPE 561 SYNTAX Unsigned32 (0..16) 562 UNITS "log2" 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The current constellation size on this band." 567 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 568 ::= { vdslLineSCMPhysBandEntry 5 } 570 vdslLineSCMPhysBandCurrPSDLevel OBJECT-TYPE 571 SYNTAX Unsigned32 572 UNITS "- 0.25 dBm/Hz" 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The transmit power spectral density for the 577 VDSL modem." 578 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 579 ::= { vdslLineSCMPhysBandEntry 6 } 581 vdslLineSCMPhysBandCurrSnrMgn OBJECT-TYPE 582 SYNTAX Integer32 583 UNITS "0.25 dBm" 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "Noise margin as seen by this Vtu and band with respect 588 to its received signal in 0.25 dB." 589 ::= { vdslLineSCMPhysBandEntry 7 } 591 vdslLineSCMPhysBandCurrAtn OBJECT-TYPE 592 SYNTAX Unsigned32 (0..255) 593 UNITS "0.25 dBm" 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "Measured difference in the total power transmitted by 598 the peer Vtu on this band and the total power received 599 by this Vtu on this band in 0.25 dB." 600 ::= { vdslLineSCMPhysBandEntry 8 } 602 -- conformance information 603 vdslLineExtSCMConformance OBJECT IDENTIFIER ::= 604 { vdslLineExtSCMMib 2 } 605 vdslLineExtSCMGroups OBJECT IDENTIFIER ::= 606 { vdslLineExtSCMConformance 1 } 607 vdslLineExtSCMCompliances OBJECT IDENTIFIER ::= 608 { vdslLineExtSCMConformance 2 } 610 vdslLineExtSCMMibCompliance MODULE-COMPLIANCE 611 STATUS current 612 DESCRIPTION 613 "The compliance statement for SNMP entities which 614 manage VDSL interfaces." 616 MODULE -- this module 618 MANDATORY-GROUPS 619 { 620 vdslLineExtSCMGroup 621 } 623 ::= { vdslLineExtSCMCompliances 1 } 625 -- units of conformance 627 vdslLineExtSCMGroup OBJECT-GROUP 628 OBJECTS 629 { 630 vdslLineSCMConfProfileBandId, 631 vdslLineSCMConfProfileBandUsage, 632 vdslLineSCMConfProfileBandTransmitPSDLevel, 633 vdslLineSCMConfProfileBandSymbolRate, 634 vdslLineSCMConfProfileBandConstellationSize, 635 vdslLineSCMConfProfileBandCenterFrequency, 636 vdslLineSCMConfProfileBandRowStatus, 637 vdslLineSCMPhysBandId, 638 vdslLineSCMPhysBandUsage, 639 vdslLineSCMPhysBandCurrPSDLevel, 640 vdslLineSCMPhysBandCurrSymbolRate, 641 vdslLineSCMPhysBandCurrConstellationSize, 642 vdslLineSCMPhysBandCurrCenterFrequency, 643 vdslLineSCMPhysBandCurrSnrMgn, 644 vdslLineSCMPhysBandCurrAtn 646 } 647 STATUS current 648 DESCRIPTION 649 "A collection of objects providing configuration 650 information for a VDSL line based upon single carrier 651 modulation modem." 652 ::= { vdslLineExtSCMGroups 1 } 654 END 656 5. Acknowledgments 658 This document contains many definitions taken from 659 draft-ietf-adslmib-vdsl-07.txt. As such any credit for the text 660 found within should be full attributed to the authors of that 661 document. 663 6. Security Considerations 665 There are a number of management objects defined in this MIB module 666 with a MAX-ACCESS clause of read-create. Such objects may be 667 considered sensitive or vulnerable in some network environments. 668 The support for SET operations in a non-secure environment without 669 proper protection can have a negative effect on network operations. 671 Some of the readable objects in this MIB module (i.e., objects with a 672 MAX-ACCESS other than not-accessible) may be considered sensitive or 673 vulnerable in some network environments. 675 VDSL layer connectivity from the Vtur will permit the subscriber to 676 manipulate both the VDSL link directly and the VDSL embedded 677 operations channel (EOC) for their own loop. For example, unchecked 678 or unfiltered fluctuations initiated by the subscriber could generate 679 sufficient notifications to potentially overwhelm either the 680 management interface to the network or the element manager. 682 Additionally, allowing write access to configuration data may allow 683 an end-user to increase their service levels or affect other 684 end-users in either a positive or negative manner. For this reason, 685 the following tables should be considered to contain sensitive 686 information: 688 - vdslLineSCMConfProfileTxBandTable 689 - vdslSCMPhysBandTable 691 It is thus important to control even GET access to the objects within 692 these tables and possibly to even encrypt the values of these objects 693 when sending them over the network via SNMP. Not all versions of 694 SNMP provide features for such a secure environment. 696 SNMP versions prior to SNMPv3 did not include adequate security. 697 Even if the network itself is secure (for example by using IPSec), 698 even then, there is no control as to who on the secure network is 699 allowed to access and GET/SET (read/change/create/delete) the objects 700 in this MIB module. 702 It is RECOMMENDED that implementers consider the security features 703 as provided by the SNMPv3 framework (see [RFC3410], section 8), 704 including full support for the SNMPv3 cryptographic mechanisms (for 705 authentication and privacy). 707 Further, deployment of SNMP versions prior to SNMPv3 is NOT 708 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 709 enable cryptographic security. It is then a customer/operator 710 responsibility to ensure that the SNMP entity giving access to an 711 instance of a MIB module which utilizes the textual conventions 712 defined in this MIB module is properly configured to give access to 713 the objects only to those principals (users) that have legitimate 714 rights to indeed GET or SET (change/create/delete) them. 716 7. IANA Considerations 717 The IANA is kindly requested to assign the value of the 718 MODULE-IDENTITY. The authors suggest transmission 98, see section 4. 720 8. References 722 8.1. Normative References 724 [DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management", 725 February 2003. 727 [DSLFWT96] DSL Forum WT-096, "SCM Specific Managed Objects In 728 VDSL Network Elements". 730 [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing 731 (TM); Access transmission systems on metallic access 732 cables; Very high speed Digital Subscriber Line (VDSL); 733 Part 1: Functional requirements", October 1999. 735 [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing 736 (TM); Access transmission systems on metallic access 737 cables; Very high speed Digital Subscriber Line (VDSL); 738 Part 1: Transceiver specification", February 2001. 740 [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line 741 foundation", November 2001. 743 [ITU9971] ITU-T G.997.1, "Physical layer management for Digital 744 Subscriber Line (DSL) Transceivers", July 1999. 746 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 747 Requirement Levels", BCP 14, RFC 2119, March 1997. 749 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 750 Rose, M. and S. Waldbusser, "Structure of Management 751 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 752 1999. 754 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 755 Rose, M. and S. Waldbusser, "Textual Conventions for 756 SMIv2", STD 58, RFC 2579, April 1999. 758 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 759 Rose, M. and S. Waldbusser, "Conformance Statements for 760 SMIv2", STD 58, RFC 2580, April 1999. 762 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 763 Conventions for Additional High Capacity Data Types", 764 RFC 2856, June 2000. 766 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 767 MIB", RFC 2863, June 2000. 769 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 770 Very High Speed Digital Subscriber Lines (VDSL)", RFC 771 3728, February 2004. 773 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 774 Subscriber Line (VDSL) Metallic Interface, Part 1: 775 Functional Requirements and Common Specification", 776 February 2001. 778 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 779 Technical Specification for a Single-Carrier Modulation 780 (SCM) Transceiver", November 2001. 782 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 783 Technical Specification for a Multi-Carrier Modulation 784 (MCM) Transceiver", November 2000. 786 8.2. Informative References 788 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 789 Access Control Model (VACM) for the Simple Network 790 Management Protocol (SNMP)", RFC 3415, December 2002. 792 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 793 "Introduction and Applicability Statements for 794 Internet-Standard Management Framework", RFC 3410, 795 December 2002. 797 Authors' Addresses 799 Menachem Dodge 800 Infineon Technologies Savan Ltd. 801 6 Hagavish St. 802 Poleg Industrial Area, 803 Netanya 42504, 804 Israel. 806 Phone: +972 9 892 4116 807 Fax: +972 9 865 8756 808 Email: mbdodge@ieee.org 810 Bob Ray 811 PESA Switching Systems, Inc. 812 330-A Wynn Drive 813 Huntsville, AL 35805 814 USA 816 Phone: +1 256 726 9200 ext. 142 817 Fax: +1 256 726 9271 818 EMail: rray@pesa.com 820 Full Copyright Statement 822 Copyright (C) The Internet Society (2004). This document is subject 823 to the rights, licenses and restrictions contained in BCP 78 and 824 except as set forth therein, the authors retain all their rights. 826 This document and the information contained herein are provided 827 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 828 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 829 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 830 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 831 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 832 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 833 PARTICULAR PURPOSE. 835 Intellectual Property 836 The IETF takes no position regarding the validity or scope of any 837 Intellectual Property Rights or other rights that might be claimed to 838 pertain to the implementation or use of the technology described in 839 this document or the extent to which any license under such rights 840 might or might not be available; nor does it represent that it has 841 made any independent effort to identify any such rights. Information 842 on the procedures with respect to rights in RFC documents can be 843 found in BCP 78 and BCP 79. 845 Copies of IPR disclosures made to the IETF Secretariat and any 846 assurances of licenses to be made available, or the result of an 847 attempt made to obtain a general license or permission for the use of 848 such proprietary rights by implementers or users of this 849 specification can be obtained from the IETF on-line IPR repository at 850 http://www.ietf.org/ipr. 852 The IETF invites any interested party to bring to its attention any 853 copyrights, patents or patent applications, or other proprietary 854 rights that may cover technology that may be required to implement 855 this standard. Please address the information to the IETF at 856 ietf-ipr@ietf.org. 858 Acknowledgement 860 Funding for the RFC Editor function is currently provided by the 861 Internet Society.