draft-ietf-pint-mib-03.txt   draft-ietf-pint-mib-04.txt 
PINT Working Group Murali Krishnaswamy PINT Working Group Murali Krishnaswamy
Internet Draft Lucent Technologies Internet Draft Lucent Technologies
Dan Romascanu Dan Romascanu
Avaya Communication Avaya Communication
Expires March 2001 6 September 2000
Management Information Base for the PINT Services Architecture Management Information Base for the PINT Services Architecture
<draft-ietf-pint-mib-03.txt> <draft-ietf-pint-mib-04.txt>
Abstract Abstract
This memo describes a proposed MIB for the PINT Services This memo describes a proposed MIB for the PINT Services
Architecture. Architecture.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are working all provisions of Section 10 of RFC 2026. Internet-Drafts are working
skipping to change at page 3, line 33 skipping to change at page 3, line 33
3. The need for PINT services monitoring MIB 3. The need for PINT services monitoring MIB
Traditionally voice (and fax) requests originate and terminate inside Traditionally voice (and fax) requests originate and terminate inside
a PSTN network. This network is well known for robust handling of the a PSTN network. This network is well known for robust handling of the
requests, in terms of availability and security. However when the requests, in terms of availability and security. However when the
requests originate from the Internet there is a concern both on the requests originate from the Internet there is a concern both on the
part of the user as well as the provider about issues like reliable part of the user as well as the provider about issues like reliable
forwarding of the call requests to the PINT gateway under various forwarding of the call requests to the PINT gateway under various
network conditions, user/host authentication, secure handling of the network conditions, user/host authentication, secure handling of the
user information etc. Performance and security management becomes user information etc. Performance and security management becomes
all the more important where PINT services cross multiple administra- all the more important where PINT services cross multiple
tive domains (or providers). administrative domains (or providers).
This MIB is an attempt to list the parameters that need to be moni- This MIB is an attempt to list the parameters that need to be
tored on an user, PINT client, PINT server and PINT gateway basis. monitored on an user, PINT client, PINT server and PINT gateway basis.
(PINT services, their invocation methods/protocols and security (PINT services, their invocation methods/protocols and security
issues associated with the PINT architecture are discussed in detail issues associated with the PINT architecture are discussed in detail
in [18]). in [18]).
4. PINT MIB - Overview 4. PINT MIB - Overview
Following is a list of some explanations on the MIB definitions that Following is a list of some explanations on the MIB definitions that
we have chosen to construct. we have chosen to construct.
o The basic purpose of this MIB is to monitor the access to PINT o The basic purpose of this MIB is to monitor the access to PINT
services both from the performance and security point of view. services both from the performance and security point of view.
Information may pertain to a certain user or his/her system Information may pertain to a certain user or his/her system
(PINT client) or the system providing the PINT services (PINT (PINT client) or the system providing the PINT services (PINT
server) or the PINT gateway that forwards the call to the PSTN server) or the PINT gateway that forwards the call to the PSTN
network. network.
o We propose to build the configuration table as an extension of o We propose to build the configuration table as an extension of
the Application MIB - RFC 2287 [19] using the augments con- the Application MIB - RFC 2287 [19] using the augments clause.
struct. Server location and contact might be retrieved from the Server location and contact might be retrieved from the
standard MIB-II sysLocation and sysContact objects. There is no standard MIB-II sysLocation and sysContact objects. There is no
need to replicate this information in the PINT MIB. However, the need to replicate this information in the PINT MIB. However, the
PINT administrator may be a different person than the sysadmin PINT administrator may be a different person than the sysadmin
with global responsibilities, thus a pintSysContact object is with global responsibilities, thus a pintSysContact object is
defined. defined.
o We chose to monitor the gateway connections from the PINT o We chose to monitor the gateway connections from the PINT
server. While the agent runs in the PINT servers, the connec- server. While the agent runs in the PINT servers, the links
tions to the gateways might need to be monitored in order to to the gateways might need to be monitored in order to
understand what goes on. We placed them in a separate MIB group, understand what goes on. We placed them in a separate MIB group,
and by using MODULE-COMPLIANCE clauses, agents that cannot and by using MODULE-COMPLIANCE clauses, agents that cannot
implement this stuff will not be mandated to do it. implement this stuff will not be mandated to do it.
o There is no traps definition in this preliminary proposal. Note o There is no traps definition in this preliminary proposal. Note
that thresholding on counters is always possible by using a that thresholding on counters is always possible by using a
standard mechanism defined by the Remote Monitoring MIB, that standard mechanism defined by the Remote Monitoring MIB, that
can be referenced here. Some events that may be defined by using can be referenced here. Some events that may be defined by using
this mechanisms: this mechanisms:
skipping to change at page 5, line 16 skipping to change at page 5, line 16
o We built a time-distribution trying to cover both short-lived, o We built a time-distribution trying to cover both short-lived,
as well as longer sessions (1-10 secs, 10 secs - 1 min., 1-15 as well as longer sessions (1-10 secs, 10 secs - 1 min., 1-15
min., 15 mins-24 hours, longer). min., 15 mins-24 hours, longer).
o PintServerClientAddress is defined as a SnmpAdminString. It may o PintServerClientAddress is defined as a SnmpAdminString. It may
include an IpAddress and/or name, but we preferred to minimize include an IpAddress and/or name, but we preferred to minimize
the number of indices at this stage, and keep a human-readable the number of indices at this stage, and keep a human-readable
format at the same time. format at the same time.
o We define pintServerUserIdName as the UserId. This UserId needs o We define pintServerUserIdName as the UserId. This UserId needs
to be unique across multiple PINT servers and gateways (depend- to be unique across multiple PINT servers and gateways depending
ing on the architecture) and is mapped to the SessionId. One on the architecture, and is mapped to the SessionId. One
way to achieve this uniqueness is by appending clientId to the way to achieve this uniqueness is by appending clientId to the
UserId string before sending to the PINT server. The SessionId UserId string before sending to the PINT server. The SessionId
could then be a combination of this new UserId and a timestamp. could then be a combination of this new UserId and a timestamp.
5. Definitions 5. Definitions
PINT-MIB DEFINITIONS ::= BEGIN PINT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2 OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SysApplInstallPkgIndex sysApplInstallPkgEntry
FROM SYSAPPL-MIB FROM SYSAPPL-MIB
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; -- RFC 2271 [20] FROM SNMP-FRAMEWORK-MIB; -- RFC 2271 [20]
pintMib MODULE-IDENTITY pintMib MODULE-IDENTITY
LAST-UPDATED "200007241525Z" LAST-UPDATED "0009061900Z"
ORGANIZATION "IETF PINT Working Group" ORGANIZATION "IETF PINT Working Group"
CONTACT-INFO CONTACT-INFO "
"
Chairs: Chairs:
Steve Bellovin Steve Bellovin
E-mail: smb@research.att.com E-mail: smb@research.att.com
Igor Faynberg Igor Faynberg
E-mail: faynberg@lucent.com E-mail: faynberg@lucent.com
Murali Krishnaswamy Murali Krishnaswamy
Postal: 3C-512, 101 Crawfords Corner Rd. Postal: 3C-512, 101 Crawfords Corner Rd.
Holmdel, NJ 07733 Holmdel, NJ 07733
Tel: +1 (732)949-3611 Tel: +1 (732)949-3611
skipping to change at page 6, line 31 skipping to change at page 6, line 28
Tel: +972 3 6458414 Tel: +972 3 6458414
E-mail: dromasca@avaya.com E-mail: dromasca@avaya.com
General Discussion:pint@lists.bell-labs.com General Discussion:pint@lists.bell-labs.com
To Subscribe: pint-request@lists.bell-labs.com To Subscribe: pint-request@lists.bell-labs.com
In Body: subscribe your-email-addres In Body: subscribe your-email-addres
Archive: http://www.bell-labs.com/mailing-lists/pint/ Archive: http://www.bell-labs.com/mailing-lists/pint/
" "
DESCRIPTION DESCRIPTION
"Revised version - editorial and MIB corrections"
REVISION "0009061900Z"
DESCRIPTION
"This MIB defines the objects necessary to monitor "This MIB defines the objects necessary to monitor
PINT Services" PINT Services"
REVISION "200007241525Z" REVISION "0007241525Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxxx." "Initial version, published as RFC xxxx."
::= { mib-2 99999 } -- Not an IANA number ::= { mib-2 99999 } -- Not an IANA number
PintServiceType ::= TEXTUAL-CONVENTION PintServiceType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION
"This TC describes the type of a PINT service."
SYNTAX INTEGER { SYNTAX INTEGER {
r2C(1), -- Request-to-Talk r2C(1), -- Request-to-Talk
r2F(2), -- Request-to-Fax r2F(2), -- Request-to-Fax
r2FB(3), -- Request-to-Fax-Back r2FB(3), -- Request-to-Fax-Back
r2HC(4) -- Request-to-Hear-Content r2HC(4) -- Request-to-Hear-Content
} }
DESCRIPTION
"This TC describes the type of a PINT service."
PintPerfStatPeriod ::= TEXTUAL-CONVENTION PintPerfStatPeriod ::= TEXTUAL-CONVENTION
STATUS current STATUS current
SYNTAX INTEGER {
last30sec(1), -- Performance Statics for the last 30 sec
last15min(2), -- 15 min
last24Hr(3), -- 24 Hour
sinceReboot(4) -- Since the time the pint server was
-- last rebooted
}
DESCRIPTION DESCRIPTION
"This TC describes the statistics period of time. "This TC describes the statistics period of time.
Note that the values of the counters indexed with a value Note that the values of the counters indexed with a value
SinceReboot(4) can be potentially affected by a counter rollover. SinceReboot(4) can be potentially affected by a counter rollover.
It is the responsibility of the application using this object to It is the responsibility of the application using this object to
take into account that the counter has been zeroed each time it take into account that the counter has been zeroed each time it
reached a value of (2**32-1)." reached a value of (2**32-1)."
SYNTAX INTEGER {
last30sec(1), -- Performance Statics for the last 30 sec
last15min(2), -- 15 min
last24Hr(3), -- 24 Hour
sinceReboot(4) -- Since the time the pint server was
-- last rebooted
}
pintServerConfig OBJECT IDENTIFIER ::= { pintMib 1 } pintServerConfig OBJECT IDENTIFIER ::= { pintMib 1 }
pintServerMonitor OBJECT IDENTIFIER ::= { pintMib 2 } pintServerMonitor OBJECT IDENTIFIER ::= { pintMib 2 }
pintMibConformance OBJECT IDENTIFIER ::= { pintMib 3 } pintMibConformance OBJECT IDENTIFIER ::= { pintMib 3 }
-- pintServerConfig - PINT configuration MIB variables -- pintServerConfig - PINT configuration MIB variables
pintReleaseNumber OBJECT-TYPE pintReleaseNumber OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 8, line 17 skipping to change at page 8, line 7
DESCRIPTION DESCRIPTION
"Table describing the PINT applications that are installed." "Table describing the PINT applications that are installed."
::= { pintServerConfig 3 } ::= { pintServerConfig 3 }
pintApplInstallPkgEntry OBJECT-TYPE pintApplInstallPkgEntry OBJECT-TYPE
SYNTAX PintApplInstallPkgEntry SYNTAX PintApplInstallPkgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entries per PINT Application." "Entries per PINT Application."
AUGMENTS { sysApplInstallPkgIndex } AUGMENTS { sysApplInstallPkgEntry }
::= { pintApplInstallPkgTable 1 } ::= { pintApplInstallPkgTable 1 }
PintApplInstallPkgEntry ::= SEQUENCE { PintApplInstallPkgEntry ::= SEQUENCE {
pintApplInstallPkgDescription SnmpAdminString pintApplInstallPkgDescription SnmpAdminString
} }
pintApplInstallPkgDescription OBJECT-TYPE pintApplInstallPkgDescription OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 8, line 46 skipping to change at page 8, line 36
DESCRIPTION DESCRIPTION
"Table describing the registered gateway applications." "Table describing the registered gateway applications."
::= { pintServerConfig 4 } ::= { pintServerConfig 4 }
pintRegisteredGatewayEntry OBJECT-TYPE pintRegisteredGatewayEntry OBJECT-TYPE
SYNTAX PintRegisteredGatewayEntry SYNTAX PintRegisteredGatewayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entries per Registered Gateway Application." "Entries per Registered Gateway Application."
AUGMENTS { sysApplInstallPkgIndex, pintRegisteredGatewayName } AUGMENTS { sysApplInstallPkgEntry }
::= { pintRegisteredGatewayTable 1 } ::= { pintRegisteredGatewayTable 1 }
pintRegisteredGatewayEntry ::= SEQUENCE { PintRegisteredGatewayEntry ::= SEQUENCE {
pintRegisteredGatewayName SnmpAdminString pintRegisteredGatewayName SnmpAdminString,
pintRegisteredGatewayDescription SnmpAdminString pintRegisteredGatewayDescription SnmpAdminString
} }
pintRegisteredGatewayName OBJECT-TYPE pintRegisteredGatewayName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Name of the registered gateway." "Name of the registered gateway."
::= { pintRegisteredGatewayEntry 1 } ::= { pintRegisteredGatewayEntry 1 }
pintRegisteredGatewayDescription OBJECT-TYPE pintRegisteredGatewayDescription OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 14, line 9 skipping to change at page 13, line 31
DESCRIPTION DESCRIPTION
"Entries in the user statistics table. "Entries in the user statistics table.
One entry is defined for each user identified by name, One entry is defined for each user identified by name,
each monitored service type and performance statistics collection each monitored service type and performance statistics collection
period." period."
INDEX {pintServerUserIdName, pintServerServiceTypeIndex, INDEX {pintServerUserIdName, pintServerServiceTypeIndex,
pintServerPerfStatPeriodIndex} pintServerPerfStatPeriodIndex}
::= { pintServerUserIdStatsTable 1 } ::= { pintServerUserIdStatsTable 1 }
PintServerUserIdStatsEntry ::= SEQUENCE { PintServerUserIdStatsEntry ::= SEQUENCE {
pintServerUserIdName UserIdName, pintServerUserIdName SnmpAdminString,
pintServerUserIdCallsReceived Counter32, pintServerUserIdCallsReceived Counter32,
pintServerUserIdSuccessfulCalls Counter32, pintServerUserIdSuccessfulCalls Counter32,
pintServerUserIdDisconnectedCalls Counter32, pintServerUserIdDisconnectedCalls Counter32,
pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls
Counter32, Counter32,
pintServerUserIdDisconnectedEgressFacilityProblemCalls Counter32 pintServerUserIdDisconnectedEgressFacilityProblemCalls Counter32
} }
pintServerUserIdName OBJECT-TYPE pintServerUserIdName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
skipping to change at page 15, line 4 skipping to change at page 14, line 25
::= { pintServerUserIdStatsEntry 3 } ::= { pintServerUserIdStatsEntry 3 }
pintServerUserIdDisconnectedCalls OBJECT-TYPE pintServerUserIdDisconnectedCalls OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of calls received from the user that were "Number of calls received from the user that were
disconnected (failed)." disconnected (failed)."
::= { pintServerUserIdStatsEntry 4 } ::= { pintServerUserIdStatsEntry 4 }
pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls
pintServerUserIdDisconnectedUserIdUserAuthorizationFailureCalls
OBJECT-TYPE OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of calls from the user that were disconnected because of user "Number of calls from the user that were disconnected because of user
authorization failure." authorization failure."
::= { pintServerUserIdStatsEntry 5 } ::= { pintServerUserIdStatsEntry 5 }
pintServerUserIdDisconnectedEgressFacilityProblemCalls OBJECT-TYPE pintServerUserIdDisconnectedEgressFacilityProblemCalls OBJECT-TYPE
skipping to change at page 15, line 43 skipping to change at page 15, line 16
SYNTAX PintServerGatewayStatsEntry SYNTAX PintServerGatewayStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entries in the gateway table. "Entries in the gateway table.
One entry is defined for each gateway identified by name, One entry is defined for each gateway identified by name,
each monitored service type and performance statistics collection each monitored service type and performance statistics collection
period." period."
INDEX { pintRegisteredGatewayName, pintServerServiceTypeIndex, INDEX { pintRegisteredGatewayName, pintServerServiceTypeIndex,
pintServerPerfStatPeriodIndex pintServerPerfStatPeriodIndex }
::= { pintServerGatewayStatsTable 1 } ::= { pintServerGatewayStatsTable 1 }
PintServerGatewayStatsEntry ::= SEQUENCE { PintServerGatewayStatsEntry ::= SEQUENCE {
pintServerGatewayCallsReceived Counter32, pintServerGatewayCallsReceived Counter32,
pintServerGatewaySuccessfulCalls Counter32, pintServerGatewaySuccessfulCalls Counter32,
pintServerGatewayDisconnectedCalls Counter32 pintServerGatewayDisconnectedCalls Counter32
} }
pintServerGatewayCallsReceived OBJECT-TYPE pintServerGatewayCallsReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 17, line 22 skipping to change at page 16, line 40
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information information
for a PINT Server." for a PINT Server."
::= { pintMibGroups 1 } ::= { pintMibGroups 1 }
pintMibMonitorGroup OBJECT-GROUP pintMibMonitorGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pintServerServiceTypeIndex,
pintServerPerfStatPeriodIndex,
pintServerGlobalCallsReceived, pintServerGlobalCallsReceived,
pintServerGlobalSuccessfulCalls, pintServerGlobalSuccessfulCalls,
pintServerGlobalDisconnectedCalls, pintServerGlobalDisconnectedCalls,
pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls, pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls,
pintServerGlobalDisconnectedServerProblemCalls, pintServerGlobalDisconnectedServerProblemCalls,
pintServerGlobalDisconnectedGatewayProblemCalls, pintServerGlobalDisconnectedGatewayProblemCalls,
pintServerClientAddress,
pintServerClientCallsReceived, pintServerClientCallsReceived,
pintServerClientSuccessfulCalls, pintServerClientSuccessfulCalls,
pintServerClientDisconnectedCalls, pintServerClientDisconnectedCalls,
pintServerClientDisconnectedClientAuthorizationFailureCalls, pintServerClientDisconnectedClientAuthorizationFailureCalls,
pintServerClientDisconnectedEgressFacilityProblemCalls, pintServerClientDisconnectedEgressFacilityProblemCalls,
pintServerUserIdName, --pintServerUserIdName,
pintServerUserIdCallsReceived, pintServerUserIdCallsReceived,
pintServerUserIdSuccessfulCalls, pintServerUserIdSuccessfulCalls,
pintServerUserIdDisconnectedCalls, pintServerUserIdDisconnectedCalls,
pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls, pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls,
pintServerUserIdDisconnectedEgressFacilityProblemCalls, pintServerUserIdDisconnectedEgressFacilityProblemCalls,
pintServerGatewayCallsReceived, pintServerGatewayCallsReceived,
pintServerGatewaySuccessfulCalls, pintServerGatewaySuccessfulCalls,
pintServerGatewayDisconnectedCalls pintServerGatewayDisconnectedCalls
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 18, line 35 skipping to change at page 17, line 50
is thus important to control even GET access to these objects and is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment. for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security fea- It is recommended that the implementers consider the security
tures as provided by the SNMPv3 framework. Specifically, the use of features as provided by the SNMPv3 framework. Specifically, the use
the User-based Security Model RFC 2574 [13] and the View- based of the User-based Security Model RFC 2574 [13] and the View- based
Access Control Model RFC 2575 [16] is recommended. Access Control Model RFC 2575 [16] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly config- entity giving access to an instance of this MIB, is properly config-
ured to give access to the objects only to those principals (users) ured to give access to the objects only to those principals (users)
that have legitimate rights to indeed GET or SET (change/cre- that have legitimate rights to indeed GET or SET (change/cre-
ate/delete) them. ate/delete) them.
8. IANA Considerations 8. IANA Considerations
skipping to change at page 19, line 15 skipping to change at page 18, line 27
Standards Action processes as defined in RFC 2434 [21]. Standards Action processes as defined in RFC 2434 [21].
9. References 9. References
[1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre- [1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre-
PINT Implementations", RFC 2458, November 1998. PINT Implementations", RFC 2458, November 1998.
[2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for [2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999. Describing SNMP Management Frameworks", RFC 2571, April 1999.
[3] Rose, M. and McCloghrie, K., "Structure and Identification of Man- [3] Rose, M. and McCloghrie, K., "Structure and Identification of
agement Information for TCP/IP-based Internets", RFC 1155, May Management Information for TCP/IP-based Internets", RFC 1155, May
1990. 1990.
[4] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, [4] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212,
March 1991. March 1991.
[5] Rose, M., "A Convention for Defining Traps for use with the SNMP", [5] Rose, M., "A Convention for Defining Traps for use with the SNMP",
RFC 1215, March 1991. RFC 1215, March 1991.
[6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of [6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of
Management Information Version 2 (SMIv2)", RFC 2578, April 1999. Management Information Version 2 (SMIv2)", RFC 2578, April 1999.
[7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual Con- [7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual
ventions for SMIv2", RFC 2579, April 1999. Conventions for SMIv2", RFC 2579, April 1999.
[8] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance [8] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance
Statements for SMIv2", RFC 2580, April 1999. Statements for SMIv2", RFC 2580, April 1999.
[9] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple Net- [9] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple
work Management Protocol", RFC 1157, May 1990. Network Management Protocol", RFC 1157, May 1990.
[10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Introduc- [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
tion to Community-based SNMPv2", RFC 1901, January 1996. "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[11] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport [11] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport
Mappings for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996. (SNMPv2)", RFC 1906, January 1996.
[12] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message Pro- [12] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message
cessing and Dispatching for the Simple Network Management Protocol Processing and Dispatching for the Simple Network Management
(SNMP)", RFC 2572, April 1999. Protocol (SNMP)", RFC 2572, April 1999.
[13] Blumenthal, U. and Wijnen, B., "User-based Security Model (USM) [13] Blumenthal, U. and Wijnen, B., "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)", for version 3 of the Simple Network Management Protocol (SNMPv3)",
RFC 2574, April 1999. RFC 2574, April 1999.
[14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996. (SNMPv2)", RFC 1905, January 1996.
[15] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC [15] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC
 End of changes. 34 change blocks. 
53 lines changed or deleted 54 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/