idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-mcm-04.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 1056. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1067. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1074. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1080. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 1048), 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.) ** 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 (May 2004) is 7283 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 103, but not defined == Unused Reference: 'RFC2856' is defined on line 974, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 981, but no explicit reference was found in the text == Unused Reference: 'RFC3593' is defined on line 985, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 989, but no explicit reference was found in the text -- 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: 11 errors (**), 0 flaws (~~), 8 warnings (==), 14 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 May 2004 7 Definitions of Managed Object Extensions 8 for Very High Speed Digital Subscriber Lines (VDSL) Using 9 Multiple Carrier Modulation (MCM) Line Coding 10 draft-ietf-adslmib-vdsl-ext-mcm-04.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 Multiple Carrier 51 Modulation (MCM) 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 .................................... 5 64 4. Definitions ................................................... 5 65 5. Acknowledgements .............................................. 18 66 6. Security Considerations ....................................... 18 67 7. References .................................................... 19 68 7.1 Normative References .......................................... 19 69 7.2 Informative References ........................................ 20 70 Authors' Addresses ............................................ 21 71 Full Copyright Statement ...................................... 21 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 The key words "MAY", "MUST", "MUST NOT", "RECOMMENDED", 89 "NOT RECOMMENDED", and "SHOULD" in this document are to be 90 interpreted as described in [RFC2119]. 92 2. Overview 94 This document describes an SNMP MIB module for managing the Line 95 Code Dependent, Physical Medium Dependent (PMD), Layer of MCM VDSL 96 Lines. These definitions are based upon the specifications for VDSL 97 as defined in T1E1, European Telecommunications Standards Institute 98 (ETSI), and International Telecommunication Union (ITU) documentation 99 [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. 100 Additionally the protocol-dependent (and line-code dependent) 101 management framework for VDSL lines specified by the Digital 102 Subscriber Line Forum (DSLF) has been taken into consideration 103 [DSLFTR057]. 105 The MIB module is located in the MIB tree under the vdslMIB, which 106 in turn is found under MIB 2 transmission. The reader is referred to 107 RFC 3728 [RFC3728] for further discussion of this subject. 109 2.1 Relationship of this MIB Module to other MIB Modules 111 The relationship of the VDSL Line MIB module to other MIB modules 112 and in particular to the IF-MIB, as presented in RFC 2863 [RFC2863], 113 is discussed in the VDSL-LINE-MIB, RFC 3728 [RFC3728]. This section 114 outlines the relationship of this VDSL Line Extension MIB to the 115 VDSL-LINE-MIB, RFC 3728 [RFC3728]. 117 2.2 Conventions used in the MIB Module 119 2.2.1 Naming Conventions 121 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 122 B. Vtur -- (VTUR) transceiver at Remote end of line 123 C. Vtu -- One of either Vtuc or Vtur 124 D. Curr -- Current 125 E. LCS -- Line Code Specific 126 F. Max -- Maximum 127 G. PSD -- Power Spectral Density 128 H. Rx -- Receive 129 I. Tx -- Transmit 131 2.3 Structure 133 The MCM VDSL Line Extension MIB contains the following MIB group: 135 o vdslMCMGroup : 137 This group supports MIB objects for defining configuration profiles 138 and for montioring individual bands of Multiple Carrier Modulation 139 (MCM) VDSL modems. It contains the following tables: 141 - vdslLineMCMConfProfileTable 142 - vdslLineMCMConfProfileTxBandTable 143 - vdslLineMCMConfProfileRxBandTable 144 - vdslLineMCMConfProfileTxPSDTable 145 - vdslLineMCMConfProfileMaxTxPSDTable 146 - vdslLineMCMConfProfileMaxRxPSDTable 148 If the MCM VDSL Line Extension MIB is implemented then all of the 149 objects in this group MUST be implemented. 151 Figure 1, below, displays the relationship of the tables in the 152 vdslMCMGroup to the vdslGroup and to the ifEntry: 154 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 156 vdslLineTableEntry (vdslLineCoding=MCM) 158 vdslLineConfProfileEntry(vdslLineConfProfileName) 159 ----> vdslLineMCMConfProfileTable 1:(0..1) 160 ----> vdslLineMCMConfProfileTxBandTable 1:(0..n) 161 ----> vdslLineMCMConfProfileRxBandTable 1:(0..n) 162 ----> vdslLineMCMConfProfileTxPSDTable 1:(0..n) 163 ----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..n) 164 ----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..n) 166 Figure 1: Table Relationships 168 When the object vdslLineCoding is set to MCM, 169 vdslLineConfProfileName is used as the index to 170 vdslLineMCMConfProfileTxBandTable. The existence of an entry in 171 any of the tables of the vdslMCMGroup is optional. 173 2.4 Persistence 175 All read-create objects defined in this MIB module SHOULD be stored 176 persistently. Following is an exhaustive list of these persistent 177 objects: 179 vdslMCMConfProfileTxWindowLength 180 vdslMCMConfProfileRowStatus 181 vdslMCMConfProfileTxBandNumber 182 vdslMCMConfProfileTxBandStart 183 vdslMCMConfProfileTxBandStop 184 vdslMCMConfProfileTxBandRowStatus 185 vdslMCMConfProfileRxBandStart 186 vdslMCMConfProfileRxBandStop 187 vdslMCMConfProfileRxBandRowStatus 188 vdslMCMConfProfileTxPSDTone 189 vdslMCMConfProfileTxPSDPSD 190 vdslMCMConfProfileTxPSDRowStatus 191 vdslMCMConfProfileMaxTxPSDTone 192 vdslMCMConfProfileMaxTxPSDPSD 193 vdslMCMConfProfileMaxTxPSDRowStatus 194 vdslMCMConfProfileMaxRxPSDTone 195 vdslMCMConfProfileMaxRxPSDPSD 196 vdslMCMConfProfileMaxRxPSDRowStatus 198 Note also that the interface indices in this MIB are maintained 199 persistently. View-based Access Control Model (VACM) data 200 relating to these SHOULD be stored persistently as well [RFC3415]. 202 3. Conformance and Compliance 204 An MCM based VDSL agent does not have to implement this MIB to be 205 compliant with RFC 3728 [RFC3728]. If the MCM VDSL Line Extension 206 MIB is implemented then the following group is mandatory: 208 - vdslMCMGroup 210 4. Definitions 212 VDSL-LINE-EXT-MCM-MIB DEFINITIONS ::= BEGIN 214 IMPORTS 216 MODULE-IDENTITY, 217 OBJECT-TYPE, 218 Unsigned32 FROM SNMPv2-SMI -- [RFC2578] 219 RowStatus FROM SNMPv2-TC -- [RFC2579] 220 MODULE-COMPLIANCE, 221 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 222 vdslMIB, 223 vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] 225 vdslExtMCMMIB MODULE-IDENTITY 226 LAST-UPDATED "200405300000Z" -- May 30, 2004 227 ORGANIZATION "ADSLMIB Working Group" 228 CONTACT-INFO "WG-email: adslmib@ietf.org 229 Info: https://www1.ietf.org/mailman/listinfo/adslmib 231 Chair: Mike Sneed 232 Sand Channel Systems 233 Postal: P.O. Box 37324 234 Raleigh NC 27627-732 235 Email: sneedmike@hotmail.com 236 Phone: +1 206 600 7022 238 Co-editor: Menachem Dodge 239 Infineon Technologies Savan Ltd. 240 6 Hagavish St. 241 Postal: Poleg Industrial Area, 242 Netanya 42504, 243 Israel. 244 Email: menachem.dodge@infineon.com 245 Phone: +972 9 892 4116 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 MCM coding. The objects in this extension MIB MUST NOT 265 be used for VDSL lines using Single Carrier Modulation (SCM) 266 line coding. If an object in this extension MIB is referenced 267 by a line which does not use MCM, 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 LCS -- Line Code Specific 276 Max -- Maximum 277 PSD -- Power Spectral Density 278 Rx -- Receive 279 Tx -- Transmit 281 Copyright (C) The Internet Society (2004). This version 282 of this MIB module is part of RFC XXXX: see the RFC 283 itself for full legal notices." 284 -- RFC Ed.: replace XXXX with assigned number & remove this note 285 REVISION "200405300000Z" -- May 30, 2004 286 DESCRIPTION "Initial version, published as RFC XXXX." 287 -- RFC Ed.: replace XXXX with assigned number & remove this note 288 ::= { vdslMIB XX } -- To be assigned by IANA 289 -- RFC Ed.: we suggest to put it under { vdslMIB 3 } because 290 -- vdslMIB 1 is the VDSL-LINE-MIB, vdslMIB 2 is the SCM 291 -- extension MIB, while vdslMIB 3 is this MCM extension MIB. 293 vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 } 294 vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1} 296 -- 297 -- Multiple carrier modulation (MCM) configuration profile tables 298 -- 300 vdslLineMCMConfProfileTable OBJECT-TYPE 301 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 302 MAX-ACCESS not-accessible 303 STATUS current 304 DESCRIPTION 305 "This table contains additional information on multiple 306 carrier VDSL lines. One entry in this table reflects a 307 profile defined by a manager which can be used to 308 configure the VDSL line. 310 If an entry in this table is referenced by a line which 311 does not use MCM, it has no effect on the operation of that 312 line." 313 ::= { vdslLineExtMCMMibObjects 1 } 315 vdslLineMCMConfProfileEntry OBJECT-TYPE 316 SYNTAX VdslLineMCMConfProfileEntry 317 MAX-ACCESS not-accessible 318 STATUS current 319 DESCRIPTION 320 "Each entry consists of a list of parameters that 321 represents the configuration of a multiple carrier 322 modulation VDSL modem. 324 A default profile with an index of 'DEFVAL', will always 325 exist and its parameters will be set to vendor specific 326 values, unless otherwise specified in this document." 327 INDEX { vdslLineConfProfileName } 328 ::= { vdslLineMCMConfProfileTable 1 } 330 VdslLineMCMConfProfileEntry ::= 331 SEQUENCE 332 { 333 vdslLineMCMConfProfileTxWindowLength Unsigned32, 334 vdslLineMCMConfProfileRowStatus RowStatus 335 } 337 vdslLineMCMConfProfileTxWindowLength OBJECT-TYPE 338 SYNTAX Unsigned32 (1..255) 339 UNITS "samples" 340 MAX-ACCESS read-create 341 STATUS current 342 DESCRIPTION 343 "Specifies the length of the transmit window, counted 344 in samples at the sampling rate corresponding to the 345 negotiated value of N." 346 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 347 ::= { vdslLineMCMConfProfileEntry 1 } 349 vdslLineMCMConfProfileRowStatus OBJECT-TYPE 350 SYNTAX RowStatus 351 MAX-ACCESS read-create 352 STATUS current 353 DESCRIPTION 354 "This object is used to create a new row or modify or 355 delete an existing row in this table. 357 A profile activated by setting this object to `active'. 358 When `active' is set, the system will validate the profile. 360 Before a profile can be deleted or taken out of 361 service, (by setting this object to `destroy' or 362 `outOfService') it must be first unreferenced 363 from all associated lines." 364 ::= { vdslLineMCMConfProfileEntry 2 } 366 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 367 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 368 MAX-ACCESS not-accessible 369 STATUS current 370 DESCRIPTION 371 "This table contains transmit band descriptor configuration 372 information for a VDSL line. Each entry in this table 373 reflects the configuration for one of possibly many bands 374 with a multiple carrier modulation (MCM) VDSL line. 375 These entries are defined by a manager and can be used to 376 configure the VDSL line. 378 If an entry in this table is referenced by a line which 379 does not use MCM, it has no effect on the operation of that 380 line." 381 ::= { vdslLineExtMCMMibObjects 2 } 383 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 384 SYNTAX VdslLineMCMConfProfileTxBandEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "Each entry consists of a transmit band descriptor, which 389 is defined by a start and a stop tone index. 390 A default profile with an index of 'DEFVAL', will 391 always exist and its parameters will be set to vendor 392 specific values, unless otherwise specified in this 393 document." 394 INDEX { vdslLineConfProfileName, 395 vdslLineMCMConfProfileTxBandNumber } 396 ::= { vdslLineMCMConfProfileTxBandTable 1 } 398 VdslLineMCMConfProfileTxBandEntry ::= 399 SEQUENCE 400 { 401 vdslLineMCMConfProfileTxBandNumber Unsigned32, 402 vdslLineMCMConfProfileTxBandStart Unsigned32, 403 vdslLineMCMConfProfileTxBandStop Unsigned32, 404 vdslLineMCMConfProfileTxBandRowStatus RowStatus 405 } 407 vdslLineMCMConfProfileTxBandNumber OBJECT-TYPE 408 SYNTAX Unsigned32 409 MAX-ACCESS not-accessible 410 STATUS current 411 DESCRIPTION 412 "The index for this band descriptor entry." 413 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 415 vdslLineMCMConfProfileTxBandStart OBJECT-TYPE 416 SYNTAX Unsigned32 417 MAX-ACCESS read-create 418 STATUS current 419 DESCRIPTION 420 "Start tone index for this band." 421 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 422 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 424 vdslLineMCMConfProfileTxBandStop OBJECT-TYPE 425 SYNTAX Unsigned32 426 MAX-ACCESS read-create 427 STATUS current 428 DESCRIPTION 429 "Stop tone index for this band." 430 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 431 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 433 vdslLineMCMConfProfileTxBandRowStatus OBJECT-TYPE 434 SYNTAX RowStatus 435 MAX-ACCESS read-create 436 STATUS current 437 DESCRIPTION 438 "This object is used to create a new row or modify or 439 delete an existing row in this table. 440 A profile activated by setting this object to `active'. 441 When `active' is set, the system will validate the profile. 443 Each entry must be internally consistent, the Stop Tone must 444 be greater than the Start Tone. Each entry must also be 445 externally consistent, all entries indexed by a specific 446 profile must not overlap. Validation of the profile will 447 check both internal and external consistency. 449 Before a profile can be deleted or taken out of 450 service, (by setting this object to `destroy' or 451 `outOfService') it must be first unreferenced 452 from all associated lines." 453 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 455 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 456 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION 460 "This table contains receive band descriptor configuration 461 information for a VDSL line. Each entry in this table 462 reflects the configuration for one of possibly many bands 463 with a multiple carrier modulation (MCM) VDSL line. 464 These entries are defined by a manager and can be used to 465 configure the VDSL line. 467 If an entry in this table is referenced by a line which 468 does not use MCM, it has no effect on the operation of that 469 line." 470 ::= { vdslLineExtMCMMibObjects 3 } 472 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 473 SYNTAX VdslLineMCMConfProfileRxBandEntry 474 MAX-ACCESS not-accessible 475 STATUS current 476 DESCRIPTION 477 "Each entry consists of a transmit band descriptor, which 478 is defined by a start and a stop tone index. 480 A default profile with an index of 'DEFVAL', will 481 always exist and its parameters will be set to vendor 482 specific values, unless otherwise specified in this 483 document." 484 INDEX { vdslLineConfProfileName, 485 vdslLineMCMConfProfileRxBandNumber } 486 ::= { vdslLineMCMConfProfileRxBandTable 1 } 488 VdslLineMCMConfProfileRxBandEntry ::= 489 SEQUENCE 490 { 491 vdslLineMCMConfProfileRxBandNumber Unsigned32, 492 vdslLineMCMConfProfileRxBandStart Unsigned32, 493 vdslLineMCMConfProfileRxBandStop Unsigned32, 494 vdslLineMCMConfProfileRxBandRowStatus RowStatus 495 } 497 vdslLineMCMConfProfileRxBandNumber OBJECT-TYPE 498 SYNTAX Unsigned32 499 MAX-ACCESS not-accessible 500 STATUS current 501 DESCRIPTION 502 "The index for this band descriptor entry." 503 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 505 vdslLineMCMConfProfileRxBandStart OBJECT-TYPE 506 SYNTAX Unsigned32 507 MAX-ACCESS read-create 508 STATUS current 509 DESCRIPTION 510 "Start tone index for this band." 511 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 512 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 514 vdslLineMCMConfProfileRxBandStop OBJECT-TYPE 515 SYNTAX Unsigned32 516 MAX-ACCESS read-create 517 STATUS current 518 DESCRIPTION 519 "Stop tone index for this band." 520 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 521 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 523 vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE 524 SYNTAX RowStatus 525 MAX-ACCESS read-create 526 STATUS current 527 DESCRIPTION 528 "This object is used to create a new row or modify or 529 delete an existing row in this table. 531 A profile activated by setting this object to `active'. 532 When `active' is set, the system will validate the profile. 533 Each entry must be internally consistent, the Stop Tone must 534 be greater than the Start Tone. Each entry must also be 535 externally consistent, all entries indexed by a specific 536 profile must not overlap. Validation of the profile will 537 check both internal and external consistency. 539 Before a profile can be deleted or taken out of 540 service, (by setting this object to `destroy' or 541 `outOfService') it must be first unreferenced 542 from all associated lines." 543 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 545 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 546 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 547 MAX-ACCESS not-accessible 548 STATUS current 549 DESCRIPTION 550 "This table contains transmit PSD mask descriptor 551 configuration information for a VDSL line. Each entry in 552 this table reflects the configuration for one tone within 553 a multiple carrier modulation (MCM) VDSL line. These 554 entries are defined by a manager and can be used to 555 configure the VDSL line. 557 If an entry in this table is referenced by a line which 558 does not use MCM, it has no effect on the operation of that 559 line." 560 ::= { vdslLineExtMCMMibObjects 4 } 562 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 563 SYNTAX VdslLineMCMConfProfileTxPSDEntry 564 MAX-ACCESS not-accessible 565 STATUS current 566 DESCRIPTION 567 "Each entry consists of a transmit PSD mask descriptor, 568 which defines the power spectral density (PSD) for a tone. 570 A default profile with an index of 'DEFVAL', will 571 always exist and its parameters will be set to vendor 572 specific values, unless otherwise specified in this 573 document." 574 INDEX { vdslLineConfProfileName, 575 vdslLineMCMConfProfileTxPSDNumber } 576 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 578 VdslLineMCMConfProfileTxPSDEntry ::= 579 SEQUENCE 580 { 581 vdslLineMCMConfProfileTxPSDNumber Unsigned32, 582 vdslLineMCMConfProfileTxPSDTone Unsigned32, 583 vdslLineMCMConfProfileTxPSDPSD Unsigned32, 584 vdslLineMCMConfProfileTxPSDRowStatus RowStatus 585 } 587 vdslLineMCMConfProfileTxPSDNumber OBJECT-TYPE 588 SYNTAX Unsigned32 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "The index for this mask descriptor entry." 593 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 595 vdslLineMCMConfProfileTxPSDTone OBJECT-TYPE 596 SYNTAX Unsigned32 597 MAX-ACCESS read-create 598 STATUS current 599 DESCRIPTION 600 "The tone index for which the PSD is being specified." 601 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 602 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 604 vdslLineMCMConfProfileTxPSDPSD OBJECT-TYPE 605 SYNTAX Unsigned32 606 UNITS "0.5dBm/Hz" 607 MAX-ACCESS read-create 608 STATUS current 609 DESCRIPTION 610 "Power Spectral Density level in steps of 0.5dBm/Hz with 611 an offset of -140dBm/Hz." 612 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 613 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 615 vdslLineMCMConfProfileTxPSDRowStatus OBJECT-TYPE 616 SYNTAX RowStatus 617 MAX-ACCESS read-create 618 STATUS current 619 DESCRIPTION 620 "This object is used to create a new row or modify or 621 delete an existing row in this table. 623 A profile activated by setting this object to `active'. 624 When `active' is set, the system will validate the profile. 626 Before a profile can be deleted or taken out of 627 service, (by setting this object to `destroy' or 628 `outOfService') it must be first unreferenced 629 from all associated lines." 630 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 632 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 633 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "This table contains transmit maximum PSD mask descriptor 638 configuration information for a VDSL line. Each entry in 639 this table reflects the configuration for one tone within 640 a multiple carrier modulation (MCM) VDSL modem. These 641 entries are defined by a manager and can be used to 642 configure the VDSL line. 644 If an entry in this table is referenced by a line which 645 does not use MCM, it has no effect on the operation of that 646 line." 647 ::= { vdslLineExtMCMMibObjects 5 } 649 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 650 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "Each entry consists of a transmit PSD mask descriptor, 655 which defines the maximum power spectral density (PSD) 656 for a tone. 658 A default profile with an index of 'DEFVAL', will 659 always exist and its parameters will be set to vendor 660 specific values, unless otherwise specified in this 661 document." 662 INDEX { vdslLineConfProfileName, 663 vdslLineMCMConfProfileMaxTxPSDNumber } 664 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 666 VdslLineMCMConfProfileMaxTxPSDEntry ::= 667 SEQUENCE 668 { 669 vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32, 670 vdslLineMCMConfProfileMaxTxPSDTone Unsigned32, 671 vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32, 672 vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus 673 } 675 vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 676 SYNTAX Unsigned32 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "The index for this band descriptor entry." 681 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 683 vdslLineMCMConfProfileMaxTxPSDTone OBJECT-TYPE 684 SYNTAX Unsigned32 685 MAX-ACCESS read-create 686 STATUS current 687 DESCRIPTION 688 "The tone index for which the PSD is being specified. 689 There must not be multiple rows defined, for a particular 690 profile, with the same value for this field." 691 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 692 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 694 vdslLineMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 695 SYNTAX Unsigned32 696 UNITS "0.5dBm/Hz" 697 MAX-ACCESS read-create 698 STATUS current 699 DESCRIPTION 700 "Power Spectral Density level in steps of 0.5dBm/Hz with 701 an offset of -140dBm/Hz." 702 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 703 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 705 vdslLineMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 706 SYNTAX RowStatus 707 MAX-ACCESS read-create 708 STATUS current 709 DESCRIPTION 710 "This object is used to create a new row or modify or 711 delete an existing row in this table. 713 A profile activated by setting this object to `active'. 714 When `active' is set, the system will validate the profile. 715 There must be only one entry in this table for each tone 716 associated with a specific profile. This will be checked 717 during the validation process. 719 Before a profile can be deleted or taken out of 720 service, (by setting this object to `destroy' or 721 `outOfService') it must be first unreferenced 722 from all associated lines." 723 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 725 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 726 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "This table contains maximum receive PSD mask descriptor 731 configuration information for a VDSL line. Each entry in 732 this table reflects the configuration for one tone within 733 a multiple carrier modulation (MCM) VDSL modem. These 734 entries are defined by a manager and can be used to 735 configure the VDSL line. 737 If an entry in this table is referenced by a line which 738 does not use MCM, it has no effect on the operation of that 739 line." 740 ::= { vdslLineExtMCMMibObjects 6 } 742 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 743 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "Each entry consists of a transmit PSD mask descriptor, 748 which defines the power spectral density (PSD) for a 749 tone. 751 A default profile with an index of 'DEFVAL', will 752 always exist and its parameters will be set to vendor 753 specific values, unless otherwise specified in this 754 document." 755 INDEX { vdslLineConfProfileName, 756 vdslLineMCMConfProfileMaxRxPSDNumber } 757 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 759 VdslLineMCMConfProfileMaxRxPSDEntry ::= 760 SEQUENCE 761 { 762 vdslLineMCMConfProfileMaxRxPSDNumber Unsigned32, 763 vdslLineMCMConfProfileMaxRxPSDTone Unsigned32, 764 vdslLineMCMConfProfileMaxRxPSDPSD Unsigned32, 765 vdslLineMCMConfProfileMaxRxPSDRowStatus RowStatus 766 } 768 vdslLineMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 769 SYNTAX Unsigned32 770 MAX-ACCESS not-accessible 771 STATUS current 772 DESCRIPTION 773 "The index for this band descriptor entry." 774 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 776 vdslLineMCMConfProfileMaxRxPSDTone OBJECT-TYPE 777 SYNTAX Unsigned32 778 MAX-ACCESS read-create 779 STATUS current 780 DESCRIPTION 781 "The tone index for which the PSD is being specified. 782 There must not be multiple rows defined, for a particular 783 profile, with the same value for this field." 784 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 785 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 787 vdslLineMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 788 SYNTAX Unsigned32 789 UNITS "0.5dBm/Hz" 790 MAX-ACCESS read-create 791 STATUS current 792 DESCRIPTION 793 "Power Spectral Density level in steps of 0.5dBm/Hz with 794 an offset of -140dBm/Hz." 795 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 796 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 798 vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 799 SYNTAX RowStatus 800 MAX-ACCESS read-create 801 STATUS current 802 DESCRIPTION 803 "This object is used to create a new row or modify or 804 delete an existing row in this table. 806 A profile activated by setting this object to `active'. 807 When `active' is set, the system will validate the profile. 808 There must be only one entry in this table for each tone 809 associated with a specific profile. This will be checked 810 during the validation process. 812 Before a profile can be deleted or taken out of 813 service, (by setting this object to `destroy' or 814 `outOfService') it must be first unreferenced 815 from all associated lines." 816 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 818 -- conformance information 820 vdslLineExtMCMConformance OBJECT IDENTIFIER ::= 821 { vdslLineExtMCMMib 2 } 822 vdslLineExtMCMGroups OBJECT IDENTIFIER ::= 823 { vdslLineExtMCMConformance 1 } 824 vdslLineExtMCMCompliances OBJECT IDENTIFIER ::= 825 { vdslLineExtMCMConformance 2 } 827 vdslLineExtMCMMibCompliance MODULE-COMPLIANCE 828 STATUS current 829 DESCRIPTION 830 "The compliance statement for SNMP entities which 831 manage VDSL interfaces." 832 MODULE -- this module 833 GROUP vdslLineExtMCMGroup 834 DESCRIPTION 835 "This group is an optional extension for VDSL lines which 836 utilize Multiple Carrier Modulation (MCM)." 837 ::= { vdslLineExtMCMCompliances 1 } 839 -- units of conformance 841 vdslLineExtMCMGroup OBJECT-GROUP 842 OBJECTS 843 { 844 vdslLineMCMConfProfileTxWindowLength, 845 vdslLineMCMConfProfileRowStatus, 846 vdslLineMCMConfProfileTxBandStart, 847 vdslLineMCMConfProfileTxBandStop, 848 vdslLineMCMConfProfileTxBandRowStatus, 849 vdslLineMCMConfProfileRxBandStart, 850 vdslLineMCMConfProfileRxBandStop, 851 vdslLineMCMConfProfileRxBandRowStatus, 852 vdslLineMCMConfProfileTxPSDTone, 853 vdslLineMCMConfProfileTxPSDPSD, 854 vdslLineMCMConfProfileTxPSDRowStatus, 855 vdslLineMCMConfProfileMaxTxPSDTone, 856 vdslLineMCMConfProfileMaxTxPSDPSD, 857 vdslLineMCMConfProfileMaxTxPSDRowStatus, 858 vdslLineMCMConfProfileMaxRxPSDTone, 859 vdslLineMCMConfProfileMaxRxPSDPSD, 860 vdslLineMCMConfProfileMaxRxPSDRowStatus 861 } 862 STATUS current 863 DESCRIPTION 864 "A collection of objects providing configuration 865 information for a VDSL line based upon multiple 866 carrier modulation modem." 867 ::= { vdslLineExtMCMGroups 1 } 869 END 871 5. Acknowledgments 873 This document contains many definitions taken from 874 draft-ietf-adslmib-vdsl-07.txt. As such, any credit for the text 875 found within should be fully attributed to the authors of that 876 document. 878 6. Security Considerations 880 There are a number of management objects defined in this MIB module 881 with a MAX-ACCESS clause of read-create. Such objects may be 882 considered sensitive or vulnerable in some network environments. 883 The support for SET operations in a non-secure environment without 884 proper protection can have a negative effect on network operations. 886 Some of the readable objects in this MIB module (i.e., objects with a 887 MAX-ACCESS other than not-accessible) may be considered sensitive or 888 vulnerable in some network environments. 890 VDSL layer connectivity from the Vtur will permit the subscriber to 891 manipulate both the VDSL link directly and the VDSL embedded 892 operations channel (EOC) for their own loop. For example, unchecked 893 or unfiltered fluctuations initiated by the subscriber could generate 894 sufficient notifications to potentially overwhelm either the 895 management interface to the network or the element manager. 897 Additionally, allowing write access to configuration data may allow 898 an end-user to increase their service levels or affect other end- 899 users in either a positive or negative manner. For this reason, the 900 following tables should be considered to contain sensitive 901 information: 903 - vdslLineMCMConfProfileTable 904 - vdslLineMCMConfProfileTxBandTable 905 - vdslLineMCMConfProfileRxBandTable 906 - vdslLineMCMConfProfileTxPSDTable 907 - vdslLineMCMConfProfileMaxTxPSDTable 908 - vdslLineMCMConfProfileMaxRxPSDTable 910 It is thus important to control even GET access to the objects within 911 these tables and possibly to even encrypt the values of these objects 912 when sending them over the network via SNMP. Not all versions of 913 SNMP provide features for such a secure environment. 915 SNMP versions prior to SNMPv3 did not include adequate security. 916 Even if the network itself is secure (for example by using IPSec), 917 even then, there is no control as to who on the secure network is 918 allowed to access and GET/SET (read/change/create/delete) the objects 919 in this MIB module. 921 It is RECOMMENDED that implementers consider the security features as 922 provided by the SNMPv3 framework (see [RFC3410], section 8), 923 including full support for the SNMPv3 cryptographic mechanisms (for 924 authentication and privacy). 926 Further, deployment of SNMP versions prior to SNMPv3 is NOT 927 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 928 enable cryptographic security. It is then a customer/operator 929 responsibility to ensure that the SNMP entity giving access to an 930 instance of a MIB module which utilizes the textual conventions 931 defined in this MIB module is properly configured to give access to 932 the objects only to those principals (users) that have legitimate 933 rights to indeed GET or SET (change/create/delete) them. 935 7. References 937 7.1. Normative References 939 [DSLFTR057]DSL Forum TR-057, "VDSL Network Element Management", 940 February 2003. 942 [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing 943 (TM); Access transmission systems on metallic access 944 cables; Very high speed Digital Subscriber Line (VDSL); 945 Part 1: Functional requirements", October 1999. 947 [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing 948 (TM); Access transmission systems on metallic access 949 cables; Very high speed Digital Subscriber Line (VDSL); 950 Part 1: Transceiver specification", February 2001. 952 [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line 953 foundation", November 2001. 955 [ITU9971] ITU-T G.997.1, "Physical layer management for Digital 956 Subscriber Line (DSL) Transceivers", July 1999. 958 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 959 Requirement Levels", BCP 14, RFC 2119, March 1997. 961 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 962 J., Rose, M. and S. Waldbusser, "Structure of 963 Management Information Version 2 (SMIv2)", STD 58, RFC 964 2578, April 1999. 966 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 967 J., Rose, M. and S. Waldbusser, "Textual Conventions 968 for SMIv2", STD 58, RFC 2579, April 1999. 970 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 971 J., Rose, M. and S. Waldbusser, "Conformance 972 Statements for SMIv2", STD 58, RFC 2580, April 1999. 974 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 975 Conventions for Additional High Capacity Data Types", 976 RFC 2856, June 2000. 978 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 979 Group MIB", RFC 2863, June 2000. 981 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 982 Simple Network Management Protocol (SNMP)", STD 62, RFC 983 3418, December 2002. 985 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 986 Performance History Based on 15 Minute Intervals", RFC 987 3593, September 2003. 989 [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An 990 Architecture for Describing Simple Network Management 991 Protocol (SNMP) Management Frameworks", RFC 3411, 992 December 2002. 994 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 995 Very High Speed Digital Subscriber Lines (VDSL)", RFC 996 3728, February 2004. 998 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 999 Subscriber Line (VDSL) Metallic Interface, Part 1: 1000 Functional Requirements and Common Specification", 1001 February 2001. 1003 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 1004 2: Technical Specification for a Single-Carrier 1005 Modulation (SCM) Transceiver", November 2001. 1007 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 1008 3: Technical Specification for a Multi-Carrier 1009 Modulation (MCM) Transceiver", November 2000. 1011 7.2. Informative References 1013 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 1014 Access Control Model (VACM) for the Simple Network 1015 Management Protocol (SNMP)", RFC 3415, December 2002. 1017 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1018 "Introduction and Applicability Statements for Internet- 1019 Standard Management Framework", RFC 3410, December 2002. 1021 Authors' Addresses 1023 Menachem Dodge 1024 Infineon Technologies Savan Ltd. 1025 6 Hagavish St. 1026 Poleg Industrial Area, 1027 Netanya 42504, 1028 Israel 1030 Phone: +972 9 892 4116 1031 Fax: +972 9 865 8756 1032 Email: menachem.dodge@infineon.com 1034 Bob Ray 1035 PESA Switching Systems, Inc. 1036 330-A Wynn Drive 1037 Huntsville, AL 35805 1038 USA 1040 Phone: +1 256 726 9200 ext. 142 1041 Fax: +1 256 726 9271 1042 EMail: rray@pesa.com 1044 Full Copyright Statement 1046 Copyright (C) The Internet Society (2004). This document is subject 1047 to the rights, licenses and restrictions contained in BCP 78 and 1048 except as set forth therein, the authors retain all their rights. 1050 This document and the information contained herein are provided on an 1051 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1052 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1053 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1054 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1055 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1056 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1058 Intellectual Property 1060 The IETF takes no position regarding the validity or scope of any 1061 Intellectual Property Rights or other rights that might be claimed to 1062 pertain to the implementation or use of the technology described in 1063 this document or the extent to which any license under such rights 1064 might or might not be available; nor does it represent that it has 1065 made any independent effort to identify any such rights. Information 1066 on the procedures with respect to rights in RFC documents can be 1067 found in BCP 78 and BCP 79. 1069 Copies of IPR disclosures made to the IETF Secretariat and any 1070 assurances of licenses to be made available, or the result of an 1071 attempt made to obtain a general license or permission for the use 1072 of such proprietary rights by implementers or users of this 1073 specification can be obtained from the IETF on-line IPR repository 1074 at http://www.ietf.org/ipr. 1076 The IETF invites any interested party to bring to its attention any 1077 copyrights, patents or patent applications, or other proprietary 1078 rights that may cover technology that may be required to implement 1079 this standard. Please address the information to the IETF at ietf- 1080 ipr@ietf.org. 1082 Acknowledgement 1084 Funding for the RFC Editor function is currently provided by the 1085 Internet Society.