idnits 2.17.1 draft-ietf-atommib-perfhistTC-04.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 document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 9. Security Considerations' ) ** 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.) (A line matching the expected section header was found, but with an unexpected indentation: ' 10. IANA Considerations' ) ** The document seems to lack an Authors' Addresses Section. ** There are 7 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [1]), 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 == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (September 1, 1998) is 9368 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 section? '2' on line 305 looks like a reference -- Missing reference section? '1' on line 298 looks like a reference -- Missing reference section? '3' on line 312 looks like a reference -- Missing reference section? '4' on line 316 looks like a reference -- Missing reference section? '5' on line 320 looks like a reference -- Missing reference section? '6' on line 323 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Textual Conventions for MIB Modules Using Performance History 3 Based on 15 Minute Intervals 5 September 1, 1998 7 Kaj Tesink (editor) 8 Bellcore 9 kaj@cc.bellcore.com 11 1. Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are 14 working documents of the Internet Engineering Task Force 15 (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as 23 ``work in progress.'' 25 To learn the current status of any Internet-Draft, please 26 check the ``1id-abstracts.txt'' listing contained in the 27 Internet- Drafts Shadow Directories on ftp.ietf.org (US East 28 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 29 or munnari.oz.au (Pacific Rim). 31 Copyright Notice 33 Copyright (C) The Internet Society (1998). All Rights 34 Reserved. 36 Abstract 38 This document defines a set of Textual Conventions for MIB 39 modules which make use of performance history data based on 15 40 minute intervals. 42 draft 15 Minute Based Performance History TCs 9/1/1998 44 2. Introduction 46 When designing a MIB module, it is often useful to define new 47 types similar to those defined in the SMI [2]. In comparison 48 to a type defined in the SMI, each of these new types has a 49 different name, a similar syntax, but a more precise 50 semantics. These newly defined types are termed textual 51 conventions, and are used for the convenience of humans 52 reading the MIB module. This is done through Textual 53 Conventions as defined in RFC1903[1]. It is the purpose of 54 this document to define the set of textual conventions to be 55 used when performance history based on 15 minute intervals is 56 kept. See for example the Trunk MIB modules [3][4][5]. 58 3. Note on Invalid Data and Proxy 60 In this document, the word proxy is meant to indicate an 61 application which receives SNMP messages and replies to them 62 on behalf of the devices where the actual implementation 63 resides, e.g., DS3/E3 interfaces. The proxy will have already 64 collected the information about the DS3/E3 interfaces into its 65 local database and may not necessarily forward requests to the 66 actual DS3/E3 interface. It is expected in such an 67 application that there are periods of time where the proxy is 68 not communicating with the DS3/E3 interfaces. In these 69 instances the proxy will not necessarily have up-to-date 70 configuration information and will most likely have missed the 71 collection of some data. Missed data collection may result in 72 some intervals in the interval table being unavailable. 74 4. Note on xyzTimeElapsed 76 While xyzTimeElapsed is defined as having a maximum there may 77 be cases (e.g., an adjustment in the system's time-of-day 78 clock) where the actual value of the current interval would 79 exceed this maximum value. 81 Suppose that an agent which aligns its 15-minute measurement 82 intervals to 15-minute time-of-day ("wall clock") boundaries 83 has a time-of-day clock that systematically gains time, and 84 that a manager periodically corrects the clock by setting it 85 back. 87 draft 15 Minute Based Performance History TCs 9/1/1998 89 It is assumed that the agent's time-of-day clock is reasonably 90 accurate, say within a few seconds per day. Thus, the 91 manager's periodic clock adjustments will normally be small, 92 and if done frequently enough, need not ever exceed 10 93 seconds. In this case all interval durations will be within 94 the allowed tolerance and none need be marked invalid, _if_ 95 the ANSI procedure of ending measurement intervals at 15- 96 minute time-of-day boundaries is followed [6]. 98 If the time-of-day clock is systematically adjusted in small 99 increments, then always ending measurement intervals at 15- 100 minute time-of-day boundaries will result in the long term in 101 the correct number of intervals with the correct average 102 duration, irrespective of whether the clock is moved ahead or 103 moved back. Thus, if, for some reason, such as an adjustment 104 in the system's time-of-day clock, the current interval 105 exceeds the maximum value, it is considered acceptable that 106 the agent will return the maximum value. 108 5. Note on xyzValidIntervals 110 The overall constraint on is 1 =< n =< 96. Any additional 111 constraints on n must be defined in the DESCRIPTION clause 112 (e.g., see [5]). 114 draft 15 Minute Based Performance History TCs 9/1/1998 116 6. Definitions 118 PerfHist-TC-MIB DEFINITIONS ::= BEGIN 120 IMPORTS 121 MODULE-IDENTITY, 122 Gauge32, mib-2 123 FROM SNMPv2-SMI 124 TEXTUAL-CONVENTION 125 FROM SNMPv2-TC; 127 perfHistTCMIB MODULE-IDENTITY 128 LAST-UPDATED "9809011100Z" 129 ORGANIZATION "IETF AToMMIB and TrunkMIB WGs" 130 CONTACT-INFO 131 "Kaj Tesink 132 Postal: Bellcore 133 331 Newman Springs Road 134 Red Bank, NJ 07701 135 USA 136 Tel: +1 732 758 5254 137 Fax: +1 732 758 2269 138 E-mail: kaj@cc.bellcore.com" 139 DESCRIPTION 140 "This MIB Module provides Textual Conventions 141 to be used by systems supporting 15 minute 142 based performance history counts." 143 ::= { mib-2 xxx } -- to be filled in by IANA 145 -- The Textual Conventions defined below are organized 146 -- alphabetically 148 -- Use of these TCs assumes the following: 149 -- 0 The agent supports 15 minute based history 150 -- counters. 151 -- 0 The agent is capable of keeping a history of n 152 -- intervals of 15 minute performance data. The 153 -- value of n is defined by the specific MIB 154 -- module but shall be 0 < n =< 96. 155 -- 0 The agent may optionally support performance 156 -- data aggregating the history intervals. 158 draft 15 Minute Based Performance History TCs 9/1/1998 160 -- 0 The agent will keep separate tables for the 161 -- current interval, the history intervals, and 162 -- the total aggregates. 163 -- 0 The agent will keep the following objects. 164 -- If performance data is kept for multiple instances 165 -- of a measured entity, then 166 -- these objects are applied to each instance of 167 -- the measured entity (e.g., interfaces). 168 -- 170 -- xyzTimeElapsed OBJECT-TYPE 171 -- SYNTAX INTEGER (0..899) 172 -- MAX-ACCESS read-only 173 -- STATUS current 174 -- DESCRIPTION 175 -- "The number of seconds that have elapsed since 176 -- the beginning of the current measurement period. 177 -- If, for some reason, such as an adjustment in the 178 -- system's time-of-day clock, the current interval 179 -- exceeds the maximum value, the agent will return 180 -- the maximum value." 181 -- ::= { xxx } 183 -- xyzValidIntervals OBJECT-TYPE 184 -- SYNTAX INTEGER (0..) 185 -- MAX-ACCESS read-only 186 -- STATUS current 187 -- DESCRIPTION 188 -- "The number of previous near end intervals 189 -- for which valid data was collected. 190 -- [ The overall constraint on is 1 =< n =< 96; ] 191 -- [ Define any additional constraints on here. ] 192 -- The value will be unless the measurement was 193 -- (re-)started within the last (*15) minutes, in which 194 -- case the value will be the number of complete 15 195 -- minute intervals for which the agent has at least 196 -- some valid data. In certain cases (e.g., in the case 197 -- where the agent is a proxy) it is possible that some 198 -- intervals are unavailable. In this case, this 199 -- interval is the maximum interval number for 200 -- which valid data is available." 201 -- ::= { xxx } 203 -- xyzInvalidIntervals OBJECT-TYPE 205 draft 15 Minute Based Performance History TCs 9/1/1998 207 -- SYNTAX INTEGER (0..) 208 -- MAX-ACCESS read-only 209 -- STATUS current 210 -- DESCRIPTION 211 -- "The number of intervals in the range from 212 -- 0 to xyzValidIntervals for which no 213 -- data is available. This object will typically 214 -- be zero except in cases where the data for some 215 -- intervals are not available (e.g., in proxy 216 -- situations)." 217 -- ::= { xxx } 219 PerfCurrentCount ::= TEXTUAL-CONVENTION 220 STATUS current 221 DESCRIPTION 222 "A counter associated with a 223 performance measurement in a current 15 224 minute measurement interval. The value 225 of this counter starts from zero and is 226 increased when associated events occur, 227 until the end of the 15 minute interval. 228 At that time the value of the counter is 229 stored in the first 15 minute history 230 interval, and the CurrentCount is 231 restarted at zero. In the 232 case where the agent has no valid data 233 available for the current interval the 234 corresponding object instance is not 235 available and upon a retrieval request 236 a corresponding error message shall be 237 returned to indicate that this instance 238 does not exist (for example, a noSuchName 239 error for SNMPv1 and a noSuchInstance for 240 SNMPv2 GET operation)." 241 SYNTAX Gauge32 243 PerfIntervalCount ::= TEXTUAL-CONVENTION 244 STATUS current 245 DESCRIPTION 246 "A counter associated with a 247 performance measurement in a previous 248 15 minute measurement interval. In the 249 case where the agent has no valid data 250 available for a particular interval the 251 corresponding object instance is not 253 draft 15 Minute Based Performance History TCs 9/1/1998 255 available and upon a retrieval request 256 a corresponding error message shall be 257 returned to indicate that this instance 258 does not exist (for example, a noSuchName 259 error for SNMPv1 and a noSuchInstance for 260 SNMPv2 GET operation). 261 In a system supporting 262 a history of n intervals with 263 IntervalCount(1) and IntervalCount(n) the 264 most and least recent intervals 265 respectively, the following applies at 266 the end of a 15 minute interval: 267 - discard the value of IntervalCount(n) 268 - the value of IntervalCount(i) becomes that 269 of IntervalCount(i-1) for n >= i > 1 270 - the value of IntervalCount(1) becomes that 271 of CurrentCount 272 - the TotalCount, if supported, is adjusted." 273 SYNTAX Gauge32 275 PerfTotalCount ::= TEXTUAL-CONVENTION 276 STATUS current 277 DESCRIPTION 278 "A counter associated with a 279 performance measurements aggregating the 280 previous valid 15 minute measurement 281 intervals. (Intervals for which no valid 282 data was available are not counted)" 283 SYNTAX Gauge32 285 END 287 draft 15 Minute Based Performance History TCs 9/1/1998 289 7. Acknowledgments 291 This document is a product of the AToMMIB and TrunkMIB Working 292 Groups. 294 draft 15 Minute Based Performance History TCs 9/1/1998 296 8. References 298 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 299 "Textual Conventions for Version 2 of the Simple Network 300 Management Protocol (SNMPv2)", RFC1903, SNMP 301 Research,Inc., Cisco Systems, Inc., Dover Beach 302 Consulting, Inc., International Network Services, January 303 1996. 305 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 306 "Structure of Management Information for Version 2 of the 307 Simple Network Management Protocol (SNMPv2)", RFC1902, 308 SNMP Research,Inc., Cisco Systems, Inc., Dover Beach 309 Consulting, Inc., International Network Services, January 310 1996. 312 [3] Fowler, D., "Definitions of Managed Objects for the DS1, 313 E1, DS2 and E2 Interface Types", RFCxxxx, Newbridge 314 Networks, ????? 1998. 316 [4] Fowler, D., "Definitions of Managed Objects for the 317 DS3/E3 Interface Type", RFCxxxx, Newbridge Networks, ???? 318 1998. 320 [5] Tesink, K., "Definitions of Managed Objects for the 321 SONET/SDH Interface Type", RFCxxxx, Bellcore, ???? 1998. 323 [6] American National Standard for Telecommunications - 324 Digital Hierarchy - Layer 1 In-Service Digital 325 Transmission Performance Monitoring, ANSI T1.231-1997, 326 September 1997. 328 draft 15 Minute Based Performance History TCs 9/1/1998 330 9. Security Considerations 332 This memo defines textual conventions for use in other MIB 333 modules. Security issues for these MIB modules are addressed 334 in the memos defining those modules. 336 10. IANA Considerations 338 Prior to publication of this memo as an RFC, IANA is requested 339 to make a suitable OBJECT IDENTIFIER assignment and update the 340 following line in the MIB: 342 ::= { mib-2 xxx } -- to be filled in by IANA 344 11. Author's Address 346 Kaj Tesink 347 Bellcore 348 331 Newman Springs Road 349 P.O. Box 7020 350 Red Bank, NJ 07701-7020 351 Phone: (732) 758-5254 352 EMail: kaj@cc.bellcore.com 354 draft 15 Minute Based Performance History TCs 9/1/1998 356 12. Full Copyright Statement 358 Copyright (C) The Internet Society (1998). All Rights 359 Reserved. 361 This document and translations of it may be copied and 362 furnished to others, and derivative works that comment on or 363 otherwise explain it or assist in its implementation may be 364 prepared, copied, published and distributed, in whole or in 365 part, without restriction of any kind, provided that the above 366 copyright notice and this paragraph are included on all such 367 copies and derivative works. However, this document itself 368 may not be modified in any way, such as by removing the 369 copyright notice or references to the Internet Society or 370 other Internet organizations, except as needed for the purpose 371 of developing Internet standards in which case the procedures 372 for copyrights defined in the Internet Standards process must 373 be followed, or as required to translate it into languages 374 other than English. 376 The limited permissions granted above are perpetual and will 377 not be revoked by the Internet Society or its successors or 378 assigns. 380 This document and the information contained herein is provided 381 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 382 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 383 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 384 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 385 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 386 PARTICULAR PURPOSE." 387 draft 15 Minute Based Performance History TCs 9/1/1998 389 Table of Contents 391 1 Status of this Memo ................................... 1 392 2 Introduction .......................................... 2 393 3 Note on Invalid Data and Proxy ........................ 2 394 4 Note on xyzTimeElapsed ................................ 2 395 5 Note on xyzValidIntervals ............................. 3 396 6 Definitions ........................................... 4 397 7 Acknowledgments ....................................... 8 398 8 References ............................................ 9 399 9 Security Considerations ............................... 10 400 10 IANA Considerations .................................. 10 401 11 Author's Address ..................................... 10 402 12 Full Copyright Statement ............................. 11