Internet DRAFT - draft-ashoka-atmaal2-mib
draft-ashoka-atmaal2-mib
Operations and Management Area K.Ashoka
Internet Draft Cisco Systems
Document: draft-ashoka-atmaal2-mib-00.txt May 2001
Definitions of Managed Objects for
ATM Adaptation Layer 2
May 5, 2001
draft-ashoka-atmaal2-mib-00.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1].
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
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 I nternet-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.
1. Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects used for managing ATM Adaptation
Layer-2 based interfaces, devices, networks and services.
This memo is an extension to RFC 1215 [25].
2. Conventions used in this document
CID Channel Identifier
CPS Common Part SubLayer
HEC Header Error Control
PDU Protocol Data Unit
SDU Service Data Unit
STF Start Field.
VCC Virtual Channel Connection
VPI Virtual Path Identifier
VCI Virtual Channel Identifier
Textual Conventions used in this MIB are defined in [6] and [19].
3. Overview
ATM AAL2 management objects are used to manage ATM interfaces,
ATM virtual links, ATM cross-connects, AAL2 entities and AAL2
Connections supported by ATM hosts, ATM switches and ATM networks.
This section provides an overview and background of how to use this
MIB.
The purpose of this memo is primarily to manage ATM AAL2 VCs.
3.1 Background
In addition to the MIB module defined in this memo, other MIB modules
are necessary to manage ATM interfaces, links and cross-connects.
Examples include MIB II for general system and interface management
(RFC 1213 [3] and RFC 2863 [4]), the DS3 or SONET MIBs for management
of SONET and DS3 physical interfaces, and, as appropriate, MIB modules
for applications that make use of ATM, such as SMDS [28] and LAN
Emulation [27]. These MIB modules are outside the scope of this
specification.
This MIB module also requires the use of the ATM-MIB module defined
in [24] and ATM-specific textual conventions defined in [34].
The current specification of this supplemental ATM2-MIB is based on
SNMPv2-SMI.
3.2 Structure of the MIB
The managed ATM AAL2 objects are arranged into the following tables:
1. ATM AAL2 interface configuration table
2. AAL2 connection performance statistics table
3. AAL2 Channel Identifier (CID) Performance Statistics Table
3.2.1 Support of ATM AAL2 by ifTable
The AAL2 entity in an ATM device (e.g., switch or host) is managed
using the ifTable. There are additional counters specified for AAL2
than those specified in the ATM B-ICI document [21]. Specific
interpretations of ifTable for the AAL2 CPCS layer are as follows.
Object Use for AAL2 CPCS layer entity
====== ==============================
ifIndex Each AAL2 entity is represented by an ifEntry.
ifDescr Description of the AAL2 entity.
ifType The value that is allocated for AAL2 is 187.
ifMtu Set to the largest PDU size for the
AAL2 CPCS layer that can be processed
by the AAL2 entity.
ifSpeed Set to 0.
ifPhysAddress An octet string of zero length.
ifAdminStatus See [17].
ifOperStatus Assumes the value down(2) if the AAL2
layer is down.
ifLastChange See [17].
ifInOctets The number of received AAL2 CPCS PDU octets.
ifOutOctets The number of AAL2 CPCS PDU octets
transmitted.
ifInUcastPkts The number of received AAL2 CPCS PDUs passed
to a higher-layer.
ifOutUcastPkts The number of AAL2 CPCS PDUs received from a
higher-layer for transmission.
[Note: The number of AAL2 PDUs actually
transmitted is the number received from a
higher-layer for transmission minus any which
are counted by ifOutErrors and ifOutDiscards.]
ifInErrors Number of errored AAL2 CPCS PDUs received.
The types of errors counted include CRC-32 errors,
SAR time-out errors, and oversized SDU errors.
IfInUnknownProtos Set to 0.
ifInDiscards Number of received AAL2 CPCS PDUs discarded.
Possible reason may be input buffer overflow.
ifOutErrors Number of AAL2 CPCS PDUs that could not be
transmitted due to errors.
ifOutDiscards Number of AAL2 CPCS PDUs received for
transmission that are discarded. Possible
reason may be output buffer overflow.
ifInMulticastPkts Set to 0.
ifInBroadcastPkts Set to 0.
ifOutMulticastPkts Set to 0.
ifOutBroadcastPkts Set to 0.
ifName Textual name (unique on this system) of the
AAL2 entity or an octet string of zero length.
ifHighSpeed Set to 0.
ifConnectorPresent Set to false (2).
ifPromiscuousMode Set to false(2).
ifLinkUpDownTrapEnable Default is disabled (2).
ifAlias The non-volatile 'alias' name for the interface
as specified by a network manager.
3.2.2 AAL2 Connection Performance Statistics Table
An AAL2 connection table is used to provide AAL2 performance
information for each AAL2 virtual connection that is terminated
at the AAL2 entity contained within an ATM switch or host.
3.2.3 AAL2 Channel Identifier (CID) Performance Statistics Table
An AAL2 Channel Identifier(CID) performance statistics table is
used to provide Channel Identifier performance information for
AAL2 CID.
5. Definitions
AAL2-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Counter32, Counter64
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
ifIndex
FROM IF-MIB;
Aal2MIB MODULE-IDENTITY
LAST-UPDATED "200105040000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
" Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: cs-atm@cisco.com
DESCRIPTION
" ATM AAL2 MIB file that provides AAL2
specific information"
REVISION "200105040000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { Mgmt XXXX}
Aal2MIBObjects OBJECT IDENTIFIER ::= { Aal2MIB 1 }
aal2VccObjects OBJECT IDENTIFIER ::= { Aal2MIBObjects 1 }
aal2VccCidObjects OBJECT IDENTIFIER ::= { Aal2MIBObjects 2 }
-- This table contains AAL2 performance statistics of a VCC at the
-- interface associated with an AAL2 entity in an ATM host
aal2VccTable OBJECT-TYPE
SYNTAX SEQUENCE OF CAal2VccEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains AAL2 VCC performance
parameters, one entry per VPI/VCI pair."
::= { aal2VccObjects 1 }
aal2VccEntry OBJECT-TYPE
SYNTAX CAal2VccEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This list contains the AAL2 VCC performance
parameters and is indexed by ifIndex and the
associated VPI/VCI."
INDEX { ifIndex, aal2VccVpi, aal2VccVci }
::= { aal2VccTable 1 }
Aal2VccEntry ::= SEQUENCE {
aal2VccVpi INTEGER,
aal2VccVci INTEGER,
aal2VccParityErrors Counter32,
aal2VccOverSizedSDUs Counter32,
aal2VccStfSeqErrors Counter32,
aal2VccInvalidPtrErrors Counter32,
aal2VccHecCodeErrors Counter32,
aal2VccOutPkts Counter64,
aal2VccInPkts Counter64,
aal2VccInOctets Counter64,
aal2VccOutOctets Counter64,
aal2VccSubCellMuxMode INTEGER
}
aal2VccVpi OBJECT-TYPE
SYNTAX INTEGER (0..4095)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VPI value of the AAL2 VCC at the interface
identified by the ifIndex."
::= { aal2VccEntry 1 }
aal2VccVci OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VCI value of the AAL2 VCC at the interface
identified by the ifIndex."
::= { aal2VccEntry 2 }
aal2VccParityErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs received with
parity errors on this AAL2 VCC."
::= { aal2VccEntry 3 }
aal2VccOverSizedSDUs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 VCC at the interface associated with an
AAL2 entity because the AAL2 SDUs were too
large."
::= { aal2VccEntry 4 }
aal2VccStfSeqErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 VCC at the interface associated with an
AAL2 entity because of STF sequence errors."
::= { aal2VccEntry 5 }
aal2VccInvalidPtrErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 VCC at the interface associated with an
AAL2 entity because of invalid pointer."
::= { aal2VccEntry 6 }
aal2VccHecCodeErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 VCC at the interface associated with an
AAL2 entity because of Hec Code Error."
::= { aal2VccEntry 7 }
aal2VccInPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs received on this
AAL2 VCC at the interface associated with an
AAL2 entity."
::= { aal2VccEntry 8 }
aal2VccOutPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs transmitted on this
AAL2 VCC at the interface associated with an
AAL2 entity."
::= { aal2VccEntry 9 }
aal2VccInOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDU octets received on
this AAL2 VCC at the interface associated with
an AAL2 entity."
::= { aal2VccEntry 10 }
aal2VccOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDU octets transmitted
on this AAL2 VCC at the interface associated
with an AAL2 entity."
::= { aal2VccEntry 11 }
aal2VccSubCellMuxMode OBJECT-TYPE
SYNTAX INTEGER {
enabled (1),
disabled (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates whether subcell multiplex
mode is enabled/disabled on this VCC at the
interface associated with an AAL2 entity."
::= { aal2VccEntry 12 }
-- This table contains AAL2 performance statistics of a Channel
-- Identifier(CID) of a VCC at the interface associated with an AAL2
-- entity in an ATM host
aal2CidTable OBJECT-TYPE
SYNTAX SEQUENCE OF CAal2CidEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains AAL2 CID performance
parameters, one entry per VPI/VCI and CID
pair."
::= { aal2VccCidObjects 1 }
aal2CidEntry OBJECT-TYPE
SYNTAX CAal2CidEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This list contains the AAL2 CID performance
parameters."
INDEX { ifIndex, aal2CidVpi,
aal2CidVci, aal2CidId }
::= { cAal2CidTable 1 }
Aal2CidEntry ::= SEQUENCE {
cAal2CidVpi INTEGER,
cAal2CidVci INTEGER,
cAal2CidId INTEGER,
cAal2CidParityErrors Counter32,
cAal2CidOverSizedSDUs Counter32,
cAal2CidStfSeqErrors Counter32,
cAal2CidInvalidPtrErrors Counter32,
cAal2CidHecCodeErrors Counter32,
cAal2CidOutPkts Counter32,
cAal2CidInPkts Counter32,
cAal2CidInOctets Counter32,
cAal2CidOutOctets Counter32
}
aal2CidVpi OBJECT-TYPE
SYNTAX INTEGER (0..4095)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VPI value of the AAL2 CID at the interface
identified by the ifIndex."
::= { aal2CidEntry 1 }
aal2CidVci OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VCI value of the AAL2 CID at the interface
identified by the ifIndex."
::= { aal2CidEntry 2 }
aal2CidId OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The CID value of the AAL2 CID at the interface
identified by the ifIndex."
::= { aal2CidEntry 3 }
aal2CidParityErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs received with
Parity errors on this AAL2 CID at the
Interface associated with an AAL2 entity"
::= { aal2CidEntry 4 }
aal2CidOverSizedSDUs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 CID at the interface associated with an
AAL2 entity because the AAL2 SDUs were too
large."
::= { aal2CidEntry 5 }
aal2CidStfSeqErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 CID at the interface associated with an
AAL2 entity because of STF sequence errors."
::= { aal2CidEntry 6 }
aal2CidInvalidPtrErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 CID at the interface associated with an
AAL2 entity because of invalid pointer."
::= { aal2CidEntry 7 }
aal2CidHecCodeErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs discarded on this
AAL2 CID at the interface associated with an
AAL2 entity because of Hec Code Error."
::= { aal2CidEntry 8 }
aal2CidInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs received on this
AAL2 CID at the interface associated with an
AAL2 entity."
::= { aal2CidEntry 9 }
aal2CidOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDUs transmitted on
this AAL2 CID at the interface associated
with an AAL2 entity."
::= { aal2CidEntry 10 }
aal2CidInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDU octets received on
this AAL2 CID at the interface associated with
an AAL2 entity."
::= { aal2CidEntry 11 }
aal2CidOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of AAL2 CPS PDU octets transmitted
on this AAL2 CID at the interface associated
with an AAL2 entity."
::= { aal2CidEntry 12 }
-- Conformance Information
Aal2MIBConformance OBJECT IDENTIFIER ::= { Aal2MIB 2 }
Aal2MIBCompliances OBJECT IDENTIFIER ::=
{ Aal2MIBConformance 1 }
Aal2MIBGroups OBJECT IDENTIFIER ::=
{ Aal2MIBConformance 2 }
-- Compliance Statement
Aal2MIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement
this AAL2 MIB."
MODULE -- this module
MANDATORY-GROUPS { cAal2VccGroup,
cAal2VccCidGroup }
::= { Aal2MIBCompliances 1 }
-- units of conformance:
aal2VccGroup OBJECT-GROUP
OBJECTS {
aal2VccParityErrors,
aal2VccOverSizedSDUs,
aal2VccStfSeqErrors,
aal2VccInvalidPtrErrors,
aal2VccHecCodeErrors,
aal2VccOutPkts,
aal2VccInPkts,
aal2VccInOctets,
aal2VccOutOctets,
aal2VccSubCellMuxMode
}
STATUS current
DESCRIPTION
"A collection of objects providing AAL2 related
parameters corresponding to a VPI/VCI."
::= { Aal2MIBGroups 1 }
aal2VccCidGroup OBJECT-GROUP
OBJECTS {
aal2CidParityErrors,
aal2CidOverSizedSDUs,
aal2CidStfSeqErrors,
aal2CidInvalidPtrErrors,
aal2CidHecCodeErrors,
aal2CidOutPkts,
aal2CidInPkts,
aal2CidInOctets,
aal2CidOutOctets
}
STATUS current
DESCRIPTION
"A collection of objects providing AAL2 related
parameters corresponding to a VPI/VCI and CID."
::= { Aal2MIBGroups 2 }
END
6. Security Considerations
The managed objects in this MIB contain sensitive information since,
collectively, they allow tracing and influencing of virtual connections
in ATM switches or networks and provide information of their traffic
characteristics.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network itself
is secure (for example by using IPSec), even then, there is no control
as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model RFC 2274 [12] and the View-based Access Control
Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
7. References
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", RFC
2271, January 1998.
[2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and
S.Waldbusser, "Structure of Management Information for Version
2 of the Simple Network Management Protocol (SNMPv2)", RFC
1902,January 1996.
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
Waldbusser, "Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
Waldbusser, "Conformance Statements for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
Waldbusser, "Transport Mappings for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, January 1998.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, January 1998.
[13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, MPv3 Applications", RFC
2273, January 1998.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, January 1998.
[16] McCloghrie, K. and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, March 1991.
[17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
RFC 2233, November 1997.
[18] Brown, T. and K. Tesink, "Definitions of Managed Objects for
SMDS Interfaces", RFC 1694, May 1994.
[19] Noto, M., Spiegel, E. and K. Tesink, Editors, "Definitions of
Textual Conventions and OBJECT-IDENTITIES for ATM Management",
RFC 2514, February 1999.
[20] ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0)
Specification, 1994.
[21] ATM Forum, B-ICI Specification, Version 2.0, af-bici-0013.002,
November 1995.
[22] "ATM Forum Private Network-Network Interface Specification,
Version 1.0 (PNNI 1.0)", af-sig-0055.000, March 1996.
[23] "ATM Forum Integrated Local Management Interface (ILMI)
Specification", Version 4.0", af-ilmi-0065.000, September
1996.
[24] Ahmed, M. and K. Tesink, "Definitions of Managed Objects for
ATM Management Version 8.0 using SMIv2", RFC 1695, August 1994.
[25] Ahmed, M. and K. Tesink, "Definitions of Managed Objects for
ATM Management Version 8.0 using SMIv2", RFC2515, February
1999.
[26] ATM Forum Protocol Independent MIB for ATM Trunking using AAL2
for Narrowband Services (Addendum to af-vtoa-0113.000)
8. Acknowledgments
This memo is the result of the work of the AToMMIB Working Group,
ATM Forum Technical Committee, VTOA Working Group and NM Working Group.
9. Author's Addresses
K. Ashoka
Cisco Systems (india) Private Limited
Prestige Waterford,
No.9, Brunton Road,
Bangalore- 560 025. India
Phone: 91-80-5321300-306 Ext.6343
EMail: kashoka@cisco.com
10.Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved. This
document and translations of it may be copied and furnished to others,
and derivative works that comment on or otherwise explain it or assist
in its implmentation may be prepared, copied, published and distributed,
in whole or in part, without restriction of any kind, provided that the
above copyright notice and this paragraph are included on all such copies
and derivative works. However, this document itself may not be modified
in any way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed for the
purpose of developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed, or
as required to translate it into
INTERNET-DRAFT ATM AAL2 Managed Objects May 2001
K. Ashoka Expires November 2001 6
