idnits 2.17.1 draft-ietf-madman-netsm-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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** 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 seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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 an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. -- The draft header indicates that this document obsoletes RFC1565, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC2248, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 93 has weird spacing: '...defines trans...' == Line 837 has weird spacing: '...ntal in provi...' == Line 915 has weird spacing: '...rnished to...' == Line 916 has weird spacing: '...herwise expla...' == Line 918 has weird spacing: '...without restr...' == (6 more instances...) -- 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 (August 1998) is 9386 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) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '3') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (ref. '5') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1907 (ref. '6') (Obsoleted by RFC 3418) ** Obsolete normative reference: RFC 1908 (ref. '7') (Obsoleted by RFC 2576) ** Obsolete normative reference: RFC 1779 (ref. '8') (Obsoleted by RFC 2253, RFC 3494) ** Obsolete normative reference: RFC 1327 (ref. '9') (Obsoleted by RFC 2156) ** Obsolete normative reference: RFC 1738 (ref. '10') (Obsoleted by RFC 4248, RFC 4266) ** Obsolete normative reference: RFC 1565 (ref. '11') (Obsoleted by RFC 2248) Summary: 21 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Ned Freed, Innosoft 2 Internet Draft Steve Kille, ISODE Consortium 3 Obsoletes: 1565, 2248 5 Network Services Monitoring MIB 7 August 1998 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, and 13 its working groups. Note that other groups may also distribute working 14 documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months. 17 Internet-Drafts may be updated, replaced, or obsoleted by other 18 documents at any time. It is not appropriate to use Internet-Drafts as 19 reference material or to cite them other than as a "working draft" or 20 "work in progress". 22 To view the entire list of current Internet-Drafts, please check 23 the "1id-abstracts.txt" listing contained in the Internet-Drafts 24 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 25 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 26 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 27 (US West Coast). 29 Copyright (C) The Internet Society (1998). All Rights Reserved. 31 1. Introduction 33 A networked application is a realization of some well defined service on 34 one or more host computers that is accessible via some network, uses 35 some network for its internal operations, or both. 37 There are a wide range of networked applications for which it is 38 appropriate to provide SNMP monitoring of their network usage. This 39 includes applications using both TCP/IP and OSI networking. This 40 document defines a MIB which contains the elements common to the 41 monitoring of any network service application. This information 42 includes a table of all monitorable network service applications, a 43 count of the associations (connections) to each application, and basic 44 information about the parameters and status of each application-related 45 association. 47 This MIB may be used on its own for any application, and for most simple 48 applications this will suffice. This MIB is also designed to serve as a 49 building block which can be used in conjunction with application- 50 specific monitoring and management. Two examples of this are MIBs 51 defining additional variables for monitoring a Message Transfer Agent 52 (MTA) service or a Directory Service Agent (DSA) service. It is expected 53 that further MIBs of this nature will be specified. 55 This MIB does not attempt to provide facilities for management of the 56 host or hosts the network service application runs on, nor does it 57 provide facilities for monitoring applications that provide something 58 other than a network service. Host resource and general application 59 monitoring is handled by the Host Resources MIB at present; development 60 of an additional application MIB is currently underway in the IETF. 62 2. Table of Contents 64 1 Introduction .................................................... 1 65 2 Table of Contents ............................................... 2 66 3 The SNMPv2 Network Management Framework ......................... 2 67 3.1 Object Definitions ............................................ 3 68 4 Rationale for having a Network Services Monitoring MIB .......... 3 69 4.1 General Relationship to Other MIBs ............................ 4 70 4.2 Restriction of Scope .......................................... 4 71 4.3 Configuration Information ..................................... 5 72 5 Application Objects ............................................. 5 73 6 Definitions ..................................................... 6 74 7 Changes made since RFC 2248 ..................................... 21 75 8 Acknowledgements ................................................ 21 76 9 References ...................................................... 21 77 10 Security Considerations ........................................ 22 78 11 Author and Chair Addresses ..................................... 22 79 12 Full Copyright Statement ....................................... 23 81 3. The SNMPv2 Network Management Framework 83 The SNMPv2 Network Management Framework consists of seven major 84 components. They are: 86 o RFC 1902 [1] which defines the SMI, the mechanisms used for 87 describing and naming objects for the purpose of management. 89 o RFC 1903 [2] defines textual conventions for SNMPv2. 91 o RFC 1904 [3] defines conformance statements for SNMPv2. 93 o RFC 1905 [4] defines transport mappings for SNMPv2. 95 o RFC 1906 [5] defines the protocol operations used for network 96 access to managed objects. 98 o RFC 1907 [6] defines the Management Information Base for SNMPv2. 100 o RFC 1908 [7] specifies coexistance between SNMP and SNMPv2. 102 The Framework permits new objects to be defined for the purpose of 103 experimentation and evaluation. 105 3.1. Object Definitions 107 Managed objects are accessed via a virtual information store, termed the 108 Management Information Base or MIB. Objects in the MIB are defined using 109 the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. 110 In particular, each object type is named by an OBJECT IDENTIFIER, an 111 administratively assigned name. The object type together with an object 112 instance serves to uniquely identify a specific instantiation of the 113 object. For human convenience, we often use a textual string, termed 114 the descriptor, to refer to the object type. 116 4. Rationale for having a Network Services Monitoring MIB 118 Much effort has been expended in developing tools to manage lower layer 119 network facilities. However, relatively little work has been done on 120 managing application layer entities. It is neither efficient nor 121 reasonable to manage all aspects of application layer entities using 122 only lower layer information. Moreover, the difficulty of managing 123 application entities in this way increases dramatically as application 124 entities become more complex. 126 This leads to a substantial need to monitor applications which provide 127 network services, particularly distributed components such as MTAs and 128 DSAs, by monitoring specific aspects of the application itself. Reasons 129 to monitor such components include but are not limited to measuring 130 load, detecting broken connectivity, isolating system failures, and 131 locating congestion. 133 In order to manage network service applications effectively two 134 requirements must be met: 136 (1) It must be possible to monitor a large number of components 137 (typical for a large organization). 139 (2) Application monitoring must be integrated into general network 140 management. 142 This specification defines simple read-only access; this is sufficient 143 to determine up/down status and provide an indication of a broad class 144 of operational problems. 146 4.1. General Relationship to Other MIBs 148 This MIB is intended to only provide facilities common to the monitoring 149 of any network service application. It does not provide all the 150 facilities necessary to monitor any specific application. Each specific 151 type of network service application is expected to have a MIB of its own 152 that makes use of these common facilities. 154 4.2. Restriction of Scope 156 The framework provided here is very minimal; there is a lot more that 157 could be done. For example: 159 (1) General network service application configuration monitoring and 160 control. 162 (2) Detailed examination and modification of individual entries in 163 service-specific request queues. 165 (3) Probing to determine the status of a specific request (e.g., the 166 location of a mail message with a specific message-id). 168 (4) Requesting that certain actions be performed (e.g., forcing an 169 immediate connection and transfer of pending messages to some 170 specific system). 172 All these capabilities are both impressive and useful. However, these 173 capabilities would require provisions for strict security checking. 174 These capabilities would also mandate a much more complex design, with 175 many characteristics likely to be fairly implementation-specific. As a 176 result such facilities are likely to be both contentious and difficult 177 to implement. 179 This document religiously keeps things simple and focuses on the basic 180 monitoring aspect of managing applications providing network services. 181 The goal here is to provide a framework which is simple, useful, and 182 widely implementable. 184 4.3. Configuration Information 186 This MIB attempts to provide information about the operational aspects 187 of an application. Further information about the actual configuration of 188 a given application may be kept in other places; the applDirectoryName 189 or applURL may be used to point to places where such information is 190 kept. 192 5. Application Objects 194 This MIB defines a set of general purpose attributes which would be 195 appropriate for a range of applications that provide network services. 196 Both OSI and non-OSI services can be accomodated. Additional tables 197 defined in extensions to this MIB provide attributes specific to 198 specific network services. 200 A table is defined which will have one row for each operational network 201 service application on the system. The only static information held on 202 the application is its name. All other static information should be 203 obtained from various directory services. The applDirectoryName is an 204 external key, which allows an SNMP MIB entry to be cleanly related to 205 the X.500 Directory. In SNMP terms, the applications are grouped in a 206 table called applTable, which is indexed by an integer key applIndex. 208 The type of the application will be determined by one or both of: 210 (1) Additional MIB variables specific to the applications. 212 (2) An association to the application of a specific protocol. 214 6. Definitions 216 NETWORK-SERVICES-MIB DEFINITIONS ::= BEGIN 218 IMPORTS 219 OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 220 FROM SNMPv2-SMI 221 DisplayString, TimeStamp, TEXTUAL-CONVENTION 222 FROM SNMPv2-TC 223 MODULE-COMPLIANCE, OBJECT-GROUP 224 FROM SNMPv2-CONF; 226 application MODULE-IDENTITY 227 LAST-UPDATED "9808030000Z" 228 ORGANIZATION "IETF Mail and Directory Management Working Group" 229 CONTACT-INFO 230 " Ned Freed 232 Postal: Innosoft International, Inc. 233 1050 Lakes Drive 234 West Covina, CA 91790 235 US 237 Tel: +1 626 919 3600 238 Fax: +1 626 919 3614 240 E-Mail: ned.freed@innosoft.com" 241 DESCRIPTION 242 "The MIB module describing network service applications" 243 REVISION "9311280000Z" 244 DESCRIPTION 245 "The original version of this MIB was published in RFC 1565" 246 REVISION "9708170000Z" 247 DESCRIPTION 248 "This revision, published in RFC 2248, adds the 249 applDescription and applURL objects, adds the quiescing 250 state to the applOperStatus object, and renames the MIB 251 from the APPLICATION-MIB to the NETWORK-SERVICE-MIB." 252 REVISION "9808030000Z" 253 DESCRIPTION 254 "This revision, published in RFC XXXX, fixes a number of 255 technical problems found in previous versions. No changes 256 have been made to the objects this MIB defines." 257 ::= {mib-2 27} 259 -- Textual conventions 261 -- DistinguishedName is used to refer to objects in the 262 -- directory. 264 DistinguishedName ::= TEXTUAL-CONVENTION 265 STATUS current 266 DESCRIPTION 267 "A Distinguished Name represented in accordance with 268 RFC 1779 [8]." 269 SYNTAX DisplayString 271 -- Uniform Resource Locators are stored in URLStrings. 273 URLString ::= TEXTUAL-CONVENTION 274 STATUS current 275 DESCRIPTION 276 "A Uniform Resource Locator represented in accordance 277 with RFC 1738 [10]." 278 SYNTAX DisplayString 280 -- The basic applTable contains a list of the application 281 -- entities. 283 applTable OBJECT-TYPE 284 SYNTAX SEQUENCE OF ApplEntry 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "The table holding objects which apply to all different 289 kinds of applications providing network services. 290 Each network service application capable of being 291 monitored should have a single entry in this table." 292 ::= {application 1} 294 applEntry OBJECT-TYPE 295 SYNTAX ApplEntry 296 MAX-ACCESS not-accessible 297 STATUS current 298 DESCRIPTION 299 "An entry associated with a single network service 300 application." 301 INDEX {applIndex} 302 ::= {applTable 1} 304 ApplEntry ::= SEQUENCE { 305 applIndex 306 INTEGER, 307 applName 308 DisplayString, 309 applDirectoryName 310 DistinguishedName, 311 applVersion 312 DisplayString, 313 applUptime 314 TimeStamp, 315 applOperStatus 316 INTEGER, 317 applLastChange 318 TimeStamp, 319 applInboundAssociations 320 Gauge32, 321 applOutboundAssociations 322 Gauge32, 323 applAccumulatedInboundAssociations 324 Counter32, 325 applAccumulatedOutboundAssociations 326 Counter32, 327 applLastInboundActivity 328 TimeStamp, 329 applLastOutboundActivity 330 TimeStamp, 331 applRejectedInboundAssociations 332 Counter32, 333 applFailedOutboundAssociations 334 Counter32, 335 applDescription 336 DisplayString, 337 applURL 338 URLString 339 } 341 applIndex OBJECT-TYPE 342 SYNTAX INTEGER (1..2147483647) 343 MAX-ACCESS not-accessible 344 STATUS current 345 DESCRIPTION 346 "An index to uniquely identify the network service 347 application. This attribute is the index used for 348 lexicographic ordering of the table." 350 ::= {applEntry 1} 352 applName OBJECT-TYPE 353 SYNTAX DisplayString 354 MAX-ACCESS read-only 355 STATUS current 356 DESCRIPTION 357 "The name the network service application chooses to be 358 known by." 359 ::= {applEntry 2} 361 applDirectoryName OBJECT-TYPE 362 SYNTAX DistinguishedName 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The Distinguished Name of the directory entry where 367 static information about this application is stored. 368 An empty string indicates that no information about 369 the application is available in the directory." 370 ::= {applEntry 3} 372 applVersion OBJECT-TYPE 373 SYNTAX DisplayString 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The version of network service application software. 378 This field is usually defined by the vendor of the 379 network service application software." 380 ::= {applEntry 4} 382 applUptime OBJECT-TYPE 383 SYNTAX TimeStamp 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The value of sysUpTime at the time the network service 388 application was last initialized. If the application was 389 last initialized prior to the last initialization of the 390 network management subsystem, then this object contains 391 a zero value." 392 ::= {applEntry 5} 394 applOperStatus OBJECT-TYPE 395 SYNTAX INTEGER { 396 up(1), 397 down(2), 398 halted(3), 399 congested(4), 400 restarting(5), 401 quiescing(6) 402 } 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "Indicates the operational status of the network service 407 application. 'down' indicates that the network service is 408 not available. 'up' indicates that the network service 409 is operational and available. 'halted' indicates that the 410 service is operational but not available. 'congested' 411 indicates that the service is operational but no additional 412 inbound associations can be accomodated. 'restarting' 413 indicates that the service is currently unavailable but is 414 in the process of restarting and will be available soon. 415 'quiescing' indicates that service is currently operational 416 but is in the process of shutting down. Additional inbound 417 associations may be rejected by applications in the 418 'quiescing' state." 419 ::= {applEntry 6} 421 applLastChange OBJECT-TYPE 422 SYNTAX TimeStamp 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The value of sysUpTime at the time the network service 427 application entered its current operational state. If 428 the current state was entered prior to the last 429 initialization of the local network management subsystem, 430 then this object contains a zero value." 431 ::= {applEntry 7} 433 applInboundAssociations OBJECT-TYPE 434 SYNTAX Gauge32 435 MAX-ACCESS read-only 436 STATUS current 437 DESCRIPTION 438 "The number of current associations to the network service 439 application, where it is the responder. An inbound 440 assocation occurs when a another application successfully 441 connects to this one." 442 ::= {applEntry 8} 444 applOutboundAssociations OBJECT-TYPE 445 SYNTAX Gauge32 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "The number of current associations to the network service 450 application, where it is the initiator. An outbound 451 association occurs when this application successfully 452 connects to another one." 453 ::= {applEntry 9} 455 applAccumulatedInboundAssociations OBJECT-TYPE 456 SYNTAX Counter32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The total number of associations to the application entity 461 since application initialization, where it was the responder." 462 ::= {applEntry 10} 464 applAccumulatedOutboundAssociations OBJECT-TYPE 465 SYNTAX Counter32 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The total number of associations to the application entity 470 since application initialization, where it was the initiator." 471 ::= {applEntry 11} 473 applLastInboundActivity OBJECT-TYPE 474 SYNTAX TimeStamp 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "The value of sysUpTime at the time this application last 479 had an inbound association. If the last association 480 occurred prior to the last initialization of the network 481 subsystem, then this object contains a zero value." 482 ::= {applEntry 12} 484 applLastOutboundActivity OBJECT-TYPE 485 SYNTAX TimeStamp 486 MAX-ACCESS read-only 487 STATUS current 488 DESCRIPTION 489 "The value of sysUpTime at the time this application last 490 had an outbound association. If the last association 491 occurred prior to the last initialization of the network 492 subsystem, then this object contains a zero value." 493 ::= {applEntry 13} 495 applRejectedInboundAssociations OBJECT-TYPE 496 SYNTAX Counter32 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "The total number of inbound associations the application 501 entity has rejected, since application initialization. 502 Rejected associations are not counted in the accumulated 503 association totals. Note that this only counts 504 associations the application entity has rejected itself; 505 it does not count rejections that occur at lower layers 506 of the network. Thus, this counter may not reflect the 507 true number of failed inbound associations." 508 ::= {applEntry 14} 510 applFailedOutboundAssociations OBJECT-TYPE 511 SYNTAX Counter32 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The total number associations where the application entity 516 is initiator and association establishment has failed, 517 since application initialization. Failed associations are 518 not counted in the accumulated association totals." 519 ::= {applEntry 15} 521 applDescription OBJECT-TYPE 522 SYNTAX DisplayString 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "A text description of the application. This information 527 is intended to identify and briefly describe the 528 application in a status display." 529 ::= {applEntry 16} 531 applURL OBJECT-TYPE 532 SYNTAX URLString 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "A URL pointing to a description of the application. 537 This information is intended to identify and describe 538 the application in a status display." 539 ::= {applEntry 17} 541 -- The assocTable augments the information in the applTable 542 -- with information about associations. Note that two levels 543 -- of compliance are specified below, depending on whether 544 -- association monitoring is mandated. 546 assocTable OBJECT-TYPE 547 SYNTAX SEQUENCE OF AssocEntry 548 MAX-ACCESS not-accessible 549 STATUS current 550 DESCRIPTION 551 "The table holding a set of all active application 552 associations." 553 ::= {application 2} 555 assocEntry OBJECT-TYPE 556 SYNTAX AssocEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "An entry associated with an association for a network 561 service application." 562 INDEX {applIndex, assocIndex} 563 ::= {assocTable 1} 565 AssocEntry ::= SEQUENCE { 566 assocIndex 567 INTEGER, 568 assocRemoteApplication 569 DisplayString, 570 assocApplicationProtocol 571 OBJECT IDENTIFIER, 572 assocApplicationType 573 INTEGER, 574 assocDuration 575 TimeStamp 576 } 578 assocIndex OBJECT-TYPE 579 SYNTAX INTEGER (1..2147483647) 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "An index to uniquely identify each association for a network 584 service application. This attribute is the index that is 585 used for lexicographic ordering of the table. Note that the 586 table is also indexed by the applIndex." 587 ::= {assocEntry 1} 589 assocRemoteApplication OBJECT-TYPE 590 SYNTAX DisplayString 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The name of the system running remote network service 595 application. For an IP-based application this should be 596 either a domain name or IP address. For an OSI application 597 it should be the string encoded distinguished name of the 598 managed object. For X.400(1984) MTAs which do not have a 599 Distinguished Name, the RFC 1327 [9] syntax 600 'mta in globalid' should be used. Note, however, that not 601 all connections an MTA are necessarily to another MTA." 602 ::= {assocEntry 2} 604 assocApplicationProtocol OBJECT-TYPE 605 SYNTAX OBJECT IDENTIFIER 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "An identification of the protocol being used for the 610 application. For an OSI Application, this will be the 611 Application Context. For Internet applications, the IANA 612 maintains a registry of the OIDs which correspond to 613 well-known applications. If the application protocol is 614 not listed in the registry, an OID value of the form 615 {applTCPProtoID port} or {applUDProtoID port} are used for 616 TCP-based and UDP-based protocols, respectively. In either 617 case 'port' corresponds to the primary port number being 618 used by the protocol." 619 ::= {assocEntry 3} 621 assocApplicationType OBJECT-TYPE 622 SYNTAX INTEGER { 623 uainitiator(1), 624 uaresponder(2), 625 peerinitiator(3), 626 peerresponder(4)} 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "This indicates whether the remote application is some type of 631 client making use of this network service (e.g., a Mail User 632 Agent) or a server acting as a peer. Also indicated is whether 633 the remote end initiated an incoming connection to the network 634 service or responded to an outgoing connection made by the 635 local application. MTAs and messaging gateways are 636 considered to be peers for the purposes of this variable." 637 ::= {assocEntry 4} 639 assocDuration OBJECT-TYPE 640 SYNTAX TimeStamp 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The value of sysUpTime at the time this association was 645 started. If this association started prior to the last 646 initialization of the network subsystem, then this 647 object contains a zero value." 648 ::= {assocEntry 5} 650 -- Conformance information 652 applConformance OBJECT IDENTIFIER ::= {application 3} 654 applGroups OBJECT IDENTIFIER ::= {applConformance 1} 655 applCompliances OBJECT IDENTIFIER ::= {applConformance 2} 656 -- Compliance statements 658 applCompliance MODULE-COMPLIANCE 659 STATUS obsolete 660 DESCRIPTION 661 "The compliance statement for SNMPv2 entities 662 which implement the Network Services Monitoring MIB 663 for basic monitoring of network service applications. 664 This is the basic compliance statement for RFC 1565." 665 MODULE 666 MANDATORY-GROUPS {applGroup} 667 ::= {applCompliances 1} 669 assocCompliance MODULE-COMPLIANCE 670 STATUS obsolete 671 DESCRIPTION 672 "The compliance statement for SNMPv2 entities which 673 implement the Network Services Monitoring MIB for basic 674 monitoring of network service applications and their 675 associations. This is compliance statement for 676 RFC 1565 implementations that support association 677 monitoring." 678 MODULE 679 MANDATORY-GROUPS {applGroup, assocGroup} 680 ::= {applCompliances 2} 682 applRFC2248Compliance MODULE-COMPLIANCE 683 STATUS deprecated 684 DESCRIPTION 685 "The compliance statement for SNMPv2 entities 686 which implement the Network Services Monitoring MIB 687 for basic monitoring of network service applications. 688 This is the basic compliance statement for RFC 2248." 689 MODULE 690 MANDATORY-GROUPS {applRFC2248Group} 691 ::= {applCompliances 3} 693 assocRFC228Compliance MODULE-COMPLIANCE 694 STATUS deprecated 695 DESCRIPTION 696 "The compliance statement for SNMPv2 entities which 697 implement the Network Services Monitoring MIB for basic 698 monitoring of network service applications and their 699 associations. This is compliance statement for 700 RFC 2248 implementations that support association 701 monitoring." 702 MODULE 703 MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group} 704 ::= {applCompliances 4} 706 applRFCXXXXCompliance MODULE-COMPLIANCE 707 STATUS current 708 DESCRIPTION 709 "The compliance statement for SNMPv2 entities 710 which implement the Network Services Monitoring MIB 711 for basic monitoring of network service applications. 712 This is the basic compliance statement for RFC XXXX." 713 MODULE 714 MANDATORY-GROUPS {applRFCXXXXGroup} 715 ::= {applCompliances 5} 717 assocRFCXXXXCompliance MODULE-COMPLIANCE 718 STATUS current 719 DESCRIPTION 720 "The compliance statement for SNMPv2 entities which 721 implement the Network Services Monitoring MIB for basic 722 monitoring of network service applications and their 723 associations. This is compliance statement for 724 RFC XXXX implementations that support association 725 monitoring." 726 MODULE 727 MANDATORY-GROUPS {applRFCXXXXGroup, assocRFCXXXXGroup} 728 ::= {applCompliances 6} 730 -- Units of conformance 732 applGroup OBJECT-GROUP 733 OBJECTS { 734 applName, applVersion, applUptime, applOperStatus, 735 applLastChange, applInboundAssociations, 736 applOutboundAssociations, applAccumulatedInboundAssociations, 737 applAccumulatedOutboundAssociations, applLastInboundActivity, 738 applLastOutboundActivity, applRejectedInboundAssociations, 739 applFailedOutboundAssociations} 740 STATUS obsolete 741 DESCRIPTION 742 "A collection of objects providing basic monitoring of 743 network service applications. This is the original set 744 of such objects defined in RFC 1565." 745 ::= {applGroups 1} 747 assocGroup OBJECT-GROUP 748 OBJECTS { 749 assocRemoteApplication, assocApplicationProtocol, 750 assocApplicationType, assocDuration} 751 STATUS obsolete 752 DESCRIPTION 753 "A collection of objects providing basic monitoring of 754 network service applications' associations. This is the 755 original set of such objects defined in RFC 1565." 756 ::= {applGroups 2} 758 applRFC2248Group OBJECT-GROUP 759 OBJECTS { 760 applName, applVersion, applUptime, applOperStatus, 761 applLastChange, applInboundAssociations, 762 applOutboundAssociations, applAccumulatedInboundAssociations, 763 applAccumulatedOutboundAssociations, applLastInboundActivity, 764 applLastOutboundActivity, applRejectedInboundAssociations, 765 applFailedOutboundAssociations, applDescription, applURL} 766 STATUS deprecated 767 DESCRIPTION 768 "A collection of objects providing basic monitoring of 769 network service applications. This group was originally 770 defined in RFC 2248; note that applDirectoryName is 771 missing." 772 ::= {applGroups 3} 774 assocRFC2248Group OBJECT-GROUP 775 OBJECTS { 776 assocRemoteApplication, assocApplicationProtocol, 777 assocApplicationType, assocDuration} 778 STATUS deprecated 779 DESCRIPTION 780 "A collection of objects providing basic monitoring of 781 network service applications' associations. This group 782 was originally defined by RFC 2248." 783 ::= {applGroups 4} 785 applRFCXXXXGroup OBJECT-GROUP 786 OBJECTS { 787 applName, applDirectoryName, applVersion, applUptime, 788 applOperStatus, applLastChange, applInboundAssociations, 789 applOutboundAssociations, applAccumulatedInboundAssociations, 790 applAccumulatedOutboundAssociations, applLastInboundActivity, 791 applLastOutboundActivity, applRejectedInboundAssociations, 792 applFailedOutboundAssociations, applDescription, applURL} 793 STATUS current 794 DESCRIPTION 795 "A collection of objects providing basic monitoring of 796 network service applications. This is the appropriate set 797 for RFC XXXX and adds the applDirectoryName object missing 798 in RFC 2248." 799 ::= {applGroups 5} 801 assocRFCXXXXGroup OBJECT-GROUP 802 OBJECTS { 803 assocRemoteApplication, assocApplicationProtocol, 804 assocApplicationType, assocDuration} 805 STATUS current 806 DESCRIPTION 807 "A collection of objects providing basic monitoring of 808 network service applications' associations. This is 809 the appropriate object set for RFC XXXX." 810 ::= {applGroups 6} 812 -- OIDs of the form {applTCPProtoID port} are intended to be used 813 -- for TCP-based protocols that don't have OIDs assigned by other 814 -- means. {applUDPProtoID port} serves the same purpose for 815 -- UDP-based protocols. In either case 'port' corresponds to 816 -- the primary port number being used by the protocol. For example, 817 -- assuming no other OID is assigned for SMTP, an OID of 818 -- {applTCPProtoID 25} could be used, since SMTP is a TCP-based 819 -- protocol that uses port 25 as its primary port. 821 applTCPProtoID OBJECT IDENTIFIER ::= {application 4} 822 applUDPProtoID OBJECT IDENTIFIER ::= {application 5} 824 END 826 7. Changes made since RFC 2248 828 This revision corrects a number of minor technical errors in the 829 construction of the network services MIB. There are no substantive 830 changes to any of the objects the MIB defines. 832 8. Acknowledgements 834 This document is a product of the Mail and Directory Management (MADMAN) 835 Working Group. It is based on an earlier MIB designed by S. Kille, T. 836 Lenggenhager, D. Partain, and W. Yeong. The Electronic Mail 837 Association's TSC committee was instrumental in providing feedback on 838 and suggesting enhancements to RFC 1565 [11] that have led to the 839 present document. 841 9. References 843 [1] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure 844 of Management Information for Version 2 of the Simple Network 845 Management Protocol (SNMPv2)", RFC 1902, January 1996. 847 [2] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Textual 848 Conventions for Version 2 of the Simple Network Management Protocol 849 (SNMPv2)", RFC 1903, January 1996. 851 [3] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Conformance 852 Statements for Version 2 of the Simple Network Management Protocol 853 (SNMPv2)", RFC 1904, January 1996. 855 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 856 Operations for Version 2 of the Simple Network Management Protocol 857 (SNMPv2)", RFC 1905, January 1996. 859 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 860 Mappings for Version 2 of the Simple Network Management Protocol 861 (SNMPv2)", RFC 1906, January 1996. 863 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management 864 Information Base for Version 2 of the Simple Network Management 865 Protocol (SNMPv2)", RFC 1907, January 1996. 867 [7] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 868 "Coexistence between Version 1 and Version 2 of the Internet- 869 standard Network Management Framework", RFC 1908, January 1996. 871 [8] Kille, S., "A String Representation of Distinguished Names", RFC 872 1779, March 1995. 874 [9] Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", 875 RFC 1327, May 1992. 877 [10] Berners-Lee, T., Masinter, L., McCahill, M., iform Resource 878 Locators (URL)", RFC 1738, December 1994. 880 [11] Freed, N., Kille, S., "Network Services Monitoring MIB", RFC 1565, 881 January 1994. 883 10. Security Considerations 885 This MIB does not offer write access, and as such cannot be used to 886 actively attack a system. However, this MIB does provide passive 887 information about the existance, type, and configuration of applications 888 on a given host that could potentially indicate some sort of 889 vulnerability. Finally, the information MIB provides about network usage 890 could be used to analyze network traffic patterns. 892 11. Author and Chair Addresses 894 Ned Freed 895 Innosoft International, Inc. 896 1050 Lakes Drive 897 West Covina, CA 91790 898 USA 899 tel: +1 626 919 3600 900 fax: +1 626 919 3614 901 email: ned.freed@innosoft.com 903 Steve Kille, MADMAN WG Chair 904 ISODE Consortium 905 The Dome, The Square 906 Richmond TW9 1DT 907 UK 908 tel: +44 181 332 9091 909 email: S.Kille@isode.com 911 12. Full Copyright Statement 913 Copyright (C) The Internet Society (1998). All Rights Reserved. 915 This document and translations of it may be copied and furnished to 916 others, and derivative works that comment on or otherwise explain it or 917 assist in its implementation may be prepared, copied, published and 918 distributed, in whole or in part, without restriction of any kind, 919 provided that the above copyright notice and this paragraph are 920 included on all such copies and derivative works. However, this 921 document itself may not be modified in any way, such as by removing the 922 copyright notice or references to the Internet Society or other 923 Internet organizations, except as needed for the purpose of developing 924 Internet standards in which case the procedures for copyrights defined 925 in the Internet Standards process must be followed, or as required to 926 translate it into languages other than English. 928 The limited permissions granted above are perpetual and will not be 929 revoked by the Internet Society or its successors or assigns. 931 This document and the information contained herein is provided on an 932 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 933 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 934 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 935 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 936 FITNESS FOR A PARTICULAR PURPOSE.