As per Relevance of the word endpoint, we have this rfc below:
Network Working Group K.
Request for Comments: 2955 Megisto
Category: Standards Track O.
RAD Data Communications, Ltd
G.
AT&T
October 2000
Definitions of Managed
for Monitoring and Controlling
Frame Relay/ATM PVC Service Interworking
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This memo defines a Management Information Base (MIB) to configure
monitor, and control a service interworking function (IWF)
Permanent Virtual Connections (PVC) between Frame Relay
Asynchronous Transfer Mode (ATM) technologies
Table of
1. The SNMP Management Framework ............................... 2
2. Conventions ................................................. 3
3. Overview .................................................... 3
3.1 Frame Relay/ATM Service Interworking Background ............ 4
3.2 Structure of the MIB ....................................... 4
3.3 Relationship to Other MIBs ................................. 5
3.3.1 Frame Relay Service MIB .................................. 6
3.3.2 Frame Relay DTE MIB ...................................... 6
3.3.3 ATM MIB .................................................. 6
3.3.4 IF MIB ................................................... 7
3.4 Point to Multipoint Considerations ......................... 7
3.5 Theory of Operation ........................................ 7
3.5.1 Creation Process ......................................... 7
3.5.2 Destruction Process ...................................... 10
Rehbehn, et al. Standards Track [Page 1]
RFC 2955 FR to ATM Service Interworking MIB October 2000
3.5.3 Modification Process ..................................... 11
4. Object Definitions .......................................... 11
4.1 The FR/ATM PVC Service IWF Connection Group ................ 13
4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 21
5. Augmentation of ATM MIB VCL Endpoint Entry (atmVclEntry) .... 27
6. Frame Relay/ATM PVC Service Interworking NOTIFICATION ....... 29
7. Conformance Information ..................................... 29
7.1 Compliance Statement For Equipment ......................... 29
7.2 Compliance Statement For Service (CNM Interface) ........... 30
7.3 Units of Conformance ....................................... 32
7.3.1 Basic FR/ATM IWF PVC Connection Group .................... 32
7.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 32
7.3.3 ATM MIB VCL Endpoint Table Augmentation .................. 33
7.3.4 Notification Group ....................................... 33
8. Acknowledgments ............................................. 34
9. References .................................................. 34
10. Security Considerations .................................... 36
11. Authors' Addresses ......................................... 37
12. Intellectual Property Rights ............................... 38
13. Full Copyright Statement ................................... 39
1. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described in
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
Rehbehn, et al. Standards Track [Page 2]
RFC 2955 FR to ATM Service Interworking MIB October 2000
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [16].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
2.
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL,
they appear in this document, are to be interpreted as described
RFC 2119 [23].
3.
This document defines a Management Information Base (MIB)
monitoring and controlling a service interworking function (IWF)
Permanent Virtual Connections (PVC) between Frame Relay
Asynchronous Transfer Mode (ATM) technologies. The agreements
which this MIB is based were reached jointly by the Frame Relay
and the ATM Forum and are documented in the Frame Relay
Document FRF.8 [17].
Rehbehn, et al. Standards Track [Page 3]
RFC 2955 FR to ATM Service Interworking MIB October 2000
3.1. Frame Relay/ATM Service Interworking
Frame relay to ATM interworking is a function that exchanges
Data Units (PDU) between a frame relay service user and an
service user. Two types of interworking functions are specified
frame relay and ATM permanent virtual connection (PVC) service users
network interworking and service interworking
Network interworking provides PDU forwarding between frame
service users inter-connected by an ATM service. Both endpoints
frame relay PVCs. Frame Relay to ATM PVC Network Interworking
defined in [20].
Service interworking provides PDU forwarding so that the ATM
user performs no frame relaying service-specific functions and
frame relay service user performs no ATM service-specific functions
Optionally, the service IWF translates particular higher
protocols to satisfy the requirements of end-systems. Frame Relay
ATM PVC Service Interworking is defined in [17].
This MIB describes management objects used to provision, monitor,
control a Frame Relay/ATM PVC Service IWF
FRF.8 [17] does not address point-to-multipoint applications of
IWF. Implementations MAY provide support for point-to-
capability using this MIB
Consult FRF.8 [17] for more details on the operation of a
Relay/ATM PVC Service IWF
3.2. Structure of the
The Frame Relay/ATM PVC Service IWF managed objects are organized
follows
(1) FR/ATM PVC Service IWF cross-connect table
(2) Connection description table,
(3) Notification
The IWF cross-connect table contains one or more rows for
inter-worked connection. Each inter-worked connection is
identified by the frAtmIwfConnIndex object. In the case of point-to
point, a single row is present. In the case of point-to-multipoint
one row exists for each multipoint destination. Index objects
the ATM port, VPI, VCI, frame relay port, and frame relay
distinguish the constituent rows used in a point-to-multipoint case
Rehbehn, et al. Standards Track [Page 4]
RFC 2955 FR to ATM Service Interworking MIB October 2000
Each inter-worked connection has attributes governing behavior of
IWF. These attributes describe how the IWF should transform a
during the forwarding process and provide rules for
(1) Mapping the ATM CLP bit to frame relay DE
(2) Mapping the ATM congestion notification bit to frame
congestion
(3) Mapping higher protocol encapsulations between ATM and
(4) Performing fragmentation and
(5) Performing ARP translation between ATM and frame
Typically, most connections share the same attributes.
attributes are represented in this MIB by the connection
table. Each row of the connection description table contains
attribute settings common to one or more inter-worked connections
One example would be full mapping and translation. All cross-
table entries that require full mapping and translation services
the frAtmIwfConnectionDescriptor object to the index value for
connection description table row that contains objects set to
that provide full mapping and translation services
A notification object provides cross-connect status change alerts
3.3. Relationship to Other
The Frame Relay/ATM PVC Service IWF MIB describes the cross
connections between frame relay and ATM service users. Each
endpoint is provisioned and managed with a technology-specific MIB
described below
Each technology-specific MIB has a table of PVC endpoints (indexed
ifIndex and logical link address such as the DLCI or VPI/VCI).
the absence of interworking, two endpoints are cross-connected via
technology-specific cross connect table (e.g.,
atmVcCrossConnectTable in the ATM MIB). However, a
between a frame relay endpoint and an ATM endpoint requires a cross
connect in the ATM IWF MIB
The following sections describe the relationship between
technology-specific MIBs and the FR/ATM PVC Service IWF MIB
Rehbehn, et al. Standards Track [Page 5]
RFC 2955 FR to ATM Service Interworking MIB October 2000
3.3.1. Frame Relay Service
Frame relay PVC endpoints are provisioned as rows in the Frame
Services MIB [19] endpoint table
Each frame relay PVC endpoint is described in the frPVCEndptTable.
connection between two frame relay endpoints is described by an
in the frame relay PVC cross-connect table frPVCConnectTable.
frPVCEndptConnectIdentifier object of each endpoint points to
frPVCConnectTable cross-connect table row for the connection
In the case of an inter-worked connection,
frPVCEndptConnectIdentifier object is set to zero. Instead,
frPVCEndptAtmIwfConnIndex object is set to the index of the FR/
IWF cross-connect table row
The frame relay PVC cross-connect table (frPVCConnectTable) does
contain an entry for the FR/ATM inter-worked connection
Note that the frPVCEndptConnectIdentifier
frPVCEndptAtmIwfConnIndex objects are set by the system as a side
effect of cross-connect establishment. Consequently, these
are read-only
3.3.2. Frame Relay DTE
The Frame Relay DTE MIB described in [24] has no relevance to
FR/ATM PVC Service IWF MIB
3.3.3. ATM
ATM PVC endpoints are provisioned as rows in the ATM MIB [21]
connection link table
Each ATM connection endpoint is described in the atmVclTable.
connection between two ATM endpoints is described by an entry in
ATM VCL cross-connect table atmVcCrossConnectTable.
atmVclCrossConnectIdentifier object of each endpoint points to
atmVcCrossConnectTable row for the connection
In the case of an inter-worked connection,
atmVclCrossConnectIdentifier object is set to zero. Instead,
frAtmIwfVclCrossConnectIdentifier object in the frAtmIwfVclEntry
set to the index of the applicable FR/ATM IWF cross-connect
row
Rehbehn, et al. Standards Track [Page 6]
RFC 2955 FR to ATM Service Interworking MIB October 2000
Note that the frAtmIwfVclCrossConnectIdentifier object is defined
in the ATM MIB but in Section 5 of this MIB. Specifically,
object is defined as a column object in a table that AUGMENTs the
MIB VCL table
The ATM VCL cross-connect table (atmVcCrossConnectTable) does
contain an entry for the inter-worked connection
Note that the atmVclCrossConnectIdentifier
frAtmIwfVclCrossConnectIdentifier objects are set by the system as
side-effect of cross-connect establishment. Consequently,
objects are read-only
3.3.4. IF
The ifIndex defined in the IF MIB [22] identifies the specific
relay and ATM endpoint interfaces. The values
and frAtmIwfConnFrPort are used in this MIB as components in
index list for the frAtmIwfConnectionTable rows
3.4. Point to Multipoint
This MIB supports IWF implementations providing point-to-
functionality. All rows of the cross-connect table indexed by
same frAtmIwfConnIndex MUST utilize the
frAtmIwfConnectionDescriptor value
A group of cross-connect table entries indexed by the
frAtmIwfConnIndex value MUST agree on which service the
operation is offered. Two cases are possible
(1) Many frame relay PVCs cross-connected to one ATM PVC,
(2) One frame relay PVC cross-connected to many ATM
3.5. Theory of
3.5.1. Creation
Multiple steps are required to create a frame relay to ATM cross
connection. First, rows must be created in the following tables
(1) The Frame Relay Service MIB
(2) The ATM MIB
(3) The FR/ATM Service IWF MIB
Rehbehn, et al. Standards Track [Page 7]
RFC 2955 FR to ATM Service Interworking MIB October 2000
(4) The FR/ATM Service IWF MIB
Second, the newly created rows are cross-linked
Finally, the administrative and operational status objects are set
'up(1)'.
A step-by-step example is provided to illustrate the
process. In this example, the term "Manager" refers to a
management system that issues SNMP protocol actions to an "Agent".
The agent is integrated with the system that implements the
relay to ATM service IWF. In this example, the following cross
connection is created
+-----------------------------------+
+---------+ | FR/ATM PVC Service IWF |
| Frame | | ------------------------------ | +-----------+
| Relay | +--------> frAtmIwfConnIndex K <--------+ | ATM |
|Endpoint | | | V | | | Endpoint |
| ------- | | | | | | | --------- |
| DLCI X | | | +------------+ | | |VPI.VCI Q.R
| on |<-+ | | | +->| on |
|ifIndex Y| | V | | ifIndex S |
+---------+ |frAtmIwfConnectionDescriptorIndex L| +-----------+
+-----------------------------------+
Step 1 - Create the frame relay PVC
a) Manager requests creation of a new row in the
b) Agent receives management request to create a row
frPVCEndptTable for the frame relay
c) A new row is created in frPVCEndptTable as follows
- frPVCEndptConnectIdentifier initialized to
- frPVCEndptAtmIwfConnIndex initialized to
- remaining row objects initialized as needed for DLCI X
ifIndex
Step 2 - Create the ATM PVC
a) Agent receives management request to create a row in
for the ATM
Rehbehn, et al. Standards Track [Page 8]
RFC 2955 FR to ATM Service Interworking MIB October 2000
b) A new row is created in atmVclTable and frAtmIwfVclTable (
AUGMENT to the atmVclTable) as follows
- atmVclCrossConnectIdentifier initialized to
- frAtmIwfVclCrossConnectIdentifier initialized to
- atmVclConnKind initialized to pvc(1)
- remaining row objects initialized as needed for VPI.VCI Q.R
ifIndex
Step 3 - Create the FR/ATM connection
a) If an existing connection descriptor is appropriate for the
connection, go to Step 4 using the selected connection
index value
b) Manager requests a new connection descriptor index value
reading frAtmIwfConnectionDescriptorIndexNext from the
c) Agent receives GET request
frAtmIwfConnectionDescriptorIndexNext and responds with the
available value
d) Manager requests a new connection descriptor row entry using
value L as the
e) Agent receives SET request to create
frAtmIwfConnectionDescriptorTable row entry causes the system
create a row in the table
Step 4 - Create the FR/ATM cross-
a) Manager requests a new cross-connect index value by
frAtmIwfConnIndexNext from the
b) Agent receives GET request for frAtmIwfConnIndexNext and
with the next available value
c) Manager requests a new cross-connect row entry using the value
as the
d) Agent receives SET request to create the
row entry (note: the frame relay and ATM PVC endpoints MUST
and be specified as part of the index fields for the
'K.S.Q.R.Y.X')
Rehbehn, et al. Standards Track [Page 9]
RFC 2955 FR to ATM Service Interworking MIB October 2000
e) System creates a row in frAtmIwfConnectionTable for the
indices
- frAtmIwfConnIndex of
- frAtmIwfConnAtmPort of
- frAtmIwfConnVpi of
- frAtmIwfConnVci of
- frAtmIwfConnFrPort of
- frAtmIwfConnDlci of
- frAtmIwfConnectionDescriptor of
Step 5 - The system sets the frame relay PVC endpoint and ATM
endpoint to point to the FR/ATM cross-connect row (as a side-
of Step 4).
a) System sets frPVCEndptAtmIwfConnIndex to
b) System sets frAtmIwfVclCrossConnectIdentifier to
Step 6 - Manager signals activation by issuing a SET for
frAtmIwfConnAdminStatus object using the value of 'up(1)'
Step 7 - Agent receives SET request for frAtmIwfConnAdminStatus
executes internal system mechanisms to activate each PVC segment
the IWF cross-connect. The successful activation permits the agent
respond with 'up(1)' when a GET request is received for the
fields
- frAtmIwfConnAtm2
- frAtmIwfConnFr2
- atmVclOperStatus (Note: there is no comparable FRS MIB object
3.5.2. Destruction
Destruction of the frame relay to ATM cross-connection is
by the network management system. The agent's processing of
request stimulates implementation-specific system clean-up actions
Following removal of the row in the cross-connection table,
frAtmIwfVclCrossConnectIdentifier in the frAtmIwfVclTable (AUGMENT
Rehbehn, et al. Standards Track [Page 10]
RFC 2955 FR to ATM Service Interworking MIB October 2000
the ATM MIB endpoint table) and frPVCEndptAtmIwfConnIndex in
Frame Relay Service MIB endpoint table are both re-initialized
zero
A step-by-step example is provided to illustrate the
process
Step 1 - Manager requests destruction of an existing row in
frAtmIwfConnectionTable by setting frAtmIwfConnRowStatus
destroy(6)
Step 2 - Agent receives the SET request and performs implementation
specific system clean-up actions for the cross-connection
Step 3 - System updates the relevant cross connect information
the frame relay PVC endpoint by setting frPVCEndptAtmIwfConnIndex
0
Step 4 - System updates the relevant cross connect information
the ATM PVC endpoint as follows
a) System sets frAtmIwfVclCrossConnectIdentifier to 0
b) System sets atmVclOperStatus to 'down(2)' (Note: there is
comparable FRS MIB object
Following the destruction of the FR/ATM cross-connection entry,
manager MAY set the frPVCConnectRowStatus and/or atmVclRowStatus
destroy(6) the associated endpoint entries
3.5.3. Modification
At the discretion of the agent, a FR/ATM cross-connect may
reconfigured by adding and/or deleting leafs to/from the IWF
as per the FR/ATM IWF cross-connect creation/destruction procedures
Reconfiguration of traffic/service category parameter values
release of the FR/ATM IWF cross-connect before those parameter
may be changed for individual frame relay or ATM endpoint segments
4. Object
FR-ATM-PVC-SERVICE-IWF-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
NOTIFICATION-TYPE
mib-2, Integer32, Counter32 FROM SNMPv2-
Rehbehn, et al. Standards Track [Page 11]
RFC 2955 FR to ATM Service Interworking MIB October 2000
RowStatus, TimeStamp FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP
NOTIFICATION-GROUP FROM SNMPv2-
AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-
atmVclEntry FROM ATM-
InterfaceIndex FROM IF-MIB
frAtmIwfMIB MODULE-
LAST-UPDATED "200009280000Z" -- September 28, 2000
ORGANIZATION "IETF Frame Relay Service MIB Working Group
CONTACT-
"WG Charter
http://www.ietf.org/html.charters/frnetmib-
WG-email
frnetmib@sunroof.eng.sun.
Subscribe
frnetmib-request@sunroof.eng.sun.
Email Archive
ftp://ftp.ietf.org/ietf-mail-archive/
Chair: Andy
Vivace Networks, Inc
Email: Andy.Malis@vivacenetworks.
WG editor: Kenneth
Megisto Systems, Inc
Email: krehbehn@megisto.
Co-author: Orly
RAD Data Communications Ltd
EMail: orly_n@rad.co.
Co-author: George
AT&T
EMail: gvm@att.com
"The MIB module for monitoring and controlling
Frame Relay/ATM PVC Service
Function."
--
-- Revision
--
Rehbehn, et al. Standards Track [Page 12]
RFC 2955 FR to ATM Service Interworking MIB October 2000
REVISION "200009280000Z
"Published as RFC 2955"
::= { mib-2 86 }
--
-- Object
--
frAtmIwfMIBObjects OBJECT
::= { frAtmIwfMIB 1 }
frAtmIwfTraps OBJECT
::= { frAtmIwfMIB 2 }
frAtmIwfTrapsPrefix OBJECT
::= { frAtmIwfTraps 0 }
frAtmIwfConformance OBJECT
::= { frAtmIwfMIB 3 }
frAtmIwfGroups OBJECT
::= { frAtmIwfConformance 1 }
frAtmIwfCompliances OBJECT
::= { frAtmIwfConformance 2 }
--
-- The FR/ATM PVC Service IWF
--
-- The Frame Relay/ATM PVC Service Interworking
-- Connection Table contains all connections
-- the interworking function
--
frAtmIwfConnIndexNext OBJECT-
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-
STATUS
"This object contains an appropriate value to
used for frAtmIwfConnIndex when creating
in the frAtmIwfConnectionTable. The value 0
indicates that no unassigned entries
available. To obtain the
value for a new entry, the manager issues
management protocol retrieval operation to
the current value of this object. After
retrieval, the agent should modify the value
the next unassigned index."
::= { frAtmIwfMIBObjects 1 }
Rehbehn, et al. Standards Track [Page 13]
RFC 2955 FR to ATM Service Interworking MIB October 2000
frAtmIwfConnectionTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table in which each row represents a
Relay/ATM interworking connection."
::= { frAtmIwfMIBObjects 2 }
frAtmIwfConnectionEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The FrAtmIwfConnectionEntry provides an entry
an interworking connection between a frame
PVC and one or more ATM PVCs, or an ATM PVC
one or more frame relay PVCs. A single
relay PVC connected to a single ATM PVC
referred to as a `point-to-point' connection
is represented by a single row in the FR/ATM
Connection Table. The case of a single
relay PVC connected to multiple ATM PVCs (
single ATM PVC connected to multiple frame
PVCs) is referred to as a `point-to-multipoint
connection and is represented by multiple rows
the FR/ATM IWF Connection Table
The object frAtmIwfConnIndex uniquely
each point-to-point or point-to-
connection. The manager obtains
frAtmIwfConnIndex value by reading
frAtmIwfConnIndexNext object
After a frAtmIwfConnIndex is assigned for
connection, the manager creates one or more
in the Cross Connect Table; one for each cross
connection between the frame relay PVC and an
PVC. In the case of `point-to-multipoint
connections, all rows are indexed by the
frAtmIwfConnIndex value and MUST refer to the
frame relay PVC or ATM PVC respectively. An
can be created only when at least one pair
frame relay and ATM PVCs exist
A row can be established by one-step set-
with all required parameter values
frAtmIwfConnRowStatus set to createAndGo(4).
Rehbehn, et al. Standards Track [Page 14]
RFC 2955 FR to ATM Service Interworking MIB October 2000
Agent should perform all error checking as needed
A pair of cross-connected PVCs, as identified by
particular value of the indexes, is released
setting frAtmIwfConnRowStatus to destroy(6).
Agent may release all associated resources.
manager may remove the related PVCs thereafter
Indexes are persistent across reboots of
system."
INDEX { frAtmIwfConnIndex
frAtmIwfConnAtmPort
frAtmIwfConnVpi
frAtmIwfConnVci
frAtmIwfConnFrPort
}
::= { frAtmIwfConnectionTable 1 }
FrAtmIwfConnectionEntry ::=
SEQUENCE {
frAtmIwfConnIndex Integer32,
frAtmIwfConnAtmPort InterfaceIndex
frAtmIwfConnVpi AtmVpIdentifier
frAtmIwfConnVci AtmVcIdentifier
frAtmIwfConnFrPort InterfaceIndex
frAtmIwfConnDlci Integer32,
frAtmIwfConnRowStatus RowStatus
frAtmIwfConnAdminStatus INTEGER
frAtmIwfConnAtm2FrOperStatus INTEGER
frAtmIwfConnAtm2FrLastChange TimeStamp
frAtmIwfConnFr2AtmOperStatus INTEGER
frAtmIwfConnFr2AtmLastChange TimeStamp
frAtmIwfConnectionDescriptor Integer32,
frAtmIwfConnFailedFrameTranslate Counter32,
frAtmIwfConnOverSizedFrames Counter32,
frAtmIwfConnFailedAal5PduTranslate Counter32,
frAtmIwfConnOverSizedSDUs Counter32,
frAtmIwfConnCrcErrors Counter32,
frAtmIwfConnSarTimeOuts Counter32
}
frAtmIwfConnIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS
"A unique value for each point-to-point or point
to-multipoint connection. The manager obtains
frAtmIwfConnIndex value by reading
Rehbehn, et al. Standards Track [Page 15]
RFC 2955 FR to ATM Service Interworking MIB October 2000
frAtmIwfConnIndexNext object. A point-to
multipoint connection will be represented in
frAtmIwfConnectionTable with multiple entries
share the same frAtmIwfConnIndex value."
::= { frAtmIwfConnectionEntry 1 }
frAtmIwfConnAtmPort OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The index in the ifTable that identifies the
port for this interworking connection."
::= { frAtmIwfConnectionEntry 2 }
frAtmIwfConnVpi OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The VPI of the ATM PVC end point for
interworking connection."
::= { frAtmIwfConnectionEntry 3 }
frAtmIwfConnVci OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The VCI of the ATM PVC end point for
connection."
::= { frAtmIwfConnectionEntry 4 }
frAtmIwfConnFrPort OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The index in the ifTable that identifies
frame relay port for this
connection."
::= { frAtmIwfConnectionEntry 5 }
frAtmIwfConnDlci OBJECT-
SYNTAX Integer32 (16..4194303)
MAX-ACCESS not-
STATUS
Rehbehn, et al. Standards Track [Page 16]
RFC 2955 FR to ATM Service Interworking MIB October 2000
"The DLCI that identifies the frame relay PVC
point for this interworking connection."
::= { frAtmIwfConnectionEntry 6 }
frAtmIwfConnRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The table row may be created
'createAndWait(5)' or 'createAndGo(4)'.
To activate a connection entry, a valid
descriptor MUST be established in
frAtmIwfConnectionDescriptor object
This object is set to 'destroy(6)' to delete
table row. Before the table row is destroyed,
OperStatus/AdminStatus of the
endpoints MUST be 'down(2)'. The deactivation
the ATM endpoint MAY occur as a side-effect
deleting the FR/ATM IWF cross-connection
row. Otherwise, 'destroy(6)' operation MUST
(error code 'inconsistentValue')."
::= { frAtmIwfConnectionEntry 7 }
frAtmIwfConnAdminStatus OBJECT-
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-
STATUS
"The desired operational state for this FR/
interworked connection
up(1) = Activate the connection. Before
activation can be completed,
OperStatus/AdminStatus of
corresponding endpoints MUST
'up(1)'. The activation of
corresponding endpoints MAY occur
a side-effect of activating
FR/ATM IWF cross-connection
down(2) = Deactivate the connection.
the deactivation can be completed
the atmVclAdminStatus of
corresponding ATM endpoint MUST
'down(2)'. The deactivation of
Rehbehn, et al. Standards Track [Page 17]
RFC 2955 FR to ATM Service Interworking MIB October 2000
ATM endpoint MAY occur as
side-effect of deactivating
FR/ATM IWF cross-connection."
::= { frAtmIwfConnectionEntry 8 }
frAtmIwfConnAtm2FrOperStatus OBJECT-
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-
STATUS
"The current operational state of
interworking connection in the ATM to
relay direction."
::= { frAtmIwfConnectionEntry 9 }
frAtmIwfConnAtm2FrLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time
interworking connection entered its
operational state in the ATM to FR direction.
the current state was entered prior to the
re-initialization of the local network
subsystem, then this object contains a
value."
::= { frAtmIwfConnectionEntry 10 }
frAtmIwfConnFr2AtmOperStatus OBJECT-
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-
STATUS
"The current operational state of
interworking connection in the frame
to ATM direction."
::= { frAtmIwfConnectionEntry 11 }
frAtmIwfConnFr2AtmLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time
interworking connection entered its
operational state in the FR to ATM direction.
the current state was entered prior to the
Rehbehn, et al. Standards Track [Page 18]
RFC 2955 FR to ATM Service Interworking MIB October 2000
re-initialization of the local network
subsystem, then this object contains a
value."
::= { frAtmIwfConnectionEntry 12 }
frAtmIwfConnectionDescriptor OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The value represents a pointer to the
descriptor in the IWF descriptor table.
attempt to set this value to an inactive or non
existent row in the Connection Descriptor
MUST fail (error code 'inconsistentValue')."
::= { frAtmIwfConnectionEntry 13 }
frAtmIwfConnFailedFrameTranslate OBJECT-
SYNTAX Counter32
UNITS "Frames
MAX-ACCESS read-
STATUS
"This object counts the number of frames
by the IWF because, while operating in
Mode, the IWF is unable to decode the
frame payload header according to the
rules. (i.e., payload header not recognized by
IWF).
Frame relay frames are received in the frame
to ATM direction of the PVC
When operating in Transparent Mode, the IWF
return noSuchInstance."
"FRF.8 [17], Section 5.3.1"
::= { frAtmIwfConnectionEntry 14 }
frAtmIwfConnOverSizedFrames OBJECT-
SYNTAX Counter32
UNITS "Frames
MAX-ACCESS read-
STATUS
"Count of frames discarded by the IWF because
frame is too large to be processed by the AAL
segmentation procedure. Specifically, the
Rehbehn, et al. Standards Track [Page 19]
RFC 2955 FR to ATM Service Interworking MIB October 2000
does not conform to the size specified in
atmVccAal5CpcsTransmitSduSize object
with the atmVclEntry at the ATM endpoint
Frame relay frames are received in the frame
to ATM direction of the PVC."
"ATM MIB [21],
FRF.8 [17], 5.3.1.4"
::= { frAtmIwfConnectionEntry 15 }
frAtmIwfConnFailedAal5PduTranslate OBJECT-
SYNTAX Counter32
UNITS "PDUs
MAX-ACCESS read-
STATUS
"This attribute counts the number of AAL5
discarded by the IWF because, while operating
Translation Mode, the IWF is unable to decode
incoming AAL5 PDU payload header according to
mapping rules. (i.e., payload header
recognized by the IWF).
AAL5 PDUs are received in the ATM to frame
direction of the PVC
When operating in Transparent Mode, the IWF
return noSuchInstance."
"FRF.8 [17], Section 5.3.1"
::= { frAtmIwfConnectionEntry 16 }
frAtmIwfConnOverSizedSDUs OBJECT-
SYNTAX Counter32
UNITS "SDUs
MAX-ACCESS read-
STATUS
"Count of AAL5 SDUs discarded by the IWF
the SDU is too large to be forwarded on the
relay segment of the connection. Specifically
the frame does not conform to the size
in the frLportFragSize object of the FRS MIB [19].
AAL5 PDUs are received in the ATM to frame
direction of the PVC."
"FRS MIB [19],
Rehbehn, et al. Standards Track [Page 20]
RFC 2955 FR to ATM Service Interworking MIB October 2000
FRF.8 [17], 5.3.1.4"
::= { frAtmIwfConnectionEntry 17 }
frAtmIwfConnCrcErrors OBJECT-
SYNTAX Counter32
UNITS "PDUs
MAX-ACCESS read-
STATUS
"The number of AAL5 CPCS PDUs received with CRC-32
errors on this AAL5 VCC at the IWF
AAL5 PDUs are received in the ATM to frame
direction of the PVC."
"ATM MIB [21], atmVclTable
::= { frAtmIwfConnectionEntry 18 }
frAtmIwfConnSarTimeOuts OBJECT-
SYNTAX Counter32
UNITS "PDUs
MAX-ACCESS read-
STATUS
"The number of partially re-assembled AAL5
PDUs which were discarded on this AAL5 VCC at
IWF because they were not fully re-
within the required time period. If the re
assembly timer is not supported, then this
contains a zero value
AAL5 PDUs are received in the ATM to frame
direction of the PVC."
"ATM MIB [21], atmVclTable
::= { frAtmIwfConnectionEntry 19 }
--
-- The FR/ATM PVC Service IWF Connection Descriptor
--
-- The Frame Relay/ATM PVC Service Interworking
-- Connection Descriptor table. A descriptor provides
-- attributes for a type of interworked connection
--
frAtmIwfConnectionDescriptorIndexNext OBJECT-
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-
Rehbehn, et al. Standards Track [Page 21]
RFC 2955 FR to ATM Service Interworking MIB October 2000
STATUS
"This object contains an appropriate value to
used for frAtmIwfConnectionDescriptorIndex
creating entries in
frAtmIwfConnectionDescriptorTable. The value 0
indicates that no unassigned entries
available. To obtain
frAtmIwfConnectionDescriptorIndexNext value for
new entry, the manager issues a
protocol retrieval operation to obtain the
value of this object. After each retrieval,
agent should modify the value to the
unassigned index."
::= { frAtmIwfMIBObjects 3 }
frAtmIwfConnectionDescriptorTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table in which each row represents a
for one type of Frame Relay/ATM
connection. A descriptor may be assigned to
or more FR/ATM PVC service IWF connections."
::= { frAtmIwfMIBObjects 4 }
frAtmIwfConnectionDescriptorEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry for a descriptor in an
connection between a frame relay PVC and an
PVC."
INDEX { frAtmIwfConnectionDescriptorIndex }
::= { frAtmIwfConnectionDescriptorTable 1 }
FrAtmIwfConnectionDescriptorEntry ::=
SEQUENCE {
frAtmIwfConnectionDescriptorIndex Integer32,
frAtmIwfConnDescriptorRowStatus RowStatus
frAtmIwfConnDeToClpMappingMode INTEGER
frAtmIwfConnClpToDeMappingMode INTEGER
frAtmIwfConnCongestionMappingMode INTEGER
frAtmIwfConnEncapsulationMappingMode INTEGER
frAtmIwfConnEncapsulationMappings BITS
frAtmIwfConnFragAndReassEnabled INTEGER
Rehbehn, et al. Standards Track [Page 22]
RFC 2955 FR to ATM Service Interworking MIB October 2000
frAtmIwfConnArpTranslationEnabled
}
frAtmIwfConnectionDescriptorIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS
"A unique value to identify a descriptor in
table "
::= { frAtmIwfConnectionDescriptorEntry 1 }
frAtmIwfConnDescriptorRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this table row. This object
used to create or delete an entry in
descriptor table
Creation of the row requires a row index (
frAtmIwfConnectionDescriptorIndexNext). If
explicitly set or in existence, all other
of the row will be created and initialized to
default value. During creation, this object
be set to 'createAndGo(4)' or 'createAndWait(5)'.
The object MUST contain the value 'active(1)'
before any connection table entry references
row
To destroy a row in this table, this object is
to the 'destroy(6)' action. Row destruction
fail (error code 'inconsistentValue') if
connection references the row."
::= { frAtmIwfConnectionDescriptorEntry 2 }
frAtmIwfConnDeToClpMappingMode OBJECT-
SYNTAX INTEGER {
mode1(1),
mode2Const0(2),
mode2Const1(3)
}
MAX-ACCESS read-
STATUS
"This object describes which mode of
is in use for loss priority mapping in the
Rehbehn, et al. Standards Track [Page 23]
RFC 2955 FR to ATM Service Interworking MIB October 2000
relay to ATM direction
mode1(1) = the DE field in the Q.922
frame shall be mapped to the
CLP field of every
generated by the
process of the AAL5
containing the information
that frame
mode2Contst0(2) = the ATM CLP field of every
generated by the
process of the AAL5
containing the information
that frame shall be set
constant 0.
mode2Contst1(3) = the ATM CLP field of every
generated by the
process of the AAL5
containing the information
that frame shall be set
constant 1."
"FRF.8 [17], Section 4.2.1"
DEFVAL { mode1 }
::= { frAtmIwfConnectionDescriptorEntry 3 }
frAtmIwfConnClpToDeMappingMode OBJECT-
SYNTAX INTEGER {
mode1(1),
mode2Const0(2),
mode2Const1(3)
}
MAX-ACCESS read-
STATUS
"This object describes which mode of
is in use for loss priority mapping in the ATM
frame relay direction
mode1(1) = if one or more cells in a
has its CLP field set, the
field of the Q.922 core
should be set
mode2Const0(2) = the DE field of the Q.922
frame should be set to
Rehbehn, et al. Standards Track [Page 24]
RFC 2955 FR to ATM Service Interworking MIB October 2000
constant 0.
mode2Const1(3) = the DE field of the Q.922
frame should be set to
constant 1."
"FRF.8 [17], Section 4.2.2"
DEFVAL { mode1 }
::= { frAtmIwfConnectionDescriptorEntry 4 }
frAtmIwfConnCongestionMappingMode OBJECT-
SYNTAX INTEGER {
mode1(1),
mode2(2)
}
MAX-ACCESS read-
STATUS
"This object describes which mode of
is in use for forward congestion
mapping in the frame relay to ATM direction
mode1(1) = The FECN field in the Q.922 core
shall be mapped to the ATM EFCI
of every cell generated by
segmentation process of the AAL5
containing the information of
frame
mode2(2) = The FECN field in the Q.922 core
shall not be mapped to the ATM
field of cells generated by
segmentation process of the AAL5
containing the information of
frame. The EFCI field is always set
'congestion not experienced'.
In both of the modes above, if there is
in the forward direction in the ATM layer
the IWF, then the IWF can set the EFCI field
'congestion experienced'."
"FRF.8 [17], Section 4.3.1.1"
DEFVAL { mode1 }
::= { frAtmIwfConnectionDescriptorEntry 5 }
frAtmIwfConnEncapsulationMappingMode OBJECT-
SYNTAX INTEGER {
Rehbehn, et al. Standards Track [Page 25]
RFC 2955 FR to ATM Service Interworking MIB October 2000
transparentMode(1),
translationMode(2),
translationModeAll(3)
}
MAX-ACCESS read-
STATUS
"This object indicates whether the mapping
upper layer protocol encapsulation is enabled
this interworking connection
transparentMode(1) = Forward the
unaltered
translationMode(2) = Perform mapping between
two encapsulations due to
incompatibilities of the
methods. Mapping is
for a subset of the
encapsulations as itemized
ings
translationModeAll(3) = Perform mapping
the two encapsulations due
the incompatibilities of
two methods.
encapsulations
translated."
"FRF.8 [17], Section 5.3"
DEFVAL { transparentMode }
::= { frAtmIwfConnectionDescriptorEntry 6 }
frAtmIwfConnEncapsulationMappings OBJECT-
SYNTAX BITS {
none (0),
bridgedPdus(1),
bridged802dot6(2),
bPdus(3),
routedIp(4),
routedOsi(5),
otherRouted(6),
x25Iso8202(7),
q933q2931(8) }
MAX-ACCESS read-
STATUS
Rehbehn, et al. Standards Track [Page 26]
RFC 2955 FR to ATM Service Interworking MIB October 2000
"If upper layer protocol encapsulation mapping
enabled on this interworking connection, then
attribute enumerates which of the
mappings are supported
none(0) = Transparent mode
bridgedPdus(1) = PID: 0x00-01,-07,-02 or -08
bridged802dot6(2) = PID: 0x00-0
bPdus(3) = PID: 0x00-0E or -0
routedIp(4) = NLPID:
routedOsi(5) = NLPID: Ox81, 0x82 or 0x83
otherRouted(6) = Other routed
x25Iso8202(7) = X25
q933q2931(8) = Q.933 and Q.2931"
"FRF.8 [17], Section 5.3.1"
DEFVAL { { none } }
::= { frAtmIwfConnectionDescriptorEntry 7 }
frAtmIwfConnFragAndReassEnabled OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2)}
MAX-ACCESS read-
STATUS
"The attribute indicates whether fragmentation
reassembly is enabled for this connection."
"FRF.8 [17], Section 5.3.1.4"
DEFVAL { disabled }
::= { frAtmIwfConnectionDescriptorEntry 8 }
frAtmIwfConnArpTranslationEnabled OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2)}
MAX-ACCESS read-
STATUS
"The attribute indicates whether ARP
is enabled for this connection."
"FRF.8 [17], Section 5.4"
DEFVAL { disabled }
::= { frAtmIwfConnectionDescriptorEntry 9 }
--
-- Augmentation of ATM MIB VCL Endpoint Table (atmVclTable
--
frAtmIwfVclTable OBJECT-
SYNTAX SEQUENCE OF
Rehbehn, et al. Standards Track [Page 27]
RFC 2955 FR to ATM Service Interworking MIB October 2000
MAX-ACCESS not-
STATUS
"The FR/ATM IWF VCL Table augments the ATM MIB
Endpoint table."
::= { frAtmIwfMIBObjects 5 }
frAtmIwfVclEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Entries in this table are created only by
agent. One entry exists for each ATM VCL
by the agent."
AUGMENTS { atmVclEntry }
::= { frAtmIwfVclTable 1 }
FrAtmIwfVclEntry ::= SEQUENCE {
frAtmIwfVclCrossConnectIdentifier Integer32
}
frAtmIwfVclCrossConnectIdentifier OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object contains the index value of
FR/ATM cross-connect table entry used to link
ATM VCL with a frame relay PVC
Each row of the atmVclTable that is not cross
connected with a frame relay PVC MUST return
value zero when this object is read
In the case of (frame relay) point to (ATM
multipoint, multiple ATM VCLs will have the
value of this object, and all their cross
connections are identified by entries that
indexed by the same value
frAtmIwfVclCrossConnectIdentifier in
frAtmIwfConnectionTable of this MIB module
The value of this object is initialized by
agent after the associated entries in
frAtmIwfConnectionTable have been created."
::= { frAtmIwfVclEntry 1 }
Rehbehn, et al. Standards Track [Page 28]
RFC 2955 FR to ATM Service Interworking MIB October 2000
--
-- Frame Relay/ATM PVC Service Interworking
--
frAtmIwfConnStatusChange NOTIFICATION-
OBJECTS { frAtmIwfConnAdminStatus
frAtmIwfConnAtm2FrOperStatus
frAtmIwfConnFr2
}
STATUS
"An indication that the status of
interworking connection has changed."
::= { frAtmIwfTrapsPrefix 1 }
--
-- Conformance
--
--
-- Compliance Statement For
--
frAtmIwfEquipmentCompliance MODULE-
STATUS
"The compliance statement for equipment
implements the FR/ATM Interworking MIB."
MODULE -- this
MANDATORY-GROUPS { frAtmIwfBasicGroup
frAtmIwfConnectionDescriptorGroup
frAtmIwfAtmVclTableAugmentGroup
frAtmIwfNotificationsGroup }
OBJECT
SYNTAX INTEGER { mode1(1) }
"Only support for Mode 1 is REQUIRED."
OBJECT
SYNTAX INTEGER { mode1(1) }
"Only support for Mode 1 is REQUIRED."
OBJECT
SYNTAX INTEGER { mode1(1) }
Rehbehn, et al. Standards Track [Page 29]
RFC 2955 FR to ATM Service Interworking MIB October 2000
"Only support for Mode 1 is REQUIRED."
OBJECT
SYNTAX INTEGER { transparentMode(1) }
"Support for Translation Mode is OPTIONAL."
OBJECT
SYNTAX BITS { none(0) }
"The IWF may provide one, some or none of
encapsulation translations defined in
5.3.1 of FRF.8 [17]."
OBJECT
SYNTAX INTEGER { disabled(2) }
"Only support for Mode 1 is REQUIRED."
OBJECT
SYNTAX INTEGER { disabled(2) }
"Support for ARP Translation is NOT REQUIRED."
::= { frAtmIwfCompliances 1 }
--
-- Compliance Statement For Service (CNM Interface
--
frAtmIwfServiceCompliance MODULE-
STATUS
"The compliance statement for a CNM interface
implements the FR/ATM Interworking MIB."
MODULE -- this
MANDATORY-GROUPS { frAtmIwfBasicGroup
frAtmIwfConnectionDescriptorGroup
frAtmIwfAtmVclTableAugmentGroup
frAtmIwfNotificationsGroup }
--
-- Exceptions for each object type implemented for
-- CNM view of the FR/ATM Interworking
--
OBJECT
MIN-ACCESS read-
Rehbehn, et al. Standards Track [Page 30]
RFC 2955 FR to ATM Service Interworking MIB October 2000
"Write access is not REQUIRED."
OBJECT
SYNTAX INTEGER { mode1(1) }
MIN-ACCESS read-
"Support for Mode 1 is REQUIRED. Other modes
OPTIONAL. Write access is NOT REQUIRED."
OBJECT
SYNTAX INTEGER { mode1(1) }
MIN-ACCESS read-
"Support for Mode 1 is REQUIRED. Other modes
OPTIONAL. Write access is NOT REQUIRED."
OBJECT
SYNTAX INTEGER { mode1(1) }
MIN-ACCESS read-
"Support for Mode 1 is REQUIRED. Other modes
OPTIONAL. Write access is NOT REQUIRED."
OBJECT
SYNTAX INTEGER { transparentMode(1) }
MIN-ACCESS read-
"Support for Transparent Mode is REQUIRED
Translation Mode is OPTIONAL. Write access is
required."
OBJECT
SYNTAX BITS { none(0) }
MIN-ACCESS read-
"The IWF may provide one, some or none of
encapsulation translations defined in
5.3.1 of FRF.8 [17]. Write access is
required."
OBJECT
SYNTAX INTEGER { disabled(2) }
MIN-ACCESS read-
"Support for Fragmentation and Reassembly is
REQUIRED. Write access is not required."
Rehbehn, et al. Standards Track [Page 31]
RFC 2955 FR to ATM Service Interworking MIB October 2000
OBJECT
SYNTAX INTEGER { disabled(2) }
MIN-ACCESS read-
"Support for ARP Translation is not required
Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
::= { frAtmIwfCompliances 2 }
--
-- Units of
--
--
-- Basic FR/ATM IWF PVC Connection
--
frAtmIwfBasicGroup OBJECT-
OBJECTS { frAtmIwfConnIndexNext
frAtmIwfConnAdminStatus
frAtmIwfConnAtm2FrOperStatus
frAtmIwfConnAtm2FrLastChange
frAtmIwfConnFr2AtmOperStatus
frAtmIwfConnFr2AtmLastChange
frAtmIwfConnectionDescriptor
frAtmIwfConnFailedFrameTranslate
frAtmIwfConnOverSizedFrames
frAtmIwfConnFailedAal5PduTranslate
frAtmIwfConnOverSizedSDUs
frAtmIwfConnCrcErrors
frAtmIwfConnSarTimeOuts
frAtmIwfConnRowStatus }
STATUS
"The collection of basic objects for
and control of FR/ATM interworking connections."
::= { frAtmIwfGroups 1 }
--
-- FR/ATM IWF PVC Connection Descriptor
--
frAtmIwfConnectionDescriptorGroup OBJECT-
OBJECTS {
Rehbehn, et al. Standards Track [Page 32]
RFC 2955 FR to ATM Service Interworking MIB October 2000
frAtmIwfConnectionDescriptorIndexNext
frAtmIwfConnDeToClpMappingMode
frAtmIwfConnClpToDeMappingMode
frAtmIwfConnCongestionMappingMode
frAtmIwfConnEncapsulationMappingMode
frAtmIwfConnEncapsulationMappings
frAtmIwfConnFragAndReassEnabled
frAtmIwfConnArpTranslationEnabled
}
STATUS
"The collection of basic objects for
of FR/ATM interworking connection descriptors."
::= { frAtmIwfGroups 2 }
--
-- ATM MIB VCL Endpoint Table Augmentation
--
frAtmIwfAtmVclTableAugmentGroup OBJECT-
OBJECTS {
}
STATUS
"The ATM MIB VCL Endpoint Table AUGMENT
contained in the FR/ATM PVC Service
MIB."
::= { frAtmIwfGroups 3 }
--
-- Notification
--
frAtmIwfNotificationsGroup NOTIFICATION-
NOTIFICATIONS { frAtmIwfConnStatusChange }
STATUS
"The notification for FR/ATM interworking
change."
::= { frAtmIwfGroups 4 }
Rehbehn, et al. Standards Track [Page 33]
RFC 2955 FR to ATM Service Interworking MIB October 2000
8.
This document was produced by the Frame Relay Service MIB
Group
The Editors thank Bert Wijnen, Kaj Tesink, Keith McCloghrie,
David Perkins for providing many helpful comments and suggestions
9.
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", STD 16,
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Conformance Statements for SMIv2",
58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Introduction to Community-based SNMPv2", RFC 1901,
1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Mappings for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1906, January 1996.
Rehbehn, et al. Standards Track [Page 34]
RFC 2955 FR to ATM Service Interworking MIB October 2000
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "
Processing and Dispatching for the Simple Network
Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM
for version 3 of the Simple Network Management
(SNMPv3)", RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
2573, April 1999.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management
(SNMP)", RFC 2575, April 1999.
[16] Case, J., Mundy, R., Partain, D. and B. Stewart, "
to Version 3 of the Internet-standard Network
Framework", RFC 2570, April 1999.
[17] Frame Relay/ATM PVC Service Interworking
Agreement, Frame Relay Forum, Document Number FRF.8.1, March
2000.
[18] Noto, M., Spiegel, E. and K. Tesink, "Definitions of
Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514,
February 1999.
[19] Rehbehn, K. and D. Fowler, "Definitions of Managed Objects
Frame Relay Service", RFC 2954, October 2000.
[20] Frame Relay/ATM PVC Network Interworking
Agreement, Frame Relay Forum, Document Number FRF.5,
20, 1994.
[21] Tesink, K., "Definitions of Managed Objects for ATM Management",
RFC 2515, February 1999.
[22] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
RFC 2863, June 2000.
[23] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997.
Rehbehn, et al. Standards Track [Page 35]
RFC 2955 FR to ATM Service Interworking MIB October 2000
[24] Brown, C. and F. Baker, "Management Information Base for
Relay DTEs Using SMIv2", RFC 2115, September 1997.
10. Security
There are a number of management objects defined in this MIB
have a MAX-ACCESS clause of read-write and/or read-create.
objects may be considered sensitive or vulnerable in some
environments. The support for SET operations in a non-
environment without proper protection can have a negative effect
network operations
No managed objects in this MIB contain sensitive information
SNMPv1 by itself is not a secure environment. Even if the
itself is secure (for example by using IPSec), even then, there is
control as to who on the secure network is allowed to access
GET/SET (read/change/create/delete) the objects in this MIB
It is recommended that the implementers consider the
features as provided by the SNMPv3 framework. Specifically, the
of the User-based Security Model RFC 2574 [12] and the View-
Access Control Model RFC 2575 [15] is recommended
It is then a customer/user responsibility to ensure that the
entity giving access to an instance of this MIB, is
configured to give access to the objects only to those
(users) that have legitimate rights to indeed GET or
(change/create/delete) them
Rehbehn, et al. Standards Track [Page 36]
RFC 2955 FR to ATM Service Interworking MIB October 2000
11. Authors'
Kenneth
Megisto Systems, Inc
20251 Century
Germantown, MD, USA 20874
Phone: +1 (301) 515-3672
EMail: krehbehn@megisto.
Orly
RAD Data Communications, Ltd
12 Hanechoshet St
Tel Aviv 69710
Phone: +972 (3) 6459588
EMail: orly_n@rad.co.
George
AT&T Labs, Room 1G-325
101 Crawfords Corner
Holmdel, NJ USA 07733
Phone: +1 908 949 7671
EMail: gvm@att.
Rehbehn, et al. Standards Track [Page 37]
RFC 2955 FR to ATM Service Interworking MIB October 2000
12. Intellectual Property
The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made 