draft-ietf-adslmib-hc-tc-07.txt   rfc3705.txt 
Network Working Group B. Ray Network Working Group B. Ray
Category: Internet Draft PESA Switching Systems Request for Comments: 3705 PESA Switching Systems
R. Abbi Category: Standards Track R. Abbi
Alcatel Alcatel
November 2003 February 2004
High Capacity Textual Conventions for MIB Modules Using High Capacity Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals Performance History Based on 15 Minute Intervals
draft-ietf-adslmib-hc-tc-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at:
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at:
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document presents a set of High Capacity Textual Conventions This document presents a set of High Capacity Textual Conventions for
for use in MIB modules which require performance history based upon use in MIB modules which require performance history based upon 15
15 minute intervals. The Textual Conventions defined in this minute intervals. The Textual Conventions defined in this document
document extend the conventions presented in RFC 3593 to 64 bit extend the conventions presented in RFC 3593 to 64 bit resolution
resolution using the conventions presented in RFC 2856. using the conventions presented in RFC 2856.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework .................... 2 1. The Internet-Standard Management Framework . . . . . . . . . . 2
2. Overview ...................................................... 2 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Definitions ................................................... 3 3. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Intellectual Property ......................................... 8 4. Intellectual Property Statement. . . . . . . . . . . . . . . . 8
5. Normative References .......................................... 8 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Informative References ........................................ 8 5.1. Normative References . . . . . . . . . . . . . . . . . . 8
7. Security Considerations ....................................... 9 5.2. Informative References . . . . . . . . . . . . . . . . . 9
8. Acknowledgements .............................................. 9 6. Security Considerations. . . . . . . . . . . . . . . . . . . . 10
9. Authors' Addresses ............................................ 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
10. Full Copyright Statement ...................................... 10 8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10
9. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 11
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a Structure of Management Information (SMI). This memo specifies a MIB
MIB module that is compliant to the SMIv2, which is described in STD module that is compliant to the SMIv2, which is described in STD 58,
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
2580 [RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Overview 2. Overview
In cases where a manager must obtain performance history data about In cases where a manager must obtain performance history data about
the behavior of equipment it manages, several strategies can be the behavior of equipment it manages, several strategies can be
followed in the design of a MIB module that represents the managed followed in the design of a MIB module that represents the managed
skipping to change at page 3, line 30 skipping to change at page 3, line 22
Counter64 type is read-only. Counter64 type is read-only.
- No sub-range can be specified in object definitions using these - No sub-range can be specified in object definitions using these
textual conventions, because sub-ranges are not allowed on textual conventions, because sub-ranges are not allowed on
Counter64 objects. Counter64 objects.
- No DEFVAL clause can be specified in object definitions using - No DEFVAL clause can be specified in object definitions using
these textual conventions, because DEFVALs are not allowed on these textual conventions, because DEFVALs are not allowed on
Counter64 objects. Counter64 objects.
- Objects defined using these textual conventions cannot be used - Objects defined using these textual conventions cannot be used in
in an INDEX clause, because there is no INDEX clause mapping an INDEX clause, because there is no INDEX clause mapping defined
defined for objects of type Counter64. for objects of type Counter64.
Use of the textual conventions presented in this memo assumes the Use of the textual conventions presented in this memo assumes the
following: following:
- The agent supports 15 minute based history counters. - The agent supports 15 minute based history counters.
- The agent is capable of keeping a history of 96 intervals of 15 - The agent is capable of keeping a history of 96 intervals of 15
minute performance data. minute performance data.
- The agent may optionally support performance data aggregating the - The agent may optionally support performance data aggregating the
skipping to change at page 4, line 4 skipping to change at page 3, line 48
history intervals, and the total aggregates. history intervals, and the total aggregates.
3. Definitions 3. Definitions
HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Counter64, Counter64,
Unsigned32, Unsigned32,
Integer32,
mib-2 FROM SNMPv2-SMI mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
hcPerfHistTCMIB MODULE-IDENTITY hcPerfHistTCMIB MODULE-IDENTITY
LAST-UPDATED "200311240000Z" -- November 24, 2003 LAST-UPDATED "200402030000Z" -- February 3, 2004
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-7324 Raleigh NC 27627-7324
USA USA
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
skipping to change at page 4, line 31 skipping to change at page 4, line 28
Co-editor: Bob Ray Co-editor: Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive Postal: 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Email: rray@pesa.com Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi Co-editor: Rajesh Abbi
Alcatel USA Alcatel USA
Postal: 2912 Wake Forest Road Postal: 2301 Sugar Bush Road
Raleigh, NC 27609-7860 Raleigh, NC 27612-3339
USA USA
Email: Rajesh.Abbi@alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194 Phone: +1 919 850 6194
" "
DESCRIPTION DESCRIPTION
"This MIB Module provides Textual Conventions to be "This MIB Module provides Textual Conventions to be
used by systems supporting 15 minute based performance used by systems supporting 15 minute based performance
history counts that require high-capacity counts. history counts that require high-capacity counts.
Copyright (C) The Internet Society (2003). This version Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC 3705: see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200311240000Z" -- November 24, 2003
DESCRIPTION "Initial version, published as RFC XXXX." REVISION "200402030000Z" -- February 3, 2004
::= { mib-2 YYYY } DESCRIPTION "Initial version, published as RFC 3705."
::= { mib-2 107 }
HCPerfValidIntervals ::= TEXTUAL-CONVENTION HCPerfValidIntervals ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of near end intervals for which data was "The number of near end intervals for which data was
collected. The value of an object with an collected. The value of an object with an
HCPerfValidIntervals syntax will be 96 unless the HCPerfValidIntervals syntax will be 96 unless the
measurement was (re-)started within the last 1440 minutes, measurement was (re-)started within the last 1440 minutes,
in which case the value will be the number of complete 15 in which case the value will be the number of complete 15
minute intervals for which the agent has at least some data. minute intervals for which the agent has at least some data.
skipping to change at page 6, line 15 skipping to change at page 6, line 20
interval, and the gauge is restarted at zero. In the case interval, and the gauge is restarted at zero. In the case
where the agent has no valid data available for the where the agent has no valid data available for the
current interval, the corresponding object instance is not current interval, the corresponding object instance is not
available and upon a retrieval request a corresponding available and upon a retrieval request a corresponding
error message shall be returned to indicate that this error message shall be returned to indicate that this
instance does not exist. instance does not exist.
This count represents a non-negative integer, which This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1 may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The (18446744073709551615 decimal), nor fall below 0. The
The value of an object with HCPerfCurrentCount syntax value of an object with HCPerfCurrentCount syntax
assumes its maximum value whenever the underlying count assumes its maximum value whenever the underlying count
exceeds 2^64-1. If the underlying count subsequently exceeds 2^64-1. If the underlying count subsequently
decreases below 2^64-1 (due, e.g., to a retroactive decreases below 2^64-1 (due, e.g., to a retroactive
adjustment as a result of entering or exiting unavailable adjustment as a result of entering or exiting unavailable
time), then the object's value also decreases. time), then the object's value also decreases.
Note that this TC is not strictly supported in SMIv2, Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not semantics associated with the Counter64 base type are not
preserved. It is possible that management applications preserved. It is possible that management applications
skipping to change at page 6, line 47 skipping to change at page 7, line 4
DESCRIPTION DESCRIPTION
"A gauge associated with a performance measurement in "A gauge associated with a performance measurement in
a previous 15 minute measurement interval. In the case a previous 15 minute measurement interval. In the case
where the agent has no valid data available for a where the agent has no valid data available for a
particular interval, the corresponding object instance is particular interval, the corresponding object instance is
not available and upon a retrieval request a corresponding not available and upon a retrieval request a corresponding
error message shall be returned to indicate that this error message shall be returned to indicate that this
instance does not exist. instance does not exist.
Let X be an object with HCPerfIntervalCount syntax. Let X be an object with HCPerfIntervalCount syntax.
Let Y be an object with HCPerfCurrentCount syntax. Let Y be an object with HCPerfCurrentCount syntax.
Let Z be an object with HCPerfTotalCount syntax. Let Z be an object with HCPerfTotalCount syntax.
Then, In a system supporting a history of n intervals with Then, in a system supporting a history of n intervals with
X(1) and X(n) the most and least recent intervals X(1) and X(n) the most and least recent intervals
respectively, the following applies at the end of a 15 respectively, the following applies at the end of a 15
minute interval: minute interval:
- discard the value of X(n) - discard the value of X(n)
- the value of X(i) becomes that of X(i-1) - the value of X(i) becomes that of X(i-1)
for n >= i > 1 for n >= i > 1
- the value of X(1) becomes that of Y. - the value of X(1) becomes that of Y.
- the value of Z, if supported, is adjusted. - the value of Z, if supported, is adjusted.
This count represents a non-negative integer, which This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1 may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The (18446744073709551615 decimal), nor fall below 0. The
The value of an object with HCPerfIntervalCount syntax value of an object with HCPerfIntervalCount syntax
assumes its maximum value whenever the underlying count assumes its maximum value whenever the underlying count
exceeds 2^64-1. If the underlying count subsequently exceeds 2^64-1. If the underlying count subsequently
decreases below 2^64-1 (due, e.g., to a retroactive decreases below 2^64-1 (due, e.g., to a retroactive
adjustment as a result of entering or exiting unavailable adjustment as a result of entering or exiting unavailable
time), then the value of the object also decreases. time), then the value of the object also decreases.
Note that this TC is not strictly supported in SMIv2, Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not semantics associated with the Counter64 base type are not
preserved. It is possible that management applications preserved. It is possible that management applications
skipping to change at page 7, line 40 skipping to change at page 7, line 51
HCPerfTotalCount ::= TEXTUAL-CONVENTION HCPerfTotalCount ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A gauge representing the aggregate of previous valid 15 "A gauge representing the aggregate of previous valid 15
minute measurement intervals. Intervals for which no minute measurement intervals. Intervals for which no
valid data was available are not counted. valid data was available are not counted.
This count represents a non-negative integer, which This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1 may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The (18446744073709551615 decimal), nor fall below 0. The
The value of an object with HCPerfTotalCount syntax value of an object with HCPerfTotalCount syntax
assumes its maximum value whenever the underlying count assumes its maximum value whenever the underlying count
exceeds 2^64-1. If the underlying count subsequently exceeds 2^64-1. If the underlying count subsequently
decreases below 2^64-1 (due, e.g., to a retroactive decreases below 2^64-1 (due, e.g., to a retroactive
adjustment as a result of entering or exiting unavailable adjustment as a result of entering or exiting unavailable
time), then the object's value also decreases. time), then the object's value also decreases.
Note that this TC is not strictly supported in SMIv2, Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not semantics associated with the Counter64 base type are not
preserved. It is possible that management applications preserved. It is possible that management applications
which rely solely upon the (Counter64) ASN.1 tag to which rely solely upon the (Counter64) ASN.1 tag to
determine object semantics will mistakenly operate upon determine object semantics will mistakenly operate upon
objects of this type as they would for Counter64 objects. objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short- This textual convention represents a limited and short-
term solution, and may be deprecated as a long term term solution, and may be deprecated as a long term
solution is defined and deployed to replace it." solution is defined and deployed to replace it."
SYNTAX Counter64 SYNTAX Counter64
END END
4. Intellectual Property 4. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances of
of licenses to be made available, or the result of an attempt made licenses to be made available, or the result of an attempt made to
to obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification can
can be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
5. Normative References 5. References
5.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
6. Informative References 5.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[T1.231] American National Standard for Telecommunications - [T1.231] American National Standard for Telecommunications - Digital
Digital Hierarchy - Layer 1 In-Service Digital Hierarchy - Layer 1 In-Service Digital Transmission
Transmission Performance Monitoring, ANSI T1.231-1997, Performance Monitoring, ANSI T1.231-1997, September 1997.
September 1997.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1, [RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1,
E1, DS2 and E2 Interface Types", RFC 2495, January 1999. E1, DS2 and E2 Interface Types", RFC 2495, January 1999.
[RFC2496] Fowler, D., "Definitions of Managed Objects for the [RFC2496] Fowler, D., "Definitions of Managed Objects for the DS3/E3
DS3/E3 Interface Type", RFC 2496, January 1999. Interface Type", RFC 2496, January 1999.
[RFC3592] Tesink, K., "Definitions of Managed Objects for the [RFC3592] Tesink, K., "Definitions of Managed Objects for the
Synchronous Optical Network/Synchronous Digital Synchronous Optical Network/Synchronous Digital Hierarchy
Hierachy (SONET/SDH) Interface Type", RFC 3592, (SONET/SDH) Interface Type", RFC 3592, November 2003.
November 2003.
[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects for
for the ADSL Lines", RFC 2662, August 1999. the ADSL Lines", RFC 2662, August 1999.
[RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual
Conventions for Additional High Capacity Data Types", Conventions for Additional High Capacity Data Types", RFC
RFC2856, June 2000. 2856, June 2000.
[RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for
for High Bit-rate DSL - 2nd Generation (HDSL2) and High Bit-rate DSL - 2nd Generation (HDSL2) and Single-Pair
Single-Pair High-Speed Digital Subscriber Line (SHDSL) High-Speed Digital Subscriber Line (SHDSL) Lines", RFC
Lines", RFC3276, May 2002. 3276, May 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals", RFC
3593, November 2003. 3593, November 2003.
7. Security Considerations 6. Security Considerations
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other defines a set of textual conventions which may be used by other MIB
MIB modules to define management objects. modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. This document has modules that define management objects. This document has therefore
therefore no impact on the security of the Internet. no impact on the security of the Internet.
8. Acknowledgements 7. Acknowledgements
This document borrows tremendously from [RFC3593] and [RFC2856]. This document borrows tremendously from [RFC3593] and [RFC2856]. As
As such, any credit for the text found within should be fully such, any credit for the text found within should be fully attributed
attributed to the authors of those documents. to the authors of those documents.
9. Authors' Addresses 8. Authors' Addresses
Bob Ray Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
EMail: rray@pesa.com EMail: rray@pesa.com
Rajesh Abbi Rajesh Abbi
Alcatel USA Alcatel USA
2912 Wake Forest Road 2301 Sugar Bush Road
Raleigh, NC 27609-7860 Raleigh, NC 27612-3339
USA USA
Phone: +1 919 850 6194 Phone: +1 919 850 6194
EMail: Rajesh.Abbi@alcatel.com EMail: Rajesh.Abbi@alcatel.com
10. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph are
are included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/