idnits 2.17.1 draft-ietf-adslmib-hc-tc-01.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 ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 7) being 68 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == 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 (June 2002) is 7986 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: 'RFC2622' is mentioned on line 119, but not defined == Unused Reference: 'RFC2662' is defined on line 431, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2493 (Obsoleted by RFC 3593) -- 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 2558 (Obsoleted by RFC 3592) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 14 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 June 2002 7 High Capacity Textual Conventions for MIB Modules Using 8 Performance History Based on 15 Minute Intervals 9 draft-ietf-adslmib-hc-tc-01.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]. Internet-Drafts are 15 working documents of the Internet Engineering Task Force (IETF), its 16 areas, and its working groups. Note that other groups may also 17 distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other documents 21 at any time. It is inappropriate to use Internet-Drafts as 22 reference material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at: 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at: 28 http://www.ietf.org/shadow.html. 30 Copyright Notice 32 Copyright (C) The Internet Society (2002). All Rights Reserved. 34 Abstract 36 This document presents a set of Textual Conventions for MIB modules 37 which extends the conventions presented in RFC2493 to 64 bit 38 resolution using the conventions presented in RFC2856. 40 Table of Contents 42 1. The SNMP Management Framework ................................... 2 43 2. Overview ........................................................ 3 44 3. Definitions ..................................................... 4 45 References ...................................................... 8 46 Security Considerations ......................................... 10 47 IANA Considerations ............................................. 10 48 Acknowledgements ................................................ 10 49 Intellectual Property Notice .................................... 10 50 Authors' Addresses .............................................. 10 51 Full Copyright Statement ........................................ 11 53 1. The SNMP Management Framework 55 The SNMP Management Framework presently consists of five major 56 components: 58 o An overall architecture, described in RFC 2571 [RFC2571]. 60 o Mechanisms for describing and naming objects and events for the 61 purpose of management. The first version of this Structure of 62 Management Information (SMI) is called SMIv1 and described in STD 63 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 64 [RFC1215]. The second version, called SMIv2, is described in STD 65 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, 66 RFC 2580 [RFC2580]. 68 o Message protocols for transferring management information. The 69 first version of the SNMP message protocol is called SNMPv1 and 70 described in STD 15, RFC 1157 [RFC1157]. A second version of the 71 SNMP message protocol, which is not an Internet standards track 72 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 73 and RFC 1906 [RFC1906]. The third version of the message 74 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 75 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 77 o Protocol operations for accessing management information. The 78 first set of protocol operations and associated PDU formats is 79 described in STD 15, RFC 1157 [RFC1157]. A second set of 80 protocol operations and associated PDU formats is described in 81 RFC 1905 [RFC1905]. 83 o A set of fundamental applications described in RFC 2573 [RFC2573] 84 and the view-based access control mechanism described in RFC 2575 85 [RFC2575]. 87 A more detailed introduction to the current SNMP Management Framework 88 can be found in RFC 2570 [RFC2570]. 90 Managed objects are accessed via a virtual information store, termed 91 the Management Information Base or MIB. Objects in the MIB are 92 defined using the mechanisms defined in the SMI. 94 This memo specifies a MIB module that is compliant to the SMIv2. The 95 textual conventions defined in this MIB module cannot be translated 96 to SMIv1 since the Counter64 type does not exist in SMIv1. 98 2. Overview 100 In cases where a manager must obtain performance history data about 101 the behavior of equipment it manages several strategies can be 102 followed in the design of a MIB that represents the managed 103 equipment, including: 105 0 The agent counts events on a continuous basis and, 106 whenever desired, the manager obtains the value of the event 107 counter and adjusts its understanding of the history of events 108 at the agent. 110 0 The agent allocates events to 'buckets' where each bucket 111 represents an interval of time. 113 Telecommunications equipment often makes use of the latter strategy. 114 For such equipment the standard practice is that history data is 115 maintained by the agent in terms of 15-minute intervals [T1.231]. 117 MIB modules for collecting performance history based on 15-minute 118 intervals have been defined for the DS1/E1 [RFC2495], DS3/E3 119 [RFC2496], SONET/SDH [RFC2558], and ADSL [RFC2622] interface types. 120 These MIB modules use a common set of textual conventions defined in 121 [RFC2493]. Those textual conventions are based on the Gauge32 122 data type. 124 A need has arisen in connection with recent work on a VDSL MIB 125 [VDSL-MIB] to define 64-bit versions of the textual conventions 126 in [RFC2493]. Ideally, these high-capacity textual conventions would 127 be based on a Gauge64 or Unsigned64 data type, but unfortunately no 128 such types exist in SMIv2. The next best choice would be to base 129 them on the CounterBasedGauge64 textual convention presented in 130 [RFC2856], but that is not possible either since SMIv2 allows only 131 base types to be used textual conventions. Therefore the textual 132 conventions presented in this memo are based directly on the 133 Counter64 type, like those in [RFC2856]. They are subject to the 134 following limitations: 136 - The MAX-ACCESS of objects defined using these textual conventions 137 must be read-only, because the MAX-ACCESS of the underlying 138 Counter64 type is read-only. 140 - No sub-range can be specified in object definitions using these 141 textual conventions, because sub-ranges are not allowed on 142 Counter64 objects. 144 - No DEFVAL clause can be specified in object definitions using 145 these textual conventions, because DEFVALs are not allowed on 146 Counter64 objects. 148 - Objects defined using these textual conventions cannot be used 149 in an INDEX clause, because there is no INDEX clause mapping 150 defined for objects of type Counter64. 152 3. Definitions 154 HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN 156 IMPORTS 157 MODULE-IDENTITY, 158 Counter64, 159 mib-2 FROM SNMPv2-SMI 160 TEXTUAL-CONVENTION FROM SNMPv2-TC; 162 hcPerfHistTCMIB MODULE-IDENTITY 163 LAST-UPDATED "200206160000Z" -- June 16, 2002 164 ORGANIZATION "ADSLMIB Working Group" 165 CONTACT-INFO "WG-email: adslmib@ietf.org 166 Info: https://www1.ietf.org/mailman/listinfo/adslmib 168 Chair: Mike Sneed 169 Postal: P.O. Box 37324 170 Raleigh NC 27627-7324 171 Email: sneedmike@hotmail.com 173 Co-editor: Bob Ray 174 PESA Switching Systems, Inc. 175 Postal: 330-A Wynn Drive 176 Huntsville, AL 35805 USA 177 Email: rray@pesa.com 178 Phone: +1 256 726 9200 ext. 142 180 Co-editor: Rajesh Abbi 181 Alcatel USA 182 Postal: 2912 Wake Forest Road 183 Raleigh, NC 27609-7860 USA 184 Email: Rajesh.Abbi@alcatel.com 185 Phone: +1 919 850 6194 186 " 187 DESCRIPTION 188 "This MIB Module provides Textual Conventions to be 189 used by systems supporting 15 minute based performance 190 history counts that require high-capacity counts." 192 REVISION "200206160000Z" -- June 16, 2002 193 DESCRIPTION "Corrected addresses and references." 195 ::= { mib-2 xxx } -- to be assigned by IANA 197 -- The Textual Conventions defined below are organized 198 -- alphabetically 199 -- Use of these TCs assumes the following: 200 -- 0 The agent supports 15 minute based history 201 -- counters. 202 -- 0 The agent is capable of keeping a history of n 203 -- intervals of 15 minute performance data. The 204 -- value of n is defined by the specific MIB 205 -- module but shall be 0 < n =< 96. 206 -- 0 The agent may optionally support performance 207 -- data aggregating the history intervals. 208 -- 0 The agent will keep separate tables for the 209 -- current interval, the history intervals, and 210 -- the total aggregates. 211 -- 0 The agent will keep the following objects. 212 -- If performance data is kept for multiple instances 213 -- of a measured entity, then 214 -- these objects are applied to each instance of 215 -- the measured entity (e.g., interfaces). 217 -- xyzTimeElapsed OBJECT-TYPE 218 -- SYNTAX INTEGER (0..899) 219 -- MAX-ACCESS read-only 220 -- STATUS current 221 -- DESCRIPTION 222 -- "The number of seconds that have elapsed since 223 -- the beginning of the current measurement period. 224 -- If, for some reason, such as an adjustment in the 225 -- system's time-of-day clock, the current interval 226 -- exceeds the maximum value, the agent will return 227 -- the maximum value." 228 -- ::= { xxx } 230 -- xyzValidIntervals OBJECT-TYPE 231 -- SYNTAX INTEGER (0..) 232 -- MAX-ACCESS read-only 233 -- STATUS current 234 -- DESCRIPTION 235 -- "The number of previous near end intervals 236 -- for which data was collected. 237 -- [ The overall constraint on is 1 =< n =< 96; ] 238 -- [ Define any additional constraints on here. ] 239 -- The value will be unless the measurement was 240 -- (re-)started within the last (*15) minutes, in which 241 -- case the value will be the number of complete 15 242 -- minute intervals for which the agent has at least 243 -- some data. In certain cases (e.g., in the case 244 -- where the agent is a proxy) it is possible that some 245 -- intervals are unavailable. In this case, this 246 -- interval is the maximum interval number for 247 -- which data is available." 248 -- ::= { xxx } 250 -- xyzInvalidIntervals OBJECT-TYPE 251 -- SYNTAX INTEGER (0..) 252 -- MAX-ACCESS read-only 253 -- STATUS current 254 -- DESCRIPTION 255 -- "The number of intervals in the range from 256 -- 0 to xyzValidIntervals for which no 257 -- data is available. This object will typically 258 -- be zero except in cases where the data for some 259 -- intervals are not available (e.g., in proxy 260 -- situations)." 261 -- ::= { xxx } 263 -- See the notes in [RFC2493] for additional information 264 -- concerning the above objects. 266 HCPerfCurrentCount ::= TEXTUAL-CONVENTION 267 STATUS current 268 DESCRIPTION 269 "A counter associated with a performance measurement in a 270 current 15 minute measurement interval. The value of this 271 counter starts from zero and is increased when associated 272 events occur, until the end of the 15 minute interval. 273 At that time the value of the counter is stored in the 274 first 15 minute history interval, and the CurrentCount is 275 restarted at zero. In the case where the agent has no valid 276 data available for the current interval the corresponding 277 object instance is not available and upon a retrieval 278 request a corresponding error message shall be returned to 279 indicate that this instance does not exist. 281 This count represents a a non-negative integer, which 282 may increase or decrease, but shall never exceed 2^64-1 283 (18446744073709551615 decimal), nor fall below 0. The 284 The value of a HCPerfCurrentCount object assumes its 285 maximum value whenever the underlying count exceeds 286 2^64-1. If the underlying count subsequently decreases 287 below 2^64-1 (due, e.g., to a retroactive adjustment as a 288 result of entering or exiting unavailable time), then the 289 HCPerfCurrentCount object also decreases. 291 Note that this TC is not strictly supported in SMIv2, 292 because the 'always increasing' and 'counter wrap' 293 semantics associated with the Counter64 base type are not 294 preserved. It is possible that management applications 295 which rely solely upon the (Counter64) ASN.1 tag to 296 determine object semantics will mistakenly operate upon 297 objects of this type as they would for Counter64 objects. 299 This textual convention represents a limited and short-term 300 solution, and may be deprecated as a long term solution is 301 defined and deployed to replace it." 302 SYNTAX Counter64 304 HCPerfIntervalCount ::= TEXTUAL-CONVENTION 305 STATUS current 306 DESCRIPTION 307 "A counter associated with a performance measurement in 308 a previous 15 minute measurement interval. In the case 309 where the agent has no valid data available for a 310 particular interval the corresponding object instance is 311 not available and upon a retrieval request a corresponding 312 error message shall be returned to indicate that this 313 instance does not exist. 315 In a system supporting a history of n intervals with 316 IntervalCount(1) and IntervalCount(n) the most and least 317 recent intervals respectively, the following applies at 318 the end of a 15 minute interval: 320 - discard the value of IntervalCount(n) 321 - the value of IntervalCount(i) becomes that 322 of IntervalCount(i-1) for n >= i > 1 323 - the value of IntervalCount(1) becomes that 324 of CurrentCount 325 - the TotalCount, if supported, is adjusted. 327 This count represents a a non-negative integer, which 328 may increase or decrease, but shall never exceed 2^64-1 329 (18446744073709551615 decimal), nor fall below 0. The 330 The value of a HCPerfIntervalCount object assumes its 331 maximum value whenever the underlying count exceeds 332 2^64-1. If the underlying count subsequently decreases 333 below 2^64-1 (due, e.g., to a retroactive adjustment as a 334 result of entering or exiting unavailable time), then the 335 HCPerfIntervalCount object also decreases. 337 Note that this TC is not strictly supported in SMIv2, 338 because the 'always increasing' and 'counter wrap' 339 semantics associated with the Counter64 base type are not 340 preserved. It is possible that management applications 341 which rely solely upon the (Counter64) ASN.1 tag to 342 determine object semantics will mistakenly operate upon 343 objects of this type as they would for Counter64 objects. 345 This textual convention represents a limited and short-term 346 solution, and may be deprecated as a long term solution is 347 defined and deployed to replace it." 348 SYNTAX Counter64 350 HCPerfTotalCount ::= TEXTUAL-CONVENTION 351 STATUS current 352 DESCRIPTION 353 "A counter associated with a performance measurements 354 aggregating the previous valid 15 minute measurement 355 intervals. Intervals for which no valid data was 356 available are not counted. 358 This count represents a a non-negative integer, which 359 may increase or decrease, but shall never exceed 2^64-1 360 (18446744073709551615 decimal), nor fall below 0. The 361 The value of a HCPerfTotalCount object assumes its 362 maximum value whenever the underlying count exceeds 363 2^64-1. If the underlying count subsequently decreases 364 below 2^64-1 (due, e.g., to a retroactive adjustment as a 365 result of entering or exiting unavailable time), then the 366 HCPerfTotalCount object also decreases. 368 Note that this TC is not strictly supported in SMIv2, 369 because the 'always increasing' and 'counter wrap' 370 semantics associated with the Counter64 base type are not 371 preserved. It is possible that management applications 372 which rely solely upon the (Counter64) ASN.1 tag to 373 determine object semantics will mistakenly operate upon 374 objects of this type as they would for Counter64 objects. 376 This textual convention represents a limited and short-term 377 solution, and may be deprecated as a long term solution is 378 defined and deployed to replace it." 379 SYNTAX Counter64 380 END 382 Informative References 384 [T1.231] American National Standard for Telecommunications - 385 Digital Hierarchy - Layer 1 In-Service Digital 386 Transmission Performance Monitoring, ANSI T1.231-1997, 387 September 1997. 389 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 390 of Management Information for TCP/IP-based Internets", 391 STD 16, RFC 1155, May 1990. 393 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, 394 "Simple Network Management Protocol", STD 15, RFC 1157, 395 May 1990. 397 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", 398 STD 16, RFC 1212, March 1991. 400 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 401 the SNMP", RFC 1215, March 1991. 403 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 404 "Introduction to Community-based SNMPv2", RFC 1901, 405 January 1996. 407 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 408 "Protocol Operations for Version 2 of the Simple Network 409 Management Protocol (SNMPv2)", RFC 1905, January 1996. 411 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 412 "Transport Mappings for Version 2 of the Simple Network 413 Management Protocol (SNMPv2)", RFC 1906, January 1996. 415 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 416 3", BCP 9, RFC 2026, October 1996. 418 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 419 Performance History Based on 15 Minute Intervals", RFC 420 2493, January 1999. 422 [RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1, 423 E1, DS2 and E2 Interface Types", RFC 2495, January 1999. 425 [RFC2496] Fowler, D., "Definitions of Managed Objects for the 426 DS3/E3 Interface Type", RFC 2496, January 1999. 428 [RFC2558] Tesink, K., "Definitions of Managed Objects for the 429 SONET/SDH Interface Type", RFC 2558, March 1999. 431 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 432 for the ADSL Lines", RFC 2662, August 1999. 434 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 435 "Introduction to Version 3 of the Internet-standard 436 Network Management Framework", RFC 2570, April 1999. 438 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 439 Architecture for Describing SNMP Management Frameworks", 440 RFC 2571, April 1999. 442 [RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, 443 "Message Processing and Dispatching for the Simple 444 Network Management Protocol (SNMP)", RFC 2572, April 445 1999. 447 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 448 Applications", RFC 2573, April 1999. 450 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 451 (USM) for version 3 of the Simple Network Management 452 Protocol (SNMPv3)", RFC 2574, April 1999. 454 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 455 Access Control Model (VACM) for the Simple Network 456 Management Protocol (SNMP)", RFC 2575, April 1999. 458 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 459 Rose, M. and S. Waldbusser, "Structure of Management 460 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 461 1999. 463 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 464 Rose, M. and S. Waldbusser, "Textual Conventions for 465 SMIv2", STD 58, RFC 2579, April 1999. 467 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 468 Rose, M. and S. Waldbusser, "Conformance Statements for 469 SMIv2", STD 58, RFC 2580, April 1999. 471 [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual 472 Conventions for Additional High Capacity Data Types", 473 RFC2856, June 2000. 475 [VDSL-MIB] Ray, B. and R. Abbi, work in progress. 477 Security Considerations 479 This module does not define any management objects. Instead, it 480 defines a set of textual conventions which may be used by other MIB 481 modules to define management objects. 483 Meaningful security considerations can only be written in the modules 484 that define management objects. 486 IANA Considerations 488 Prior to publication of this memo as an RFC, IANA is requested to 489 make a suitable OBJECT IDENTIFIER assignment. 491 Acknowledgements 493 This document borrows tremendously from [RFC2493] and [RFC2856]. 494 As such, any credit for the text found within should be fully 495 attributed to the authors of those documents. 497 Intellectual Property Notice 499 The IETF takes no position regarding the validity or scope of any 500 intellectual property or other rights that might be claimed to 501 pertain to the implementation or use of the technology described in 502 this document or the extent to which any license under such rights 503 might or might not be available; neither does it represent that it 504 has made any effort to identify any such rights. Information on the 505 IETF's procedures with respect to rights in standards-track and 506 standards-related documentation can be found in BCP-11. Copies of 507 claims of rights made available for publication and any assurances of 508 licenses to be made available, or the result of an attempt made to 509 obtain a general license or permission for the use of such 510 proprietary rights by implementors or users of this specification can 511 be obtained from the IETF Secretariat. 513 The IETF invites any interested party to bring to its attention any 514 copyrights, patents or patent applications, or other proprietary 515 rights which may cover technology that may be required to practice 516 this standard. Please address the information to the IETF Executive 517 Director. 519 Authors' Addresses 521 Bob Ray 522 PESA Switching Systems, Inc. 523 330-A Wynn Drive 524 Huntsville, AL 35805 USA 525 Phone: +1 256 726 9200 ext. 142 526 Fax: +1 256 726 9271 527 EMail: rray@pesa.com 529 Rajesh Abbi 530 Alcatel USA 531 2912 Wake Forest Road 532 Raleigh, NC 27609-7860 USA 534 Phone: +1 919 850 6194 535 EMail: Rajesh.Abbi@alcatel.com 537 Full Copyright Statement 539 Copyright (C) The Internet Society (2002). All Rights Reserved. 541 This document and translations of it may be copied and furnished to 542 others, and derivative works that comment on or otherwise explain it 543 or assist in its implementation may be prepared, copied, published 544 and distributed, in whole or in part, without restriction of any 545 kind, provided that the above copyright notice and this paragraph are 546 included on all such copies and derivative works. However, this 547 document itself may not be modified in any way, such as by removing 548 the copyright notice or references to the Internet Society or other 549 Internet organizations, except as needed for the purpose of 550 developing Internet standards in which case the procedures for 551 copyrights defined in the Internet Standards process must be 552 followed, or as required to translate it into languages other than 553 English. 555 The limited permissions granted above are perpetual and will not be 556 revoked by the Internet Society or its successors or assigns. 558 This document and the information contained herein is provided on an 559 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 560 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 561 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 562 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 563 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.