draft-ietf-tn3270e-rt-mib-06.txt   draft-ietf-tn3270e-rt-mib-07.txt 
TN3270E Working Group Kenneth White TN3270E Working Group Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-06.txt> IBM Corp. INTERNET DRAFT: <draft-ietf-tn3270e-rt-mib-07.txt> IBM Corp.
Expiration Date: December, 1998 Robert Moore Expiration Date: January, 1999 Robert Moore
IBM Corp. IBM Corp.
Definitions of Protocol and Managed Objects for Definitions of Protocol and Managed Objects for
TN3270E Response Time Collection Using SMIv2 TN3270E Response Time Collection Using SMIv2
(TN3270E-RT-MIB) (TN3270E-RT-MIB)
<draft-ietf-tn3270e-rt-mib-06.txt> <draft-ietf-tn3270e-rt-mib-07.txt>
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, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other Internet Drafts may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract Abstract
This memo defines the protocol and the Management Information Base (MIB) This memo defines the protocol and the Management Information Base (MIB)
for performing response time data collection on TN3270 and TN3270E for performing response time data collection on TN3270 and TN3270E
sessions by a TN3270E server. The response time data collected by a sessions by a TN3270E server. The response time data collected by a
TN3270E server is structured to support both validation of service level TN3270E server is structured to support both validation of service level
agreements and performance monitoring of TN3270 and TN3270E Sessions. agreements and performance monitoring of TN3270 and TN3270E Sessions.
This MIB has as a prerequisite the TN3270E-MIB, reference [16]. This MIB has as a prerequisite the TN3270E-MIB, reference [20].
TN3270E, defined by RFC 2355 [15], refers to the enhancements made to TN3270E, defined by RFC 2355 [19], refers to the enhancements made to
the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC
1041 [14], RFC 854 [12], and RFC 860 [13] for a sample of what is meant 1041 [18], RFC 854 [16], and RFC 860 [17] for a sample of what is meant
by TN3270 practices. by TN3270 practices.
The specification of this MIB uses the Structure of Management
Information (SMI) for Version 2 of the Simple Network Management
Protocol (refer to RFC1902 [3]).
Table of Contents Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3
3.0 Response Time Collection Methodology . . . . . . . . . . . . . 3 3.0 Response Time Collection Methodology . . . . . . . . . . . . . 3
3.1 General Response Time Collection . . . . . . . . . . . . . . . 3 3.1 General Response Time Collection . . . . . . . . . . . . . . . 3
3.2 TN3270E Server Response Time Collection . . . . . . . . . . . 5 3.2 TN3270E Server Response Time Collection . . . . . . . . . . . 5
3.3 Correlating TN3270E Server and Host Response Times . . . . . . 9 3.3 Correlating TN3270E Server and Host Response Times . . . . . . 9
skipping to change at page 2, line 40 skipping to change at page 2, line 38
6.0 Security Considerations . . . . . . . . . . . . . . . . . . . 38 6.0 Security Considerations . . . . . . . . . . . . . . . . . . . 38
7.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 39 7.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 39
8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39 8.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39
9.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 9.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 41 10.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 41
11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 41 11.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 42
1.0 Introduction 1.0 Introduction
This document is a product of the TN3270E Working Group. It defines a This document is a product of the TN3270E Working Group. It defines a
protocol and a MIB module to enable a TN3270E server to collect and keep protocol and a MIB module to enable a TN3270E server to collect and keep
track of response time data for both TN3270 and TN3270E clients. Basis track of response time data for both TN3270 and TN3270E clients. Basis
for implementing this MIB: for implementing this MIB:
o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using o TN3270E-MIB, Base Definitions of Managed Objects for TN3270E Using
SMIv2 [16] SMIv2 [20]
o TN3270E RFCs o TN3270E RFCs
o Telnet Timing Mark Option RFC [13]. o Telnet Timing Mark Option RFC [17].
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 [19]. document are to be interpreted as described in RFC 2119, reference [23].
2.0 The SNMP Network Management Framework 2.0 The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of six major The SNMP Management Framework presently consists of five major
components. They are: components:
o the overall architecture, described in RFC 2271 [7].
o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects o An overall architecture, described in RFC 2271 [1].
for the Internet suite of protocols.
o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8] o Mechanisms for describing and naming objects and events for the
-- the protocol for accessing managed information. purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called
SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].
o the user-based security model defined in RFC 2274 [10]. o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The
third version of the message protocol is called SNMPv3 and described
in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o the view-based access control model defined in RFC 2275 [11]. o Protocol operations for accessing management information. The first
set of protocol operations and associated PDU formats is described
in RFC 1157 [8]. A second set of protocol operations and associated
PDU formats is described in RFC 1905 [13].
Textual conventions are defined in RFC 1903 [4], and conformance o A set of fundamental applications described in RFC 2273 [14] and the
statements are defined in RFC 1904 [5]. Common applications are defined view-based access control mechanism described in RFC 2275 [15].
in RFC 2273 [9].
The Framework permits new objects to be defined for the purpose of Managed objects are accessed via a virtual information store, termed the
experimentation and evaluation. Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate conforming to the SMIv1 can be produced through the appropriate
translation. translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3.0 Response Time Collection Methodology 3.0 Response Time Collection Methodology
This section explains the methodology and approach used by the MIB This section explains the methodology and approach used by the MIB
defined by this memo for response time data collection by a TN3270E defined by this memo for response time data collection by a TN3270E
server. server.
3.1 General Response Time Collection 3.1 General Response Time Collection
Two primary methods exist for measuring response times in SNA networks: Two primary methods exist for measuring response times in SNA networks:
skipping to change at page 5, line 37 skipping to change at page 5, line 45
A TN3270E server connects a Telnet client performing 3270 emulation to a A TN3270E server connects a Telnet client performing 3270 emulation to a
target SNA host over both a client-side network (client to TN3270E target SNA host over both a client-side network (client to TN3270E
server) and an SNA Network (TN3270E server to target SNA host). The server) and an SNA Network (TN3270E server to target SNA host). The
client-side network is typically TCP/IP, but it need not be. For ease client-side network is typically TCP/IP, but it need not be. For ease
of exposition this document uses the term "IP network" to refer to the of exposition this document uses the term "IP network" to refer to the
client-side network, since IP is by far the most common protocol for client-side network, since IP is by far the most common protocol for
these networks. these networks.
A TN3270E server can use SNA definite responses and the TN3270 A TN3270E server can use SNA definite responses and the TN3270
Enhancement (RFC 2355 [15]) RESPONSES function to calculate response Enhancement (RFC 2355 [19]) RESPONSES function to calculate response
times for a transaction, by timestamping when a client request arrives times for a transaction, by timestamping when a client request arrives
at the server, when the reply arrives from the target host, and when the at the server, when the reply arrives from the target host, and when the
response acknowledging this reply arrives from the client. response acknowledging this reply arrives from the client.
Section 3.4, Timestamp Calculation, provides specifics on when in the Section 3.4, Timestamp Calculation, provides specifics on when in the
sequence of flows between a TN3270E client and its target SNA host a sequence of flows between a TN3270E client and its target SNA host a
TN3270E server takes the required timestamps. In addition, it provides TN3270E server takes the required timestamps. In addition, it provides
information on how a TN3270 TIMING-MARK request/response flow can be information on how a TN3270 TIMING-MARK request/response flow can be
used instead of DR for approximating IP network transit times. used instead of DR for approximating IP network transit times.
skipping to change at page 22, line 39 skipping to change at page 22, line 39
TN3270E-RT-MIB DEFINITIONS ::= BEGIN TN3270E-RT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Gauge32 Counter32, Unsigned32, Gauge32
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, DateAndTime, TimeStamp, TestAndIncr RowStatus, DateAndTime, TimeStamp, TestAndIncr
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
Tn3270eTAddress, tn3270eSrvrConfIndex, tn3270eSrvrConfIndex, tn3270eClientGroupName,
tn3270eClientGroupName, tn3270eResMapElementType tn3270eResMapElementType
FROM TN3270E-MIB FROM TN3270E-MIB
IANATn3270eAddrType IANATn3270eAddrType, IANATn3270eAddress
FROM IANATn3270eTC-MIB FROM IANATn3270eTC-MIB
snanauMIB snanauMIB
FROM SNA-NAU-MIB; FROM SNA-NAU-MIB;
tn3270eRtMIB MODULE-IDENTITY tn3270eRtMIB MODULE-IDENTITY
LAST-UPDATED "9806050000Z" -- June 5, 1998 LAST-UPDATED "9807270000Z" -- July 27, 1998
ORGANIZATION "TN3270E Working Group" ORGANIZATION "TN3270E Working Group"
CONTACT-INFO CONTACT-INFO
"Kenneth White (kennethw@vnet.ibm.com) "Kenneth White (kennethw@vnet.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114 IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195 P.O. Box 12195
3039 Cornwallis 3039 Cornwallis
RTP, NC 27709-2195 RTP, NC 27709-2195
Robert Moore (remoore@us.ibm.com) Robert Moore (remoore@us.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114 IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195 P.O. Box 12195
3039 Cornwallis 3039 Cornwallis
RTP, NC 27709-2195 RTP, NC 27709-2195
(919) 254-4436" (919) 254-4436"
DESCRIPTION DESCRIPTION
"This module defines a portion of the management "This module defines a portion of the management
information base (MIB) that enables monitoring of information base (MIB) that enables monitoring of
TN3270 and TN3270E clients' response times by a TN3270 and TN3270E clients' response times by a
TN3270E server." TN3270E server."
REVISION "9807270000Z" -- July 27, 1998
DESCRIPTION
"RFC nnnn (Proposed Standard)" -- RFC Editor to fill in
::= { snanauMIB 9 } ::= { snanauMIB 9 }
-- snanauMIB ::= { mib-2 34 } -- snanauMIB ::= { mib-2 34 }
-- Top level structure of the MIB -- Top level structure of the MIB
tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 } tn3270eRtNotifications OBJECT IDENTIFIER ::= { tn3270eRtMIB 0 }
tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 } tn3270eRtObjects OBJECT IDENTIFIER ::= { tn3270eRtMIB 1 }
tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 } tn3270eRtConformance OBJECT IDENTIFIER ::= { tn3270eRtMIB 3 }
-- MIB Objects -- MIB Objects
skipping to change at page 25, line 55 skipping to change at page 25, line 58
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold for generating a tn3270eRtExceeded "The threshold for generating a tn3270eRtExceeded
notification, signalling that a monitored total response notification, signalling that a monitored total response
time has exceeded the specified limit. A value of zero time has exceeded the specified limit. A value of zero
for this object suppresses generation of this notification. for this object suppresses generation of this notification.
The value of this object is used only if the corresponding The value of this object is used only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected." tn3270eRtCollCtlType has average(3) and traps(5) selected.
A tn3270eRtExceeded notification is not generated again for a
tn3270eRtDataEntry until an average response time falling below
the low threshold tn3270eRtCollCtlThreshLow specified for the
client group has occurred for the entry."
DEFVAL { 0 } -- suppress notifications DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 5 } ::= { tn3270eRtCollCtlEntry 5 }
tn3270eRtCollCtlThreshLow OBJECT-TYPE tn3270eRtCollCtlThreshLow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold for generating a tn3270eRtOkay notification, "The threshold for generating a tn3270eRtOkay notification,
signalling that a monitored total response time has fallen signalling that a monitored total response time has fallen
below the specified limit. A value of zero for this object below the specified limit. A value of zero for this object
suppresses generation of this notification. The value of suppresses generation of this notification. The value of
skipping to change at page 26, line 15 skipping to change at page 26, line 24
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold for generating a tn3270eRtOkay notification, "The threshold for generating a tn3270eRtOkay notification,
signalling that a monitored total response time has fallen signalling that a monitored total response time has fallen
below the specified limit. A value of zero for this object below the specified limit. A value of zero for this object
suppresses generation of this notification. The value of suppresses generation of this notification. The value of
this object is used only if the corresponding this object is used only if the corresponding
tn3270eRtCollCtlType has average(3) and traps(5) selected." tn3270eRtCollCtlType has average(3) and traps(5) selected.
A tn3270eRtOkay notification is not generated again for a
tn3270eRtDataEntry until an average response time
exceeding the high threshold tn3270eRtCollCtlThreshHigh
specified for the client group has occurred for the entry."
DEFVAL { 0 } -- suppress notifications DEFVAL { 0 } -- suppress notifications
::= { tn3270eRtCollCtlEntry 6 } ::= { tn3270eRtCollCtlEntry 6 }
tn3270eRtCollCtlIdleCount OBJECT-TYPE tn3270eRtCollCtlIdleCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "transactions" UNITS "transactions"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is used to determine whether a "The value of this object is used to determine whether a
skipping to change at page 28, line 52 skipping to change at page 29, line 12
INDEX { INDEX {
tn3270eSrvrConfIndex, -- Server's local index tn3270eSrvrConfIndex, -- Server's local index
tn3270eClientGroupName, -- Collection target tn3270eClientGroupName, -- Collection target
tn3270eRtDataClientAddrType, tn3270eRtDataClientAddrType,
tn3270eRtDataClientAddress, tn3270eRtDataClientAddress,
tn3270eRtDataClientPort } tn3270eRtDataClientPort }
::= { tn3270eRtDataTable 1 } ::= { tn3270eRtDataTable 1 }
Tn3270eRtDataEntry ::= SEQUENCE { Tn3270eRtDataEntry ::= SEQUENCE {
tn3270eRtDataClientAddrType IANATn3270eAddrType, tn3270eRtDataClientAddrType IANATn3270eAddrType,
tn3270eRtDataClientAddress Tn3270eTAddress, tn3270eRtDataClientAddress IANATn3270eAddress,
tn3270eRtDataClientPort Unsigned32, tn3270eRtDataClientPort Unsigned32,
tn3270eRtDataAvgRt Gauge32, tn3270eRtDataAvgRt Gauge32,
tn3270eRtDataAvgIpRt Gauge32, tn3270eRtDataAvgIpRt Gauge32,
tn3270eRtDataAvgCountTrans Gauge32, tn3270eRtDataAvgCountTrans Gauge32,
tn3270eRtDataIntTimeStamp DateAndTime, tn3270eRtDataIntTimeStamp DateAndTime,
tn3270eRtDataTotalRts Counter32, tn3270eRtDataTotalRts Counter32,
tn3270eRtDataTotalIpRts Counter32, tn3270eRtDataTotalIpRts Counter32,
tn3270eRtDataCountTrans Counter32, tn3270eRtDataCountTrans Counter32,
tn3270eRtDataCountDrs Counter32, tn3270eRtDataCountDrs Counter32,
tn3270eRtDataElapsRndTrpSq Unsigned32, tn3270eRtDataElapsRndTrpSq Unsigned32,
skipping to change at page 29, line 31 skipping to change at page 29, line 45
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of address represented by the value "Indicates the type of address represented by the value
of tn3270eRtDataClientAddress. The value unknown(0) is of tn3270eRtDataClientAddress. The value unknown(0) is
used if aggregate data is being collected for the client used if aggregate data is being collected for the client
group." group."
::= { tn3270eRtDataEntry 1 } ::= { tn3270eRtDataEntry 1 }
tn3270eRtDataClientAddress OBJECT-TYPE tn3270eRtDataClientAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX IANATn3270eAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the IP address of the TN3270 client being "Contains the IP address of the TN3270 client being
monitored. A zero-length octet string is used if monitored. A zero-length octet string is used if
aggregate data is being collected for the client group." aggregate data is being collected for the client group."
::= { tn3270eRtDataEntry 2 } ::= { tn3270eRtDataEntry 2 }
tn3270eRtDataClientPort OBJECT-TYPE tn3270eRtDataClientPort OBJECT-TYPE
SYNTAX Unsigned32(0..65535) SYNTAX Unsigned32(0..65535)
skipping to change at page 38, line 36 skipping to change at page 38, line 50
::= { tn3270eRtGroups 2 } ::= { tn3270eRtGroups 2 }
END END
6.0 Security Considerations 6.0 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. An authentication protocol is SHOULD be employed in such environments. An authentication protocol is
defined in [10]. A protocol for access control is defined in [11]. defined in [12]. A protocol for access control is defined in [15].
Several objects in this MIB allow write access or provide for row 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 a
negative effect on network operations. It is RECOMMENDED that negative effect on network operations. It is RECOMMENDED that
implementers seriously consider whether set operations or row creation implementers seriously consider whether set operations or row creation
SHOULD be allowed without providing, at a minimum, authentication of SHOULD be allowed without providing, at a minimum, authentication of
request origin. It is RECOMMENDED that without such support that the request origin. It is RECOMMENDED that without such support that the
following objects be implemented as read-only: following objects be implemented as read-only:
o tn3270eRtCollCtlType o tn3270eRtCollCtlType
o tn3270eRtCollCtlSPeriod o tn3270eRtCollCtlSPeriod
o tn3270eRtCollCtlSPMult o tn3270eRtCollCtlSPMult
o tn3270eRtCollCtlThreshHigh o tn3270eRtCollCtlThreshHigh
o tn3270eRtCollCtlThreshLow o tn3270eRtCollCtlThreshLow
o tn3270eRtCollCtlIdleCount o tn3270eRtCollCtlIdleCount
o tn3270eRtCollCtlBucketBndry1 o tn3270eRtCollCtlBucketBndry1
skipping to change at page 39, line 41 skipping to change at page 40, line 5
8.0 Acknowledgments 8.0 Acknowledgments
This document is a product of the TN3270E Working Group. Special thanks This document is a product of the TN3270E Working Group. Special thanks
are due to Derek Bolton and Michael Boe of Cisco Systems for their are due to Derek Bolton and Michael Boe of Cisco Systems for their
numerous comments and suggestions for improving the structure of this numerous comments and suggestions for improving the structure of this
MIB. Thanks also to Randy Presuhn of BMC Software for his valuable MIB. Thanks also to Randy Presuhn of BMC Software for his valuable
review comments on several versions of the document. review comments on several versions of the document.
9.0 References 9.0 References
[1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network [1] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for
Management Protocol", RFC 1157, SNMP Research, Performance Systems Describing SNMP Management Frameworks", RFC 2271, Cabletron
International, MIT Laboratory for Computer Science, May 1990. Systems, Inc., BMC Software, Inc., IBM T.J. Watson Research,
January 1998.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [2] Rose, M., and K. McCloghrie, "Structure and Identification of
for Network Management of TCP/IP-based internets: MIB-II", STD 17, Management Information for TCP/IP-based Internets", RFC 1155,
RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991.
[3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, January 1996. Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, January 1996. (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance
"Conformance Statements for Version 2 of the Simple Network Statements for Version 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC 1904, January 1996. (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Operations for Version 2 of the Simple Network Management Protocol Management Protocol", RFC 1157, SNMP Research, Performance Systems
(SNMPv2)", RFC 1905, January 1996. International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Describing SNMP Management Frameworks", RFC 2271, Cabletron "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research,
Systems, BMC Software, Inc., IBM T.J. Watson Research, January Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
1998. International Network Services, January 1996.
[8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Dispatching for the Simple Network Management Protocol (SNMP)", RFC Mappings for Version 2 of the Simple Network Management Protocol
2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Research, January 1998. Dover Beach Consulting, Inc., International Network Services,
January 1996.
[9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, Processing and Dispatching for the Simple Network Management
January 1998. Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998. 2274, IBM T. J. Watson Research, January 1998.
[11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Model (VACM) for the Simple Network Management Protocol (SNMP)", Operations for Version 2 of the Simple Network Management Protocol
RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Systems, Inc., January 1998. Dover Beach Consulting, Inc., International Network Services,
January 1996.
[12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998
[16] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC
854, May 1983. 854, May 1983.
[13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, [17] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860,
May 1983. May 1983.
[14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.
[15] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998. [19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.
[16] White, K. and Moore, R., "Base Definitions of Managed Objects for [20] White, K. and Moore, R., "Base Definitions of Managed Objects for
TN3270E Using SMIv2", Internet-Draft Work in progress, April 1998. TN3270E Using SMIv2", Internet-Draft Work in progress, April 1998.
[17] IBM, International Technical Support Centers, "Response Time Data [21] IBM, International Technical Support Centers, "Response Time Data
Gathering", GG24-3212-01, November 1990. Gathering", GG24-3212-01, November 1990.
[18] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF [22] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF
Standards Process", BCP 11, RFC 2028, October 1996. Standards Process", BCP 11, RFC 2028, October 1996.
[19] Bradner, S., "Key words for use in RFCs to Indicate Requirement [23] 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.
10.0 Authors' Addresses 10.0 Authors' Addresses
Kenneth D. White Kenneth D. White
Dept. BRQA/Bldg. 501/G114 Dept. BRQA/Bldg. 501/G114
IBM Corporation IBM Corporation
P.O.Box 12195 P.O.Box 12195
3039 Cornwallis 3039 Cornwallis
Research Triangle Park, NC 27709, USA Research Triangle Park, NC 27709, USA
E-mail: kennethw@vnet.ibm.com E-mail: kennethw@vnet.ibm.com
Robert Moore Robert Moore
Dept. BRQA/Bldg. 501/G114 Dept. BRQA/Bldg. 501/G114
 End of changes. 52 change blocks. 
85 lines changed or deleted 130 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/