idnits 2.17.1 draft-ietf-applmib-wwwmib-00.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-24) 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1419 has weird spacing: '...ponding entry...' -- 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 (December 1, 1996) is 10006 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? '1' on line 67 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT WWW MIB December 1, 1996 3 Definitions of Managed Objects for WWW Servers 5 7 Carl W. Kalbfleisch 8 OnRamp Technologies, Inc. 9 cwk@onramp.net 11 Harrie Hazewinkel 12 DESIRE / MUSIQ 13 Joint Research Centre of the E.C. 14 harrie.hazewinkel@jrc.it 16 Juergen Schoenwaelder 17 University of Twente 18 schoenw@cs.utwente.nl 20 December 1, 1996 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 26 areas, and its working groups. Note that other groups may also 27 distribute working documents as Internet-Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six 30 months and may be updated, replaced, or obsoleted by other 31 documents at any time. It is inappropriate to use Internet- 32 Drafts as reference material or to cite them other than as 33 ``work in progress.'' 35 To learn the current status of any Internet-Draft, please check 36 the ``1id-abstracts.txt'' listing contained in the Internet- 37 Drafts Shadow Directories on ftp.is.co.za (Africa), 38 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 39 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 41 Distribution of this document is unlimited. Please send comments 42 to the HTTP-MIB mailing list . Discussions of 43 the mailing list are archived at 44 General discussions about 45 application MIBs should take place on the Application MIB Working 46 Group, , mailing list. 48 1. Abstract 50 This memo defines an experimental portion of the Management 51 Information Base (MIB) for use with network management 52 protocols in the Internet Community. In particular it 53 describes a set of managed objects for WWW servers. These 54 objects include extensions to Network Services Monitoring 55 MIB, extensions to sysApplMIB, error reporting and document 56 storage information. Some portions of this information are 57 not yet defined and will be added to this document in future 58 revisions. These attributes are applicable to the HTTP 59 protocol of WWW but may also be applicable to other information 60 retrieval services like ftp, nntp, gopher and wais. 62 2. The SNMPv2 Network Management Framework 64 The SNMPv2 Network Management Framework consists of four major 65 components. They are: 67 o STD 17, RFC 1213 [1] defines MIB-II, the core set of managed 68 objects for the Internet suite of protocols. 70 o RFC 1902 Structure of Management Information for Version 2 of 71 the Simple Network Management Protocol (SNMPv2) 73 o RFC 1903 Textual Conventions for Version 2 of the Simple 74 Network Management Protocol (SNMPv2) 76 o RFC 1904 Conformance Statements for Version 2 of the Simple 77 Network Management Protocol (SNMPv2) 79 o RFC 1905 Protocol Operations for Version 2 of the Simple 80 Network Management Protocol (SNMPv2) 82 o RFC 1906 Transport Mappings for Version 2 of the Simple 83 Network Management Protocol (SNMPv2) 85 o RFC 1907 Management Information Base for Version 2 of the 86 Simple Network Management Protocol (SNMPv2) 88 o RFC 1908 Coexistence between Version 1 and Version 2 of the 89 Internet-standard Network Management Framework 91 The Framework permits new objects to be defined for the purpose of 92 experimentation and evaluation. 94 2.1. Object Definitions 96 Managed objects are accessed via a virtual information store, 97 termed the Management Information Base or MIB. Objects in the MIB 98 are defined using the subset of Abstract Syntax Notation One 99 (ASN.1) defined in the SMI [ref]. In particular, each object type is 100 named by an OBJECT IDENTIFIER, an administratively assigned name. 101 The object type together with an object instance serves to 102 uniquely identify a specific instantiation of the object. For 103 human convenience, we often use a textual string, termed the 104 object descriptor, to refer to the object type. 106 3. Notation 108 This notation [## .. ##] delineates editorial text. This 109 information will either be removed in the final document or 110 replaced with real text at those points. 112 4. A Note on Terminology 114 This section defines the terminology used throughout this draft. 116 The 'World Wide Web' (WWW) is the name of a world wide information 117 system which is based on the concept of documents that can be linked 118 together by embedding references to documents located at local or 119 remote locations. References to a document are made using Uniform 120 Resource Locators (URL) as defined in RFC 1738 [?]. 122 A 'WWW-site' is defined as a host in the Internet that embodies 123 the WWW. 125 A 'document' is defined like a coherent piece of information/data. 126 No assumptions are made about the content or type. 128 A 'Document Transport Protocol' (DTP) is defined as a generic name 129 for all protocols that allow to perform operations on 'documents' 130 stored on WWW-sites. 132 A 'Uniform Resource Locator' (URL) is defined as formatted string 133 representation for a 'document' available via the Internet. 134 The 'URL' maps onto a certain 'DTP' and 'WWW-site' of where and how 135 to retrieve a 'document'. 136 For the syntax and semantics of the string representation is 137 referred to rfc1630 [?] and rfc1738 [?] 139 A 'request' is defined as a protocol operation which is targeted to 140 a 'document' and invokes an action on the target document. The 141 'request type' specifies the action that should be performed and 142 a 'request' can have a document attached to it. 144 A 'response' is defined as a protocol operation which is returned as 145 a result of a previous (and associated) request. The 'response 146 status' indicates if the requested action was successful or if 147 errors occurred. A 'response' can have a document attached to it. 149 An 'application' is defined as one or more units of executable code 150 and other resources, installed on a single host system that a manager 151 may think of as a single object for management purposes. 153 A 'networked application' is defined as an application type which 154 is not neccesaryly installed an a single host, but makes use of an 155 underlying transport protocol in order to behave as a single object 156 in the eyes of an operator. 158 A 'server' is defined as the networked application invoking the DTP 159 operations. A 'server' provides access facilty to 'documents' and/or 160 storage facilty of 'documents'. The 'document' resides on locally 161 accessible disks or in applications processing the DTP operations. 163 A 'client' is defined as the networked application invoking the DTP 164 operations. A 'clients issues the 'requests' and interprets the 165 'responses'. 167 A 'proxy' is defined as a networked application acting both as 168 server and client for the purpose of making request for other 169 clients. 'Requests' and 'responses' are passed by the 'proxy' with 170 possible mapping between different DTP's. The 'proxy doesn't 171 change the 'document' transferred. 173 A 'caching proxy' is defined as a proxy with the capability of 174 locally storing 'responses' to associated 'requests' in order to 175 respond with the local stored 'response' to the associated 'request'. 177 An 'entity' is defined as a 'server', a 'client', a 'proxy' or ' a 178 'caching proxy' which can be accessed by an unique transport address. 180 5. Introduction 182 The World Wide Web (WWW) is a network of information, accessible 183 via a simple easy to use interface. The information is often 184 presented in HyperText and/or multi-media. The information is 185 provided by servers which are located all around the world and 186 are linked to each other via hyperlinks. 187 The protocol these servers listen to is the Hypertext Transfer 188 Protocol performing the actual transfer of the information. 189 The usability of the web depends largely on the performance of 190 these servers. WWW servers are typically monitored through log 191 files. This becomes a difficult task when a single organization is 192 responsible for a number of servers. Since many organizations 193 currently use the Internet Standard SNMP to manage their network 194 devices, it is desirable to treat these WWW servers as additional 195 devices within this framework. This will allow a single Network 196 Management Station (NMS) to automate the management of a number of 197 WWW servers as well as the entire enterprise. Defining a standard for 198 this purpose allows a single management application to manage a 199 number of servers from a variety of vendors. Additionally, a formal 200 definition of what has to be managed and how to manage it tends to 201 lead to integrated and improved performance and fault management. 203 6. WWW Entities 205 The focus of this MIB is the management of WWW entities. These 206 entities are servers, clients and proxies which communicate with 207 each other using the HyperText transfer Protocol (HTTP). This is a 208 stateless protocol based on the Client/ Server paradigm. Therefore, 209 this MIB includes WWW Server, client and proxy role of the WWW 210 entity. The following section describe what is meant by server, 211 client and proxy entities. 213 Due to the similarity of HTTP to other information retrieval 214 protocols, it is anticipated that this MIB may be directly useful to 215 the management of applications processing other types of protocols 216 such ftp, nntp, gopher and wais. An appendix is provided to describe 217 how such application of this MIB might be made to other protocols. 219 6.1. WWW Server 221 A WWW server is a proprietor of a general store of information. It 222 waits for a client to come with a request for information and then 223 returns the requested information to the client. 225 The coverage of this MIB is suitable for WWW server although certain 226 variables are not relevant in case the MIB is used for WWW server 227 management. In that case the not relevant objects should return the 228 zero-value. 230 6.2. WWW Client 232 A WWW client, or also called a browser, is a application which can 233 request information from server and present the returned information 234 in the appropriate format. Whenever, the client application cannot 235 display the proper format of the retrieved information helper 236 applications assist the WWW client with presenting the information. 238 The coverage of this MIB is primerly for WWW servers, but clients 239 can be managed by it as well. In case of managing the client certain 240 variables are not relevant which should than return the zero-value. 242 6.3. WWW Proxy 244 Proxies are used to provide transformations of information passed 245 between systems/ applications. The proxies are inside the chain of 246 the client and the server handling the request for the operator. 247 That server is not necesarrily an WWW server, but can also be an 248 other type of application providing information requested. Such an 249 application can be, for instance, a database which can be examined 250 with SQL. In this particular case the proxy transfers the 251 HTTP-request into SQL request and performs the other way around on 252 the SQL respond by transferring it into an HTTP-request. Another 253 way of using the proxy is to create some extra fire-wall whereby 254 the proxy takes care of security issues. Although, this is not a 255 real proxy. 257 To have useful management information about proxies the MIB 258 definition contains objects for outgoing and incoming of any 259 particular request or response. Derived information from these so 260 called low-level values are dependant on the use. For instance, if 261 request are transformed into database requests you can have 262 information on successful transformations. Whenever the proxy is 263 used inside the fire-wall you can see how many attempts of 264 breaking the fire-wall were made. This last one can mean there is 265 someone trying to break a way into your network. 267 6.4. WWW Cached Proxy 269 A special kind of proxies are the cached proxies. They are not 270 always requesting information from the server lying behind. The 271 cache contains already information made by earlier requests. The 272 cached proxy uses that information to return the appropriate 273 information without asking the real information provider. 275 The useful network management information is here to know how 276 many requests were already inside the cache of the proxy. This can 277 also be explained as the so called 'hits/miss'-ratio. Although that 278 this variable contained explicitly by this MIB and is inside the 279 MIB. This ratio can be calculated by the two objects incoming 280 requests and outgoing requests or even by the responses. 282 7. HTTP Message 284 The WWW server, client and proxy described above communicate with 285 each other using HTTP Messages. A HTTP message consist of request 286 from clients to servers and responses from servers to clients. The 287 message types use the generic format of RFC 822 [## ref TBD ##]. 289 generic-message = ( Request-Line | Status-Line) 290 *message-header 291 CRLF 292 [ message-body ] 294 The mapping of the message onto the byte counter need some special 295 attention. All bytes before the optional message-body are in this MIB 296 are counted as header bytes and the bytes of the message body are 297 named the data bytes. 299 [## is this sufficiently clear to understand the *HeaderBytes and 300 *DataBytes attributes defined in the MIB ##] 302 8. Relationship to other Standards Efforts 304 WWW servers are seen as a specific type of generic application as 305 well as a specific type of networked application. For this reason, 306 their management can be viewed either in terms of the operational 307 model of the sysApplMIB or the service model of the NSM MIB. Since 308 organizations have members of their staff interested in one and/or 309 both of these models, this MIB is designed to address viewing the 310 WWW server from one and/or both models simultaneously. 312 Additionally, users interested in both sets of data are interested in 313 the relationship between sysApplMIB and NSM. At the time of writing 314 this document, it is assumed that sysApplMIB will not address this 315 relationship, so it is defined within this MIB. [## a conformance 316 statement which provides just the implementation of this relationship 317 is likely since other implementers may be interested in NSM, sysAppl 318 and their relationship without the attributes defined in this MIB. 319 For instance, any of the existing extentions to NSM could fit this 320 category. ##] 322 These attributes are intended to address the requirements specified 323 in the document "Applicability of Standards Track MIBs to Management 324 of World Wide Web Servers" [ref]. 326 8.1. Relationship to NSM 327 The Network Services Monitoring MIB is defined as the base set of 328 attributes for managing network applications. This MIB extends that 329 set of attributes for items specific to WWW. 331 8.2. Relationship to sysAppl and applMib 333 The sysApplMIB defines attributes for management of applications 334 which can be realized without instrumenting an application. The 335 ApplMIB extends that framework to include additional attributes 336 which will require instrumentation. This MIB extends the framework 337 again with attributes specific to WWW. 339 8.3. Document relation to sysApplInstall 341 This MIB treats documents on the WWW server as packages installed 342 on the server. Any collection of documents can be defined as a 343 package. The wwwDocInstallPkg and wwwDocInstallElmt attributes 344 provide details of a document on the server. 346 8.4. Usage example for NSM to sysApplMIB relationship 348 The nsmToSysApplElmtRunTable is defined in the applMib to 349 relate NSM and sysApplMIB. The relationship between services 350 defined in the NSM and the applications and elements implementing 351 them in the sysAppl/applMIB framework depends on the implementation 352 of the software. The manager needs to be know about this so that a 353 management application can understand the ramification of such things 354 that effect instances in the various tables. 356 WWW supporting "virtual hosts" on a single machine may implement to 357 NSM and sysAppl components quite differently. Two such 358 implementations are Apache and Netscape. 360 Apache implements a set of processes each capable of servicing 361 requests for any of the virtual domains configured for the host. 362 In comparison, the Netscape server implements a set of processes 363 for each virtual domain. 365 So if a machine were configured as the virtual domain servers for 366 www.a.com and www.b.com, then the following entries in NSM and 367 sysApplMIB would make sense: 369 Apache 371 applTable 372 1) www.a.com 373 2) www.b.com 375 sysApplRunTable 376 1) httpd 378 sysApplElmtRunTable 379 1.1-1.N (where N is max simultaneous requests) 381 Netscape 383 applTable 384 1) www.a.com 385 2) www.b.com 387 sysApplRunTable 388 1) httpd 389 2) httpd 391 sysApplElmtRunTable 392 1.1 - 1.N ( N is max simultaneous for www.a.com) 393 2.1 - 2.M ( M is max simultaneous for www.a.com) 395 With the definition of the nsmToSysApplElmtRunTable, the 396 relationships between the applTable and sysApplRunElmtTable 397 can be defined. If N and M are both fixed to 2, then the 398 Apache and Netscape examples above would have the following 399 entries in the nsmToSysApplElmtRunTable: 401 NOTE: Entries in the following tables are of the form: 403 index) applIndex <-> sysApplRunIndex.sysAppRunElmtIndex 405 Apache 406 nsmToSysApplElmtRunTable 407 1) 1 <-> 1.1 408 2) 1 <-> 1.2 409 3) 2 <-> 1.1 410 4) 2 <-> 1.2 412 Netscape 413 1) 1 <-> 1.1 414 2) 1 <-> 1.2 415 3) 2 <-> 2.1 416 4) 2 <-> 2.2 418 The management application would read this table. It would determine 419 if non-unique sysApplRunIndex.sysAppRunElmtIndex occur for different 420 values of applIndex and if so, know that control of those entries 421 would also effect the other entries. 423 9. Structure of the MIB 425 This document defines a MIB for management of WWW servers. The 426 MIB has the following portions: 428 -Extensions to NSM [ref] 429 -Extensions to sysAppl [ref] framework 430 -error reporting 431 -document storage and statistics 432 -relationships to other MIBs 434 9.1. The systems group 436 The System group consists of a table describing all the entities 437 operated by this host. The table contains not only basic network 438 management information for (potentially) multiple entities running 439 on a single host, but also information for all entities within 440 virtual domains of the host. The columnar objects in the table 441 can be divided into two main groups: 443 1. global administrative information of the entity, such as entity 444 contact person, and 445 2. network information, such as the transport address to which the 446 entity listens. 448 [## see appendix todo list for discussion of the indexing of this 449 table ##] 451 9.2. The Statistics group 453 The statistics group provides network management information about 454 the traffic received or transmitted by an entity. This group contains 455 all network traffic related counters and consists of three tables, 456 which are the summary table, the request table and the response 457 table. 459 9.2.1. SummaryTable 461 The SummaryTable, containing a set of network traffic related 462 counters. The table provides a summarization of the network 463 traffic which is also found in the request and response table as 464 well as counters of discarded and unknown incoming traffic. It is 465 well recognized that certain variables are redundant with respect 466 to the request and response tables, but they are added to provide 467 an operator a quick network overview and reduce SNMP network 468 traffic. 470 9.2.2. RequestTable 472 The RequestTable contains the set of detailed information of 473 incoming and outgoing requests. Here every particular request type 474 can be counted seperately. 476 9.2.3. ResponseTable 477 The ResponseTable contains the set of detailed information of 478 incoming and outgoing requests. Here every particular response type 479 can be counted seperately. 481 9.3. The Document group 483 The document group contains the network management information about 484 the accessed data. The group consists of the following tables. 486 9.3.1. wwwDocNameTable 488 The wwwDocNameTbale provides a means for fast indexing to an entry 489 into the document table given the name of the document. 491 9.3.2. wwwDocTable 493 The wwwDocTable defines the attributes maintained about a given 494 document. The statistics are defined based on the view of the 495 document from the service. The wwwDocInstallPkg and 496 wwwDocInstallElmt are provided to map to a file on the servers disk 497 and provide information via the sysAppl package framework on the 498 specifics of the file. 500 9.3.3. wwwDocFilterTable 501 The wwwDocFilterTable is provided so that the manager can configure 502 which documents are stored into the other two tables. The filtering 503 is based on regular expressions [## need to define reference ##]. 504 This allows the manage to customize the statistics that are gathered 505 to the most relevant documents that he is interested in. 507 9.4. The Error group 509 [## TBD ##] 511 9.5. The Application group 513 The application group defines those attributes which extend the 514 sysAppl/applMIB framework for WWW. For each table in the sysApplMIB, 515 a table is defined utilizing the defined indexing scheme to extend 516 the table for WWW specific attributes. 518 [## additional sections can be added here when we define attributes 519 within the skeleton tables ##] 521 9.6. The Relation group 523 This group of objects defines how this MIB relates to other MIBs. 525 10. Definitions 527 WWW-MIB DEFINITIONS ::= BEGIN 528 IMPORTS 529 applIndex FROM APPLICATION-MIB 530 sysApplInstallPkgIndex, 531 sysApplInstallElmtIndex, 532 sysApplRunIndex, 533 sysApplPastRunIndex, sysApplElmtRunIndex,sysApplElmtPastRunIndex, 534 sysApplElmtRunInvocID, 535 sysApplElmtPastRunInvocID FROM SYSAPPL-MIB 536 ZeroBasedCounter32, TimeFilter FROM RMON2-MIB 537 mib-2 FROM RFC1213-MIB 538 MODULE-IDENTITY, OBJECT-TYPE, 539 Counter32, Integer32 FROM SNMPv2-SMI 540 TEXTUAL-CONVENTION, DisplayString, 541 TimeStamp, TAddress, DateAndTime, 542 RowStatus FROM SNMPv2-TC 543 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 545 wwwMIB MODULE-IDENTITY 546 LAST-UPDATED "9611190000Z" 547 ORGANIZATION "Application MIB Working Group" 548 CONTACT-INFO 549 " Carl W. Kalbfleisch 551 Postal: On-Ramp Technologies 552 1950 Stemmons Freeway 553 Suite 2026 - INFOMART 554 Dallas, TX 75207 555 US 557 Tel: +1 214 672-RAMP 558 Fax: +1 214 672-7275 560 E-mail: cwk@onramp.net" 562 DESCRIPTION 563 "The MIB module for WWW enities. The MIB is named www-mib 564 although it should be applicable to include a wide family 565 of 'Networked Information Retrieval' protocols such as 566 http, nntp, ftp, gopher and wais." 568 REVISION "9611190000Z" 569 DESCRIPTION 570 "Add skelton tables for extending sysApplMib framework 571 within the wwwAppl branch." 573 REVISION "9609240000Z" 574 DESCRIPTION 575 "Update a number of descriptions to make MIB less www 576 specific and more general. Remove wwwEntityObjectID. 577 Move wwwDocNamePkg and wwwDocNameElmt to wwwDocInstallElmt 578 and wwwDocInstallPkg in wwwDocTable." 580 REVISION "9609230000Z" 581 DESCRIPTION 582 "Update a number of descriptions to make MIB less www 583 specific and more general. Changed names of Header/Data 584 byte attributes to Control/Content byte attributes." 586 REVISION "9608160000Z" 587 DESCRIPTION 588 "Initial Internet Draft Release. This is based on two 589 previous revisions, neither of which were internet drafts. 590 See http://http-mib.onramp.net/ for archives, mailing 591 list, etc." 593 ::= { mib-2 8080 } 595 -- 596 -- Object Identifiers for the www-MIB 597 -- 598 wwwMIBObjects OBJECT IDENTIFIER ::= { wwwMIB 1 } 599 wwwMIBConformance OBJECT IDENTIFIER ::= { wwwMIB 2 } 600 wwwMIBCompliances OBJECT IDENTIFIER ::= { wwwMIBConformance 1 } 601 wwwMIBGroups OBJECT IDENTIFIER ::= { wwwMIBConformance 2 } 603 -- 604 -- Textual Conventions 605 -- 606 WwwRequestType ::= TEXTUAL-CONVENTION 607 STATUS current 608 DESCRIPTION 609 "The WwwRequestType describes the types of requests. 610 The value of this type is exactly the same textual 611 identification of request types used in the information 612 transport protocol. 614 For the proper values is refered to the specific protocol 615 specification." 616 SYNTAX DisplayString (SIZE (1..40)) 618 WwwResponseType ::= TEXTUAL-CONVENTION 619 STATUS current 620 DESCRIPTION 621 "The WwwResponseType defines the different response values 622 used by information transport protocols. 623 The value of this type are the 3-digit codes used in the 624 information transport protocol. 626 For the proper values is refered to the specific protocol 627 specification." 628 SYNTAX INTEGER (100..999) 630 -- 631 -- The following textual conventions are used for document 632 -- storage. 633 -- 634 WwwDocType::= TEXTUAL-CONVENTION 635 STATUS current 636 DESCRIPTION 637 "This data type is used to describe the document type. 638 It differentiates between 'static' and 'dynamic' 639 documents. A document is said to be 'static' if subsequent 640 accesses of the same document cause the same data to 641 be sent to the requestor. The document is not changed 642 during the processing of the request by the server and 643 transport towards the client. A document is said to be 644 'dynamic' if subsequent accesses of the file may produce 645 various response data depending on various input 646 parameters or run-time conditions." 647 SYNTAX INTEGER 648 { 649 wwwDocStatic (1), 650 wwwDocDynamic (2) 651 } 653 WwwDocName ::= TEXTUAL-CONVENTION 654 STATUS current 655 DESCRIPTION 656 "The server relative name of a document. If the URL were 657 http://www.x.org/standards/search/search.cgi?string=test 658 then the value of this textual convention would resolve 659 to '/standards/search/search.cgi'." 660 SYNTAX DisplayString 662 WwwDocIndex ::= TEXTUAL-CONVENTION 663 STATUS current 664 DESCRIPTION 665 "This data type is used to index documents. Index values 666 are monotonically increasing from 1. Index values are 667 not reused unless the value wraps. This means that if a 668 documents entry in the table is deleted, then re-added in 669 the document table because it is accessed again, then the 670 document will have a new index value." 671 SYNTAX INTEGER (1..2147483647) 673 -- 674 -- The www System Group 675 -- 676 -- The www System group contains information about the www protocol 677 -- entities. 678 -- 679 wwwSystem OBJECT IDENTIFIER ::= { wwwMIBObjects 1 } 681 wwwEntityTable OBJECT-TYPE 682 SYNTAX SEQUENCE OF WwwEntityEntry 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "The table of the entities present on the system." 687 ::= { wwwSystem 1 } 689 wwwEntityEntry OBJECT-TYPE 690 SYNTAX WwwEntityEntry 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "Details of a particular entity which can be a 695 Server, a Client, a Proxy or a Caching-Proxy." 696 INDEX { applIndex } 697 ::= { wwwEntityTable 1 } 699 WwwEntityEntry ::= SEQUENCE { 700 wwwEntityDescription DisplayString, 701 wwwEntityContact DisplayString, 702 wwwEntityProtocol OBJECT IDENTIFIER, 703 wwwEntityProtocolVersion DisplayString, 704 wwwEntityName DisplayString, 705 wwwEntityAddress TAddress, 706 wwwEntityType INTEGER 707 } 709 wwwEntityDescription OBJECT-TYPE 710 SYNTAX DisplayString 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "Textual description of the entity. This shall include 715 at least the vendor and version number of the application. 716 In a minimal case, this might be the Product Token for 717 the application." 718 ::= { wwwEntityEntry 1 } 720 wwwEntityContact OBJECT-TYPE 721 SYNTAX DisplayString 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The textual identification of the contact person 726 for this entity, together with information on how 727 to contact this person. For instance, this might 728 be 'webmaster@domain.name'." 729 ::= { wwwEntityEntry 2 } 731 wwwEntityProtocol OBJECT-TYPE 732 SYNTAX OBJECT IDENTIFIER 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "An identification of the primary protocol in use by this 737 entity. For Internet applications, the IANA maintains 738 a registry of the OIDs which correspond to well-known 739 applications. If the application protocol is not listed 740 in the registry, an OID value of the form {applTCPProtoID 741 port} or {applUDProtoID port} are used for TCP-based and 742 UDP-based protocols, respectively. In either case 'port' 743 corresponds to the primary port number being used by the 744 protocol." 745 ::= { wwwEntityEntry 3 } 747 wwwEntityProtocolVersion OBJECT-TYPE 748 SYNTAX DisplayString 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "Textual description of the version of the information 753 transport protocol implemented. 754 For HTTP version 1.1, the value shall be the 'HTTP/1.1'." 755 ::= { wwwEntityEntry 4 } 757 wwwEntityName OBJECT-TYPE 758 SYNTAX DisplayString 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The fully qualified domain name by which this entity is 763 known. This may be different than applName since that 764 value is only a textual name for the application." 765 ::= { wwwEntityEntry 5 } 767 wwwEntityAddress OBJECT-TYPE 768 SYNTAX TAddress 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "The Transport Address at which the entity listens for 773 Requests or Responses." 774 ::= { wwwEntityEntry 6 } 776 wwwEntityType OBJECT-TYPE 777 SYNTAX INTEGER { 778 server(1), 779 client(2), 780 proxy(3), 781 cachingProxy(4) 782 } 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "Identification of the role of the entity." 787 ::= { wwwEntityEntry 7 } 789 -- The www Statistics Group 790 -- 791 -- The www Statistics group contains information concerning the 792 -- utilisation of the www protocol entity. 794 wwwStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 2 } 795 -- 796 -- wwwSummaryTable 797 -- 798 -- 799 wwwSummaryTable OBJECT-TYPE 800 SYNTAX SEQUENCE OF WwwSummaryEntry 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "The table providing overview statistics for the 805 entities on this system." 806 ::= { wwwStatistics 1 } 808 wwwSummaryEntry OBJECT-TYPE 809 SYNTAX WwwSummaryEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "Overview statistics for an individual entity." 814 INDEX { applIndex } 815 ::= { wwwSummaryTable 1 } 817 WwwSummaryEntry ::= SEQUENCE { 818 wwwSummaryInRequests Counter32, 819 wwwSummaryOutRequests Counter32, 820 wwwSummaryRequestErrors Counter32, 821 wwwSummaryRequestDiscards Counter32, 822 wwwSummaryInResponses Counter32, 823 wwwSummaryOutResponses Counter32, 824 wwwSummaryResponseDiscards Counter32, 825 wwwSummaryInUnknowns Counter32, 826 wwwSummaryInControlBytes Counter32, 827 wwwSummaryInContentBytes Counter32, 828 wwwSummaryOutControlBytes Counter32, 829 wwwSummaryOutContentBytes Counter32 830 } 832 wwwSummaryInRequests OBJECT-TYPE 833 SYNTAX Counter32 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "The number of requests received by this entity." 838 ::= { wwwSummaryEntry 1 } 840 wwwSummaryOutRequests OBJECT-TYPE 841 SYNTAX Counter32 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "The number of requests generated by this entity." 846 ::= { wwwSummaryEntry 2 } 848 wwwSummaryRequestErrors OBJECT-TYPE 849 SYNTAX Counter32 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "The number of requests containing errors and detected 854 by this entity" 855 ::= { wwwSummaryEntry 3 } 857 wwwSummaryRequestDiscards OBJECT-TYPE 858 SYNTAX Counter32 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The number of requests discarded by this entity." 863 ::= { wwwSummaryEntry 4 } 865 wwwSummaryInResponses OBJECT-TYPE 866 SYNTAX Counter32 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "The number of responses received by this entity." 871 ::= { wwwSummaryEntry 5 } 873 wwwSummaryOutResponses OBJECT-TYPE 874 SYNTAX Counter32 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "The number of responses generated by this entity." 879 ::= { wwwSummaryEntry 6 } 881 wwwSummaryResponseDiscards OBJECT-TYPE 882 SYNTAX Counter32 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The number of responses discarded by this entity." 887 ::= { wwwSummaryEntry 7 } 889 wwwSummaryInUnknowns OBJECT-TYPE 890 SYNTAX Counter32 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The number of unknown messages detected by this entity." 895 ::= { wwwSummaryEntry 8 } 897 wwwSummaryInControlBytes OBJECT-TYPE 898 SYNTAX Counter32 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The number of protocol control bytes received by this 903 entity." 904 ::= { wwwSummaryEntry 9 } 906 wwwSummaryInContentBytes OBJECT-TYPE 907 SYNTAX Counter32 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "The number of protocol content bytes received by this 912 entity." 913 ::= { wwwSummaryEntry 10 } 915 wwwSummaryOutControlBytes OBJECT-TYPE 916 SYNTAX Counter32 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The number of protocol control bytes generated by this 921 entity." 922 ::= { wwwSummaryEntry 11 } 924 wwwSummaryOutContentBytes OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "The number of protocol content bytes generated by this 930 entity." 931 ::= { wwwSummaryEntry 12 } 933 -- 934 -- wwwRequestTable 935 -- 936 -- 937 -- 938 -- 939 wwwRequestTable OBJECT-TYPE 940 SYNTAX SEQUENCE OF WwwRequestEntry 941 MAX-ACCESS not-accessible 942 STATUS current 943 DESCRIPTION 944 "The table providing detailed request statistics for the 945 entities on this system." 946 ::= { wwwStatistics 2 } 948 wwwRequestEntry OBJECT-TYPE 949 SYNTAX WwwRequestEntry 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "Request statistics for an individual entity." 954 INDEX { applIndex, wwwRequestIndex } 955 ::= { wwwRequestTable 1 } 957 WwwRequestEntry ::= SEQUENCE { 958 wwwRequestIndex WwwRequestType, 959 wwwRequestInCount Counter32, 960 wwwRequestInControlBytes Counter32, 961 wwwRequestInContentBytes Counter32, 962 wwwRequestInLastTime TimeStamp, 963 wwwRequestOutCount Counter32, 964 wwwRequestOutControlBytes Counter32, 965 wwwRequestOutContentBytes Counter32, 966 wwwRequestOutLastTime TimeStamp 967 } 969 wwwRequestIndex OBJECT-TYPE 970 SYNTAX WwwRequestType 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "The particular request type the statistics apply to." 975 ::= { wwwRequestEntry 1 } 977 wwwRequestInCount OBJECT-TYPE 978 SYNTAX Counter32 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The number of requests of this type received by 983 this entity." 984 ::= { wwwRequestEntry 2 } 986 wwwRequestInControlBytes OBJECT-TYPE 987 SYNTAX Counter32 988 MAX-ACCESS read-only 989 STATUS current 990 DESCRIPTION 991 "The number of protocol control bytes of this type 992 received by this entity." 993 ::= { wwwRequestEntry 3 } 995 wwwRequestInContentBytes OBJECT-TYPE 996 SYNTAX Counter32 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The number of protocol content data bytes received 1001 with this type by this entity." 1002 ::= { wwwRequestEntry 4 } 1004 wwwRequestInLastTime OBJECT-TYPE 1005 SYNTAX TimeStamp 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The value of sysUpTime when the last byte of the last 1010 complete request of this type was received by this 1011 entity." 1012 ::= { wwwRequestEntry 5 } 1014 wwwRequestOutCount OBJECT-TYPE 1015 SYNTAX Counter32 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION 1019 "The number of requests of this type generated by this 1020 entity." 1021 ::= { wwwRequestEntry 6 } 1023 wwwRequestOutControlBytes OBJECT-TYPE 1024 SYNTAX Counter32 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The number of protocol control bytes of this type 1029 generated by this entity." 1030 ::= { wwwRequestEntry 7 } 1032 wwwRequestOutContentBytes OBJECT-TYPE 1033 SYNTAX Counter32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The number of protocol content bytes generated by 1038 this type of request by this entity." 1039 ::= { wwwRequestEntry 8 } 1041 wwwRequestOutLastTime OBJECT-TYPE 1042 SYNTAX TimeStamp 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "The value of sysUpTime when the first byte of the 1047 last request of this type was send by this entity." 1048 ::= { wwwRequestEntry 9 } 1050 -- 1051 -- wwwResponseTable 1052 -- 1053 -- 1054 -- 1055 -- 1056 wwwResponseTable OBJECT-TYPE 1057 SYNTAX SEQUENCE OF WwwResponseEntry 1058 MAX-ACCESS not-accessible 1059 STATUS current 1060 DESCRIPTION 1061 "The table providing detailed response statistics for the 1062 entities on this system." 1063 ::= { wwwStatistics 3 } 1065 wwwResponseEntry OBJECT-TYPE 1066 SYNTAX WwwResponseEntry 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION 1070 "Response statistics for an individual entity." 1071 INDEX { applIndex, wwwResponseIndex } 1072 ::= { wwwResponseTable 1 } 1074 WwwResponseEntry ::= SEQUENCE { 1075 wwwResponseIndex WwwResponseType, 1076 wwwResponseInCount Counter32, 1077 wwwResponseInControlBytes Counter32, 1078 wwwResponseInContentBytes Counter32, 1079 wwwResponseInLastTime TimeStamp, 1080 wwwResponseOutCount Counter32, 1081 wwwResponseOutControlBytes Counter32, 1082 wwwResponseOutContentBytes Counter32, 1083 wwwResponseOutLastTime TimeStamp 1084 } 1086 wwwResponseIndex OBJECT-TYPE 1087 SYNTAX WwwResponseType 1088 MAX-ACCESS not-accessible 1089 STATUS current 1090 DESCRIPTION 1091 "The particular response type the statistics apply to." 1092 ::= { wwwResponseEntry 1 } 1094 wwwResponseInCount OBJECT-TYPE 1095 SYNTAX Counter32 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "The number of responses of this type received by this 1100 entity." 1101 ::= { wwwResponseEntry 2 } 1103 wwwResponseInControlBytes OBJECT-TYPE 1104 SYNTAX Counter32 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "The number of protocol control bytes of this type 1109 received by this entity." 1110 ::= { wwwResponseEntry 3 } 1112 wwwResponseInContentBytes OBJECT-TYPE 1113 SYNTAX Counter32 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "The number of protocol content bytes received 1118 by this type of response by this entity." 1119 ::= { wwwResponseEntry 4 } 1121 wwwResponseInLastTime OBJECT-TYPE 1122 SYNTAX TimeStamp 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "The value of sysUpTime when the last byte of the last 1127 complete response of this type was received by this 1128 entity." 1129 ::= { wwwResponseEntry 5 } 1131 wwwResponseOutCount OBJECT-TYPE 1132 SYNTAX Counter32 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The number of responses of this type generated by this 1137 entity." 1138 ::= { wwwResponseEntry 6 } 1140 wwwResponseOutControlBytes OBJECT-TYPE 1141 SYNTAX Counter32 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "The number of protocol control bytes of this type 1146 generated by this entity." 1147 ::= { wwwResponseEntry 7 } 1149 wwwResponseOutContentBytes OBJECT-TYPE 1150 SYNTAX Counter32 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "The number of protocol content bytes generated by this 1155 type of response by this entity." 1156 ::= { wwwResponseEntry 8 } 1158 wwwResponseOutLastTime OBJECT-TYPE 1159 SYNTAX TimeStamp 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The value of sysUpTime when the first byte of the 1164 last response of this type was sent by this entity." 1165 ::= { wwwResponseEntry 9 } 1167 -- 1168 -- wwwDocument 1169 -- 1170 -- This portion of the MIB defines objects for the document store. 1171 -- 1172 -- The document store is view from two perspectives: 1173 -- 1174 -- -as seen from clients of the entity from a service perspective 1175 -- -as viewed by the collection of files in the filesystem 1176 -- 1177 -- The first case is defined as a table of statistics as seen from 1178 -- the service perspective. This wwwDocTable is indexed by applIndex 1179 -- and a unique value for that entity for each document. The entries 1180 -- in this table defines statistics and information from this service 1181 -- perspective. 1182 -- 1183 -- The second case is defined using the sysApplInstallPkgTable and the 1184 -- sysApplInstallElmtTable. An entry in the sysApplInstallPkgTable can 1185 -- be defined for the entire collection of document resources the 1186 -- service provides, or any subset of those document resources. For 1187 -- instance, an Internet service provider may configure a separate 1188 -- entry in the sysApplInstallPkgTable for each customer on a server 1189 -- supporting multiple virtual servers, for each user name of a 1190 -- domain, etc. 1191 -- 1192 -- Entries in the sysApplInstallElmtTable correspond to each file in 1193 -- the filesystem which are mapped to entries in wwwDocTable. These 1194 -- entries in sysApplInstallElmtTable may be loaded by the agent when 1195 -- the file is first accessed, or be pre-loaded even with entries of 1196 -- files that have never been accessed by the service. 1197 -- 1198 -- The wwwDocNameTable provides a mapping from the name of the 1199 -- document resource from the service perspective to the indices 1200 -- of the wwwDocTable, the sysApplInstallPkgTable and the 1201 -- sysApplInstallElmtTable. 1202 -- 1204 wwwDocument OBJECT IDENTIFIER ::= { wwwMIBObjects 3 } 1206 -- 1207 -- wwwDocNameTable 1208 -- 1210 -- [## Note that SMI limits the max. number of elements in an 1211 -- object identifier to 128. This means that a wwwDocNameName is 1212 -- more or less limited to 100 characters. ##] 1214 wwwDocNameTable OBJECT-TYPE 1215 SYNTAX SEQUENCE OF WwwDocNameEntry 1216 MAX-ACCESS not-accessible 1217 STATUS current 1218 DESCRIPTION 1219 "The table of document name to index mappings. This table is 1220 provided so that if the document name is known, the index 1221 into the wwwDocTable can be obtained without having to 1222 traverse the entire wwwDocTable. Entries are indexed by 1223 the URL path without any possible arguments. 1225 If the value of wwwEntityName.1 is www.a.org, then the 1226 wwwDocTable entry for http://www.a.org/foo/bar.html can be 1227 obtained by retrieving 1228 wwwDocNameIndex.1.13.47.102.111.111.47.98.97.114.46.104.116.109.108" 1229 ::= {wwwDocument 1} 1231 wwwDocNameEntry OBJECT-TYPE 1232 SYNTAX WwwDocNameEntry 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "An entry associated with a particular mapping 1237 in the wwwDocNameTable." 1238 INDEX {applIndex, wwwDocNameName} 1239 ::= {wwwDocNameTable 1} 1241 WwwDocNameEntry ::= SEQUENCE 1242 { 1243 wwwDocNameName WwwDocName, 1244 wwwDocNameIndex WwwDocIndex 1245 } 1247 wwwDocNameName OBJECT-TYPE 1248 SYNTAX WwwDocName 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "Auxilary object used along with applIndex to uniquely identify 1253 a wwwDocNameEntry for a wwwEntityEntry. applIndex is the table 1254 index value from the Network Services Monitoring MIB." 1255 ::= {wwwDocNameEntry 1} 1257 wwwDocNameIndex OBJECT-TYPE 1258 SYNTAX WwwDocIndex 1259 MAX-ACCESS read-only 1260 STATUS current 1261 DESCRIPTION 1262 "A value that can be used along with applIndex to access the 1263 wwwDocNameName document information in the wwwDocTable. 1264 applIndex is the table index value from the Network Services 1265 Monitoring MIB." 1266 ::= {wwwDocNameEntry 2} 1268 -- 1269 -- wwwDocFilterTable 1270 -- 1271 wwwDocFilterTable OBJECT-TYPE 1272 SYNTAX SEQUENCE OF WwwDocFilterEntry 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "This table is used to filter out entries that should not appear 1277 in the wwwDocNameTable. A document name is matched against the 1278 expressions listed in this table. A successful match will stop 1279 further processing of this entry so that this document name will 1280 not appear in the wwwDocNameTable." 1281 ::= { wwwDocument 2 } 1283 wwwDocFilterEntry OBJECT-TYPE 1284 SYNTAX WwwDocFilterEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "An entry that filters documents that match a specific regular 1289 expression." 1290 INDEX { applIndex, wwwDocFilterIndex } 1291 ::= { wwwDocFilterTable 1} 1293 WwwDocFilterEntry ::= SEQUENCE { 1294 wwwDocFilterIndex Integer32, 1295 wwwDocFilterRegexp DisplayString, 1296 wwwDocFilterStatus RowStatus 1297 } 1299 wwwDocFilterIndex OBJECT-TYPE 1300 SYNTAX Integer32 (1..10000) 1301 MAX-ACCESS not-accessible 1302 STATUS current 1303 DESCRIPTION 1304 "An arbitrary integer used only for indexing purposes." 1305 ::= { wwwDocFilterEntry 1 } 1307 wwwDocFilterRegexp OBJECT-TYPE 1308 SYNTAX DisplayString 1309 MAX-ACCESS read-create 1310 STATUS current 1311 DESCRIPTION 1312 "A regular expression that is matched against the document 1313 name. [## Definition of a regular expression missing. ##]" 1314 ::= { wwwDocFilterEntry 2 } 1316 wwwDocFilterStatus OBJECT-TYPE 1317 SYNTAX RowStatus 1318 MAX-ACCESS read-create 1319 STATUS current 1320 DESCRIPTION 1321 "An object used to create and remove entries in the 1322 wwwDocFilterTable." 1323 ::= { wwwDocFilterEntry 3 } 1325 -- 1326 -- wwwDocTable 1327 -- 1328 -- 1329 -- 1330 -- 1331 wwwDocTable OBJECT-TYPE 1332 SYNTAX SEQUENCE OF WwwDocEntry 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "The table of documents accessible from any entity configured 1337 in the wwwEntityTable. The agent minimally adds entries to this 1338 table to correspond with documents that have been accessed. 1339 It may choose to add entries for documents which have not yet 1340 been accessed as well." 1341 ::= { wwwDocument 3 } 1343 wwwDocEntry OBJECT-TYPE 1344 SYNTAX WwwDocEntry 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "An entry associated with a particular mapping in the 1349 wwwDocTable." 1350 INDEX {applIndex, wwwDocNameIndex, wwwDocTimeMark} 1351 ::= {wwwDocTable 1} 1353 WwwDocEntry ::= SEQUENCE 1354 { 1355 wwwDocTimeMark TimeFilter, 1356 wwwDocInstallPkg Integer32, 1357 wwwDocInstallElmt Integer32, 1358 wwwDocName WwwDocName, 1359 wwwDocType WwwDocType, 1360 wwwDocFirstAccessTimeStamp DateAndTime, 1361 wwwDocLastAccessTimeStamp DateAndTime, 1362 wwwDocLastAccessResponseType WwwResponseType, 1363 wwwDocInBytes ZeroBasedCounter32, 1364 wwwDocOutBytes ZeroBasedCounter32, 1365 wwwDocInCount ZeroBasedCounter32, 1366 wwwDocOutCount ZeroBasedCounter32, 1367 wwwDocSpecific OBJECT IDENTIFIER, 1368 wwwDocStatus RowStatus 1369 } 1371 wwwDocTimeMark OBJECT-TYPE 1372 SYNTAX TimeFilter 1373 MAX-ACCESS not-accessible 1374 STATUS current 1375 DESCRIPTION 1376 "A TimeFilter for this entry by which the real accesses 1377 are counted between two sequential retrievals of this table. 1378 The TimeFilter is a textual convention in RMON-2, 1379 draft-ietf-rmonmib-rmonmib-v2-03.txt. 1380 For the appropriate behaviour is referred to that MIB. 1381 The values during startup time are exactly the same 1382 during the last actions of the HTTP-server before the 1383 server went down. 1385 [## we do not actually want to purge 1386 this table when sysUptime resets. We need to consider 1387 whether this is still an acceptable use of TimeFilter. 1388 The reasoning is that we want these attributes to be 1389 maintained across restarts of the http software, the 1390 management software and the host computer. In other words, 1391 we want the data in the table to be persistent. At the 1392 same time, since the table is likely very large, we want 1393 the ability to read the updates since a given time. I would 1394 prefer the following. Rather than purging the table when 1395 sysUptime is zero (wrap or restart), return all entries in 1396 the table. For instance wwwDocName.x.y.0 would return 1397 all documents for all valid values of x and y. ##]" 1398 ::= {wwwDocEntry 1} 1400 -- [## A TC for this index has been requested from the application MIB 1401 -- WG. If added, we should insure that 0 is in the valid range. ##] 1403 wwwDocInstallPkg OBJECT-TYPE 1404 SYNTAX Integer32 (0..'7fffffff'h) 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "This value can be used to index into the sysApplInstallPkgTable 1409 which defines the documents for this wwwEntity. Entries in the 1410 sysApplInstallPkgTable can be allocated so that the documents 1411 that the web server provides are viewed as an installed package. 1412 There might be a single package for the entire server, a package 1413 for each virtual host on the server, or entries for each user. 1414 For instance, the documents that make up www.a.org could be 1415 viewed as a package. Additionally, users whose pages show up as 1416 www.a.org/~user could be separate packages or part of the main 1417 package. If there is no file on the filesystem which corresponds 1418 to this URL (for instance it is handled internally to the web 1419 server) and there is no corresponding entry in the 1420 sysApplInstallPkgTable, then the value of this object is 0." 1421 ::= {wwwDocEntry 2} 1423 -- [## A TC for this index has been requested from the application MIB 1424 -- WG. If added, we should insure that 0 is in the valid range. ##] 1426 wwwDocInstallElmt OBJECT-TYPE 1427 SYNTAX Integer32 (0..'7fffffff'h) 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "This value can be used along with the corresponding value for 1432 wwwDocNamePkg to index into the sysApplInstallElmtTable to find 1433 specific information about the representation of this document 1434 on the fileservers disk. The sysApplInstallPkgTable should 1435 contain an entry for every document, file, and script utilized 1436 by the web server, even if those entries correspond to items 1437 that have never been accessed. This means that there may be 1438 items in the sysApplInstallElmt tables that are not referenced 1439 from this table. If there is no corresponding file on the 1440 fileserver, then the value of this object is 0. This can occur 1441 if the URL is handled internally to the web server, or if all 1442 accesses to the URL indicate a failed requests such as document 1443 not found." 1444 ::= {wwwDocEntry 3} 1446 wwwDocName OBJECT-TYPE 1447 SYNTAX WwwDocName 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "The name of this document relative to the www entity 1452 name as seen from the web. For instance if the www 1453 entity name is www.a.org and this file is accessible 1454 on the web as http://www.a.org/foo.html, then the 1455 value of this object would be '/foo.html'." 1456 ::= {wwwDocEntry 4} 1458 wwwDocType OBJECT-TYPE 1459 SYNTAX WwwDocType 1460 MAX-ACCESS read-only 1461 STATUS current 1462 DESCRIPTION 1463 "Indicates the type of the document. If the document is 'static', 1464 then the related sysApplInstallElmtSize refers to the size that 1465 is transmitted when this document is requested. If the document 1466 is 'dynamic', then the related sysApplInstallElmtSize is 0 and 1467 the amount of data transmitted on access is not known, but 1468 understood to be variable." 1469 ::= {wwwDocEntry 5} 1471 wwwDocFirstAccessTimeStamp OBJECT-TYPE 1472 SYNTAX DateAndTime 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "The date and time that this document was first accessed 1477 since being inserted into this table or being modified. If 1478 entries are inserted on access, then this also corresponds 1479 to the date and time of being placed into this table. If 1480 entries are inserted into the table prior to being accessed, 1481 then this value should be all zero. When a document is accessed 1482 following being modified on the servers disk, this value is 1483 reset to the timestamp of such access. [## do we want to use 1484 the RowStatus 'notInService' to indicate rows that are 1485 inserted prior to use? ##]" 1486 ::= {wwwDocEntry 6} 1488 wwwDocLastAccessTimeStamp OBJECT-TYPE 1489 SYNTAX DateAndTime 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "The date and time that this document was last accessed." 1494 ::= {wwwDocEntry 7} 1496 wwwDocLastAccessResponseType OBJECT-TYPE 1497 SYNTAX WwwResponseType 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "The protocol response type which was sent to the client 1502 the last time this document was accessed." 1503 ::= {wwwDocEntry 8} 1505 wwwDocInBytes OBJECT-TYPE 1506 SYNTAX ZeroBasedCounter32 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "The number of bytes received by this entity while transporting 1511 references to this document." 1512 ::= {wwwDocEntry 9} 1514 wwwDocOutBytes OBJECT-TYPE 1515 SYNTAX ZeroBasedCounter32 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "The number of content bytes while transmitting this document." 1520 ::= {wwwDocEntry 10} 1522 wwwDocInCount OBJECT-TYPE 1523 SYNTAX ZeroBasedCounter32 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "The number of times this document has been received." 1528 ::= {wwwDocEntry 11} 1530 wwwDocOutCount OBJECT-TYPE 1531 SYNTAX ZeroBasedCounter32 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "The number of times this document has been transmitted." 1536 ::= {wwwDocEntry 12} 1538 wwwDocSpecific OBJECT-TYPE 1539 SYNTAX OBJECT IDENTIFIER 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "A reference to MIB definitions specific to the particular 1544 document being realized by this entry. For example, if this 1545 entry corresponds to a CGI based URL, then this value might 1546 refer to a table specific to the usage of that URL with 1547 various parameter combinations. If this information is not 1548 present, its value should be set to the OBJECT IDENTIFIER 1549 { 0 0 }, which is a syntactically valid object identifier, 1550 and any conformant implementation of ASN.1 and BER must be 1551 able to generate and recognize this value. Agents that do 1552 not support any extensions return { 0 0 } for all entries 1553 in this table. [## Is this a sufficient way to allow extension 1554 to support parameters? ##]" 1555 ::= {wwwDocEntry 13} 1557 wwwDocStatus OBJECT-TYPE 1558 SYNTAX RowStatus 1559 MAX-ACCESS read-write 1560 STATUS current 1561 DESCRIPTION 1562 "The status of this row. Rows are added to this table by the 1563 agent, normally when a resource is first requested. Writing 1564 'Destroy' to this object removes this entry from the 1565 wwwDocTable as well as removing the associated entry in the 1566 wwwDocNameTable. No other value is supported." 1567 ::= {wwwDocEntry 14} 1569 -- 1570 -- wwwError 1571 -- 1572 -- Objects which define error reporting conditions 1573 -- 1574 wwwError OBJECT IDENTIFIER ::= { wwwMIBObjects 4 } 1576 -- 1577 -- wwwAppl 1578 -- 1579 -- Objects which extend sysApplMIB/applMIB framework 1580 -- 1581 wwwAppl OBJECT IDENTIFIER ::= { wwwMIBObjects 5 } 1582 wwwApplInstalled OBJECT IDENTIFIER ::= { wwwAppl 1 } 1583 wwwApplRun OBJECT IDENTIFIER ::= { wwwAppl 2 } 1585 -- 1586 -- wwwApplInstallPkgTable 1587 -- 1588 wwwApplInstallPkgTable OBJECT-TYPE 1589 SYNTAX SEQUENCE OF WwwApplInstallPkgEntry 1590 MAX-ACCESS not-accessible 1591 STATUS current 1592 DESCRIPTION 1593 "The table listing the www software application packages 1594 installed on a host computer. In order to appear in 1595 this table, it may be necessary for the application 1596 to be installed using some type of software 1597 installation mechanism or global registry so that its 1598 existence can be detected by the agent implementation. 1600 This table extends the sysApplInstallPkgTable of the 1601 sysApplMib/applMib framework with attributes specific 1602 to www applications." 1603 ::= { wwwApplInstalled 1 } 1605 wwwApplInstallPkgEntry OBJECT-TYPE 1606 SYNTAX WwwApplInstallPkgEntry 1607 MAX-ACCESS not-accessible 1608 STATUS current 1609 DESCRIPTION 1610 "The logical row describing an installed www application 1611 package." 1612 INDEX { sysApplInstallPkgIndex } 1613 ::= { wwwApplInstallPkgTable 1 } 1615 WwwApplInstallPkgEntry ::= SEQUENCE 1616 { 1617 wwwApplInstallPkgBogus Integer32 1618 } 1620 wwwApplInstallPkgBogus OBJECT-TYPE 1621 SYNTAX Integer32 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "A place holder to satisfy the MIB compiler." 1626 ::= { wwwApplInstallPkgEntry 1} 1628 -- 1629 -- wwwApplInstallElmtTable 1630 -- 1631 wwwApplInstallElmtTable OBJECT-TYPE 1632 SYNTAX SEQUENCE OF WwwApplInstallElmtEntry 1633 MAX-ACCESS not-accessible 1634 STATUS current 1635 DESCRIPTION 1636 "This table details the individual application package 1637 elements (files and executables) which comprise the 1638 www applications defined in the wwwApplInstallPkgTable. 1640 Table entries are indexed by sysApplInstallPkgIndex, 1641 sysApplInstallElmtIndex to facilitate retrieval of 1642 all elements associated with a particular installed 1643 application package. 1645 This table extends the sysApplInstallElmtTable of the 1646 sysApplMib/applMib framework with attributes specific 1647 to www applications." 1648 ::= { wwwApplInstalled 2 } 1650 wwwApplInstallElmtEntry OBJECT-TYPE 1651 SYNTAX WwwApplInstallElmtEntry 1652 MAX-ACCESS not-accessible 1653 STATUS current 1654 DESCRIPTION 1655 "The logical row describing an element of an installed 1656 www application. The element may be an executable or 1657 non-executable file." 1658 INDEX {sysApplInstallPkgIndex, sysApplInstallElmtIndex} 1659 ::= { wwwApplInstallElmtTable 1 } 1661 WwwApplInstallElmtEntry ::= SEQUENCE 1662 { 1663 wwwApplInstallElmtBogus Integer32 1664 } 1666 wwwApplInstallElmtBogus OBJECT-TYPE 1667 SYNTAX Integer32 1668 MAX-ACCESS read-only 1669 STATUS current 1670 DESCRIPTION 1671 "A place holder to satisfy the MIB compiler." 1672 ::= { wwwApplInstallElmtEntry 1} 1674 -- 1675 -- wwwApplRunTable 1676 -- 1677 wwwApplRunTable OBJECT-TYPE 1678 SYNTAX SEQUENCE OF WwwApplRunEntry 1679 MAX-ACCESS not-accessible 1680 STATUS current 1681 DESCRIPTION 1682 "The table describes the www applications which are 1683 executing on the host. Each time an application is 1684 invoked, an entry is created in this table. When an 1685 application ends, the entry is removed from this table and 1686 placed in the wwwApplPastRunTable. Note that the 1687 corresponding entry in sysApplRunTable is moved to 1688 sysAPplPastRunTable at the same time. 1690 The table is indexed by sysApplInstallPkgIndex, 1691 sysApplRunIndex to enable managers to easily locate all 1692 invocations of a particular application package. 1694 This table extends the sysApplRunTable of the 1695 sysApplMib/applMib framework with attributes specific 1696 to www applications." 1697 ::= { wwwApplRun 1 } 1699 wwwApplRunEntry OBJECT-TYPE 1700 SYNTAX WwwApplRunEntry 1701 MAX-ACCESS not-accessible 1702 STATUS current 1703 DESCRIPTION 1704 "The logical row describing a www application which is 1705 currently running on this host." 1706 INDEX { sysApplInstallPkgIndex, sysApplRunIndex } 1707 ::= { wwwApplRunTable 1 } 1709 WwwApplRunEntry ::= SEQUENCE { 1710 wwwApplRunBogus Integer32 1711 } 1713 wwwApplRunBogus OBJECT-TYPE 1714 SYNTAX Integer32 1715 MAX-ACCESS read-only 1716 STATUS current 1717 DESCRIPTION 1718 "A place holder to satisfy the MIB compiler." 1719 ::= { wwwApplRunEntry 1} 1721 -- 1722 -- wwwApplPastRunTable 1723 -- 1724 wwwApplPastRunTable OBJECT-TYPE 1725 SYNTAX SEQUENCE OF WwwApplPastRunEntry 1726 MAX-ACCESS not-accessible 1727 STATUS current 1728 DESCRIPTION 1729 "A history of the www applications that have previously run 1730 on the host computer. An entry is moved to this table 1731 from the wwwApplRunTable when the invoked application 1732 represented by the entry ceases to be running. 1734 Entries remain in this table until they are aged out when 1735 either the table size reaches a maximum as determined by 1736 the sysApplPastRunMaxRows, or when an entry has aged to 1737 exceed a time limit as set by sysApplPastRunTblTimeLimit. 1739 Entries in this table are indexed by sysApplInstallPkgIndex, 1740 sysApplPastRunIndex to facilitate retrieval of all past 1741 run invocations of a particular installed application. 1743 This table extends the sysApplPastRunTable of the 1744 sysApplMib/applMib framework with attributes specific 1745 to www applications." 1746 ::= { wwwApplRun 2 } 1748 wwwApplPastRunEntry OBJECT-TYPE 1749 SYNTAX WwwApplPastRunEntry 1750 MAX-ACCESS not-accessible 1751 STATUS current 1752 DESCRIPTION 1753 "The logical row describing an invocation of a www 1754 application which was previously run and has terminated. 1755 The entry is basically copied from the wwwApplRunTable 1756 when the application instance terminates. Hence, the 1757 entry's value for sysApplPastRunIndex is the same as its 1758 value was for sysApplRunIndex." 1759 INDEX { sysApplInstallPkgIndex, sysApplPastRunIndex } 1760 ::= { wwwApplPastRunTable 1 } 1762 WwwApplPastRunEntry ::= SEQUENCE 1763 { 1764 wwwApplPastRunBogus Integer32 1765 } 1767 wwwApplPastRunBogus OBJECT-TYPE 1768 SYNTAX Integer32 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "A place holder to satisfy the MIB compiler." 1773 ::= { wwwApplPastRunEntry 1} 1775 -- 1776 -- wwwApplElmtRunTable 1777 -- 1778 wwwApplElmtRunTable OBJECT-TYPE 1779 SYNTAX SEQUENCE OF WwwApplElmtRunEntry 1780 MAX-ACCESS not-accessible 1781 STATUS current 1782 DESCRIPTION 1783 "The table describes the processes which are 1784 currently executing on the host system which are 1785 associated with an invoked www application. 1787 The table is indexed by sysApplElmtRunInvocID, 1788 sysApplElmtRunIndex to make it easy to locate all running 1789 elements of a particular invoked application. 1791 This table extends the sysApplElmtRunTable of the 1792 sysApplMib/applMib framework with attributes specific 1793 to www applications." 1794 ::= { wwwApplRun 3 } 1796 wwwApplElmtRunEntry OBJECT-TYPE 1797 SYNTAX WwwApplElmtRunEntry 1798 MAX-ACCESS not-accessible 1799 STATUS current 1800 DESCRIPTION 1801 "The logical row describing a process currently 1802 running on this host which is associated with an 1803 invoked www application." 1804 INDEX { sysApplElmtRunInvocID, sysApplElmtRunIndex } 1805 ::= { wwwApplElmtRunTable 1 } 1807 WwwApplElmtRunEntry ::= SEQUENCE 1808 { 1809 wwwApplElmtRunBogus Integer32 1810 } 1812 wwwApplElmtRunBogus OBJECT-TYPE 1813 SYNTAX Integer32 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "A place holder to satisfy the MIB compiler." 1818 ::= { wwwApplElmtRunEntry 1} 1820 -- 1821 -- wwwApplElmtPastRunTable 1822 -- 1823 wwwApplElmtPastRunTable OBJECT-TYPE 1824 SYNTAX SEQUENCE OF WwwApplElmtPastRunEntry 1825 MAX-ACCESS not-accessible 1826 STATUS current 1827 DESCRIPTION 1828 "The table describes the processes which have previously 1829 executed on the host system as part of a www application. 1831 Entries are added to this table when the corresponding 1832 process in the wwwApplElmtRun Table terminates. Just as 1833 the sysApplElmtRun entry is copied to sysApplElmtPastRun, 1834 the wwwApplElmtRun entry is copied to wwwApplElmntPastRun. 1836 Entries remain in this table until they are aged out when 1837 either the number of entries in the table reaches a 1838 maximum as determined by sysApplElmtPastRunMaxRows, or 1839 when an entry has aged to exceed a time limit as set by 1840 sysApplElmtPastRunTblTimeLimit. When aging out entries, 1841 the oldest entry, as determined by the value of 1842 sysApplElmtPastRunTimeEnded, will be removed first. 1844 The table is indexed by sysApplElmtPastRunInvocID, 1845 sysApplElmtPastRunIndex to make it easy to locate all 1846 previously executed processes of a particular invoked 1847 application. 1849 This table extends the sysApplElmtPastRunTable of the 1850 sysApplMib/applMib framework with attributes specific 1851 to www applications." 1852 ::= { wwwApplRun 4 } 1854 wwwApplElmtPastRunEntry OBJECT-TYPE 1855 SYNTAX WwwApplElmtPastRunEntry 1856 MAX-ACCESS not-accessible 1857 STATUS current 1858 DESCRIPTION 1859 "The logical row describing a process which was 1860 previously executed on this host as part of a 1861 www application. The entry is basically copied 1862 from the wwwApplElmtRunTable when the process 1863 terminates. Hence, the entry's value for 1864 sysApplElmtPastRunIndex is the same as its value 1865 was for sysApplElmtRunIndex. Only those 1866 processes which could be associated with an 1867 identified application are included in this table." 1868 INDEX { sysApplElmtPastRunInvocID, sysApplElmtPastRunIndex } 1869 ::= { wwwApplElmtPastRunTable 1 } 1871 WwwApplElmtPastRunEntry ::= SEQUENCE 1872 { 1873 wwwApplElmtPastRunBogus Integer32 1874 } 1876 wwwApplElmtPastRunBogus OBJECT-TYPE 1877 SYNTAX Integer32 1878 MAX-ACCESS read-only 1879 STATUS current 1880 DESCRIPTION 1881 "A place holder to satisfy the MIB compiler." 1882 ::= { wwwApplElmtPastRunEntry 1} 1884 -- 1885 -- wwwRelate 1886 -- 1887 -- Objects which define relationships to other MIB modules. 1888 -- 1889 wwwRelate OBJECT IDENTIFIER ::= { wwwMIBObjects 6 } 1891 -- 1892 -- 1893 -- Conformance and compliance definitions. 1894 -- 1895 -- 1896 wwwMIBEntityGroup OBJECT-GROUP 1897 OBJECTS 1898 { 1899 wwwEntityDescription, 1900 wwwEntityContact, 1901 wwwEntityProtocol, 1902 wwwEntityProtocolVersion, 1903 wwwEntityName, 1904 wwwEntityAddress, 1905 wwwEntityType 1906 } 1907 STATUS current 1908 DESCRIPTION 1909 "" 1910 ::= { wwwMIBGroups 1 } 1912 wwwMIBSummaryGroup OBJECT-GROUP 1913 OBJECTS 1914 { 1915 wwwSummaryInRequests, 1916 wwwSummaryOutRequests, 1917 wwwSummaryRequestErrors, 1918 wwwSummaryRequestDiscards, 1919 wwwSummaryInResponses, 1920 wwwSummaryOutResponses, 1921 wwwSummaryResponseDiscards, 1922 wwwSummaryInUnknowns, 1923 wwwSummaryInControlBytes, 1924 wwwSummaryInContentBytes, 1925 wwwSummaryOutControlBytes, 1926 wwwSummaryOutContentBytes 1927 } 1928 STATUS current 1929 DESCRIPTION 1930 "" 1931 ::= { wwwMIBGroups 2 } 1933 wwwMIBRequestGroup OBJECT-GROUP 1934 OBJECTS 1935 { 1936 wwwRequestInCount, 1937 wwwRequestInControlBytes, 1938 wwwRequestInContentBytes, 1939 wwwRequestInLastTime, 1940 wwwRequestOutCount, 1941 wwwRequestOutControlBytes, 1942 wwwRequestOutContentBytes, 1943 wwwRequestOutLastTime 1944 } 1945 STATUS current 1946 DESCRIPTION 1947 "" 1948 ::= { wwwMIBGroups 3 } 1950 wwwMIBResponseGroup OBJECT-GROUP 1951 OBJECTS 1952 { 1953 wwwResponseInCount, 1954 wwwResponseInControlBytes, 1955 wwwResponseInContentBytes, 1956 wwwResponseInLastTime, 1957 wwwResponseOutCount, 1958 wwwResponseOutControlBytes, 1959 wwwResponseOutContentBytes, 1960 wwwResponseOutLastTime 1961 } 1962 STATUS current 1963 DESCRIPTION 1964 "" 1965 ::= { wwwMIBGroups 4 } 1967 wwwMIBDocumentGroup OBJECT-GROUP 1968 OBJECTS 1969 { 1970 wwwDocNameIndex, 1971 wwwDocFilterRegexp, 1972 wwwDocFilterStatus, 1973 wwwDocInstallPkg, 1974 wwwDocInstallElmt, 1975 wwwDocName, 1976 wwwDocType, 1977 wwwDocFirstAccessTimeStamp, 1978 wwwDocLastAccessTimeStamp, 1979 wwwDocLastAccessResponseType, 1980 wwwDocInBytes, 1981 wwwDocOutBytes, 1982 wwwDocInCount, 1983 wwwDocOutCount, 1984 wwwDocSpecific, 1985 wwwDocStatus 1986 } 1987 STATUS current 1988 DESCRIPTION 1989 "" 1990 ::= { wwwMIBGroups 5 } 1992 -- wwwMIBRelateGroup OBJECT-GROUP 1993 -- OBJECTS 1994 -- { 1995 -- } 1996 -- STATUS current 1997 -- DESCRIPTION 1998 -- "" 1999 -- ::= { wwwMIBGroups 6 } 2001 wwwMIBApplGroup OBJECT-GROUP 2002 OBJECTS 2003 { 2004 wwwApplInstallPkgBogus, 2005 wwwApplInstallElmtBogus, 2006 wwwApplRunBogus, 2007 wwwApplPastRunBogus, 2008 wwwApplElmtRunBogus, 2009 wwwApplElmtPastRunBogus 2010 } 2011 STATUS current 2012 DESCRIPTION 2013 "" 2014 ::= { wwwMIBGroups 7 } 2016 -- 2017 -- [## need to define remaining attributes here. ##] 2018 -- 2020 wwwCompliance MODULE-COMPLIANCE 2021 STATUS current 2022 DESCRIPTION 2023 "The compliance statement for SNMP entities 2024 which implement the WWW-MIB." 2025 MODULE -- this module 2026 MANDATORY-GROUPS 2027 { 2028 wwwMIBEntityGroup, 2029 wwwMIBSummaryGroup, 2030 wwwMIBRequestGroup, 2031 wwwMIBResponseGroup, 2032 wwwMIBDocumentGroup, 2033 -- wwwMIBRelateGroup, 2034 wwwMIBApplGroup 2035 } 2036 ::= { wwwMIBCompliances 1 } 2038 END 2040 11. Verification 2042 The MIB module is verified using the SMICng MIB compiler by 2043 Dave Perkins. The following include file can be used along 2044 with the SMICng compiler. Besides the standard MIBs released 2045 with the SMICng distribution, the RMON2-MIB and SYSAPPL-MIB 2046 are require for the compilation. 2048 11.1. SMICng Include File 2050 12. References 2052 [] Kalbfleisch, C., "Applicability of Standards Track MIBs to 2053 Management of World Wide Web Servers", RFC-2039, OnRamp 2054 Technologies, November 1996 2056 [] Anonymous, "Logging in the W3C httpd", 2057 http://www.w3.org/hypertext/WWW/Daemon/User/Config/Logging.html, 2058 W3C, July 1995 2060 [] McCloghrie, K., and M. Rose, Editors, "Management Information 2061 Base for Network Management of TCP/IP-based internets: MIB- 2062 II", STD 17, RFC 1213, Hughes LAN Systems, Performance 2063 Systems International, March 1991. 2065 [] Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC 1514, 2066 Network Innovations, Intel Corporation, Carnegie Mellon 2067 University, September 1993 2069 [] Kille, S., and N. Freed, "Network Services Monitoring MIB", 2070 RFC 1565, ISODE Consortium, Innosoft, January 1994 2072 [] Saperia, J., C. Krupczak, R. Sturm, and J. Weinstock, "Definition 2073 of Managed Objects for Applications", 2074 draft-ietf-applmib-sysapplmib-02.txt, BGS Systems, Empire 2075 Technologies, Enterprise Management Professional Services, 2076 Bellcore, May 1996 2078 [] Krupczak, C. and S. Waldbusser, "Applicability of Host Resources 2079 MIB to Application Management", Empire Technologies, Inc., 2080 International Network Services, October 1995. 2082 [] Kille, S., and N. Freed, "Mail Monitoring MIB", RFC 1566, ISODE 2083 Consortium, Innosoft, January 1994 2085 [] Mansfield, G., and S. Kille, "X.500 Directory Monitoring MIB", 2086 RFC 1567, AIC Systems Laboratory, ISODE Consortium, January 1994 2088 [] Postel, J., and Reynolds, J.K., "File TransferProtocol (FTP).", 2089 RFC 959, USC/ISI, October 1985. 2091 [] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A 2092 Proposed Standard for the Stream-Based Transmission of News", RFC 2093 977, UC San Diego & UC Berkeley, February 1986. 2095 [] Horton, M., and R. Adams, "Standard for interchange of USENET 2096 messages", RFC 1036, AT&T Bell Laboratories, Center for Seismic 2097 Studies, December 1987. 2099 [## Addition references are needed here for RMON-2, FTP, NNTP, GOPHER, 2100 WAIS, HTTP 1.1 ##] 2102 13. Acknowledgments 2104 This document was produced by the Application MIB working group and 2105 the members of the http-mib@onramp.net mailing list. 2107 The authors gratefully acknowledges the comments of the following 2108 individuals: 2110 Randy Preshun 2111 John Saperia 2112 Cheryl Krupczak 2114 14. Security Considerations 2116 Security issues are not discussed in this memo. 2118 15. Appendix - Applicability to other services 2120 This MIB is defined solely for the management of WWW servers, clients 2121 and proxies. It is realized however that the MIB may be directly 2122 applicable to other network information retrieval services. This 2123 appendix outlines how the MIB might be utilized for a number of 2124 other services. This may or may not provide the desired level of 2125 management of these types of applications. In some instances, a 2126 separate MIB may need to be defined for the service. 2128 15.1. FTP 2130 The File Transfer Protocol allows people to transfer file from one 2131 system to another system. The protocol is connection-oriented 2132 established by TCP. The client is responsible to generate requests 2133 and interpreted the responses from the server. 2134 The server interpreted requests and generate responses. 2136 The protocol consists two channels: 2138 o Control connection on which the traffic consists of service 2139 commands (the requests) and of replies (responses). The service 2140 commands reflect the operations such as the authentication 2141 (login-procedure), the actual file transfer and the 2142 logout-procedure. The replies are used to ensure the 2143 synchronisation of requests, actions in the file transfer process 2144 and guarantee that the user always knows the current state of the 2145 server. There is at least one reply to each service command. 2147 o Data connection on which the actual data transfer takes place. 2149 The mapping of an FTP-entity onto the WWW-MIB is straight forward. 2150 Global and administrative FTP-entity information can be mapped onto 2151 the entity table. The network traffic can be map onto the tables 2152 in the statistics group whereby the service commands are mapped on 2153 requests and the replies are mapped on responses. With respect to the 2154 byte counters the bytes transferred in the control connection is 2155 counted in the HeaderByte counters and the bytes transferred at the 2156 data connection is counted in the DataByte counters. The parameters 2157 with respect to the transferred files can be mapped onto the document 2158 table. 2160 15.2. NNTP 2162 The Network News Transfer Protocol is used for distribution, 2163 inquiry, retrieval, and posting of news articles. The news articles 2164 are stored in a central database allowing a subscriber to select 2165 only those items he wishes to read. Indexing, cross-referencing, 2166 and expiration of aged messages are also provided. 2168 The protocol consists of the same Request/Response paradigm like 2169 HTTP and FTP. Commands are given as requests and can be followed by 2170 parameters. The responses consist of two different types, a status 2171 response and a text responses. 2173 The mapping of a NNTP-entity is a little more complex than FTP, 2174 but still possible. Global and administrative information can be 2175 mapped onto the entity table. The network traffic can be map onto 2176 the tables in the statistics group whereby the commands are mapped 2177 on the requests and the status responses are mapped on the responses. 2178 The implementor should take special care of the mapping of the byte 2179 counters. All 'ControlByte' counters are counting the bytes which are 2180 not the body part of a message. The body part bytes has to be mapped 2181 onto the 'DataByte' counters. For details about the syntax of a 2182 message is referred to RFC 1036 [## ref TBD ##]. The text responses 2183 has to be mapped on the document table by seeing them as the 2184 transferred information. 2186 15.3. GOPHER 2188 The Gopher protocol is a distributed document search and retrieval 2189 protocol and is also based on the Request/Response paradigm. 2190 The protocol is stateless whereby faults the user does not force 2191 to start over. 2193 Clients with the Gopher protocol connect themselves to servers 2194 and generate requests. The servers respond with the requested 2195 informations which is displayed by the gopher client. This type 2196 of interaction in gopher is called transactions. 2198 The commands within gopher are determined by the server, because 2199 he responds with the information of which command is used for a 2200 particular information retrieval command. This feature gives gopher 2201 a wide variaty of possible commands. 2203 The mapping of the Gopher entity is almost straight forward. Global 2204 and administrative information can be mapped onto the entity table. 2205 The network traffic needs special attention to map it onto the tables 2206 in the statistics group whereby the transaction of the message 2207 towards the server is mapped on the requests and the transaction 2208 message coming from the server is mapped on the responses. Although 2209 the variaty of requests can be enormous the mapping can be done 2210 straight forward, but if requests are directly getting documents 2211 you can map them in the document table. For this MIB it is preferred 2212 to map them on the responses. 2214 15.4. WAIS 2216 [## TBD ##] 2218 15.5. Archie 2220 [## TBD ##] 2222 16. Appendix - Todo List 2224 [## This section will be removed when the document is complete 2225 because all items that are "to do" will have been done! ##] 2227 16.1. Resolve wwwDocName usage and TC definition 2228 The wwwDocNameName value likely needs to be limited to around 100 2229 bytes in length because it is an index. The wwwDocName could however 2230 represent a longer number of bytes. One option is to define it as 2231 OCTET STRING so it can be as long as necessary, but rfc-1902 2232 indicates there may be interoperability issues with OCTET STRING 2233 greater than 255 bytes. 2235 16.2. Terminology 2236 Flush out section on terminology 2238 16.3. Handle illegal index values 2239 Determine what to do with illegal index values for pointers to 2240 other tables, specifically for sysAppl. 2242 16.4. Handle NSM to sysApplMIB relationship 2243 Determine where nsmToSysApplElmtRunTable should be defined. 2244 Options appear to be sysApplMIB, this MIB or a separate document. 2246 Currently the definition has been moved to applMib. 2248 16.5. Handle applIndex 2249 Currently the wwwEntityTable is indexed with applIndex from 2250 NSM. This causes potential problems in certain implementations and 2251 configuration if the WWW-MIB implementer does not implement the 2252 applTable and on the same machine an NSM agent is provided by 2253 the OS or other vendor. In this case, there is potential for 2254 applTable indexes to conflict with wwwEntityTable indexes which 2255 do not actually extend the applTable information. The NSM indicates 2256 it is to be the base for all network service applications. WWW-MIB 2257 clearly fits this definition. Unfortunately, a number of implementers 2258 have indicated that they do not plan to implement NSM. So, the 2259 options seem to be to clearly document the situation and perhaps 2260 propose some suggested index values for applIndex in the 2261 wwwEntityTable, or require NSM to be implemented. The document 2262 currently indicates that "wording" for the applIndex usage in 2263 wwwEntityTable needs to be defined. 2265 The editor beleive that the applIndex should be used for this table 2266 and that either the applTable should be required, or index values 2267 should be suggested for the wwwEntityTable such that conflicts can 2268 be avoided. 2270 16.6. Identify attributes for sysAppl framework 2271 Currently a skeleton of tables has been defined that extend the 2272 sysAppl/applMib framework. The idea is that the sysAppl framework 2273 will apply to a portion of the MIB. Attributes that are desired 2274 for www, but not defined in either sysAppl or applMib will be 2275 placed within these skeleton tables. 2277 16.7. Regular Expression 2278 Pick as standard definition for regular expressions for the 2279 wwwDocFilter. 2281 16.8. Proxy Entity 2282 Determine additional attributes that are needed to handle proxy in 2283 terms of an entity. 2285 16.9. Proxy Documents 2286 Determine whether the represenation of the wwwDoc tables is 2287 sufficient or necessary for proxy. 2289 16.10. Handle all [##...##] 2290 Remove and resolve all [##...##] notation. 2292 17. Authors' Address 2294 Carl W. Kalbfleisch 2295 OnRamp Technologies, Inc. 2296 Email: cwk@onramp.net 2297 1950 Stemmons Frwy 2298 2026 INFOMART 2299 Dallas, TX 75207 2300 USA Tel: (214) 672-7246 2301 cwk@onramp.net Fax: (214) 672-7275 2303 Harrie Hazewinkel 2304 Centre for Earth Observation 2305 Institute for Space Applications 2306 Joint Research Centre of the E.C. 2307 TP. 950 2308 Ispra 21020 (VA) Italy Tel: +39+(0)332+789384 2309 harrie.hazewinkel@jrc.it Fax: +39+(0)332+785500 2311 Juergen Schoenwaelder 2312 Computer Science Department 2313 University of Twente 2314 P.O. Box 217, NL-7500 AE Enschede 2315 The Netherlands. Tel: +31-53-489-3678 2316 schoenw@cs.utwente.nl Fax: +31-53-489-3247 2318 Table of Contents 2320 1. Abstract..........2 2321 2. The SNMPv2 Network Management Framework..........2 2322 2.1. Object Definitions..........2 2323 3. Notation..........3 2324 4. A Note on Terminology..........3 2325 5. Introduction..........4 2326 6. WWW Entities..........4 2327 6.1. WWW Server..........5 2328 6.2. WWW Client..........5 2329 6.3. WWW Proxy..........5 2330 6.4. WWW Cached Proxy..........6 2331 7. HTTP Message..........6 2332 8. Relationship to other Standards Efforts..........6 2333 8.1. Relationship to NSM..........7 2334 8.2. Relationship to sysAppl and applMib..........7 2335 8.3. Document relation to sysApplInstall..........7 2336 8.4. Usage example for NSM to sysApplMIB relationship..........7 2337 9. Structure of the MIB..........8 2338 9.1. The systems group..........9 2339 9.2. The Statistics group..........9 2340 9.2.1. SummaryTable..........9 2341 9.2.2. RequestTable..........9 2342 9.2.3. ResponseTable..........9 2343 9.3. The Document group..........10 2344 9.3.1. wwwDocNameTable..........10 2345 9.3.2. wwwDocTable..........10 2346 9.3.3. wwwDocFilterTable..........10 2347 9.4. The Error group..........10 2348 9.5. The Application group..........10 2349 9.6. The Relation group..........10 2350 10. Definitions..........10 2351 11. Verification..........39 2352 11.1. SMICng Include File..........39 2353 12. References..........39 2354 13. Acknowledgments..........40 2355 14. Security Considerations..........40 2356 15. Appendix - Applicability to other services..........40 2357 15.1. FTP..........40 2358 15.2. NNTP..........41 2359 15.3. GOPHER..........41 2360 15.4. WAIS..........42 2361 15.5. Archie..........42 2362 16. Appendix - Todo List..........42 2363 16.1. Resolve wwwDocName usage and TC definition..........42 2364 16.2. Terminology..........42 2365 16.3. Handle illegal index values..........42 2366 16.4. Handle NSM to sysApplMIB relationship..........42 2367 16.5. Handle applIndex..........43 2368 16.6. Identify attributes for sysAppl framework..........43 2369 16.7. Regular Expression..........43 2370 16.8. Proxy Entity..........43 2371 16.9. Proxy Documents..........43 2372 16.10. Handle all [##...##]..........43 2373 17. Authors' Address..........43