idnits 2.17.1 draft-ietf-applmib-wwwmib-03.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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 Introduction 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.) ** There are 6 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([9], [10]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (June 1997) is 9811 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) -- Missing reference section? '9' on line 1581 looks like a reference -- Missing reference section? '10' on line 1585 looks like a reference -- Missing reference section? '1' on line 1545 looks like a reference -- Missing reference section? '2' on line 1551 looks like a reference -- Missing reference section? '3' on line 1556 looks like a reference -- Missing reference section? '4' on line 1561 looks like a reference -- Missing reference section? '6' on line 1571 looks like a reference -- Missing reference section? '5' on line 1567 looks like a reference -- Missing reference section? '12' on line 1680 looks like a reference -- Missing reference section? '13' on line 1716 looks like a reference -- Missing reference section? '11' on line 1589 looks like a reference -- Missing reference section? 'RFC 0977' on line 259 looks like a reference -- Missing reference section? 'RFC 2054' on line 259 looks like a reference -- Missing reference section? 'RFC 2055' on line 259 looks like a reference -- Missing reference section? '7' on line 1574 looks like a reference -- Missing reference section? '8' on line 1577 looks like a reference -- Missing reference section? '14' on line 1668 looks like a reference -- Missing reference section? '15' on line 1659 looks like a reference -- Missing reference section? '16' on line 1608 looks like a reference -- Missing reference section? '17' on line 1612 looks like a reference -- Missing reference section? '18' on line 1615 looks like a reference -- Missing reference section? '19' on line 1619 looks like a reference -- Missing reference section? '20' on line 1622 looks like a reference -- Missing reference section? '21' on line 1625 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 1 warning (==), 26 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft WWW Service MIB June 1997 4 Definitions of Managed Objects for WWW Services 6 June 3, 1997 8 10 Carl W. Kalbfleisch 11 Verio, Inc. 12 cwk@verio.net 14 Harrie Hazewinkel 15 Joint Research Centre of the E.C. 16 harrie.hazewinkel@jrc.it 18 Juergen Schoenwaelder 19 University of Twente 20 schoenw@cs.utwente.nl 22 Status of this Memo 24 This document is an Internet-Draft. Internet-Drafts are working 25 documents of the Internet Engineering Task Force (IETF), its areas, 26 and its working groups. Note that other groups may also distribute 27 working documents as Internet-Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet- Drafts as reference 32 material or to cite them other than as ``work in progress.'' 34 To learn the current status of any Internet-Draft, please check the 35 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 36 Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 37 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 38 ftp.isi.edu (US West Coast). 40 Distribution of this document is unlimited. Please send comments to 41 the Application MIB Working Group, . 43 1. Abstract 45 This memo defines an experimental portion of the Management 46 Information Base (MIB) for use with network management protocols in 47 the Internet Community. In particular it describes a set of objects 48 for managing World-Wide Web (WWW) services. This MIB extents the 49 application management framework defined by the System Application 50 Management MIB (SYSAPPL-MIB) [9] and the Application Management MIB 51 (APPL-MIB) [10]. The WWW service statistics are based on an abstract 52 document transfer protocol (DTP). This abstract protocol can be 53 mapped on protocols like HTTP or FTP. Additional mappings may be 54 defined in the future in order to use this MIB with other document 55 transfer protocols. 57 2. The SNMPv2 Network Management Framework 59 The SNMP Network Management Framework presently consists of three 60 major components. They are: 62 o the SMI, described in RFC 1902 [1] - the mechanisms used for 63 describing and naming objects for the purpose of management. 65 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed 66 objects for the Internet suite of protocols. 68 o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol 69 for accessing managed objects. 71 The Framework permits new objects to be defined for the purpose of 72 experimentation and evaluation. 74 2.1. Object Definitions 76 Managed objects are accessed via a virtual information store, termed 77 the Management Information Base or MIB. Objects in the MIB are 78 defined using the subset of Abstract Syntax Notation One (ASN.1) 79 defined in the SMI [1]. In particular, each object type is named by 80 an OBJECT IDENTIFIER, an administratively assigned name. The object 81 type together with an object instance serves to uniquely identify a 82 specific instantiation of the object. For human convenience, we often 83 use a textual string, termed the object descriptor, to refer to the 84 object type. 86 3. Terminology 88 This section defines the terminology used throughout this document. 90 o The 'World-Wide Web' (WWW) is a world wide information system 91 which is based on the concept of documents that are linked 92 together by embedding references (links) to other local or 93 remote documents. 95 o A 'document' is a coherent piece of data which is accessible in 96 the World-Wide Web. No assumptions are made about the content or 97 the type of a document. 99 o A 'Uniform Resource Locator' (URL) is a formatted string 100 representation for a document available via the Internet. URLs 101 are used to express references between documents. For the syntax 102 and semantics of the URL string representation is referred to 103 RFC 1630 [6] and RFC 1738 [5] 105 o A 'Document Transfer Protocol' (DTP) is a protocol used within 106 the World-Wide Web to transfer documents. The DTP is an 107 abstraction from real protocols, such as HTTP [12] or FTP [13]. 109 o A 'request' is a DTP protocol operation which is targeted to a 110 'document' and invokes an action on the target document. The 111 request type specifies the action that should be performed. A 112 request can have a document associated to it. 114 o A 'response' is a DTP protocol operation which is returned as a 115 result of a previous (and associated) request. The response 116 status indicates if the requested action was successful or if 117 errors occurred. A response can have a document associated to 118 it. 120 o An 'entity' is defined as a program which uses or provides a 121 World-Wide Web service realized through a document transfer 122 protocol. Entities can be further subdivided into client, 123 server, proxy and caching proxy entities. 125 o A 'client' is an entity which establishes connections for the 126 purpose of sending requests and receiving responses. 128 o A 'server' is an entity that accepts connections in order to 129 service requests by sending back responses. 131 o A 'proxy' is an intermediary entity which acts as both a server 132 and a client for the purpose of making requests on behalf of 133 other clients. Requests are serviced internally or by passing 134 them on, with possible translation, to other servers. 136 o A 'caching proxy' is a proxy with the capability of locally 137 storing responses to associated requests. A caching proxy can 138 respond to similar requests with a previously stored response. 140 4. Overview 142 The World-Wide Web (WWW) is a global network of information, 143 accessible via user friendly programs (so-called browser). 144 Information is stored in documents, which can have various formats, 145 including hyper-text and multi-media documents. Access to these 146 documents is provided by servers which are located all around the 147 world and are linked to each other via hyper-links embedded in 148 documents. 150 The usability of the World-Wide Web depends largely on the 151 performance of the services realized by these servers. The services 152 are typically monitored through log files. This becomes a difficult 153 task when a single organization is responsible for a large number of 154 services. It is therefore desirable to treat WWW services as objects 155 that can be managed by using the Internet network management 156 framework. 158 4.1. Purpose and Requirements 160 The goal of this MIB is to define a standardized set of objects which 161 lead to integrated and improved performance and fault management in a 162 heterogenous environment of WWW services. This MIB focuses on the 163 service level view. It does not deal with the operational view, which 164 is covered by the system application and the application MIBs [9,10]. 166 The purpose of this document is to define a set of managed objects 167 that allow to monitor WWW services for short-term operational 168 purposes, such as problem detection and troubleshooting. No attempts 169 are made here to cover accounting or hit metering issues. 171 The scope of the MIB is further limited by the requirement that an 172 implementation conforming to this MIB must be possible without a 173 putting a huge CPU or memory burden on the WWW server implementation. 175 Another issue not covered by this MIB is WWW service configuration. 176 Server software has become an interesting market where competing 177 vendors constantly invent new features in order to shape their 178 products. It is therefore not possible to reach consensus on a common 179 way to configure WWW services. 181 4.2. Relationship to other Standards Efforts 183 The WWW service MIB fits into the application management architecture 184 defined in the system application management MIB [9]. The system 185 application MIB [9] and the application MIB [10] use a process 186 oriented model, where an application is viewed as a collection of 187 processes. The WWW service MIB described in this memo uses a service 188 oriented view, which looks at the services provided by a set of 189 processes. 191 The relationship between the process oriented view and the service 192 oriented view is a many-to-many relationship, because one process can 193 implement multiple services and multiple services can be implemented 194 by a single set of processes. The application management MIB [9] is 195 expected to contain a generic mapping table, which maps back and 196 forth between both views. 198 4.3. WWW Entities 200 The MIB is organized around the concept of a WWW entity. A WWW entity 201 is either a clients, a server or a proxy. Clients send out requests 202 to request information from a server or proxy entity. Server entities 203 receive, process and respond to requests received from client 204 entities. A server has access to local documents, which can be 205 transfered to clients. 207 A proxy is a special server, who acts as both a server and a client 208 for the purpose of making requests on behalf of other clients. A 209 proxy is able to translate between the client and the origin server. 210 A proxy might also interact with other information retrieval system, 211 like for example databases. 213 The MIB defined in this memo distinguishes between outgoing and 214 incoming requests and responses. This allows to obtain statistics for 215 clients, servers and proxies with a single set of objects. 217 A special proxy server is the caching proxy, which maintains a cache 218 of previously received documents in order to reduce the bandwidth 219 used by World-Wide Web clients. One interesting management 220 information is the percentage of requests that were served from the 221 cache of the caching proxy (hits/miss-ratio). This ratio is not 222 contained explicitly in this MIB. Instead, the ratio can be derived 223 from the objects that count incoming and outgoing requests and 224 responses. 226 4.4. Document Transfer Protocol 228 The MIB is based on the concept of an abstract document transfer 229 protocol (DTP). The purpose of the abstract document transfer 230 protocol is to make the MIB definitions independent from concrete 231 protocols, like the Hypertext Transfer Protocol (HTTP) [11,12] or the 232 File Transfer Protocol (FTP) [13]. 234 The document transfer protocol makes the following assumptions: 236 - The transfer protocol uses a request/response style of 237 interactions. 239 - The request contains a request type, which defines the 240 operations performed by the receiving server. The request type 241 is represented by an OCTET STRING. It might be necessary to 242 define a translation into an OCTET STRING value for protocols 243 that use numbers to identify request types. 245 - The response contains a status code, which indicates if the 246 request was processed successfully or which error occured. The 247 status code is represented as an INTEGER value. It might be 248 necessary to define a mapping for protocols that do not use an 249 INTEGER status code. 251 - The MIB defined in this memo makes the assumption that every 252 response can be related to a particular request. Some protocols 253 allow to send multiple responses to a single request. This case 254 can be handled by defining which responses is the "primary" 255 response to a request. 257 The appendix of this memo defines a mapping of the document transfer 258 protocol on the HTTP protocol and the FTP protocol. Mappings to other 259 protocols, like NNTP [RFC 0977] or WebNFS [RFC 2054, RFC 2055] might 260 be defined in the future. 262 5. Structure of the MIB 264 This section presents the structure of the MIB. The objects are 265 arranged into the following groups: 267 o entity information 269 o service statistics 271 o document statistics 273 5.1. Entity Group 275 The entity group consists of a table describing all the entities 276 managed by the SNMP agent. The entity table contains not only basic 277 network management information for (potentially) multiple entities 278 running on a single host, but also information for all entities 279 within virtual domains of the host. The columnar objects in the table 280 can be divided into two main groups: 282 1. global administrative information of the entity, such as entity 283 contact person, and 285 2. network information, such as the transfer protocol. 287 5.2. Service Statistics Group 289 The service statistics group provides network management information 290 about the traffic received or transmitted by an entity. This group 291 contains all network traffic related counters and consists of five 292 tables: 294 o The wwwSummaryTable contains a set of network traffic related 295 counters. The table provides a summarization of the network 296 traffic which is also found in the request and response tables. 297 It is well recognized that certain variables are redundant with 298 respect to the request and response tables, but they are added 299 to provide an operator a quick overview and to reduce SNMP 300 network traffic. 302 o The wwwRequestInTable contains detailed information about 303 incoming requests. Every particular request type is counted 304 separately. 306 o The wwwRequestOutTable contains detailed information about 307 outgoing requests. Every particular request type is counted 308 separately. 310 o The wwwResponseInTable contains detailed information about 311 incoming responses. Every particular response type is counted 312 separately. 314 o The wwwResponseOutTable contains detailed information about 315 outgoing responses. Every particular response type is counted 316 separately. 318 5.3. Document Statistics Group 320 The document group contains information about the documents which 321 where accessed in the past. The group consist of the following 322 tables: 324 o The wwwDocCtrlTable provides the manager a means to control and 325 configure which statistics are collected and when statistics 326 will expire. 328 o The wwwDocLastNTable provides the manager information about the 329 last N documents which where accessed. The table lists the 330 document attempted to read together with the request and 331 response type of the DTP. The request and response types provide 332 a manager information of how the read attempts were handled by 333 the WWW entity. The number of documents in the wwwDocLastNTable 334 is controlled by the wwwDocCtrlLastNSize object in the 335 wwwDocCtrlTable. The wwwDocCtrlLastNStatus object of the 336 wwwDocCtrlTable allows to disable table updates so that a 337 manager can read fast changing tables. 339 o The wwwDocBucketTable lists the buckets of statistical 340 information that have been collected for a WWW entity. An entry 341 in the wwwDocBucketTable contains administrative information 342 about the bucket (the creation timestamp or the sort order) as 343 well as summary information (number of accesses, number of 344 document and number of bytes transferred). 346 o The wwwDocBucketTopNTable provides the manager an overview of 347 the top N documents which were accessed. The size N of a bucket 348 is controlled by the wwwDocCtrlBucketSize object in the 349 wwwDocCtrlTable. A new bucket is created after a certain time 350 interval has passed. The time interval is controlled by the 351 wwwDocCtrlBucketTimeInterval object of the wwwDocCtrlTable. The 352 maximum number of buckets maintained by the SNMP agent is 353 controlled by the wwwDocCtrlBuckets object of the 354 wwwDocCtrlTable. A bucket can be sorted according to the number 355 of accesses or the number of bytes transferred. The sort order 356 is controlled by wwwDocCtrlBucketSort object of the 357 wwwDocCtrlTable. 359 6. Definitions 361 WWW-MIB DEFINITIONS ::= BEGIN 363 IMPORTS 364 mib-2, 365 MODULE-IDENTITY, 366 OBJECT-TYPE, 367 Counter32, 368 Integer32, 369 Unsigned32 370 FROM SNMPv2-SMI 372 TEXTUAL-CONVENTION, 373 DisplayString, 374 TimeStamp, 375 DateAndTime, 376 TimeInterval 377 FROM SNMPv2-TC 379 MODULE-COMPLIANCE, 380 OBJECT-GROUP 381 FROM SNMPv2-CONF; 383 wwwMIB MODULE-IDENTITY 384 LAST-UPDATED "9703260000Z" 385 ORGANIZATION "Application MIB Working Group" 386 CONTACT-INFO 387 " Carl W. Kalbfleisch 389 Postal: Verio, Inc. 390 1950 Stemmons Freeway 391 Suite 2004 - Infomart 392 Dallas, TX 75207 393 US 395 Tel: +1 972 238-8303 396 Fax: +1 972 238-0268 398 E-mail: cwk@verio.net 400 Harrie Hazewinkel 402 Postal: MUSIQ/DESIRE/CEO Program 403 Centre for Earth Observation 404 Institute for Space Applications 405 Joint Research Centre of the E.C. 407 TP. 950 408 Ispra 21020 (VA) Italy 410 Tel: +39+(0)332+789384 411 Fax: +39+(0)332+785500 413 E-mail: harrie.hazewinkel@jrc.it 415 Juergen Schoenwaelder 417 Postal: Computer Science Department 418 University of Twente 419 P.O. Box 217, NL-7500 AE Enschede 420 The Netherlands. 422 Tel: +31-53-489-3678 423 Fax: +31-53-489-3247 425 E-mail: schoenw@cs.utwente.nl" 426 DESCRIPTION 427 "The MIB module for WWW entities. The MIB is applicable to 428 a wide family of 'Networked Information Retrieval' protocols. 429 Examples are HTTP and FTP." 431 REVISION "9706030000Z" 432 DESCRIPTION 433 "Removed text which described relationship issues because 434 relationships are now handled in the application MIB. 435 Rewrote the terminology section. Changed the structure 436 of the whole text. Removed the [## ##] marks because 437 nearly all of them referred to the old document group. 438 Rewrote and overview section. Added a discussion of 439 security issues. Added two compliance statements to 440 allow a minimal implementation for high-speed servers. 441 Added the new document tables - renamed most objects 442 in order to get a consistent naming scheme." 444 REVISION "9705050000Z" 445 DESCRIPTION 446 "Removed all the *Bogus objects and the wwwRelate group. 447 Changed the name of the document to refer to WWW services. 448 Changes the WwwRequestType to OCTET STRING to avoid 449 DisplayString subtyping and to make it more generic. 450 Changed WwwResponseType to Integer32. Removed the 451 wwwSummaryRequestErrors, wwwSummaryRequestDiscards, 452 wwwSummaryResponseDiscards, wwwSummaryInUnknowns 453 objects. Merged the wwwSummary[In|Out]Bytes into a 454 single counters. Rewrote the abstract of this document." 456 REVISION "9703260000Z" 457 DESCRIPTION 458 "Removed wwwEntityProtocolVersion. Change syntax of 459 wwwEntityUpTime. Change index of wwwDocTable. Fix import 460 for mib-2. Change description of wwwEntityLastTime. Change 461 description for wwwEntityIndex. Change wwwEntityIndex to 462 Unsigned32. Change wwwDocInstallPkg and wwwDocInstallElmt 463 to Unsigned32 to align with change to SYSAPPL-MIB. Change 464 INDEX clause for wwwDocNameEntry to use IMPLIED. Removed 465 the SMICng include file. Removed the 'Done List' appendix. 466 Replaced the protocol mappings section with a shorter 467 version. Removed the HTTP specific section from the main 468 text." 470 REVISION "9701300000Z" 471 DESCRIPTION 472 "Removed wwwEntityAddress, wwwDocFirstAccessTimeStamp, 473 wwwDocInBytes and wwwDocInCount. Rename wwwDocOutBytes to 474 wwwDocBytes and wwwDocOutCount to wwwDocCount. Changed 475 description of wwwDocStatus. Add separate indexes for request 476 and response in and out tables." 478 REVISION "9701080000Z" 479 DESCRIPTION 480 "Remove usage of applIndex. Split request/response tables." 482 REVISION "9611190000Z" 483 DESCRIPTION 484 "Add skeleton tables for extending SYSAPPL-MIB framework 485 within the wwwAppl branch." 487 REVISION "9609240000Z" 488 DESCRIPTION 489 "Update a number of descriptions to make MIB less www specific 490 and more general. Remove wwwEntityObjectID. Move wwwDocNamePkg 491 and wwwDocNameElmt to wwwDocInstallElmt and wwwDocInstallPkg 492 in wwwDocTable." 494 REVISION "9609230000Z" 495 DESCRIPTION 496 "Update a number of descriptions to make MIB less www 497 specific and more general. Changed names of Header/Data 498 byte attributes to Control/Content byte attributes." 500 ::= { mib-2 8080 } -- TBD 502 -- 503 -- Object Identifier Assignments 504 -- 506 wwwMIBObjects OBJECT IDENTIFIER ::= { wwwMIB 1 } 507 wwwMIBConformance OBJECT IDENTIFIER ::= { wwwMIB 2 } 508 wwwMIBCompliances OBJECT IDENTIFIER ::= { wwwMIBConformance 1 } 509 wwwMIBGroups OBJECT IDENTIFIER ::= { wwwMIBConformance 2 } 511 -- 512 -- Textual Conventions 513 -- 515 WwwRequestType ::= TEXTUAL-CONVENTION 516 STATUS current 517 DESCRIPTION 518 "The WwwRequestType describes the types of requests. 519 The value of this type is exactly the same textual 520 identification of request types used in the information 521 transport protocol. 523 For the proper values is referred to the specific 524 protocol specification." 525 SYNTAX OCTET STRING (SIZE (1..40)) 527 WwwResponseType ::= TEXTUAL-CONVENTION 528 STATUS current 529 DESCRIPTION 530 "The WwwResponseType defines the different response values 531 used by information transport protocols. 532 The value of this type are the 3-digit codes used in the 533 information transport protocol. 535 For the proper values is referred to the specific 536 protocol specification." 537 SYNTAX Integer32 (0..2147483647) 539 WwwEntityType ::= TEXTUAL-CONVENTION 540 STATUS current 541 DESCRIPTION 542 "The type of the wwwEntity." 543 SYNTAX INTEGER { 544 wwwEntityTypeServer(1), 545 wwwEntityTypeClient(2), 546 wwwEntityTypeProxy(3), 547 wwwEntityTypeCachingProxy(4), 548 wwwEntityTypeOther(5) 549 } 551 WwwEntityOperStatus ::= TEXTUAL-CONVENTION 552 STATUS current 553 DESCRIPTION 554 "The operational status of the wwwEntity. 'down' 555 indicates that the wwwEntity is not available. 556 'running' indicates that the wwwEntity is operational 557 and available. 'halted' indicates that the wwwEntity 558 is operational but not available. 'congested' 559 indicates that the wwwEntity is operational but no 560 additional inbound associations can be accommodated. 561 'restarting' indicates that the wwwEntity is currently 562 unavailable but is in the process of restarting and 563 will be available soon." 564 SYNTAX INTEGER { 565 down(1), 566 running(2), 567 halted(3), 568 congested(4), 569 restarting(5) 570 } 572 WwwDocName ::= TEXTUAL-CONVENTION 573 STATUS current 574 DESCRIPTION 575 "The server relative name of a document. If the URL were 576 http://www.x.org/standards/search/search.cgi?string=test 577 then the value of this textual convention would resolve 578 to '/standards/search/search.cgi'." 579 SYNTAX DisplayString 581 WwwDocSort ::= TEXTUAL-CONVENTION 582 STATUS current 583 DESCRIPTION 584 "A data type defining the sort oder of document statistics. 586 The value 'accesses' means that every new created bucket 587 is sorted in descending order according to the number of 588 document access attempts. 590 The value 'bytes' means that every new created bucket 591 is sorted in descending order according to the number of 592 bytes transfered in response to document accesses." 593 SYNTAX INTEGER { accesses(1), bytes(2) } 595 -- The WWW Entity Group 596 -- 597 -- The WWW entity group contains information about the WWW entities 598 -- known by the SNMP protocol entity. 600 wwwEntity OBJECT IDENTIFIER ::= { wwwMIBObjects 1 } 602 wwwEntityTable OBJECT-TYPE 603 SYNTAX SEQUENCE OF WwwEntityEntry 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "The table of the entities present on the system." 608 ::= { wwwEntity 1 } 610 wwwEntityEntry OBJECT-TYPE 611 SYNTAX WwwEntityEntry 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "Details of a particular entity which can be a 616 Server, a Client, a Proxy or a Caching-Proxy." 617 INDEX { wwwEntityIndex } 618 ::= { wwwEntityTable 1 } 620 WwwEntityEntry ::= SEQUENCE { 621 wwwEntityIndex Unsigned32, 622 wwwEntityDescription DisplayString, 623 wwwEntityContact DisplayString, 624 wwwEntityProtocol OBJECT IDENTIFIER, 625 wwwEntityName DisplayString, 626 wwwEntityType WwwEntityType, 627 wwwEntityUptime TimeStamp, 628 wwwEntityOperStatus WwwEntityOperStatus, 629 wwwEntityLastChange TimeStamp 630 } 632 wwwEntityIndex OBJECT-TYPE 633 SYNTAX Unsigned32 (1..'ffffffff'h) 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "An integer used for indexing purposes. Generally 638 monotonically increasing from 1 as new entities 639 are initialized. 641 The value for each entity must remain constant 642 from one re-initialization of the network management 643 agent to the next re-initialization." 644 ::= { wwwEntityEntry 1 } 646 wwwEntityDescription OBJECT-TYPE 647 SYNTAX DisplayString 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "Textual description of the entity. This shall include 652 at least the vendor and version number of the application. 653 In a minimal case, this might be the Product Token (see RFC 654 2086) for the application." 655 ::= { wwwEntityEntry 2 } 657 wwwEntityContact OBJECT-TYPE 658 SYNTAX DisplayString 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "The textual identification of the contact person 663 for this entity, together with information on how 664 to contact this person. For instance, this might 665 be 'webmaster@domain.name'." 666 ::= { wwwEntityEntry 3 } 668 wwwEntityProtocol OBJECT-TYPE 669 SYNTAX OBJECT IDENTIFIER 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "An identification of the primary protocol in use by this 674 entity. For Internet applications, the IANA maintains 675 a registry of the OIDs which correspond to well-known 676 applications. If the application protocol is not listed 677 in the registry, an OID value of the form {applTCPProtoID 678 port} or {applUDProtoID port} are used for TCP-based and 679 UDP-based protocols, respectively. In either case 'port' 680 corresponds to the primary port number being used by the 681 protocol." 682 ::= { wwwEntityEntry 4 } 684 wwwEntityName OBJECT-TYPE 685 SYNTAX DisplayString 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION 689 "The fully qualified domain name by which this entity is 690 known. This may be different than applName since that 691 value is only a textual name for the application." 692 ::= { wwwEntityEntry 5 } 694 wwwEntityType OBJECT-TYPE 695 SYNTAX WwwEntityType 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "Identification of the role of the entity." 700 ::= { wwwEntityEntry 6 } 702 wwwEntityUptime OBJECT-TYPE 703 SYNTAX TimeStamp 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "The value of sysUpTime at the time the wwwEntity 708 was last initialized. If the application was 709 last initialized prior to the last initialization of the 710 network management subsystem, then this object contains 711 a zero value." 712 ::= { wwwEntityEntry 7 } 714 wwwEntityOperStatus OBJECT-TYPE 715 SYNTAX WwwEntityOperStatus 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "Indicates the operational status of the wwwEntity." 720 ::= { wwwEntityEntry 8 } 722 wwwEntityLastChange OBJECT-TYPE 723 SYNTAX TimeStamp 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "The value of wwwEntityUpTime at the time the wwwEntity 728 entered its current operational state. If 729 the current state was entered prior to the last 730 initialization of the local network management subsystem, 731 then this object contains a zero value." 732 ::= { wwwEntityEntry 9 } 734 -- The WWW Service Statistics Group 735 -- 736 -- The WWW statistics group contains information concerning the 737 -- requests and responses send or received by WWW entities. 739 wwwServiceStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 2 } 741 wwwSummaryTable OBJECT-TYPE 742 SYNTAX SEQUENCE OF WwwSummaryEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "The table providing overview statistics for the 747 entities on this system." 748 ::= { wwwServiceStatistics 1 } 750 wwwSummaryEntry OBJECT-TYPE 751 SYNTAX WwwSummaryEntry 752 MAX-ACCESS not-accessible 753 STATUS current 754 DESCRIPTION 755 "Overview statistics for an individual entity." 756 INDEX { wwwEntityIndex } 757 ::= { wwwSummaryTable 1 } 759 WwwSummaryEntry ::= SEQUENCE { 760 wwwSummaryInRequests Counter32, 761 wwwSummaryOutRequests Counter32, 762 wwwSummaryInResponses Counter32, 763 wwwSummaryOutResponses Counter32, 764 wwwSummaryInBytes Counter32, 765 wwwSummaryOutBytes Counter32 766 } 768 wwwSummaryInRequests OBJECT-TYPE 769 SYNTAX Counter32 770 MAX-ACCESS read-only 771 STATUS current 772 DESCRIPTION 773 "The number of requests successfully received by and processed 774 by this entity." 775 ::= { wwwSummaryEntry 1 } 777 wwwSummaryOutRequests OBJECT-TYPE 778 SYNTAX Counter32 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "The number of requests generated by this entity." 783 ::= { wwwSummaryEntry 2 } 785 wwwSummaryInResponses OBJECT-TYPE 786 SYNTAX Counter32 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "The number of responses successfully received and processed 791 by this entity." 792 ::= { wwwSummaryEntry 3 } 794 wwwSummaryOutResponses OBJECT-TYPE 795 SYNTAX Counter32 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "The number of responses generated by this entity." 800 ::= { wwwSummaryEntry 4 } 802 wwwSummaryInBytes OBJECT-TYPE 803 SYNTAX Counter32 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "The number of content bytes received by this entity." 808 ::= { wwwSummaryEntry 5 } 810 wwwSummaryOutBytes OBJECT-TYPE 811 SYNTAX Counter32 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "The number of content bytes generated by this entity." 816 ::= { wwwSummaryEntry 6 } 818 -- The WWW request tables contain detailed information about 819 -- requests send or received by WWW entities. 821 wwwRequestInTable OBJECT-TYPE 822 SYNTAX SEQUENCE OF WwwRequestInEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "The table providing detailed request statistics for the 827 entities on this system." 828 ::= { wwwServiceStatistics 2 } 830 wwwRequestInEntry OBJECT-TYPE 831 SYNTAX WwwRequestInEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "Request statistics for an individual entity." 836 INDEX { wwwEntityIndex, wwwRequestInIndex } 837 ::= { wwwRequestInTable 1 } 839 WwwRequestInEntry ::= SEQUENCE { 840 wwwRequestInIndex WwwRequestType, 841 wwwRequestInCount Counter32, 842 wwwRequestInBytes Counter32, 843 wwwRequestInLastTime TimeStamp 844 } 846 wwwRequestInIndex OBJECT-TYPE 847 SYNTAX WwwRequestType 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "The particular request type the statistics apply to." 852 ::= { wwwRequestInEntry 1 } 854 wwwRequestInCount OBJECT-TYPE 855 SYNTAX Counter32 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "The number of requests of this type received by 860 this entity." 861 ::= { wwwRequestInEntry 2 } 863 wwwRequestInBytes OBJECT-TYPE 864 SYNTAX Counter32 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "The number of content bytes per request type 869 received by this entity." 870 ::= { wwwRequestInEntry 3 } 872 wwwRequestInLastTime OBJECT-TYPE 873 SYNTAX TimeStamp 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "The value of sysUpTime when the last byte of the last 878 complete request of this type was received by this 879 entity." 880 ::= { wwwRequestInEntry 4 } 882 wwwRequestOutTable OBJECT-TYPE 883 SYNTAX SEQUENCE OF WwwRequestOutEntry 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "The table providing detailed request statistics for the 888 entities on this system." 889 ::= { wwwServiceStatistics 3 } 891 wwwRequestOutEntry OBJECT-TYPE 892 SYNTAX WwwRequestOutEntry 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "Request statistics for an individual entity." 897 INDEX { wwwEntityIndex, wwwRequestOutIndex } 898 ::= { wwwRequestOutTable 1 } 900 WwwRequestOutEntry ::= SEQUENCE { 901 wwwRequestOutIndex WwwRequestType, 902 wwwRequestOutCount Counter32, 903 wwwRequestOutBytes Counter32, 904 wwwRequestOutLastTime TimeStamp 905 } 907 wwwRequestOutIndex OBJECT-TYPE 908 SYNTAX WwwRequestType 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "The particular request type the statistics apply to." 913 ::= { wwwRequestOutEntry 1 } 915 wwwRequestOutCount OBJECT-TYPE 916 SYNTAX Counter32 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The number of requests of this type generated by this 921 entity." 922 ::= { wwwRequestOutEntry 2 } 924 wwwRequestOutBytes OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "The number of content bytes per response type 930 generated by this entity." 931 ::= { wwwRequestOutEntry 3 } 933 wwwRequestOutLastTime OBJECT-TYPE 934 SYNTAX TimeStamp 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "The value of sysUpTime when the first byte of the 939 last request of this type was send by this entity." 940 ::= { wwwRequestOutEntry 4 } 942 -- The WWW response tables contain detailed information about 943 -- responses send or received by WWW entities. 945 wwwResponseInTable OBJECT-TYPE 946 SYNTAX SEQUENCE OF WwwResponseInEntry 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "The table providing detailed response statistics for the 951 entities on this system." 952 ::= { wwwServiceStatistics 4 } 954 wwwResponseInEntry OBJECT-TYPE 955 SYNTAX WwwResponseInEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "Response statistics for an individual entity." 960 INDEX { wwwEntityIndex, wwwResponseInIndex } 961 ::= { wwwResponseInTable 1 } 963 WwwResponseInEntry ::= SEQUENCE { 964 wwwResponseInIndex WwwResponseType, 965 wwwResponseInCount Counter32, 966 wwwResponseInBytes Counter32, 967 wwwResponseInLastTime TimeStamp 968 } 970 wwwResponseInIndex OBJECT-TYPE 971 SYNTAX WwwResponseType 972 MAX-ACCESS not-accessible 973 STATUS current 974 DESCRIPTION 975 "The particular response type the statistics apply to." 976 ::= { wwwResponseInEntry 1 } 978 wwwResponseInCount OBJECT-TYPE 979 SYNTAX Counter32 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "The number of responses of this type received by this 984 entity." 985 ::= { wwwResponseInEntry 2 } 987 wwwResponseInBytes OBJECT-TYPE 988 SYNTAX Counter32 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The number of content bytes per response type 993 received by this entity." 994 ::= { wwwResponseInEntry 3 } 996 wwwResponseInLastTime OBJECT-TYPE 997 SYNTAX TimeStamp 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The value of sysUpTime when the last byte of the last 1002 complete response of this type was received by this 1003 entity." 1004 ::= { wwwResponseInEntry 4 } 1006 wwwResponseOutTable OBJECT-TYPE 1007 SYNTAX SEQUENCE OF WwwResponseOutEntry 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "The table providing detailed response statistics for the 1012 entities on this system." 1013 ::= { wwwServiceStatistics 5 } 1015 wwwResponseOutEntry OBJECT-TYPE 1016 SYNTAX WwwResponseOutEntry 1017 MAX-ACCESS not-accessible 1018 STATUS current 1019 DESCRIPTION 1020 "Response statistics for an individual entity." 1021 INDEX { wwwEntityIndex, wwwResponseOutIndex } 1022 ::= { wwwResponseOutTable 1 } 1024 WwwResponseOutEntry ::= SEQUENCE { 1025 wwwResponseOutIndex WwwResponseType, 1026 wwwResponseOutCount Counter32, 1027 wwwResponseOutBytes Counter32, 1028 wwwResponseOutLastTime TimeStamp 1029 } 1031 wwwResponseOutIndex OBJECT-TYPE 1032 SYNTAX WwwResponseType 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "The particular response type the statistics apply to." 1037 ::= { wwwResponseOutEntry 1 } 1039 wwwResponseOutCount OBJECT-TYPE 1040 SYNTAX Counter32 1041 MAX-ACCESS read-only 1042 STATUS current 1043 DESCRIPTION 1044 "The number of responses of this type generated by this 1045 entity." 1046 ::= { wwwResponseOutEntry 2 } 1048 wwwResponseOutBytes OBJECT-TYPE 1049 SYNTAX Counter32 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "The number of content bytes per response type 1054 generated by this entity." 1055 ::= { wwwResponseOutEntry 3 } 1057 wwwResponseOutLastTime OBJECT-TYPE 1058 SYNTAX TimeStamp 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The value of sysUpTime when the first byte of the 1063 last response of this type was sent by this entity." 1064 ::= { wwwResponseOutEntry 4 } 1066 -- The WWW Document Statistics Group 1067 -- 1068 -- The WWW document statistics group contains statistics about 1069 -- document read attempts. 1071 wwwDocumentStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 3 } 1073 wwwDocCtrlTable OBJECT-TYPE 1074 SYNTAX SEQUENCE OF WwwDocCtrlEntry 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "A table which controls the how the MIB implementation 1079 collects and maintains document statistics." 1080 ::= { wwwDocumentStatistics 1 } 1082 wwwDocCtrlEntry OBJECT-TYPE 1083 SYNTAX WwwDocCtrlEntry 1084 MAX-ACCESS not-accessible 1085 STATUS current 1086 DESCRIPTION 1087 "An entry with which allows to configure the 1088 wwwDocLastNTable, the wwwDocBucketTable, 1089 and the wwwBucketTopNDocTable." 1090 INDEX { wwwEntityIndex } 1091 ::= { wwwDocCtrlTable 1 } 1093 WwwDocCtrlEntry ::= SEQUENCE { 1094 wwwDocCtrlLastNSize Unsigned32, 1095 wwwDocCtrlLastNStatus INTEGER, 1096 wwwDocCtrlBuckets Integer32, 1097 wwwDocCtrlBucketSize Integer32, 1098 wwwDocCtrlBucketSort WwwDocSort, 1099 wwwDocCtrlBucketTimeInterval TimeInterval 1100 } 1102 wwwDocCtrlLastNSize OBJECT-TYPE 1103 SYNTAX Unsigned32 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 "The maximum number of entries in the wwwDocLastNTable." 1108 DEFVAL { 25 } 1109 ::= { wwwDocCtrlEntry 1 } 1111 wwwDocCtrlLastNStatus OBJECT-TYPE 1112 SYNTAX INTEGER { enabled(1), disabled(2) } 1113 MAX-ACCESS read-write 1114 STATUS current 1115 DESCRIPTION 1116 "Indicates whether the wwwDocLastNTable is currently 1117 updated by the agent or not. This object allows a 1118 manager to suspend the update process in order to 1119 read it in a consistent state." 1120 DEFVAL { enabled } 1121 ::= { wwwDocCtrlEntry 2 } 1123 wwwDocCtrlBuckets OBJECT-TYPE 1124 SYNTAX Integer32 (0..2147483647) 1125 MAX-ACCESS read-write 1126 STATUS current 1127 DESCRIPTION 1128 "The maximum number of buckets in the associated 1129 'wwwDocBucketTopNTable' before the oldest bucket 1130 is deleted." 1131 DEFVAL { 2 } 1132 ::= { wwwDocCtrlEntry 3 } 1134 wwwDocCtrlBucketSize OBJECT-TYPE 1135 SYNTAX Integer32 (0..2147483647) 1136 MAX-ACCESS read-write 1137 STATUS current 1138 DESCRIPTION 1139 "The maximum number of entries in the associated 1140 'wwwDocBucketTopNTable' per bucket." 1141 DEFVAL { 25 } 1142 ::= { wwwDocCtrlEntry 4 } 1144 wwwDocCtrlBucketSort OBJECT-TYPE 1145 SYNTAX WwwDocSort 1146 MAX-ACCESS read-write 1147 STATUS current 1148 DESCRIPTION 1149 "The sort order of new the buckets. The value is only 1150 important at the moment when a new bucket is 1151 created. Changing this value does not affect the order 1152 in any existing buckets." 1153 DEFVAL { accesses } 1154 ::= { wwwDocCtrlEntry 5 } 1156 wwwDocCtrlBucketTimeInterval OBJECT-TYPE 1157 SYNTAX TimeInterval 1158 MAX-ACCESS read-write 1159 STATUS current 1160 DESCRIPTION 1161 "The time interval after which a new bucket is created." 1162 DEFVAL { 90000 } -- 15 minutes (resolution .01 s) 1163 ::= { wwwDocCtrlEntry 6 } 1165 wwwDocLastNTable OBJECT-TYPE 1166 SYNTAX SEQUENCE OF WwwDocLastNEntry 1167 MAX-ACCESS not-accessible 1168 STATUS current 1169 DESCRIPTION 1170 "The table which logs the last N read attempts." 1171 ::= { wwwDocumentStatistics 2 } 1173 wwwDocLastNEntry OBJECT-TYPE 1174 SYNTAX WwwDocLastNEntry 1175 MAX-ACCESS not-accessible 1176 STATUS current 1177 DESCRIPTION 1178 "An entry associated which logs the last N read 1179 attempts of an entity." 1180 INDEX { wwwEntityIndex, wwwDocLastNIndex } 1181 ::= { wwwDocLastNTable 1 } 1183 WwwDocLastNEntry ::= SEQUENCE { 1184 wwwDocLastNIndex Unsigned32, 1185 wwwDocLastNName WwwDocName, 1186 wwwDocLastNTimeStamp DateAndTime, 1187 wwwDocLastNRequestType WwwRequestType, 1188 wwwDocLastNResponseType WwwResponseType, 1189 wwwDocLastNBytes Unsigned32 1190 } 1192 wwwDocLastNIndex OBJECT-TYPE 1193 SYNTAX Unsigned32 1194 MAX-ACCESS not-accessible 1195 STATUS current 1196 DESCRIPTION 1197 "An arbitrary monotonically increasing integer number 1198 used for indexing the wwwDocLastNTable. The value 1199 starts from 1 and represents the order in which the 1200 documents were accessed." 1201 ::= { wwwDocLastNEntry 1 } 1203 wwwDocLastNName OBJECT-TYPE 1204 SYNTAX WwwDocName 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "The name of the document which was attempted to access." 1209 ::= { wwwDocLastNEntry 2 } 1211 wwwDocLastNTimeStamp OBJECT-TYPE 1212 SYNTAX DateAndTime 1213 MAX-ACCESS read-only 1214 STATUS current 1215 DESCRIPTION 1216 "The date and time that this document was attempted 1217 to access." 1218 ::= { wwwDocLastNEntry 3 } 1220 wwwDocLastNRequestType OBJECT-TYPE 1221 SYNTAX WwwRequestType 1222 MAX-ACCESS read-only 1223 STATUS current 1224 DESCRIPTION 1225 "The protocol request type which was received by the 1226 server when this document access was attempted." 1227 ::= { wwwDocLastNEntry 4 } 1229 wwwDocLastNResponseType OBJECT-TYPE 1230 SYNTAX WwwResponseType 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "The protocol response type which was sent to the client 1235 as a result of this attempt to access a document." 1236 ::= { wwwDocLastNEntry 5 } 1238 wwwDocLastNBytes OBJECT-TYPE 1239 SYNTAX Unsigned32 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "The number of bytes that were returned as a result of 1244 this attempt to access a document." 1245 ::= { wwwDocLastNEntry 6 } 1247 wwwDocBucketTable OBJECT-TYPE 1248 SYNTAX SEQUENCE OF WwwDocBucketEntry 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "The table providing a per bucket administrative and summary 1253 information of the 'wwwDocBucketTopNTable'." 1254 ::= { wwwDocumentStatistics 3 } 1256 wwwDocBucketEntry OBJECT-TYPE 1257 SYNTAX WwwDocBucketEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "An entry associated with a particular mapping in the 1262 wwwDocBucketTable." 1263 INDEX { wwwEntityIndex, wwwDocBucketIndex } 1264 ::= { wwwDocBucketTable 1 } 1266 WwwDocBucketEntry ::= SEQUENCE { 1267 wwwDocBucketIndex Integer32, 1268 wwwDocBucketTimeStamp TimeStamp, 1269 wwwDocBucketAccesses Unsigned32, 1270 wwwDocBucketDocuments Unsigned32, 1271 wwwDocBucketBytes Unsigned32, 1272 wwwDocBucketSort WwwDocSort 1273 } 1275 wwwDocBucketIndex OBJECT-TYPE 1276 SYNTAX Integer32 (1..2147483647) 1277 MAX-ACCESS not-accessible 1278 STATUS current 1279 DESCRIPTION 1280 "An arbitrary monotonically increasing integer number 1281 used for indexing the wwwDocBucketTable. The index 1282 number wraps to 1 whenever the maximum value is reached." 1283 ::= { wwwDocBucketEntry 1 } 1285 wwwDocBucketTimeStamp OBJECT-TYPE 1286 SYNTAX TimeStamp 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "The time when the bucket was created." 1291 ::= { wwwDocBucketEntry 2 } 1293 wwwDocBucketAccesses OBJECT-TYPE 1294 SYNTAX Unsigned32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "The total amount of access attempts counted in this bucket." 1300 ::= { wwwDocBucketEntry 3 } 1302 wwwDocBucketDocuments OBJECT-TYPE 1303 SYNTAX Unsigned32 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "The total amount of different documents which 1308 were attempted to read for this bucket." 1309 ::= { wwwDocBucketEntry 4 } 1311 wwwDocBucketBytes OBJECT-TYPE 1312 SYNTAX Unsigned32 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "The total amount of bytes which were transfered 1317 for this bucket." 1318 ::= { wwwDocBucketEntry 5 } 1320 wwwDocBucketSort OBJECT-TYPE 1321 SYNTAX WwwDocSort 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "The sort order with which this bucket was created." 1326 ::= { wwwDocBucketEntry 6 } 1328 wwwDocBucketTopNTable OBJECT-TYPE 1329 SYNTAX SEQUENCE OF WwwDocBucketTopNEntry 1330 MAX-ACCESS not-accessible 1331 STATUS current 1332 DESCRIPTION 1333 "The table of documents accessible from any entity configured 1334 in the wwwEntityTable. The agent minimally adds entries to 1335 this table to correspond with documents that have been 1336 accessed. It may choose to add entries for documents which 1337 have not yet been accessed as well." 1338 ::= { wwwDocumentStatistics 4 } 1340 wwwDocBucketTopNEntry OBJECT-TYPE 1341 SYNTAX WwwDocBucketTopNEntry 1342 MAX-ACCESS not-accessible 1343 STATUS current 1344 DESCRIPTION 1345 "An entry associated with a particular mapping in the 1346 wwwDocTable." 1347 INDEX { wwwEntityIndex, wwwDocBucketIndex, wwwDocBucketTopNIndex } 1348 ::= { wwwDocBucketTopNTable 1 } 1350 WwwDocBucketTopNEntry ::= SEQUENCE { 1351 wwwDocBucketTopNIndex Integer32, 1352 wwwDocBucketTopNName WwwDocName, 1353 wwwDocBucketTopNAccesses Unsigned32, 1354 wwwDocBucketTopNBytes Unsigned32, 1355 wwwDocBucketTopNLastResponseType WwwResponseType 1356 } 1358 wwwDocBucketTopNIndex OBJECT-TYPE 1359 SYNTAX Integer32 (1..2147483647) 1360 MAX-ACCESS not-accessible 1361 STATUS current 1362 DESCRIPTION 1363 "An arbitrary monotonically increasing integer number 1364 used for indexing the wwwDocBucketTopNTable. The index 1365 is inversely correlated to the sorting order of the 1366 table. For example, if the table is sorted according 1367 to document accesses, than the document with the highes 1368 access rate will get the index value 1." 1369 ::= { wwwDocBucketTopNEntry 1 } 1371 wwwDocBucketTopNName OBJECT-TYPE 1372 SYNTAX WwwDocName 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "The name of the document which was attempted to access." 1377 ::= { wwwDocBucketTopNEntry 2 } 1379 wwwDocBucketTopNAccesses OBJECT-TYPE 1380 SYNTAX Unsigned32 1381 MAX-ACCESS read-only 1382 STATUS current 1383 DESCRIPTION 1384 "The total amount of access attempts for this document." 1385 ::= { wwwDocBucketTopNEntry 3 } 1387 wwwDocBucketTopNBytes OBJECT-TYPE 1388 SYNTAX Unsigned32 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "The number of bytes that were returned as a result of 1393 this attempt to access a document." 1394 ::= { wwwDocBucketTopNEntry 4 } 1396 wwwDocBucketTopNLastResponseType OBJECT-TYPE 1397 SYNTAX WwwResponseType 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "The protocol response type which was sent to the client 1402 as a result of this attempt to access a document." 1403 ::= { wwwDocBucketTopNEntry 5 } 1405 -- Conformance and Compliance Definitions 1406 -- 1408 wwwMIBEntityGroup OBJECT-GROUP 1409 OBJECTS { 1410 wwwEntityDescription, 1411 wwwEntityContact, 1412 wwwEntityProtocol, 1413 wwwEntityName, 1414 wwwEntityType, 1415 wwwEntityUptime, 1416 wwwEntityOperStatus, 1417 wwwEntityLastChange 1418 } 1419 STATUS current 1420 DESCRIPTION 1421 "" 1422 ::= { wwwMIBGroups 1 } 1424 wwwMIBSummaryGroup OBJECT-GROUP 1425 OBJECTS { 1426 wwwSummaryInRequests, 1427 wwwSummaryOutRequests, 1428 wwwSummaryInResponses, 1429 wwwSummaryOutResponses, 1430 wwwSummaryInBytes, 1431 wwwSummaryOutBytes 1432 } 1433 STATUS current 1434 DESCRIPTION 1435 "" 1436 ::= { wwwMIBGroups 2 } 1438 wwwMIBRequestInGroup OBJECT-GROUP 1439 OBJECTS { 1440 wwwRequestInCount, 1441 wwwRequestInBytes, 1442 wwwRequestInLastTime 1443 } 1444 STATUS current 1445 DESCRIPTION 1446 "" 1447 ::= { wwwMIBGroups 3 } 1449 wwwMIBRequestOutGroup OBJECT-GROUP 1450 OBJECTS { 1451 wwwRequestOutCount, 1452 wwwRequestOutBytes, 1453 wwwRequestOutLastTime 1454 } 1455 STATUS current 1456 DESCRIPTION 1457 "" 1458 ::= { wwwMIBGroups 4 } 1460 wwwMIBResponseInGroup OBJECT-GROUP 1461 OBJECTS { 1462 wwwResponseInCount, 1463 wwwResponseInBytes, 1464 wwwResponseInLastTime 1465 } 1466 STATUS current 1467 DESCRIPTION 1468 "" 1469 ::= { wwwMIBGroups 5 } 1471 wwwMIBResponseOutGroup OBJECT-GROUP 1472 OBJECTS { 1473 wwwResponseOutCount, 1474 wwwResponseOutBytes, 1475 wwwResponseOutLastTime 1476 } 1477 STATUS current 1478 DESCRIPTION 1479 "" 1480 ::= { wwwMIBGroups 6 } 1482 wwwMIBDocumentGroup OBJECT-GROUP 1483 OBJECTS { 1484 wwwDocCtrlLastNSize, 1485 wwwDocCtrlLastNStatus, 1486 wwwDocCtrlBuckets, 1487 wwwDocCtrlBucketSize, 1488 wwwDocCtrlBucketSort, 1489 wwwDocCtrlBucketTimeInterval, 1490 wwwDocLastNName, 1491 wwwDocLastNTimeStamp, 1492 wwwDocLastNRequestType, 1493 wwwDocLastNResponseType, 1494 wwwDocLastNBytes, 1495 wwwDocBucketTimeStamp, 1496 wwwDocBucketAccesses, 1497 wwwDocBucketDocuments, 1498 wwwDocBucketBytes, 1499 wwwDocBucketSort, 1500 wwwDocBucketTopNName, 1501 wwwDocBucketTopNAccesses, 1502 wwwDocBucketTopNBytes, 1503 wwwDocBucketTopNLastResponseType 1504 } 1505 STATUS current 1506 DESCRIPTION 1507 "" 1508 ::= { wwwMIBGroups 7 } 1510 wwwMinimalCompliance MODULE-COMPLIANCE 1511 STATUS current 1512 DESCRIPTION 1513 "The compliance statement for SNMP entities which implement 1514 the minimal subset of the WWW-MIB. Implementors might 1515 choose this subset for high-performance server where full 1516 compliance might be to expensive." 1517 MODULE -- this module 1518 MANDATORY-GROUPS { 1519 wwwMIBEntityGroup, 1520 wwwMIBSummaryGroup 1521 } 1522 ::= { wwwMIBCompliances 1 } 1524 wwwFullCompliance MODULE-COMPLIANCE 1525 STATUS current 1526 DESCRIPTION 1527 "The compliance statement for SNMP entities which implement 1528 the full WWW-MIB." 1529 MODULE -- this module 1530 MANDATORY-GROUPS { 1531 wwwMIBEntityGroup, 1532 wwwMIBSummaryGroup, 1533 wwwMIBRequestInGroup, 1534 wwwMIBRequestOutGroup, 1535 wwwMIBResponseInGroup, 1536 wwwMIBResponseOutGroup, 1537 wwwMIBDocumentGroup 1538 } 1539 ::= { wwwMIBCompliances 2 } 1541 END 1543 7. References 1545 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1546 Waldbusser, "Structure of Management Information for Version 2 of 1547 the Simple Network Management Protocol (SNMPv2)", RFC1902, SNMP 1548 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1549 International Network Services, January 1996. 1551 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1552 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1553 RFC 1213, Hughes LAN Systems, Performance Systems International, 1554 March 1991. 1556 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1557 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1558 International, Performance Systems International, MIT Laboratory 1559 for Computer Science, May 1990. 1561 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1562 Waldbusser, "Protocol Operations for Version 2 of the Simple 1563 Network Management Protocol (SNMPv2)", RFC1905, SNMP Research,Inc., 1564 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1565 Network Services, January 1996. 1567 [5] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource 1568 Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of 1569 Minnesota, December 1994. 1571 [6] T. Berners-Lee, "Universal Resource Identifiers in WWW", RFC 1630, 1572 CERN, June 1994. 1574 [7] D. Crocker, "STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT 1575 MESSAGES", RFC 822, University of Delaware, August 1982. 1577 [8] C. Kalbfleisch, "Applicability of Standards Track MIBs to 1578 Management of World Wide Web Servers", RFC 2039, OnRamp 1579 Technologies, November 1996. 1581 [9] Krupczak, C., and J. Saperia, "Definitions of System-Level Managed 1582 Objects for Applications", draft-ietf-applmib-sysapplmib-08.txt, 1583 Empire Technologies, BGS Systems, March 1997. 1585 [10] Kalbfleisch, C., Krupczak, C., Preshun, R., and J. Saperia, 1586 "Application Management MIB", draft-ietf-applmib-mib-02.txt, Verio, 1587 Empire Technologies, BMC Software, BGS Systems, March 1997. 1589 [11] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext Transfer 1590 Protocol -- HTTP/1.0", RFC 1945, MIT/LCS, UC Irvine, MIT/LCS, May 1591 1996. 1593 [12] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners- 1594 Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, UC 1595 Irvine, DEC, DEC, MIT/LCS, January 1997. 1597 [13] Postel, J., and J.K. Reynolds, "File Transfer Protocol (FTP)", STD 1598 9, RFC 959, USC/ISI, October 1985. 1600 [14] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A 1601 Proposed Standard for the Stream-Based Transmission of News", RFC 1602 977, UC San Diego & UC Berkeley, February 1986. 1604 [15] Horton, M., and R. Adams, "Standard for interchange of USENET 1605 messages", RFC 1036, AT&T Bell Laboratories, Center for Seismic 1606 Studies, December 1987. 1608 [16] Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC 1514, 1609 Network Innovations, Intel Corporation, Carnegie Mellon University, 1610 September 1993. 1612 [17] Kille, S., and N. Freed, "Network Services Monitoring MIB", RFC 1613 1565, ISODE Consortium, Innosoft, January 1994. 1615 [18] Krupczak, C., and S. Waldbusser, "Applicability of Host Resources 1616 MIB to Application Management", Empire Technologies, Inc., 1617 International Network Services, October 1995. 1619 [19] Kille, S., and N. Freed, "Mail Monitoring MIB", RFC 1566, ISODE 1620 Consortium, Innosoft, January 1994. 1622 [20] Mansfield, G., and S. Kille, "X.500 Directory Monitoring MIB", RFC 1623 1567, AIC Systems Laboratory, ISODE Consortium, January 1994 1625 [21] S. Waldbusser, "Remote Network Monitoring Management Information 1626 Base Version 2 using SMIv2", RFC 2021, INS, January, 1997. 1628 8. Acknowledgments 1630 This document was produced by the Application MIB working group and 1631 the members of the http-mib@onramp.net mailing list. 1633 The authors gratefully acknowledges the comments of the following 1634 individuals: 1636 Randy Preshun 1637 John Saperia 1638 Cheryl Krupczak 1640 9. Security Considerations 1642 The MIB objects defined in the memo might disclose information that 1643 should be protected. In particular, the document statistics group 1644 contains traffic information, which includes the names of documents 1645 that were a target of a protocol operation. It is therefore adviced 1646 to use SNMP access control and SNMP security mechanism (where 1647 available) in order to protect this information in sensitive 1648 environments. 1650 The service statistics are less sensitive, because they do not 1651 contain details about the target of individual requests/responses. 1652 However, it is suggested that sites configure MIB views so that a 1653 user of this MIB can only see the portion of the statistics that 1654 belong to the WWW entities managed by that user. 1656 10. Document Transfer Protocol Mappings 1658 This appendix describes how existing protocols such as HTTP [13,14] 1659 and FTP [15] can be mapped on the abstract Document Transfer Protocol 1660 (DTP) used within the definitions of the WWW MIB. Every mapping must 1661 define the identifier which is used to uniquely identify the transfer 1662 protocol. In addition, the mappings must define how requests and 1663 responses are identified and how the transferred byte stream is split 1664 into control and content bytes. 1666 10.1. The HyperText Transfer Protocol 1668 The HyperText Transfer Protocol (HTTP) [13,14] is an application- 1669 level protocol used to transfer hypermedia documents in a distributed 1670 networked environment. HTTP is based on the request/response paradigm 1671 and can be mapped on the abstract DTP easily. 1673 The HTTP protocol usually runs over TCP and uses the well-known TCP 1674 port 80. Therefore, the default value for the wwwEntityProtocol 1675 object is { applTCPProtoID 80 }. 1677 HTTP allows for both requests and responses an open-ended set of 1678 message types. The general messages syntax of HTTP is therefore used 1679 for the protocol mapping. The BNF specification of the general HTTP 1680 message syntax as defined in [12] is as follows: 1682 HTTP-message = start-line 1683 *message-header 1684 CRLF 1685 [ message-body ] 1687 start-line = Request-Line | Status-Line 1689 Request-Line = Method SP Request-URI SP HTTP-Version CRLF 1691 Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF 1693 Every HTTP-message where the start-line is a Request-Line is 1694 considered a request in the abstract DTP. Every HTTP-message where 1695 the start-line is a Status-Line is considered a response in the 1696 abstract DTP. The rest of the mappings are defined as follows: 1698 o The wwwRequestType corresponds to the method token in the 1699 Request-Line. 1701 o The wwwResponseType corresponds to the Status-Code in the 1702 Status-Line. 1704 o The control bytes of an HTTP-message are defined as the number 1705 of bytes in the start-line and the message headers. 1707 o The content bytes of an HTTP-message are the number of bytes in 1708 the message body. 1710 10.2. The File Transfer Protocol 1712 The File Transfer Protocol (FTP) [13] is an application-level 1713 protocol used to transfer files between hosts connected by the TCP/IP 1714 suite of protocols. FTP is based on a request/response paradigm and 1715 can be mapped on the abstract DTP as defined in this section. The FTP 1716 model as defined in [13] is depicted below. 1718 ------------- 1719 |+---------+| 1720 || User || -------- 1721 ||Interface|<--->| User | 1722 |+----|----+| -------- 1723 ---------- | | | 1724 |+------+| control connection |+----|----+| 1725 ||Server|<------------------->|| Client || 1726 || PI || Commands/Replies || PI || 1727 |+--|---+| |+----|----+| 1728 | | | | | | 1729 -------- |+--|---+| Data |+----|----+| -------- 1730 | File |<--->|Server|<------------------->|| Client |<--->| File | 1731 |System| || DTP || Connection || DTP || |System| 1732 -------- |+------+| |+---------+| -------- 1733 ---------- ------------- 1735 FTP uses two different connection types between a client and a server 1736 to transfer files. The control connection is persistent during a FTP 1737 session and used to exchange FTP commands and associated replies. The 1738 data connection is only available when bulk data has to be 1739 transferred. 1741 The FTP protocol usually runs over TCP and uses the well-known TCP 1742 port 21 to setup the control connection. Therefore, the default value 1743 for the wwwEntityProtocol object is { applTCPProtoID 21 }. 1745 Every FTP command is considered a request in the abstract DTP. Every 1746 FTP reply is considered a response in the abstract DTP. I should be 1747 noted that a single FTP command can result in multiple FTP replies 1748 (e.g. preliminary positive replies). The definition above maps 1749 multiple FTP replies into multiple DTP responses. The rest of the 1750 mappings are defined as follows: 1752 o The wwwRequestType corresponds to the FTP command token. 1754 o The wwwResponseType corresponds to the three-digit code which 1755 starts a reply. Multi-line replies with the same three-digit 1756 code are counted as a single DTP response. 1758 o The control bytes of a FTP transaction are all the bytes 1759 transferred over the control connection. 1761 o The content bytes of a FTP transaction are all the bytes 1762 transferred over the data connection. Note that content bytes 1763 can only be associated to FTP commands which cause a data 1764 transfer. FTP replies do not contain content bytes. 1766 11. Todo List 1768 This section will be removed when the document is complete because 1769 all items that are "to do" will have been done! 1771 o Check if we need additional objects or clarifications to handle 1772 proxies and caching proxies. 1774 o Check if the wwwDocLastNTable and the wwwDocBucketTopNTable can 1775 be combined while also solving the multiple manager problem. 1777 o Rework the reference section. Some references can be removed and 1778 other might need to be added. 1780 12. Authors' Address 1782 Carl W. Kalbfleisch 1783 Verio, Inc. 1784 1950 Stemmons Frwy 1785 2004 INFOMART 1786 Dallas, TX 75207 1787 USA Tel: (972) 238-8303 1788 cwk@verio.net Fax: (972) 238-0268 1790 Harrie Hazewinkel 1791 MUSIQ/DESIRE/CEO Program 1792 Institute for Space Applications 1793 Joint Research Centre of the E.C. 1794 TP. 950 1795 Ispra 21020 (VA) Italy Tel: +39+(0)332+789384 1796 harrie.hazewinkel@jrc.it Fax: +39+(0)332+785500 1798 Juergen Schoenwaelder 1799 Computer Science Department 1800 University of Twente 1801 P.O. Box 217, NL-7500 AE Enschede 1802 The Netherlands Tel: +31-53-489-3678 1803 schoenw@cs.utwente.nl Fax: +31-53-489-3247 1805 Table of Contents 1807 1 Abstract ..................................................... 2 1808 2 The SNMPv2 Network Management Framework ...................... 2 1809 2.1 Object Definitions ......................................... 2 1810 3 Terminology .................................................. 3 1811 4 Overview ..................................................... 4 1812 4.1 Purpose and Requirements ................................... 4 1813 4.2 Relationship to other Standards Efforts .................... 5 1814 4.3 WWW Entities ............................................... 5 1815 4.4 Document Transfer Protocol ................................. 6 1816 5 Structure of the MIB ......................................... 6 1817 5.1 Entity Group ............................................... 7 1818 5.2 Service Statistics Group ................................... 7 1819 5.3 Document Statistics Group .................................. 8 1820 6 Definitions .................................................. 9 1821 7 References ................................................... 34 1822 8 Acknowledgments .............................................. 36 1823 9 Security Considerations ...................................... 36 1824 10 Document Transfer Protocol Mappings ......................... 36 1825 10.1 The HyperText Transfer Protocol ........................... 37 1826 10.2 The File Transfer Protocol ................................ 38 1827 11 Todo List ................................................... 39 1828 12 Authors' Address ............................................ 39