idnits 2.17.1 draft-ietf-pint-mib-04.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 == The page length should not exceed 58 lines per page, but there was 19 longer pages, the longest (page 2) being 60 lines == 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 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 (6 September 2000) is 8626 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) ** Obsolete normative reference: RFC 2434 (ref. '21') (Obsoleted by RFC 5226) Summary: 20 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PINT Working Group Murali Krishnaswamy 3 Internet Draft Lucent Technologies 4 Dan Romascanu 5 Avaya Communication 7 Expires March 2001 6 September 2000 9 Management Information Base for the PINT Services Architecture 11 13 Abstract 15 This memo describes a proposed MIB for the PINT Services 16 Architecture. 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance with 21 all provisions of Section 10 of RFC 2026. Internet-Drafts are working 22 documents of the Internet Engineering Task Force (IETF), its areas, 23 and its working groups. Note that other groups may also distribute 24 working documents as Internet- Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 1. Introduction 39 PINT services are an emerging set of new Internet based applications 40 where voice (and fax) requests to the PSTN (Public Switched Telephone 41 Network) are carried over the Internet. RFC 2458 [1] gives a good 42 introduction to the (pre-standard) PINT architecture and services. 43 It also has examples of some of the early implementations of pre- 44 PINT. 46 This document defines a MIB which contains the elements for 47 monitoring the performance of a PINT based service. The MIB consists 48 of details of the four basic PINT services and their performance 49 statistics measured under various criteria. 51 It is not the purpose of this MIB to enable management of the PINT 52 networking elements. We are concerned only with the PINT specific 53 performance parameters. While it is understood that PINT service 54 performance is closely related to host and network performance, they 55 are not addressed here. 57 2. The SNMP Management Framework 59 The SNMP Management Framework presently consists of five major 60 components: 62 o An overall architecture, described in RFC 2571 [2]. 64 o Mechanisms for describing and naming objects and events for the 65 purpose of management. The first version of this Structure of 66 Management Information (SMI) is called SMIv1 and described in 67 RFC 1155 [3], RFC 1212 [4] and RFC 1215 [5]. The second version, 68 called SMIv2, is described in RFC 2578 [6], RFC 2579 [7] and RFC 69 2580 [8]. 71 o Message protocols for transferring management information. The 72 first version of the SNMP message protocol is called SNMPv1 and 73 described in RFC 1157 [9]. A second version of the SNMP message 74 protocol, which is not an Internet standards track protocol, is 75 called SNMPv2c and described in RFC 1901 [10] and RFC 1906 [11]. 76 The third version of the message protocol is called SNMPv3 and 77 described in RFC 1906 [11], RFC 2572 [12] and RFC 2574 [13]. 79 o Protocol operations for accessing management information. The 80 first set of protocol operations and associated PDU formats is 81 described in RFC 1157 [9]. A second set of protocol operations 82 and associated PDU formats is described in RFC 1905 [14]. 84 o A set of fundamental applications described in RFC 2573 [15] and 85 the view-based access control mechanism described in RFC 2575 87 [16]. 89 A more detailed introduction to the current SNMP Management Framework 90 can be found in RFC 2570 [17]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. Objects in the MIB are 94 defined using the mechanisms defined in the SMI. 96 This memo specifies a MIB module that is compliant to the SMIv2. A 97 MIB conforming to the SMIv1 can be produced through the appropriate 98 translations. The resulting translated MIB must be semantically 99 equivalent, except where objects or events are omitted because no 100 translation is possible (use of Counter64). Some machine-readable 101 information in SMIv2 will be converted into textual descriptions in 102 SMIv1 during the translation process. However, this loss of machine 103 readable information is not considered to change the semantics of the 104 MIB. 106 3. The need for PINT services monitoring MIB 108 Traditionally voice (and fax) requests originate and terminate inside 109 a PSTN network. This network is well known for robust handling of the 110 requests, in terms of availability and security. However when the 111 requests originate from the Internet there is a concern both on the 112 part of the user as well as the provider about issues like reliable 113 forwarding of the call requests to the PINT gateway under various 114 network conditions, user/host authentication, secure handling of the 115 user information etc. Performance and security management becomes 116 all the more important where PINT services cross multiple 117 administrative domains (or providers). 119 This MIB is an attempt to list the parameters that need to be 120 monitored on an user, PINT client, PINT server and PINT gateway basis. 122 (PINT services, their invocation methods/protocols and security 123 issues associated with the PINT architecture are discussed in detail 124 in [18]). 126 4. PINT MIB - Overview 128 Following is a list of some explanations on the MIB definitions that 129 we have chosen to construct. 131 o The basic purpose of this MIB is to monitor the access to PINT 132 services both from the performance and security point of view. 133 Information may pertain to a certain user or his/her system 134 (PINT client) or the system providing the PINT services (PINT 135 server) or the PINT gateway that forwards the call to the PSTN 136 network. 138 o We propose to build the configuration table as an extension of 139 the Application MIB - RFC 2287 [19] using the augments clause. 140 Server location and contact might be retrieved from the 141 standard MIB-II sysLocation and sysContact objects. There is no 142 need to replicate this information in the PINT MIB. However, the 143 PINT administrator may be a different person than the sysadmin 144 with global responsibilities, thus a pintSysContact object is 145 defined. 147 o We chose to monitor the gateway connections from the PINT 148 server. While the agent runs in the PINT servers, the links 149 to the gateways might need to be monitored in order to 150 understand what goes on. We placed them in a separate MIB group, 151 and by using MODULE-COMPLIANCE clauses, agents that cannot 152 implement this stuff will not be mandated to do it. 154 o There is no traps definition in this preliminary proposal. Note 155 that thresholding on counters is always possible by using a 156 standard mechanism defined by the Remote Monitoring MIB, that 157 can be referenced here. Some events that may be defined by using 158 this mechanisms: 160 * continuous login/authentication failure or refusal from a 161 particular client or user 163 * nuisance call - repeated calls (within a specified period) 164 to a number originating from the same user 166 o The client performance and user performance tables may be rather 167 resource demanding for an agent implementation. In some MIBs, 168 like the Remote Monitoring (RMON) MIBs, control mechanisms were 169 built in order to activate those statistics on demand. If 170 needed, a sorting ('topN') mechanism can be designed, so that a 171 sorted view of clients or users is presented for the high level 172 debugging. 174 o We built a time-distribution trying to cover both short-lived, 175 as well as longer sessions (1-10 secs, 10 secs - 1 min., 1-15 176 min., 15 mins-24 hours, longer). 178 o PintServerClientAddress is defined as a SnmpAdminString. It may 179 include an IpAddress and/or name, but we preferred to minimize 180 the number of indices at this stage, and keep a human-readable 181 format at the same time. 183 o We define pintServerUserIdName as the UserId. This UserId needs 184 to be unique across multiple PINT servers and gateways depending 185 on the architecture, and is mapped to the SessionId. One 186 way to achieve this uniqueness is by appending clientId to the 187 UserId string before sending to the PINT server. The SessionId 188 could then be a combination of this new UserId and a timestamp. 190 5. Definitions 192 PINT-MIB DEFINITIONS ::= BEGIN 194 IMPORTS 195 OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2 196 FROM SNMPv2-SMI 197 TEXTUAL-CONVENTION 198 FROM SNMPv2-TC 199 MODULE-COMPLIANCE, OBJECT-GROUP 200 FROM SNMPv2-CONF 201 sysApplInstallPkgEntry 202 FROM SYSAPPL-MIB 203 SnmpAdminString 204 FROM SNMP-FRAMEWORK-MIB; -- RFC 2271 [20] 206 pintMib MODULE-IDENTITY 207 LAST-UPDATED "0009061900Z" 208 ORGANIZATION "IETF PINT Working Group" 209 CONTACT-INFO " 210 Chairs: 211 Steve Bellovin 212 E-mail: smb@research.att.com 214 Igor Faynberg 215 E-mail: faynberg@lucent.com 217 Murali Krishnaswamy 218 Postal: 3C-512, 101 Crawfords Corner Rd. 219 Holmdel, NJ 07733 220 Tel: +1 (732)949-3611 221 FAX: +1 (732)949-3210 222 E-mail: murali@lucent.com 224 Dan Romascanu 225 Postal: Atidim Technology Park, Bldg 3 226 Tel Aviv, Israel 227 Tel: +972 3 6458414 228 E-mail: dromasca@avaya.com 230 General Discussion:pint@lists.bell-labs.com 231 To Subscribe: pint-request@lists.bell-labs.com 232 In Body: subscribe your-email-addres 233 Archive: http://www.bell-labs.com/mailing-lists/pint/ 234 " 236 DESCRIPTION 237 "Revised version - editorial and MIB corrections" 238 REVISION "0009061900Z" 239 DESCRIPTION 240 "This MIB defines the objects necessary to monitor 241 PINT Services" 242 REVISION "0007241525Z" 243 DESCRIPTION 244 "Initial version, published as RFC xxxx." 245 ::= { mib-2 99999 } -- Not an IANA number 247 PintServiceType ::= TEXTUAL-CONVENTION 248 STATUS current 249 DESCRIPTION 250 "This TC describes the type of a PINT service." 251 SYNTAX INTEGER { 252 r2C(1), -- Request-to-Talk 253 r2F(2), -- Request-to-Fax 254 r2FB(3), -- Request-to-Fax-Back 255 r2HC(4) -- Request-to-Hear-Content 256 } 258 PintPerfStatPeriod ::= TEXTUAL-CONVENTION 259 STATUS current 260 DESCRIPTION 261 "This TC describes the statistics period of time. 263 Note that the values of the counters indexed with a value 264 SinceReboot(4) can be potentially affected by a counter rollover. 265 It is the responsibility of the application using this object to 266 take into account that the counter has been zeroed each time it 267 reached a value of (2**32-1)." 268 SYNTAX INTEGER { 269 last30sec(1), -- Performance Statics for the last 30 sec 270 last15min(2), -- 15 min 271 last24Hr(3), -- 24 Hour 272 sinceReboot(4) -- Since the time the pint server was 273 -- last rebooted 274 } 276 pintServerConfig OBJECT IDENTIFIER ::= { pintMib 1 } 277 pintServerMonitor OBJECT IDENTIFIER ::= { pintMib 2 } 278 pintMibConformance OBJECT IDENTIFIER ::= { pintMib 3 } 280 -- pintServerConfig - PINT configuration MIB variables 282 pintReleaseNumber OBJECT-TYPE 283 SYNTAX SnmpAdminString 284 MAX-ACCESS read-only 285 STATUS current 286 DESCRIPTION 287 "An indication of version of the PINT protocol supported 288 by this agent." 289 ::= { pintServerConfig 1 } 291 pintSysContact OBJECT-TYPE 292 SYNTAX SnmpAdminString 293 MAX-ACCESS read-write 294 STATUS current 295 DESCRIPTION 296 "Contact information related to the administration of the PINT 297 services." 298 ::= { pintServerConfig 2 } 300 pintApplInstallPkgTable OBJECT-TYPE 301 SYNTAX SEQUENCE OF PintApplInstallPkgEntry 302 MAX-ACCESS not-accessible 303 STATUS current 304 DESCRIPTION 305 "Table describing the PINT applications that are installed." 306 ::= { pintServerConfig 3 } 308 pintApplInstallPkgEntry OBJECT-TYPE 309 SYNTAX PintApplInstallPkgEntry 310 MAX-ACCESS not-accessible 311 STATUS current 312 DESCRIPTION 313 "Entries per PINT Application." 314 AUGMENTS { sysApplInstallPkgEntry } 315 ::= { pintApplInstallPkgTable 1 } 317 PintApplInstallPkgEntry ::= SEQUENCE { 318 pintApplInstallPkgDescription SnmpAdminString 319 } 321 pintApplInstallPkgDescription OBJECT-TYPE 322 SYNTAX SnmpAdminString 323 MAX-ACCESS read-only 324 STATUS current 325 DESCRIPTION 326 "Textual description of the installed PINT application." 327 ::= { pintApplInstallPkgEntry 1 } 329 pintRegisteredGatewayTable OBJECT-TYPE 330 SYNTAX SEQUENCE OF PintRegisteredGatewayEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "Table describing the registered gateway applications." 335 ::= { pintServerConfig 4 } 337 pintRegisteredGatewayEntry OBJECT-TYPE 338 SYNTAX PintRegisteredGatewayEntry 339 MAX-ACCESS not-accessible 340 STATUS current 341 DESCRIPTION 342 "Entries per Registered Gateway Application." 343 AUGMENTS { sysApplInstallPkgEntry } 344 ::= { pintRegisteredGatewayTable 1 } 346 PintRegisteredGatewayEntry ::= SEQUENCE { 347 pintRegisteredGatewayName SnmpAdminString, 348 pintRegisteredGatewayDescription SnmpAdminString 349 } 351 pintRegisteredGatewayName OBJECT-TYPE 352 SYNTAX SnmpAdminString 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "Name of the registered gateway." 357 ::= { pintRegisteredGatewayEntry 1 } 359 pintRegisteredGatewayDescription OBJECT-TYPE 360 SYNTAX SnmpAdminString 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "Textual description of the registered gateway." 365 ::= { pintRegisteredGatewayEntry 2 } 367 -- pintServerMonitor - PINT monitoring statistics MIB variables 369 pintServerGlobalPerf OBJECT IDENTIFIER ::= {pintServerMonitor 1 } 370 pintServerClientPerf OBJECT IDENTIFIER ::= {pintServerMonitor 2 } 371 pintServerUserIdPerf OBJECT IDENTIFIER ::= {pintServerMonitor 3 } 372 pintServerGatewayPerf OBJECT IDENTIFIER ::= {pintServerMonitor 4 } 374 pintServerGlobalStatsTable OBJECT-TYPE 375 SYNTAX SEQUENCE OF PintServerGlobalStatsEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "Table displaying the monitored global server statistics." 380 ::= { pintServerGlobalPerf 1 } 382 pintServerGlobalStatsEntry OBJECT-TYPE 383 SYNTAX PintServerGlobalStatsEntry 384 MAX-ACCESS not-accessible 385 STATUS current 386 DESCRIPTION 387 "Entries in the global statistics table. 388 One entry is defined for each monitored service type and 389 performance statistics collection period." 390 INDEX {pintServerServiceTypeIndex, pintServerPerfStatPeriodIndex} 391 ::= { pintServerGlobalStatsTable 1 } 393 PintServerGlobalStatsEntry ::= SEQUENCE { 394 pintServerServiceTypeIndex PintServiceType, 395 pintServerPerfStatPeriodIndex PintPerfStatPeriod, 396 pintServerGlobalCallsReceived Counter32, 397 pintServerGlobalSuccessfulCalls Counter32, 398 pintServerGlobalDisconnectedCalls Counter32, 399 pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls 400 Counter32, 401 pintServerGlobalDisconnectedServerProblemCalls Counter32, 402 pintServerGlobalDisconnectedGatewayProblemCalls Counter32 403 } 405 pintServerServiceTypeIndex OBJECT-TYPE 406 SYNTAX PintServiceType 407 MAX-ACCESS not-accessible 408 STATUS current 409 DESCRIPTION 410 "The unique identifier of the monitored service." 411 ::= { pintServerGlobalStatsEntry 1 } 413 pintServerPerfStatPeriodIndex OBJECT-TYPE 414 SYNTAX PintPerfStatPeriod 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "Time period for which the performance statistics are requested 419 from the pint server." 420 ::= { pintServerGlobalStatsEntry 2 } 422 pintServerGlobalCallsReceived OBJECT-TYPE 423 SYNTAX Counter32 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "Number of received global calls." 428 ::= { pintServerGlobalStatsEntry 3 } 430 pintServerGlobalSuccessfulCalls OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "Number of global successful calls." 436 ::= { pintServerGlobalStatsEntry 4 } 438 pintServerGlobalDisconnectedCalls OBJECT-TYPE 439 SYNTAX Counter32 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "Number of global disconnected (failed) calls." 444 ::= { pintServerGlobalStatsEntry 5 } 446 pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls 447 OBJECT-TYPE 448 SYNTAX Counter32 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "Number of global calls that were disconnected because of client 453 or user authorization failure." 454 ::= { pintServerGlobalStatsEntry 6 } 455 pintServerGlobalDisconnectedServerProblemCalls OBJECT-TYPE 456 SYNTAX Counter32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "Number of global calls that were disconnected because of 461 server problems." 462 ::= { pintServerGlobalStatsEntry 7 } 464 pintServerGlobalDisconnectedGatewayProblemCalls OBJECT-TYPE 465 SYNTAX Counter32 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "Number of global calls that were disconnected because of 470 gateway problems." 471 ::= { pintServerGlobalStatsEntry 8 } 473 pintServerClientStatsTable OBJECT-TYPE 474 SYNTAX SEQUENCE OF PintServerClientStatsEntry 475 MAX-ACCESS not-accessible 476 STATUS current 477 DESCRIPTION 478 "Table displaying the monitored server client statistics." 479 ::= { pintServerClientPerf 1 } 481 pintServerClientStatsEntry OBJECT-TYPE 482 SYNTAX PintServerClientStatsEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "Entries in the client server statistics table. 487 One entry is defined for each client identified by name, 488 monitored service type and performance statistics collection 489 period." 490 INDEX {pintServerClientAddress, pintServerServiceTypeIndex, 491 pintServerPerfStatPeriodIndex} 492 ::= { pintServerClientStatsTable 1 } 494 PintServerClientStatsEntry ::= SEQUENCE { 495 pintServerClientAddress SnmpAdminString, 496 pintServerClientCallsReceived Counter32, 497 pintServerClientSuccessfulCalls Counter32, 498 pintServerClientDisconnectedCalls Counter32, 499 pintServerClientDisconnectedClientAuthorizationFailureCalls 500 Counter32, 501 pintServerClientDisconnectedEgressFacilityProblemCalls Counter32 502 } 503 pintServerClientAddress OBJECT-TYPE 504 SYNTAX SnmpAdminString 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "The unique identifier of the monitored client 509 identified by its address represented as as a string." 510 ::= { pintServerClientStatsEntry 1 } 512 pintServerClientCallsReceived OBJECT-TYPE 513 SYNTAX Counter32 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "Number of calls received from the specific client." 518 ::= { pintServerClientStatsEntry 2 } 520 pintServerClientSuccessfulCalls OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "Number of calls from the client successfully completed." 526 ::= { pintServerClientStatsEntry 3 } 528 pintServerClientDisconnectedCalls OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "Number of calls received from the client, and that were 534 disconnected (failed)." 535 ::= { pintServerClientStatsEntry 4 } 537 pintServerClientDisconnectedClientAuthorizationFailureCalls 538 OBJECT-TYPE 539 SYNTAX Counter32 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "Number of calls from the client that were disconnected because of 544 client authorization failure." 545 ::= { pintServerClientStatsEntry 5 } 547 pintServerClientDisconnectedEgressFacilityProblemCalls OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "Number of calls from the client that were disconnected because 553 of egress facility problems." 554 ::= { pintServerClientStatsEntry 6 } 556 pintServerUserIdStatsTable OBJECT-TYPE 557 SYNTAX SEQUENCE OF PintServerUserIdStatsEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "Table displaying the monitored Pint service user statistics." 562 ::= { pintServerUserIdPerf 1 } 564 pintServerUserIdStatsEntry OBJECT-TYPE 565 SYNTAX PintServerUserIdStatsEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "Entries in the user statistics table. 570 One entry is defined for each user identified by name, 571 each monitored service type and performance statistics collection 572 period." 573 INDEX {pintServerUserIdName, pintServerServiceTypeIndex, 574 pintServerPerfStatPeriodIndex} 575 ::= { pintServerUserIdStatsTable 1 } 577 PintServerUserIdStatsEntry ::= SEQUENCE { 578 pintServerUserIdName SnmpAdminString, 579 pintServerUserIdCallsReceived Counter32, 580 pintServerUserIdSuccessfulCalls Counter32, 581 pintServerUserIdDisconnectedCalls Counter32, 582 pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls 583 Counter32, 584 pintServerUserIdDisconnectedEgressFacilityProblemCalls Counter32 585 } 587 pintServerUserIdName OBJECT-TYPE 588 SYNTAX SnmpAdminString 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "The unique identifier of the monitored user 593 identified by its name." 594 ::= { pintServerUserIdStatsEntry 1 } 596 pintServerUserIdCallsReceived OBJECT-TYPE 597 SYNTAX Counter32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Number of calls received from the specific user." 602 ::= { pintServerUserIdStatsEntry 2 } 604 pintServerUserIdSuccessfulCalls OBJECT-TYPE 605 SYNTAX Counter32 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "Number of calls from the user successfully completed." 610 ::= { pintServerUserIdStatsEntry 3 } 612 pintServerUserIdDisconnectedCalls OBJECT-TYPE 613 SYNTAX Counter32 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "Number of calls received from the user that were 618 disconnected (failed)." 619 ::= { pintServerUserIdStatsEntry 4 } 620 pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls 621 OBJECT-TYPE 622 SYNTAX Counter32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "Number of calls from the user that were disconnected because of user 627 authorization failure." 628 ::= { pintServerUserIdStatsEntry 5 } 630 pintServerUserIdDisconnectedEgressFacilityProblemCalls OBJECT-TYPE 631 SYNTAX Counter32 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "Number of calls from the user that were disconnected because of 636 egress facility problems." 637 ::= { pintServerUserIdStatsEntry 6 } 639 pintServerGatewayStatsTable OBJECT-TYPE 640 SYNTAX SEQUENCE OF PintServerGatewayStatsEntry 641 MAX-ACCESS not-accessible 642 STATUS current 643 DESCRIPTION 644 "Table displaying the monitored gateway statistics." 645 ::= { pintServerGatewayPerf 1 } 647 pintServerGatewayStatsEntry OBJECT-TYPE 648 SYNTAX PintServerGatewayStatsEntry 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "Entries in the gateway table. 653 One entry is defined for each gateway identified by name, 654 each monitored service type and performance statistics collection 655 period." 657 INDEX { pintRegisteredGatewayName, pintServerServiceTypeIndex, 658 pintServerPerfStatPeriodIndex } 659 ::= { pintServerGatewayStatsTable 1 } 661 PintServerGatewayStatsEntry ::= SEQUENCE { 662 pintServerGatewayCallsReceived Counter32, 663 pintServerGatewaySuccessfulCalls Counter32, 664 pintServerGatewayDisconnectedCalls Counter32 665 } 667 pintServerGatewayCallsReceived OBJECT-TYPE 668 SYNTAX Counter32 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "Number of calls received at the specified gateway." 673 ::= { pintServerGatewayStatsEntry 1 } 675 pintServerGatewaySuccessfulCalls OBJECT-TYPE 676 SYNTAX Counter32 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "Number of calls successfully completed at the specified gateway." 681 ::= { pintServerGatewayStatsEntry 2 } 683 pintServerGatewayDisconnectedCalls OBJECT-TYPE 684 SYNTAX Counter32 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "Number of calls that were disconnected (failed) at the specified 689 gateway." 690 ::= { pintServerGatewayStatsEntry 3 } 692 -- 693 -- Notifications Section 694 -- (none defined) 695 -- 697 -- 698 -- Conformance Section 699 -- 701 pintMibCompliances OBJECT IDENTIFIER ::= { pintMibConformance 1 } 702 pintMibGroups OBJECT IDENTIFIER ::= { pintMibConformance 2 } 704 pintMibCompliance MODULE-COMPLIANCE 705 STATUS current 706 DESCRIPTION 707 "Describes the requirements for conformance to the 708 PINT MIB." 709 MODULE -- this module 710 MANDATORY-GROUPS { pintMibConfigGroup, pintMibMonitorGroup } 711 ::= { pintMibCompliances 1 } 713 pintMibConfigGroup OBJECT-GROUP 714 OBJECTS { 715 pintReleaseNumber, 716 pintSysContact, 717 pintApplInstallPkgDescription, 718 pintRegisteredGatewayName, 719 pintRegisteredGatewayDescription 720 } 721 STATUS current 722 DESCRIPTION 723 "A collection of objects providing configuration 724 information 725 for a PINT Server." 726 ::= { pintMibGroups 1 } 728 pintMibMonitorGroup OBJECT-GROUP 729 OBJECTS { 730 pintServerGlobalCallsReceived, 731 pintServerGlobalSuccessfulCalls, 732 pintServerGlobalDisconnectedCalls, 733 pintServerGlobalDisconnectedClientUserAuthorizationFailureCalls, 734 pintServerGlobalDisconnectedServerProblemCalls, 735 pintServerGlobalDisconnectedGatewayProblemCalls, 736 pintServerClientCallsReceived, 737 pintServerClientSuccessfulCalls, 738 pintServerClientDisconnectedCalls, 739 pintServerClientDisconnectedClientAuthorizationFailureCalls, 740 pintServerClientDisconnectedEgressFacilityProblemCalls, 741 --pintServerUserIdName, 742 pintServerUserIdCallsReceived, 743 pintServerUserIdSuccessfulCalls, 744 pintServerUserIdDisconnectedCalls, 745 pintServerUserIdDisconnectedUserIdAuthorizationFailureCalls, 746 pintServerUserIdDisconnectedEgressFacilityProblemCalls, 747 pintServerGatewayCallsReceived, 748 pintServerGatewaySuccessfulCalls, 749 pintServerGatewayDisconnectedCalls 750 } 751 STATUS current 752 DESCRIPTION 753 "A collection of objects providing monitoring 754 information 755 for a PINT Server." 756 ::= { pintMibGroups 2 } 758 END 760 6. Acknowledgements 762 The authors would like to thank Igor Faynberg for his encouragement 763 to produce this work. 765 7. Security Considerations 767 There is only one management object defined in this MIB that has a 768 MAX-ACCESS clause of read-write (pintSysContact). There are no read- 769 create objects. This read-write object may be considered sensitive or 770 vulnerable in some network environments. The support for SET opera- 771 tions in a non-secure environment without proper protection can have 772 a negative effect on network operations. 774 There are a number of managed objects in this MIB that may contain 775 information that may be sensitive from a business perspective. One 776 could be the customer identification (UserIdName). Also information 777 on PINT services performance might itself be need to be guarded. It 778 is thus important to control even GET access to these objects and 779 possibly to even encrypt the values of these object when sending them 780 over the network via SNMP. Not all versions of SNMP provide features 781 for such a secure environment. 783 SNMPv1 by itself is not a secure environment. Even if the network 784 itself is secure (for example by using IPSec), even then, there is no 785 control as to who on the secure network is allowed to access and 786 GET/SET (read/change/create/delete) the objects in this MIB. 788 It is recommended that the implementers consider the security 789 features as provided by the SNMPv3 framework. Specifically, the use 790 of the User-based Security Model RFC 2574 [13] and the View- based 791 Access Control Model RFC 2575 [16] is recommended. 793 It is then a customer/user responsibility to ensure that the SNMP 794 entity giving access to an instance of this MIB, is properly config- 795 ured to give access to the objects only to those principals (users) 796 that have legitimate rights to indeed GET or SET (change/cre- 797 ate/delete) them. 799 8. IANA Considerations 801 All extensions to the values listed in this MIB must be done through 802 Standards Action processes as defined in RFC 2434 [21]. 804 9. References 806 [1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre- 807 PINT Implementations", RFC 2458, November 1998. 809 [2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for 810 Describing SNMP Management Frameworks", RFC 2571, April 1999. 812 [3] Rose, M. and McCloghrie, K., "Structure and Identification of 813 Management Information for TCP/IP-based Internets", RFC 1155, May 814 1990. 816 [4] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, 817 March 1991. 819 [5] Rose, M., "A Convention for Defining Traps for use with the SNMP", 820 RFC 1215, March 1991. 822 [6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of 823 Management Information Version 2 (SMIv2)", RFC 2578, April 1999. 825 [7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual 826 Conventions for SMIv2", RFC 2579, April 1999. 828 [8] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance 829 Statements for SMIv2", RFC 2580, April 1999. 831 [9] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple 832 Network Management Protocol", RFC 1157, May 1990. 834 [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 835 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 837 [11] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 838 Mappings for Version 2 of the Simple Network Management Protocol 839 (SNMPv2)", RFC 1906, January 1996. 841 [12] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message 842 Processing and Dispatching for the Simple Network Management 843 Protocol (SNMP)", RFC 2572, April 1999. 845 [13] Blumenthal, U. and Wijnen, B., "User-based Security Model (USM) 846 for version 3 of the Simple Network Management Protocol (SNMPv3)", 847 RFC 2574, April 1999. 849 [14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 850 Operations for Version 2 of the Simple Network Management Protocol 851 (SNMPv2)", RFC 1905, January 1996. 853 [15] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC 854 2573, April 1999. 856 [16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 857 Control Model (VACM) for the Simple Network Management Protocol 858 (SNMP)", RFC 2575, April 1999. 860 [17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 861 Version 3 of the Internet-standard Network Management Framework", 862 RFC 2570, April 1999. 864 [18] S. Petrack, L. Conroy, "The PINT Service Protocol: Extensions to 865 SIP and SDP for IP Access to Telephone Call Services", draft-ietf- 866 pint-protocol-01.txt, 14 July 1999. 868 [19] C. Krupczak, J. Saperia, "Definitions of System-Level Managed 869 Objects for Applications", RFC 2287, February 1998. 871 [20] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for 872 Describing SNMP Management Frameworks", RFC 2271, January 1998. 874 [21] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA Consid- 875 erations Section in RFCs", RFC 2434, October 1998. 877 10. Authors' Addresses 879 Murali Krishnaswamy 880 Lucent Technologies 881 3C-512, 101 Crawfords Corner Rd. 883 Holmdel, NJ 07733 884 Tel: +1 (732)949-3611 885 Fax: +1 (732)949-3210 886 E-mail: murali@lucent.com 888 Dan Romascanu 889 Avaya Communication 890 Atidim Technology Park, Bldg 3 891 Tel Aviv, Israel 892 Tel: +972 3 6458414 893 E-mail: dromasca@lucent.com