draft-ietf-pint-mib-05.txt   rfc3055.txt 
PINT Working Group Murali Krishnaswamy Network Working Group M. Krishnaswamy
Internet Draft Lucent Technologies Request for Comments: 3055 Photuris, Inc.
Dan Romascanu Category: Standards Track D. Romascanu
Avaya Communication Avaya Communication
February 2001
Expires May 2001 16 November 2000
Management Information Base for the PINT Services Architecture Management Information Base for the PINT Services Architecture
<draft-ietf-pint-mib-05.txt> Status of this Memo
Abstract
This memo describes a proposed MIB for the PINT Services
Architecture.
Table of Contents This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Status of this Memo 1 Copyright Notice
Abstract 1
1 Introduction 2
2 The SNMP Management Framework 2
3 The need for PINT Services monitoring MIB 3
4 PINT MIB Overview 4
5 Definitions 5
6 Acknowledgements 17
7 Security Considerations 18
8 IANA Considerations 18
9 Intellectual Property 18
10 References 19
11 Author's Address 20
A Full Copyright Statement 21
Status of this Memo Copyright (C) The Internet Society (2001). All Rights Reserved.
This document is an Internet-Draft and is in full conformance with Abstract
all provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet- Drafts.
Internet-Drafts are draft documents valid for a maximum of six months This memo describes a proposed Management Information Base (MIB) for
and may be updated, replaced, or obsoleted by other documents at any the PSTN/Internet Interworking (PINT) Services Architecture.
time. It is inappropriate to use Internet Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Table of Contents
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at 1. Introduction ................................................ 2
http://www.ietf.org/shadow.html. 2. The SNMP Management Framework ............................... 2
3. The need for PINT Services monitoring MIB ................... 3
4. PINT MIB Overview ........................................... 4
5. Definitions ................................................. 5
6. Acknowledgements ............................................ 17
7. Security Considerations ..................................... 17
8. IANA Considerations ......................................... 18
9. Intellectual Property ....................................... 18
10. References .................................................. 18
11. Authors' Addresses .......................................... 20
12. Full Copyright Statement .................................... 21
1. Introduction 1. Introduction
PINT services are an emerging set of new Internet based applications PINT services are an emerging set of new Internet based applications
where voice (and fax) requests to the PSTN (Public Switched Telephone where voice (and fax) requests to the PSTN (Public Switched Telephone
Network) are carried over the Internet. RFC 2458 [1] gives a good Network) are carried over the Internet. RFC 2458 [1] gives a good
introduction to the (pre-standard) PINT architecture and services. introduction to the (pre-standard) PINT architecture and services.
It also has examples of some of the early implementations of pre- It also has examples of some of the early implementations of pre-
PINT. PINT.
This document defines a MIB which contains the elements for This document defines a MIB which contains the elements for
monitoring the performance of a PINT based service. The MIB consists monitoring the performance of a PINT based service. The MIB consists
of details of the four basic PINT services and their performance of details of the four basic PINT services and their performance
statistics measured under various criteria. statistics measured under various criteria.
It is not the purpose of this MIB to enable management of the PINT It is not the purpose of this MIB to enable management of the PINT
networking elements. We are concerned only with the PINT specific networking elements. We are concerned only with the PINT specific
performance parameters. While it is understood that PINT service performance parameters. While it is understood that PINT service
performance is closely related to host and network performance, they performance is closely related to host and network performance, they
are not addressed here. are not addressed here.
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [2]. o An overall architecture, described in RFC 2571 [2].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [3], RFC 1212 [4] and RFC 1215 [5]. The second version, STD 16, RFC 1155 [3], STD 16, RFC 1212 [4] and RFC 1215 [5].
called SMIv2, is described in RFC 2578 [6], RFC 2579 [7] and RFC The second version, called SMIv2, is described in STD 58,
2580 [8]. RFC 2578 [6], RFC 2579 [7] and RFC 2580 [8].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [9]. A second version of the SNMP message described in STD 15, RFC 1157 [9]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [10] and RFC 1906 [11]. protocol, is called SNMPv2c and described in RFC 1901 [10] and
The third version of the message protocol is called SNMPv3 and RFC 1906 [11]. The third version of the message protocol is
described in RFC 1906 [11], RFC 2572 [12] and RFC 2574 [13]. called SNMPv3 and described in RFC 1906 [11], RFC 2572 [12] and
RFC 2574 [13].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [9]. A second set of protocol operations described in STD 15, RFC 1157 [9]. A second set of protocol
and associated PDU formats is described in RFC 1905 [14]. operations and associated PDU formats is described in RFC 1905
[14].
o A set of fundamental applications described in RFC 2573 [15] and o A set of fundamental applications described in RFC 2573 [15] and
the view-based access control mechanism described in RFC 2575 the view-based access control mechanism described in RFC 2575
[16]. [16].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [17]. can be found in RFC 2570 [17].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
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
requests, in terms of availability and security. However when the the requests, in terms of availability and security. However when
requests originate from the Internet there is a concern both on the the requests originate from the Internet there is a concern both on
part of the user as well as the provider about issues like reliable the part of the user as well as the provider about issues like
forwarding of the call requests to the PINT gateway under various reliable forwarding of the call requests to the PINT gateway under
network conditions, user/host authentication, secure handling of the various network conditions, user/host authentication, secure handling
user information etc. Performance and security management becomes of the user information etc. Performance and security management
all the more important where PINT services cross multiple becomes all the more important where PINT services cross multiple
administrative 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 chose to build the configuration table as an extension of the o We chose to build the configuration table as an extension of the
Application MIB - RFC 2287 [19] using the augments construct. Application MIB - RFC 2287 [19] using the augments construct.
Server location and contact might be retrieved from the standard Server location and contact might be retrieved from the standard
MIB-II sysLocation and sysContact objects. There is no need to MIB-II sysLocation and sysContact objects. There is no need to
replicate this information in the PINT MIB. However, the PINT replicate this information in the PINT MIB. However, the PINT
administrator may be a different person than the sysadmin with administrator may be a different person than the sysadmin with
global responsibilities, thus a pintSysContact object is 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
tions to the gateways might need to be monitored in order to connections to the gateways might need to be monitored in order
understand what goes on. We placed them in a separate MIB group, to understand what goes on. We placed them in a separate MIB
and by using MODULE-COMPLIANCE clauses, agents that cannot group, and by using MODULE-COMPLIANCE clauses, agents that
implement this stuff will not be mandated to do it. cannot implement this stuff will not be mandated to do it.
o There is no traps definition in this MIB module. Note that o There is no traps definition in this MIB module. Note that
thresholding on counters is always possible by using a standard thresholding on counters is always possible by using a standard
mechanism defined by the Remote Monitoring MIB, that can be ref- mechanism defined by the Remote Monitoring MIB, that can be
erenced here. Some events that may be defined by using this referenced here. Some events that may be defined by using this
mechanisms: mechanisms:
* continuous login/authentication failure or refusal from a * continuous login/authentication failure or refusal from a
particular client or user particular client or user
* nuisance call - repeated calls (within a specified period) * nuisance call - repeated calls (within a specified
to a number originating from the same user period) to a number originating from the same user
o The client performance and user performance tables may be rather o The client performance and user performance tables may be rather
resource demanding for an agent implementation. In some MIBs, resource demanding for an agent implementation. In some MIBs,
like the Remote Monitoring (RMON) MIBs, control mechanisms were like the Remote Monitoring (RMON) MIBs, control mechanisms were
built in order to activate those statistics on demand. If built in order to activate those statistics on demand. If
needed, a sorting ('topN') mechanism can be designed, so that a needed, a sorting ('topN') mechanism can be designed, so that a
sorted view of clients or users is presented for the high level sorted view of clients or users is presented for the high level
debugging. debugging.
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
ing on the architecture) and is mapped to the SessionId. One (depending on the architecture) and is mapped to the SessionId.
way to achieve this uniqueness is by appending clientId to the One way to achieve this uniqueness is by appending clientId to
UserId string before sending to the PINT server. The SessionId the UserId string before sending to the PINT server. The
could then be a combination of this new UserId and a timestamp. SessionId 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
sysApplInstallPkgEntry sysApplInstallPkgEntry
FROM SYSAPPL-MIB FROM SYSAPPL-MIB
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; -- RFC 2571 [2] FROM SNMP-FRAMEWORK-MIB; -- RFC 2571 [2]
pintMib MODULE-IDENTITY pintMib MODULE-IDENTITY
LAST-UPDATED "200011161400Z" LAST-UPDATED "200102010000Z" -- 1 Feb 2001
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
Authors: Authors: Murali Krishnaswamy
Murali Krishnaswamy Postal: 20 Corporate Place South
Postal: 3C-512, 101 Crawfords Corner Rd. Piscataway, NJ 08854
Holmdel, NJ 07733 Tel: +1 (732)465-1000
Tel: +1 (732)949-3611 E-mail: murali@photuris.com
FAX: +1 (732)949-3210
E-mail: murali@lucent.com
Dan Romascanu Dan Romascanu
Postal: Atidim Technology Park, Bldg 3 Postal: Atidim Technology Park, Bldg 3
Tel Aviv, Israel Tel Aviv, Israel
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
following Area Director Review"
REVISION "200009061900Z"
DESCRIPTION
"Revised version - editorial and MIB corrections"
REVISION "200009061900Z"
DESCRIPTION
"This MIB defines the objects necessary to monitor "This MIB defines the objects necessary to monitor
PINT Services" PINT Services"
REVISION "200007241525Z"
-- Revision history
REVISION "200102010000Z" -- 1 Feb 2001
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxxx." "Initial version, published as RFC 3055."
::= { mib-2 xxxx } -- To be assigned by IANA ::= { mib-2 93 }
PintServiceType ::= TEXTUAL-CONVENTION PintServiceType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This TC describes the type of a PINT service." "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
} }
PintPerfStatPeriod ::= TEXTUAL-CONVENTION PintPerfStatPeriod ::= TEXTUAL-CONVENTION
STATUS current STATUS current
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
skipping to change at page 10, line 13 skipping to change at page 9, line 32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entries in the global statistics table. "Entries in the global statistics table.
One entry is defined for each monitored service type and One entry is defined for each monitored service type and
performance statistics collection period." performance statistics collection period."
INDEX {pintServerServiceTypeIndex, pintServerPerfStatPeriodIndex} INDEX {pintServerServiceTypeIndex, pintServerPerfStatPeriodIndex}
::= { pintServerGlobalStatsTable 1 } ::= { pintServerGlobalStatsTable 1 }
PintServerGlobalStatsEntry ::= SEQUENCE { PintServerGlobalStatsEntry ::= SEQUENCE {
pintServerServiceTypeIndex PintServiceType, pintServerServiceTypeIndex PintServiceType,
pintServerPerfStatPeriodIndex PintPerfStatPeriod, pintServerPerfStatPeriodIndex PintPerfStatPeriod,
pintServerGlobalCallsReceived Counter32, pintServerGlobalCallsReceived Counter32,
pintServerGlobalSuccessfulCalls Counter32, pintServerGlobalSuccessfulCalls Counter32,
pintServerGlobalDisconnectedCalls Counter32, pintServerGlobalDisconnectedCalls Counter32,
pintServerGlobalDisCUAutFCalls Counter32, pintServerGlobalDisCUAutFCalls Counter32,
pintServerGlobalDisServProbCalls Counter32, pintServerGlobalDisServProbCalls Counter32,
pintServerGlobalDisGatProbCalls Counter32 pintServerGlobalDisGatProbCalls Counter32
} }
pintServerServiceTypeIndex OBJECT-TYPE pintServerServiceTypeIndex OBJECT-TYPE
SYNTAX PintServiceType SYNTAX PintServiceType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unique identifier of the monitored service." "The unique identifier of the monitored service."
::= { pintServerGlobalStatsEntry 1 } ::= { pintServerGlobalStatsEntry 1 }
skipping to change at page 12, line 19 skipping to change at page 11, line 36
DESCRIPTION DESCRIPTION
"Entries in the client server statistics table. "Entries in the client server statistics table.
One entry is defined for each client identified by name, One entry is defined for each client identified by name,
monitored service type and performance statistics collection monitored service type and performance statistics collection
period." period."
INDEX {pintServerClientAddress, pintServerServiceTypeIndex, INDEX {pintServerClientAddress, pintServerServiceTypeIndex,
pintServerPerfStatPeriodIndex} pintServerPerfStatPeriodIndex}
::= { pintServerClientStatsTable 1 } ::= { pintServerClientStatsTable 1 }
PintServerClientStatsEntry ::= SEQUENCE { PintServerClientStatsEntry ::= SEQUENCE {
pintServerClientAddress SnmpAdminString, pintServerClientAddress SnmpAdminString,
pintServerClientCallsReceived Counter32, pintServerClientCallsReceived Counter32,
pintServerClientSuccessfulCalls Counter32, pintServerClientSuccessfulCalls Counter32,
pintServerClientDisconnectedCalls Counter32, pintServerClientDisconnectedCalls Counter32,
pintServerClientDisCAutFCalls Counter32, pintServerClientDisCAutFCalls Counter32,
pintServerClientDisEFProbCalls Counter32 pintServerClientDisEFProbCalls Counter32
} }
pintServerClientAddress OBJECT-TYPE pintServerClientAddress OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 14, line 51 skipping to change at page 14, line 21
::= { 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 }
pintServerUserIdDiscUIdAFailCalls pintServerUserIdDiscUIdAFailCalls
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
authorization failure." user authorization failure."
::= { pintServerUserIdStatsEntry 5 } ::= { pintServerUserIdStatsEntry 5 }
pintServerUserIdEFProbCalls OBJECT-TYPE pintServerUserIdEFProbCalls 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 "Number of calls from the user that were disconnected because of
egress facility problems." egress facility problems."
::= { pintServerUserIdStatsEntry 6 } ::= { pintServerUserIdStatsEntry 6 }
skipping to change at page 18, line 8 skipping to change at page 17, line 25
END END
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Igor Faynberg for his encouragement The authors would like to thank Igor Faynberg for his encouragement
to produce this work. to produce this work.
7. Security Considerations 7. Security Considerations
There is only one management object defined in this MIB that has a There is only one management object defined in this MIB that has a
MAX-ACCESS clause of read-write (pintSysContact). There are no read- MAX-ACCESS clause of read-write (pintSysContact). There are no
create objects. This read-write object may be considered sensitive or read-create objects. This read-write object may be considered
vulnerable in some network environments. The support for SET opera- sensitive or vulnerable in some network environments. The support
tions in a non-secure environment without proper protection can have for SET operations in a non-secure environment without proper
a negative effect on network operations. protection can have a negative effect on network operations.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective. One information that may be sensitive from a business perspective. One
could be the customer identification (UserIdName). Also information could be the customer identification (UserIdName). Also information
on PINT services performance might itself be need to be guarded. It on PINT services performance might itself be need to be guarded. It
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
ured to give access to the objects only to those principals (users) configured to give access to the objects only to those principals
that have legitimate rights to indeed GET or SET (change/cre- (users) that have legitimate rights to indeed GET or SET
ate/delete) them. (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
All extensions to the values listed in this MIB must be done through All extensions to the values listed in this MIB must be done through
Standards Action processes as defined in RFC 2434 [20]. Standards Action processes as defined in RFC 2434 [20].
9. Intellectual Property 9. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per- intellectual property or other rights that might be claimed to
tain to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might this document or the extent to which any license under such rights
or might not be available; neither does it represent that it has made might or might not be available; neither does it represent that it
any effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and standards- IETF's procedures with respect to rights in standards-track and
related documentation can be found in BCP-11. Copies of claims of standards-related documentation can be found in BCP-11. Copies of
rights made available for publication and any assurances of licenses claims of rights made available for publication and any assurances of
to be made available, or the result of an attempt made to obtain a licenses to be made available, or the result of an attempt made to
general license or permission for the use of such proprietary rights obtain a general license or permission for the use of such
by implementors or users of this specification can be obtained from proprietary rights by implementors or users of this specification can
the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
10. References 10. References
[1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre- [1] Lu, H., Conroy, L., Bellovin, S., Krishnaswamy, M., Burg, F.,
PINT Implementations", RFC 2458, November 1998. DeSimone, A., Tewani, K., Davidson, P., Schulzrinne, H. and K.
Vishwanathan, "Toward the PSTN/Internet Inter-Networking --
Pre-PINT Implementations", RFC 2458, November 1998.
[2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for [2] Wijnen, B., Harrington, D. and R. Presuhn, "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 K. McCloghrie, "Structure and Identification of
agement Information for TCP/IP-based Internets", RFC 1155, May Management Information for TCP/IP-based Internets", STD 16, RFC
1990. 1155, May 1990.
[4] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, [4] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
March 1991. RFC 1212, 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
RFC 1215, March 1991. SNMP", RFC 1215, March 1991.
[6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of [6] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of
Management Information Version 2 (SMIv2)", RFC 2578, April 1999. Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual Con- [7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual
ventions for SMIv2", RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[8] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance [8] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
Statements for SMIv2", RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[9] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple Net- [9] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
work Management Protocol", RFC 1157, May 1990. Network Management Protocol", STD 15, RFC 1157, May 1990.
[10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Introduc- [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
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 S. Waldbusser, "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 B. Wijnen, "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 B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)", for version 3 of the Simple Network Management Protocol
RFC 2574, April 1999. (SNMPv3)", RFC 2574, April 1999.
[14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [14] Case, J., McCloghrie, K., Rose, M. and Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1905, January 1996. Protocol (SNMPv2)", RFC 1905, January 1996.
[15] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC [15] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999. 2573, April 1999.
[16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [16] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to [17] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction
Version 3 of the Internet-standard Network Management Framework", to Version 3 of the Internet-standard Network Management
RFC 2570, April 1999. Framework", RFC 2570, April 1999.
[18] S. Petrack, L. Conroy, "The PINT Service Protocol: Extensions to [18] Petrack, S. and L. Conroy, "The PINT Service Protocol:
SIP and SDP for IP Access to Telephone Call Services", draft-ietf- Extensions to SIP and SDP for IP Access to Telephone Call
pint-protocol-01.txt, 14 July 1999. Services", RFC 2848, June 2000.
[19] C. Krupczak, J. Saperia, "Definitions of System-Level Managed [19] Krupczak, C. and J. Saperia, "Definitions of System-Level
Objects for Applications", RFC 2287, February 1998. Managed Objects for Applications", RFC 2287, February 1998.
[20] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA Consid- [20] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
erations Section in RFCs", RFC 2434, October 1998. Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
11. Authors' Addresses 11. Authors' Addresses
Murali Krishnaswamy Murali Krishnaswamy
Lucent Technologies Lucent Technologies
3C-512, 101 Crawfords Corner Rd. 3C-512, 101 Crawfords Corner Rd.
Holmdel, NJ 07733 Holmdel, NJ 07733
Tel: +1 (732)949-3611
Fax: +1 (732)949-3210 Phone: +1 (732)949-3611
E-mail: murali@lucent.com Fax: +1 (732)949-3210
EMail: murali@lucent.com
Dan Romascanu Dan Romascanu
Avaya Communication Avaya Communication
Atidim Technology Park, Bldg 3 Atidim Technology Park, Bldg 3
Tel Aviv, Israel Tel Aviv, Israel
Tel: +972 3 6458414
E-mail: dromasca@avaya.com
A. Full Copyright Statement Phone: +972 3 6458414
EMail: dromasca@avaya.com
This document and translations of it may be copied and furnished to 12. Full Copyright Statement
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright (C) The Internet Society (2001). All Rights Reserved.
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and translations of it may be copied and furnished to
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING others, and derivative works that comment on or otherwise explain it
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING or assist in its implementation may be prepared, copied, published
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION and distributed, in whole or in part, without restriction of any
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF kind, provided that the above copyright notice and this paragraph are
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 81 change blocks. 
244 lines changed or deleted 221 lines changed or added

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