idnits 2.17.1 draft-ietf-pint-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 20 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 4 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (7 October 1999) is 8968 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 2458 (ref. '1') ** Obsolete normative reference: RFC 2571 (ref. '2') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '5') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '9') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '10') ** Obsolete normative reference: RFC 1906 (ref. '11') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '12') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '13') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '14') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '15') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '16') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '17') (Obsoleted by RFC 3410) == Outdated reference: A later version (-03) exists of draft-ietf-pint-protocol-01 ** Obsolete normative reference: RFC 2271 (ref. '20') (Obsoleted by RFC 2571) Summary: 20 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 PINT Working Group Murali Krishnaswamy 2 Internet Draft Dan Romascanu 3 Lucent Technologies 5 Expires April 2000 7 October 1999 7 Management Information Base for the PINT Services Architecture 9 11 Abstract 13 This memo describes a proposed MIB for the PINT Services 14 Architecture. 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC 2026. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, 21 and its working groups. Note that other groups may also distribute 22 working documents as Internet- Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 1. Introduction 37 PINT services are an emerging set of new Internet based applications 38 where voice (and fax) requests to the PSTN (Public Switched Telephone 39 Network) are carried over the Internet. RFC 2458 [1] gives a good 40 introduction to the (pre-standard) PINT architecture and services. 41 It also has examples of some of the early implementations of pre- 42 PINT. 44 This document defines a MIB which contains the elements for 45 monitoring the performance of a PINT based service. The MIB consists 46 of details of the four basic PINT services and their performance 47 statistics measured under various criteria. 49 It is not the purpose of this MIB to enable management of the PINT 50 networking elements. We are concerned only with the PINT specific 51 performance parameters. While it is understood that PINT service 52 performance is closely related to host and network performance, they 53 are not addressed here. 55 2. The SNMP Management Framework 57 The SNMP Management Framework presently consists of five major 58 components: 60 o An overall architecture, described in RFC 2571 [2]. 62 o Mechanisms for describing and naming objects and events for 63 the purpose of management. The first version of this Struc- 64 ture of Management Information (SMI) is called SMIv1 and 65 described in RFC 1155 [3], RFC 1212 [4] and RFC 1215 [5]. The 66 second version, called SMIv2, is described in RFC 2578 [6], 67 RFC 2579 [7] and RFC 2580 [8]. 69 o Message protocols for transferring management information. 70 The first version of the SNMP message protocol is called 71 SNMPv1 and described in RFC 1157 [9]. A second version of the 72 SNMP message protocol, which is not an Internet standards 73 track protocol, is called SNMPv2c and described in RFC 1901 74 [10] and RFC 1906 [11]. The third version of the message pro- 75 tocol is called SNMPv3 and described in RFC 1906 [11], RFC 76 2572 [12] and RFC 2574 [13]. 78 o Protocol operations for accessing management information. The 79 first set of protocol operations and associated PDU formats 80 is described in RFC 1157 [9]. A second set of protocol opera- 81 tions and associated PDU formats is described in RFC 1905 82 [14]. 84 o A set of fundamental applications described in RFC 2573 [15] 85 and the view-based access control mechanism described in RFC 86 2575 [16]. 88 A more detailed introduction to the current SNMP Management Framework 89 can be found in RFC 2570 [17]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. Objects in the MIB are 93 defined using the mechanisms defined in the SMI. 95 This memo specifies a MIB module that is compliant to the SMIv2. A 96 MIB conforming to the SMIv1 can be produced through the appropriate 97 translations. The resulting translated MIB must be semantically 98 equivalent, except where objects or events are omitted because no 99 translation is possible (use of Counter64). Some machine-readable 100 information in SMIv2 will be converted into textual descriptions in 101 SMIv1 during the translation process. However, this loss of machine 102 readable information is not considered to change the semantics of the 103 MIB. 105 3. The need for PINT services monitoring MIB 107 Traditionally voice (and fax) requests originate and terminate inside 108 a PSTN network. This network is well known for robust handling of the 109 requests, in terms of availability and security. However when the 110 requests originate from the Internet there is a concern both on the 111 part of the user as well as the provider about issues like reliable 112 forwarding of the call requests to the PINT gateway under various 113 network conditions, user/host authentication, secure handling of the 114 user information etc. Performance and security management becomes 115 all the more important where PINT services cross multiple administra- 116 tive domains (or providers). 118 This MIB is an attempt to list the parameters that need to be moni- 119 tored on an user, PINT client, PINT server and PINT gateway basis. 121 (PINT services, their invocation methods/protocols and security 122 issues associated with the PINT architecture are discussed in detail 123 in [18]). 125 4. PINT MIB - Overview 126 Following is a list of some explanations on the MIB definitions that 127 we have chosen to construct. 129 o The basic purpose of this MIB is to monitor the access to PINT 130 services both from the performance and security point of view. 131 Information may pertain to a certain user or his/her system 132 (PINT client) or the system providing the PINT services (PINT 133 server) or the PINT gateway that forwards the call to the PSTN 134 network. 136 o We propose to build the configuration table as an extension of 137 the Application MIB - RFC 2287 [19] using the augments con- 138 struct. Server location and contact might be retrieved from the 139 standard MIB-II sysLocation and sysContact objects. There is no 140 need to replicate this information in the PINT MIB. However, the 141 PINT administrator may be a different person than the sysadmin 142 with global responsibilities, thus a pintSysContact object is 143 defined. 145 o We chose to monitor the gateway connections from the PINT 146 server. While the agent runs in the PINT servers, the connec- 147 tions to the gateways might need to be monitored in order to 148 understand what goes on. We placed them in a separate MIB group, 149 and by using MODULE-COMPLIANCE clauses, agents that cannot 150 implement this stuff will not be mandated to do it. 152 o There is no traps definition in this preliminary proposal. Note 153 that thresholding on counters is always possible by using a 154 standard mechanism defined by the Remote Monitoring MIB, that 155 can be referenced here. Some events that may be defined by using 156 this mechanisms: 158 * continuous login/authentication failure or refusal from a 159 particular client or user 161 * nuisance call - repeated calls (within a specified period) 162 to a number originating from the same user 164 o The client performance and user performance tables may be rather 165 resource demanding for an agent implementation. In some MIBs, 166 like the Remote Monitoring (RMON) MIBs, control mechanisms were 167 built in order to activate those statistics on demand. If 168 needed, a sorting ('topN') mechanism can be designed, so that a 169 sorted view of clients or users is presented for the high level 170 debugging. 172 o We built a time-distribution trying to cover both short-lived, 173 as well as longer sessions (1-10 secs, 10 secs - 1 min., 1-15 174 min., 15 mins-24 hours, longer). 176 o PintServerClientAddress is defined as a SnmpAdminString. It may 177 include an IpAddress and/or name, but we preferred to minimize 178 the number of indices at this stage, and keep a human-readable 179 format at the same time. 181 o We define pintServerUserIdName as the UserId. This UserId needs 182 to be unique across multiple PINT servers and gateways (depend- 183 ing on the architecture) and is mapped to the SessionId. One 184 way to achieve this uniqueness is by appending clientId to the 185 UserId string before sending to the PINT server. The SessionId 186 could then be a combination of this new UserId and a timestamp. 188 5. Definitions 190 PINT-MIB DEFINITIONS ::= BEGIN 192 IMPORTS 193 OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2 194 FROM SNMPv2-SMI 195 TEXTUAL-CONVENTION 196 FROM SNMPv2-TC 197 MODULE-COMPLIANCE, OBJECT-GROUP 198 FROM SNMPv2-CONF 199 SysApplInstallPkgIndex 200 FROM SYSAPPL-MIB 201 SnmpAdminString 202 FROM SNMP-FRAMEWORK-MIB; -- RFC 2271 [20] 204 pintMib MODULE-IDENTITY 205 LAST-UPDATED "9908310732Z" 206 ORGANIZATION "Lucent Technologies" 207 CONTACT-INFO 208 "Murali Krishnaswamy 209 Postal: 3C-512, 101 Crawfords Corner Rd. 211 Holmdel, NJ 07733 212 Tel: +1 (732)949-3611 213 FAX: +1 (732)949-3210 214 E-mail: murali@lucent.com 216 Dan Romascanu 217 Postal: Atidim Technology Park, Bldg 3 218 Tel Aviv, Israel 219 Tel: +972 3 6458414 220 E-mail: dromasca@lucent.com" 222 DESCRIPTION 223 "This MIB defines the objects necessary to monitor 224 PINT Services" 225 REVISION "9909161200Z" 226 DESCRIPTION 227 "Initial version, published as RFC xxxx." 228 ::= { mib-2 99999 } -- Not an IANA number 230 PintServiceType ::= TEXTUAL-CONVENTION 231 SYNTAX INTEGER { 232 R2C(1), -- Request-to-Talk 233 R2F(2), -- Request-to-Fax 234 R2FB(3), -- Request-to-Fax-Back 235 R2HC(4) -- Request-to-Hear-Content 236 } 238 PintPerfStatPeriod ::= TEXTUAL-CONVENTION 239 SYNTAX INTEGER { 240 Last30sec(1), -- Performance Statics for the last 30 sec 241 Last15min(2), -- 15 min 242 Last24Hr(3), -- 24 Hour 243 SinceReboot(4) -- Since the time the pint server was 244 -- last rebooted 245 } 246 DESCRIPTION 247 "Note that the values of the counters indexed with a value 248 SinceReboot(4) can be potentially affected by a counter rollover. 249 It is the responsibility of the application using this object to 250 take into account that the counter has been zeroed each time it 251 reached a value of (2**32-1)." 253 pintServerConfig OBJECT IDENTIFIER ::= { pintMib 1 } 254 pintServerMonitor OBJECT IDENTIFIER ::= { pintMib 2 } 255 pintMibConformance OBJECT IDENTIFIER ::= { pintMib 3 } 256 -- pintServerConfig - PINT configuration MIB variables 258 pintReleaseNumber OBJECT-TYPE 259 SYNTAX SnmpAdminString 260 MAX-ACCESS read-only 261 STATUS current 262 DESCRIPTION 263 "An indication of version of the PINT protocol supported 264 by this agent." 265 ::= { pintServerConfig 1 } 267 pintSysContact OBJECT-TYPE 268 SYNTAX SnmpAdminString 269 MAX-ACCESS read-write 270 STATUS current 271 DESCRIPTION 272 "Contact information related to the administration of the PINT 273 services." 274 ::= { pintServerConfig 2 } 276 pintApplInstallPkgTable OBJECT-TYPE 277 SYNTAX SEQUENCE OF PintApplInstallPkgEntry 278 MAX-ACCESS not-accessible 279 STATUS current 280 DESCRIPTION 281 "Table describing the PINT applications that are installed." 282 ::= { pintServerConfig 3 } 284 pintApplInstallPkgEntry OBJECT-TYPE 285 SYNTAX PintApplInstallPkgEntry 286 MAX-ACCESS not-accessible 287 STATUS current 288 DESCRIPTION 289 "Entries per PINT Application." 290 AUGMENTS { sysApplInstallPkgIndex } 291 ::= { pintApplInstallPkgTable 1 } 293 PintApplInstallPkgEntry ::= SEQUENCE { 294 pintApplInstallPkgDescription SnmpAdminString 295 } 297 pintApplInstallPkgDescription OBJECT-TYPE 298 SYNTAX SnmpAdminString 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "Textual description of the installed PINT application." 303 ::= { pintApplInstallPkgEntry 1 } 305 pintRegisteredGatewayTable OBJECT-TYPE 306 SYNTAX SEQUENCE OF PintRegisteredGatewayEntry 307 MAX-ACCESS not-accessible 308 STATUS current 309 DESCRIPTION 310 "Table describing the registered gateway applications." 311 ::= { pintServerConfig 4 } 313 pintRegisteredGatewayEntry OBJECT-TYPE 314 SYNTAX PintRegisteredGatewayEntry 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "Entries per Registered Gateway Application." 319 AUGMENTS { sysApplInstallPkgIndex, pintRegisteredGatewayName } 320 ::= { pintRegisteredGatewayTable 1 } 322 pintRegisteredGatewayEntry ::= SEQUENCE { 323 pintRegisteredGatewayName SnmpAdminString 324 pintRegisteredGatewayDescription SnmpAdminString 325 } 327 pintRegisteredGatewayName OBJECT-TYPE 328 SYNTAX SnmpAdminString 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "Name of the registered gateway." 333 ::= { pintRegisteredGatewayEntry 1 } 335 pintRegisteredGatewayDescription OBJECT-TYPE 336 SYNTAX SnmpAdminString 337 MAX-ACCESS read-only 338 STATUS current 339 DESCRIPTION 340 "Textual description of the registered gateway." 341 ::= { pintRegisteredGatewayEntry 2 } 343 -- pintServerMonitor - PINT monitoring statistics MIB variables 345 pintServerGlobalPerf OBJECT IDENTIFIER ::= {pintServerMonitor 1 } 346 pintServerClientPerf OBJECT IDENTIFIER ::= {pintServerMonitor 2 } 347 pintServerUserIdPerf OBJECT IDENTIFIER ::= {pintServerMonitor 3 } 348 pintServerGatewayPerf OBJECT IDENTIFIER ::= {pintServerMonitor 4 } 349 pintServerGlobalStatsTable OBJECT-TYPE 350 SYNTAX SEQUENCE OF PintServerGlobalStatsEntry 351 MAX-ACCESS not-accessible 352 STATUS current 353 DESCRIPTION 354 "Table displaying the monitored global server statistics." 355 ::= { pintServerGlobalPerf 1 } 357 pintServerGlobalStatsEntry OBJECT-TYPE 358 SYNTAX PintServerGlobalStatsEntry 359 MAX-ACCESS not-accessible 360 STATUS current 361 DESCRIPTION 362 "Entries in the global statistics table. 363 One entry is defined for each monitored service type and 364 performance statistics collection period." 365 INDEX {pintServerServiceTypeIndex, pintServerPerfStatPeriodIndex} 366 ::= { pintServerGlobalStatsTable 1 } 368 PintServerGlobalStatsEntry ::= SEQUENCE { 369 pintServerServiceTypeIndex PintServiceType, 370 pintServerPerfStatPeriodIndex PintPerfStatPeriod, 371 pintServerGlobalCallsReceived Counter32, 372 pintServerGlobalSuccessfulCalls Counter32, 373 pintServerGlobalDisconnectedCalls Counter32, 374 pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls 375 Counter32, 376 pintServerGlobalDisconnectedServerProblemCalls Counter32, 377 pintServerGlobalDisconnectedGatewayProblemCalls Counter32 378 } 380 pintServerServiceTypeIndex OBJECT-TYPE 381 SYNTAX PintServiceType 382 MAX-ACCESS not-accessible 383 STATUS current 384 DESCRIPTION 385 "The unique identifier of the monitored service." 386 ::= { pintServerGlobalStatsEntry 1 } 388 pintServerPerfStatPeriodIndex OBJECT-TYPE 389 SYNTAX PintPerfStatPeriod 390 MAX-ACCESS not-accessible 391 STATUS current 392 DESCRIPTION 393 "Time period for which the performance statistics are requested 394 from the pint server." 395 ::= { pintServerGlobalStatsEntry 2 } 396 pintServerGlobalCallsReceived OBJECT-TYPE 397 SYNTAX Counter32 398 MAX-ACCESS read-only 399 STATUS current 400 DESCRIPTION 401 "Number of received global calls." 402 ::= { pintServerGlobalStatsEntry 3 } 404 pintServerGlobalSuccessfulCalls OBJECT-TYPE 405 SYNTAX Counter32 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "Number of global successful calls." 410 ::= { pintServerGlobalStatsEntry 4 } 412 pintServerGlobalDisconnectedCalls OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "Number of global disconnected (failed) calls." 418 ::= { pintServerGlobalStatsEntry 5 } 420 pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls 421 OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "Number of global calls that were disconnected because of client 427 or user authorization failure." 428 ::= { pintServerGlobalStatsEntry 6 } 430 pintServerGlobalDisconnectedServerProblemCalls OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "Number of global calls that were disconnected because of 436 server problems." 437 ::= { pintServerGlobalStatsEntry 7 } 439 pintServerGlobalDisconnectedGatewayProblemCalls OBJECT-TYPE 440 SYNTAX Counter32 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "Number of global calls that were disconnected because of 445 gateway problems." 446 ::= { pintServerGlobalStatsEntry 8 } 448 pintServerClientStatsTable OBJECT-TYPE 449 SYNTAX SEQUENCE OF PintServerClientStatsEntry 450 MAX-ACCESS not-accessible 451 STATUS current 452 DESCRIPTION 453 "Table displaying the monitored server client statistics." 454 ::= { pintServerClientPerf 1 } 456 pintServerClientStatsEntry OBJECT-TYPE 457 SYNTAX PintServerClientStatsEntry 458 MAX-ACCESS not-accessible 459 STATUS current 460 DESCRIPTION 461 "Entries in the client server statistics table. 462 One entry is defined for each client identified by name, 463 monitored service type and performance statistics collection 464 period." 465 INDEX {pintServerClientAddress, pintServerServiceTypeIndex, 466 pintServerPerfStatPeriodIndex} 467 ::= { pintServerClientStatsTable 1 } 469 PintServerClientStatsEntry ::= SEQUENCE { 470 pintServerClientAddress SnmpAdminString, 471 pintServerClientCallsReceived Counter32, 472 pintServerClientSuccessfulCalls Counter32, 473 pintServerClientDisconnectedCalls Counter32, 474 pintServerClientDisconnectedClientAuthorizationFailureCalls 475 Counter32, 476 pintServerClientDisconnectedEgressFacilityProblemCalls Counter32 477 } 479 pintServerClientAddress OBJECT-TYPE 480 SYNTAX SnmpAdminString 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "The unique identifier of the monitored client 485 identified by its address represented as as a string." 486 ::= { pintServerClientStatsEntry 1 } 488 pintServerClientCallsReceived OBJECT-TYPE 489 SYNTAX Counter32 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "Number of calls received from the specific client." 494 ::= { pintServerClientStatsEntry 2 } 496 pintServerClientSuccessfulCalls OBJECT-TYPE 497 SYNTAX Counter32 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "Number of calls from the client successfully completed." 502 ::= { pintServerClientStatsEntry 3 } 504 pintServerClientDisconnectedCalls OBJECT-TYPE 505 SYNTAX Counter32 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "Number of calls received from the client, and that were 510 disconnected (failed)." 511 ::= { pintServerClientStatsEntry 4 } 513 pintServerClientDisconnectedClientAuthorizationFailureCalls 514 OBJECT-TYPE 515 SYNTAX Counter32 516 MAX-ACCESS read-only 517 STATUS current 518 DESCRIPTION 519 "Number of calls from the client that were disconnected because of 520 client authorization failure." 521 ::= { pintServerClientStatsEntry 5 } 523 pintServerClientDisconnectedEgressFacilityProblemCalls OBJECT-TYPE 524 SYNTAX Counter32 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "Number of calls from the client that were disconnected because 529 of egress facility problems." 530 ::= { pintServerClientStatsEntry 6 } 531 pintServerUserIdStatsTable OBJECT-TYPE 532 SYNTAX SEQUENCE OF PintServerUserIdStatsEntry 533 MAX-ACCESS not-accessible 534 STATUS current 535 DESCRIPTION 536 "Table displaying the monitored Pint service user statistics." 537 ::= { pintServerUserIdPerf 1 } 539 pintServerUserIdStatsEntry OBJECT-TYPE 540 SYNTAX PintServerUserIdStatsEntry 541 MAX-ACCESS not-accessible 542 STATUS current 543 DESCRIPTION 544 "Entries in the user statistics table. 545 One entry is defined for each user identified by name, 546 each monitored service type and performance statistics collection 547 period." 548 INDEX {pintServerUserIdName, pintServerServiceTypeIndex, 549 pintServerPerfStatPeriodIndex} 550 ::= { pintServerUserIdStatsTable 1 } 552 PintServerUserIdStatsEntry ::= SEQUENCE { 553 pintServerUserIdName UserIdName, 554 pintServerUserIdCallsReceived Counter32, 555 pintServerUserIdSuccessfulCalls Counter32, 556 pintServerUserIdDisconnectedCalls Counter32, 557 pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls 558 Counter32, 559 pintServerUserIdDisconnectedEgressFacilityProblemCalls Counter32 560 } 562 pintServerUserIdName OBJECT-TYPE 563 SYNTAX SnmpAdminString 564 MAX-ACCESS not-accessible 565 STATUS current 566 DESCRIPTION 567 "The unique identifier of the monitored user 568 identified by its name." 569 ::= { pintServerUserIdStatsEntry 1 } 571 pintServerUserIdCallsReceived OBJECT-TYPE 572 SYNTAX Counter32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "Number of calls received from the specific user." 577 ::= { pintServerUserIdStatsEntry 2 } 578 pintServerUserIdSuccessfulCalls OBJECT-TYPE 579 SYNTAX Counter32 580 MAX-ACCESS read-only 581 STATUS current 582 DESCRIPTION 583 "Number of calls from the user successfully completed." 584 ::= { pintServerUserIdStatsEntry 3 } 586 pintServerUserIdDisconnectedCalls OBJECT-TYPE 587 SYNTAX Counter32 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "Number of calls received from the user that were 592 disconnected (failed)." 593 ::= { pintServerUserIdStatsEntry 4 } 595 pintServerUserIdDisconnectedUserIdUserAuthorizationFailureCalls 596 OBJECT-TYPE 597 SYNTAX Counter32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Number of calls from the user that were disconnected because of user 602 authorization failure." 603 ::= { pintServerUserIdStatsEntry 5 } 605 pintServerUserIdDisconnectedEgressFacilityProblemCalls OBJECT-TYPE 606 SYNTAX Counter32 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "Number of calls from the user that were disconnected because of 611 egress facility problems." 612 ::= { pintServerUserIdStatsEntry 6 } 614 pintServerGatewayStatsTable OBJECT-TYPE 615 SYNTAX SEQUENCE OF PintServerGatewayStatsEntry 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "Table displaying the monitored gateway statistics." 620 ::= { pintServerGatewayPerf 1 } 621 pintServerGatewayStatsEntry OBJECT-TYPE 622 SYNTAX PintServerGatewayStatsEntry 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "Entries in the gateway table. 627 One entry is defined for each gateway identified by name, 628 each monitored service type and performance statistics collection 629 period." 631 INDEX { pintRegisteredGatewayName, pintServerServiceTypeIndex, 632 pintServerPerfStatPeriodIndex 633 ::= { pintServerGatewayStatsTable 1 } 635 PintServerGatewayStatsEntry ::= SEQUENCE { 636 pintServerGatewayCallsReceived Counter32, 637 pintServerGatewaySuccessfulCalls Counter32, 638 pintServerGatewayDisconnectedCalls Counter32 639 } 641 pintServerGatewayCallsReceived OBJECT-TYPE 642 SYNTAX Counter32 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "Number of calls received at the specified gateway." 647 ::= { pintServerGatewayStatsEntry 1 } 649 pintServerGatewaySuccessfulCalls OBJECT-TYPE 650 SYNTAX Counter32 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "Number of calls successfully completed at the specified gateway." 655 ::= { pintServerGatewayStatsEntry 2 } 657 pintServerGatewayDisconnectedCalls OBJECT-TYPE 658 SYNTAX Counter32 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "Number of calls that were disconnected (failed) at the specified 663 gateway." 664 ::= { pintServerGatewayStatsEntry 3 } 666 -- 667 -- Notifications Section 668 -- (none defined) 669 -- 671 -- 672 -- Conformance Section 673 -- 675 pintMibCompliances OBJECT IDENTIFIER ::= { pintMibConformance 1 } 676 pintMibGroups OBJECT IDENTIFIER ::= { pintMibConformance 2 } 678 pintMibCompliance MODULE-COMPLIANCE 679 STATUS current 680 DESCRIPTION 681 "Describes the requirements for conformance to the 682 PINT MIB." 683 MODULE -- this module 684 MANDATORY-GROUPS { pintMibConfigGroup, pintMibMonitorGroup } 685 ::= { pintMibCompliances 1 } 687 pintMibConfigGroup OBJECT-GROUP 688 OBJECTS { 689 pintReleaseNumber, 690 pintSysContact, 691 pintApplInstallPkgDescription, 692 pintRegisteredGatewayName, 693 pintRegisteredGatewayDescription 694 } 695 STATUS current 696 DESCRIPTION 697 "A collection of objects providing configuration 698 information 699 for a PINT Server." 700 ::= { pintMibGroups 1 } 702 pintMibMonitorGroup OBJECT-GROUP 703 OBJECTS { 704 pintServerServiceTypeIndex, 705 pintServerPerfStatPeriodIndex, 706 pintServerGlobalCallsReceived, 707 pintServerGlobalSuccessfulCalls, 708 pintServerGlobalDisconnectedCalls, 709 pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls, 710 pintServerGlobalDisconnectedServerProblemCalls, 711 pintServerGlobalDisconnectedGatewayProblemCalls, 712 pintServerClientAddress, 713 pintServerClientCallsReceived, 714 pintServerClientSuccessfulCalls, 715 pintServerClientDisconnectedCalls, 716 pintServerClientDisconnectedClientAuthorizationFailureCalls, 717 pintServerClientDisconnectedEgressFacilityProblemCalls, 718 pintServerUserIdName, 719 pintServerUserIdCallsReceived, 720 pintServerUserIdSuccessfulCalls, 721 pintServerUserIdDisconnectedCalls, 722 pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls, 723 pintServerUserIdDisconnectedEgressFacilityProblemCalls, 724 pintServerGatewayCallsReceived, 725 pintServerGatewaySuccessfulCalls, 726 pintServerGatewayDisconnectedCalls 727 } 728 STATUS current 729 DESCRIPTION 730 "A collection of objects providing monitoring 731 information 732 for a PINT Server." 733 ::= { pintMibGroups 2 } 735 END 737 6. Acknowledgements 739 The authors would like to thank Igor Faynberg for his encouragement 740 to produce this work. 742 7. Security Considerations 744 There is only one management object defined in this MIB that has a 745 MAX-ACCESS clause of read-write (pintSysContact). There are no read- 746 create objects. This read-write object may be considered sensitive or 747 vulnerable in some network environments. The support for SET opera- 748 tions in a non-secure environment without proper protection can have 749 a negative effect on network operations. 751 There are a number of managed objects in this MIB that may contain 752 information that may be sensitive from a business perspective. One 753 could be the customer identification (UserIdName). Also information 754 on PINT services performance might itself be need to be guarded. It 755 is thus important to control even GET access to these objects and 756 possibly to even encrypt the values of these object when sending them 757 over the network via SNMP. Not all versions of SNMP provide features 758 for such a secure environment. 760 SNMPv1 by itself is not a secure environment. Even if the network 761 itself is secure (for example by using IPSec), even then, there is no 762 control as to who on the secure network is allowed to access and 763 GET/SET (read/change/create/delete) the objects in this MIB. 765 It is recommended that the implementers consider the security 766 features as provided by the SNMPv3 framework. Specifically, the use 767 of the User-based Security Model RFC 2574 [13] and the View- based 768 Access Control Model RFC 2575 [16] is recommended. 770 It is then a customer/user responsibility to ensure that the SNMP 771 entity giving access to an instance of this MIB, is properly config- 772 ured to give access to the objects only to those principals (users) 773 that have legitimate rights to indeed GET or SET 774 (change/create/delete) them. 776 8. References 778 [1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre- 779 PINT Implementations", RFC 2458, November 1998. 781 [2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for 782 Describing SNMP Management Frameworks", RFC 2571, April 1999. 784 [3] Rose, M. and McCloghrie, K., "Structure and Identification of 785 Management Information for TCP/IP-based Internets", RFC 1155, May 786 1990. 788 [4] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, 789 March 1991. 791 [5] Rose, M., "A Convention for Defining Traps for use with the SNMP", 792 RFC 1215, March 1991. 794 [6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of 795 Management Information Version 2 (SMIv2)", RFC 2578, April 1999. 797 [7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual Con- 798 ventions for SMIv2", RFC 2579, April 1999. 800 [8] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance 801 Statements for SMIv2", RFC 2580, April 1999. 803 [9] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple Net- 804 work Management Protocol", RFC 1157, May 1990. 806 [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Introduc- 807 tion to Community-based SNMPv2", RFC 1901, January 1996. 809 [11] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 810 Mappings for Version 2 of the Simple Network Management Protocol 811 (SNMPv2)", RFC 1906, January 1996. 813 [12] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message Pro- 814 cessing and Dispatching for the Simple Network Management Protocol 815 (SNMP)", RFC 2572, April 1999. 817 [13] Blumenthal, U. and Wijnen, B., "User-based Security Model (USM) 818 for version 3 of the Simple Network Management Protocol (SNMPv3)", 819 RFC 2574, April 1999. 821 [14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 822 Operations for Version 2 of the Simple Network Management Protocol 823 (SNMPv2)", RFC 1905, January 1996. 825 [15] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC 826 2573, April 1999. 828 [16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 829 Control Model (VACM) for the Simple Network Management Protocol 830 (SNMP)", RFC 2575, April 1999. 832 [17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 833 Version 3 of the Internet-standard Network Management Framework", 834 RFC 2570, April 1999. 836 [18] S. Petrack, L. Conroy, "The PINT Service Protocol: Extensions to 837 SIP and SDP for IP Access to Telephone Call Services", draft- 838 ietf-pint-protocol-01.txt, 14 July 1999. 840 [19] C. Krupczak, J. Saperia, "Definitions of System-Level Managed 841 Objects for Applications", RFC 2287, February 1998. 843 [20] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for 844 Describing SNMP Management Frameworks", RFC 2271, January 1998. 846 9. Authors' Addresses 848 Murali Krishnaswamy 849 Lucent Technologies 850 3C-512, 101 Crawfords Corner Rd. 851 Holmdel, NJ 07733 852 Tel: +1 (732)949-3611 853 Fax: +1 (732)949-3210 854 E-mail: murali@lucent.com 856 Dan Romascanu 857 Lucent Technologies 858 Atidim Technology Park, Bldg 3 859 Tel Aviv, Israel 860 Tel: +972 3 6458414 861 E-mail: dromasca@lucent.com