< draft-ietf-ion-mib-05.txt		draft-ietf-ion-mib-06.txt >
	Internetworking Over NBMA (ion) Working Group Maria Greene		Internetworking Over NBMA (ion) Working Group Maria Greene
	INTERNET DRAFT Independent Contractor		INTERNET DRAFT Xedia Corp.
	Expires July, 1998 James Luciani		Expires July, 1998 James Luciani
	<draft-ietf-ion-mib-05.txt> Bay Networks, Inc.		<draft-ietf-ion-mib-06.txt> Bay Networks, Inc.
	Kenneth White		Kenneth White
	IBM Corp.		IBM Corp.
	Ted T.I. Kuo		Ted T.I. Kuo
	Bay Networks, Inc.		Bay Networks, Inc.
	January 1998		January 1998
	Definitions of Managed Objects for		Definitions of Managed Objects for
	Classical IP and ARP Over ATM Using SMIv2		Classical IP and ARP Over ATM Using SMIv2
	(IPOA-MIB)		(IPOA-MIB)
	Status of this Memo		Status of this Memo
	This document is an Internet Draft. Internet Drafts are working		This document is an Internet Draft. Internet Drafts are working
	documents of the Internet Engineering Task Force (IETF), its Areas,		documents of the Internet Engineering Task Force (IETF), its Areas,
	and its Working Groups. Note that other groups may also distribute		and its Working Groups. Note that other groups may also distribute
	working documents as Internet Drafts.		working documents as Internet Drafts.
	Internet Drafts are draft documents valid for a maximum of six		Internet Drafts are draft documents valid for a maximum of six
	months. Internet Drafts may be updated, replaced, or obsoleted by		months. Internet Drafts may be updated, replaced, or obsoleted by
	other documents at any time. It is not appropriate to use Internet		other documents at any time. It is not appropriate to use Internet
	Drafts as reference material or to cite them other than as a "working		Drafts as reference material or to cite them other than as a "working
	draft" or "work in progress."		draft" or "work in progress."
	Please check the I-D abstract listing contained in each Internet		Please check the I-D abstract listing contained in each Internet
	Draft directory to learn the current status of this or any Internet		Draft directory to learn the current status of this or any Internet
	Draft. Distribution of this document is unlimited.		Draft. Distribution of this document is unlimited.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (1997). All Rights Reserved.		Copyright (C) The Internet Society (1998). All Rights Reserved.
	Abstract		Abstract
	The purpose of this memo is to define the Management Information		The purpose of this memo is to define the Management Information
	Base (MIB) for supporting Classical IP and ARP over ATM as specified		Base (MIB) for supporting Classical IP and ARP over ATM as specified
	in Classical IP and ARP over ATM, refer to reference [3]. Support of		in Classical IP and ARP over ATM, refer to reference [3]. Support of
	an ATM interface by an IP layer will require implementation of objects		an ATM interface by an IP layer will require implementation of objects
	from several Management Information Bases (MIBs) as well as their		from several Management Information Bases (MIBs) as well as their
	enhancement in order to enable usage of ATM transports. It is the		enhancement in order to enable usage of ATM transports. It is the
	intent of this MIB to fully adhere to all prerequisite MIBs unless		intent of this MIB to fully adhere to all prerequisite MIBs unless
	explicitly stated. Deviations will be documented in corresponding		explicitly stated. Deviations will be documented in corresponding
	conformance statements. The specification of this MIB will utilize		conformance statements. The specification of this MIB will utilize
	the Structure of Management Information (SMI) for Version 2 of the		the Structure of Management Information (SMI) for Version 2 of the
	Simple Network Management Protocol Version (refer to RFC1902,		Simple Network Management Protocol Version (refer to RFC 1902,
	reference [1]).		reference [1]).
	Table of Contents		Table of Contents
	1.0 Introduction............................................. 2		1. Introduction.............................................. 2
	2.0 The SNMPv2 Network Management Framework.................. 3		2. The SNMPv2 Network Management Framework................... 3
	2.1 Object Definitions....................................... 4		2.1 Object Definitions....................................... 4
	3.0 Structure of the MIB..................................... 4		3. Structure of the MIB...................................... 4
	3.1 Basic Support MIB Definitions............................ 5		3.1 Basic Support MIB Definitions............................ 5
	3.1.1 ATM Logical IP Subnet (LIS) Table...................... 5		3.1.1 ATM Logical IP Subnet (LIS) Table...................... 5
	3.1.2 ATM Logical IP IF Mapping Table........................ 7		3.1.2 ATM Logical IP Subnet Interface Mapping Table.......... 7
	3.1.3 ATMARP Remote Server Table............................. 7		3.1.3 ATMARP Remote Server Table............................. 7
	3.1.4 ATM VC Table........................................... 8		3.1.4 ATM VC Table........................................... 8
	3.1.5 ATM Config PVC Table................................... 9		3.1.5 ATM Config PVC Table................................... 9
	3.1.6 Notifications.......................................... 10 .		3.1.6 Notifications.......................................... 10 .
	3.2 Client Supported MIB Definitions......................... 10		3.2 Client Supported MIB Definitions......................... 10
	3.2.1 ATMARP Client Table.................................... 11		3.2.1 ATMARP Client Table.................................... 11
	3.3 Server Supported MIB Definitions......................... 12		3.3 Server Supported MIB Definitions......................... 12
	3.3.1 ATMARP Server Table.................................... 12		3.3.1 ATMARP Server Table.................................... 12
	3.3.2 Notifications.......................................... 13		3.3.2 Notifications.......................................... 13
	4.0 Definitions.............................................. 13		4. Definitions............................................... 14
	5.0 Security Considerations.................................. 46		5. Security Considerations................................... 48
	6.0 Acknowledgments.......................................... 47		6. Intellectual Property..................................... 49
	7.0 References............................................... 47		7. Acknowledgments........................................... 50
	8.0 Authors' Addresses....................................... 48		8. References................................................ 50
	9.0 Full Copyright Statement................................. 49		9. Authors' Addresses........................................ 51
			10. Full Copyright Statement................................. 52
	1. Introduction		1. Introduction
	This document is a product of the Internetworking Over NBMA Working		This document is a product of the Internetworking Over NBMA Working
	Group. Its purpose is to define a MIB module for extending the		Group. Its purpose is to define a MIB module for extending the
	traditional MIBs supported by a TCP/IP implementation to support		traditional MIBs supported by a TCP/IP implementation to support
	Classical IP and ARP over ATM.		Classical IP and ARP over ATM.
	Many MIB related RFCs and Internet Drafts have been considered in the		Many MIB related RFCs and Internet Drafts have been considered in the
	development of this document. The ones that are considered central to		development of this document. The ones that are considered central to
	the extensions defined by this document are:		the extensions defined by this document are:
	o RFC 2011 - SNMPv2 Management Information Base for the		o RFC 2011 - SNMPv2 Management Information Base for the
	Internet Protocol using SMIv2 [10]. The IP over ATM		Internet Protocol using SMIv2 [9]. The IP over ATM
	(IPOA) MIB provides extensions to the IP Group for		(IPOA) MIB provides extensions to the IP Group for
	handling IP over ATM flows. A basic understanding of		handling IP over ATM flows. A basic understanding of
	the IP Group is essential for understanding this		the IP Group is essential for understanding this
	document.		document.
	o RFC 2233 - The Interfaces Group MIB (IF-MIB) using SMIv2.		o RFC 2233 - The Interfaces Group MIB (IF-MIB) using SMIv2,
			reference [2]. This document is important since it
	This document is important since it provides several		provides several very useful enhancements over the
	very useful enhancements over the interface group		interface group defined in RFC 1213 (reference [5])
	defined in RFC 1213 that aid in handling ATM related		that aid in handling ATM related interfaces.
	interfaces.
	o RFC 1695 - Definitions of Managed Objects for ATM Management		o RFC 1695 - Definitions of Managed Objects for ATM Management
	[4] (ATM-MIB). Support of this MIB is REQUIRED for		[4] (ATM-MIB). Support of this MIB is REQUIRED for
	implementing the layers between AAL5 and ATM. The		implementing the layers between AAL5 and ATM. The
	contents of this MIB will not explicitly be addressed		contents of this MIB will not explicitly be addressed
	here. The ATM-MIB provides a basis for managing ATM		here. The ATM-MIB provides a basis for managing ATM
	interface layering and management of:		interface layering and management of:
	- ATM Switched Virtual Connections (SVCs)		- ATM Switched Virtual Connections (SVCs)
	- ATM Permanent Virtual Connections (PVCs)		- ATM Permanent Virtual Connections (PVCs)
	The ATM Forum UNI ILMI MIB is specified by the ATM Forum in various		The ATM Forum UNI ILMI MIB is specified by the ATM Forum in various
	versions of the UNI specification. The ILMI MIBs being defined are not		versions of the UNI specification. The ILMI MIBs being defined are
	supported via SNMP agents but via SNMP requests sent over an ATM		not supported via SNMP agents but via SNMP requests sent over an ATM
	network to an ATM entity encapsulated in an AAL5 header. Support of		network to an ATM entity encapsulated in an AAL5 header. Support of
	the ILMI MIB(s) is considered out of the scope of this document.		the ILMI MIB(s) is considered out of the scope of this document.
	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 RFC 2119, reference		document are to be interpreted as described in RFC 2119, reference
	[11].		[10].
	2. The SNMPv2 Network Management Framework		2. The SNMPv2 Network Management Framework
	The SNMP Network Management Framework presently consists of three		The SNMPv2 Network Management Framework consists of seven major
	major components. They are:		components. They are:
	o the SMI, described in RFC 1902 [1], - the mechanisms used for		o RFC 1902 [1] which defines the SMI, the mechanisms used for
	describing and naming objects for the purpose of management.		describing and naming objects for the purpose of management.
	o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed		o RFC 1903 [6] defines textual conventions for SNMPv2.
	objects for the Internet suite of protocols.
	o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol		o RFC 1904 [8] defines conformance statements for SNMPv2.
	for accessing managed information.
	Textual conventions are defined in RFC 1903 [6], and conformance		o RFC 1905 [7] defines transport mappings for SNMPv2.
	statements are defined in RFC 1904 [8].
			o RFC 1906 [12] defines the protocol operations used for network
			access to managed objects.
			o RFC 1907 [13] defines the Management Information Base for SNMPv2.
			o RFC 1908 [14] specifies coexistence between SNMPv1 and SNMPv2.
	The Framework permits new objects to be defined for the purpose of		The Framework permits new objects to be defined for the purpose of
	experimentation and evaluation.		experimentation and evaluation.
	This memo specifies a MIB module that is compliant to the SNMPv2 SMI.		This memo specifies a MIB module that is compliant to the SNMPv2 SMI.
	A semantically identical MIB conforming to the SNMPv1 SMI can be		A semantically identical MIB conforming to the SNMPv1 SMI can be
	produced through the appropriate translation.		produced through the appropriate translation.
	2.1. Object Definitions		2.1. Object Definitions
	skipping to change at page 4, line 28 ¶		skipping to change at page 4, line 33 ¶
	use a textual string, termed the descriptor, to refer to the object		use a textual string, termed the descriptor, to refer to the object
	type.		type.
	3. Structure of the MIB		3. Structure of the MIB
	The Classical ARP and IP over ATM (IPOA) MIB structure is split into		The Classical ARP and IP over ATM (IPOA) MIB structure is split into
	three components:		three components:
	o Basic Support MIB Definitions		o Basic Support MIB Definitions
	o Client Supported MIB Definitions		o Client Supported MIB Definitions
	o ATMARP Server MIB Definitions		o Server Supported MIB Definitions
	All IP and ARP over ATM entities, both clients and ATMARP Servers, are		All IP and ARP over ATM entities, both clients and ATMARP Servers, are
	REQUIRED to support the MIB definitions in the Basic Support MIB		REQUIRED to support the MIB definitions in the Basic Support MIB
	Definitions section. Clients need to additionally support the MIB		Definitions section. Clients need to additionally support the MIB
	definitions outlined in the Client specific section and ATMARP Servers		definitions outlined in the Client specific section and ATMARP Servers
	MUST additionally support the ATMARP Server specific MIB definitions.		MUST additionally support the ATMARP Server specific MIB definitions.
	Implementation of the Definitions of Managed Objects for ATM		Implementation of the Definitions of Managed Objects for ATM
	Management [4] defines the modeling of the various layers within an		Management [4] defines the modeling of the various layers within an
	ATM Interface. This modeling is assumed as a prerequisite for the IPOA		ATM Interface. This modeling is assumed as a prerequisite for the
	MIB. The IPOA MIB makes no assumptions on how this layering is		IPOA-MIB. The IPOA-MIB makes no assumptions on how this layering is
	actually implemented within a system. Several of the MIB tables		actually implemented within a system. Several of the MIB tables
	defined by the IPOA MIB, like the base TCP/IP MIBs, requires that an		defined by the IPOA-MIB, like the base TCP/IP MIBs, require that an
	ifIndex exist that points to an ATM Interface. Refer to the		ifIndex exist that points to an ATM Interface. Refer to the ATM-MIB
	Definitions of Managed Objects for ATM Management (ATM-MIB) for the		[4] for the definition of ATM Interface layering.
	definition of ATM Interface layering.
	The use of an IP over ATM Virtual Interface Layer is NOT explicitly		The use of an IP over ATM Virtual Interface layer is NOT explicitly
	REQUIRED by the IPOA MIB. The use of virtual layers above an ATM-MIB		REQUIRED by the IPOA-MIB. The use of virtual layers above an ATM-MIB
	defined interface layer is not absolutely necessary for modeling the		defined interface layer is not absolutely necessary for modeling the
	attachment of IP to an ATM network. The IPOA MIB refers to use of a		attachment of IP to an ATM network. The IPOA-MIB refers to use of a
	generic ifIndex object, who's value SHOULD reflect that of some		generic ifIndex object, whose value SHOULD reflect that of some
	specific ATM related interface as determined by an implementation. It		specific ATM related interface as determined by an implementation. It
	up to the implementers of this MIB to determine their own ATM		is up to the implementers of this MIB to determine their own ATM
	interface layering (assuming compliance with the IF-MIB and the ATM-		interface layering (assuming compliance with the IF-MIB and the ATM-
	MIB).		MIB).
	The Internet Assigned Numbers Authority (IANA) ifType ipOverAtm(114)		The Internet Assigned Numbers Authority (IANA) ifType ipOverAtm(114)
	was created for use by systems that require an virtual IP over ATM		was created for use by systems that require a virtual IP over ATM
	interface layer. The IF-MIB's ifStackTable SHOULD be used to show the		interface layer. The IF-MIB's ifStackTable SHOULD be used to show the
	relationship between virtual IP over ATM interfaces and the actual ATM		relationship between virtual IP over ATM interfaces and the actual ATM
	physical interface layers. The current set of ifType values can be		physical interface layers. The current set of ifType values can be
	accessed via the IANA homepage at: "http://www.iana.org/iana/".		accessed via the IANA homepage at: "http://www.iana.org/iana/".
	3.1. Basic Support MIB Definitions		3.1. Basic Support MIB Definitions
	Basic support that MUST be implemented by both Clients and ATMARP		Basic support that MUST be implemented by both Clients and ATMARP
	Servers consists of:		Servers consists of:
	o ATM Logical IP Subnet (LIS) Table		o ATM Logical IP Subnet (LIS) Table
	o ATM Logical IP IF Mapping Table		o ATM Logical IP Subnet Interface Mapping Table
	o ATMARP Remote Server Table		o ATMARP Remote Server Table
	o ATM VC Table		o ATM VC Table
	o ATM Config PVC Table		o ATM Config PVC Table
	o Notifications		o Notifications
	3.1.1. ATM Logical IP Subnet (LIS) Table		3.1.1. ATM Logical IP Subnet (LIS) Table
	The ATM Logical IP Subnet (LIS) Table defines the subnets that this		The ATM Logical IP Subnet (LIS) Table defines the subnets that this
	system is a member of for purposes of reaching destinations over an		system is a member of for purposes of reaching destinations over an
	ATM transport. The LIS table is indexed by the subnet address		ATM transport. The LIS table is indexed by the subnet address
	(ipoaLisSubnetAddr) and not ifIndex. The ipoaLisIfMappingTable		(ipoaLisSubnetAddr) and not ifIndex. The ipoaLisIfMappingTable
	described in the next section provides the mapping between Logical IP		described in the next section provides the mapping between Logical IP
	Subnets and the interface layer. It is possible that the same LIS can		Subnets and the interface layer. It is possible that the same LIS can
	be reached via different ATM physical interfaces.		be reached via different ATM interfaces.
	The ipAddrTable and the ipoaClientTable provides the mapping from a		The ipAddrTable and the ipoaClientTable provides the mapping from a
	local IP address to an ATM physical interface. One or more		local IP address to an ATM interface. One or more ipAddrTable entries
	ipAddrTable entries can point to the same ipoaLisEntry. An		can point to the same ipoaLisEntry. An ipAddrEntry's ipAdEntAddr
	ipAddrEntry's ipAdEntAddr ANDed with its ipAdEntNetMask SHOULD equal		ANDed with its ipAdEntNetMask SHOULD equal an ipoaLisEntry's
	an ipoaLisEntry's ipoaLisSubnetAddr. Given that an interface can be		ipoaLisSubnetAddr. Given that an interface can be multi-homed, each
	multi-homed, each local IP address associated with an interface		local IP address associated with an interface requires an entry in the
	requires an entry in the ipAddrTable. Each ipAddrTable entry for a		ipAddrTable. Each ipAddrTable entry for a local IP address associated
	local IP address associated with an ATM physical interface SHOULD map		with an ATM interface SHOULD map to an entry in the ipoaLisTable.
	to an entry in the ipoaLisTable.
	The bulk of the objects in an ipoaLisEntry exists to control ATMARP		The bulk of the objects in an ipoaLisEntry exists to control ATMARP
	for a particular LIS:		for a particular LIS. In a PVC only environment it is implementation
			dependent as to whether this table should be supported:
	ipoaLisInactivityTimer		ipoaLisInactivityTimer
	ipoaLisMinHoldingTime		ipoaLisMinHoldingTime
	ipoaLisQDepth		ipoaLisQDepth
	ipoaLisMaxCalls		ipoaLisMaxCalls
	ipoaLisCacheEntryAge		ipoaLisCacheEntryAge
	ipoaLisRetries		ipoaLisRetries
	ipoaLisTimeout		ipoaLisTimeout
	The value of an ipoaLisMaxCalls object defines the maximum number of		The value of an ipoaLisMaxCalls object defines the maximum number of
	VCs that can be established simultaneously per LIS. The value of an		VCs that can be established simultaneously per LIS. The value of an
	ipoaLisDefaultPeakCellRate object defines the best effort default peak		ipoaLisDefaultPeakCellRate object defines the best effort default peak
	cell rate in both the forward and backward directions when		cell rate in both the forward and backward directions when
	establishing VCCs (Virtual Channel Connections). Refer to RFC 1755,		establishing VCCs (Virtual Channel Connections). Refer to RFC 1755,
	ATM Signaling Support for IP over ATM (reference [12]), for a		ATM Signaling Support for IP over ATM (reference [11]), for a
	definition of the use of this object's value.		definition of the use of this object's value.
	The ipAddrTable's ipAdEntReasmMaxSize is the "The size of the largest		The ipAddrTable's ipAdEntReasmMaxSize is the "The size of the largest
	IP datagram which this entity can re-assemble from incoming IP		IP datagram which this entity can re-assemble from incoming IP
	fragmented datagrams received on this interface" and is different from		fragmented datagrams received on this interface" and is different from
	the ipoaLisTable's ipoaLisDefaultMtu with is the default MTU used		the ipoaLisTable's ipoaLisDefaultMtu with is the default MTU used
	within an LIS. Note that this is the default MTU not the actual which		within an LIS. Note that this is the default MTU, not the actual MTU
	is represented as ipoaVcNegotiatedMtu in the ipoaVcTable.		(which is represented as ipoaVcNegotiatedMtu in the ipoaVcTable).
	The ipoaLisRowStatus object enables entries in the ipoaLisTable to be		The ipoaLisRowStatus object enables entries in the ipoaLisTable to be
	created or deleted via SNMP. Creation of an ipoaLisTable entry results		created or deleted via SNMP. Creation of an ipoaLisTable entry
	in the addition of a corresponding ipAddrTable entry and an		results in the addition of a corresponding ipAddrTable entry and an
	ipoaLisIfMappingTable entry. Creation of multiple ipAddrTable entries		ipoaLisIfMappingTable entry. Creation of multiple ipAddrTable entries
	and ipoaLisIfMappingTable entries for the same LIS is not addressed by		and ipoaLisIfMappingTable entries for the same LIS is not addressed by
	this document. When ipoaLisRowStatus is changed from active(1) to		this document. When ipoaLisRowStatus is changed from active(1) to
	notInService(2) or from active(1) to destroy(6), this has the side-		notInService(2) or from active(1) to destroy(6), this has the side-
	effect of removing all entries from the ipNetToMediaTable that are		effect of removing all entries from the ipNetToMediaTable that are
	associated with this LIS (in other words, it flushes the entity's		associated with this LIS (in other words, it flushes the entity's
	ATMARP cache). It also removes the ipoaVcTable entries that were		ATMARP cache). It also removes the ipoaVcTable entries that were
	associated with those ipNetToMediaTable entries. Destroying the row		associated with those ipNetToMediaTable entries. Destroying the row
	removes the corresponding entries in the ipoaArpSrvrTable,		removes the corresponding entries in the ipoaArpSrvrTable,
	ipoaArpClientTable, ipoaLisIfMappingTable and the		ipoaArpClientTable, ipoaLisIfMappingTable, and the
	ipoaArpRemoteSrvrTable.		ipoaArpRemoteSrvrTable.
	Entries in both the ipNetToMediaTable and the ipoaVcTable that are		Entries in both the ipNetToMediaTable and the ipoaVcTable that are
	associated with an ipoaConfigPvcEntry are not effected by changes to		associated with an ipoaConfigPvcEntry are not affected by changes to
	ipoaLisRowStatus.		ipoaLisRowStatus.
	3.1.2. ATM Logical IP IF Mapping Table		3.1.2. ATM Logical IP Subnet Interface Mapping Table
	The ipoaLisIfMappingTable maps a LIS to all ATM physical interfaces		The ipoaLisIfMappingTable maps a LIS to all ATM interfaces from which
	that it is configured to be supported from. Each entry in the		it is configured to be supported. Each entry in the
	ipoaLisIfMappingTable SHOULD map to an ipAddrTable entry. It is also		ipoaLisIfMappingTable SHOULD map to an ipAddrTable entry. It is also
	possible for a system, most commonly a switch, to have multiple LISes		possible for a system, most commonly a switch, to have multiple LISs
	associated with the same ATM physical interface.		associated with the same ATM interface.
	3.1.3. ATMARP Remote Server Table		3.1.3. ATMARP Remote Server Table
	Entries in the ipoaArpRemoteSrvrTable exists to locally configure the		Entries in the ipoaArpRemoteSrvrTable exists to locally configure the
	remote ATMARP Servers that exist on a per LIS and interface basis.		remote ATMARP Servers that exist on a per LIS and interface basis.
	Classic2 requires that at least one ATMARP Server be configured per		Classical IP and ARP over ATM [3] requires that at least one ATMARP
	LIS where SVC traffic is intended. PVC usage doesn't require use of		Server be configured per LIS where SVC traffic is intended. PVC usage
	ATMARP. No ipoaArpRemoteSrvrTable entries SHOULD be configured for a		doesn't require use of ATMARP. No ipoaArpRemoteSrvrTable entries
	LIS where only PVCs will be used. An entry in the		SHOULD be configured for a LIS where only PVCs will be used. An entry
	ipoaArpRemoteSrvrTable is indexed by the subnet address of the LIS		in the ipoaArpRemoteSrvrTable is indexed by the subnet address of the
	(ipoaLisSubnetAddr), the ATM address of the remote ATMARP Server		LIS (ipoaLisSubnetAddr), the ATM address of the remote ATMARP Server
	(ipoaArpRemoteSrvrAtmAddr) and an interface ifIndex		(ipoaArpRemoteSrvrAtmAddr) and an interface ifIndex
	(ipoaArpRemoteSrvrIfIndex) value.		(ipoaArpRemoteSrvrIfIndex) value.
	The object ipoaArpRemoteSrvrIpAddr in an ipoaArpRemoteSrvrEntry is set		The object ipoaArpRemoteSrvrIpAddr in an ipoaArpRemoteSrvrEntry is set
	with the IP Address of the Remote ATMARP Server when a VC to the		with the IP Address of the Remote ATMARP Server when a VC to the
	Remote ATMARP Server is established. A value of 0 SHOULD be used when		Remote ATMARP Server is established. A value of 0.0.0.0 SHOULD be
	the IP address of the Remote ATMARP Server is not known. Once		used when the IP address of the Remote ATMARP Server is not known.
	ipoaArpRemoteSrvrIpAddr is set then the ipoaVcTable can be searched		Once ipoaArpRemoteSrvrIpAddr is set then the ipoaVcTable can be
	using ipoaArpRemoteSrvrIfIndex and ipoaArpRemoteSrvrIpAddr to find the		searched using ipoaArpRemoteSrvrIfIndex and ipoaArpRemoteSrvrIpAddr to
	VC in use to the Remote ATMARP Server.		find the VC in use to the Remote ATMARP Server.
	ipoaArpRemoteSrvrIfIndex is defined to have the textual convention of		ipoaArpRemoteSrvrIfIndex is defined to have the textual convention of
	InterfaceIndexOrZero. Adding ipoaArpRemoteSrvrIfIndex to the index		InterfaceIndexOrZero. Adding ipoaArpRemoteSrvrIfIndex to the index
	clause allows a system to have a VC to a ATMARP Remote Server on a per		clause allows a system to have a VC to a ATMARP Remote Server on a per
	LIS and interface basis. An entry in this table SHOULD exist for each		LIS and interface basis. An entry in this table SHOULD exist for each
	interface on a per LIS basis. Each interface would then have a		interface on a per LIS basis. Each interface would then have a
	separate VC to the Remote ATMARP Server for ATMARP purposes.		separate VC to the Remote ATMARP Server for ATMARP purposes.
	An implementation that wants to use a single VC MAY use an		An implementation that wants to use a single VC MAY use an
	ipoaArpRemoteSrvrIfIndex value of 0 when configuring an		ipoaArpRemoteSrvrIfIndex value of 0 when configuring an
	ipoaArpRemoteSrvrEntry for the associating LIS. If		ipoaArpRemoteSrvrEntry for the associating LIS. If
	ipoaArpRemoteSrvrIfIndex is 0 then an implementation dependent method		ipoaArpRemoteSrvrIfIndex is 0 then an implementation dependent method
	MAY be used for finding the vpi and vci of the VC in use to the Remote		MAY be used for finding the VPI and VCI of the VC in use to the Remote
	ATMARP Server. For example, search the ipoaVcTable for a match		ATMARP Server. For example, search the ipoaVcTable for a match
	between ipNetToMediaNetAddress and ipoaArpRemoteSrvrIpAddr from an		between ipNetToMediaNetAddress and ipoaArpRemoteSrvrIpAddr from an
	ipoaArpRemoteSrvrEntry, ignoring ipNetToMediaIfIndex. Since a single		ipoaArpRemoteSrvrEntry, ignoring ipNetToMediaIfIndex. Since a single
	VC is being used the first match SHOULD correspond to the correct VC.		VC is being used the first match SHOULD correspond to the correct VC.
	If a PVC is intended to be used to communicate with a remote ATMARP		If a PVC is intended to be used to communicate with a remote ATMARP
	Server then the ipoaConfigPvcTable MUST be used to create and activate		Server then the ipoaConfigPvcTable MUST be used to create and activate
	the PVC prior to activating a ipoaArpRemoteSrvrEntry.		the PVC prior to activating a ipoaArpRemoteSrvrEntry.
	The object ipoaArpRemoteSrvrRowStatus enables remote create and		The object ipoaArpRemoteSrvrRowStatus allows for row creation and
	deletion of entries in the ipoaArpRemoteSrvrTable. The objects		deletion of entries in the ipoaArpRemoteSrvrTable. The objects
	ipoaArpRemoteSrvrAdminStatus and ipoaArpRemoteSrvrOperStatus exists to		ipoaArpRemoteSrvrAdminStatus and ipoaArpRemoteSrvrOperStatus exists to
	control and relect the operation use of a Remote ATMARP Server defined		control and relect the operational use of a Remote ATMARP Server
	by an ipoaArpRemoteSrvrEntry. The object ipoaArpRemoteSrvrOperStatus		defined by an ipoaArpRemoteSrvrEntry. The object
	SHOULD have a value of active(1) when a SVC has been established to		ipoaArpRemoteSrvrOperStatus SHOULD have a value of up(1) when an SVC
	the Remote ATMARP Server or if using a PVC when the In_ATMARP reply		has been established to the Remote ATMARP Server or if using a PVC
	with the IP Address of the Remote ATMARP Server has been received.		when the InATMARP reply with the IP Address of the Remote ATMARP
	The value of inActive(2) SHOULD be used to indicate that a VC to the		Server has been received. The value of down(2) SHOULD be used to
	Remote ATMARP Server doesn't exist.		indicate that a VC to the Remote ATMARP Server doesn't exist.
	3.1.4. ATM VC Table		3.1.4. ATM VC Table
	An entry in the ipoaVcTable SHOULD have at least one corresponding		An entry in the ipoaVcTable SHOULD have at least one corresponding
	ipNetToMediaTable entry. Both tables use the ipNetToMediaTable's		ipNetToMediaTable entry. Both tables use the ipNetToMediaTable's
	indexes ipNetToMediaIfIndex and ipNetToMediaNetAddress. The		indexes ipNetToMediaIfIndex and ipNetToMediaNetAddress. The
	ipoaVcTable has the additional indexes ipoaVcVpi and ipoaVcVci. An		ipoaVcTable has the additional indexes ipoaVcVpi and ipoaVcVci. An
	ipoaVcEntry exists for every VC per ATM physical interface per		ipoaVcEntry exists for every VC per ATM interface per destination IP
	destination IP address. Refer to the following diagram that		address. Refer to the following diagram that illustrates the
	illustrates the relationship between ipoaVcTable and the		relationship between ipoaVcTable and the ipNetToMediaTable:
	ipNetToMediaTable:
	ipoaVcTable ipNetToMediatable		ipoaVcTable ipNetToMediatable
	------------------------------ ----------------------------		------------------------------ ----------------------------
	| ipNetToMediaIfIndex | | ipNetToMediaIfIndex |		| ipNetToMediaIfIndex | | ipNetToMediaIfIndex |
	| ipNetToMediaNetAddress | | ipNetToMediaNetAddress |		| ipNetToMediaNetAddress | | ipNetToMediaNetAddress |
	| ipoaVcVpi | | |		| ipoaVcVpi | | |
	| ipoaVcVci | | |		| ipoaVcVci | | |
	| ipoaVcType | | |		| ipoaVcType | | |
	º ---> use IpoaAtmAddr TC º º ipNetToMediaPhysAddress º		| ---> use IpoaAtmAddr TC | | ipNetToMediaPhysAddress |
	| ipoaVcNegotiatedEncapsType | | |		| ipoaVcNegotiatedEncapsType | | |
	| ipoaVcNegotiatedMtu | | |		| ipoaVcNegotiatedMtu | | |
	| | | ipNetToMediaType |		| | | ipNetToMediaType |
	------------------------------ ----------------------------		------------------------------ ----------------------------
	ipoaVcType indicates if the entry is for a SVC or a PVC. An		ipoaVcType indicates if the entry is for an SVC or an PVC. An
	ipoaVcEntry, corresponding to a PVC, is created automatically when an		ipoaVcEntry, corresponding to an PVC, is created automatically when an
	ipoaConfigPvcEntry is created and the IP Address at the end of the PVC		ipoaConfigPvcEntry is created and the IP Address at the end of the PVC
	is discovered. The associating ipNetToMediaTable entry would have its		is discovered. The associating ipNetToMediaTable entry would have its
	ipNetToMediaType set to static(4). ipNetToMediaTable entries created		ipNetToMediaType set to static(4). ipNetToMediaTable entries created
	during ATMARP processing have a ipNetToMediaType of dynamic(3). The		during ATMARP processing have a ipNetToMediaType of dynamic(3). The
	process to locally configuring an ipNetToMediaTable entry and an		process to locally configuring an ipNetToMediaTable entry and an
	ipoaVcTable entry for a SVC without using ATMARP is not within the		ipoaVcTable entry for an SVC without using ATMARP is not within the
	scope of this document.		scope of this document.
	The objects ipoaVcVpi and ipoaVcVci are defined to have a MAX-ACCESS		The objects ipoaVcVpi and ipoaVcVci are defined to have a MAX-ACCESS
	of not-accessible since they are only used for purposes of indexing		of not-accessible since they are only used for purposes of indexing an
	and entry in the ipoaVcTable.		entry in the ipoaVcTable.
	3.1.5. ATM Config PVC Table		3.1.5. ATM Config PVC Table
	An entry in the ipoaVcTable is created after the In_ATMARP reply is		An entry in the ipoaVcTable is created after the InATMARP reply is
	successfully received for an ipoaConfigPvcEntry during its activation.		successfully received for an ipoaConfigPvcEntry during its activation.
	In_ATMARP should return the IP Address of the other end of the PVC in		InATMARP should return the IP Address of the other end of the PVC in
	order to have the needed indexes to create an ipNetToMediaEntry and an		order to have the needed indexes to create an ipNetToMediaEntry and an
	ipoaVcEntry. ipoaConfigPvcRowStatus would then be set to active(1).		ipoaVcEntry. ipoaConfigPvcRowStatus would then be set to active(1).
	The object ipoaConfigPvcRowStatus doesn't get a value of active(1)		The object ipoaConfigPvcRowStatus doesn't get a value of active(1)
	until the In_ATMARP reply is received. If the row was complete it		until the InATMARP reply is received. If the row was complete it
	would have a value of notInService as defined by RFC 1903 as oppose to		would have a value of notInService(2) as defined by RFC 1903 as
	notReady. The value of a ipoaConfigPvcRowStatus object can be used to		opposed to notReady(3). The value of a ipoaConfigPvcRowStatus object
	determine if the PVC is available for use or not. The value of an		can be used to determine if the PVC is available for use or not. The
	ipoaConfigPvcRowStatus object SHOULD be set to notInService and the		value of an ipoaConfigPvcRowStatus object SHOULD be set to
	corresponding ARP Cache entry deleted whenever a PVC becomes unusable.		notInService(2) and the corresponding ARP Cache entry deleted whenever
			a PVC becomes unusable.
	A Network Management Station wanting to create a PVC at a particular		A Network Management Station wanting to create a PVC at a particular
	system for use as an IP transport would:		system for use as an IP transport would:
	o use the ATM-MIB, reference [4], to create the PVC		o use the ATM-MIB, reference [4], to create the PVC
	o use the ipoaConfigPvcTable in the IPOA MIB to configure		o use the ipoaConfigPvcTable in the IPOA-MIB to configure
	the PVC for use by IP		the PVC for use by IP
	Refer to the following diagram that illustrates the relationship		Refer to the following diagram that illustrates the relationship
	between the ipoaVcTable and the ipoaConfigPvcTable:		between the ipoaVcTable and the ipoaConfigPvcTable:
	ipoaVcTable ipoaConfigPvcTable		ipoaVcTable ipoaConfigPvcTable
	------------------------------ ----------------------------		------------------------------ ----------------------------
	| ipNetToMediaIfIndex | | ipNetToMediaIfIndex |		| ipNetToMediaIfIndex | | ipNetToMediaIfIndex |
	| ipNetToMediaNetAddress | | |		| ipNetToMediaNetAddress | | |
	| ipoaVcVpi | | ipoaConfigPvcVpi |		| ipoaVcVpi | | ipoaConfigPvcVpi |
	| ipoaVcVci | | ipoaConfigPvcVci |		| ipoaVcVci | | ipoaConfigPvcVci |
	| ipoaVcType | | |		| ipoaVcType | | |
	| | | ipoaConfigPvcDefaultMtu |		| | | ipoaConfigPvcDefaultMtu |
	| ipoaVcNegotiatedEncapsType | | |		| ipoaVcNegotiatedEncapsType | | |
	| ipoaVcNegotiatedMtu | | |		| ipoaVcNegotiatedMtu | | |
	| | | ipoaConfigPvcRowStatus |		| | | ipoaConfigPvcRowStatus |
	------------------------------ ----------------------------		------------------------------ ----------------------------
	When the ipoaVcEntry is created its ipoaVcType will be set to pvc(1),		When the ipoaVcEntry is created its ipoaVcType will be set to pvc(1),
	its ipoaVcNegotiatedEncapsType set to llcSnap(1), and its		its ipoaVcNegotiatedEncapsType set to llcSnap(1), and its
	ipoaVcNegotiatedMtu set to 9180 octets by default. Classic2 allows use		ipoaVcNegotiatedMtu set to 9180 octets by default. Classical IP and
	of other MTU values for PVCs but considers how selection of a value		ARP over ATM [3] allows use of other MTU values for PVCs but considers
	other than 9180 to be out of scope. ipoaConfigPvcDefaultMtu can be		the selection of a value other than 9180 to be out of scope.
	used to configure the MTU to be used for the PVC. Both ends MUST have		ipoaConfigPvcDefaultMtu can be used to configure the MTU to be used
	the same value configured. The associating ipNetToMediaTable entry		for the PVC. Both ends MUST have the same value configured. The
	would have its ipNetToMediaType set to static(4).		associating ipNetToMediaTable entry would have its ipNetToMediaType
			set to static(4).
	Changing ipoaConfigPvcRowStatus from active(1) to notInService(2) or		Changing ipoaConfigPvcRowStatus from active(1) to notInService(2) or
	from active(1) to destroy(6) has the side-effect of removing the		from active(1) to destroy(6) has the side-effect of removing the
	corresponding ipNetToMediaTable, ipoaVcTable and ipoaConfigPvcTable		corresponding ipNetToMediaTable, ipoaVcTable, and ipoaConfigPvcTable
	entries.		entries.
	3.1.6. Notifications		3.1.6. Notifications
	Both ATM clients and ATMARP Servers MUST support generation of a		Both ATM clients and ATMARP Servers MUST support generation of an
	ipoaMtuExceed notification.		ipoaMtuExceeded notification.
	3.2. Client Supported MIB Definitions		3.2. Client Supported MIB Definitions
	The ATMARP Client Table is the only additional MIB table that a client		The ATMARP Client Table is the only additional MIB table that a client
	MUST implement.		MUST implement.
	3.2.1. ATMARP Client Table		3.2.1. ATMARP Client Table
	An entry in the ipoaArpClientTable SHOULD have an corresponding		An entry in the ipoaArpClientTable SHOULD have a corresponding
	ipAddrTable entry where both are indexed by the same ipAdEntAddr.		ipAddrTable entry where both are indexed by the same ipAdEntAddr
	Refer to the following diagram that illustrates the relationship		value. Refer to the following diagram that illustrates the
	between ipoaArpClientTable and ipAddrTable entries:		relationship between ipoaArpClientTable and ipAddrTable entries:
	ipoaArpClientTable ipAddrTable		ipoaArpClientTable ipAddrTable
	----------------------------------- ------------------------		----------------------------------- ------------------------
	| ipAdEntAddr | | ipAdEntAddr |		| ipAdEntAddr | | ipAdEntAddr |
	| | | ipAdEntNetMask |		| | | ipAdEntNetMask |
	| | | ipAdEntIfIndex |		| | | ipAdEntIfIndex |
	| ipoaArpClientAtmAddr | | |		| ipoaArpClientAtmAddr | | |
	| ipoaArpClientSrvrInUse | | |		| ipoaArpClientSrvrInUse | | |
	| ipoaArpClientInArpReqsIn | | |		| ipoaArpClientInArpInReqs | | |
	| ipoaArpClientInArpReqsOut | | |		| ipoaArpClientInArpOutReqs | | |
	| ipoaArpClientInArpRepliesIn | | |		| ipoaArpClientInArpInReplies | | |
	| ipoaArpClientInArpRepliesOut | | |		| ipoaArpClientInArpOutReplies | | |
	| ipoaArpClientInArpInvalidReqsIn | | |		| ipoaArpClientInArpInvalidInReqs | | |
	| ipoaArpClientInArpInvalidReqsOut| | |		| ipoaArpClientInArpInvalidOutReqs| | |
	| ipoaArpClientArpReqsIn | | |		| ipoaArpClientArpInReqs | | |
	| ipoaArpClientArpReqsOut | | |		| ipoaArpClientArpOutReqs | | |
	| ipoaArpClientArpRepliesIn | | |		| ipoaArpClientArpInReplies | | |
	| ipoaArpClientArpRepliesOut | | |		| ipoaArpClientArpOutReplies | | |
	| ipoaArpClientArpNaksIn | | |		| ipoaArpClientArpInNaks | | |
	| ipoaArpClientArpNaksOut | | |		| ipoaArpClientArpOutNaks | | |
	| ipoaArpClientArpOpUnknown | | |		| ipoaArpClientArpUnknownOps | | |
	| ipoaArpClientArpSrvrNoResp | | |		| ipoaArpClientArpNoSrvrResps | | |
	| ipoaArpClientRowStatus | | |		| ipoaArpClientRowStatus | | |
	| | | ipAdEntBcastAddr |		| | | ipAdEntBcastAddr |
	| | | ipAdEntReasmMaxSize |		| | | ipAdEntReasmMaxSize |
	----------------------------------- ------------------------		----------------------------------- ------------------------
	Both tables use the same index, ipAdEntAddr. The ipAddrTable's		Both tables have the same index, ipAdEntAddr. The ipAddrTable's
	ipAdEntNetMask when ANDed with its ipAdEntAddr yield the subnet of the		ipAdEntNetMask when ANDed with its corresponding ipAdEntAddr yield the
	LIS which indexes the ipoaLisTable. The ipAddrTable's ipAdEntIfIndex		subnet of the LIS which can be used as an index into the ipoaLisTable
	points to an physical interface ifTable entry. The attachment point		(ipoaLisSubnetAddr). The ipAddrTable's ipAdEntIfIndex points to an
	for IP into an ATM network is via an ATM interface's ifIndex. This		interface ifTable entry via an ifIndex value. The attachment point
	ifIndex is contained in an ipAddrTable entry.		for IP into an ATM network is via an ATM interface's ifIndex. Each
			ipoaArpClientEntry MUST point to an ATM interface via its
			corresponding ipAddrEntry.
	ipoaArpClientAtmAddr is the local ATM address associated with the		ipoaArpClientAtmAddr is the local ATM address associated with the
	corresponding ATM ifTable entry. ipoaArpClientSrvrInUse is the ATM		corresponding ATM ifTable entry. ipoaArpClientSrvrInUse is the ATM
	address of the ATMARP Server being used for a particular client. If		address of the ATMARP Server being used for a particular client. If
	SVCs are not being used then the value of this object is 0.		SVCs are not being used then the value of this object is a zero-length
			OCTET STRING.
	It is sometimes possible for a system to have multiple IP addresses		It is sometimes possible for a system to have multiple IP addresses
	configured within the same IP subnet. The indexing of this table would		configured within the same IP subnet. The indexing of this table
	seem to preclude that, however, it is possible to have additional		would seem to preclude that. However, it is possible to have
	entries in the ipAddrTable with the same ifIndex and with the same		additional entries in the ipAddrTable with the same ifIndex and with
	subnet address. The mechanism for adding these entries to the		the same subnet address. The mechanism for adding these multiple
	ipAddrTable (which is read-only) is beyond the scope of this document.		entries to the ipAddrTable (which is read-only) is beyond the scope of
			this document.
	The counter object ipoaArpClientInArpInvalidReqsIn is "The number of		The counter object ipoaArpClientInArpInvalidInReqs is "The number of
	times that this client detects an invalid In_ATMARP request."		times that this client detects an invalid InATMARP request." This
	Increment this object when processing fails for an In_ATMARP request.		object SHOULD be incremented when processing fails for an InATMARP
	For example, incorrect In_ATMARP Request structure fields. The object		request (e.g., for incorrect InATMARP request structure fields). The
	ipoaArpClientInArpInvalidReqsOut is defined as "The number of times		object ipoaArpClientInArpInvalidOutReqs is defined as "The number of
	that this client did not receive an In_ATMARP reply." This is		times that this client did not receive an InATMARP reply." This is
	different from ipoaArpClientArpSrvrNoResp which counts the number of		different from ipoaArpClientArpNoSrvrResps which counts the number of
	times no response was received from an ATMARP request.		times no response was received from an ATMARP request.
	In_ATMARP retransmission processing is not controlled by objects in		InATMARP retransmission processing is not controlled by objects in the
	the ipoaLisTable. In general, the ipoaLisTable objects relate to		ipoaLisTable. In general, the ipoaLisTable objects relate to ATMARP
	ATMARP Server processing. Configuration of In_ATMARP retransmission		Server processing. Configuration of InATMARP retransmission
	processing is considered to be implementation dependent and not		processing is considered to be implementation dependent and not
	defined by the IPOA MIB.		defined by the IPOA-MIB.
	Implementations SHOULD use local policy for defining both In_ATMARP		Implementations SHOULD use local policy for defining both InATMARP
	timeout and retry count values. This policy would be expected to		timeout and retry count values. This policy would be expected to
	differ for sending an In_ATMARP Request over a PVC as opposed to a		differ for sending an InATMARP Request over an PVC as opposed to an
	SVC. For transmission of an In_ATMARP Request over an SVC a timeout of		SVC. For transmission of an InATMARP Request over an SVC a timeout of
	60 seconds with a retry count of 3 is suggested. In_ATMARP		60 seconds with a retry count of 3 is suggested. InATMARP
	transmission over a PVC should differ since its retry limit may need		transmission over a PVC should differ since its retry limit may need
	to be infinite in order to insure that In_ATMARP Request processing		to be infinite in order to ensure that InATMARP Request processing
	eventually occurs.		eventually occurs.
	3.3. Server Supported Objects		3.3. Server Supported MIB Definitions
	ATMARP Servers MUST support:		ATMARP Servers MUST support:
	o ATMARP Server Table		o ATMARP Server Table
	o Notifications		o Notifications
	as defined in the following sections. This table exists only on a		as defined in the following sections. This table exists only on a
	system where at least one ATMARP Server is present.		system where at least one ATMARP Server is present.
	3.3.1. ATMARP Server Table		3.3.1. ATMARP Server Table
	This table defines the list of ATMARP Servers within a LIS. Each entry		This table defines the list of ATMARP Servers within a LIS. Each
	of the table defines each ATMARP Server's ATM address, the LIS it is a		entry of the table defines each ATMARP Server's ATM address, the LIS
	member of, and various In_ATMARP and ATMARP statistics.		it is a member of, and various InATMARP and ATMARP statistics.
	An entry in this table provides information about an ATMARP Server		An entry in this table provides information about an ATMARP Server
	within a LIS and is indexed by ipAdEntAddr (a local IP Address from an		within a LIS and is indexed by ipAdEntAddr (a local IP Address from an
	IP Address Table entry) and ipoaArpSrvrAddr (an ATM Address associated		IP Address Table entry) and ipoaArpSrvrAddr (an ATM Address associated
	with the ATMARP Server).		with the ATMARP Server).
	Entries MAY be created by a management application using the		Entries MAY be created by a management application using the
	ipoaArpSrvrRowStatus object. Entries in this table MAY also be created		ipoaArpSrvrRowStatus object. Entries in this table MAY also be
	by the system and not by a management application, for example as a		created by the system and not by a management application, for example
	result of ILMI.		via ILMI.
	Entries in this table MAY be deleted by setting the		Entries in this table MAY be deleted by setting the
	ipoaArpSrvrRowStatus object to destroy(6). This includes entries that		ipoaArpSrvrRowStatus object to destroy(6). This includes entries that
	were added by the system and not by a management application.		were added by the system and not by a management application.
	On a host that supports multiple ATMARP Servers where the local IP		On a host that supports multiple ATMARP Servers where the local IP
	address being associated with each ATMARP Server is the same (for		address being associated with each ATMARP Server is the same (for
	example a non-multi homed host) then the ATM Address, ipoaArpSrvrAddr,		example a non-multihomed host), the ATM Address (ipoaArpSrvrAddr)
	uniquely identifies a particular Server. On a host supporting multiple		uniquely identifies a particular ATMARP Server. On a host supporting
	ATMARP Servers having a single ATM Interface with a single ATM Address		multiple ATMARP Servers having a single ATM Interface with a single
	then ipAdEntAddr MUST be used to uniquely identify an entry in the		ATM Address, the ipAdEntAddr MUST be used to uniquely identify an
	ipoaArpSrvrTable.		entry in the ipoaArpSrvrTable.
	The definition of the ipoaArpSrvrTable doesn't allow an implementation		The indexing of the ipoaArpSrvrTable does not allow entries with the
	that supports multiple ATMARP Servers, a single ATM Address and a		same or no local IP Address (ipAdEntAddr) and the same ATM Address
	single local IP Address (or no local IP Addresses).		(ipoaArpSrvrAddr) to exist. The values of the index elements when
			combined to index a row must be unique.
	3.3.2. Notifications		3.3.2. Notifications
	An ATMARP Server MUST support the following notifications:		An ATMARP Server MUST support the following notifications:
	o ipoaDuplicateIpAddress		o ipoaDuplicateIpAddress
	o ipoaLisCreate		o ipoaLisCreate
	o ipoaLisDelete		o ipoaLisDelete
	Generation of ipoaLisCreate and ipoaLisDelete notifications is		Generation of ipoaLisCreate and ipoaLisDelete notifications is
	controlled by the ipoaLisTrapEnable object. These notifications		controlled by the ipoaLisTrapEnable object. These notifications
	indicated when an ipoaLisEntry is either created or deleted. The		indicate when an ipoaLisEntry is either created or deleted. The
	purpose of these notifications is to enable Network Management		purpose of these notifications is to enable Network Management
	Applications to dynamically discover the existence of ATMARP Server		Applications to dynamically discover the existence of ATMARP Server
	LIS participation in order to eventually determine LIS composition via		LIS participation in order to eventually determine LIS composition via
	subsequent SNMP queries. It is permissible for a ATM client only		subsequent SNMP queries. It is permissible for a ATM client-only
	system to support the ipoaLisTrapEnable object and generate		system to support the ipoaLisTrapEnable object and generate
	ipoaLisCreate and ipoaLisDelete notifications.		ipoaLisCreate and ipoaLisDelete notifications.
	4. Definitions		4. Definitions
	IPOA-MIB DEFINITIONS ::= BEGIN		IPOA-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,		MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
	experimental, Integer32, IpAddress, Counter32,		experimental, Integer32, IpAddress, Counter32,
	Gauge32		Gauge32
	FROM SNMPv2-SMI		FROM SNMPv2-SMI
	TEXTUAL-CONVENTION, RowStatus		TEXTUAL-CONVENTION, RowStatus
	FROM SNMPv2-TC		FROM SNMPv2-TC
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF		FROM SNMPv2-CONF
	ipNetToMediaNetAddress, ipNetToMediaIfIndex,		ipNetToMediaNetAddress, ipNetToMediaIfIndex,
	ipNetToMediaPhysAddress, ipAdEntAddr		ipNetToMediaPhysAddress, ipAdEntAddr
	FROM IP-MIB		FROM IP-MIB
	-- The following textual conventions are defined locally within		-- The following textual conventions are defined locally within
	-- this MIB module. They have been prefixed with Ipoa to		-- this MIB module. They have been prefixed with 'Ipoa' to
	-- distinguish them from their counterparts in the ATM-TC-MIB.		-- distinguish them from their counterparts in the ATM-TC-MIB.
	-- This was done so that the IPOA-MIB could be advanced as		-- This was done so that the IPOA-MIB could be advanced as
	-- an standards based MIB without waiting for the ATM-TC-MIB.		-- a standards-based MIB without waiting for the ATM-TC-MIB.
	-- AtmConnKind, AtmAddr		-- AtmConnKind, AtmAddr
	-- FROM ATM-TC-MIB		-- FROM ATM-TC-MIB
	InterfaceIndex, InterfaceIndexOrZero		InterfaceIndex, InterfaceIndexOrZero
	FROM IF-MIB		FROM IF-MIB
	;		;
	ipoaMIB MODULE-IDENTITY		ipoaMIB MODULE-IDENTITY
	LAST-UPDATED "9801100000Z" -- January 10, 1998		LAST-UPDATED "9801220000Z" -- January 22, 1998
	ORGANIZATION "IETF Internetworking Over NBMA Working		ORGANIZATION "IETF Internetworking Over NBMA Working
	Group (ion)"		Group (ion)"
	CONTACT-INFO		CONTACT-INFO
	"Maria Greene (greene@ultranet.com)		"Maria Greene (greene@xedia.com)
	Independent Contractor		Xedia Corp.
	Jim Luciani (jluciani@BayNetworks.com)		Jim Luciani (jluciani@BayNetworks.com)
	Bay Networks		Bay Networks
	Kenneth White (kennethw@vnet.ibm.com)		Kenneth White (kennethw@vnet.ibm.com)
	IBM Corp.		IBM Corp.
	Ted Kuo (tkuo@eos.ncsu.edu)		Ted Kuo (tkuo@eos.ncsu.edu)
	Bay Networks"		Bay Networks"
	DESCRIPTION		DESCRIPTION
	skipping to change at page 15, line 38 ¶		skipping to change at page 15, line 43 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATM address used by the network entity.		"The ATM address used by the network entity.
	The semantics are implied by the length.		The semantics are implied by the length.
	The address types are:		The address types are:
	- no address (0 octets)		- no address (0 octets)
	- E.164 (8 octets)		- E.164 (8 octets)
	- NSAP (20 octets)		- NSAP (20 octets)
	In addition, when subaddresses are used the AtmAddr		In addition, when subaddresses are used IpoaAtmAddr
	may represent the concatenation of address and		may represent the concatenation of address and
	subaddress. The associated address types are:		subaddress. The associated address types are:
	- E.164, E.164 (16 octets)		- E.164, E.164 (16 octets)
	- E.164, NSAP (28 octets)		- E.164, NSAP (28 octets)
	- NSAP, NSAP (40 octets)		- NSAP, NSAP (40 octets)
	Address lengths other than defined in this definition		Address lengths other than defined in this definition
	imply address types defined elsewhere.		imply address types defined elsewhere.
	Note: The E.164 address is encoded in BCD format."		Note: The E.164 address is encoded in BCD format."
	SYNTAX OCTET STRING (SIZE(0..40))		SYNTAX OCTET STRING (SIZE(0..40))
	IpoaAtmConnKind ::= TEXTUAL-CONVENTION		IpoaAtmConnKind ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The use of call control. The use is as		"The use of call control. The use is as follows:
	follows:
	pvc(1)		pvc(1)
	Virtual link of a PVC. Should not be		Virtual link of a PVC. Should not be
	used in an PVC/SVC (i.e., SPVC)		used in a PVC/SVC (i.e., SPVC)
	crossconnect.		crossconnect.
	svcIncoming(2)		svcIncoming(2)
	Virtual link established after a		Virtual link established after a
	received signaling request to setup		received signaling request to setup
	an SVC.		an SVC.
	svcOutgoing(3)		svcOutgoing(3)
	Virtual link established after a		Virtual link established after a
	transmitted or forwarded signaling		transmitted or forwarded signaling
	request to setup an SVC.		request to setup an SVC.
	spvcInitiator(4)		spvcInitiator(4)
	skipping to change at page 16, line 47 ¶		skipping to change at page 17, line 4 ¶
	svcOutgoing(3),		svcOutgoing(3),
	spvcInitiator(4),		spvcInitiator(4),
	spvcTarget(5)		spvcTarget(5)
	}		}
	-- Top-level structure of the MIB		-- Top-level structure of the MIB
	ipoaObjects OBJECT IDENTIFIER ::= { ipoaMIB 1 }		ipoaObjects OBJECT IDENTIFIER ::= { ipoaMIB 1 }
	ipoaNotifications OBJECT IDENTIFIER ::= { ipoaMIB 2 }		ipoaNotifications OBJECT IDENTIFIER ::= { ipoaMIB 2 }
	ipoaConformance OBJECT IDENTIFIER ::= { ipoaMIB 3 }		ipoaConformance OBJECT IDENTIFIER ::= { ipoaMIB 3 }
	-- MIB Objects		-- MIB Objects
	ipoaLisTrapEnable OBJECT-TYPE		ipoaLisTrapEnable OBJECT-TYPE
	SYNTAX INTEGER { enabled(1), disabled(2) }		SYNTAX INTEGER { enabled(1), disabled(2) }
	MAX-ACCESS read-write		MAX-ACCESS read-write
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates whether ipoaLisCreate and ipoaLisDelete		"Indicates whether ipoaLisCreate and ipoaLisDelete
	traps should be generated by this system.		traps should be generated by this system.
	By default, this object should have the value		By default, this object should have the value
	enabled(1) for systems where ATMARP Servers are		enabled(1) for systems where ATMARP Servers are
	present and disabled(2) on systems where only		present and disabled(2) on systems where only
	clients reside."		clients reside."
	::= { ipoaObjects 1 }		::= { ipoaObjects 1 }
	-- The Logical IP Subnet Table		-- The ATM Logical IP Subnet (LIS) Table
	ipoaLisTable OBJECT-TYPE		ipoaLisTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaLisEntry		SYNTAX SEQUENCE OF IpoaLisEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"There is one entry in this table for every Logical IP		"There is one entry in this table for every Logical IP
	Subnet (LIS) that this system is a member of."		Subnet (LIS) of which this system is a member.
			The bulk of the objects in an ipoaLisEntry exists
			to control ATMARP for a particular LIS. In a PVC only
			environment it is implementation dependent as to
			whether this table should be supported."
	::= { ipoaObjects 2 }		::= { ipoaObjects 2 }
	ipoaLisEntry OBJECT-TYPE		ipoaLisEntry OBJECT-TYPE
	SYNTAX IpoaLisEntry		SYNTAX IpoaLisEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Information about a single LIS that this system is a		"Information about a single LIS of which this system
	member of.		is a member.
	This table is indexed by an IP subnet address.
	Membership in a LIS is independent of the actual ATM		Membership in a LIS is independent of the actual ATM
	physical interfaces being used. The ipoaLisTable defines		interfaces being used. The ipoaLisTable defines
	all LISes that a system is a member of. The ipAddrTable		all LISs that a system is a member of. The ipAddrTable
	and the ipoaClientTable provides the mapping from local		and the ipoaClientTable provides the mapping from local
	IP address to ATM physical interface. The		IP address to ATM interface. The ipoaLisIfMappingTable
	ipoaLisIfMappingTable provides the mappings between		provides the mappings between Logical IP Subnets and
	Logical IP Subnets and interfaces.		interfaces.
	The ipoaLisTable is indexed by ipoaLisSubnetAddr.		The ipoaLisTable is indexed by ipoaLisSubnetAddr (IP
	An entry in the ipAddrTable should exist for each		subnet address). An entry in the ipoaLisTable should
	ipAddrEntry that is associated with an IP over ATM		exist for each ipAddrEntry that is associated with an
	interface. Its ipAdEntAddr and ipAdEntNetMask when ANDed		ATM related interface used for Classical IP and ARP
	should map to a ipoaLisSubnetAddr."		over ATM traffic.
			Its ipAdEntAddr and ipAdEntNetMask when ANDed together
			should equal the ipoaLisSubnetAddr of the corresponding
			ipoaLisEntry."
	INDEX { ipoaLisSubnetAddr }		INDEX { ipoaLisSubnetAddr }
	::= { ipoaLisTable 1 }		::= { ipoaLisTable 1 }
	IpoaLisEntry ::= SEQUENCE {		IpoaLisEntry ::= SEQUENCE {
	ipoaLisSubnetAddr IpAddress,		ipoaLisSubnetAddr IpAddress,
	ipoaLisDefaultMtu Integer32,		ipoaLisDefaultMtu Integer32,
	ipoaLisDefaultEncapsType IpoaEncapsType,		ipoaLisDefaultEncapsType IpoaEncapsType,
	ipoaLisInactivityTimer Integer32,		ipoaLisInactivityTimer Integer32,
	ipoaLisMinHoldingTime Integer32,		ipoaLisMinHoldingTime Integer32,
	ipoaLisQDepth Integer32,		ipoaLisQDepth Integer32,
	skipping to change at page 18, line 33 ¶		skipping to change at page 18, line 45 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The IP subnet address associated with this LIS."		"The IP subnet address associated with this LIS."
	::= { ipoaLisEntry 1 }		::= { ipoaLisEntry 1 }
	ipoaLisDefaultMtu OBJECT-TYPE		ipoaLisDefaultMtu OBJECT-TYPE
	SYNTAX Integer32 (0..65535)		SYNTAX Integer32 (0..65535)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The default MTU used within this LIS. Note that the		"The default MTU used within this LIS. Note that the
	actual size used for a VC between two members of the		actual MTU used for a VC between two members of the
	LIS may be negotiated during connection setup and may		LIS may be negotiated during connection setup and may
	be different than this value. The ipoaVcNegotiatedMtu		be different than this value. The ipoaVcNegotiatedMtu
	object indicates the actual MTU in use for a		object indicates the actual MTU in use for a
	particular VC."		particular VC."
	DEFVAL { 9180 }		DEFVAL { 9180 }
	::= { ipoaLisEntry 2 }		::= { ipoaLisEntry 2 }
	ipoaLisDefaultEncapsType OBJECT-TYPE		ipoaLisDefaultEncapsType OBJECT-TYPE
	SYNTAX IpoaEncapsType		SYNTAX IpoaEncapsType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The default encapsulation to use on VCs created for		"The default encapsulation to use on VCs created for
	this LIS. Note that the actual encapsulation type may		this LIS. Note that the actual encapsulation type may
	be negotiated during connection setup and may be		be negotiated during connection setup and may be
	different than this value. The ipoaVcNegotiatedEncapsType		different than this value. The
	object indicates the actual encapsulation in use for a		ipoaVcNegotiatedEncapsType object indicates the actual
	particular VC."		encapsulation in use for a particular VC."
	DEFVAL { llcSnap }		DEFVAL { llcSnap }
	::= { ipoaLisEntry 3 }		::= { ipoaLisEntry 3 }
	ipoaLisInactivityTimer OBJECT-TYPE		ipoaLisInactivityTimer OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32
	UNITS "seconds"		UNITS "seconds"
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The time, in seconds, before a call established for an		"The time, in seconds, before a call established for an
	ipNetToMediaEntry on a client will timeout due to no		ipNetToMediaEntry on a client will timeout due to no
	traffic being passed on the VC. A value of 0 implies		traffic being passed on the VC. A value of 0 implies
	no time out."		no time out."
	REFERENCE		REFERENCE
	"RFC1755, Sec. 3.4 VC Teardown"		"RFC 1755, Sec. 3.4 VC Teardown"
	DEFVAL { 300 }		DEFVAL { 1200 }
	::= { ipoaLisEntry 4 }		::= { ipoaLisEntry 4 }
	ipoaLisMinHoldingTime OBJECT-TYPE		ipoaLisMinHoldingTime OBJECT-TYPE
	SYNTAX Integer32 (0..65535)		SYNTAX Integer32 (0..65535)
	UNITS "seconds"		UNITS "seconds"
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The minimum amount of time, in seconds, that a call		"The minimum amount of time, in seconds, that a call
	will remain open. If 0 then ipoaInactivityTimer will		will remain open. If 0 then ipoaInactivityTimer will
	completely determine when a call is terminated."		completely determine when a call is terminated."
	REFERENCE		REFERENCE
	"RFC1755, Sec. 3.4 VC Teardown"		"RFC 1755, Sec. 3.4 VC Teardown"
	DEFVAL { 60 }		DEFVAL { 60 }
	::= { ipoaLisEntry 5 }		::= { ipoaLisEntry 5 }
	ipoaLisQDepth OBJECT-TYPE		ipoaLisQDepth OBJECT-TYPE
	SYNTAX Integer32 (1..65535)		SYNTAX Integer32 (1..65535)
	UNITS "packets"		UNITS "packets"
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The maximum number of outstanding requests that are		"The maximum number of outstanding requests that are
	allowed while waiting for ATMARP replies and		allowed while waiting for ATMARP replies and
	In_ATMARP replies for this LIS."		InATMARP replies for this LIS."
	DEFVAL { 1 }		DEFVAL { 1 }
	::= { ipoaLisEntry 6 }		::= { ipoaLisEntry 6 }
	ipoaLisMaxCalls OBJECT-TYPE		ipoaLisMaxCalls OBJECT-TYPE
	SYNTAX Integer32 (1..65535)		SYNTAX Integer32 (1..65535)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The maximum number of SVCs that can be established		"The maximum number of SVCs that can be established
	simultaneously."		simultaneously for this LIS."
	DEFVAL { 500 }		DEFVAL { 500 }
	::= { ipoaLisEntry 7 }		::= { ipoaLisEntry 7 }
	ipoaLisCacheEntryAge OBJECT-TYPE		ipoaLisCacheEntryAge OBJECT-TYPE
	SYNTAX Integer32 (60..1200)		SYNTAX Integer32 (60..1200)
	UNITS "seconds"		UNITS "seconds"
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The time, in seconds, before an ipNetToMediaEntry will		"The time, in seconds, before an ipNetToMediaEntry will
	age out of the table. Note that the default value will		age out of the table. Note that the default value will
	be different for a client and a server. A ATMARP Server		be different for a client and a server. An ATMARP
	should use a default of 1200 and a client should use		Server should use a default of 1200 and a client should
	900."		use 900."
	DEFVAL { 900 }		DEFVAL { 900 }
	::= { ipoaLisEntry 8 }		::= { ipoaLisEntry 8 }
	ipoaLisRetries OBJECT-TYPE		ipoaLisRetries OBJECT-TYPE
	SYNTAX Integer32 (0..10)		SYNTAX Integer32 (0..10)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times the ATMARP request will be retried		"The number of times the ATMARP request will be retried
	when no response is received in the timeout interval		when no response is received in the timeout interval
	skipping to change at page 21, line 11 ¶		skipping to change at page 21, line 22 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object is the signalling parameter that		"This object is the signalling parameter that
	should be used when setting up all best effort		should be used when setting up all best effort
	VCCs (Virtual Channel Connections).		VCCs (Virtual Channel Connections).
	This parameter applies to the forward and		This parameter applies to the forward and
	backward direction on a per best effort VCC basis.		backward direction on a per best effort VCC basis.
	A value of zero implies that no configured default		A value of zero implies that no configured default
	exists and that local policy should be used to		exists and that local policy should be used to
	determine the actual default to used during		determine the actual default to used during
	call setup. ATM Signaling Support for IP over ATM		call setup. ATM Signaling Support for IP over ATM
	(RFC 1755) recommends 1/10th of the ATM interface's		(RFC 1755) recommends 1/10th of the ATM interface's
	speed."		speed."
	::= { ipoaLisEntry 11 }		::= { ipoaLisEntry 11 }
	ipoaLisActiveVcs OBJECT-TYPE		ipoaLisActiveVcs OBJECT-TYPE
	SYNTAX Gauge32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Number of active SVCs."		"Number of active SVCs for this LIS."
	::= { ipoaLisEntry 12 }		::= { ipoaLisEntry 12 }
	ipoaLisRowStatus OBJECT-TYPE		ipoaLisRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object allows entries to be created and deleted		"This object allows entries to be created and deleted
	in the ipoaLisTable.		in the ipoaLisTable.
	When the ipoaLisRowStatus deleted (by setting this		When the ipoaLisRowStatus deleted (by setting this
	object to destroy(6)), this has the side-effect of		object to destroy(6)), this has the side-effect of
	removing all entries from the ipNetToMediaTable that		removing all entries from the ipNetToMediaTable that
	are associated with this LIS (in other words, it		are associated with this LIS (in other words, it
	flushes the entity's ATMARP cache). It also removes		flushes the entity's ATMARP cache). It also removes
	the ipoaVcTable entries that were associated with those		the ipoaVcTable entries that were associated with those
	ipNetToMediaTable entries. Destroying the row also		ipNetToMediaTable entries. Destroying the row also
	removes the corresponding entries in the		removes the corresponding entries in the
	ipoaArpSrvrTable, ipoaArpClientTable,		ipoaArpSrvrTable, ipoaArpClientTable,
	ipoaLisIfMappingTable and ipoaArpRemoteSrvrTable.		ipoaLisIfMappingTable, and ipoaArpRemoteSrvrTable.
	Entries in both the ipNetToMediaTable and the		Entries in both the ipNetToMediaTable and the
	ipoaVcTable that are associated with a		ipoaVcTable that are associated with a
	ipoaConfigPvcEntry are not effected by changes to		ipoaConfigPvcEntry are not affected by changes to
	ipoaLisRowStatus."		ipoaLisRowStatus."
	REFERENCE		REFERENCE
	"RFC 1903, 'Textual Conventions for version 2 of the		"RFC 1903, 'Textual Conventions for Version 2 of the
	Simple Network Management Protocol (SNMPv2).'"		Simple Network Management Protocol (SNMPv2).'"
	::= { ipoaLisEntry 13 }		::= { ipoaLisEntry 13 }
	-- The Logical IP Interface Mapping Table		-- The ATM Logical IP Subnet Interface Mapping Table
	ipoaLisIfMappingTable OBJECT-TYPE		ipoaLisIfMappingTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaLisIfMappingEntry		SYNTAX SEQUENCE OF IpoaLisIfMappingEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"There is one entry in this table for every combination		"There is one entry in this table for every combination
	of ipoaLisEntry and IP over ATM interface."		of ipoaLisEntry and IP over ATM interface."
	::= { ipoaObjects 3 }		::= { ipoaObjects 3 }
	skipping to change at page 22, line 27 ¶		skipping to change at page 22, line 37 ¶
	SYNTAX IpoaLisIfMappingEntry		SYNTAX IpoaLisIfMappingEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Defines an entry in the ipoaLisIfMappingTable."		"Defines an entry in the ipoaLisIfMappingTable."
	INDEX { ipoaLisSubnetAddr, ipoaLisIfMappingIfIndex }		INDEX { ipoaLisSubnetAddr, ipoaLisIfMappingIfIndex }
	::= { ipoaLisIfMappingTable 1 }		::= { ipoaLisIfMappingTable 1 }
	IpoaLisIfMappingEntry ::= SEQUENCE {		IpoaLisIfMappingEntry ::= SEQUENCE {
	ipoaLisIfMappingIfIndex InterfaceIndex,		ipoaLisIfMappingIfIndex InterfaceIndex,
	ipoaLisIfMappingStatus RowStatus }		ipoaLisIfMappingRowStatus RowStatus }
	ipoaLisIfMappingIfIndex OBJECT-TYPE		ipoaLisIfMappingIfIndex OBJECT-TYPE
	SYNTAX InterfaceIndex		SYNTAX InterfaceIndex
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ipAdEntIfIndex object from a ipAddrEntry		"The ipAdEntIfIndex object from an ipAddrEntry
	is used as an index to this table when its		is used as an index to this table when its
	ipAdEntAddr is in the subnet implied by		ipAdEntAddr is in the subnet implied by
	ipoaLisSubnetAddr."		ipoaLisSubnetAddr."
	::= { ipoaLisIfMappingEntry 1 }		::= { ipoaLisIfMappingEntry 1 }
	ipoaLisIfMappingStatus OBJECT-TYPE		ipoaLisIfMappingRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object allows entries to be created and deleted		"This object allows entries to be created and deleted
	in the ipoaLisIfMappingTable."		in the ipoaLisIfMappingTable."
	REFERENCE		REFERENCE
	"RFC 1903, 'Textual Conventions for version 2 of the		"RFC 1903, 'Textual Conventions for Version 2 of the
	Simple Network Management Protocol (SNMPv2).'"		Simple Network Management Protocol (SNMPv2).'"
	::= { ipoaLisIfMappingEntry 2 }		::= { ipoaLisIfMappingEntry 2 }
	-- The ATMARP Client Table		-- The ATMARP Client Table
	ipoaArpClientTable OBJECT-TYPE		ipoaArpClientTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaArpClientEntry		SYNTAX SEQUENCE OF IpoaArpClientEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATMARP clients running on this system."		"The ATMARP clients running on this system."
	::= { ipoaObjects 4 }		::= { ipoaObjects 4 }
	ipoaArpClientEntry OBJECT-TYPE		ipoaArpClientEntry OBJECT-TYPE
	SYNTAX IpoaArpClientEntry		SYNTAX IpoaArpClientEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Information about a single ATMARP Client. Clients		"Information about a single ATMARP Client. Clients
	can be started and stopped by adding and removing		can be started and stopped by adding and removing
	entries from this table. Note that adding and removing		entries from this table. An entry in the
	entries from this table may have the same effect on
	the corresponding ipAddrTable entry. An entry in the
	ipoaArpClientTable has a corresponding entry in the		ipoaArpClientTable has a corresponding entry in the
	ipAddrTable. Both are indexed by ipAdEntAddr.		ipAddrTable. Both are indexed by ipAdEntAddr.
	The ifIndex and subnet mask of a client entry are the		The ifIndex and subnet mask of a client entry are the
	ipAddrEntry's ipAdEntIfIndex and ipAdEntNetMask		ipAddrEntry's ipAdEntIfIndex and ipAdEntNetMask,
	respectively. A remote creation of an object in this		respectively.
			Note that adding and removing entries from this table
			may have the same effect on the corresponding
			ipAddrTable entry. Row creation of an entry in this
	table requires that either the corresponding ipAddrTable		table requires that either the corresponding ipAddrTable
	entry exists or that ipAdEntIfIndex and ipAdEntNetMask		entry exists or that ipAdEntIfIndex and ipAdEntNetMask
	be specified in the creation of a ipoaArpClientEntry		be specified in the creation of an ipoaArpClientEntry
	at a minimum in order to create the corresponding		at a minimum in order to create the corresponding
	ipAddrEntry. Specification of ipAdEntBcastAddr and		ipAddrEntry. Specification of ipAdEntBcastAddr and
	ipAdEntReasmMaxSize to complete a ipAddrEntry is		ipAdEntReasmMaxSize to complete an ipAddrEntry is
			implementation dependent.
			Whether a corresponding ipAddrEntry is deleted during
			the deletion of an ipoaArpClientEntry is considered
	implementation dependent."		implementation dependent."
	INDEX { ipAdEntAddr }		INDEX { ipAdEntAddr }
	::= { ipoaArpClientTable 1 }		::= { ipoaArpClientTable 1 }
	IpoaArpClientEntry ::= SEQUENCE {		IpoaArpClientEntry ::= SEQUENCE {
	ipoaArpClientAtmAddr IpoaAtmAddr,		ipoaArpClientAtmAddr IpoaAtmAddr,
	ipoaArpClientSrvrInUse IpoaAtmAddr,		ipoaArpClientSrvrInUse IpoaAtmAddr,
	ipoaArpClientInArpReqsIn Counter32,		ipoaArpClientInArpInReqs Counter32,
	ipoaArpClientInArpReqsOut Counter32,		ipoaArpClientInArpOutReqs Counter32,
	ipoaArpClientInArpRepliesIn Counter32,		ipoaArpClientInArpInReplies Counter32,
	ipoaArpClientInArpRepliesOut Counter32,		ipoaArpClientInArpOutReplies Counter32,
	ipoaArpClientInArpInvalidReqsIn Counter32,		ipoaArpClientInArpInvalidInReqs Counter32,
	ipoaArpClientInArpInvalidReqsOut Counter32,		ipoaArpClientInArpInvalidOutReqs Counter32,
	ipoaArpClientArpReqsIn Counter32,		ipoaArpClientArpInReqs Counter32,
	ipoaArpClientArpReqsOut Counter32,		ipoaArpClientArpOutReqs Counter32,
	ipoaArpClientArpRepliesIn Counter32,		ipoaArpClientArpInReplies Counter32,
	ipoaArpClientArpRepliesOut Counter32,		ipoaArpClientArpOutReplies Counter32,
	ipoaArpClientArpNaksIn Counter32,		ipoaArpClientArpInNaks Counter32,
	ipoaArpClientArpNaksOut Counter32,		ipoaArpClientArpOutNaks Counter32,
	ipoaArpClientArpOpUnknown Counter32,		ipoaArpClientArpUnknownOps Counter32,
	ipoaArpClientArpSrvrNoResp Counter32,		ipoaArpClientArpNoSrvrResps Counter32,
	ipoaArpClientRowStatus RowStatus }		ipoaArpClientRowStatus RowStatus }
	ipoaArpClientAtmAddr OBJECT-TYPE		ipoaArpClientAtmAddr OBJECT-TYPE
	SYNTAX IpoaAtmAddr		SYNTAX IpoaAtmAddr
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATM address of the client."		"The ATM address of the client."
	::= { ipoaArpClientEntry 1 }		::= { ipoaArpClientEntry 1 }
	ipoaArpClientSrvrInUse OBJECT-TYPE		ipoaArpClientSrvrInUse OBJECT-TYPE
	SYNTAX IpoaAtmAddr		SYNTAX IpoaAtmAddr
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATM address of the ATMARP Server,		"The ATM address of the ATMARP Server,
	ipoaArpRemoteSrvrAtmAddr, in use by this client. A		ipoaArpRemoteSrvrAtmAddr, in use by this client. A
	zero length octet string implies that communication		zero length octet string implies that communication
	with a Remote ATMARP Server is not in effect."		with a Remote ATMARP Server is not in effect."
	DEFVAL { ''H }		DEFVAL { ''H }
	::= { ipoaArpClientEntry 2 }		::= { ipoaArpClientEntry 2 }
	ipoaArpClientInArpReqsIn OBJECT-TYPE		ipoaArpClientInArpInReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP requests received by this		"The number of InATMARP requests received by this
	client."		client."
	::= { ipoaArpClientEntry 3 }		::= { ipoaArpClientEntry 3 }
	ipoaArpClientInArpReqsOut OBJECT-TYPE		ipoaArpClientInArpOutReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP requests sent by this client."		"The number of InATMARP requests sent by this client."
	::= { ipoaArpClientEntry 4 }		::= { ipoaArpClientEntry 4 }
	ipoaArpClientInArpRepliesIn OBJECT-TYPE		ipoaArpClientInArpInReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP replies received by this		"The number of InATMARP replies received by this
	client."		client."
	::= { ipoaArpClientEntry 5 }		::= { ipoaArpClientEntry 5 }
	ipoaArpClientInArpRepliesOut OBJECT-TYPE		ipoaArpClientInArpOutReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of In_ATMARP replies sent by this client."		"Total number of InATMARP replies sent by this client."
	::= { ipoaArpClientEntry 6 }		::= { ipoaArpClientEntry 6 }
	ipoaArpClientInArpInvalidReqsIn OBJECT-TYPE		ipoaArpClientInArpInvalidInReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times that this client detected an		"The number of times that this client detected an
	invalid In_ATMARP request."		invalid InATMARP request."
	::= { ipoaArpClientEntry 7 }		::= { ipoaArpClientEntry 7 }
	ipoaArpClientInArpInvalidReqsOut OBJECT-TYPE		ipoaArpClientInArpInvalidOutReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times that this client did not receive		"The number of times that this client did not
	a In_ATMARP reply."		receive an InATMARP reply."
	::= { ipoaArpClientEntry 8 }		::= { ipoaArpClientEntry 8 }
	ipoaArpClientArpReqsIn OBJECT-TYPE		ipoaArpClientArpInReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of ATMARP requests received by this		"Total number of ATMARP requests received by this
	client."		client."
	::= { ipoaArpClientEntry 9 }		::= { ipoaArpClientEntry 9 }
	ipoaArpClientArpReqsOut OBJECT-TYPE		ipoaArpClientArpOutReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of ATMARP requests sent by this client."		"Total number of ATMARP requests sent by this client."
	::= { ipoaArpClientEntry 10 }		::= { ipoaArpClientEntry 10 }
	ipoaArpClientArpRepliesIn OBJECT-TYPE		ipoaArpClientArpInReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of ATMARP replies received by this		"Total number of ATMARP replies received by this
	client."		client."
	::= { ipoaArpClientEntry 11 }		::= { ipoaArpClientEntry 11 }
	ipoaArpClientArpRepliesOut OBJECT-TYPE		ipoaArpClientArpOutReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of ATMARP replies sent by this client."		"Total number of ATMARP replies sent by this client."
	::= { ipoaArpClientEntry 12 }		::= { ipoaArpClientEntry 12 }
	ipoaArpClientArpNaksIn OBJECT-TYPE		ipoaArpClientArpInNaks OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of negative ATMARP replies		"Total number of negative ATMARP replies
	received by this client."		received by this client."
	::= { ipoaArpClientEntry 13 }		::= { ipoaArpClientEntry 13 }
	ipoaArpClientArpNaksOut OBJECT-TYPE		ipoaArpClientArpOutNaks OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of negative ATMARP replies		"Total number of negative ATMARP replies sent by
	send by this client."		this client.
			Classic IP and ARP over ATM does not require an
			ATMARP client to transmit an ATMARP_NAK upon
			receipt of an ATMARP request from another ATMARP
			client. However, implementation experience has
			shown that this error condition is somewhat easy
			to create inadvertently by configuring one ATMARP
			client with an ipoaArpRemoteSrvrTable entry
			containing an ipoaArpRemoteSrvrAtmAddr value which
			is the ATM address of another ATMARP client-only
			system.
			If an ATMARP client supports the transmission of
			ATMARP_NAKs, then it should increment
			ipoaArpClientArpOutNaks each time it transmits
			an ATMARP_NAK. Otherwise, support of this
			object is considered optional."
	::= { ipoaArpClientEntry 14 }		::= { ipoaArpClientEntry 14 }
	ipoaArpClientArpOpUnknown OBJECT-TYPE		ipoaArpClientArpUnknownOps OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times that this client received		"The number of times that this client received
	an ATMARP message with an operation code for which		an ATMARP message with an operation code for which
	it is not coded to support."		it is not coded to support."
	::= { ipoaArpClientEntry 15 }		::= { ipoaArpClientEntry 15 }
	ipoaArpClientArpSrvrNoResp OBJECT-TYPE		ipoaArpClientArpNoSrvrResps OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times this client failed to receive		"The number of times this client failed to receive
	a response from a ATMARP Server within the		a response from a ATMARP Server within the
	ipoaLisTimeout value for ipoaLisRetries times.		ipoaLisTimeout value for ipoaLisRetries times.
	This may imply that the client will re-elect a		This may imply that the client will re-elect a
	primary ATMARP Server for this LIS from the		new primary ATMARP Server for this LIS from the
	ipoaArpRemoteSrvrTable."		ipoaArpRemoteSrvrTable."
	::= { ipoaArpClientEntry 16 }		::= { ipoaArpClientEntry 16 }
	ipoaArpClientRowStatus OBJECT-TYPE		ipoaArpClientRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object allows entries to be created and deleted		"This object allows entries to be created and
	from the ipoaArpClientTable."		deleted from the ipoaArpClientTable."
	REFERENCE		REFERENCE
	"RFC 1903, 'Textual Conventions for version 2 of the		"RFC 1903, 'Textual Conventions for Version 2 of the
	Simple Network Management Protocol (SNMPv2).'"		Simple Network Management Protocol (SNMPv2).'"
	::= { ipoaArpClientEntry 17 }		::= { ipoaArpClientEntry 17 }
	-- The ATMARP Server Table		-- The ATMARP Server Table
	ipoaArpSrvrTable OBJECT-TYPE		ipoaArpSrvrTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaArpSrvrEntry		SYNTAX SEQUENCE OF IpoaArpSrvrEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATMARP Servers running on this system."		"The ATMARP Servers running on this system."
	::= { ipoaObjects 5 }		::= { ipoaObjects 5 }
	ipoaArpSrvrEntry OBJECT-TYPE		ipoaArpSrvrEntry OBJECT-TYPE
	SYNTAX IpoaArpSrvrEntry		SYNTAX IpoaArpSrvrEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Information about an ATMARP Server within a LIS. An		"Information about an ATMARP Server within a LIS. An
	entry in this table has two indexes: first ipAdEntAddr,		entry in this table has two indexes: first ipAdEntAddr,
	which is the IP address that this system uses as a		which is the IP address that this system uses as a
	member of the LIS, and then ipoaArpSrvrAddr, which is		member of the LIS, and then ipoaArpSrvrAddr, which is
	the ATM address of the ATMARP Server.		the ATM address of the ATMARP Server.
	Entries may be created by a management application using		Entries may be created by a management application
	the ipoaArpSrvrRowStatus object. Entries in this		using the ipoaArpSrvrRowStatus object. Entries in this
	table may also be created by the system and not by a		table may also be created by the system and not by a
	management application, for example as a result of ILMI.		management application, for example via ILMI.
	Entries in this table may be deleted by setting the		Entries in this table may be deleted by setting the
	ipoaArpSrvrRowStatus object to 'destroy(6)'. This		ipoaArpSrvrRowStatus object to 'destroy(6)'. This
	includes entries that were added by the system and not by		includes entries that were added by the system and not
	a management application."		by a management application."
	INDEX { ipAdEntAddr, ipoaArpSrvrAddr }		INDEX { ipAdEntAddr, ipoaArpSrvrAddr }
	::= { ipoaArpSrvrTable 1 }		::= { ipoaArpSrvrTable 1 }
	IpoaArpSrvrEntry ::= SEQUENCE {		IpoaArpSrvrEntry ::= SEQUENCE {
	ipoaArpSrvrAddr IpoaAtmAddr,		ipoaArpSrvrAddr IpoaAtmAddr,
	ipoaArpSrvrLis IpAddress,		ipoaArpSrvrLis IpAddress,
	ipoaArpSrvrInArpReqsIn Counter32,		ipoaArpSrvrInArpInReqs Counter32,
	ipoaArpSrvrInArpReqsOut Counter32,		ipoaArpSrvrInArpOutReqs Counter32,
	ipoaArpSrvrInArpRepliesIn Counter32,		ipoaArpSrvrInArpInReplies Counter32,
	ipoaArpSrvrInArpRepliesOut Counter32,		ipoaArpSrvrInArpOutReplies Counter32,
	ipoaArpSrvrInArpInvalidReqsIn Counter32,		ipoaArpSrvrInArpInvalidInReqs Counter32,
	ipoaArpSrvrInArpInvalidReqsOut Counter32,		ipoaArpSrvrInArpInvalidOutReqs Counter32,
	ipoaArpSrvrArpReqsIn Counter32,		ipoaArpSrvrArpInReqs Counter32,
	ipoaArpSrvrArpRepliesOut Counter32,		ipoaArpSrvrArpOutReplies Counter32,
	ipoaArpSrvrArpNaksOut Counter32,		ipoaArpSrvrArpOutNaks Counter32,
	ipoaArpSrvrArpDupIpAddr Counter32,		ipoaArpSrvrArpDupIpAddrs Counter32,
	ipoaArpSrvrArpOpUnknown Counter32,		ipoaArpSrvrArpUnknownOps Counter32,
	ipoaArpSrvrRowStatus RowStatus }		ipoaArpSrvrRowStatus RowStatus }
	ipoaArpSrvrAddr OBJECT-TYPE		ipoaArpSrvrAddr OBJECT-TYPE
	SYNTAX IpoaAtmAddr		SYNTAX IpoaAtmAddr
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATM address of the ATMARP Server."		"The ATM address of the ATMARP Server."
	::= { ipoaArpSrvrEntry 1 }		::= { ipoaArpSrvrEntry 1 }
	ipoaArpSrvrLis OBJECT-TYPE		ipoaArpSrvrLis OBJECT-TYPE
	SYNTAX IpAddress		SYNTAX IpAddress
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The subnet address that identifies the LIS this server		"The subnet address that identifies the LIS with
	is associated with."		which this server is associated."
	::= { ipoaArpSrvrEntry 2 }		::= { ipoaArpSrvrEntry 2 }
	ipoaArpSrvrInArpReqsIn OBJECT-TYPE		ipoaArpSrvrInArpInReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP requests received by this		"The number of InATMARP requests received by this
	ATMARP Server."		ATMARP Server."
	::= { ipoaArpSrvrEntry 3 }		::= { ipoaArpSrvrEntry 3 }
	ipoaArpSrvrInArpReqsOut OBJECT-TYPE		ipoaArpSrvrInArpOutReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP requests sent by this ATMARP		"The number of InATMARP requests sent by this ATMARP
	Server."		Server."
	::= { ipoaArpSrvrEntry 4 }		::= { ipoaArpSrvrEntry 4 }
	ipoaArpSrvrInArpRepliesIn OBJECT-TYPE		ipoaArpSrvrInArpInReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP replies received by this		"The number of InATMARP replies received by this
	ATMARP Server."		ATMARP Server."
	::= { ipoaArpSrvrEntry 5 }		::= { ipoaArpSrvrEntry 5 }
	ipoaArpSrvrInArpRepliesOut OBJECT-TYPE		ipoaArpSrvrInArpOutReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of In_ATMARP replies sent by this ATMARP		"The number of InATMARP replies sent by this ATMARP
	Server."		Server."
	::= { ipoaArpSrvrEntry 6 }		::= { ipoaArpSrvrEntry 6 }
	ipoaArpSrvrInArpInvalidReqsIn OBJECT-TYPE		ipoaArpSrvrInArpInvalidInReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of invalid In_ATMARP requests received by		"The number of invalid InATMARP requests received by
	this ATMARP Server."		this ATMARP Server."
	::= { ipoaArpSrvrEntry 7 }		::= { ipoaArpSrvrEntry 7 }
	ipoaArpSrvrInArpInvalidReqsOut OBJECT-TYPE		ipoaArpSrvrInArpInvalidOutReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times that this server did not receive		"The number of times that this server did not receive
	a In_ATMARP reply."		an InATMARP reply."
	::= { ipoaArpSrvrEntry 8 }		::= { ipoaArpSrvrEntry 8 }
	ipoaArpSrvrArpReqsIn OBJECT-TYPE		ipoaArpSrvrArpInReqs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of ATMARP requests received by this		"Total number of ATMARP requests received by this
	ATMARP Server."		ATMARP Server."
	::= { ipoaArpSrvrEntry 9 }		::= { ipoaArpSrvrEntry 9 }
	ipoaArpSrvrArpRepliesOut OBJECT-TYPE		ipoaArpSrvrArpOutReplies OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of ATMARP replies sent by this ATMARP		"Total number of ATMARP replies sent by this ATMARP
	Server."		Server."
	::= { ipoaArpSrvrEntry 10 }		::= { ipoaArpSrvrEntry 10 }
	ipoaArpSrvrArpNaksOut OBJECT-TYPE		ipoaArpSrvrArpOutNaks OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of negative ATMARP replies sent by this		"Total number of negative ATMARP replies sent by this
	ATMARP Server."		ATMARP Server."
	::= { ipoaArpSrvrEntry 11 }		::= { ipoaArpSrvrEntry 11 }
	ipoaArpSrvrArpDupIpAddr OBJECT-TYPE		ipoaArpSrvrArpDupIpAddrs OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times that a duplicate IP address was		"The number of times that a duplicate IP address was
	detected by this ATMARP Server."		detected by this ATMARP Server."
	::= { ipoaArpSrvrEntry 12 }		::= { ipoaArpSrvrEntry 12 }
	ipoaArpSrvrArpOpUnknown OBJECT-TYPE		ipoaArpSrvrArpUnknownOps OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of times that this ATMARP Server received		"The number of times that this ATMARP Server received
	an ATMARP message with an operation code for which it		an ATMARP message with an operation code for which it
	is not coded to support."		is not coded to support."
	::= { ipoaArpSrvrEntry 13 }		::= { ipoaArpSrvrEntry 13 }
	ipoaArpSrvrRowStatus OBJECT-TYPE		ipoaArpSrvrRowStatus OBJECT-TYPE
	skipping to change at page 31, line 4 ¶		skipping to change at page 31, line 40 ¶
	is not coded to support."		is not coded to support."
	::= { ipoaArpSrvrEntry 13 }		::= { ipoaArpSrvrEntry 13 }
	ipoaArpSrvrRowStatus OBJECT-TYPE		ipoaArpSrvrRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object allows entries to be created and deleted		"This object allows entries to be created and deleted
	from the ipoaArpSrvrTable."		from the ipoaArpSrvrTable."
	REFERENCE		REFERENCE
	"RFC 1903, 'Textual Conventions for version 2 of the		"RFC 1903, 'Textual Conventions for Version 2 of the
	Simple Network Management Protocol (SNMPv2).'"		Simple Network Management Protocol (SNMPv2).'"
	::= { ipoaArpSrvrEntry 14 }		::= { ipoaArpSrvrEntry 14 }
	-- The Remote ATMARP Server Table		-- The Remote ATMARP Server Table
	ipoaArpRemoteSrvrTable OBJECT-TYPE		ipoaArpRemoteSrvrTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaArpRemoteSrvrEntry		SYNTAX SEQUENCE OF IpoaArpRemoteSrvrEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A table of non-local ATMARP Servers associated with a		"A table of non-local ATMARP Servers associated with a
	LIS. An entry in this table has three indexes: first		LIS. An entry in this table has three indexes: first
	the ipoaLisSubnetAddr of the LIS that the corresponding		the ipoaLisSubnetAddr of the LIS for which the
	ATMARP Server provides ATMARP services for, then the		corresponding ATMARP Server provides ATMARP services,
	ipoaArpRemoteSrvrAtmAddr, which is the ATM address of		then the ipoaArpRemoteSrvrAtmAddr, which is the ATM
	the remote ATMARP Server and finally the ifIndex of the		address of the remote ATMARP Server, and finally the
	interface on which the VC to the ATMARP Remote Server		ifIndex of the interface on which the VC to the ATMARP
	will be opened. A ifIndex value of 0 should be used		Remote Server will be opened. An ifIndex value of 0
	when a single VC is to be shared for ATMARP purposes		should be used when a single VC is to be shared for
	by multiple interfaces."		ATMARP purposes by multiple interfaces."
	::= { ipoaObjects 6 }		::= { ipoaObjects 6 }
	ipoaArpRemoteSrvrEntry OBJECT-TYPE		ipoaArpRemoteSrvrEntry OBJECT-TYPE
	SYNTAX IpoaArpRemoteSrvrEntry		SYNTAX IpoaArpRemoteSrvrEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Information about one non-local ATMARP Server."		"Information about one non-local ATMARP Server."
	INDEX { ipoaLisSubnetAddr, ipoaArpRemoteSrvrAtmAddr,		INDEX { ipoaLisSubnetAddr, ipoaArpRemoteSrvrAtmAddr,
	ipoaArpRemoteSrvrIfIndex }		ipoaArpRemoteSrvrIfIndex }
	skipping to change at page 32, line 4 ¶		skipping to change at page 32, line 39 ¶
	ipoaArpRemoteSrvrIpAddr IpAddress,		ipoaArpRemoteSrvrIpAddr IpAddress,
	ipoaArpRemoteSrvrAdminStatus INTEGER,		ipoaArpRemoteSrvrAdminStatus INTEGER,
	ipoaArpRemoteSrvrOperStatus INTEGER }		ipoaArpRemoteSrvrOperStatus INTEGER }
	ipoaArpRemoteSrvrAtmAddr OBJECT-TYPE		ipoaArpRemoteSrvrAtmAddr OBJECT-TYPE
	SYNTAX IpoaAtmAddr		SYNTAX IpoaAtmAddr
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATM address of the remote ATMARP Server."		"The ATM address of the remote ATMARP Server."
	::= { ipoaArpRemoteSrvrEntry 1 }		::= { ipoaArpRemoteSrvrEntry 1 }
	ipoaArpRemoteSrvrRowStatus OBJECT-TYPE		ipoaArpRemoteSrvrRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object allows entries to be created and deleted		"This object allows entries to be created and deleted
	from the ipoaArpRemoteSrvrTable.		from the ipoaArpRemoteSrvrTable.
	Deleting an ipoaArpRemoteSrvrEntry (by setting this		Deleting an ipoaArpRemoteSrvrEntry (by setting this
	object to destroy(6)) may effect ipoaArpClientTable		object to destroy(6)) may affect ipoaArpClientTable
	entries. The object ipoaArpClientSrvrInUse in an		entries. The object ipoaArpClientSrvrInUse in an
	ipoaArpClientSrvrEntry may contain the ATM address		ipoaArpClientSrvrEntry may contain the ATM address
	of a ATMARP Remote Server who's entry in the		of an ATMARP Remote Server whose entry in the
	ipoaArpRemoteSrvrTable is being removed. In this		ipoaArpRemoteSrvrTable is being removed. In this
	case, any corresponding ipoaArpClientSrvrInUse		case, any corresponding ipoaArpClientSrvrInUse
	objects should be at a minimum invalidated by		objects should be at a minimum invalidated by
	setting their values to that of a zero length		setting their values to that of a zero length
	OCTET STRING.		OCTET STRING.
	The value of ipoaArpRemoteSrvrOperStatus should be		The value of ipoaArpRemoteSrvrOperStatus should be
	consistent with that of ipoaArpRemoteSrvrRowStatus.		consistent with that of ipoaArpRemoteSrvrRowStatus.
	For example, successfully setting the value of		For example, successfully setting the value of
	this object to notInService(2) after it being in		this object to notInService(2) after its being in
	the active(1) state should result in		the up(1) state should result in
	ipoaArpRemoteSrvrOperStatus being set to inActive(2)		ipoaArpRemoteSrvrOperStatus being set to down(2)
	if currently active(1)."		if currently up(1)."
	REFERENCE		REFERENCE
	"RFC 1903, 'Textual Conventions for version 2 of the		"RFC 1903, 'Textual Conventions for Version 2 of the
	Simple Network Management Protocol (SNMPv2).'"		Simple Network Management Protocol (SNMPv2).'"
	::= { ipoaArpRemoteSrvrEntry 2 }		::= { ipoaArpRemoteSrvrEntry 2 }
	ipoaArpRemoteSrvrIfIndex OBJECT-TYPE		ipoaArpRemoteSrvrIfIndex OBJECT-TYPE
	SYNTAX InterfaceIndexOrZero		SYNTAX InterfaceIndexOrZero
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ifIndex of the interface that the VC to the		"The ifIndex of the interface that the VC to the
	Remote ATMARP Server is associated with."		Remote ATMARP Server is associated with."
	::= { ipoaArpRemoteSrvrEntry 3 }		::= { ipoaArpRemoteSrvrEntry 3 }
	ipoaArpRemoteSrvrIpAddr OBJECT-TYPE		ipoaArpRemoteSrvrIpAddr OBJECT-TYPE
	SYNTAX IpAddress		SYNTAX IpAddress
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The IP Address of the Remote ATMARP Server. A value of		"The IP Address of the Remote ATMARP Server. A
	0 implies that this address isn't known."		value of 0.0.0.0 implies that this address isn't
	DEFVAL { 0 }		known."
			DEFVAL { '00000000'H }
	::= { ipoaArpRemoteSrvrEntry 4 }		::= { ipoaArpRemoteSrvrEntry 4 }
	ipoaArpRemoteSrvrAdminStatus OBJECT-TYPE		ipoaArpRemoteSrvrAdminStatus OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	active(1), -- use this ATMARP Server		up(1), -- use this ATMARP Server
	inActive(2) -- stop using this ATMARP Server		down(2) -- stop using this ATMARP Server
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The desired state for use of the ATMARP Server		"The desired state for use of the ATMARP Server
	represented by an entry in this table.		represented by an entry in this table.
	ipoaArpRemoteSrvrAdminStatus values:		ipoaArpRemoteSrvrAdminStatus values:
	active(1) - Attempt to activate use of the		up(1) - Attempt to activate use of the
	ATMARP Server represented by this		ATMARP Server represented by this
	entry in the ipoaArpRemoteSrvrTable.		entry in the ipoaArpRemoteSrvrTable.
	inActive(2) - Inactivate use of this ATMARP		down(2) - Deactivate use of this ATMARP
	Server.		Server.
	When a managed system creates an entry in this		When a managed system creates an entry in this
	table ipoaArpRemoteSrvrAdminStatus and		table ipoaArpRemoteSrvrAdminStatus and
	ipoaArpRemoteSrvrOperStatus are initialized as		ipoaArpRemoteSrvrOperStatus are initialized as
	inActive(2) by default."		down(2) by default."
	DEFVAL { inActive }		DEFVAL { down }
	::= { ipoaArpRemoteSrvrEntry 5 }		::= { ipoaArpRemoteSrvrEntry 5 }
	ipoaArpRemoteSrvrOperStatus OBJECT-TYPE		ipoaArpRemoteSrvrOperStatus OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	active(1), -- eligible for use		up(1), -- eligible for use
	inActive(2) -- not eligible for use		down(2) -- not eligible for use
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The current operational state for use of a Remote		"The current operational state for use of a Remote
	ATMARP Server. An active(1) entry has a VC		ATMARP Server. An up(1) entry has a VC
	established to the respective Remote ATMARP		established to the respective Remote ATMARP
	Server:		Server:
	active(1) - A VC exists to Remote ATMARP Server		up(1) - A VC exists to Remote ATMARP Server
	who's IP Address is stored in		whose IP Address is stored in
	ipoaArpRemoteSrvrIpAddr. This VC can		ipoaArpRemoteSrvrIpAddr. This VC can
	be determined by searching the		be determined by searching the
	ipoaVcTable using		ipoaVcTable using
	ipoaArpRemoteSrvrIfIndex (if not 0		ipoaArpRemoteSrvrIfIndex (if not 0,
	otherwise ignore ipNetToMediaIfIndex		otherwise ignore ipNetToMediaIfIndex
	index) and ipoaArpRemoteSrvrIpAddr.		index) and ipoaArpRemoteSrvrIpAddr.
	A ipoaArpClientEntry should exist		An ipoaArpClientEntry should exist
	with its ipoaArpClientSrvrInUse		with its ipoaArpClientSrvrInUse
	object having the same value as		object having the same value as
	ipoaArpRemoteSrvrAtmAddr.		ipoaArpRemoteSrvrAtmAddr.
	inActive(2) - Entry exists without an active VC to		down(2) - Entry exists without an active VC to
	the Remote ATMARP Server.		the Remote ATMARP Server.
	Transition from an active(1) to an inActive(2)		Transition from up(1) to down(2)
	status may effect ipoaArpClientTable entries.		status may affect ipoaArpClientTable entries.
	The object ipoaArpClientSrvrInUse in an		The object ipoaArpClientSrvrInUse in an
	ipoaArpClientSrvrEntry may contain the ATM address		ipoaArpClientSrvrEntry may contain the ATM address
	of a ATMARP Remote Server who's entry in the		of an ATMARP Remote Server whose entry in the
	ipoaArpRemoteSrvrTable is being inactivated. In		ipoaArpRemoteSrvrTable is being deactivated. In
	this case, any corresponding ipoaArpClientSrvrInUse		this case, any corresponding ipoaArpClientSrvrInUse
	objects should be at a minimum invalidated by		objects should be at a minimum invalidated by
	setting their values to that of a zero length		setting their values to that of a zero length
	OCTET STRING.		OCTET STRING.
	If ipoaArpRemoteSrvrAdminStatus is inActive(2) then		If ipoaArpRemoteSrvrAdminStatus is down(2) then
	ipoaArpRemoteSrvrOperStatus should be inActive(2).		ipoaArpRemoteSrvrOperStatus should be down(2).
	If ipoaArpRemoteSrvrAdminStatus is changed to		If ipoaArpRemoteSrvrAdminStatus is changed to
	active(1) then ipoaArpRemoteSrvrOperStatus should		up(1) then ipoaArpRemoteSrvrOperStatus should
	change to active(1) if the Remote ATMARP Server		change to up(1) if the Remote ATMARP Server
	entry can be activated."		entry can be activated."
	DEFVAL { inActive }		DEFVAL { down }
	::= { ipoaArpRemoteSrvrEntry 6 }		::= { ipoaArpRemoteSrvrEntry 6 }
	-- The VC Table		-- The ATM VC Table
	ipoaVcTable OBJECT-TYPE		ipoaVcTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaVcEntry		SYNTAX SEQUENCE OF IpoaVcEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A system that support IP over ATM is an IP system and		"A system that supports IP over ATM is an IP system and
	therefore MUST support all of the appropriate tables		therefore MUST support all of the appropriate tables in
	from RFC1213, MIB-II. This includes the		the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233),
	ipNetToMediaTable (the ARP cache). The ipoaVcTable		the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012), and
			the UDP-MIB (RFC 2013). This includes the
			ipNetToMediaTable (the ARP cache) that is defined
			within the IP-MIB (RFC 2011). The ipoaVcTable
	keeps a set of VCs for each entry in the ARP cache		keeps a set of VCs for each entry in the ARP cache
	that was put there by a IP over ATM system acting		that was put there by an IP over ATM system acting
	as either a host or server. The ipoaVcTable doesn't		as either a host or server. The ipoaVcTable doesn't
	augment the ipNetToMediaTable (ARP Cache) since the		augment the ipNetToMediaTable (ARP Cache) since the
	the correspondence between tables is not one-to-one.		the correspondence between tables is not necessarily
			one-to-one.
	An ipNetToMediaPhysAddress object should contain the		An ipNetToMediaPhysAddress object should contain the
	content as defined by the IpoaAtmAddr textual		content as defined by the IpoaAtmAddr textual
	convention when used to hold a IPOA-MIB ATM Address."		convention when used to hold an IPOA-MIB ATM Address."
	::= { ipoaObjects 7 }		::= { ipoaObjects 7 }
	ipoaVcEntry OBJECT-TYPE		ipoaVcEntry OBJECT-TYPE
	SYNTAX IpoaVcEntry		SYNTAX IpoaVcEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A VC (permanent or switched) that this host or server		"A VC (permanent or switched) that this host or server
	has opened with another member of a LIS. Additional		has opened with another member of a LIS. Additional
	information can be determined about the VC from the		information can be determined about the VC from the
	ATM-MIB, the AToM MIB.		ATM-MIB.
	In an SVC environment, entries can not be created in		Entries in this table cannot be created by management
	this table by a management application. Entries are		applications.
	automatically added by the system as the result of
	ATMARP processing.		In an SVC environment, an entry is automatically added
			by the system as the result of ATMARP processing.
	In a PVC environment, an entry is automatically added		In a PVC environment, an entry is automatically added
	to this table when an entry is created in the		to this table when an entry is created in the
	ipoaConfigPvcTable and the IP Address at the end of		ipoaConfigPvcTable and the IP Address at the remote
	the PVC is discovered using In_ATMARP. An entry also		end of the PVC is discovered using InATMARP. An
	is added to the ipNetToMediaTable."		entry also is added to the ipNetToMediaTable."
	INDEX { ipNetToMediaIfIndex,		INDEX { ipNetToMediaIfIndex,
	ipNetToMediaNetAddress,		ipNetToMediaNetAddress,
	ipoaVcVpi,		ipoaVcVpi,
	ipoaVcVci		ipoaVcVci
	}		}
	::= { ipoaVcTable 1 }		::= { ipoaVcTable 1 }
	IpoaVcEntry ::= SEQUENCE {		IpoaVcEntry ::= SEQUENCE {
	ipoaVcVpi IpoaVpiInteger,		ipoaVcVpi IpoaVpiInteger,
	ipoaVcVci IpoaVciInteger,		ipoaVcVci IpoaVciInteger,
	skipping to change at page 36, line 35 ¶		skipping to change at page 37, line 28 ¶
	::= { ipoaVcEntry 4 }		::= { ipoaVcEntry 4 }
	ipoaVcNegotiatedMtu OBJECT-TYPE		ipoaVcNegotiatedMtu OBJECT-TYPE
	SYNTAX Integer32 (0..65535)		SYNTAX Integer32 (0..65535)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The MTU used when communicating over this circuit."		"The MTU used when communicating over this circuit."
	::= { ipoaVcEntry 5 }		::= { ipoaVcEntry 5 }
			-- The ATM Config PVC Table
	ipoaConfigPvcTable OBJECT-TYPE		ipoaConfigPvcTable OBJECT-TYPE
	SYNTAX SEQUENCE OF IpoaConfigPvcEntry		SYNTAX SEQUENCE OF IpoaConfigPvcEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table MUST be supported when PVCs are intended to		"This table MUST be supported when PVCs are intended to
	be supported in order to enable the setup of PVCs for		be supported in order to enable the setup of PVCs for
	use by IP."		use by IP."
	::= { ipoaObjects 8 }		::= { ipoaObjects 8 }
	ipoaConfigPvcEntry OBJECT-TYPE		ipoaConfigPvcEntry OBJECT-TYPE
	SYNTAX IpoaConfigPvcEntry		SYNTAX IpoaConfigPvcEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Defines a single PVC that exists at this host for use		"Defines a single PVC that exists at this host for
	by IP. "		use by IP."
	INDEX { ipoaConfigPvcIfIndex,		INDEX { ipoaConfigPvcIfIndex,
	ipoaConfigPvcVpi,		ipoaConfigPvcVpi,
	ipoaConfigPvcVci		ipoaConfigPvcVci
	}		}
	::= { ipoaConfigPvcTable 1 }		::= { ipoaConfigPvcTable 1 }
	IpoaConfigPvcEntry ::= SEQUENCE {		IpoaConfigPvcEntry ::= SEQUENCE {
	ipoaConfigPvcIfIndex InterfaceIndex,		ipoaConfigPvcIfIndex InterfaceIndex,
	ipoaConfigPvcVpi IpoaVpiInteger,		ipoaConfigPvcVpi IpoaVpiInteger,
	ipoaConfigPvcVci IpoaVciInteger,		ipoaConfigPvcVci IpoaVciInteger,
	skipping to change at page 37, line 48 ¶		skipping to change at page 38, line 42 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The VCI value for the Virtual Circuit."		"The VCI value for the Virtual Circuit."
	::= { ipoaConfigPvcEntry 3 }		::= { ipoaConfigPvcEntry 3 }
	ipoaConfigPvcDefaultMtu OBJECT-TYPE		ipoaConfigPvcDefaultMtu OBJECT-TYPE
	SYNTAX Integer32 (0..65535)		SYNTAX Integer32 (0..65535)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Classic2 allows use of other MTU values for PVCs		"Classical IP and ARP over ATM allows use of
	but considers the how a value other than 9180 could		other MTU values for PVCs but considers how a
	be selected to be out of scope. ipoaConfigPvcDefaultMtu		value other than 9180 could be selected to be out
	can be used to configure the MTU to be used for the PVC.		of scope. ipoaConfigPvcDefaultMtu can be used to
			configure the MTU to be used for the PVC.
	Both ends MUST have the same value configured."		Both ends MUST have the same value configured."
	DEFVAL { 9180 }		DEFVAL { 9180 }
	::= { ipoaConfigPvcEntry 4 }		::= { ipoaConfigPvcEntry 4 }
	ipoaConfigPvcRowStatus OBJECT-TYPE		ipoaConfigPvcRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object allows rows to be created and deleted in the		"This object allows rows to be created and deleted in
	ipoaConfigPvcTable. Creation of a entry in this table		the ipoaConfigPvcTable. Creation of an entry in this
	should eventually result in the creation of a		table should eventually result in the creation of an
	ipNetToMediaEntry and a corresponding ipoaVcEntry		ipNetToMediaEntry and a corresponding ipoaVcEntry
	after In_ATMARP has determined the destination address of		after InATMARP has determined the destination address
	system that the PVC is connected to. Setting this object		of the remote system that the PVC is connected to.
	to destroy(6) should remove the corresponding		Setting this object to destroy(6) should remove the
	ipNetToMediaTable and ipoaVcTable entries."		corresponding ipNetToMediaTable and ipoaVcTable
			entries."
	REFERENCE		REFERENCE
	"RFC 1903, 'Textual Conventions for version 2 of the		"RFC 1903, 'Textual Conventions for Version 2 of the
	Simple Network Management Protocol (SNMPv2).'"		Simple Network Management Protocol (SNMPv2).'"
	::= { ipoaConfigPvcEntry 5 }		::= { ipoaConfigPvcEntry 5 }
	-- Notifications		-- Notifications
			ipoaTrapPrefix OBJECT IDENTIFIER ::= { ipoaNotifications 0 }
	ipoaMtuExceeded NOTIFICATION-TYPE		ipoaMtuExceeded NOTIFICATION-TYPE
	OBJECTS {		OBJECTS {
	ipoaVcNegotiatedMtu		ipoaVcNegotiatedMtu
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A frame was received that exceeds the negotiated		"A frame was received that exceeds the negotiated
	MTU size. The vpi and vci of the VC for which this		MTU size. The VPI and VCI of the VC for which this
	condition was detected can be determined from the		condition was detected can be determined from the
	index vlaues for ipoaVcNegotiatedMtu. In addition,		index values for ipoaVcNegotiatedMtu. In addition,
	the ifIndex and IP Address can be determined as		the ifIndex and IP Address can be determined as
	well, refer to the ipoaVcTable."		well (refer to the ipoaVcTable)."
	::= { ipoaNotifications 1 }		::= { ipoaTrapPrefix 1 }
	ipoaDuplicateIpAddress NOTIFICATION-TYPE		ipoaDuplicateIpAddress NOTIFICATION-TYPE
	OBJECTS {		OBJECTS {
	ipNetToMediaIfIndex,		ipNetToMediaIfIndex,
	ipNetToMediaNetAddress,		ipNetToMediaNetAddress,
	ipNetToMediaPhysAddress,		ipNetToMediaPhysAddress,
	ipNetToMediaPhysAddress		ipNetToMediaPhysAddress
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ATMARP Server has detected more than one ATM end		"The ATMARP Server has detected more than one ATM end
	point attempting to associate the same IP address with		point attempting to associate the same IP address with
	different ATM hardware addresses."		different ATM addresses."
	::= { ipoaNotifications 2 }
			::= { ipoaTrapPrefix 2 }
	ipoaLisCreate NOTIFICATION-TYPE		ipoaLisCreate NOTIFICATION-TYPE
	OBJECTS {		OBJECTS {
	ipoaLisSubnetAddr		ipoaLisSubnetAddr
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Generation of this trap occurs when a ipoaLisEntry is		"Generation of this trap occurs when an ipoaLisEntry is
	created and ipoaLisTrapEnable is enabled(1)."		created while the ipoaLisTrapEnable.0 object has the
	::= { ipoaNotifications 3 }		value enabled(1)."
			::= { ipoaTrapPrefix 3 }
	ipoaLisDelete NOTIFICATION-TYPE		ipoaLisDelete NOTIFICATION-TYPE
	OBJECTS {		OBJECTS {
	ipoaLisSubnetAddr		ipoaLisSubnetAddr
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Generation of this trap occurs when a ipoaLisEntry is		"Generation of this trap occurs when an ipoaLisEntry is
	deleted and ipoaLisTrapEnable is enabled(1)."		deleted while the ipoaLisTrapEnable.0 object has the
	::= { ipoaNotifications 4 }		value enabled(1)."
			::= { ipoaTrapPrefix 4 }
	-- Conformance Definitions		-- Conformance Definitions
	ipoaGroups OBJECT IDENTIFIER ::= { ipoaConformance 1 }		ipoaGroups OBJECT IDENTIFIER ::= { ipoaConformance 1 }
	ipoaCompliances OBJECT IDENTIFIER ::= { ipoaConformance 2 }		ipoaCompliances OBJECT IDENTIFIER ::= { ipoaConformance 2 }
	-- compliance statements		-- compliance statements
	ipoaCompliance MODULE-COMPLIANCE		ipoaCompliance MODULE-COMPLIANCE
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The compliance statement for agents that support the		"The compliance statement for agents that support the
	IPOA-MIB."		IPOA-MIB."
	MODULE -- this module		MODULE -- this module
	MANDATORY-GROUPS { ipoaGeneralGroup,		MANDATORY-GROUPS { ipoaGeneralGroup,
	ipoaBasicNotificationsGroup		ipoaBasicNotificationsGroup
	}		}
	GROUP ipoaClientGroup		GROUP ipoaClientGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for all hosts where IP		"This group is mandatory for all hosts where IP
	over ATM client support is required."		over ATM client support is present."
	GROUP ipoaSrvrGroup		GROUP ipoaSrvrGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for all hosts where ATMARP		"This group is mandatory for all hosts where ATMARP
	Servers are present."		Servers are present."
			GROUP ipoaSrvrNotificationsGroup
	GROUP ipoaSrvrNotificationsGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for all hosts where ATMARP		"This group is mandatory for all hosts where ATMARP
	Servers are present."		Servers are present."
			GROUP ipoaLisNotificationsGroup
			DESCRIPTION
			"This group is mandatory for all hosts where
			ATMARP client only support is present and
			ipoaLisTrapEnable is allowed to be set to
			enabled(1)."
			GROUP ipoaLisTableGroup
			DESCRIPTION
			"This group is mandatory for all entities which
			support IP over ATM SVCs. Support of objects in
			this group by IP over ATM clients which only
			support IP over ATM PVCs is optional."
	OBJECT ipoaLisDefaultMtu		OBJECT ipoaLisDefaultMtu
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to allow the user to		"The agent is not required to allow the user
	change the default MTU from the value 9180.		to change the default MTU from the value 9180.
	The agent is not required to support a SET		The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaLisDefaultEncapsType		OBJECT ipoaLisDefaultEncapsType
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to allow the user to		"The agent is not required to allow the user to
	specify the default encapsulation type for the		specify the default encapsulation type for the
	skipping to change at page 41, line 21 ¶		skipping to change at page 42, line 34 ¶
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support a SET		"The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaLisRetries		OBJECT ipoaLisRetries
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to allow the user		"The agent is not required to allow the user
	to change the default number of times a ATMARP		to change the default number of times an ATMARP
	request will be retried when no response is		request will be retried when no response is
	received from the default of 2.		received from the default of 2.
	The agent is not required to support a SET		The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaLisTimeout		OBJECT ipoaLisTimeout
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	skipping to change at page 42, line 5 ¶		skipping to change at page 43, line 18 ¶
	"Implementations that do not support IP over		"Implementations that do not support IP over
	ATM SVC usage are not required to allow the		ATM SVC usage are not required to allow the
	user to specify a best effort default peak cell		user to specify a best effort default peak cell
	rate since typically the ipoaLisTable won't		rate since typically the ipoaLisTable won't
	exist.		exist.
	The agent is not required to support a SET		The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaLisIfMappingStatus		OBJECT ipoaLisIfMappingRowStatus
	MIN-ACCESS read-only		SYNTAX INTEGER {
			active(1) -- subset of RowStatus
			}
			MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support a SET		"The agent is not required to support a SET
	operation to this object in the absence of		operation to this object, and only one
	adequate security. In this case show the		of the six enumerated values for the
	value of this object as being either active(1)		RowStatus textual convention need be
	or notInService(2) depending on the associating		supported, specifically: active(1)."
	interface entry's ifOperStatus. Don't allow
	set support."
	OBJECT ipoaArpClientAtmAddr		OBJECT ipoaArpClientAtmAddr
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support a SET		"The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaArpSrvrLis		OBJECT ipoaArpSrvrLis
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support a SET		"The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaArpRemoteSrvrAdminStatus		OBJECT ipoaArpRemoteSrvrAdminStatus
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support a SET		"The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security. In this case the value of		adequate security. In this case the value of
	this object should be active(1) when a VC		this object should be up(1) when a VC
	exists to the Remote ATMARP Server or		exists to the Remote ATMARP Server or
	otherwise inActive(2). Don't allow set		otherwise down(2), and the agent should not
	support. ipoaArpRemoteSrvrOperStatus would		allow a SET operation to this object."
	have the same value as
	ipoaArpRemoteSrvrAdminStatus."
	OBJECT ipoaConfigPvcDefaultMtu		OBJECT ipoaConfigPvcDefaultMtu
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support a SET		"The agent is not required to support a SET
	operation to this object in the absence of		operation to this object in the absence of
	adequate security."		adequate security."
	OBJECT ipoaLisRowStatus		OBJECT ipoaLisRowStatus
	MIN-ACCESS read-only		SYNTAX INTEGER {
			active(1) -- subset of RowStatus
			}
			MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support this		"Write access is not required, and only one
	object in the absence of adequate security		of the six enumerated values for the
	or when remote creation is not enabled."		RowStatus textual convention need be
			supported, specifically: active(1)."
	OBJECT ipoaArpClientRowStatus		OBJECT ipoaArpClientRowStatus
	MIN-ACCESS read-only		SYNTAX INTEGER {
			active(1) -- subset of RowStatus
			}
			MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support this		"Write access is not required, and only one
	object in the absence of adequate security		of the six enumerated values for the
	or when remote creation is not enabled."		RowStatus textual convention need be
			supported, specifically: active(1)."
	OBJECT ipoaArpRemoteSrvrRowStatus		OBJECT ipoaArpRemoteSrvrRowStatus
	MIN-ACCESS read-only		SYNTAX INTEGER {
			active(1) -- subset of RowStatus
			}
			MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support this		"Write access is not required, and only one
	object in the absence of adequate security		of the six enumerated values for the
	or when remote creation is not enabled."		RowStatus textual convention need be
			supported, specifically: active(1)."
	OBJECT ipoaArpSrvrRowStatus		OBJECT ipoaArpSrvrRowStatus
	MIN-ACCESS read-only		SYNTAX INTEGER {
			active(1) -- subset of RowStatus
			}
			MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support this		"Write access is not required, and only one
	object in the absence of adequate security		of the six enumerated values for the
	or when remote creation is not enabled."		RowStatus textual convention need be
			supported, specifically: active(1)."
	OBJECT ipoaConfigPvcRowStatus		OBJECT ipoaConfigPvcRowStatus
	MIN-ACCESS read-only		SYNTAX INTEGER {
			active(1) -- subset of RowStatus
			}
			MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The agent is not required to support this		"Write access is not required, and only one
	object in the absence of adequate security		of the six enumerated values for the
	or when remote creation is not enabled."		RowStatus textual convention need be
			supported, specifically: active(1)."
			OBJECT ipoaArpClientArpOutNaks
			MIN-ACCESS not-accessible
			DESCRIPTION
			"Classic IP and ARP over ATM does not require
			an ATMARP client to transmit an ATMARP_NAK
			upon receipt of an ATMARP request from another
			ATMARP client. This object should be
			implemented when an ATMARP client supports the
			transmission of ATMARP_NAKs."
	::= { ipoaCompliances 1 }		::= { ipoaCompliances 1 }
	-- units of conformance		-- units of conformance
	ipoaGeneralGroup OBJECT-GROUP		ipoaGeneralGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
			ipoaLisTrapEnable,
	ipoaLisSubnetAddr,		ipoaLisSubnetAddr,
	ipoaLisDefaultMtu,		ipoaLisDefaultMtu,
	ipoaLisDefaultEncapsType,		ipoaLisDefaultEncapsType,
	ipoaLisInactivityTimer,		ipoaLisInactivityTimer,
	ipoaLisMinHoldingTime,		ipoaLisMinHoldingTime,
	ipoaLisQDepth,		ipoaLisQDepth,
	ipoaLisMaxCalls,		ipoaLisMaxCalls,
	ipoaLisCacheEntryAge,		ipoaLisCacheEntryAge,
	ipoaLisRetries,		ipoaLisRetries,
	ipoaLisTimeout,		ipoaLisTimeout,
	ipoaLisDefaultPeakCellRate,		ipoaLisDefaultPeakCellRate,
	ipoaLisActiveVcs,		ipoaLisActiveVcs,
	ipoaLisRowStatus,		ipoaLisRowStatus,
	ipoaLisIfMappingStatus,		ipoaLisIfMappingRowStatus,
	ipoaArpRemoteSrvrRowStatus,		ipoaArpRemoteSrvrRowStatus,
	ipoaArpRemoteSrvrIpAddr,		ipoaArpRemoteSrvrIpAddr,
	ipoaArpRemoteSrvrAdminStatus,		ipoaArpRemoteSrvrAdminStatus,
	ipoaArpRemoteSrvrOperStatus,		ipoaArpRemoteSrvrOperStatus,
	ipoaVcType,		ipoaVcType,
	ipoaVcNegotiatedEncapsType,		ipoaVcNegotiatedEncapsType,
	ipoaVcNegotiatedMtu,		ipoaVcNegotiatedMtu,
	ipoaConfigPvcDefaultMtu,		ipoaConfigPvcDefaultMtu,
	ipoaConfigPvcRowStatus		ipoaConfigPvcRowStatus
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The required objects."		"This group is mandatory for all IP over ATM entities."
	::= { ipoaGroups 1 }		::= { ipoaGroups 1 }
	ipoaClientGroup OBJECT-GROUP		ipoaClientGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	ipoaArpClientAtmAddr,		ipoaArpClientAtmAddr,
	ipoaArpClientSrvrInUse,		ipoaArpClientSrvrInUse,
	ipoaArpClientInArpReqsIn,		ipoaArpClientInArpInReqs,
	ipoaArpClientInArpReqsOut,		ipoaArpClientInArpOutReqs,
	ipoaArpClientInArpRepliesIn,		ipoaArpClientInArpInReplies,
	ipoaArpClientInArpRepliesOut,		ipoaArpClientInArpOutReplies,
	ipoaArpClientInArpInvalidReqsIn,		ipoaArpClientInArpInvalidInReqs,
	ipoaArpClientInArpInvalidReqsOut,		ipoaArpClientInArpInvalidOutReqs,
	ipoaArpClientArpReqsIn,		ipoaArpClientArpInReqs,
	ipoaArpClientArpReqsOut,		ipoaArpClientArpOutReqs,
	ipoaArpClientArpRepliesIn,		ipoaArpClientArpInReplies,
	ipoaArpClientArpRepliesOut,		ipoaArpClientArpOutReplies,
	ipoaArpClientArpNaksIn,		ipoaArpClientArpInNaks,
	ipoaArpClientArpNaksOut,		ipoaArpClientArpOutNaks,
	ipoaArpClientArpOpUnknown,		ipoaArpClientArpUnknownOps,
	ipoaArpClientArpSrvrNoResp,		ipoaArpClientArpNoSrvrResps,
	ipoaArpClientRowStatus		ipoaArpClientRowStatus
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for all hosts where IP over		"This group is mandatory for all hosts where an IP
	ATM client support is required."		over ATM client is present."
	::= { ipoaGroups 2 }		::= { ipoaGroups 2 }
	ipoaSrvrGroup OBJECT-GROUP		ipoaSrvrGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	ipoaLisTrapEnable,
	ipoaArpSrvrLis,		ipoaArpSrvrLis,
	ipoaArpSrvrInArpReqsIn,		ipoaArpSrvrInArpInReqs,
	ipoaArpSrvrInArpReqsOut,		ipoaArpSrvrInArpOutReqs,
	ipoaArpSrvrInArpRepliesIn,		ipoaArpSrvrInArpInReplies,
	ipoaArpSrvrInArpRepliesOut,		ipoaArpSrvrInArpOutReplies,
	ipoaArpSrvrInArpInvalidReqsIn,		ipoaArpSrvrInArpInvalidInReqs,
	ipoaArpSrvrInArpInvalidReqsOut,		ipoaArpSrvrInArpInvalidOutReqs,
	ipoaArpSrvrArpReqsIn,		ipoaArpSrvrArpInReqs,
	ipoaArpSrvrArpRepliesOut,		ipoaArpSrvrArpOutReplies,
	ipoaArpSrvrArpNaksOut,		ipoaArpSrvrArpOutNaks,
	ipoaArpSrvrArpDupIpAddr,		ipoaArpSrvrArpDupIpAddrs,
	ipoaArpSrvrArpOpUnknown,		ipoaArpSrvrArpUnknownOps,
	ipoaArpSrvrRowStatus		ipoaArpSrvrRowStatus
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for all hosts where ATMARP		"This group is mandatory for all hosts where ATMARP
	Servers are present."		Servers are present."
	::= { ipoaGroups 3 }		::= { ipoaGroups 3 }
	ipoaBasicNotificationsGroup NOTIFICATION-GROUP		ipoaBasicNotificationsGroup NOTIFICATION-GROUP
	NOTIFICATIONS {		NOTIFICATIONS {
	ipoaMtuExceeded		ipoaMtuExceeded
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The notifications which an IP over ATM entity		"The notification which an IP over ATM entity
	is required to implement."		is required to implement."
	::= { ipoaGroups 4 }		::= { ipoaGroups 4 }
	ipoaSrvrNotificationsGroup NOTIFICATION-GROUP		ipoaSrvrNotificationsGroup NOTIFICATION-GROUP
	NOTIFICATIONS {		NOTIFICATIONS {
	ipoaDuplicateIpAddress,		ipoaDuplicateIpAddress
	ipoaLisCreate,
	ipoaLisDelete
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The notifications which an IP over ATM ATMARP		"The notification which an IP over ATM ATMARP
	Server is required to implement."		Server is required to implement."
	::= { ipoaGroups 5 }		::= { ipoaGroups 5 }
			ipoaLisNotificationsGroup NOTIFICATION-GROUP
			NOTIFICATIONS {
			ipoaLisCreate,
			ipoaLisDelete
			}
			STATUS current
			DESCRIPTION
			"The LIS-related notifications which are required
			to be implemented by an IP over ATM ATMARP server,
			as well as by any IP over ATM client which allows
			ipoaLisTrapEnable to be set to enabled(1)."
			::= { ipoaGroups 6 }
			ipoaLisTableGroup OBJECT-GROUP
			OBJECTS {
			ipoaLisTrapEnable,
			ipoaLisSubnetAddr,
			ipoaLisDefaultMtu,
			ipoaLisDefaultEncapsType,
			ipoaLisInactivityTimer,
			ipoaLisMinHoldingTime,
			ipoaLisQDepth,
			ipoaLisMaxCalls,
			ipoaLisCacheEntryAge,
			ipoaLisRetries,
			ipoaLisTimeout,
			ipoaLisDefaultPeakCellRate,
			ipoaLisActiveVcs,
			ipoaLisRowStatus,
			ipoaLisIfMappingRowStatus,
			ipoaArpRemoteSrvrRowStatus,
			ipoaArpRemoteSrvrIpAddr,
			ipoaArpRemoteSrvrAdminStatus,
			ipoaArpRemoteSrvrOperStatus
			}
			STATUS current
			DESCRIPTION
			"This group is mandatory for all entities which
			support IP over ATM SVCs. Support of objects in
			this group by IP over ATM clients which only
			support IP over ATM PVCs is optional."
			::= { ipoaGroups 7 }
	END		END
	5. Security Considerations		5. Security Considerations
	Certain management information defined in this MIB MAY be considered		Certain management information defined in this MIB MAY be considered
	sensitive in some network environments. Therefore, authentication of		sensitive in some network environments. Therefore, authentication of
	received SNMP requests and controlled access to management information		received SNMP requests and controlled access to management information
	SHOULD be employed in such environments. The method for this		SHOULD be employed in such environments. The method for this
	authentication is a function of the SNMP Administrative Framework, and		authentication is a function of the SNMP Administrative Framework, and
	has not been expanded by this MIB.		has not been expanded by this MIB.
	Several objects in this MIB allow write access or provide for remote		Several objects in this MIB allow write access or provide for row
	creation. Allowing this support in a non-secure environment can have a		creation. Allowing this support in a non-secure environment can have
	negative effect on network operations. It is RECOMMENDED that		a negative effect on network operations. It is RECOMMENDED that
	implementers seriously consider whether set operations MAY be allowed		implementers seriously consider whether set operations or row creation
	without providing, at a minimum, authentication of request origin. It		be allowed without providing, at a minimum, authentication of request
	it RECOMMENDED that without such support that the following objects be		origin. It is RECOMMENDED that without such support that the
	implemented as read-only:		following objects be implemented as read-only:
	o ipoaLisDefaultMtu		o ipoaLisDefaultMtu
	o ipoaLisDefaultEncapsType		o ipoaLisDefaultEncapsType
	o ipoaLisInactivityTimer		o ipoaLisInactivityTimer
	o ipoaLisMinHoldingTime		o ipoaLisMinHoldingTime
	o ipoaLisQDepth		o ipoaLisQDepth
	o ipoaLisMaxCalls		o ipoaLisMaxCalls
	o ipoaLisCacheEntryAge		o ipoaLisCacheEntryAge
	o ipoaLisRetries		o ipoaLisRetries
	o ipoaLisTimeout		o ipoaLisTimeout
	o ipoaLisDefaultPeakCellRate		o ipoaLisDefaultPeakCellRate
	o ipoaLisIfMappingStatus, show state as being either active(1) or
	notInService(2) depending on the associating interface entry's
	ifOperStatus. Don't allow set support.
	o ipoaArpClientAtmAddr		o ipoaArpClientAtmAddr
	o ipoaArpSrvrLis		o ipoaArpSrvrLis
	o ipoaArpRemoteSrvrAdminStatus, show status as being either		o ipoaArpRemoteSrvrAdminStatus, show status as being either
	active(1) when a VC exists to the Remote ATMARP Server or		up(1) when a VC exists to the Remote ATMARP Server or
	otherwise inActive(2). Don't allow set support.		otherwise down(2). Don't allow set support.
	ipoaArpRemoteSrvrOperStatus would have the same value as		ipoaArpRemoteSrvrOperStatus would have the same value as
	ipoaArpRemoteSrvrAdminStatus.		ipoaArpRemoteSrvrAdminStatus.
	o ipoaConfigPvcDefaultMtu		o ipoaConfigPvcDefaultMtu
	The following objects SHOULD either be implemented as read-only or not
	implemented when security is an issue as previously discussed:
	o ipoaLisRowStatus		o ipoaLisRowStatus
	o ipoaArpClientRowStatus		o ipoaArpClientRowStatus
	o ipoaArpRemoteSrvrRowStatus		o ipoaArpRemoteSrvrRowStatus
	o ipoaArpSrvrRowStatus		o ipoaArpSrvrRowStatus
	o ipoaConfigPvcRowStatus		o ipoaConfigPvcRowStatus
			o ipoaLisIfMappingRowStatus
	6. Acknowledgments		6. Intellectual Property
			The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to pertain
			to the implementation or use of the technology described in this
			document or the extent to which any license under such rights might or
			might not be available; neither does it represent that it has made any
			effort to identify any such rights. Information on the IETF's
			procedures with respect to rights in standards-track and standards-
			related documentation can be found in BCP-11. Copies of claims of
			rights made available for publication and any assurances of licenses
			to be made available, or the result of an attempt made to obtain a
			general license or permission for the use of such proprietary rights
			by implementors or users of this specification can be obtained from
			the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			7. Acknowledgments
	This document is a product of the Internetworking Over NBMA Working		This document is a product of the Internetworking Over NBMA Working
	Group. The authors of this document would like to recognize Keith		Group. The authors of this document would like to recognize Keith
	McCloghrie from Cisco Systems for his support as our mentor from the		McCloghrie from Cisco Systems for his support as our mentor from the
	Network Management Area.		Network Management Area.
	7. References		8. References
	[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and		[1] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure
	Waldbusser S., "Structure of Management Information for version 2		of Management Information for Version 2 of the Simple Network
	of the Simple Network Management Protocol (SNMPv2)", RFC 1902,		Management Protocol (SNMPv2)", RFC 1902, January 1996.
	January 1996.
	[2] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB		[2] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB
	using SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997		using SMIv2", RFC 2233, November 1997.
	[3] Network Working Group, Laubach M., and Halpern J., "Classical IP		[3] Laubach M., and Halpern J., "Classical IP and ARP over ATM",
	and ARP over ATM", Internet Draft, March 26, 1997		Internet Draft, March 26, 1997.
	[4] Ahmed, M., and Tesink, K., "Definitions of Managed Objects for ATM		[4] Ahmed, M., and Tesink, K., "Definitions of Managed Objects for ATM
	Management Version 8.0 using SMIv2", RFC 1695, Bell Communications		Management Version 8.0 using SMIv2", RFC 1695, August 1994.
	Research, August 1994.
	[5] McCloghrie, K., and M. Rose, Editors, "Management Information Base		[5] McCloghrie, K., and M. Rose, Editors, "Management Information Base
	for Network Management of TCP/IP-based internets: MIB-II", STD 17,		for Network Management of TCP/IP-based internets: MIB-II", STD 17,
	RFC 1213, Hughes LAN Systems, Performance Systems International,		RFC 1213, March 1991.
	March 1991.
	[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.		[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
	Waldbusser, "Protocol Operations for version 2 of the Simple		Conventions for Version 2 of the Simple Network Management Protocol
	Network Management Protocol (SNMPv2)", RFC 1905, January 1996.		(SNMPv2)", RFC 1903, January 1996.
	[8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.		[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
	Waldbusser, "Conformance Statements for version 2 of the Simple		Operations for Version 2 of the Simple Network Management Protocol
	Network Management Protocol (SNMPv2)", RFC 1904, January 1996.		(SNMPv2)", RFC 1905, January 1996.
	[9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network		[8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance
	Management Protocol", RFC 1157, SNMP Research, Performance Systems		Statements for Version 2 of the Simple Network Management Protocol
	International, MIT Laboratory for Computer Science, May 1990.		(SNMPv2)", RFC 1904, January 1996.
	[10] Network Working Group, and McCloghrie K., "SNMPv2 MIB for IP", RFC		[9] McCloghrie K., "Management Information Base for the Internet
	2011, November 1996.		Protocol using SMIv2", RFC 2011, November 1996.
	[11] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[10] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997		Levels", BCP 14, RFC 2119, March 1997.
	[12] Perez, M., Liaw, F., Mankin, A., Hoffman, E., Grossman, D., Malis,		[11] Perez, M., Liaw, F., Mankin, A., Hoffman, E., Grossman, D., Malis,
	A., "ATM Signaling Support for IP over ATM", RFC 1755, February		A., "ATM Signaling Support for IP over ATM", RFC 1755, February
	1995		1995.
	8. Authors' Addresses		[12] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport
			Mappings for Version 2 of the Simple Network Management Protocol
			(SNMPv2)", RFC 1906, January 1996.
			[13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management
			Information Base for Version 2 of the Simple Network Management
			Protocol (SNMPv2)", RFC 1907, January 1996.
			[14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
			"Coexistence between Version 1 and Version 2 of the Internet-
			standard Network Management Framework", RFC 1908, January 1996.
			9. Authors' Addresses
	Maria N. Greene		Maria N. Greene
	Independent Contractor		Xedia Corp.
	E-mail: greene@ultranet.com		119 Russell Dr.
			Littleton, MA 01460
			E-mail: maria@xedia.com
	James Luciani		James Luciani
	Bay Networks, Inc.		Bay Networks, Inc.
	3 Federal St., BL3-04		3 Federal St., BL3-04
	Billerica, MA 01821, USA		Billerica, MA 01821, USA
	Phone: +1-508-439-4734		Phone: +1-508-439-4734
	E-mail: luciani@baynetworks.com		E-mail: luciani@baynetworks.com
	Kenneth D. White		Kenneth D. White
	Dept. G80/Bldg 503		Dept. G80/Bldg 503
	skipping to change at page 49, line 5 ¶		skipping to change at page 52, line 16 ¶
	E-mail: kennethw@vnet.ibm.com		E-mail: kennethw@vnet.ibm.com
	Ted T.I. Kuo		Ted T.I. Kuo
	Bay Networks, Inc.		Bay Networks, Inc.
	4401 Great America Parkway		4401 Great America Parkway
	Santa Clara, CA 95052-8185		Santa Clara, CA 95052-8185
	Phone: +1-408-495-7319		Phone: +1-408-495-7319
	fax: +1-408-495-1905		fax: +1-408-495-1905
	E-mail: ted_kuo@Baynetworks.com		E-mail: ted_kuo@Baynetworks.com
	9. Full Copyright Statement		10. Full Copyright Statement
	Copyright (C) The Internet Society (1997). All Rights Reserved.		Copyright (C) The Internet Society (1998). 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 and		or assist in its implementation may be prepared, copied, published and
	distributed, in whole or in part, without restriction of any kind,		distributed, in whole or in part, without restriction of any kind,
	provided that the above copyright notice and this paragraph are		provided that the above copyright notice and this paragraph 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 developing		Internet organizations, except as needed for the purpose of developing
End of changes. 288 change blocks.
	603 lines changed or deleted		757 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/