idnits 2.17.1 draft-ietf-adslmib-hc-tc-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. 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 ** Missing expiration date. The document expiration date should appear on the first and last page. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 59 lines 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. == 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 (November 2003) is 7468 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2026' is defined on line 417, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2495 (Obsoleted by RFC 3895) -- Obsolete informational reference (is this intentional?): RFC 2496 (Obsoleted by RFC 3896) -- Obsolete informational reference (is this intentional?): RFC 3276 (Obsoleted by RFC 4319) Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group B. Ray 2 Category: Internet Draft PESA Switching Systems 3 R. Abbi 4 Alcatel 5 November 2003 7 High Capacity Textual Conventions for MIB Modules Using 8 Performance History Based on 15 Minute Intervals 9 draft-ietf-adslmib-hc-tc-07.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at: 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at: 30 http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The Internet Society (2003). All Rights Reserved. 36 Abstract 38 This document presents a set of High Capacity Textual Conventions 39 for use in MIB modules which require performance history based upon 40 15 minute intervals. The Textual Conventions defined in this 41 document extend the conventions presented in RFC 3593 to 64 bit 42 resolution using the conventions presented in RFC 2856. 44 Table of Contents 46 1. The Internet-Standard Management Framework .................... 2 47 2. Overview ...................................................... 2 48 3. Definitions ................................................... 3 49 4. Intellectual Property ......................................... 8 50 5. Normative References .......................................... 8 51 6. Informative References ........................................ 8 52 7. Security Considerations ....................................... 9 53 8. Acknowledgements .............................................. 9 54 9. Authors' Addresses ............................................ 9 55 10. Full Copyright Statement ...................................... 10 57 1. The Internet-Standard Management Framework 59 For a detailed overview of the documents that describe the current 60 Internet-Standard Management Framework, please refer to section 7 of 61 RFC 3410 [RFC3410]. 63 Managed objects are accessed via a virtual information store, termed 64 the Management Information Base or MIB. MIB objects are generally 65 accessed through the Simple Network Management Protocol (SNMP). 66 Objects in the MIB are defined using the mechanisms defined in the 67 Structure of Management Information (SMI). This memo specifies a 68 MIB module that is compliant to the SMIv2, which is described in STD 69 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 70 2580 [RFC2580]. 72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 74 document are to be interpreted as described in [RFC2119]. 76 2. Overview 78 In cases where a manager must obtain performance history data about 79 the behavior of equipment it manages, several strategies can be 80 followed in the design of a MIB module that represents the managed 81 equipment, including: 83 - The agent counts events on a continuous basis and, whenever 84 desired, the manager obtains the value of the event counter and 85 adjusts its understanding of the history of events at the agent. 87 - The agent allocates events to 'buckets' where each bucket 88 represents an interval of time. 90 Telecommunications equipment often makes use of the latter strategy. 91 For such equipment the standard practice is that history data is 92 maintained by the agent in terms of 15-minute intervals [T1.231]. 94 MIB modules for collecting performance history based on 15-minute 95 intervals have been defined for the DS1/E1 [RFC2495], DS3/E3 96 [RFC2496], SONET/SDH [RFC3592], ADSL [RFC2662], HDLS2 and SHDSL 98 [RFC3276] interface types. These MIB modules use a common set of 99 textual conventions defined in [RFC3593]. 101 A need has arisen to define 64-bit versions of the textual 102 conventions in [RFC3593]. Ideally, these high-capacity textual 103 conventions would be based on a Gauge64 or Unsigned64 data type, but 104 unfortunately no such types exist in SMIv2. The next best choice 105 would be to base them on the CounterBasedGauge64 textual convention 106 presented in [RFC2856], but that is not possible either since SMIv2 107 allows only base types to be used in defining textual conventions. 108 Therefore, the textual conventions presented in this memo are based 109 directly on the Counter64 type, like those in [RFC2856]. They are 110 subject to the following limitations: 112 - The MAX-ACCESS of objects defined using these textual conventions 113 must be read-only, because the MAX-ACCESS of the underlying 114 Counter64 type is read-only. 116 - No sub-range can be specified in object definitions using these 117 textual conventions, because sub-ranges are not allowed on 118 Counter64 objects. 120 - No DEFVAL clause can be specified in object definitions using 121 these textual conventions, because DEFVALs are not allowed on 122 Counter64 objects. 124 - Objects defined using these textual conventions cannot be used 125 in an INDEX clause, because there is no INDEX clause mapping 126 defined for objects of type Counter64. 128 Use of the textual conventions presented in this memo assumes the 129 following: 131 - The agent supports 15 minute based history counters. 133 - The agent is capable of keeping a history of 96 intervals of 15 134 minute performance data. 136 - The agent may optionally support performance data aggregating the 137 history intervals. 139 - The agent will keep separate tables for the current interval, the 140 history intervals, and the total aggregates. 142 3. Definitions 144 HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN 146 IMPORTS 147 MODULE-IDENTITY, 148 Counter64, 149 Unsigned32, 150 mib-2 FROM SNMPv2-SMI 151 TEXTUAL-CONVENTION FROM SNMPv2-TC; 153 hcPerfHistTCMIB MODULE-IDENTITY 154 LAST-UPDATED "200311240000Z" -- November 24, 2003 155 ORGANIZATION "ADSLMIB Working Group" 156 CONTACT-INFO "WG-email: adslmib@ietf.org 157 Info: https://www1.ietf.org/mailman/listinfo/adslmib 159 Chair: Mike Sneed 160 Sand Channel Systems 161 Postal: P.O. Box 37324 162 Raleigh NC 27627-7324 163 USA 164 Email: sneedmike@hotmail.com 165 Phone: +1 206 600 7022 167 Co-editor: Bob Ray 168 PESA Switching Systems, Inc. 169 Postal: 330-A Wynn Drive 170 Huntsville, AL 35805 171 USA 172 Email: rray@pesa.com 173 Phone: +1 256 726 9200 ext. 142 175 Co-editor: Rajesh Abbi 176 Alcatel USA 177 Postal: 2912 Wake Forest Road 178 Raleigh, NC 27609-7860 179 USA 180 Email: Rajesh.Abbi@alcatel.com 181 Phone: +1 919 850 6194 182 " 183 DESCRIPTION 184 "This MIB Module provides Textual Conventions to be 185 used by systems supporting 15 minute based performance 186 history counts that require high-capacity counts. 188 Copyright (C) The Internet Society (2003). This version 189 of this MIB module is part of RFC XXXX: see the RFC 190 itself for full legal notices." 191 -- RFC Ed.: replace XXXX with assigned number & remove this note 192 REVISION "200311240000Z" -- November 24, 2003 193 DESCRIPTION "Initial version, published as RFC XXXX." 194 -- RFC Ed.: replace XXXX with assigned number & remove this note 195 ::= { mib-2 YYYY } 196 -- RFC Ed.: replace YYYY with IANA-assigned number & remove this note 198 HCPerfValidIntervals ::= TEXTUAL-CONVENTION 199 STATUS current 200 DESCRIPTION 201 "The number of near end intervals for which data was 202 collected. The value of an object with an 203 HCPerfValidIntervals syntax will be 96 unless the 204 measurement was (re-)started within the last 1440 minutes, 205 in which case the value will be the number of complete 15 206 minute intervals for which the agent has at least some data. 207 In certain cases (e.g., in the case where the agent is a 208 proxy) it is possible that some intervals are unavailable. 209 In this case, this interval is the maximum interval number 210 for which data is available." 211 SYNTAX Integer32 (0..96) 213 HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION 214 STATUS current 215 DESCRIPTION 216 "The number of near end intervals for which no data is 217 available. The value of an object with an 218 HCPerfInvalidIntervals syntax will typically be zero except 219 in cases where the data for some intervals are not available 220 (e.g., in proxy situations)." 221 SYNTAX Integer32 (0..96) 223 HCPerfTimeElapsed ::= TEXTUAL-CONVENTION 224 STATUS current 225 DESCRIPTION 226 "The number of seconds that have elapsed since the beginning 227 of the current measurement period. If, for some reason, 228 such as an adjustment in the system's time-of-day clock or 229 the addition of a leap second, the duration of the current 230 interval exceeds the maximum value, the agent will return 231 the maximum value. 233 For 15 minute intervals, the range is limited to (0..899). 234 For 24 hour intervals, the range is limited to (0..86399)." 235 SYNTAX Integer32 (0..86399) 237 HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION 238 STATUS current 239 DESCRIPTION 240 "This convention defines a range of values that may be set 241 in a fault threshold alarm control. As the number of 242 seconds in a 15-minute interval numbers at most 900, 243 objects of this type may have a range of 0...900, where the 244 value of 0 disables the alarm." 245 SYNTAX Unsigned32 (0..900) 247 HCPerfCurrentCount ::= TEXTUAL-CONVENTION 248 STATUS current 249 DESCRIPTION 250 "A gauge associated with a performance measurement in a 251 current 15 minute measurement interval. The value of an 252 object with an HCPerfCurrentCount syntax starts from zero 253 and is increased when associated events occur, until the 254 end of the 15 minute interval. At that time the value of 255 the gauge is stored in the first 15 minute history 256 interval, and the gauge is restarted at zero. In the case 257 where the agent has no valid data available for the 258 current interval, the corresponding object instance is not 259 available and upon a retrieval request a corresponding 260 error message shall be returned to indicate that this 261 instance does not exist. 263 This count represents a non-negative integer, which 264 may increase or decrease, but shall never exceed 2^64-1 265 (18446744073709551615 decimal), nor fall below 0. The 266 The value of an object with HCPerfCurrentCount syntax 267 assumes its maximum value whenever the underlying count 268 exceeds 2^64-1. If the underlying count subsequently 269 decreases below 2^64-1 (due, e.g., to a retroactive 270 adjustment as a result of entering or exiting unavailable 271 time), then the object's value also decreases. 273 Note that this TC is not strictly supported in SMIv2, 274 because the 'always increasing' and 'counter wrap' 275 semantics associated with the Counter64 base type are not 276 preserved. It is possible that management applications 277 which rely solely upon the (Counter64) ASN.1 tag to 278 determine object semantics will mistakenly operate upon 279 objects of this type as they would for Counter64 objects. 281 This textual convention represents a limited and short- 282 term solution, and may be deprecated as a long term 283 solution is defined and deployed to replace it." 284 SYNTAX Counter64 286 HCPerfIntervalCount ::= TEXTUAL-CONVENTION 287 STATUS current 288 DESCRIPTION 289 "A gauge associated with a performance measurement in 290 a previous 15 minute measurement interval. In the case 291 where the agent has no valid data available for a 292 particular interval, the corresponding object instance is 293 not available and upon a retrieval request a corresponding 294 error message shall be returned to indicate that this 295 instance does not exist. 297 Let X be an object with HCPerfIntervalCount syntax. 298 Let Y be an object with HCPerfCurrentCount syntax. 299 Let Z be an object with HCPerfTotalCount syntax. 300 Then, In a system supporting a history of n intervals with 301 X(1) and X(n) the most and least recent intervals 302 respectively, the following applies at the end of a 15 303 minute interval: 305 - discard the value of X(n) 306 - the value of X(i) becomes that of X(i-1) 307 for n >= i > 1 309 - the value of X(1) becomes that of Y. 310 - the value of Z, if supported, is adjusted. 312 This count represents a non-negative integer, which 313 may increase or decrease, but shall never exceed 2^64-1 314 (18446744073709551615 decimal), nor fall below 0. The 315 The value of an object with HCPerfIntervalCount syntax 316 assumes its maximum value whenever the underlying count 317 exceeds 2^64-1. If the underlying count subsequently 318 decreases below 2^64-1 (due, e.g., to a retroactive 319 adjustment as a result of entering or exiting unavailable 320 time), then the value of the object also decreases. 322 Note that this TC is not strictly supported in SMIv2, 323 because the 'always increasing' and 'counter wrap' 324 semantics associated with the Counter64 base type are not 325 preserved. It is possible that management applications 326 which rely solely upon the (Counter64) ASN.1 tag to 327 determine object semantics will mistakenly operate upon 328 objects of this type as they would for Counter64 objects. 330 This textual convention represents a limited and short- 331 term solution, and may be deprecated as a long term 332 solution is defined and deployed to replace it." 333 SYNTAX Counter64 335 HCPerfTotalCount ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION 338 "A gauge representing the aggregate of previous valid 15 339 minute measurement intervals. Intervals for which no 340 valid data was available are not counted. 342 This count represents a non-negative integer, which 343 may increase or decrease, but shall never exceed 2^64-1 344 (18446744073709551615 decimal), nor fall below 0. The 345 The value of an object with HCPerfTotalCount syntax 346 assumes its maximum value whenever the underlying count 347 exceeds 2^64-1. If the underlying count subsequently 348 decreases below 2^64-1 (due, e.g., to a retroactive 349 adjustment as a result of entering or exiting unavailable 350 time), then the object's value also decreases. 352 Note that this TC is not strictly supported in SMIv2, 353 because the 'always increasing' and 'counter wrap' 354 semantics associated with the Counter64 base type are not 355 preserved. It is possible that management applications 356 which rely solely upon the (Counter64) ASN.1 tag to 357 determine object semantics will mistakenly operate upon 358 objects of this type as they would for Counter64 objects. 360 This textual convention represents a limited and short- 361 term solution, and may be deprecated as a long term 362 solution is defined and deployed to replace it." 363 SYNTAX Counter64 364 END 366 4. Intellectual Property 368 The IETF takes no position regarding the validity or scope of any 369 intellectual property or other rights that might be claimed to 370 pertain to the implementation or use of the technology described in 371 this document or the extent to which any license under such rights 372 might or might not be available; neither does it represent that it 373 has made any effort to identify any such rights. Information on the 374 IETF's procedures with respect to rights in standards-track and 375 standards-related documentation can be found in BCP-11. Copies of 376 claims of rights made available for publication and any assurances 377 of licenses to be made available, or the result of an attempt made 378 to obtain a general license or permission for the use of such 379 proprietary rights by implementors or users of this specification 380 can be obtained from the IETF Secretariat. 382 The IETF invites any interested party to bring to its attention any 383 copyrights, patents or patent applications, or other proprietary 384 rights which may cover technology that may be required to practice 385 this standard. Please address the information to the IETF Executive 386 Director. 388 5. Normative References 390 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 391 Requirement Levels", BCP 14, RFC 2119, March 1997. 393 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 394 Rose, M. and S. Waldbusser, "Structure of Management 395 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 396 1999. 398 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 399 Rose, M. and S. Waldbusser, "Textual Conventions for 400 SMIv2", STD 58, RFC 2579, April 1999. 402 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 403 Rose, M. and S. Waldbusser, "Conformance Statements for 404 SMIv2", STD 58, RFC 2580, April 1999. 406 6. Informative References 408 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 409 "Introduction and Applicability Statements for Internet- 410 Standard Management Framework", RFC 3410, December 2002. 412 [T1.231] American National Standard for Telecommunications - 413 Digital Hierarchy - Layer 1 In-Service Digital 414 Transmission Performance Monitoring, ANSI T1.231-1997, 415 September 1997. 417 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 418 3", BCP 9, RFC 2026, October 1996. 420 [RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1, 421 E1, DS2 and E2 Interface Types", RFC 2495, January 1999. 423 [RFC2496] Fowler, D., "Definitions of Managed Objects for the 424 DS3/E3 Interface Type", RFC 2496, January 1999. 426 [RFC3592] Tesink, K., "Definitions of Managed Objects for the 427 Synchronous Optical Network/Synchronous Digital 428 Hierachy (SONET/SDH) Interface Type", RFC 3592, 429 November 2003. 431 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 432 for the ADSL Lines", RFC 2662, August 1999. 434 [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual 435 Conventions for Additional High Capacity Data Types", 436 RFC2856, June 2000. 438 [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects 439 for High Bit-rate DSL - 2nd Generation (HDSL2) and 440 Single-Pair High-Speed Digital Subscriber Line (SHDSL) 441 Lines", RFC3276, May 2002. 443 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 444 Performance History Based on 15 Minute Intervals", RFC 445 3593, November 2003. 447 7. Security Considerations 449 This module does not define any management objects. Instead, it 450 defines a set of textual conventions which may be used by other 451 MIB modules to define management objects. 453 Meaningful security considerations can only be written in the MIB 454 modules that define management objects. This document has 455 therefore no impact on the security of the Internet. 457 8. Acknowledgements 459 This document borrows tremendously from [RFC3593] and [RFC2856]. 460 As such, any credit for the text found within should be fully 461 attributed to the authors of those documents. 463 9. Authors' Addresses 465 Bob Ray 466 PESA Switching Systems, Inc. 467 330-A Wynn Drive 468 Huntsville, AL 35805 469 USA 471 Phone: +1 256 726 9200 ext. 142 472 Fax: +1 256 726 9271 473 EMail: rray@pesa.com 475 Rajesh Abbi 476 Alcatel USA 477 2912 Wake Forest Road 478 Raleigh, NC 27609-7860 479 USA 481 Phone: +1 919 850 6194 482 EMail: Rajesh.Abbi@alcatel.com 484 10. Full Copyright Statement 486 Copyright (C) The Internet Society (2003). All Rights Reserved. 487 This document and translations of it may be copied and furnished to 488 others, and derivative works that comment on or otherwise explain it 489 or assist in its implementation may be prepared, copied, published 490 and distributed, in whole or in part, without restriction of any 491 kind, provided that the above copyright notice and this paragraph 492 are included on all such copies and derivative works. However, this 493 document itself may not be modified in any way, such as by removing 494 the copyright notice or references to the Internet Society or other 495 Internet organizations, except as needed for the purpose of 496 developing Internet standards in which case the procedures for 497 copyrights defined in the Internet Standards process must be 498 followed, or as required to translate it into languages other than 499 English. 501 The limited permissions granted above are perpetual and will not be 502 revoked by the Internet Society or its successors or assigns. 504 This document and the information contained herein is provided on an 505 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 506 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 507 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 508 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 509 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.