idnits 2.17.1 draft-ietf-adslmib-vdsl-ext-mcm-05.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 1071. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1082. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1089. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1095. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 1063), 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 (December 2004) is 7065 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFTR57' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2701' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2702' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9931' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9971' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' Summary: 8 errors (**), 0 flaws (~~), 3 warnings (==), 15 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group M. Dodge 2 Category: Internet Draft ECI Telecom 3 B. Ray 4 PESA Switching Systems 5 December 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-05.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 Multiple Carrier 48 Modulation (MCM) 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 ................................................... 5 62 5. Acknowledgements .............................................. 18 63 6. Security Considerations ....................................... 18 64 7. IANA Considerations ............................................ 19 65 8. References ..................................................... 19 66 8.1 Normative References ........................................... 19 67 8.2 Informative References ......................................... 21 68 Authors' Addresses ............................................. 21 69 Full Copyright Statement ....................................... 21 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 MCM VDSL 90 Lines. These definitions are based upon the specifications for VDSL 91 as defined in T1E1, European Telecommunications Standards Institute 92 (ETSI), and International Telecommunication Union (ITU) documentation 93 [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. 94 Additionally the protocol-dependent (and line-code dependent) 95 management framework for VDSL lines specified by the Digital 96 Subscriber Line Forum (DSLF) has been taken into consideration 97 [DSLFTR57]. 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 E. LCS -- Line Code Specific 121 F. Max -- Maximum 122 G. PSD -- Power Spectral Density 123 H. Rx -- Receive 124 I. Tx -- Transmit 126 2.3 Structure 128 The MCM VDSL Line Extension MIB contains the following MIB group: 130 o vdslMCMGroup : 132 This group supports MIB objects for defining configuration profiles 133 and for monitoring individual bands of Multiple Carrier Modulation 134 (MCM) VDSL modems. It contains the following tables: 136 - vdslLineMCMConfProfileTable 137 - vdslLineMCMConfProfileTxBandTable 138 - vdslLineMCMConfProfileRxBandTable 139 - vdslLineMCMConfProfileTxPSDTable 140 - vdslLineMCMConfProfileMaxTxPSDTable 141 - vdslLineMCMConfProfileMaxRxPSDTable 143 If the MCM 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 vdslMCMGroup to the vdslGroup and to the ifEntry: 149 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 151 vdslLineTableEntry (vdslLineCoding=MCM) 152 vdslLineConfProfileEntry(vdslLineConfProfileName) 153 ----> vdslLineMCMConfProfileTable 1:(0..1) 154 ----> vdslLineMCMConfProfileTxBandTable 1:(0..n) 155 ----> vdslLineMCMConfProfileRxBandTable 1:(0..n) 156 ----> vdslLineMCMConfProfileTxPSDTable 1:(0..n) 157 ----> vdslLineMCMConfProfileMaxTxPSDTable 1:(0..n) 158 ----> vdslLineMCMConfProfileMaxRxPSDTable 1:(0..n) 160 Figure 1: Table Relationships 162 When the object vdslLineCoding is set to MCM, 163 vdslLineConfProfileName is used as the index to each of the six 164 vdslLineMCMConfProfile Tables. The existence of an entry in 165 any of the tables of the vdslMCMGroup is optional. 167 2.4 Persistence 169 All read-create objects defined in this MIB module SHOULD be stored 170 persistently. Following is an exhaustive list of these persistent 171 objects: 173 vdslMCMConfProfileTxWindowLength 174 vdslMCMConfProfileRowStatus 175 vdslMCMConfProfileTxBandNumber 176 vdslMCMConfProfileTxBandStart 177 vdslMCMConfProfileTxBandStop 178 vdslMCMConfProfileTxBandRowStatus 179 vdslMCMConfProfileRxBandStart 180 vdslMCMConfProfileRxBandStop 181 vdslMCMConfProfileRxBandRowStatus 182 vdslMCMConfProfileTxPSDTone 183 vdslMCMConfProfileTxPSDPSD 184 vdslMCMConfProfileTxPSDRowStatus 185 vdslMCMConfProfileMaxTxPSDTone 186 vdslMCMConfProfileMaxTxPSDPSD 187 vdslMCMConfProfileMaxTxPSDRowStatus 188 vdslMCMConfProfileMaxRxPSDTone 189 vdslMCMConfProfileMaxRxPSDPSD 190 vdslMCMConfProfileMaxRxPSDRowStatus 192 Note also that the interface indices in this MIB are maintained 193 persistently. View-based Access Control Model (VACM) data 194 relating to these SHOULD be stored persistently as well [RFC3415]. 196 3. Conformance and Compliance 198 An MCM based VDSL agent does not have to implement this MIB to be 199 compliant with RFC 3728 [RFC3728]. If the MCM VDSL Line Extension 200 MIB is implemented then the following group is mandatory: 202 - vdslMCMGroup 204 4. Definitions 206 VDSL-LINE-EXT-MCM-MIB DEFINITIONS ::= BEGIN 208 IMPORTS 209 MODULE-IDENTITY, 210 OBJECT-TYPE, 211 transmission, 212 Unsigned32 FROM SNMPv2-SMI -- [RFC2578] 213 RowStatus FROM SNMPv2-TC -- [RFC2579] 214 MODULE-COMPLIANCE, 215 OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 216 ifIndex FROM IF-MIB -- [RFC2863] 217 vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] 219 vdslExtMCMMIB MODULE-IDENTITY 220 LAST-UPDATED "200412160000Z" -- December 16, 2004 221 ORGANIZATION "ADSLMIB Working Group" 222 CONTACT-INFO "WG-email: adslmib@ietf.org 223 Info: https://www1.ietf.org/mailman/listinfo/adslmib 225 Chair: Mike Sneed 226 Sand Channel Systems 227 Postal: P.O. Box 37324 228 Raleigh NC 27627-732 229 Email: sneedmike@hotmail.com 230 Phone: +1 206 600 7022 232 Co-Chair: Bob Ray 233 PESA Switching Systems, Inc. 234 Postal: 330-A Wynn Drive 235 Huntsville, AL 35805 236 USA 237 Email: rray@pesa.com 238 Phone: +1 256 726 9200 ext. 142 240 Co-editor: Menachem Dodge 241 ECI Telecom Ltd. 242 Postal: 30 hasivim St. 243 Petach Tikva 49517, 244 Israel. 245 Email: mbdodge@ieee.org 246 Phone: +972 3 926 8421 248 Co-editor: Bob Ray 249 PESA Switching Systems, Inc. 250 Postal: 330-A Wynn Drive 251 Huntsville, AL 35805 252 USA 253 Email: rray@pesa.com 254 Phone: +1 256 726 9200 ext. 142 255 " 257 DESCRIPTION 258 "The VDSL-LINE-MIB found in RFC 3728 defines objects for 259 the management of a pair of VDSL transceivers at each end of 260 the VDSL line. The VDSL-LINE-MIB configures and monitors the 261 line code independent parameters (TC layer) of the VDSL line. 262 This MIB module is an optional extension of the VDSL-LINE-MIB 263 and defines objects for configuration and monitoring of the 264 line code specific (LCS) elements (PMD layer) for VDSL lines 265 using MCM coding. The objects in this extension MIB MUST NOT 266 be used for VDSL lines using Single Carrier Modulation (SCM) 267 line coding. If an object in this extension MIB is referenced 268 by a line which does not use MCM, it has no effect on the 269 operation of that line. 271 Naming Conventions: 272 Vtuc -- (VTUC) transceiver at near (Central) end of line 273 Vtur -- (VTUR) transceiver at Remote end of line 274 Vtu -- One of either Vtuc or Vtur 275 Curr -- Current 276 LCS -- Line Code Specific 277 Max -- Maximum 278 PSD -- Power Spectral Density 279 Rx -- Receive 280 Tx -- Transmit 282 Copyright (C) The Internet Society (2004). This version 283 of this MIB module is part of RFC XXXX: see the RFC 284 itself for full legal notices." 285 -- RFC Ed.: replace XXXX with assigned number & remove this note 286 REVISION "200412160000Z" -- December 16, 2004 287 DESCRIPTION "Initial version, published as RFC XXXX." 288 -- RFC Ed.: replace XX with assigned number & remove this note 289 ::= { transmission XX } -- To be assigned by IANA 290 -- RFC Ed.: we suggest to put it under { transmission 228 } because 291 -- this is the next available number, transmission 227 292 -- would be used for the SCM MIB. 294 vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 } 295 vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1} 297 -- 298 -- Multiple carrier modulation (MCM) configuration profile tables 299 -- 301 vdslLineMCMConfProfileTable OBJECT-TYPE 302 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 303 MAX-ACCESS not-accessible 304 STATUS current 305 DESCRIPTION 306 "This table contains additional information on multiple 307 carrier VDSL lines. One entry in this table reflects a 308 profile defined by a manager which can be used to 309 configure the VDSL line. 311 If an entry in this table is referenced by a line which 312 does not use MCM, it has no effect on the operation of that 313 line. 315 All read-create objects defined in this MIB module SHOULD be 316 stored persistently." 318 ::= { vdslLineExtMCMMibObjects 1 } 320 vdslLineMCMConfProfileEntry OBJECT-TYPE 321 SYNTAX VdslLineMCMConfProfileEntry 322 MAX-ACCESS not-accessible 323 STATUS current 324 DESCRIPTION 325 "Each entry consists of a list of parameters that 326 represents the configuration of a multiple carrier 327 modulation VDSL modem." 328 INDEX { vdslLineConfProfileName } 329 ::= { vdslLineMCMConfProfileTable 1 } 331 VdslLineMCMConfProfileEntry ::= 332 SEQUENCE 333 { 334 vdslLineMCMConfProfileTxWindowLength Unsigned32, 335 vdslLineMCMConfProfileRowStatus RowStatus 336 } 338 vdslLineMCMConfProfileTxWindowLength OBJECT-TYPE 339 SYNTAX Unsigned32 (1..255) 340 UNITS "samples" 341 MAX-ACCESS read-create 342 STATUS current 343 DESCRIPTION 344 "Specifies the length of the transmit window, counted 345 in samples at the sampling rate corresponding to the 346 negotiated value of N." 347 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 348 ::= { vdslLineMCMConfProfileEntry 1 } 350 vdslLineMCMConfProfileRowStatus OBJECT-TYPE 351 SYNTAX RowStatus 352 MAX-ACCESS read-create 353 STATUS current 354 DESCRIPTION 355 "This object is used to create a new row or modify or 356 delete an existing row in this table. 358 A profile is activated by setting this object to `active'. 359 When `active' is set, the system will validate the profile. 361 None of the columns in this row may be modified while the 362 row is in the 'active' state. 364 Before a profile can be deleted or taken out of 365 service, (by setting this object to `destroy' or 366 `notInService') it must be first unreferenced 367 from all associated lines." 368 ::= { vdslLineMCMConfProfileEntry 2 } 370 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 371 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "This table contains transmit band descriptor configuration 376 information for a VDSL line. Each entry in this table 377 reflects the configuration for one of possibly many bands 378 with a multiple carrier modulation (MCM) VDSL line. 379 These entries are defined by a manager and can be used to 380 configure the VDSL line. 382 If an entry in this table is referenced by a line which 383 does not use MCM, it has no effect on the operation of that 384 line. 386 All read-create objects defined in this MIB module SHOULD be 387 stored persistently." 388 ::= { vdslLineExtMCMMibObjects 2 } 390 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 391 SYNTAX VdslLineMCMConfProfileTxBandEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "Each entry consists of a transmit band descriptor, which 396 is defined by a start and a stop tone index." 397 INDEX { vdslLineConfProfileName, 398 vdslLineMCMConfProfileTxBandNumber } 399 ::= { vdslLineMCMConfProfileTxBandTable 1 } 401 VdslLineMCMConfProfileTxBandEntry ::= 402 SEQUENCE 403 { 404 vdslLineMCMConfProfileTxBandNumber Unsigned32, 405 vdslLineMCMConfProfileTxBandStart Unsigned32, 406 vdslLineMCMConfProfileTxBandStop Unsigned32, 407 vdslLineMCMConfProfileTxBandRowStatus RowStatus 408 } 410 vdslLineMCMConfProfileTxBandNumber OBJECT-TYPE 411 SYNTAX Unsigned32 (1..4096) 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "The index for this band descriptor entry." 416 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 418 vdslLineMCMConfProfileTxBandStart OBJECT-TYPE 419 SYNTAX Unsigned32 (1..4096) 420 MAX-ACCESS read-create 421 STATUS current 422 DESCRIPTION 423 "Start tone index for this band." 424 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 425 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 427 vdslLineMCMConfProfileTxBandStop OBJECT-TYPE 428 SYNTAX Unsigned32 (1..4096) 429 MAX-ACCESS read-create 430 STATUS current 431 DESCRIPTION 432 "Stop tone index for this band." 433 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 434 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 436 vdslLineMCMConfProfileTxBandRowStatus OBJECT-TYPE 437 SYNTAX RowStatus 438 MAX-ACCESS read-create 439 STATUS current 440 DESCRIPTION 441 "This object is used to create a new row or modify or 442 delete an existing row in this table. 443 A profile activated by setting this object to `active'. 444 When `active' is set, the system will validate the profile. 446 Each entry must be internally consistent, the Stop Tone must 447 be greater than the Start Tone. Each entry must also be 448 externally consistent, all entries indexed by a specific 449 profile must not overlap. Validation of the profile will 450 check both internal and external consistency. 452 None of the columns in this row may be modified while the 453 row is in the 'active' state. 455 Before a profile can be deleted or taken out of 456 service, (by setting this object to `destroy' or 457 `notInService') it must be first unreferenced 458 from all associated lines." 459 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 461 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 462 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 463 MAX-ACCESS not-accessible 464 STATUS current 465 DESCRIPTION 466 "This table contains receive band descriptor configuration 467 information for a VDSL line. Each entry in this table 468 reflects the configuration for one of possibly many bands 469 with a multiple carrier modulation (MCM) VDSL line. 470 These entries are defined by a manager and can be used to 471 configure the VDSL line. 473 If an entry in this table is referenced by a line which 474 does not use MCM, it has no effect on the operation of that 475 line. 477 All read-create objects defined in this MIB module SHOULD be 478 stored persistently." 479 ::= { vdslLineExtMCMMibObjects 3 } 481 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 482 SYNTAX VdslLineMCMConfProfileRxBandEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "Each entry consists of a transmit band descriptor, which 487 is defined by a start and a stop tone index." 489 INDEX { vdslLineConfProfileName, 490 vdslLineMCMConfProfileRxBandNumber } 491 ::= { vdslLineMCMConfProfileRxBandTable 1 } 493 VdslLineMCMConfProfileRxBandEntry ::= 494 SEQUENCE 495 { 496 vdslLineMCMConfProfileRxBandNumber Unsigned32, 497 vdslLineMCMConfProfileRxBandStart Unsigned32, 498 vdslLineMCMConfProfileRxBandStop Unsigned32, 499 vdslLineMCMConfProfileRxBandRowStatus RowStatus 500 } 502 vdslLineMCMConfProfileRxBandNumber OBJECT-TYPE 503 SYNTAX Unsigned32 (1..4096) 504 MAX-ACCESS not-accessible 505 STATUS current 506 DESCRIPTION 507 "The index for this band descriptor entry." 508 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 510 vdslLineMCMConfProfileRxBandStart OBJECT-TYPE 511 SYNTAX Unsigned32 (1..4096) 512 MAX-ACCESS read-create 513 STATUS current 514 DESCRIPTION 515 "Start tone index for this band." 516 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 517 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 519 vdslLineMCMConfProfileRxBandStop OBJECT-TYPE 520 SYNTAX Unsigned32 (1..4096) 521 MAX-ACCESS read-create 522 STATUS current 523 DESCRIPTION 524 "Stop tone index for this band." 525 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 526 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 528 vdslLineMCMConfProfileRxBandRowStatus OBJECT-TYPE 529 SYNTAX RowStatus 530 MAX-ACCESS read-create 531 STATUS current 532 DESCRIPTION 533 "This object is used to create a new row or modify or 534 delete an existing row in this table. 536 A profile activated by setting this object to `active'. 537 When `active' is set, the system will validate the profile. 538 Each entry must be internally consistent, the Stop Tone must 539 be greater than the Start Tone. Each entry must also be 540 externally consistent, all entries indexed by a specific 541 profile must not overlap. Validation of the profile will 542 check both internal and external consistency. 544 None of the columns in this row may be modified while the 545 row is in the 'active' state. 547 Before a profile can be deleted or taken out of 548 service, (by setting this object to `destroy' or 549 `notInService') it must be first unreferenced 550 from all associated lines." 551 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 553 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 554 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION 558 "This table contains transmit PSD mask descriptor 559 configuration information for a VDSL line. Each entry in 560 this table reflects the configuration for one tone within 561 a multiple carrier modulation (MCM) VDSL line. These 562 entries are defined by a manager and can be used to 563 configure the VDSL line. 565 If an entry in this table is referenced by a line which 566 does not use MCM, it has no effect on the operation of that 567 line. 569 All read-create objects defined in this MIB module SHOULD be 570 stored persistently." 571 ::= { vdslLineExtMCMMibObjects 4 } 573 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 574 SYNTAX VdslLineMCMConfProfileTxPSDEntry 575 MAX-ACCESS not-accessible 576 STATUS current 577 DESCRIPTION 578 "Each entry consists of a transmit PSD mask descriptor, 579 which defines the power spectral density (PSD) for a tone." 581 INDEX { vdslLineConfProfileName, 582 vdslLineMCMConfProfileTxPSDNumber } 583 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 585 VdslLineMCMConfProfileTxPSDEntry ::= 586 SEQUENCE 587 { 588 vdslLineMCMConfProfileTxPSDNumber Unsigned32, 589 vdslLineMCMConfProfileTxPSDTone Unsigned32, 590 vdslLineMCMConfProfileTxPSDPSD Unsigned32, 591 vdslLineMCMConfProfileTxPSDRowStatus RowStatus 592 } 594 vdslLineMCMConfProfileTxPSDNumber OBJECT-TYPE 595 SYNTAX Unsigned32 (1..4096) 596 MAX-ACCESS not-accessible 597 STATUS current 598 DESCRIPTION 599 "The index for this mask descriptor entry." 600 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 602 vdslLineMCMConfProfileTxPSDTone OBJECT-TYPE 603 SYNTAX Unsigned32 (1..4096) 604 MAX-ACCESS read-create 605 STATUS current 606 DESCRIPTION 607 "The tone index for which the PSD is being specified." 608 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 609 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 611 vdslLineMCMConfProfileTxPSDPSD OBJECT-TYPE 612 SYNTAX Unsigned32 613 UNITS "0.5dBm/Hz" 614 MAX-ACCESS read-create 615 STATUS current 616 DESCRIPTION 617 "Power Spectral Density level in steps of 0.5dBm/Hz with 618 an offset of -140dBm/Hz." 619 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 620 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 622 vdslLineMCMConfProfileTxPSDRowStatus OBJECT-TYPE 623 SYNTAX RowStatus 624 MAX-ACCESS read-create 625 STATUS current 626 DESCRIPTION 627 "This object is used to create a new row or modify or 628 delete an existing row in this table. 630 A profile activated by setting this object to `active'. 631 When `active' is set, the system will validate the profile. 633 None of the columns in this row may be modified while the 634 row is in the 'active' state. 636 Before a profile can be deleted or taken out of 637 service, (by setting this object to `destroy' or 638 `notInService') it must be first unreferenced 639 from all associated lines." 640 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 642 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 643 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 644 MAX-ACCESS not-accessible 645 STATUS current 646 DESCRIPTION 647 "This table contains transmit maximum PSD mask descriptor 648 configuration information for a VDSL line. Each entry in 649 this table reflects the configuration for one tone within 650 a multiple carrier modulation (MCM) VDSL modem. These 651 entries are defined by a manager and can be used to 652 configure the VDSL line. 654 If an entry in this table is referenced by a line which 655 does not use MCM, it has no effect on the operation of that 656 line. 658 All read-create objects defined in this MIB module SHOULD be 659 stored persistently." 660 ::= { vdslLineExtMCMMibObjects 5 } 662 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 663 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "Each entry consists of a transmit PSD mask descriptor, 668 which defines the maximum power spectral density (PSD) 670 for a tone." 671 INDEX { vdslLineConfProfileName, 672 vdslLineMCMConfProfileMaxTxPSDNumber } 673 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 675 VdslLineMCMConfProfileMaxTxPSDEntry ::= 676 SEQUENCE 677 { 678 vdslLineMCMConfProfileMaxTxPSDNumber Unsigned32, 679 vdslLineMCMConfProfileMaxTxPSDTone Unsigned32, 680 vdslLineMCMConfProfileMaxTxPSDPSD Unsigned32, 681 vdslLineMCMConfProfileMaxTxPSDRowStatus RowStatus 682 } 684 vdslLineMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 685 SYNTAX Unsigned32 (1..4096) 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "The index for this band descriptor entry." 690 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 692 vdslLineMCMConfProfileMaxTxPSDTone OBJECT-TYPE 693 SYNTAX Unsigned32 (1..4096) 694 MAX-ACCESS read-create 695 STATUS current 696 DESCRIPTION 697 "The tone index for which the PSD is being specified. 698 There must not be multiple rows defined, for a particular 699 profile, with the same value for this field." 700 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 701 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 703 vdslLineMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 704 SYNTAX Unsigned32 705 UNITS "0.5dBm/Hz" 706 MAX-ACCESS read-create 707 STATUS current 708 DESCRIPTION 709 "Power Spectral Density level in steps of 0.5dBm/Hz with 710 an offset of -140dBm/Hz." 711 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 712 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 714 vdslLineMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 715 SYNTAX RowStatus 716 MAX-ACCESS read-create 717 STATUS current 718 DESCRIPTION 719 "This object is used to create a new row or modify or 720 delete an existing row in this table. 722 A profile activated by setting this object to `active'. 723 When `active' is set, the system will validate the profile. 724 There must be only one entry in this table for each tone 725 associated with a specific profile. This will be checked 726 during the validation process. 728 None of the columns in this row may be modified while the 729 row is in the 'active' state. 731 Before a profile can be deleted or taken out of 732 service, (by setting this object to `destroy' or 733 `notInService') it must be first unreferenced 734 from all associated lines." 735 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 737 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 738 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "This table contains maximum receive PSD mask descriptor 743 configuration information for a VDSL line. Each entry in 744 this table reflects the configuration for one tone within 745 a multiple carrier modulation (MCM) VDSL modem. These 746 entries are defined by a manager and can be used to 747 configure the VDSL line. 749 If an entry in this table is referenced by a line which 750 does not use MCM, it has no effect on the operation of that 751 line. 753 All read-create objects defined in this MIB module SHOULD be 754 stored persistently." 755 ::= { vdslLineExtMCMMibObjects 6 } 757 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 758 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 759 MAX-ACCESS not-accessible 760 STATUS current 761 DESCRIPTION 762 "Each entry consists of a transmit PSD mask descriptor, 763 which defines the power spectral density (PSD) for a 764 tone." 766 INDEX { vdslLineConfProfileName, 767 vdslLineMCMConfProfileMaxRxPSDNumber } 768 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 770 VdslLineMCMConfProfileMaxRxPSDEntry ::= 771 SEQUENCE 772 { 773 vdslLineMCMConfProfileMaxRxPSDNumber Unsigned32, 774 vdslLineMCMConfProfileMaxRxPSDTone Unsigned32, 775 vdslLineMCMConfProfileMaxRxPSDPSD Unsigned32, 776 vdslLineMCMConfProfileMaxRxPSDRowStatus RowStatus 777 } 779 vdslLineMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 780 SYNTAX Unsigned32 (1..4096) 781 MAX-ACCESS not-accessible 782 STATUS current 783 DESCRIPTION 784 "The index for this band descriptor entry." 785 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 787 vdslLineMCMConfProfileMaxRxPSDTone OBJECT-TYPE 788 SYNTAX Unsigned32 (1..4096) 789 MAX-ACCESS read-create 790 STATUS current 791 DESCRIPTION 792 "The tone index for which the PSD is being specified. 793 There must not be multiple rows defined, for a particular 794 profile, with the same value for this field." 795 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 796 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 798 vdslLineMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 799 SYNTAX Unsigned32 800 UNITS "0.5dBm/Hz" 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "Power Spectral Density level in steps of 0.5dBm/Hz with 805 an offset of -140dBm/Hz." 806 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 807 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 809 vdslLineMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 810 SYNTAX RowStatus 811 MAX-ACCESS read-create 812 STATUS current 813 DESCRIPTION 814 "This object is used to create a new row or modify or 815 delete an existing row in this table. 817 A profile activated by setting this object to `active'. 818 When `active' is set, the system will validate the profile. 819 There must be only one entry in this table for each tone 820 associated with a specific profile. This will be checked 821 during the validation process. 823 None of the columns in this row may be modified while the 824 row is in the 'active' state. 826 Before a profile can be deleted or taken out of 827 service, (by setting this object to `destroy' or 828 `notInService') it must be first unreferenced 829 from all associated lines." 830 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 832 -- conformance information 834 vdslLineExtMCMConformance OBJECT IDENTIFIER ::= 835 { vdslLineExtMCMMib 2 } 836 vdslLineExtMCMGroups OBJECT IDENTIFIER ::= 837 { vdslLineExtMCMConformance 1 } 838 vdslLineExtMCMCompliances OBJECT IDENTIFIER ::= 839 { vdslLineExtMCMConformance 2 } 841 vdslLineExtMCMMibCompliance MODULE-COMPLIANCE 842 STATUS current 843 DESCRIPTION 844 "The compliance statement for SNMP entities which 845 manage VDSL interfaces." 846 MODULE -- this module 847 GROUP vdslLineExtMCMGroup 848 DESCRIPTION 849 "This group is an optional extension for VDSL lines which 850 utilize Multiple Carrier Modulation (MCM)." 851 ::= { vdslLineExtMCMCompliances 1 } 853 -- units of conformance 855 vdslLineExtMCMGroup OBJECT-GROUP 856 OBJECTS 857 { 858 vdslLineMCMConfProfileTxWindowLength, 859 vdslLineMCMConfProfileRowStatus, 860 vdslLineMCMConfProfileTxBandStart, 861 vdslLineMCMConfProfileTxBandStop, 862 vdslLineMCMConfProfileTxBandRowStatus, 863 vdslLineMCMConfProfileRxBandStart, 864 vdslLineMCMConfProfileRxBandStop, 865 vdslLineMCMConfProfileRxBandRowStatus, 866 vdslLineMCMConfProfileTxPSDTone, 867 vdslLineMCMConfProfileTxPSDPSD, 868 vdslLineMCMConfProfileTxPSDRowStatus, 869 vdslLineMCMConfProfileMaxTxPSDTone, 870 vdslLineMCMConfProfileMaxTxPSDPSD, 871 vdslLineMCMConfProfileMaxTxPSDRowStatus, 872 vdslLineMCMConfProfileMaxRxPSDTone, 873 vdslLineMCMConfProfileMaxRxPSDPSD, 874 vdslLineMCMConfProfileMaxRxPSDRowStatus 875 } 876 STATUS current 877 DESCRIPTION 878 "A collection of objects providing configuration 879 information for a VDSL line based upon multiple 880 carrier modulation modem." 881 ::= { vdslLineExtMCMGroups 1 } 883 END 885 5. Acknowledgments 887 This document contains many definitions taken from an earlier 888 draft of the VDSL MIB [RFC3728]. As such any credit for the text 889 found within should be fully attributed to the authors of that 890 document. 892 6. Security Considerations 894 There are a number of management objects defined in this MIB module 895 with a MAX-ACCESS clause of read-create. Such objects may be 896 considered sensitive or vulnerable in some network environments. 897 The support for SET operations in a non-secure environment without 898 proper protection can have a negative effect on network operations. 899 These are the tables and objects and their sensitivity/vulnerability: 901 vdslLineMCMConfProfileTable, 902 vdslLineMCMConfProfileTxWindowLength, 903 vdslLineMCMConfProfileRowStatus, 904 vdslLineMCMConfProfileTxBandTable, 905 vdslLineMCMConfProfileTxBandStart, 906 vdslLineMCMConfProfileTxBandStop, 907 vdslLineMCMConfProfileTxBandRowStatus, 908 vdslLineMCMConfProfileRxBandTable, 909 vdslLineMCMConfProfileRxBandStart, 910 vdslLineMCMConfProfileRxBandStop, 911 vdslLineMCMConfProfileRxBandRowStatus, 912 vdslLineMCMConfProfileTxPSDTable, 913 vdslLineMCMConfProfileTxPSDTone, 914 vdslLineMCMConfProfileTxPSDPSD, 915 vdslLineMCMConfProfileTxPSDRowStatus, 916 vdslLineMCMConfProfileMaxTxPSDTable 917 vdslLineMCMConfProfileMaxTxPSDTone, 918 vdslLineMCMConfProfileMaxTxPSDPSD, 919 vdslLineMCMConfProfileMaxTxPSDRowStatus, 920 vdslLineMCMConfProfileMaxRxPSDTable 921 vdslLineMCMConfProfileMaxRxPSDTone, 922 vdslLineMCMConfProfileMaxRxPSDPSD, 923 vdslLineMCMConfProfileMaxRxPSDRowStatus 925 Some of the readable objects in this MIB module (i.e., objects with a 926 MAX-ACCESS other than not-accessible) may be considered sensitive or 927 vulnerable in some network environments. 929 VDSL layer connectivity from the Vtur will permit the subscriber to 930 manipulate both the VDSL link directly and the VDSL embedded 931 operations channel (EOC) for their own loop. For example, unchecked 932 or unfiltered fluctuations initiated by the subscriber could generate 933 sufficient notifications to potentially overwhelm either the 934 management interface to the network or the element manager. 936 Additionally, allowing write access to configuration data may allow 937 an end-user to increase their service levels or affect other 938 end-users in either a positive or negative manner. For this reason, 939 the tables and objects listed above should be considered to contain 940 sensitive information. 942 SNMP versions prior to SNMPv3 did not include adequate security. 943 Even if the network itself is secure (for example by using IPSec), 944 even then, there is no control as to who on the secure network is 945 allowed to access and GET/SET (read/change/create/delete) the objects 946 in this MIB module. 948 It is RECOMMENDED that implementers consider the security features as 949 provided by the SNMPv3 framework (see [RFC3410], section 8), 950 including full support for the SNMPv3 cryptographic mechanisms (for 951 authentication and privacy). 953 Further, deployment of SNMP versions prior to SNMPv3 is NOT 954 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 955 enable cryptographic security. It is then a customer/operator 956 responsibility to ensure that the SNMP entity giving access to an 957 instance of a MIB module which utilizes the textual conventions 958 defined in this MIB module is properly configured to give access to 959 the objects only to those principals (users) that have legitimate 960 rights to indeed GET or SET (change/create/delete) them. 962 7. IANA Considerations 963 The IANA is kindly requested to assign the value of the 964 MODULE-IDENTITY. The authors suggest transmission 228, 965 see section 4. 967 8. References 969 8.1. Normative References 971 [DSLFTR57] DSL Forum TR-057, "VDSL Network Element Management", 972 February 2003. 974 [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing 975 (TM); Access transmission systems on metallic access 976 cables; Very high speed Digital Subscriber Line (VDSL); 977 Part 1: Functional requirements", October 1999. 979 [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing 980 (TM); Access transmission systems on metallic access 981 cables; Very high speed Digital Subscriber Line (VDSL); 982 Part 1: Transceiver specification", February 2001. 984 [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line 985 foundation", November 2001. 987 [ITU9971] ITU-T G.997.1, "Physical layer management for Digital 988 Subscriber Line (DSL) Transceivers", July 1999. 990 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 991 Requirement Levels", BCP 14, RFC 2119, March 1997. 993 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 994 J., Rose, M. and S. Waldbusser, "Structure of 995 Management Information Version 2 (SMIv2)", STD 58, RFC 996 2578, April 1999. 998 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 999 J., Rose, M. and S. Waldbusser, "Textual Conventions 1000 for SMIv2", STD 58, RFC 2579, April 1999. 1002 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1003 J., Rose, M. and S. Waldbusser, "Conformance 1004 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1006 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 1007 Group MIB", RFC 2863, June 2000. 1009 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 1010 Very High Speed Digital Subscriber Lines (VDSL)", RFC 1011 3728, February 2004. 1013 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 1014 Subscriber Line (VDSL) Metallic Interface, Part 1: 1015 Functional Requirements and Common Specification", 1016 February 2001. 1018 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 1019 2: Technical Specification for a Single-Carrier 1020 Modulation (SCM) Transceiver", November 2001. 1022 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 1023 3: Technical Specification for a Multi-Carrier 1024 Modulation (MCM) Transceiver", November 2000. 1026 8.2. Informative References 1028 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 1029 Access Control Model (VACM) for the Simple Network 1030 Management Protocol (SNMP)", RFC 3415, December 2002. 1032 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1033 "Introduction and Applicability Statements for 1034 Internet-Standard Management Framework", RFC 3410, 1035 December 2002. 1037 Authors' Addresses 1039 Menachem Dodge 1040 ECI Telecom Ltd. 1041 30 Hasivim St. 1042 Petach Tikva 49517, 1043 Israel. 1045 Phone: +972 3 926 8421 1046 Fax: +972 3 928 7342 1047 Email: mbdodge@ieee.org 1049 Bob Ray 1050 PESA Switching Systems, Inc. 1051 330-A Wynn Drive 1052 Huntsville, AL 35805 1053 USA 1055 Phone: +1 256 726 9200 ext. 142 1056 Fax: +1 256 726 9271 1057 EMail: rray@pesa.com 1059 Full Copyright Statement 1061 Copyright (C) The Internet Society (2004). This document is subject 1062 to the rights, licenses and restrictions contained in BCP 78 and 1063 except as set forth therein, the authors retain all their rights. 1065 This document and the information contained herein are provided on an 1066 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1067 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1068 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1069 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1070 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1071 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1073 Intellectual Property 1075 The IETF takes no position regarding the validity or scope of any 1076 Intellectual Property Rights or other rights that might be claimed to 1077 pertain to the implementation or use of the technology described in 1078 this document or the extent to which any license under such rights 1079 might or might not be available; nor does it represent that it has 1080 made any independent effort to identify any such rights. Information 1081 on the procedures with respect to rights in RFC documents can be 1082 found in BCP 78 and BCP 79. 1084 Copies of IPR disclosures made to the IETF Secretariat and any 1085 assurances of licenses to be made available, or the result of an 1086 attempt made to obtain a general license or permission for the use 1087 of such proprietary rights by implementers or users of this 1088 specification can be obtained from the IETF on-line IPR repository 1089 at http://www.ietf.org/ipr. 1091 The IETF invites any interested party to bring to its attention any 1092 copyrights, patents or patent applications, or other proprietary 1093 rights that may cover technology that may be required to implement 1094 this standard. Please address the information to the IETF at ietf- 1095 ipr@ietf.org. 1097 Acknowledgement 1099 Funding for the RFC Editor function is currently provided by the 1100 Internet Society.