| 1 |
<pre>Network Working Group K. Tesink, Editor |
| 2 |
Request for Comments: 2493 Bellcore |
| 3 |
Category: Standards Track January 1999 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Textual Conventions for MIB Modules Using Performance History</span> |
| 7 |
<span class="h1">Based on 15 Minute Intervals</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This document specifies an Internet standards track protocol for the |
| 12 |
Internet community, and requests discussion and suggestions for |
| 13 |
improvements. Please refer to the current edition of the "Internet |
| 14 |
Official Protocol Standards" (STD 1) for the standardization state |
| 15 |
and status of this protocol. Distribution of this memo is unlimited. |
| 16 |
|
| 17 |
Copyright Notice |
| 18 |
|
| 19 |
Copyright (C) The Internet Society (1999). All Rights Reserved. |
| 20 |
|
| 21 |
Abstract |
| 22 |
|
| 23 |
This document defines a set of Textual Conventions for MIB modules |
| 24 |
which make use of performance history data based on 15 minute |
| 25 |
intervals. |
| 26 |
|
| 27 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Table of Contents</span> |
| 28 |
|
| 29 |
<a href="#section-1">1</a> Table of Contents ..................................... <a href="#page-1">1</a> |
| 30 |
<a href="#section-2">2</a> Introduction .......................................... <a href="#page-1">1</a> |
| 31 |
<a href="#section-3">3</a> Note on Invalid Data and Proxy ........................ <a href="#page-2">2</a> |
| 32 |
<a href="#section-4">4</a> Note on xyzTimeElapsed ................................ <a href="#page-3">3</a> |
| 33 |
<a href="#section-5">5</a> Note on xyzValidIntervals ............................. <a href="#page-3">3</a> |
| 34 |
<a href="#section-6">6</a> Definitions ........................................... <a href="#page-3">3</a> |
| 35 |
<a href="#section-7">7</a> Acknowledgments ....................................... <a href="#page-7">7</a> |
| 36 |
<a href="#section-8">8</a> References ............................................ <a href="#page-7">7</a> |
| 37 |
<a href="#section-9">9</a> Security Considerations ............................... <a href="#page-8">8</a> |
| 38 |
<a href="#section-10">10</a> IANA Considerations .................................. <a href="#page-8">8</a> |
| 39 |
<a href="#section-11">11</a> Author's Address ..................................... <a href="#page-8">8</a> |
| 40 |
<a href="#section-12">12</a> Intellectual Property ................................ <a href="#page-8">8</a> |
| 41 |
<a href="#section-13">13</a> Full Copyright Statement ............................. <a href="#page-9">9</a> |
| 42 |
|
| 43 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span> |
| 44 |
|
| 45 |
In cases where a manager must obtain performance history data about |
| 46 |
the behavior of equipment it manages several strategies can be |
| 47 |
followed in the design of a MIB that represents the managed |
| 48 |
equipment, including: |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Tesink, Ed. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 55 |
|
| 56 |
|
| 57 |
0 The agent counts events on a continuous basis and, |
| 58 |
whenever desired, the manager obtains the value of the event |
| 59 |
counter and adjusts its understanding of the history of events |
| 60 |
at the agent. |
| 61 |
|
| 62 |
0 The agent allocates events to 'buckets' where each bucket |
| 63 |
represents an interval of time. |
| 64 |
|
| 65 |
Telecommunications equipment often makes use of the latter strategy. |
| 66 |
See [<a href="#ref-3" title=""Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types"">3</a>][4][<a href="#ref-5" title=""Definitions of Managed Objects for the SONET/SDH Interface Type"">5</a>] for examples. In particular, for this equipment it is |
| 67 |
common that history data is maintained by the agent in terms of |
| 68 |
fifteen minute intervals. |
| 69 |
|
| 70 |
This memo does not attempt to compare the relative merits of |
| 71 |
different strategies to obtain history data. Differences may include |
| 72 |
polling policy, the amount of management traffic between manager and |
| 73 |
agent, agent simplicity, and 'data currentness' of the data obtained |
| 74 |
by the manager. MIB designers should consider these aspects when |
| 75 |
choosing a particular strategy in a MIB design. Instead, this memo |
| 76 |
provides definitions that can be used in MIB modules that require |
| 77 |
history data based on fifteen minute intervals. |
| 78 |
|
| 79 |
When designing a MIB module, it is often useful to define new types |
| 80 |
similar to those defined in the SMI [<a href="#ref-2" title=""Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)"">2</a>]. In comparison to a type |
| 81 |
defined in the SMI, each of these new types has a different name, a |
| 82 |
similar syntax, but a more precise semantics. These newly defined |
| 83 |
types are termed textual conventions, and are used for the |
| 84 |
convenience of humans reading the MIB module. This is done through |
| 85 |
Textual Conventions as defined in <a href="./rfc1903">RFC1903</a>[<a href="#ref-1" title=""Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)"">1</a>]. It is the purpose of |
| 86 |
this document to define the set of textual conventions to be used |
| 87 |
when performance history based on 15 minute intervals is kept. See |
| 88 |
for example the Trunk MIB modules [<a href="#ref-3" title=""Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types"">3</a>][4][<a href="#ref-5" title=""Definitions of Managed Objects for the SONET/SDH Interface Type"">5</a>]. |
| 89 |
|
| 90 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Note on Invalid Data and Proxy</span> |
| 91 |
|
| 92 |
In this document, the word proxy is meant to indicate an application |
| 93 |
which receives SNMP messages and replies to them on behalf of the |
| 94 |
devices where the actual implementation resides, e.g., DS3/E3 |
| 95 |
interfaces. The proxy will have already collected the information |
| 96 |
about the DS3/E3 interfaces into its local database and may not |
| 97 |
necessarily forward requests to the actual DS3/E3 interface. It is |
| 98 |
expected in such an application that there are periods of time where |
| 99 |
the proxy is not communicating with the DS3/E3 interfaces. In these |
| 100 |
instances the proxy will not necessarily have up-to-date |
| 101 |
configuration information and will most likely have missed the |
| 102 |
collection of some data. Missed data collection may result in some |
| 103 |
intervals in the interval table being unavailable. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Tesink, Ed. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Note on xyzTimeElapsed</span> |
| 114 |
|
| 115 |
While xyzTimeElapsed is defined as having a maximum there may be |
| 116 |
cases (e.g., an adjustment in the system's time-of-day clock) where |
| 117 |
the actual value of the current interval would exceed this maximum |
| 118 |
value. |
| 119 |
|
| 120 |
Suppose that an agent which aligns its 15-minute measurement |
| 121 |
intervals to 15-minute time-of-day ("wall clock") boundaries has a |
| 122 |
time-of-day clock that systematically gains time, and that a manager |
| 123 |
periodically corrects the clock by setting it back. |
| 124 |
|
| 125 |
It is assumed that the agent's time-of-day clock is reasonably |
| 126 |
accurate, say within a few seconds per day. Thus, the manager's |
| 127 |
periodic clock adjustments will normally be small, and if done |
| 128 |
frequently enough, need not ever exceed 10 seconds. In this case all |
| 129 |
interval durations will be within the allowed tolerance and none need |
| 130 |
be marked invalid, _if_ the ANSI procedure of ending measurement |
| 131 |
intervals at 15-minute time-of-day boundaries is followed [<a href="#ref-6" title="ANSI T1.231-1997">6</a>]. |
| 132 |
|
| 133 |
If the time-of-day clock is systematically adjusted in small |
| 134 |
increments, then always ending measurement intervals at 15-minute |
| 135 |
time-of-day boundaries will result in the long term in the correct |
| 136 |
number of intervals with the correct average duration, irrespective |
| 137 |
of whether the clock is moved ahead or moved back. Thus, if, for |
| 138 |
some reason, such as an adjustment in the system's time-of-day clock, |
| 139 |
the current interval exceeds the maximum value, it is considered |
| 140 |
acceptable that the agent will return the maximum value. |
| 141 |
|
| 142 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Note on xyzValidIntervals</span> |
| 143 |
|
| 144 |
The overall constraint on <n> is 1 =< n =< 96. Any additional |
| 145 |
constraints on n must be defined in the DESCRIPTION clause (e.g., see |
| 146 |
[<a href="#ref-5" title=""Definitions of Managed Objects for the SONET/SDH Interface Type"">5</a>]). |
| 147 |
|
| 148 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Definitions</span> |
| 149 |
|
| 150 |
PerfHist-TC-MIB DEFINITIONS ::= BEGIN |
| 151 |
|
| 152 |
IMPORTS |
| 153 |
MODULE-IDENTITY, |
| 154 |
Gauge32, mib-2 |
| 155 |
FROM SNMPv2-SMI |
| 156 |
TEXTUAL-CONVENTION |
| 157 |
FROM SNMPv2-TC; |
| 158 |
|
| 159 |
|
| 160 |
perfHistTCMIB MODULE-IDENTITY |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Tesink, Ed. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 167 |
|
| 168 |
|
| 169 |
LAST-UPDATED "9811071100Z" |
| 170 |
ORGANIZATION "IETF AToMMIB and TrunkMIB WGs" |
| 171 |
CONTACT-INFO |
| 172 |
"Kaj Tesink |
| 173 |
Postal: Bellcore |
| 174 |
331 Newman Springs Road |
| 175 |
Red Bank, NJ 07701 |
| 176 |
USA |
| 177 |
Tel: +1 732 758 5254 |
| 178 |
Fax: +1 732 758 2269 |
| 179 |
E-mail: [email protected]" |
| 180 |
DESCRIPTION |
| 181 |
"This MIB Module provides Textual Conventions |
| 182 |
to be used by systems supporting 15 minute |
| 183 |
based performance history counts." |
| 184 |
::= { mib-2 58 } |
| 185 |
|
| 186 |
|
| 187 |
|
| 188 |
|
| 189 |
-- The Textual Conventions defined below are organized |
| 190 |
-- alphabetically |
| 191 |
|
| 192 |
-- Use of these TCs assumes the following: |
| 193 |
-- 0 The agent supports 15 minute based history |
| 194 |
-- counters. |
| 195 |
-- 0 The agent is capable of keeping a history of n |
| 196 |
-- intervals of 15 minute performance data. The |
| 197 |
-- value of n is defined by the specific MIB |
| 198 |
-- module but shall be 0 < n =< 96. |
| 199 |
-- 0 The agent may optionally support performance |
| 200 |
-- data aggregating the history intervals. |
| 201 |
-- 0 The agent will keep separate tables for the |
| 202 |
-- current interval, the history intervals, and |
| 203 |
-- the total aggregates. |
| 204 |
-- 0 The agent will keep the following objects. |
| 205 |
-- If performance data is kept for multiple instances |
| 206 |
-- of a measured entity, then |
| 207 |
-- these objects are applied to each instance of |
| 208 |
-- the measured entity (e.g., interfaces). |
| 209 |
-- |
| 210 |
|
| 211 |
|
| 212 |
-- xyzTimeElapsed OBJECT-TYPE |
| 213 |
-- SYNTAX INTEGER (0..899) |
| 214 |
-- MAX-ACCESS read-only |
| 215 |
-- STATUS current |
| 216 |
-- DESCRIPTION |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Tesink, Ed. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 223 |
|
| 224 |
|
| 225 |
-- "The number of seconds that have elapsed since |
| 226 |
-- the beginning of the current measurement period. |
| 227 |
-- If, for some reason, such as an adjustment in the |
| 228 |
-- system's time-of-day clock, the current interval |
| 229 |
-- exceeds the maximum value, the agent will return |
| 230 |
-- the maximum value." |
| 231 |
-- ::= { xxx } |
| 232 |
|
| 233 |
-- xyzValidIntervals OBJECT-TYPE |
| 234 |
-- SYNTAX INTEGER (0..<n>) |
| 235 |
-- MAX-ACCESS read-only |
| 236 |
-- STATUS current |
| 237 |
-- DESCRIPTION |
| 238 |
-- "The number of previous near end intervals |
| 239 |
-- for which data was collected. |
| 240 |
-- [ The overall constraint on <n> is 1 =< n =< 96; ] |
| 241 |
-- [ Define any additional constraints on <n> here. ] |
| 242 |
-- The value will be <n> unless the measurement was |
| 243 |
-- (re-)started within the last (<n>*15) minutes, in which |
| 244 |
-- case the value will be the number of complete 15 |
| 245 |
-- minute intervals for which the agent has at least |
| 246 |
-- some data. In certain cases (e.g., in the case |
| 247 |
-- where the agent is a proxy) it is possible that some |
| 248 |
-- intervals are unavailable. In this case, this |
| 249 |
-- interval is the maximum interval number for |
| 250 |
-- which data is available." |
| 251 |
-- ::= { xxx } |
| 252 |
|
| 253 |
-- xyzInvalidIntervals OBJECT-TYPE |
| 254 |
-- SYNTAX INTEGER (0..<n>) |
| 255 |
-- MAX-ACCESS read-only |
| 256 |
-- STATUS current |
| 257 |
-- DESCRIPTION |
| 258 |
-- "The number of intervals in the range from |
| 259 |
-- 0 to xyzValidIntervals for which no |
| 260 |
-- data is available. This object will typically |
| 261 |
-- be zero except in cases where the data for some |
| 262 |
-- intervals are not available (e.g., in proxy |
| 263 |
-- situations)." |
| 264 |
-- ::= { xxx } |
| 265 |
|
| 266 |
PerfCurrentCount ::= TEXTUAL-CONVENTION |
| 267 |
STATUS current |
| 268 |
DESCRIPTION |
| 269 |
"A counter associated with a |
| 270 |
performance measurement in a current 15 |
| 271 |
minute measurement interval. The value |
| 272 |
of this counter starts from zero and is |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Tesink, Ed. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 279 |
|
| 280 |
|
| 281 |
increased when associated events occur, |
| 282 |
until the end of the 15 minute interval. |
| 283 |
At that time the value of the counter is |
| 284 |
stored in the first 15 minute history |
| 285 |
interval, and the CurrentCount is |
| 286 |
restarted at zero. In the |
| 287 |
case where the agent has no valid data |
| 288 |
available for the current interval the |
| 289 |
corresponding object instance is not |
| 290 |
available and upon a retrieval request |
| 291 |
a corresponding error message shall be |
| 292 |
returned to indicate that this instance |
| 293 |
does not exist (for example, a noSuchName |
| 294 |
error for SNMPv1 and a noSuchInstance for |
| 295 |
SNMPv2 GET operation)." |
| 296 |
SYNTAX Gauge32 |
| 297 |
|
| 298 |
PerfIntervalCount ::= TEXTUAL-CONVENTION |
| 299 |
STATUS current |
| 300 |
DESCRIPTION |
| 301 |
"A counter associated with a |
| 302 |
performance measurement in a previous |
| 303 |
15 minute measurement interval. In the |
| 304 |
case where the agent has no valid data |
| 305 |
available for a particular interval the |
| 306 |
corresponding object instance is not |
| 307 |
available and upon a retrieval request |
| 308 |
a corresponding error message shall be |
| 309 |
returned to indicate that this instance |
| 310 |
does not exist (for example, a noSuchName |
| 311 |
error for SNMPv1 and a noSuchInstance for |
| 312 |
SNMPv2 GET operation). |
| 313 |
In a system supporting |
| 314 |
a history of n intervals with |
| 315 |
IntervalCount(1) and IntervalCount(n) the |
| 316 |
most and least recent intervals |
| 317 |
respectively, the following applies at |
| 318 |
the end of a 15 minute interval: |
| 319 |
- discard the value of IntervalCount(n) |
| 320 |
- the value of IntervalCount(i) becomes that |
| 321 |
of IntervalCount(i-1) for n >= i > 1 |
| 322 |
- the value of IntervalCount(1) becomes that |
| 323 |
of CurrentCount |
| 324 |
- the TotalCount, if supported, is adjusted." |
| 325 |
SYNTAX Gauge32 |
| 326 |
|
| 327 |
PerfTotalCount ::= TEXTUAL-CONVENTION |
| 328 |
STATUS current |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Tesink, Ed. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 335 |
|
| 336 |
|
| 337 |
DESCRIPTION |
| 338 |
"A counter associated with a |
| 339 |
performance measurements aggregating the |
| 340 |
previous valid 15 minute measurement |
| 341 |
intervals. (Intervals for which no valid |
| 342 |
data was available are not counted)" |
| 343 |
SYNTAX Gauge32 |
| 344 |
|
| 345 |
|
| 346 |
END |
| 347 |
|
| 348 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span> |
| 349 |
|
| 350 |
This document is a product of the AToMMIB and TrunkMIB Working |
| 351 |
Groups. |
| 352 |
|
| 353 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 354 |
|
| 355 |
[<a id="ref-1">1</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, |
| 356 |
"Textual Conventions for Version 2 of the Simple Network |
| 357 |
Management Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996. |
| 358 |
|
| 359 |
[<a id="ref-2">2</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, |
| 360 |
"Structure of Management Information for Version 2 of the Simple |
| 361 |
Network Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>, January 1996. |
| 362 |
|
| 363 |
[<a id="ref-3">3</a>] Fowler, D., "Definitions of Managed Objects for the DS1, E1, DS2 |
| 364 |
and E2 Interface Types", <a href="./rfc2495">RFC 2495</a>, January 1999. |
| 365 |
|
| 366 |
[<a id="ref-4">4</a>] Fowler, D., "Definitions of Managed Objects for the DS3/E3 |
| 367 |
Interface Type", <a href="./rfc2496">RFC 2496</a>, January 1999. |
| 368 |
|
| 369 |
[<a id="ref-5">5</a>] Tesink, K., "Definitions of Managed Objects for the SONET/SDH |
| 370 |
Interface Type", Work in Progress. |
| 371 |
|
| 372 |
[<a id="ref-6">6</a>] American National Standard for Telecommunications - Digital |
| 373 |
Hierarchy - Layer 1 In-Service Digital Transmission Performance |
| 374 |
Monitoring, ANSI T1.231-1997, September 1997. |
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Tesink, Ed. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span> |
| 394 |
|
| 395 |
This memo defines textual conventions for use in other MIB modules. |
| 396 |
Security issues for these MIB modules are addressed in the memos |
| 397 |
defining those modules. |
| 398 |
|
| 399 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span> |
| 400 |
|
| 401 |
Prior to publication of this memo as an RFC, IANA is requested to |
| 402 |
make a suitable OBJECT IDENTIFIER assignment. |
| 403 |
|
| 404 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Author's Address</span> |
| 405 |
|
| 406 |
Kaj Tesink |
| 407 |
Bellcore |
| 408 |
331 Newman Springs Road |
| 409 |
P.O. Box 7020 |
| 410 |
Red Bank, NJ 07701-7020 |
| 411 |
|
| 412 |
Phone: (732) 758-5254 |
| 413 |
EMail: [email protected] |
| 414 |
|
| 415 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Intellectual Property</span> |
| 416 |
|
| 417 |
The IETF takes no position regarding the validity or scope of any |
| 418 |
intellectual property or other rights that might be claimed to |
| 419 |
pertain to the implementation or use of the technology described in |
| 420 |
this document or the extent to which any license under such rights |
| 421 |
might or might not be available; neither does it represent that it |
| 422 |
has made any effort to identify any such rights. Information on the |
| 423 |
IETF's procedures with respect to rights in standards-track and |
| 424 |
standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of |
| 425 |
claims of rights made available for publication and any assurances of |
| 426 |
licenses to be made available, or the result of an attempt made to |
| 427 |
obtain a general license or permission for the use of such |
| 428 |
proprietary rights by implementors or users of this specification can |
| 429 |
be obtained from the IETF Secretariat. |
| 430 |
|
| 431 |
The IETF invites any interested party to bring to its attention any |
| 432 |
copyrights, patents or patent applications, or other proprietary |
| 433 |
rights which may cover technology that may be required to practice |
| 434 |
this standard. Please address the information to the IETF Executive |
| 435 |
Director. |
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Tesink, Ed. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2493">RFC 2493</a> 15 Minute Based Performance History TCs January 1999</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Full Copyright Statement</span> |
| 450 |
|
| 451 |
Copyright (C) The Internet Society (1999). All Rights Reserved. |
| 452 |
|
| 453 |
This document and translations of it may be copied and furnished to |
| 454 |
others, and derivative works that comment on or otherwise explain it |
| 455 |
or assist in its implementation may be prepared, copied, published |
| 456 |
and distributed, in whole or in part, without restriction of any |
| 457 |
kind, provided that the above copyright notice and this paragraph are |
| 458 |
included on all such copies and derivative works. However, this |
| 459 |
document itself may not be modified in any way, such as by removing |
| 460 |
the copyright notice or references to the Internet Society or other |
| 461 |
Internet organizations, except as needed for the purpose of |
| 462 |
developing Internet standards in which case the procedures for |
| 463 |
copyrights defined in the Internet Standards process must be |
| 464 |
followed, or as required to translate it into languages other than |
| 465 |
English. |
| 466 |
|
| 467 |
The limited permissions granted above are perpetual and will not be |
| 468 |
revoked by the Internet Society or its successors or assigns. |
| 469 |
|
| 470 |
This document and the information contained herein is provided on an |
| 471 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 472 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 473 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 474 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 475 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 476 |
|
| 477 |
|
| 478 |
|
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
Tesink, Ed. Standards Track [Page 9] |
| 501 |
</pre> |