idnits 2.17.1 draft-ietf-applmib-wwwmib-07.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): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 112 lines 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1860 has weird spacing: '...for the purpo...' -- 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 (March 1, 1998) is 9552 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Downref: Normative reference to an Informational RFC: RFC 1630 (ref. '5') ** Obsolete normative reference: RFC 1738 (ref. '6') (Obsoleted by RFC 4248, RFC 4266) ** Downref: Normative reference to an Informational RFC: RFC 1945 (ref. '7') ** Obsolete normative reference: RFC 2068 (ref. '8') (Obsoleted by RFC 2616) ** Downref: Normative reference to an Informational RFC: RFC 2039 (ref. '10') == Outdated reference: A later version (-11) exists of draft-ietf-applmib-mib-04 ** Obsolete normative reference: RFC 977 (ref. '13') (Obsoleted by RFC 3977) ** Downref: Normative reference to an Informational RFC: RFC 2054 (ref. '14') ** Downref: Normative reference to an Informational RFC: RFC 2055 (ref. '15') Summary: 22 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects for WWW Services 4 March 1, 1998 6 8 Harrie Hazewinkel 9 Joint Research Centre of the E.C. 10 harrie.hazewinkel@jrc.it 12 Carl W. Kalbfleisch 13 Verio, Inc. 14 cwk@verio.net 16 Juergen Schoenwaelder 17 TU Braunschweig 18 schoenw@ibr.cs.tu-bs.de 20 Status of this Memo 22 This document is an Internet-Draft. Internet-Drafts are working 23 documents of the Internet Engineering Task Force (IETF), its areas, 24 and its working groups. Note that other groups may also distribute 25 working documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as ``work in progress.'' 32 To learn the current status of any Internet-Draft, please check the 33 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 34 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 35 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 36 ftp.isi.edu (US West Coast). 38 Distribution of this document is unlimited. Please send comments to 39 the Application MIB Working Group, . 41 Copyright Notice 43 Copyright (C) The Internet Society (1998). All Rights Reserved. 45 1. Abstract 47 This memo defines an experimental portion of the Management 48 Information Base (MIB) for use with network management protocols in 49 the Internet Community. In particular it describes a set of objects 50 for managing World-Wide Web (WWW) services. This MIB extends the 51 application management framework defined by the System Application 52 Management MIB (SYSAPPL-MIB) and the Application Management MIB 53 (APPLICATION-MIB). The protocol statistics defined in the WWW Service 54 MIB are based on an abstract document transfer protocol (DTP). This 55 memo also defines a mapping of the abstract DTP to HTTP and FTP. 56 Additional mappings may be defined in the future in order to use this 57 MIB with other document transfer protocols. It is anticipated that 58 such future mappings will be defined in separate RFCs. 60 2. The SNMPv2 Network Management Framework 62 The SNMP Network Management Framework presently consists of three 63 major components. They are: 65 o the SMI, described in RFC 1902 [1] - the mechanisms used for 66 describing and naming objects for the purpose of management. 68 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed 69 objects for the Internet suite of protocols. 71 o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol 72 for accessing managed objects. 74 The Framework permits new objects to be defined for the purpose of 75 experimentation and evaluation. 77 2.1. Object Definitions 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. Objects in the MIB are 81 defined using the subset of Abstract Syntax Notation One (ASN.1) 82 defined in the SMI [1]. In particular, each object type is named by 83 an OBJECT IDENTIFIER, an administratively assigned name. The object 84 type together with an object instance serves to uniquely identify a 85 specific instantiation of the object. For human convenience, we often 86 use a textual string, termed the object descriptor, to refer to the 87 object type. 89 3. Terminology 91 This section defines the terminology used throughout this document. 93 o The 'World-Wide Web' (WWW) is a world wide information system 94 which is based on the concept of documents that are linked 95 together by embedding references (links) to other local or 96 remote documents. 98 o A 'document' is a coherent piece of data which is accessible in 99 the World-Wide Web. No assumptions are made about the content or 100 the type of a document. 102 o A 'Uniform Resource Locator' (URL) is a formatted string 103 representation for a document available via the Internet. URLs 104 are used to express references between documents. For the syntax 105 and semantics of the URL string representation is referred to 106 RFC 1630 [5] and RFC 1738 [6] 108 o A 'Document Transfer Protocol' (DTP) is a protocol used within 109 the World-Wide Web to invoke actions on documents. The DTP is an 110 abstraction from real protocols, such as HTTP [7,8] or FTP [9]. 112 o A 'request' is a DTP protocol operation which is targeted to a 113 'document' and invokes an action on the target document. The 114 request type specifies the action that should be performed. A 115 request can have a document associated to it. 117 o A 'response' is a DTP protocol operation which is returned as a 118 result of a previous (and associated) request. The response 119 status indicates if the requested action was successful or if 120 errors occurred. A response can have a document associated to 121 it. 123 o A 'WWW service' is a set of actions that can be invoked on a 124 document. Typical actions are the transfer of documents or the 125 retrieval of administrative information about documents. WWW 126 services are provided by means of a DTP. A WWW service can be 127 identified by the DTP protocol used to invoke services and the 128 transport endpoint used by that protocol. 130 o A 'client' is a program which establishes connections for the 131 purpose of sending requests and receiving responses. 133 o A 'server' is a program that accepts connections in order to 134 service requests by sending back responses. 136 o A 'proxy' is an intermediary program which acts as both a server 137 and a client for the purpose of making requests on behalf of 138 other clients. Requests are serviced internally or by passing 139 them on, with possible translation, to other servers. 141 o A 'caching proxy' is a proxy with the capability of locally 142 storing responses to associated requests. A caching proxy can 143 respond to similar requests with a previously stored response. 145 4. Overview 147 The World-Wide Web (WWW) is a global network of information. 148 Information is stored in documents, which can have various formats, 149 including hyper-text and multi-media documents. Access to these 150 documents is provided by servers which are located all around the 151 world and are linked to each other via hyper-links embedded in 152 documents. 154 The usability of the World-Wide Web depends largely on the 155 performance of the services realized by these servers. The services 156 are typically monitored through log files. This becomes a difficult 157 task when a single organization is responsible for a large number of 158 services. It is therefore desirable to treat WWW services as objects 159 that can be managed by using the Internet network management 160 framework [10]. 162 4.1. Purpose and Requirements 164 The goal of this MIB is to define a standardized set of objects which 165 lead to integrated and improved performance and fault management in a 166 heterogenous environment of WWW services. This MIB focuses on the 167 service oriented view. It does not deal with the process oriented 168 view, which is covered by the System Application MIB [11] and the 169 Application MIB [12]. 171 This document defines a set of managed objects to monitor WWW 172 services for short-term operational purposes, such as problem 173 detection and troubleshooting. No attempts are made here to cover 174 accounting or hit metering issues. 176 The scope of the MIB is further limited by the requirement that an 177 implementation conforming to this MIB must be possible without 178 putting a huge CPU or memory burden on the WWW server implementation. 180 In addition, this MIB does not cover WWW service configuration. 182 Server software has become an open market where competing vendors 183 constantly invent new features in order to shape their products. It 184 is therefore not possible to reach consensus on a common way to 185 configure WWW services at this point in time. 187 4.2. Relationship to other Standards Efforts 189 The WWW service MIB fits into the application management architecture 190 defined in the System Application MIB [11]. The System Application 191 MIB and the Application MIB [12] use a process oriented view, where 192 an application is viewed as a collection of processes. The WWW 193 service MIB described in this memo uses a service oriented view, 194 which looks at the services provided by a set of processes. 196 The relationship between the process oriented view and the service 197 oriented view is a many-to-many relationship, because one process can 198 implement multiple services and multiple services can be implemented 199 by a single set of processes. The Application Management MIB [12] 200 contains generic mapping tables, which map back and forth between 201 both views. 203 4.3. WWW Services 205 The MIB is organized around the concept of WWW services. WWW services 206 are a set of actions that can be invoked on a document. A WWW service 207 is provided or used by either a client, a server or a proxy. Clients 208 send out requests for information to server or proxy server. Servers 209 receive, process and respond to requests received from clients. 210 Servers usually have access to local documents, which can be 211 transfered to clients. 213 A proxy is a special server, who acts as both a server and a client 214 for the purpose of making requests on behalf of other clients. A 215 proxy is able to translate between the client and the origin server. 216 A proxy might also interact with other information retrieval system, 217 like for example databases. 219 The MIB defined in this memo distinguishes between outgoing and 220 incoming requests and responses. This allows to obtain statistics for 221 clients, servers and proxies with a single set of objects. 223 A special proxy server is the caching proxy, which maintains a cache 224 of previously received documents in order to reduce the bandwidth 225 used by World-Wide Web clients. One interesting piece of management 226 information is the percentage of requests that were served from the 227 cache of the caching proxy (hits/miss-ratio). This ratio is not 228 contained explicitly in this MIB. Instead, the ratio can be derived 229 from the objects that count incoming and outgoing requests and 230 responses. 232 4.4. Document Transfer Protocol 234 The MIB is based on the concept of an abstract document transfer 235 protocol (DTP). The purpose of the abstract document transfer 236 protocol is to make the MIB definitions independent from concrete 237 protocols, like the Hypertext Transfer Protocol (HTTP) [7,8] or the 238 File Transfer Protocol (FTP) [9]. 240 The abstract document transfer protocol makes the following 241 assumptions about a concrete transfer protocol: 243 o The transfer protocol uses a request/response style of 244 interactions. 246 o Every request contains a request type, which defines the 247 operations performed by the receiving server. The request type 248 is represented by an OCTET STRING. It might be necessary to 249 define a translation into an OCTET STRING value for protocols 250 that use numbers to identify request types. 252 o A response contains a status code, which indicates if the 253 request was processed successfully or which error occured. The 254 status code is represented as an INTEGER value. It might be 255 necessary to define a mapping for protocols that do not use an 256 INTEGER status code. 258 o A transfer protocol can send multiple responses for a single 259 request. Multiple responses are counted separately in the 260 protocol statistics group. 262 A primary response has to be identified for the document 263 statistics. The primary response is the response that indicates 264 whether the request was successful. 266 Section 7 of this memo defines a mapping of the document transfer 267 protocol to the HTTP protocol and the FTP protocol. Mappings to other 268 protocols, like NNTP [13] or WebNFS [14,15] might be defined in the 269 future. 271 5. Structure of the MIB 273 This section presents the structure of the MIB. The objects are 274 arranged into the following groups: 276 o service information 278 o protocol statistics 280 o document statistics 282 5.1. Service Information Group 284 The service information group consists of a single table describing 285 all the WWW services managed by the SNMP agent. The service table 286 contains administrative network management information for 287 (potentially) multiple WWW services running on a single host. It also 288 contains information for all services within virtual domains of a 289 host. The columnar objects in the table can be divided into two main 290 groups: 292 o global administrative information of the service, such as 293 service contact person, and 295 o network information, such as the transfer protocol. 297 5.2. Protocol Statistics Group 299 The protocol statistics group provides network management information 300 about the traffic received or transmitted by a WWW service. This 301 group contains counters related to DTP protocol operations and 302 consists of five tables: 304 o The wwwSummaryTable contains a set of network traffic related 305 counters. The table provides a summarization of the network 306 traffic and protocol operations related to a WWW service. It is 307 well recognized that certain variables are redundant with 308 respect to the request and response tables, but they are added 309 to provide an operator a quick overview and to reduce SNMP 310 network traffic. 312 o The wwwRequestInTable contains detailed information about 313 incoming requests. Every particular request type is counted 314 separately. 316 o The wwwRequestOutTable contains detailed information about 317 outgoing requests. Every particular request type is counted 318 separately. 320 o The wwwResponseInTable contains detailed information about 321 incoming responses. Every particular response type is counted 322 separately. 324 o The wwwResponseOutTable contains detailed information about 325 outgoing responses. Every particular response type is counted 326 separately. 328 5.3. Document Statistics Group 330 The document group contains information about the documents which 331 were accessed in the past. The group provides four types of 332 statistics. 334 1. Details about the last N attempts to invoke actions on 335 documents. 337 2. The Top N documents sorted by the number of actions invoked on 338 them computed over a time interval. 340 3. The Top N documents sorted by the number of content bytes 341 transferred computed over a time interval. 343 4. Summary statistics computed over a time interval. 345 The Top N document statistics are collected in buckets in order to 346 reduce agent resources and to allow a manager to detect changes in 347 the service usage pattern. Buckets are filled over a configurable 348 time interval. The agent computes the Top N statistics and starts a 349 new bucket once the time interval for the bucket has passed. The time 350 interval if configurable for each WWW service. 352 The document statistics group associates a response type to the 353 request which invoked an action. In case a DTP sends multiple 354 responses, the primary response must be used to derive the response 355 type of the request/response interaction. 357 The group consist of the following tables: 359 o The wwwDocCtrlTable provides the manager a means to limit the 360 document statistic tables in size and to control the expiration 361 and creation of buckets. 363 o The wwwDocLastNTable provides the manager information about the 364 last N documents which where accessed. The table lists the 365 documents attempted to read together with the request and 366 response type of the DTP and a status message. The request and 367 response types provide a manager information of how attempts to 368 invoke actions were handled by the DTP. The status message 369 object provides human readable text to further describe the 370 response type. 372 The number of documents in the wwwDocLastNTable is controlled by 373 the wwwDocCtrlLastNSize object in the wwwDocCtrlTable. The 374 wwwDocCtrlLastNStatus object of the wwwDocCtrlTable allows the 375 management application to disable table updates so that it can 376 read a consistent snapshot of a fast changing wwwDocLastNTable. 378 o The wwwDocBucketTable lists the buckets of statistical 379 information that have been collected. An entry in the 380 wwwDocBucketTable contains the creation timestamp of the bucket 381 as well as summary information (number of accesses, number of 382 documents accessed and number of bytes transferred). 384 The time interval is controlled by the 385 wwwDocCtrlBucketTimeInterval object of the wwwDocCtrlTable. The 386 maximum number of buckets maintained by the SNMP agent for a 387 particular WWW service is controlled by the wwwDocCtrlBuckets 388 object of the wwwDocCtrlTable. 390 o The wwwDocAccessTopNTable provides the manager an overview of 391 the top N documents which were accessed while statistics were 392 collected for a particular bucket. The wwwDocAccessTopNTable is 393 sorted by the number of read attempts per document. The maximum 394 number of entries in the wwwDocAccessTopNTable is controlled by 395 the wwwDocCtrlTopNSize object. 397 o The wwwDocBytesTopNTable provides the manager an overview of the 398 top N documents which caused most of the network traffic while 399 statistics were collected for a particular bucket. The 400 wwwDocBytesTopNTable is sorted by the number of bytes 401 transfered. The maximum number of entries in the 402 wwwDocBytesTopNTable is controlled by the wwwDocCtrlTopNSize 403 object. 405 The Top N statistics and the parameters of the underlying bucket are 406 not visible in the MIB as long as the bucket is filled up. Instead, 407 the following steps must be taken when the time interval for a 408 buckets has passed: 410 1. A new entry in the wwwDocBucketTable is created to summarize the 411 document statistics for that time interval. 413 2. The corresponding entries in the wwwDocAccessTopNTable and the 414 wwwDocBytesTopNTable are computed and made available. 416 3. If the resulting number of entries in the wwwDocBucketTable for 417 the WWW service now exceeds wwwDocCtrlBuckets, then the oldest 418 bucket for this WWW service and all corresponding entries in the 419 wwwDocBucketTable, wwwDocAccessTopNTable, and 420 wwwDocBytesTopNTable are deleted. 422 Note that a bucket usually contains much more data than displayed in 423 the Top N tables. The number of entries in the Top N table for a 424 bucket is controlled by wwwDocCtrlTopNSize, while the number of 425 entries in a bucket depends on the number of actions invoked on 426 documents within the time interval over which a bucket is filled up. 427 It is therefore suggested to discard the data associated with a 428 bucket once the entries for the wwwDocBucketTable, 429 wwwDocAccessTopNTable and wwwDocBytesTopNTable have been calculated. 431 6. Definitions 433 WWW-MIB DEFINITIONS ::= BEGIN 435 IMPORTS 436 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 437 Counter32, Counter64, Integer32, Unsigned32 438 FROM SNMPv2-SMI 440 TEXTUAL-CONVENTION, DisplayString, TimeStamp, 441 DateAndTime, TimeInterval 442 FROM SNMPv2-TC 444 MODULE-COMPLIANCE, OBJECT-GROUP 445 FROM SNMPv2-CONF 447 Utf8String 448 FROM SYSAPPL-MIB; 450 wwwMIB MODULE-IDENTITY 451 LAST-UPDATED "9703010000Z" 452 ORGANIZATION "Application MIB Working Group" 453 CONTACT-INFO 454 " Harrie Hazewinkel 455 Postal: Joint Research Centre of the E.C. 456 via Fermi - Ispra 21020 (VA) 457 Italy 459 Tel: +39+(0)332+789384 460 Fax: +39+(0)332+785500 461 E-mail: harrie.hazewinkel@jrc.it 463 Carl W. Kalbfleisch 465 Postal: Verio, Inc. 466 1950 Stemmons Freeway 467 Suite 2004 - Infomart 468 Dallas, TX 75207 469 US 471 Tel: +1 972 238-8303 472 Fax: +1 972 238-0268 473 E-mail: cwk@verio.net 475 Juergen Schoenwaelder 477 Postal: TU Braunschweig 478 Bueltenweg 74/75 479 38106 Braunschweig 480 Germany 482 Tel: +49 531 391-3683 483 Fax: +49 531 489-5936 484 E-mail: schoenw@ibr.cs.tu-bs.de" 485 DESCRIPTION 486 "This WWW service MIB module is applicable to services 487 realized by a family of 'Document Transfer Protocols' 488 (DTP). Examples of DTPs are HTTP and FTP." 489 -- Get real registration number from IANA. 490 -- ::= { mib-2 XXXX } 491 ::= { mib-2 8080 } 493 -- 494 -- Object Identifier Assignments 495 -- 497 wwwMIBObjects OBJECT IDENTIFIER ::= { wwwMIB 1 } 498 wwwMIBConformance OBJECT IDENTIFIER ::= { wwwMIB 2 } 500 -- 501 -- Textual Conventions 502 -- 504 WwwRequestType ::= TEXTUAL-CONVENTION 505 STATUS current 506 DESCRIPTION 507 "The WwwRequestType defines the textual identification of 508 request types used by a document transfer protocol. For 509 the proper values for a given DTP, refer to the protocol 510 mappings for that DTP." 511 SYNTAX OCTET STRING (SIZE (1..40)) 513 WwwResponseType ::= TEXTUAL-CONVENTION 514 STATUS current 515 DESCRIPTION 516 "The WwwResponseType defines the different response values 517 used by document transfer protocols. For the proper values 518 for a given DTP, refer to the protocol mappings for that 519 DTP." 520 SYNTAX Integer32 (0..2147483647) 522 WwwOperStatus ::= TEXTUAL-CONVENTION 523 STATUS current 524 DESCRIPTION 525 "The operational status of a WWW service. 'down' indicates 526 that the service is not available. 'running' indicates 527 that the service is operational and available. 'halted' 528 indicates that the service is operational but not 529 available. 'congested' indicates that the service is 530 operational but no additional inbound associations can be 531 accommodated. 'restarting' indicates that the service is 532 currently unavailable but is in the process of restarting 533 and will be available soon." 534 SYNTAX INTEGER { 535 down(1), 536 running(2), 537 halted(3), 538 congested(4), 539 restarting(5) 540 } 542 WwwDocName ::= TEXTUAL-CONVENTION 543 STATUS current 544 DESCRIPTION 545 "The server relative name of a document. If the URL were 546 http://www.x.org/standards/search/search.cgi?string=test 547 then the value of this textual convention would resolve 548 to '/standards/search/search.cgi'." 550 SYNTAX DisplayString 552 -- The WWW Service Information Group 553 -- 554 -- The WWW service information group contains information about 555 -- the WWW services known by the SNMP agent. 557 wwwService OBJECT IDENTIFIER ::= { wwwMIBObjects 1 } 559 wwwServiceTable OBJECT-TYPE 560 SYNTAX SEQUENCE OF WwwServiceEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "The table of the WWW services known by the SNMP agent." 565 ::= { wwwService 1 } 567 wwwServiceEntry OBJECT-TYPE 568 SYNTAX WwwServiceEntry 569 MAX-ACCESS not-accessible 570 STATUS current 571 DESCRIPTION 572 "Details about a particular WWW service." 573 INDEX { wwwServiceIndex } 574 ::= { wwwServiceTable 1 } 576 WwwServiceEntry ::= SEQUENCE { 577 wwwServiceIndex Unsigned32, 578 wwwServiceDescription Utf8String, 579 wwwServiceContact Utf8String, 580 wwwServiceProtocol OBJECT IDENTIFIER, 581 wwwServiceName DisplayString, 582 wwwServiceType INTEGER, 583 wwwServiceUptime TimeStamp, 584 wwwServiceOperStatus WwwOperStatus, 585 wwwServiceLastChange TimeStamp 586 } 588 wwwServiceIndex OBJECT-TYPE 589 SYNTAX Unsigned32 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "An integer used to uniquely identify a WWW service. The 594 value must be the same as the corresponding value of the 595 applSrvInst defined in the Application Management MIB 596 (APPLICATION-MIB) if the applSrvInst object is available. 597 It might be necessary to manually configure sub-agents in 598 order to meet this requirement." 599 ::= { wwwServiceEntry 1 } 601 wwwServiceDescription OBJECT-TYPE 602 SYNTAX Utf8String 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "Textual description of the WWW service. This shall include 607 at least the vendor and version number of the application 608 realizing the WWW service. In a minimal case, this might 609 be the Product Token (see RFC 2068) for the application." 610 ::= { wwwServiceEntry 2 } 612 wwwServiceContact OBJECT-TYPE 613 SYNTAX Utf8String 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "The textual identification of the contact person for this 618 service, together with information on how to contact this 619 person. For instance, this might be a string containing an 620 email address, e.g. ''." 621 ::= { wwwServiceEntry 3 } 623 wwwServiceProtocol OBJECT-TYPE 624 SYNTAX OBJECT IDENTIFIER 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "An identification of the primary protocol in use by this 629 service. For Internet applications, the IANA maintains 630 a registry of the OIDs which correspond to well-known 631 application protocols. If the application protocol is not 632 listed in the registry, an OID value of the form 633 {applTCPProtoID port} or {applUDProtoID port} are used for 634 TCP-based and UDP-based protocols, respectively. In either 635 case 'port' corresponds to the primary port number being 636 used by the protocol." 637 ::= { wwwServiceEntry 4 } 639 wwwServiceName OBJECT-TYPE 640 SYNTAX DisplayString 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The fully qualified domain name by which this service is 645 known. This object must contain the virtual host name if 646 the service is realized for a virtual host." 647 ::= { wwwServiceEntry 5 } 649 wwwServiceType OBJECT-TYPE 650 SYNTAX INTEGER { 651 wwwServer(1), 652 wwwClient(2), 653 wwwProxy(3), 654 wwwCachingProxy(4), 655 wwwOther(5) 656 } 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The application type using or realizing this WWW service." 661 ::= { wwwServiceEntry 6 } 663 wwwServiceUptime OBJECT-TYPE 664 SYNTAX TimeStamp 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION 668 "The value of sysUpTime at the time the WWW service was last 669 initialized. If the application was last initialized prior 670 to the last initialization of the network management 671 subsystem, then this object contains a zero value." 672 ::= { wwwServiceEntry 7 } 674 wwwServiceOperStatus OBJECT-TYPE 675 SYNTAX WwwOperStatus 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "Indicates the operational status of the WWW service." 680 ::= { wwwServiceEntry 8 } 682 wwwServiceLastChange OBJECT-TYPE 683 SYNTAX TimeStamp 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The value of sysUpTime at the time the WWW service entered 688 its current operational state. If the current state was 689 entered prior to the last initialization of the local 690 network management subsystem, then this object contains 691 a zero value." 692 ::= { wwwServiceEntry 9 } 694 -- The WWW Protocol Statistics Group 695 -- 696 -- The WWW protocol statistics group contains statistics about 697 -- the DTP requests and responses send or received. 699 wwwProtocolStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 2 } 701 wwwSummaryTable OBJECT-TYPE 702 SYNTAX SEQUENCE OF WwwSummaryEntry 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 "The table providing overview statistics for the 707 WWW services on this system." 708 ::= { wwwProtocolStatistics 1 } 710 wwwSummaryEntry OBJECT-TYPE 711 SYNTAX WwwSummaryEntry 712 MAX-ACCESS not-accessible 713 STATUS current 714 DESCRIPTION 715 "Overview statistics for an individual service." 716 INDEX { wwwServiceIndex } 717 ::= { wwwSummaryTable 1 } 719 WwwSummaryEntry ::= SEQUENCE { 720 wwwSummaryInRequests Counter32, 721 wwwSummaryOutRequests Counter32, 722 wwwSummaryInResponses Counter32, 723 wwwSummaryOutResponses Counter32, 724 wwwSummaryInBytes Counter64, 725 wwwSummaryInBytesLow Counter32, 726 wwwSummaryOutBytes Counter64, 727 wwwSummaryOutBytesLow Counter32 728 } 730 wwwSummaryInRequests OBJECT-TYPE 731 SYNTAX Counter32 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The number of requests successfully received." 737 ::= { wwwSummaryEntry 1 } 739 wwwSummaryOutRequests OBJECT-TYPE 740 SYNTAX Counter32 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "The number of requests generated." 745 ::= { wwwSummaryEntry 2 } 747 wwwSummaryInResponses OBJECT-TYPE 748 SYNTAX Counter32 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The number of responses successfully received." 753 ::= { wwwSummaryEntry 3 } 755 wwwSummaryOutResponses OBJECT-TYPE 756 SYNTAX Counter32 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "The number of responses generated." 761 ::= { wwwSummaryEntry 4 } 763 wwwSummaryInBytes OBJECT-TYPE 764 SYNTAX Counter64 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The number of content bytes received." 769 ::= { wwwSummaryEntry 5 } 771 wwwSummaryInBytesLow OBJECT-TYPE 772 SYNTAX Counter32 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "The lowest thirty-two bits of wwwSummaryInBytes." 777 ::= { wwwSummaryEntry 6 } 779 wwwSummaryOutBytes OBJECT-TYPE 780 SYNTAX Counter64 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The number of content bytes transmitted." 785 ::= { wwwSummaryEntry 7 } 787 wwwSummaryOutBytesLow OBJECT-TYPE 788 SYNTAX Counter32 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "The lowest thirty-two bits of wwwSummaryOutBytes." 793 ::= { wwwSummaryEntry 8 } 795 -- The WWW request tables contain detailed information about 796 -- requests send or received by WWW services. 798 wwwRequestInTable OBJECT-TYPE 799 SYNTAX SEQUENCE OF WwwRequestInEntry 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "The table providing detailed statistics for requests 804 received by WWW services on this system." 805 ::= { wwwProtocolStatistics 2 } 807 wwwRequestInEntry OBJECT-TYPE 808 SYNTAX WwwRequestInEntry 809 MAX-ACCESS not-accessible 810 STATUS current 811 DESCRIPTION 812 "Request statistics for an individual service." 813 INDEX { wwwServiceIndex, wwwRequestInIndex } 814 ::= { wwwRequestInTable 1 } 816 WwwRequestInEntry ::= SEQUENCE { 817 wwwRequestInIndex WwwRequestType, 818 wwwRequestInCount Counter32, 819 wwwRequestInBytes Counter32, 820 wwwRequestInLastTime TimeStamp 821 } 823 wwwRequestInIndex OBJECT-TYPE 824 SYNTAX WwwRequestType 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "The particular request type the statistics apply to." 829 ::= { wwwRequestInEntry 1 } 831 wwwRequestInCount OBJECT-TYPE 832 SYNTAX Counter32 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "The number of requests of this type received by this 837 WWW service." 838 ::= { wwwRequestInEntry 2 } 840 wwwRequestInBytes OBJECT-TYPE 841 SYNTAX Counter32 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "The number of content bytes per request type received 846 by this WWW service." 847 ::= { wwwRequestInEntry 3 } 849 wwwRequestInLastTime OBJECT-TYPE 850 SYNTAX TimeStamp 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The value of sysUpTime when the last byte of the last 855 complete request of this type was received by this WWW 856 service." 857 ::= { wwwRequestInEntry 4 } 859 wwwRequestOutTable OBJECT-TYPE 860 SYNTAX SEQUENCE OF WwwRequestOutEntry 861 MAX-ACCESS not-accessible 862 STATUS current 863 DESCRIPTION 864 "The table providing detailed statistics for requests 865 generated by the services on this system." 866 ::= { wwwProtocolStatistics 3 } 868 wwwRequestOutEntry OBJECT-TYPE 869 SYNTAX WwwRequestOutEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "Request statistics for an individual service." 874 INDEX { wwwServiceIndex, wwwRequestOutIndex } 875 ::= { wwwRequestOutTable 1 } 877 WwwRequestOutEntry ::= SEQUENCE { 878 wwwRequestOutIndex WwwRequestType, 879 wwwRequestOutCount Counter32, 880 wwwRequestOutBytes Counter32, 881 wwwRequestOutLastTime TimeStamp 882 } 884 wwwRequestOutIndex OBJECT-TYPE 885 SYNTAX WwwRequestType 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "The particular request type the statistics apply to." 890 ::= { wwwRequestOutEntry 1 } 892 wwwRequestOutCount OBJECT-TYPE 893 SYNTAX Counter32 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "The number of requests of this type generated by this 898 WWW service." 899 ::= { wwwRequestOutEntry 2 } 901 wwwRequestOutBytes OBJECT-TYPE 902 SYNTAX Counter32 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The number of content bytes per requests type generated 907 by this WWW service." 908 ::= { wwwRequestOutEntry 3 } 910 wwwRequestOutLastTime OBJECT-TYPE 911 SYNTAX TimeStamp 912 MAX-ACCESS read-only 913 STATUS current 914 DESCRIPTION 915 "The value of sysUpTime when the first byte of the last 916 request of this type was send by this WWW service." 917 ::= { wwwRequestOutEntry 4 } 919 -- The WWW response tables contain detailed information about 920 -- responses send or received by WWW services. 922 wwwResponseInTable OBJECT-TYPE 923 SYNTAX SEQUENCE OF WwwResponseInEntry 924 MAX-ACCESS not-accessible 925 STATUS current 926 DESCRIPTION 927 "The table providing detailed statistics for responses 928 received by WWW services on this system." 929 ::= { wwwProtocolStatistics 4 } 931 wwwResponseInEntry OBJECT-TYPE 932 SYNTAX WwwResponseInEntry 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "Response statistics for an individual service." 937 INDEX { wwwServiceIndex, wwwResponseInIndex } 938 ::= { wwwResponseInTable 1 } 940 WwwResponseInEntry ::= SEQUENCE { 941 wwwResponseInIndex WwwResponseType, 942 wwwResponseInCount Counter32, 943 wwwResponseInBytes Counter32, 944 wwwResponseInLastTime TimeStamp 945 } 947 wwwResponseInIndex OBJECT-TYPE 948 SYNTAX WwwResponseType 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "The particular response type the statistics apply to." 953 ::= { wwwResponseInEntry 1 } 955 wwwResponseInCount OBJECT-TYPE 956 SYNTAX Counter32 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "The number of responses of this type received by this 961 WWW service." 962 ::= { wwwResponseInEntry 2 } 964 wwwResponseInBytes OBJECT-TYPE 965 SYNTAX Counter32 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "The number of content bytes per response type received 970 by this WWW service." 971 ::= { wwwResponseInEntry 3 } 973 wwwResponseInLastTime OBJECT-TYPE 974 SYNTAX TimeStamp 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "The value of sysUpTime when the last byte of the last 979 complete response of this type was received by this WWW 980 service." 981 ::= { wwwResponseInEntry 4 } 983 wwwResponseOutTable OBJECT-TYPE 984 SYNTAX SEQUENCE OF WwwResponseOutEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "The table providing detailed statistics for responses 989 generated by services on this system." 990 ::= { wwwProtocolStatistics 5 } 992 wwwResponseOutEntry OBJECT-TYPE 993 SYNTAX WwwResponseOutEntry 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "Response statistics for an individual service." 998 INDEX { wwwServiceIndex, wwwResponseOutIndex } 999 ::= { wwwResponseOutTable 1 } 1001 WwwResponseOutEntry ::= SEQUENCE { 1002 wwwResponseOutIndex WwwResponseType, 1003 wwwResponseOutCount Counter32, 1004 wwwResponseOutBytes Counter32, 1005 wwwResponseOutLastTime TimeStamp 1006 } 1008 wwwResponseOutIndex OBJECT-TYPE 1009 SYNTAX WwwResponseType 1010 MAX-ACCESS not-accessible 1011 STATUS current 1012 DESCRIPTION 1013 "The particular response type the statistics apply to." 1014 ::= { wwwResponseOutEntry 1 } 1016 wwwResponseOutCount OBJECT-TYPE 1017 SYNTAX Counter32 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "The number of responses of this type generated by this 1022 WWW service." 1023 ::= { wwwResponseOutEntry 2 } 1025 wwwResponseOutBytes OBJECT-TYPE 1026 SYNTAX Counter32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The number of content bytes per response type generated 1031 by this WWW service." 1032 ::= { wwwResponseOutEntry 3 } 1034 wwwResponseOutLastTime OBJECT-TYPE 1035 SYNTAX TimeStamp 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "The value of sysUpTime when the first byte of the last 1040 response of this type was sent by this WWW service." 1041 ::= { wwwResponseOutEntry 4 } 1043 -- The WWW Document Statistics Group 1044 -- 1045 -- The WWW document statistics group contains statistics about 1046 -- document read attempts. 1048 wwwDocumentStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 3 } 1050 wwwDocCtrlTable OBJECT-TYPE 1051 SYNTAX SEQUENCE OF WwwDocCtrlEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "A table which controls how the MIB implementation 1056 collects and maintains document statistics." 1057 ::= { wwwDocumentStatistics 1 } 1059 wwwDocCtrlEntry OBJECT-TYPE 1060 SYNTAX WwwDocCtrlEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "An entry which allows to configure the wwwDocLastNTable, 1065 the wwwDocBucketTable, the wwwDocAccessTopNTable, and 1066 the wwwDocBytesTopNTable." 1067 INDEX { wwwServiceIndex } 1068 ::= { wwwDocCtrlTable 1 } 1070 WwwDocCtrlEntry ::= SEQUENCE { 1071 wwwDocCtrlLastNSize Unsigned32, 1072 wwwDocCtrlLastNStatus INTEGER, 1073 wwwDocCtrlBuckets Unsigned32, 1074 wwwDocCtrlBucketTimeInterval TimeInterval, 1075 wwwDocCtrlTopNSize Unsigned32 1076 } 1078 wwwDocCtrlLastNSize OBJECT-TYPE 1079 SYNTAX Unsigned32 1080 MAX-ACCESS read-write 1081 STATUS current 1082 DESCRIPTION 1083 "The maximum number of entries in the wwwDocLastNTable." 1084 DEFVAL { 25 } 1085 ::= { wwwDocCtrlEntry 1 } 1087 wwwDocCtrlLastNStatus OBJECT-TYPE 1088 SYNTAX INTEGER { enabled(1), disabled(2) } 1089 MAX-ACCESS read-write 1090 STATUS current 1091 DESCRIPTION 1092 "Indicates whether the wwwDocLastNTable is currently updated 1093 by the agent or not. This object allows a manager to 1094 suspend the update process in order to retrieve the 1095 wwwDocLastNTable in a consistent state. The agent is 1096 expected to take a snapshot of the wwwDocLastNTable and to 1097 continue updating the table so that recent information is 1098 available as soon as the value is changed back to enabled. 1100 Setting this object to enabled if it has not been set to 1101 disabled previously by the same manager can interfere with 1102 an operation in progress initiated by another manager. It 1103 is therefore necessary that managers synchronize their 1104 usage of this object." 1105 DEFVAL { enabled } 1106 ::= { wwwDocCtrlEntry 2 } 1108 wwwDocCtrlBuckets OBJECT-TYPE 1109 SYNTAX Unsigned32 1110 MAX-ACCESS read-write 1111 STATUS current 1112 DESCRIPTION 1113 "The maximum number of buckets maintained by the agent 1114 before the oldest bucket is deleted. The buckets are used 1115 to populate the wwwDocAccessTopNTable and the 1116 wwwDocBytesTopNTable." 1117 DEFVAL { 2 } 1118 ::= { wwwDocCtrlEntry 3 } 1120 wwwDocCtrlBucketTimeInterval OBJECT-TYPE 1121 SYNTAX TimeInterval 1122 MAX-ACCESS read-write 1123 STATUS current 1124 DESCRIPTION 1125 "The time interval after which a new bucket is created. 1126 Changing this object has no effect on existing buckets." 1127 DEFVAL { 90000 } -- 15 minutes (resolution .01 s) 1128 ::= { wwwDocCtrlEntry 4 } 1130 wwwDocCtrlTopNSize OBJECT-TYPE 1131 SYNTAX Unsigned32 1132 MAX-ACCESS read-write 1133 STATUS current 1134 DESCRIPTION 1135 "The maximum number of entries shown in the 1136 wwwDocAccessTopNTable of the wwwDocBytesTopNTable. 1137 Changing this object has no effect on existing buckets." 1138 DEFVAL { 25 } 1139 ::= { wwwDocCtrlEntry 5 } 1141 wwwDocLastNTable OBJECT-TYPE 1142 SYNTAX SEQUENCE OF WwwDocLastNEntry 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "The table which logs the last N access attempts." 1147 ::= { wwwDocumentStatistics 2 } 1149 wwwDocLastNEntry OBJECT-TYPE 1150 SYNTAX WwwDocLastNEntry 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "An entry which describes a recent access attempt." 1155 INDEX { wwwServiceIndex, wwwDocLastNIndex } 1156 ::= { wwwDocLastNTable 1 } 1158 WwwDocLastNEntry ::= SEQUENCE { 1159 wwwDocLastNIndex Unsigned32, 1160 wwwDocLastNName WwwDocName, 1161 wwwDocLastNTimeStamp DateAndTime, 1162 wwwDocLastNRequestType WwwRequestType, 1163 wwwDocLastNResponseType WwwResponseType, 1164 wwwDocLastNStatusMsg DisplayString, 1165 wwwDocLastNBytes Unsigned32 1166 } 1168 wwwDocLastNIndex OBJECT-TYPE 1169 SYNTAX Unsigned32 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "An arbitrary monotonically increasing integer number used 1174 for indexing the wwwDocLastNTable. The first document 1175 accessed appears in the table with this index value equal 1176 to one. Each subsequent document is indexed with the next 1177 sequential index value. The Nth document accessed will be 1178 indexed by N. This table presents a sliding window of the 1179 last N documents accessed where N is the value of 1180 wwwDocCtrlLastNSize. Thus at any given time, the entries in 1181 this table will be indexed by N-wwwDocCtrlLastNSize thru 1182 N. The wwwDocCtrlLastNStatus attribute should be used to 1183 control the updating of this table to allow the manager to 1184 read its contents." 1185 ::= { wwwDocLastNEntry 1 } 1187 wwwDocLastNName OBJECT-TYPE 1188 SYNTAX WwwDocName 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "The name of the document which was attempted to access." 1193 ::= { wwwDocLastNEntry 2 } 1195 wwwDocLastNTimeStamp OBJECT-TYPE 1196 SYNTAX DateAndTime 1197 MAX-ACCESS read-only 1198 STATUS current 1199 DESCRIPTION 1200 "The date and time that this document was attempted 1201 to access." 1202 ::= { wwwDocLastNEntry 3 } 1204 wwwDocLastNRequestType OBJECT-TYPE 1205 SYNTAX WwwRequestType 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "The protocol request type which was received by the 1210 server when this document access was attempted." 1211 ::= { wwwDocLastNEntry 4 } 1213 wwwDocLastNResponseType OBJECT-TYPE 1214 SYNTAX WwwResponseType 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "The protocol response type which was sent to the client 1219 as a result of this attempt to access a document. This 1220 object contains the type of the primary response in case 1221 there were multiple responses to a single request." 1222 ::= { wwwDocLastNEntry 5 } 1224 wwwDocLastNStatusMsg OBJECT-TYPE 1225 SYNTAX DisplayString 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "This object contains a human readable description of the 1230 reason why the wwwDocLastNResponseType has been returned to 1231 the client. This object defines the implementation specific 1232 reason if the value of wwwDocLastNResponseType indicates an 1233 error. For example, this object can indicate that the 1234 requested document could not be transferred due to a 1235 timeout condition or the document could not be transferred 1236 because a 'soft link' pointing to the document could not be 1237 resolved." 1238 ::= { wwwDocLastNEntry 6 } 1240 wwwDocLastNBytes OBJECT-TYPE 1241 SYNTAX Unsigned32 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "The number of content bytes that were returned as a 1246 result of this attempt to access a document." 1247 ::= { wwwDocLastNEntry 7 } 1249 wwwDocBucketTable OBJECT-TYPE 1250 SYNTAX SEQUENCE OF WwwDocBucketEntry 1251 MAX-ACCESS not-accessible 1252 STATUS current 1253 DESCRIPTION 1254 "This table provides administrative summary information for 1255 the buckets maintained per WWW service." 1256 ::= { wwwDocumentStatistics 3 } 1258 wwwDocBucketEntry OBJECT-TYPE 1259 SYNTAX WwwDocBucketEntry 1260 MAX-ACCESS not-accessible 1261 STATUS current 1262 DESCRIPTION 1263 "An entry which describes the parameters associated with a 1264 particular bucket." 1265 INDEX { wwwServiceIndex, wwwDocBucketIndex } 1266 ::= { wwwDocBucketTable 1 } 1268 WwwDocBucketEntry ::= SEQUENCE { 1269 wwwDocBucketIndex Unsigned32, 1270 wwwDocBucketTimeStamp TimeStamp, 1271 wwwDocBucketAccesses Unsigned32, 1272 wwwDocBucketDocuments Unsigned32, 1273 wwwDocBucketBytes Unsigned32 1274 } 1276 wwwDocBucketIndex OBJECT-TYPE 1277 SYNTAX Unsigned32 1278 MAX-ACCESS not-accessible 1279 STATUS current 1280 DESCRIPTION 1281 "An arbitrary monotonically increasing integer number 1282 used for indexing the wwwDocBucketTable. The index number 1283 wraps to 1 whenever the maximum value is reached." 1284 ::= { wwwDocBucketEntry 1 } 1286 wwwDocBucketTimeStamp OBJECT-TYPE 1287 SYNTAX TimeStamp 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The value of sysUpTime when the bucket was made available." 1292 ::= { wwwDocBucketEntry 2 } 1294 wwwDocBucketAccesses OBJECT-TYPE 1295 SYNTAX Unsigned32 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The total number of access attempts for any document 1300 provided by this WWW service during the time interval 1301 over which this bucket was created." 1302 ::= { wwwDocBucketEntry 3 } 1304 wwwDocBucketDocuments OBJECT-TYPE 1305 SYNTAX Unsigned32 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "The total number of different documents which were 1310 attempted to be read from this this WWW service during 1311 the time interval over which this bucket was created." 1312 ::= { wwwDocBucketEntry 4 } 1314 wwwDocBucketBytes OBJECT-TYPE 1315 SYNTAX Unsigned32 1316 MAX-ACCESS read-only 1317 STATUS current 1318 DESCRIPTION 1319 "The total number of content bytes which were transferred 1320 from this WWW service during the time interval over which 1321 this bucket was created." 1322 ::= { wwwDocBucketEntry 5 } 1324 wwwDocAccessTopNTable OBJECT-TYPE 1325 SYNTAX SEQUENCE OF WwwDocAccessTopNEntry 1326 MAX-ACCESS not-accessible 1327 STATUS current 1328 DESCRIPTION 1329 "The table of the most frequently accessed documents in a 1330 given bucket." 1331 ::= { wwwDocumentStatistics 4 } 1333 wwwDocAccessTopNEntry OBJECT-TYPE 1334 SYNTAX WwwDocAccessTopNEntry 1335 MAX-ACCESS not-accessible 1336 STATUS current 1337 DESCRIPTION 1338 "An entry in the top N table sorted by document accesses." 1339 INDEX { wwwServiceIndex, wwwDocBucketIndex, 1340 wwwDocAccessTopNIndex } 1341 ::= { wwwDocAccessTopNTable 1 } 1343 WwwDocAccessTopNEntry ::= SEQUENCE { 1344 wwwDocAccessTopNIndex Unsigned32, 1345 wwwDocAccessTopNName WwwDocName, 1346 wwwDocAccessTopNAccesses Unsigned32, 1347 wwwDocAccessTopNBytes Unsigned32, 1348 wwwDocAccessTopNLastResponseType WwwResponseType 1349 } 1351 wwwDocAccessTopNIndex OBJECT-TYPE 1352 SYNTAX Unsigned32 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "An arbitrary monotonically increasing integer number 1357 used for indexing the wwwDocAccessTopNTable. The index is 1358 inversely correlated to the sorting order of the table. The 1359 document with the highest access count will get the index 1360 value 1." 1361 ::= { wwwDocAccessTopNEntry 1 } 1363 wwwDocAccessTopNName OBJECT-TYPE 1364 SYNTAX WwwDocName 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "The name of the document which was attempted to access." 1369 ::= { wwwDocAccessTopNEntry 2 } 1371 wwwDocAccessTopNAccesses OBJECT-TYPE 1372 SYNTAX Unsigned32 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "The total number of access attempts for this document." 1377 ::= { wwwDocAccessTopNEntry 3 } 1379 wwwDocAccessTopNBytes OBJECT-TYPE 1380 SYNTAX Unsigned32 1381 MAX-ACCESS read-only 1382 STATUS current 1383 DESCRIPTION 1384 "The total number of content bytes that were transmitted 1385 as a result of attempts to access this document." 1386 ::= { wwwDocAccessTopNEntry 4 } 1388 wwwDocAccessTopNLastResponseType OBJECT-TYPE 1389 SYNTAX WwwResponseType 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "The protocol response type which was sent to the client 1394 as a result of the last attempt to access this document. 1395 This object contains the type of the primary response in 1396 case there were multiple responses to a single request." 1397 ::= { wwwDocAccessTopNEntry 5 } 1399 wwwDocBytesTopNTable OBJECT-TYPE 1400 SYNTAX SEQUENCE OF WwwDocBytesTopNEntry 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION 1404 "The table of the documents which caused most of the network 1405 traffic in a given bucket." 1406 ::= { wwwDocumentStatistics 5 } 1408 wwwDocBytesTopNEntry OBJECT-TYPE 1409 SYNTAX WwwDocBytesTopNEntry 1410 MAX-ACCESS not-accessible 1411 STATUS current 1412 DESCRIPTION 1413 "An entry in the top N table sorted by network traffic." 1414 INDEX { wwwServiceIndex, wwwDocBucketIndex, 1415 wwwDocBytesTopNIndex } 1416 ::= { wwwDocBytesTopNTable 1 } 1418 WwwDocBytesTopNEntry ::= SEQUENCE { 1419 wwwDocBytesTopNIndex Unsigned32, 1420 wwwDocBytesTopNName WwwDocName, 1421 wwwDocBytesTopNAccesses Unsigned32, 1422 wwwDocBytesTopNBytes Unsigned32, 1423 wwwDocBytesTopNLastResponseType WwwResponseType 1424 } 1426 wwwDocBytesTopNIndex OBJECT-TYPE 1427 SYNTAX Unsigned32 1428 MAX-ACCESS not-accessible 1429 STATUS current 1430 DESCRIPTION 1431 "An arbitrary monotonically increasing integer number 1432 used for indexing the wwwDocBytesTopNTable. The index is 1433 inversely correlated to the sorting order of the table. The 1434 document with the highest byte count will get the index 1435 value 1." 1436 ::= { wwwDocBytesTopNEntry 1 } 1438 wwwDocBytesTopNName OBJECT-TYPE 1439 SYNTAX WwwDocName 1440 MAX-ACCESS read-only 1441 STATUS current 1442 DESCRIPTION 1443 "The name of the document which was attempted to access." 1444 ::= { wwwDocBytesTopNEntry 2 } 1446 wwwDocBytesTopNAccesses OBJECT-TYPE 1447 SYNTAX Unsigned32 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "The total number of access attempts for this document." 1452 ::= { wwwDocBytesTopNEntry 3 } 1454 wwwDocBytesTopNBytes OBJECT-TYPE 1455 SYNTAX Unsigned32 1456 MAX-ACCESS read-only 1457 STATUS current 1458 DESCRIPTION 1459 "The total number of content bytes that were transmitted 1460 as a result of attempts to access this document." 1461 ::= { wwwDocBytesTopNEntry 4 } 1463 wwwDocBytesTopNLastResponseType OBJECT-TYPE 1464 SYNTAX WwwResponseType 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "The protocol response type which was sent to the client 1469 as a result of the last attempt to access this document. 1470 This object contains the type of the primary response in 1471 case there were multiple responses to a single request." 1472 ::= { wwwDocBytesTopNEntry 5 } 1474 -- 1475 -- Conformance Definitions 1476 -- 1478 wwwMIBCompliances OBJECT IDENTIFIER ::= { wwwMIBConformance 1 } 1479 wwwMIBGroups OBJECT IDENTIFIER ::= { wwwMIBConformance 2 } 1481 wwwMinimalCompliance MODULE-COMPLIANCE 1482 STATUS current 1483 DESCRIPTION 1484 "The compliance statement for SNMP agents which implement 1485 the minimal subset of the WWW-MIB. Implementors might 1486 choose this subset for high-performance server where 1487 full compliance might be to expensive." 1488 MODULE -- this module 1489 MANDATORY-GROUPS { 1490 wwwServiceGroup, 1491 wwwSummaryGroup 1492 } 1493 ::= { wwwMIBCompliances 1 } 1495 wwwFullCompliance MODULE-COMPLIANCE 1496 STATUS current 1497 DESCRIPTION 1498 "The compliance statement for SNMP agents which implement 1499 the full WWW-MIB. 1501 The wwwRequestInTable and wwwResponseOutTable tables will 1502 always be empty for a pure WWW client implementation and 1503 wwwSummaryInRequests and wwwSummaryOutResponses will both 1504 be zero. 1506 The wwwRequestOutTable and wwwResponseInTable tables will 1507 always be empty for a pure WWW server implementation and 1508 wwwSummaryOutRequests and wwwSummaryInResponses will both 1509 be zero. 1511 An implementation for a WWW proxy must be capable to 1512 populate all tables." 1513 MODULE -- this module 1514 MANDATORY-GROUPS { 1515 wwwServiceGroup, 1516 wwwSummaryGroup, 1517 wwwRequestInGroup, 1518 wwwRequestOutGroup, 1519 wwwResponseInGroup, 1520 wwwResponseOutGroup, 1521 wwwDocumentGroup 1522 } 1523 ::= { wwwMIBCompliances 2 } 1525 wwwServiceGroup OBJECT-GROUP 1526 OBJECTS { 1527 wwwServiceDescription, 1528 wwwServiceContact, 1529 wwwServiceProtocol, 1530 wwwServiceName, 1531 wwwServiceType, 1532 wwwServiceUptime, 1533 wwwServiceOperStatus, 1534 wwwServiceLastChange 1535 } 1536 STATUS current 1537 DESCRIPTION 1538 "A collection of objects providing information about 1539 the WWW services known by the SNMP agent." 1540 ::= { wwwMIBGroups 1 } 1542 wwwSummaryGroup OBJECT-GROUP 1543 OBJECTS { 1544 wwwSummaryInRequests, 1545 wwwSummaryOutRequests, 1546 wwwSummaryInResponses, 1547 wwwSummaryOutResponses, 1548 wwwSummaryInBytes, 1549 wwwSummaryInBytesLow, 1550 wwwSummaryOutBytes, 1551 wwwSummaryOutBytesLow 1552 } 1553 STATUS current 1554 DESCRIPTION 1555 "A collection of objects providing summary statistics 1556 about requests and responses generated and received 1557 by a WWW service." 1558 ::= { wwwMIBGroups 2 } 1560 wwwRequestInGroup OBJECT-GROUP 1561 OBJECTS { 1562 wwwRequestInCount, 1563 wwwRequestInBytes, 1564 wwwRequestInLastTime 1565 } 1566 STATUS current 1567 DESCRIPTION 1568 "A collection of objects providing detailed statistics 1569 about requests received by a WWW service." 1570 ::= { wwwMIBGroups 3 } 1572 wwwRequestOutGroup OBJECT-GROUP 1573 OBJECTS { 1574 wwwRequestOutCount, 1575 wwwRequestOutBytes, 1576 wwwRequestOutLastTime 1577 } 1578 STATUS current 1579 DESCRIPTION 1580 "A collection of objects providing detailed statistics 1581 about requests generated by a WWW service." 1582 ::= { wwwMIBGroups 4 } 1584 wwwResponseInGroup OBJECT-GROUP 1585 OBJECTS { 1586 wwwResponseInCount, 1587 wwwResponseInBytes, 1588 wwwResponseInLastTime 1589 } 1590 STATUS current 1591 DESCRIPTION 1592 "A collection of objects providing detailed statistics 1593 about responses received by a WWW service." 1594 ::= { wwwMIBGroups 5 } 1596 wwwResponseOutGroup OBJECT-GROUP 1597 OBJECTS { 1598 wwwResponseOutCount, 1599 wwwResponseOutBytes, 1600 wwwResponseOutLastTime 1601 } 1602 STATUS current 1603 DESCRIPTION 1604 "A collection of objects providing detailed statistics 1605 about responses generated by a WWW service." 1606 ::= { wwwMIBGroups 6 } 1608 wwwDocumentGroup OBJECT-GROUP 1609 OBJECTS { 1610 wwwDocCtrlLastNSize, 1611 wwwDocCtrlLastNStatus, 1612 wwwDocCtrlBuckets, 1613 wwwDocCtrlBucketTimeInterval, 1614 wwwDocCtrlTopNSize, 1615 wwwDocLastNName, 1616 wwwDocLastNTimeStamp, 1617 wwwDocLastNRequestType, 1618 wwwDocLastNResponseType, 1619 wwwDocLastNStatusMsg, 1620 wwwDocLastNBytes, 1621 wwwDocBucketTimeStamp, 1622 wwwDocBucketAccesses, 1623 wwwDocBucketDocuments, 1624 wwwDocBucketBytes, 1625 wwwDocAccessTopNName, 1626 wwwDocAccessTopNAccesses, 1627 wwwDocAccessTopNBytes, 1628 wwwDocAccessTopNLastResponseType, 1629 wwwDocBytesTopNName, 1630 wwwDocBytesTopNAccesses, 1631 wwwDocBytesTopNBytes, 1632 wwwDocBytesTopNLastResponseType 1633 } 1634 STATUS current 1635 DESCRIPTION 1636 "A collection of objects providing information about 1637 accesses to documents." 1638 ::= { wwwMIBGroups 7 } 1640 END 1642 7. Document Transfer Protocol Mappings 1644 This section describes how existing protocols such as HTTP [7,8] and 1645 FTP [9] can be mapped on the abstract Document Transfer Protocol 1646 (DTP) used within the definitions of the WWW MIB. Every mapping must 1647 define the identifier which is used to uniquely identify the transfer 1648 protocol. In addition, the mappings must define how requests and 1649 responses are identified. 1651 7.1. The HyperText Transfer Protocol 1653 The HyperText Transfer Protocol (HTTP) [7,8] is an application-level 1654 protocol used to transfer hypermedia documents in a distributed 1655 networked environment. HTTP is based on the request/response paradigm 1656 and can be mapped on the abstract DTP easily. 1658 The HTTP protocol usually runs over TCP and uses the well-known TCP 1659 port 80. Therefore, the default value for the wwwServiceProtocol 1660 object is { applTCPProtoID 80 }. 1662 HTTP allows for both requests and responses an open-ended set of 1663 message types. The general messages syntax of HTTP is therefore used 1664 for the protocol mapping. The BNF specification of the general HTTP 1665 message syntax as defined in [8] is as follows: 1667 HTTP-message = start-line 1668 *message-header 1669 CRLF 1670 [ message-body ] 1672 start-line = Request-Line | Status-Line 1674 Request-Line = Method SP Request-URI SP HTTP-Version CRLF 1676 Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF 1678 Every HTTP-message where the start-line is a Request-Line is 1679 considered a request in the abstract DTP. Every HTTP-message where 1680 the start-line is a Status-Line is considered a response in the 1681 abstract DTP. The mappings of wwwRequestType and wwwResponseType are 1682 defined as follows: 1684 o The wwwRequestType corresponds to the method token in the 1685 Request-Line. 1687 o The wwwResponseType corresponds to the Status-Code in the 1688 Status-Line. 1690 7.2. The File Transfer Protocol 1692 The File Transfer Protocol (FTP) [9] is an application-level protocol 1693 used to transfer files between hosts connected by the TCP/IP suite of 1694 protocols. FTP is based on a request/response paradigm and is mapped 1695 on the abstract DTP as defined in this section. The FTP model as 1696 defined in [9] is depicted below. 1698 ------------- 1699 |+---------+| 1700 || User || -------- 1701 ||Interface|<--->| User | 1702 |+----|----+| -------- 1703 ---------- | | | 1704 |+------+| control connection |+----|----+| 1705 ||Server|<------------------->|| Client || 1706 || PI || Commands/Replies || PI || 1707 |+--|---+| |+----|----+| 1708 | | | | | | 1709 -------- |+--|---+| Data |+----|----+| -------- 1710 | File |<--->|Server|<------------------->|| Client |<--->| File | 1711 |System| || DTP || Connection || DTP || |System| 1712 -------- |+------+| |+---------+| -------- 1713 ---------- ------------- 1715 FTP uses two different connection types between a client and a server 1716 to transfer files. The control connection is persistent during a FTP 1717 session and used to exchange FTP commands and associated replies. The 1718 data connection is only available when bulk data has to be 1719 transferred. 1721 The FTP protocol usually runs over TCP and uses the well-known TCP 1722 port 21 to setup the control connection. Therefore, the default value 1723 for the wwwServiceProtocol object is { applTCPProtoID 21 }. 1725 Every FTP command is considered a request in the abstract DTP. Every 1726 FTP reply is considered a response in the abstract DTP. It should be 1727 noted that a single FTP command can result in multiple FTP replies 1728 (e.g. preliminary positive replies). The primary response for a FTP 1729 request contains a status code of the form 2xy, 3xy, 4xy or 5xy. See 1730 section 4.2 in [9] for the exact meaning of these status codes. The 1731 mappings for wwwRequestType and wwwResponseType are defined as 1732 follows: 1734 o The wwwRequestType corresponds to the FTP command token. 1736 o The wwwResponseType corresponds to the three-digit code which 1737 starts a reply. Multi-line replies with the same three-digit 1738 code are counted as a single DTP response. 1740 8. Security Considerations 1742 The MIB objects defined in the memo might disclose information that 1743 should be protected. In particular, the document statistics group 1744 contains traffic information, which includes the names of documents 1745 that were a target of protocol operations. It is therefore adviced to 1746 use SNMP access control and SNMP security mechanism (where available) 1747 in order to protect this information in sensitive environments. 1749 The protocol statistics are less sensitive, because they do not 1750 contain details about the target of individual requests/responses. 1751 However, it is suggested that sites configure MIB views so that a 1752 user of this MIB can only see the portion of the statistics that 1753 belong to the WWW services managed by that user. 1755 9. Acknowledgments 1757 This document was produced by the Application MIB working group. The 1758 editors gratefully acknowledge the comments of the following 1759 individuals: 1761 Mark Gamble, Cheryl Krupczak, Randy Preshun, John Saperia, 1762 Bob Stewart, Martin Toet, Chris Wellens 1764 10. Editors' Address 1766 Harrie Hazewinkel Email: harrie.hazewinkel@jrc.it 1767 Joint Research Centre of the E.C. Tel: +39 (0)332 789384 1768 via Fermi - Ispra 21020 (VA) Fax: +39 (0)332 78550 1769 Italy 1771 Carl W. Kalbfleisch Email: cwk@verio.net 1772 Verio, Inc. Tel: +1 972 238-8303 1773 1950 Stemmons Frwy Fax: +1 972 238-0268 1774 2004 INFOMART 1775 Dallas, TX 75207 1776 USA 1778 Juergen Schoenwaelder Email: schoenw@ibr.cs.tu-bs.de 1779 TU Braunschweig Tel: +49 531 391-3683 1780 Bueltenweg 74/75 Fax: +49 531 489-5936 1781 38106 Braunschweig 1782 Germany 1784 11. References 1786 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1787 Waldbusser, "Structure of Management Information for Version 2 of 1788 the Simple Network Management Protocol (SNMPv2)", RFC1902, SNMP 1789 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1790 International Network Services, January 1996. 1792 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1793 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1794 RFC 1213, Hughes LAN Systems, Performance Systems International, 1795 March 1991. 1797 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1798 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1799 International, Performance Systems International, MIT Laboratory 1800 for Computer Science, May 1990. 1802 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1803 Waldbusser, "Protocol Operations for Version 2 of the Simple 1804 Network Management Protocol (SNMPv2)", RFC1905, SNMP Research,Inc., 1805 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1806 Network Services, January 1996. 1808 [5] T. Berners-Lee, "Universal Resource Identifiers in WWW", RFC 1630, 1809 CERN, June 1994. 1811 [6] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource 1812 Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of 1813 Minnesota, December 1994. 1815 [7] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext Transfer 1816 Protocol -- HTTP/1.0", RFC 1945, MIT/LCS, UC Irvine, MIT/LCS, May 1817 1996. 1819 [8] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners- 1820 Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, UC 1821 Irvine, DEC, DEC, MIT/LCS, January 1997. 1823 [9] Postel, J., and J.K. Reynolds, "File Transfer Protocol (FTP)", STD 1824 9, RFC 959, USC/ISI, October 1985. 1826 [10] C. Kalbfleisch, "Applicability of Standards Track MIBs to 1827 Management of World Wide Web Servers", RFC 2039, OnRamp 1828 Technologies, November 1996. 1830 [11] Krupczak, C., and J. Saperia, "Definitions of System-Level Managed 1831 Objects for Applications", RFC 2287, Empire Technologies, BGS 1832 Systems, February 1998. 1834 [12] Kalbfleisch, C., Krupczak, C., Preshun, R., and J. Saperia, 1835 "Application Management MIB", draft-ietf-applmib-mib-04.txt, Verio, 1836 Empire Technologies, BMC Software, BGS Systems, July 1997. 1838 [13] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A 1839 Proposed Standard for the Stream-Based Transmission of News", RFC 1840 977, UC San Diego & UC Berkeley, February 1986. 1842 [14] Callaghan, B., "WebNFS Client Specification", RFC 2054, Sun 1843 Microsystems, October 1996 1845 [15] Callaghan, B., "WebNFS Server Specification", RFC 2055, Sun 1846 Microsystems, October 1996 1848 12. Full Copyright Statement 1850 Copyright (C) The Internet Society (1998). All Rights Reserved. 1852 This document and translations of it may be copied and furnished to 1853 others, and derivative works that comment on or otherwise explain it 1854 or assist in its implementation may be prepared, copied, published 1855 and distributed, in whole or in part, without restriction of any 1856 kind, provided that the above copyright notice and this paragraph are 1857 included on all such copies and derivative works. However, this 1858 document itself may not be modified in any way, such as by removing 1859 the copyright notice or references to the Internet Society or other 1860 Internet organizations, except as needed for the purpose of 1861 developing Internet standards in which case the procedures for 1862 copyrights defined in the Internet Standards process must be 1863 followed, or as required to translate it into languages other than 1864 English. 1866 The limited permissions granted above are perpetual and will not be 1867 revoked by the Internet Society or its successors or assigns. 1869 This document and the information contained herein is provided on an 1870 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1871 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1872 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1873 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1874 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1876 Table of Contents 1878 1 Abstract ..................................................... 2 1879 2 The SNMPv2 Network Management Framework ...................... 2 1880 2.1 Object Definitions ......................................... 2 1881 3 Terminology .................................................. 3 1882 4 Overview ..................................................... 4 1883 4.1 Purpose and Requirements ................................... 4 1884 4.2 Relationship to other Standards Efforts .................... 5 1885 4.3 WWW Services ............................................... 5 1886 4.4 Document Transfer Protocol ................................. 6 1887 5 Structure of the MIB ......................................... 7 1888 5.1 Service Information Group .................................. 7 1889 5.2 Protocol Statistics Group .................................. 7 1890 5.3 Document Statistics Group .................................. 8 1891 6 Definitions .................................................. 10 1892 7 Document Transfer Protocol Mappings .......................... 36 1893 7.1 The HyperText Transfer Protocol ............................ 36 1894 7.2 The File Transfer Protocol ................................. 37 1895 8 Security Considerations ...................................... 38 1896 9 Acknowledgments .............................................. 39 1897 10 Editors' Address ............................................ 39 1898 11 References .................................................. 40 1899 12 Full Copyright Statement .................................... 41