idnits 2.17.1 draft-ietf-applmib-wwwmib-09.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 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1973 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 (August 25, 1998) is 9373 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) == Unused Reference: '16' is defined on line 1918, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2028 (ref. '16') (Obsoleted by RFC 9281) ** Downref: Normative reference to an Informational RFC: RFC 1630 (ref. '17') ** Obsolete normative reference: RFC 1738 (ref. '18') (Obsoleted by RFC 4248, RFC 4266) ** Downref: Normative reference to an Informational RFC: RFC 1945 (ref. '19') ** Obsolete normative reference: RFC 2068 (ref. '20') (Obsoleted by RFC 2616) ** Downref: Normative reference to an Informational RFC: RFC 2039 (ref. '22') == Outdated reference: A later version (-11) exists of draft-ietf-applmib-mib-08 ** Obsolete normative reference: RFC 977 (ref. '25') (Obsoleted by RFC 3977) ** Downref: Normative reference to an Informational RFC: RFC 2054 (ref. '26') ** Downref: Normative reference to an Informational RFC: RFC 2055 (ref. '27') Summary: 33 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft WWW Service MIB August 1998 3 Definitions of Managed Objects for WWW Services 5 August 25, 1998 7 9 Harrie Hazewinkel 10 Joint Research Centre of the E.C. 11 harrie.hazewinkel@jrc.it 13 Carl W. Kalbfleisch 14 Verio, Inc. 15 cwk@verio.net 17 Juergen Schoenwaelder 18 TU Braunschweig 19 schoenw@ibr.cs.tu-bs.de 21 Status of this Memo 23 This document is an Internet-Draft. Internet-Drafts are working 24 documents of the Internet Engineering Task Force (IETF), its areas, 25 and its working groups. Note that other groups may also distribute 26 working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as ``work in progress.'' 33 To view the entire list of current Internet-Drafts, please check the 34 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 35 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 36 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 37 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 39 Distribution of this document is unlimited. Please send comments to 40 the Application MIB Working Group, . 42 Copyright Notice 44 Copyright (C) The Internet Society (1998). All Rights Reserved. 46 1. Abstract 48 This memo defines an experimental portion of the Management 49 Information Base (MIB) for use with network management protocols in 50 the Internet Community. In particular it describes a set of objects 51 for managing World Wide Web (WWW) services. This MIB extends the 52 application management framework defined by the System Application 53 Management MIB (SYSAPPL-MIB) and the Application Management MIB 54 (APPLICATION-MIB). The protocol statistics defined in the WWW Service 55 MIB are based on an abstract document transfer protocol (DTP). This 56 memo also defines a mapping of the abstract DTP to HTTP and FTP. 57 Additional mappings may be defined in the future in order to use this 58 MIB with other document transfer protocols. It is anticipated that 59 such future mappings will be defined in separate RFCs. 61 2. The SNMP Management Framework 63 The SNMP Management Framework presently consists of five major 64 components: 66 o An overall architecture, described in RFC 2271 [1]. 68 o Mechanisms for describing and naming objects and events for the 69 purpose of management. The first version of this Structure of 70 Management Information (SMI) is called SMIv1 and described in 71 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 72 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 73 1904 [7]. 75 o Message protocols for transferring management information. The 76 first version of the SNMP message protocol is called SNMPv1 and 77 described in RFC 1157 [8]. A second version of the SNMP message 78 protocol, which is not an Internet standards track protocol, is 79 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 80 The third version of the message protocol is called SNMPv3 and 81 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 83 o Protocol operations for accessing management information. The 84 first set of protocol operations and associated PDU formats is 85 described in RFC 1157 [8]. A second set of protocol operations 86 and associated PDU formats is described in RFC 1905 [13]. 88 o A set of fundamental applications described in RFC 2273 [14] and 89 the view-based access control mechanism described in RFC 2275 90 [15]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. Objects in the MIB are 94 defined using the mechanisms defined in the SMI. 96 This memo specifies a MIB module that is compliant to the SMIv2. A 97 MIB conforming to the SMIv1 can be produced through the appropriate 98 translations. The resulting translated MIB must be semantically 99 equivalent, except where objects or events are omitted because no 100 translation is possible (use of Counter64). Some machine readable 101 information in SMIv2 will be converted into textual descriptions in 102 SMIv1 during the translation process. However, this loss of machine 103 readable information is not considered to change the semantics of the 104 MIB. 106 3. Terminology 108 This section defines the terminology used throughout this document. 110 o The 'World Wide Web' (WWW) is a world wide information system 111 which is based on the concept of documents that are linked 112 together by embedding references (links) to other local or 113 remote documents. 115 o A 'document' is a coherent piece of data which is accessible in 116 the World Wide Web. No assumptions are made about the content or 117 the type of a document. 119 o A 'Uniform Resource Locator' (URL) is a formatted string 120 representation for a document available via the Internet. URLs 121 are used to express references between documents. For the syntax 122 and semantics of the URL string representation refer to RFC 1630 123 [17] and RFC 1738 [18] 125 o A 'Document Transfer Protocol' (DTP) is a protocol used within 126 the World Wide Web to invoke actions on documents. The DTP is an 127 abstraction from real protocols, such as HTTP [19,20] or FTP 128 [21]. 130 o A 'request' is a DTP protocol operation which is targeted to a 131 'document' and invokes an action on the target document. The 132 request type specifies the action that should be performed. A 133 request can have a document associated with it. 135 o A 'response' is a DTP protocol operation which is returned as a 136 result of a previous (and associated) request. The response 137 status indicates if the requested action was successful or if 138 errors occurred. A response can have a document associated with 139 it. 141 o A 'WWW service' is a set of actions that can be invoked on a 142 document. Typical actions are the transfer of documents or the 143 retrieval of administrative information about documents. WWW 144 services are provided by means of a DTP. A WWW service can be 145 identified by the DTP protocol used to invoke services and the 146 transport endpoint used by that protocol. 148 o A 'client' is a program which establishes connections for the 149 purpose of sending requests and receiving responses. 151 o A 'server' is a program that accepts connections in order to 152 service requests by sending back responses. 154 o A 'proxy' is an intermediary program which acts as both a server 155 and a client for the purpose of making requests on behalf of 156 other clients. Requests are serviced internally or by passing 157 them on, with possible translation, to other servers. 159 o A 'caching proxy' is a proxy with the capability of locally 160 storing responses to associated requests. A caching proxy can 161 respond to similar requests with a previously stored response. 163 4. Overview 165 The World Wide Web (WWW) is a global network of information. 166 Information is stored in documents, which can have various formats, 167 including hyper-text and multi-media documents. Access to these 168 documents is provided by servers which are located all around the 169 world and are linked to each other via hyper-links embedded in 170 documents. 172 The usability of the World Wide Web depends largely on the 173 performance of the services realized by these servers. The services 174 are typically monitored through log files. This becomes a difficult 175 task when a single organization is responsible for a large number of 176 services. It is therefore desirable to treat WWW services as objects 177 that can be managed by using the Internet network management 178 framework [22]. 180 4.1. Purpose and Requirements 182 The goal of this MIB is to define a standardized set of objects which 183 lead to integrated and improved performance and fault management in a 184 heterogeneous environment of WWW services. This MIB focuses on the 185 service-oriented view. It does not deal with the process oriented 186 view, which is covered by the System Application MIB [23] and the 187 Application MIB [24]. 189 This document defines a set of managed objects to monitor WWW 190 services for short-term operational purposes, such as problem 191 detection and troubleshooting. No attempts are made here to cover 192 accounting or hit metering issues. 194 The scope of the MIB is further limited by the requirement that an 195 implementation conforming to this MIB must be possible without 196 putting a huge CPU or memory burden on the WWW server implementation. 198 In addition, this MIB does not cover WWW service configuration. 199 Server software has become an open market where competing vendors 200 constantly invent new features in order to shape their products. It 201 is therefore not possible to reach consensus on a common way to 202 configure WWW services at this point in time. 204 4.2. Relationship to other Standards Efforts 206 The WWW Service MIB fits into the application management architecture 207 defined in the System Application MIB [23]. The System Application 208 MIB and the Application MIB [24] use a process-oriented view, where 209 an application is viewed as a collection of processes. The WWW 210 Service MIB described in this memo uses a service-oriented view, 211 which looks at the services provided by a set of processes. 213 The relationship between the process-oriented view and the service- 214 oriented view is a many-to-many relationship, because one process can 215 implement multiple services and multiple services can be implemented 216 by a single set of processes. The Application Management MIB [24] 217 contains generic mapping tables, which map back and forth between 218 both views. 220 4.3. WWW Services 222 The MIB is organized around the concept of WWW services. WWW services 223 are a set of actions that can be invoked on a document. A WWW service 224 is provided or used by either a client, a server or a proxy. Clients 225 send out requests for information to server or proxy server. Servers 226 receive, process and respond to requests received from clients. 227 Servers usually have access to local documents, which can be 228 transfered to clients. 230 A proxy is a special server, who acts as both a server and a client 231 for the purpose of making requests on behalf of other clients. A 232 proxy is able to translate between the client and the origin server. 233 A proxy might also interact with other information retrieval system, 234 like for example databases. 236 The MIB defined in this memo distinguishes between outgoing and 237 incoming requests and responses. This makes it possible to obtain 238 statistics for clients, servers and proxies with a single set of 239 objects. 241 A special proxy server is the caching proxy, which maintains a cache 242 of previously received documents in order to reduce the bandwidth 243 used by World Wide Web clients. One interesting piece of management 244 information is the percentage of requests that were served from the 245 cache of the caching proxy (hits/miss-ratio). This ratio is not 246 contained explicitly in this MIB. Instead, the ratio can be derived 247 from the objects that count incoming and outgoing requests and 248 responses. 250 4.4. Document Transfer Protocol 252 The MIB is based on the concept of an abstract document transfer 253 protocol (DTP). The purpose of the abstract document transfer 254 protocol is to make the MIB definitions independent from concrete 255 protocols, like the Hypertext Transfer Protocol (HTTP) [19,20] or the 256 File Transfer Protocol (FTP) [21]. 258 The abstract document transfer protocol makes the following 259 assumptions about a concrete transfer protocol: 261 o The transfer protocol uses a request/response style of 262 interactions. 264 o Every request contains a request type, which defines the 265 operations performed by the receiving server. The request type 266 is represented by an OCTET STRING. It might be necessary to 267 define a translation into an OCTET STRING value for protocols 268 that use numbers to identify request types. 270 o A response contains a status code, which indicates if the 271 request was processed successfully or which error occurred. The 272 status code is represented as an INTEGER value. It might be 273 necessary to define a mapping for protocols that do not use an 274 INTEGER status code. 276 o A transfer protocol can send multiple responses for a single 277 request. Multiple responses are counted separately in the 278 protocol statistics group. 280 A primary response has to be identified for the document 281 statistics. The primary response is the response that indicates 282 whether the request was successful. 284 Section 7 of this memo defines a mapping of the document transfer 285 protocol to the HTTP protocol and the FTP protocol. Mappings to other 286 protocols, like NNTP [25] or WebNFS [26,27] might be defined in the 287 future. 289 5. Structure of the MIB 291 This section presents the structure of the MIB. The objects are 292 arranged into the following groups: 294 o service information 296 o protocol statistics 298 o document statistics 300 5.1. Service Information Group 302 The service information group consists of a single table describing 303 all the WWW services managed by the SNMP agent. The service table 304 contains administrative network management information for 305 (potentially) multiple WWW services running on a single host. It also 306 contains information for all services within virtual domains of a 307 host. The columnar objects in the table can be divided into two main 308 groups: 310 o global administrative information of the service, such as 311 service contact person, and 313 o network information, such as the transfer protocol. 315 5.2. Protocol Statistics Group 317 The protocol statistics group provides network management information 318 about the traffic received or transmitted by a WWW service. This 319 group contains counters related to DTP protocol operations and 320 consists of five tables: 322 o The wwwSummaryTable contains a set of network traffic related 323 counters. The table provides a summarization of the network 324 traffic and protocol operations related to a WWW service. It is 325 well recognized that certain variables are redundant with 326 respect to the request and response tables, but they are added 327 to provide an operator a quick overview and to reduce SNMP 328 network traffic. 330 o The wwwRequestInTable contains detailed information about 331 incoming requests. Every particular request type is counted 332 separately. 334 o The wwwRequestOutTable contains detailed information about 335 outgoing requests. Every particular request type is counted 336 separately. 338 o The wwwResponseInTable contains detailed information about 339 incoming responses. Every particular response type is counted 340 separately. 342 o The wwwResponseOutTable contains detailed information about 343 outgoing responses. Every particular response type is counted 344 separately. 346 5.3. Document Statistics Group 348 The document group contains information about the documents which 349 were accessed in the past. The group provides four types of 350 statistics. 352 1. Details about the last N attempts to invoke actions on 353 documents. 355 2. The Top N documents sorted by the number of actions invoked on 356 them computed over a time interval. 358 3. The Top N documents sorted by the number of content bytes 359 transferred computed over a time interval. 361 4. Summary statistics computed over a time interval. 363 The Top N document statistics are collected in buckets in order to 364 reduce agent resources and to allow a manager to detect changes in 365 the service usage pattern. Buckets are filled over a configurable 366 time interval. The agent computes the Top N statistics and starts a 367 new bucket once the time interval for the bucket has passed. The time 368 interval is configurable for each WWW service. 370 The document statistics group associates a response type to the 371 request which invoked an action. In case a DTP sends multiple 372 responses, the primary response must be used to derive the response 373 type of the request/response interaction. 375 The group consist of the following tables: 377 o The wwwDocCtrlTable provides the manager a means to limit the 378 document statistic tables in size and to control the expiration 379 and creation of buckets. 381 o The wwwDocLastNTable provides the manager information about the 382 last N documents which where accessed. The table lists the 383 documents for which access was attempted along with the request 384 and response type of the DTP and a status message. The request 385 and response types provide a manager information of how attempts 386 to invoke actions were handled by the DTP. The status message 387 object provides human readable text to further describe the 388 response type. 390 The number of documents in the wwwDocLastNTable is controlled by 391 the wwwDocCtrlLastNSize object in the wwwDocCtrlTable. The 392 wwwDocCtrlLastNLock object of the wwwDocCtrlTable allows a 393 management application to lock the wwwDocLastNTable in order to 394 retrieve a consistent snapshot of the fast changing 395 wwwDocLastNTable. 397 o The wwwDocBucketTable lists the buckets of statistical 398 information that have been collected. An entry in the 399 wwwDocBucketTable contains the creation timestamp of the bucket 400 as well as summary information (number of accesses, number of 401 documents accessed and number of bytes transferred). 403 The time interval is controlled by the 404 wwwDocCtrlBucketTimeInterval object of the wwwDocCtrlTable. The 405 maximum number of buckets maintained by the SNMP agent for a 406 particular WWW service is controlled by the wwwDocCtrlBuckets 407 object of the wwwDocCtrlTable. 409 o The wwwDocAccessTopNTable provides the manager an overview of 410 the top N documents which were accessed while statistics were 411 collected for a particular bucket. The wwwDocAccessTopNTable is 412 sorted by the number of read attempts per document. The maximum 413 number of entries in the wwwDocAccessTopNTable is controlled by 414 the wwwDocCtrlTopNSize object. 416 o The wwwDocBytesTopNTable provides the manager an overview of the 417 top N documents which caused most of the network traffic while 418 statistics were collected for a particular bucket. The 419 wwwDocBytesTopNTable is sorted by the number of bytes 420 transfered. The maximum number of entries in the 421 wwwDocBytesTopNTable is controlled by the wwwDocCtrlTopNSize 422 object. 424 The Top N statistics and the parameters of the underlying bucket are 425 not visible in the MIB as long as the bucket is filling up. Instead, 426 the following steps must be taken when the time interval for a 427 buckets has passed: 429 1. A new entry in the wwwDocBucketTable is created to summarize the 430 document statistics for that time interval. 432 2. The corresponding entries in the wwwDocAccessTopNTable and the 433 wwwDocBytesTopNTable are computed and made available. 435 3. If the resulting number of entries in the wwwDocBucketTable for 436 the WWW service now exceeds wwwDocCtrlBuckets, then the oldest 437 bucket for this WWW service and all corresponding entries in the 438 wwwDocBucketTable, wwwDocAccessTopNTable, and 439 wwwDocBytesTopNTable are deleted. 441 Note that a bucket usually contains much more data than displayed in 442 the Top N tables. The number of entries in the Top N table for a 443 bucket is controlled by wwwDocCtrlTopNSize, while the number of 444 entries in a bucket depends on the number of actions invoked on 445 documents within the time interval over which a bucket is filled up. 446 It is therefore suggested to discard the data associated with a 447 bucket once the entries for the wwwDocBucketTable, 448 wwwDocAccessTopNTable and wwwDocBytesTopNTable have been calculated. 450 6. Definitions 452 WWW-MIB DEFINITIONS ::= BEGIN 454 IMPORTS 455 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 456 Counter32, Counter64, Integer32, Unsigned32, TimeTicks 457 FROM SNMPv2-SMI 459 TEXTUAL-CONVENTION, DisplayString, TimeStamp, 460 DateAndTime, TimeInterval 461 FROM SNMPv2-TC 463 MODULE-COMPLIANCE, OBJECT-GROUP 464 FROM SNMPv2-CONF 466 Utf8String 467 FROM SYSAPPL-MIB; 469 wwwMIB MODULE-IDENTITY 470 LAST-UPDATED "9708250000Z" 471 ORGANIZATION "Application MIB Working Group" 472 CONTACT-INFO 473 " Harrie Hazewinkel 475 Postal: Joint Research Centre of the E.C. 476 via Fermi - Ispra 21020 (VA) 477 Italy 479 Tel: +39+(0)332 786322 480 Fax: +39+(0)332 785641 481 E-mail: harrie.hazewinkel@jrc.it 483 Carl W. Kalbfleisch 485 Postal: Verio, Inc. 486 1950 Stemmons Freeway 487 Suite 2004 - Infomart 488 Dallas, TX 75207 489 US 491 Tel: +1 972 238-8303 492 Fax: +1 972 238-0268 493 E-mail: cwk@verio.net 495 Juergen Schoenwaelder 497 Postal: TU Braunschweig 498 Bueltenweg 74/75 499 38106 Braunschweig 500 Germany 502 Tel: +49 531 391-3683 503 Fax: +49 531 489-5936 504 E-mail: schoenw@ibr.cs.tu-bs.de" 505 DESCRIPTION 506 "This WWW service MIB module is applicable to services 507 realized by a family of 'Document Transfer Protocols' 508 (DTP). Examples of DTPs are HTTP and FTP." 509 -- Get real registration number from IANA. 510 -- ::= { mib-2 XXXX } 511 ::= { mib-2 8080 } 513 -- 514 -- Object Identifier Assignments 515 -- 517 wwwMIBObjects OBJECT IDENTIFIER ::= { wwwMIB 1 } 518 wwwMIBConformance OBJECT IDENTIFIER ::= { wwwMIB 2 } 520 -- 521 -- Textual Conventions 522 -- 524 WwwRequestType ::= TEXTUAL-CONVENTION 525 STATUS current 526 DESCRIPTION 527 "The WwwRequestType defines the textual identification of 528 request types used by a document transfer protocol. For 529 the proper values for a given DTP, refer to the protocol 530 mappings for that DTP." 531 SYNTAX OCTET STRING (SIZE (1..40)) 533 WwwResponseType ::= TEXTUAL-CONVENTION 534 STATUS current 535 DESCRIPTION 536 "The WwwResponseType defines the different response values 537 used by document transfer protocols. For the proper values 538 for a given DTP, refer to the protocol mappings for that 539 DTP." 540 SYNTAX Integer32 (0..2147483647) 542 WwwOperStatus ::= TEXTUAL-CONVENTION 543 STATUS current 544 DESCRIPTION 545 "The operational status of a WWW service. 'down' indicates 546 that the service is not available. 'running' indicates 547 that the service is operational and available. 'halted' 548 indicates that the service is operational but not 549 available. 'congested' indicates that the service is 550 operational but no additional inbound associations can be 551 accommodated. 'restarting' indicates that the service is 552 currently unavailable but is in the process of restarting 553 and will be available soon." 554 SYNTAX INTEGER { 555 down(1), 556 running(2), 557 halted(3), 558 congested(4), 559 restarting(5) 560 } 562 WwwDocName ::= TEXTUAL-CONVENTION 563 DISPLAY-HINT "255a" 564 STATUS current 565 DESCRIPTION 566 "The server relative name of a document. If the URL were 567 http://www.x.org/standards/search/search.cgi?string=test 568 then the value of this textual convention would resolve 569 to '/standards/search/search.cgi'." 570 SYNTAX OCTET STRING (SIZE (0..255)) 572 -- The WWW Service Information Group 573 -- 574 -- The WWW service information group contains information about 575 -- the WWW services known by the SNMP agent. 577 wwwService OBJECT IDENTIFIER ::= { wwwMIBObjects 1 } 579 wwwServiceTable OBJECT-TYPE 580 SYNTAX SEQUENCE OF WwwServiceEntry 581 MAX-ACCESS not-accessible 582 STATUS current 583 DESCRIPTION 584 "The table of the WWW services known by the SNMP agent." 585 ::= { wwwService 1 } 587 wwwServiceEntry OBJECT-TYPE 588 SYNTAX WwwServiceEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "Details about a particular WWW service." 593 INDEX { wwwServiceIndex } 594 ::= { wwwServiceTable 1 } 596 WwwServiceEntry ::= SEQUENCE { 597 wwwServiceIndex Unsigned32, 598 wwwServiceDescription Utf8String, 599 wwwServiceContact Utf8String, 600 wwwServiceProtocol OBJECT IDENTIFIER, 601 wwwServiceName DisplayString, 602 wwwServiceType INTEGER, 603 wwwServiceUptime TimeStamp, 604 wwwServiceOperStatus WwwOperStatus, 605 wwwServiceLastChange TimeStamp 606 } 608 wwwServiceIndex OBJECT-TYPE 609 SYNTAX Unsigned32 610 MAX-ACCESS not-accessible 611 STATUS current 612 DESCRIPTION 613 "An integer used to uniquely identify a WWW service. The 614 value must be the same as the corresponding value of the 615 applSrvInst defined in the Application Management MIB 616 (APPLICATION-MIB) if the applSrvInst object is available. 617 It might be necessary to manually configure sub-agents in 618 order to meet this requirement." 619 ::= { wwwServiceEntry 1 } 621 wwwServiceDescription OBJECT-TYPE 622 SYNTAX Utf8String 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "Textual description of the WWW service. This shall include 627 at least the vendor and version number of the application 628 realizing the WWW service. In a minimal case, this might 629 be the Product Token (see RFC 2068) for the application." 630 ::= { wwwServiceEntry 2 } 632 wwwServiceContact OBJECT-TYPE 633 SYNTAX Utf8String 634 MAX-ACCESS read-only 635 STATUS current 636 DESCRIPTION 637 "The textual identification of the contact person for this 638 service, together with information on how to contact this 639 person. For instance, this might be a string containing an 640 email address, e.g. ''." 641 ::= { wwwServiceEntry 3 } 643 wwwServiceProtocol OBJECT-TYPE 644 SYNTAX OBJECT IDENTIFIER 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "An identification of the primary protocol in use by this 649 service. For Internet applications, the IANA maintains 650 a registry of the OIDs which correspond to well-known 651 application protocols. If the application protocol is not 652 listed in the registry, an OID value of the form 653 {applTCPProtoID port} or {applUDPProtoID port} are used for 654 TCP-based and UDP-based protocols, respectively. In either 655 case 'port' corresponds to the primary port number being 656 used by the protocol." 657 REFERENCE 658 "The OID values applTCPProtoID and applUDPProtoID are 659 defined in the NETWORK-SERVICES-MIB (RFC 2248)." 660 ::= { wwwServiceEntry 4 } 662 wwwServiceName OBJECT-TYPE 663 SYNTAX DisplayString 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "The fully qualified domain name by which this service is 668 known. This object must contain the virtual host name if 669 the service is realized for a virtual host." 670 ::= { wwwServiceEntry 5 } 672 wwwServiceType OBJECT-TYPE 673 SYNTAX INTEGER { 674 wwwOther(1), 675 wwwServer(2), 676 wwwClient(3), 677 wwwProxy(4), 678 wwwCachingProxy(5) 679 } 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The application type using or realizing this WWW service." 685 ::= { wwwServiceEntry 6 } 687 wwwServiceUptime OBJECT-TYPE 688 SYNTAX TimeStamp 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "The value of sysUpTime at the time the WWW service was last 693 initialized. If the service was last initialized prior to 694 the last initialization of the network management subsystem, 695 then this object contains a zero value." 696 ::= { wwwServiceEntry 7 } 698 wwwServiceOperStatus OBJECT-TYPE 699 SYNTAX WwwOperStatus 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "Indicates the operational status of the WWW service." 704 ::= { wwwServiceEntry 8 } 706 wwwServiceLastChange OBJECT-TYPE 707 SYNTAX TimeStamp 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "The value of sysUpTime at the time the WWW service entered 712 its current operational state. If the current state was 713 entered prior to the last initialization of the local 714 network management subsystem, then this object contains 715 a zero value." 716 ::= { wwwServiceEntry 9 } 718 -- The WWW Protocol Statistics Group 719 -- 720 -- The WWW protocol statistics group contains statistics about 721 -- the DTP requests and responses sent or received. 723 wwwProtocolStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 2 } 725 wwwSummaryTable OBJECT-TYPE 726 SYNTAX SEQUENCE OF WwwSummaryEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "The table providing overview statistics for the 731 WWW services on this system." 732 ::= { wwwProtocolStatistics 1 } 734 wwwSummaryEntry OBJECT-TYPE 735 SYNTAX WwwSummaryEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "Overview statistics for an individual service." 740 INDEX { wwwServiceIndex } 741 ::= { wwwSummaryTable 1 } 743 WwwSummaryEntry ::= SEQUENCE { 744 wwwSummaryInRequests Counter32, 745 wwwSummaryOutRequests Counter32, 746 wwwSummaryInResponses Counter32, 747 wwwSummaryOutResponses Counter32, 748 wwwSummaryInBytes Counter64, 749 wwwSummaryInBytesLow Counter32, 750 wwwSummaryOutBytes Counter64, 751 wwwSummaryOutBytesLow Counter32 752 } 754 wwwSummaryInRequests OBJECT-TYPE 755 SYNTAX Counter32 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "The number of requests successfully received." 760 ::= { wwwSummaryEntry 1 } 762 wwwSummaryOutRequests OBJECT-TYPE 763 SYNTAX Counter32 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "The number of requests generated." 768 ::= { wwwSummaryEntry 2 } 770 wwwSummaryInResponses OBJECT-TYPE 771 SYNTAX Counter32 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "The number of responses successfully received." 776 ::= { wwwSummaryEntry 3 } 778 wwwSummaryOutResponses OBJECT-TYPE 779 SYNTAX Counter32 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "The number of responses generated." 784 ::= { wwwSummaryEntry 4 } 786 wwwSummaryInBytes OBJECT-TYPE 787 SYNTAX Counter64 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The number of content bytes received." 792 ::= { wwwSummaryEntry 5 } 794 wwwSummaryInBytesLow OBJECT-TYPE 795 SYNTAX Counter32 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "The lowest thirty-two bits of wwwSummaryInBytes." 800 ::= { wwwSummaryEntry 6 } 802 wwwSummaryOutBytes OBJECT-TYPE 803 SYNTAX Counter64 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "The number of content bytes transmitted." 808 ::= { wwwSummaryEntry 7 } 810 wwwSummaryOutBytesLow OBJECT-TYPE 811 SYNTAX Counter32 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "The lowest thirty-two bits of wwwSummaryOutBytes." 816 ::= { wwwSummaryEntry 8 } 818 -- The WWW request tables contain detailed information about 819 -- requests send or received by WWW services. 821 wwwRequestInTable OBJECT-TYPE 822 SYNTAX SEQUENCE OF WwwRequestInEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "The table providing detailed statistics for requests 827 received by WWW services on this system." 828 ::= { wwwProtocolStatistics 2 } 830 wwwRequestInEntry OBJECT-TYPE 831 SYNTAX WwwRequestInEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "Request statistics for an individual service." 836 INDEX { wwwServiceIndex, wwwRequestInIndex } 837 ::= { wwwRequestInTable 1 } 839 WwwRequestInEntry ::= SEQUENCE { 840 wwwRequestInIndex WwwRequestType, 841 wwwRequestInCount Counter32, 842 wwwRequestInBytes Counter32, 843 wwwRequestInLastTime TimeStamp 844 } 846 wwwRequestInIndex OBJECT-TYPE 847 SYNTAX WwwRequestType 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "The particular request type the statistics apply to." 852 ::= { wwwRequestInEntry 1 } 854 wwwRequestInCount OBJECT-TYPE 855 SYNTAX Counter32 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "The number of requests of this type received by this 860 WWW service." 861 ::= { wwwRequestInEntry 2 } 863 wwwRequestInBytes OBJECT-TYPE 864 SYNTAX Counter32 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "The number of content bytes per request type received 869 by this WWW service." 870 ::= { wwwRequestInEntry 3 } 872 wwwRequestInLastTime OBJECT-TYPE 873 SYNTAX TimeStamp 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "The value of sysUpTime when the last byte of the last 878 complete request of this type was received by this WWW 879 service." 880 ::= { wwwRequestInEntry 4 } 882 wwwRequestOutTable OBJECT-TYPE 883 SYNTAX SEQUENCE OF WwwRequestOutEntry 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "The table providing detailed statistics for requests 888 generated by the services on this system." 889 ::= { wwwProtocolStatistics 3 } 891 wwwRequestOutEntry OBJECT-TYPE 892 SYNTAX WwwRequestOutEntry 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "Request statistics for an individual service." 897 INDEX { wwwServiceIndex, wwwRequestOutIndex } 898 ::= { wwwRequestOutTable 1 } 900 WwwRequestOutEntry ::= SEQUENCE { 901 wwwRequestOutIndex WwwRequestType, 902 wwwRequestOutCount Counter32, 903 wwwRequestOutBytes Counter32, 904 wwwRequestOutLastTime TimeStamp 905 } 907 wwwRequestOutIndex OBJECT-TYPE 908 SYNTAX WwwRequestType 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "The particular request type the statistics apply to." 913 ::= { wwwRequestOutEntry 1 } 915 wwwRequestOutCount OBJECT-TYPE 916 SYNTAX Counter32 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The number of requests of this type generated by this 921 WWW service." 922 ::= { wwwRequestOutEntry 2 } 924 wwwRequestOutBytes OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "The number of content bytes per requests type generated 930 by this WWW service." 931 ::= { wwwRequestOutEntry 3 } 933 wwwRequestOutLastTime OBJECT-TYPE 934 SYNTAX TimeStamp 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "The value of sysUpTime when the first byte of the last 939 request of this type was send by this WWW service." 940 ::= { wwwRequestOutEntry 4 } 942 -- The WWW response tables contain detailed information about 943 -- responses sent or received by WWW services. 945 wwwResponseInTable OBJECT-TYPE 946 SYNTAX SEQUENCE OF WwwResponseInEntry 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "The table providing detailed statistics for responses 951 received by WWW services on this system." 952 ::= { wwwProtocolStatistics 4 } 954 wwwResponseInEntry OBJECT-TYPE 955 SYNTAX WwwResponseInEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "Response statistics for an individual service." 960 INDEX { wwwServiceIndex, wwwResponseInIndex } 961 ::= { wwwResponseInTable 1 } 963 WwwResponseInEntry ::= SEQUENCE { 964 wwwResponseInIndex WwwResponseType, 965 wwwResponseInCount Counter32, 966 wwwResponseInBytes Counter32, 967 wwwResponseInLastTime TimeStamp 968 } 970 wwwResponseInIndex OBJECT-TYPE 971 SYNTAX WwwResponseType 972 MAX-ACCESS not-accessible 973 STATUS current 974 DESCRIPTION 975 "The particular response type the statistics apply to." 976 ::= { wwwResponseInEntry 1 } 978 wwwResponseInCount OBJECT-TYPE 979 SYNTAX Counter32 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "The number of responses of this type received by this 984 WWW service." 985 ::= { wwwResponseInEntry 2 } 987 wwwResponseInBytes OBJECT-TYPE 988 SYNTAX Counter32 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The number of content bytes per response type received 993 by this WWW service." 994 ::= { wwwResponseInEntry 3 } 996 wwwResponseInLastTime OBJECT-TYPE 997 SYNTAX TimeStamp 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The value of sysUpTime when the last byte of the last 1002 complete response of this type was received by this WWW 1003 service." 1004 ::= { wwwResponseInEntry 4 } 1006 wwwResponseOutTable OBJECT-TYPE 1007 SYNTAX SEQUENCE OF WwwResponseOutEntry 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "The table providing detailed statistics for responses 1012 generated by services on this system." 1014 ::= { wwwProtocolStatistics 5 } 1016 wwwResponseOutEntry OBJECT-TYPE 1017 SYNTAX WwwResponseOutEntry 1018 MAX-ACCESS not-accessible 1019 STATUS current 1020 DESCRIPTION 1021 "Response statistics for an individual service." 1022 INDEX { wwwServiceIndex, wwwResponseOutIndex } 1023 ::= { wwwResponseOutTable 1 } 1025 WwwResponseOutEntry ::= SEQUENCE { 1026 wwwResponseOutIndex WwwResponseType, 1027 wwwResponseOutCount Counter32, 1028 wwwResponseOutBytes Counter32, 1029 wwwResponseOutLastTime TimeStamp 1030 } 1032 wwwResponseOutIndex OBJECT-TYPE 1033 SYNTAX WwwResponseType 1034 MAX-ACCESS not-accessible 1035 STATUS current 1036 DESCRIPTION 1037 "The particular response type the statistics apply to." 1038 ::= { wwwResponseOutEntry 1 } 1040 wwwResponseOutCount OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The number of responses of this type generated by this 1046 WWW service." 1047 ::= { wwwResponseOutEntry 2 } 1049 wwwResponseOutBytes OBJECT-TYPE 1050 SYNTAX Counter32 1051 MAX-ACCESS read-only 1052 STATUS current 1053 DESCRIPTION 1054 "The number of content bytes per response type generated 1055 by this WWW service." 1056 ::= { wwwResponseOutEntry 3 } 1058 wwwResponseOutLastTime OBJECT-TYPE 1059 SYNTAX TimeStamp 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "The value of sysUpTime when the first byte of the last 1064 response of this type was sent by this WWW service." 1065 ::= { wwwResponseOutEntry 4 } 1067 -- The WWW Document Statistics Group 1068 -- 1069 -- The WWW document statistics group contains statistics about 1070 -- document read attempts. 1072 wwwDocumentStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 3 } 1074 wwwDocCtrlTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF WwwDocCtrlEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "A table which controls how the MIB implementation 1080 collects and maintains document statistics." 1081 ::= { wwwDocumentStatistics 1 } 1083 wwwDocCtrlEntry OBJECT-TYPE 1084 SYNTAX WwwDocCtrlEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "An entry used to configure the wwwDocLastNTable, 1089 the wwwDocBucketTable, the wwwDocAccessTopNTable, 1090 and the wwwDocBytesTopNTable." 1091 INDEX { wwwServiceIndex } 1092 ::= { wwwDocCtrlTable 1 } 1094 WwwDocCtrlEntry ::= SEQUENCE { 1095 wwwDocCtrlLastNSize Unsigned32, 1096 wwwDocCtrlLastNLock TimeTicks, 1097 wwwDocCtrlBuckets Unsigned32, 1098 wwwDocCtrlBucketTimeInterval TimeInterval, 1099 wwwDocCtrlTopNSize Unsigned32 1100 } 1102 wwwDocCtrlLastNSize OBJECT-TYPE 1103 SYNTAX Unsigned32 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 "The maximum number of entries in the wwwDocLastNTable." 1108 DEFVAL { 25 } 1109 ::= { wwwDocCtrlEntry 1 } 1111 wwwDocCtrlLastNLock OBJECT-TYPE 1112 SYNTAX TimeTicks 1113 MAX-ACCESS read-write 1114 STATUS current 1115 DESCRIPTION 1116 "This object allows a manager to lock the wwwDocLastNTable 1117 in order to retrieve the wwwDocLastNTable in a consistent 1118 state. The agent is expected to take a snapshot of the 1119 wwwDocLastNTable when it is locked and to continue updating 1120 the real wwwDocLastNTable table so that recent information is 1121 available as soon as the wwwDocLastNTable is unlocked again. 1123 Setting this object to a value greater than 0 will lock 1124 the table. The timer ticks backwards until it reaches 0. 1125 The table unlocks automatically once the timer reaches 0 1126 and the timer stops ticking. 1128 A manager can increase the timer to request more time to 1129 read the table. However, any attempt to decrease the timer 1130 will fail with an inconsistentValue error. This rule ensures 1131 that multiple managers can simultaneously lock and retrieve 1132 the wwwDocLastNTable." 1133 ::= { wwwDocCtrlEntry 2 } 1135 wwwDocCtrlBuckets OBJECT-TYPE 1136 SYNTAX Unsigned32 1137 MAX-ACCESS read-write 1138 STATUS current 1139 DESCRIPTION 1140 "The maximum number of buckets maintained by the agent 1141 before the oldest bucket is deleted. The buckets are used 1142 to populate the wwwDocAccessTopNTable and the 1143 wwwDocBytesTopNTable." 1144 DEFVAL { 2 } 1145 ::= { wwwDocCtrlEntry 3 } 1147 wwwDocCtrlBucketTimeInterval OBJECT-TYPE 1148 SYNTAX TimeInterval 1149 MAX-ACCESS read-write 1150 STATUS current 1151 DESCRIPTION 1152 "The time interval after which a new bucket is created. 1153 Changing this object has no effect on existing buckets." 1155 DEFVAL { 90000 } -- 15 minutes (resolution .01 s) 1156 ::= { wwwDocCtrlEntry 4 } 1158 wwwDocCtrlTopNSize OBJECT-TYPE 1159 SYNTAX Unsigned32 1160 MAX-ACCESS read-write 1161 STATUS current 1162 DESCRIPTION 1163 "The maximum number of entries shown in the 1164 wwwDocAccessTopNTable and the wwwDocBytesTopNTable. 1165 Changing this object has no effect on existing buckets." 1166 DEFVAL { 25 } 1167 ::= { wwwDocCtrlEntry 5 } 1169 wwwDocLastNTable OBJECT-TYPE 1170 SYNTAX SEQUENCE OF WwwDocLastNEntry 1171 MAX-ACCESS not-accessible 1172 STATUS current 1173 DESCRIPTION 1174 "The table which logs the last N access attempts." 1175 ::= { wwwDocumentStatistics 2 } 1177 wwwDocLastNEntry OBJECT-TYPE 1178 SYNTAX WwwDocLastNEntry 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION 1182 "An entry which describes a recent access attempt." 1183 INDEX { wwwServiceIndex, wwwDocLastNIndex } 1184 ::= { wwwDocLastNTable 1 } 1186 WwwDocLastNEntry ::= SEQUENCE { 1187 wwwDocLastNIndex Unsigned32, 1188 wwwDocLastNName WwwDocName, 1189 wwwDocLastNTimeStamp DateAndTime, 1190 wwwDocLastNRequestType WwwRequestType, 1191 wwwDocLastNResponseType WwwResponseType, 1192 wwwDocLastNStatusMsg DisplayString, 1193 wwwDocLastNBytes Unsigned32 1194 } 1196 wwwDocLastNIndex OBJECT-TYPE 1197 SYNTAX Unsigned32 1198 MAX-ACCESS not-accessible 1199 STATUS current 1200 DESCRIPTION 1201 "An arbitrary monotonically increasing integer number used 1202 for indexing the wwwDocLastNTable. The first document 1203 accessed appears in the table with this index value equal 1204 to one. Each subsequent document is indexed with the next 1205 sequential index value. The Nth document accessed will be 1206 indexed by N. This table presents a sliding window of the 1207 last N documents accessed where N is the value of 1208 wwwDocCtrlLastNSize. Thus at any given time, the entries in 1209 this table will be indexed by N-wwwDocCtrlLastNSize thru 1210 N. The wwwDocCtrlLastNLock attribute can be used to lock 1211 this table to allow the manager to read its contents." 1212 ::= { wwwDocLastNEntry 1 } 1214 wwwDocLastNName OBJECT-TYPE 1215 SYNTAX WwwDocName 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "The name of the document for which access was attempted." 1220 ::= { wwwDocLastNEntry 2 } 1222 wwwDocLastNTimeStamp OBJECT-TYPE 1223 SYNTAX DateAndTime 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "The date and time of the last attempt to access this 1228 document." 1229 ::= { wwwDocLastNEntry 3 } 1231 wwwDocLastNRequestType OBJECT-TYPE 1232 SYNTAX WwwRequestType 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "The protocol request type which was received by the 1237 server when this document access was attempted." 1238 ::= { wwwDocLastNEntry 4 } 1240 wwwDocLastNResponseType OBJECT-TYPE 1241 SYNTAX WwwResponseType 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "The protocol response type which was sent to the client 1246 as a result of this attempt to access a document. This 1247 object contains the type of the primary response if 1248 there were multiple responses to a single request." 1249 ::= { wwwDocLastNEntry 5 } 1251 wwwDocLastNStatusMsg OBJECT-TYPE 1252 SYNTAX DisplayString 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "This object contains a human readable description of the 1257 reason why the wwwDocLastNResponseType was returned to the 1258 client. This object defines the implementation-specific 1259 reason if the value of wwwDocLastNResponseType indicates 1260 an error. For example, this object can indicate that the 1261 requested document could not be transferred due to a 1262 timeout condition or the document could not be transferred 1263 because a 'soft link' pointing to the document could not be 1264 resolved." 1265 ::= { wwwDocLastNEntry 6 } 1267 wwwDocLastNBytes OBJECT-TYPE 1268 SYNTAX Unsigned32 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "The number of content bytes that were returned as a 1273 result of this attempt to access a document." 1274 ::= { wwwDocLastNEntry 7 } 1276 wwwDocBucketTable OBJECT-TYPE 1277 SYNTAX SEQUENCE OF WwwDocBucketEntry 1278 MAX-ACCESS not-accessible 1279 STATUS current 1280 DESCRIPTION 1281 "This table provides administrative summary information for 1282 the buckets maintained per WWW service." 1283 ::= { wwwDocumentStatistics 3 } 1285 wwwDocBucketEntry OBJECT-TYPE 1286 SYNTAX WwwDocBucketEntry 1287 MAX-ACCESS not-accessible 1288 STATUS current 1289 DESCRIPTION 1290 "An entry which describes the parameters associated with a 1291 particular bucket." 1292 INDEX { wwwServiceIndex, wwwDocBucketIndex } 1293 ::= { wwwDocBucketTable 1 } 1295 WwwDocBucketEntry ::= SEQUENCE { 1296 wwwDocBucketIndex Unsigned32, 1297 wwwDocBucketTimeStamp TimeStamp, 1298 wwwDocBucketAccesses Unsigned32, 1299 wwwDocBucketDocuments Unsigned32, 1300 wwwDocBucketBytes Unsigned32 1301 } 1303 wwwDocBucketIndex OBJECT-TYPE 1304 SYNTAX Unsigned32 1305 MAX-ACCESS not-accessible 1306 STATUS current 1307 DESCRIPTION 1308 "An arbitrary monotonically increasing integer number 1309 used for indexing the wwwDocBucketTable. The index number 1310 wraps to 1 whenever the maximum value is reached." 1311 ::= { wwwDocBucketEntry 1 } 1313 wwwDocBucketTimeStamp OBJECT-TYPE 1314 SYNTAX TimeStamp 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "The value of sysUpTime when the bucket was made available." 1319 ::= { wwwDocBucketEntry 2 } 1321 wwwDocBucketAccesses OBJECT-TYPE 1322 SYNTAX Unsigned32 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "The total number of access attempts for any document 1327 provided by this WWW service during the time interval 1328 over which this bucket was created." 1329 ::= { wwwDocBucketEntry 3 } 1331 wwwDocBucketDocuments OBJECT-TYPE 1332 SYNTAX Unsigned32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "The total number of different documents for which access 1337 was attempted this this WWW service during the time interval 1338 over which this bucket was created." 1339 ::= { wwwDocBucketEntry 4 } 1341 wwwDocBucketBytes OBJECT-TYPE 1342 SYNTAX Unsigned32 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The total number of content bytes which were transferred 1347 from this WWW service during the time interval over which 1348 this bucket was created." 1349 ::= { wwwDocBucketEntry 5 } 1351 wwwDocAccessTopNTable OBJECT-TYPE 1352 SYNTAX SEQUENCE OF WwwDocAccessTopNEntry 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "The table of the most frequently accessed documents in a 1357 given bucket. This table is sorted by the column 1358 wwwDocAccessTopNAccesses. Entries having the same number 1359 of accesses are secondarily sorted by wwwDocAccessTopNBytes. 1360 Entries with the same number of accesses and the same 1361 number of bytes will have an arbitrary order." 1362 ::= { wwwDocumentStatistics 4 } 1364 wwwDocAccessTopNEntry OBJECT-TYPE 1365 SYNTAX WwwDocAccessTopNEntry 1366 MAX-ACCESS not-accessible 1367 STATUS current 1368 DESCRIPTION 1369 "An entry in the top N table sorted by document accesses." 1370 INDEX { wwwServiceIndex, wwwDocBucketIndex, 1371 wwwDocAccessTopNIndex } 1372 ::= { wwwDocAccessTopNTable 1 } 1374 WwwDocAccessTopNEntry ::= SEQUENCE { 1375 wwwDocAccessTopNIndex Unsigned32, 1376 wwwDocAccessTopNName WwwDocName, 1377 wwwDocAccessTopNAccesses Unsigned32, 1378 wwwDocAccessTopNBytes Unsigned32, 1379 wwwDocAccessTopNLastResponseType WwwResponseType 1380 } 1382 wwwDocAccessTopNIndex OBJECT-TYPE 1383 SYNTAX Unsigned32 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "An arbitrary monotonically increasing integer number 1388 used for indexing the wwwDocAccessTopNTable. The index is 1389 inversely correlated to the sorting order of the table. The 1390 document with the highest access count will get the index 1391 value 1." 1392 ::= { wwwDocAccessTopNEntry 1 } 1394 wwwDocAccessTopNName OBJECT-TYPE 1395 SYNTAX WwwDocName 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "The name of the document for which access was attempted." 1400 ::= { wwwDocAccessTopNEntry 2 } 1402 wwwDocAccessTopNAccesses OBJECT-TYPE 1403 SYNTAX Unsigned32 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The total number of access attempts for this document." 1408 ::= { wwwDocAccessTopNEntry 3 } 1410 wwwDocAccessTopNBytes OBJECT-TYPE 1411 SYNTAX Unsigned32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The total number of content bytes that were transmitted 1416 as a result of attempts to access this document." 1417 ::= { wwwDocAccessTopNEntry 4 } 1419 wwwDocAccessTopNLastResponseType OBJECT-TYPE 1420 SYNTAX WwwResponseType 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "The protocol response type which was sent to the client 1425 as a result of the last attempt to access this document. 1426 This object contains the type of the primary response if 1427 there were multiple responses to a single request." 1428 ::= { wwwDocAccessTopNEntry 5 } 1430 wwwDocBytesTopNTable OBJECT-TYPE 1431 SYNTAX SEQUENCE OF WwwDocBytesTopNEntry 1432 MAX-ACCESS not-accessible 1433 STATUS current 1434 DESCRIPTION 1435 "The table of the documents which caused most network 1436 traffic in a given bucket. This table is sorted by the 1437 column wwwDocBytesTopNBytes. Entries having the same number 1438 bytes are secondarily sorted by wwwDocBytesTopNAccesses. 1439 Entries with the same number of accesses and the same 1440 number of bytes will have an arbitrary order." 1441 ::= { wwwDocumentStatistics 5 } 1443 wwwDocBytesTopNEntry OBJECT-TYPE 1444 SYNTAX WwwDocBytesTopNEntry 1445 MAX-ACCESS not-accessible 1446 STATUS current 1447 DESCRIPTION 1448 "An entry in the top N table sorted by network traffic." 1449 INDEX { wwwServiceIndex, wwwDocBucketIndex, 1450 wwwDocBytesTopNIndex } 1451 ::= { wwwDocBytesTopNTable 1 } 1453 WwwDocBytesTopNEntry ::= SEQUENCE { 1454 wwwDocBytesTopNIndex Unsigned32, 1455 wwwDocBytesTopNName WwwDocName, 1456 wwwDocBytesTopNAccesses Unsigned32, 1457 wwwDocBytesTopNBytes Unsigned32, 1458 wwwDocBytesTopNLastResponseType WwwResponseType 1459 } 1461 wwwDocBytesTopNIndex OBJECT-TYPE 1462 SYNTAX Unsigned32 1463 MAX-ACCESS not-accessible 1464 STATUS current 1465 DESCRIPTION 1466 "An arbitrary monotonically increasing integer number 1467 used for indexing the wwwDocBytesTopNTable. The index is 1468 inversely correlated to the sorting order of the table. The 1469 document with the highest byte count will get the index 1470 value 1." 1471 ::= { wwwDocBytesTopNEntry 1 } 1473 wwwDocBytesTopNName OBJECT-TYPE 1474 SYNTAX WwwDocName 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "The name of the document for which access was attempted." 1479 ::= { wwwDocBytesTopNEntry 2 } 1481 wwwDocBytesTopNAccesses OBJECT-TYPE 1482 SYNTAX Unsigned32 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "The total number of access attempts for this document." 1487 ::= { wwwDocBytesTopNEntry 3 } 1489 wwwDocBytesTopNBytes OBJECT-TYPE 1490 SYNTAX Unsigned32 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "The total number of content bytes that were transmitted 1495 as a result of attempts to access this document." 1496 ::= { wwwDocBytesTopNEntry 4 } 1498 wwwDocBytesTopNLastResponseType OBJECT-TYPE 1499 SYNTAX WwwResponseType 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "The protocol response type which was sent to the client 1504 as a result of the last attempt to access this document. 1505 This object contains the type of the primary response if 1506 there were multiple responses to a single request." 1507 ::= { wwwDocBytesTopNEntry 5 } 1509 -- 1510 -- Conformance Definitions 1511 -- 1513 wwwMIBCompliances OBJECT IDENTIFIER ::= { wwwMIBConformance 1 } 1514 wwwMIBGroups OBJECT IDENTIFIER ::= { wwwMIBConformance 2 } 1516 wwwMinimalCompliance MODULE-COMPLIANCE 1517 STATUS current 1518 DESCRIPTION 1519 "The compliance statement for SNMP agents which implement 1520 the minimal subset of the WWW-MIB. Implementors might 1521 choose this subset for high-performance server where 1522 full compliance might be to expensive." 1523 MODULE -- this module 1524 MANDATORY-GROUPS { 1525 wwwServiceGroup, 1526 wwwSummaryGroup 1527 } 1528 ::= { wwwMIBCompliances 1 } 1530 wwwFullCompliance MODULE-COMPLIANCE 1531 STATUS current 1532 DESCRIPTION 1533 "The compliance statement for SNMP agents which implement 1534 the full WWW-MIB. 1536 The wwwRequestInTable and wwwResponseOutTable tables will 1537 always be empty for a pure WWW client implementation and 1538 wwwSummaryInRequests and wwwSummaryOutResponses will both 1539 be zero. 1541 The wwwRequestOutTable and wwwResponseInTable tables will 1542 always be empty for a pure WWW server implementation and 1543 wwwSummaryOutRequests and wwwSummaryInResponses will both 1544 be zero. 1546 An implementation for a WWW proxy must be capable to 1547 populate all tables." 1548 MODULE -- this module 1549 MANDATORY-GROUPS { 1550 wwwServiceGroup, 1551 wwwSummaryGroup, 1552 wwwRequestInGroup, 1553 wwwRequestOutGroup, 1554 wwwResponseInGroup, 1555 wwwResponseOutGroup, 1556 wwwDocumentGroup 1557 } 1558 ::= { wwwMIBCompliances 2 } 1560 wwwServiceGroup OBJECT-GROUP 1561 OBJECTS { 1562 wwwServiceDescription, 1563 wwwServiceContact, 1564 wwwServiceProtocol, 1565 wwwServiceName, 1566 wwwServiceType, 1567 wwwServiceUptime, 1568 wwwServiceOperStatus, 1569 wwwServiceLastChange 1570 } 1571 STATUS current 1572 DESCRIPTION 1573 "A collection of objects providing information about 1574 the WWW services known by the SNMP agent." 1576 ::= { wwwMIBGroups 1 } 1578 wwwSummaryGroup OBJECT-GROUP 1579 OBJECTS { 1580 wwwSummaryInRequests, 1581 wwwSummaryOutRequests, 1582 wwwSummaryInResponses, 1583 wwwSummaryOutResponses, 1584 wwwSummaryInBytes, 1585 wwwSummaryInBytesLow, 1586 wwwSummaryOutBytes, 1587 wwwSummaryOutBytesLow 1588 } 1589 STATUS current 1590 DESCRIPTION 1591 "A collection of objects providing summary statistics 1592 about requests and responses generated and received 1593 by a WWW service." 1594 ::= { wwwMIBGroups 2 } 1596 wwwRequestInGroup OBJECT-GROUP 1597 OBJECTS { 1598 wwwRequestInCount, 1599 wwwRequestInBytes, 1600 wwwRequestInLastTime 1601 } 1602 STATUS current 1603 DESCRIPTION 1604 "A collection of objects providing detailed statistics 1605 about requests received by a WWW service." 1606 ::= { wwwMIBGroups 3 } 1608 wwwRequestOutGroup OBJECT-GROUP 1609 OBJECTS { 1610 wwwRequestOutCount, 1611 wwwRequestOutBytes, 1612 wwwRequestOutLastTime 1613 } 1614 STATUS current 1615 DESCRIPTION 1616 "A collection of objects providing detailed statistics 1617 about requests generated by a WWW service." 1618 ::= { wwwMIBGroups 4 } 1620 wwwResponseInGroup OBJECT-GROUP 1621 OBJECTS { 1622 wwwResponseInCount, 1623 wwwResponseInBytes, 1624 wwwResponseInLastTime 1625 } 1626 STATUS current 1627 DESCRIPTION 1628 "A collection of objects providing detailed statistics 1629 about responses received by a WWW service." 1630 ::= { wwwMIBGroups 5 } 1632 wwwResponseOutGroup OBJECT-GROUP 1633 OBJECTS { 1634 wwwResponseOutCount, 1635 wwwResponseOutBytes, 1636 wwwResponseOutLastTime 1637 } 1638 STATUS current 1639 DESCRIPTION 1640 "A collection of objects providing detailed statistics 1641 about responses generated by a WWW service." 1642 ::= { wwwMIBGroups 6 } 1644 wwwDocumentGroup OBJECT-GROUP 1645 OBJECTS { 1646 wwwDocCtrlLastNSize, 1647 wwwDocCtrlLastNLock, 1648 wwwDocCtrlBuckets, 1649 wwwDocCtrlBucketTimeInterval, 1650 wwwDocCtrlTopNSize, 1651 wwwDocLastNName, 1652 wwwDocLastNTimeStamp, 1653 wwwDocLastNRequestType, 1654 wwwDocLastNResponseType, 1655 wwwDocLastNStatusMsg, 1656 wwwDocLastNBytes, 1657 wwwDocBucketTimeStamp, 1658 wwwDocBucketAccesses, 1659 wwwDocBucketDocuments, 1660 wwwDocBucketBytes, 1661 wwwDocAccessTopNName, 1662 wwwDocAccessTopNAccesses, 1663 wwwDocAccessTopNBytes, 1664 wwwDocAccessTopNLastResponseType, 1665 wwwDocBytesTopNName, 1666 wwwDocBytesTopNAccesses, 1667 wwwDocBytesTopNBytes, 1668 wwwDocBytesTopNLastResponseType 1669 } 1670 STATUS current 1671 DESCRIPTION 1672 "A collection of objects providing information about 1673 accesses to documents." 1674 ::= { wwwMIBGroups 7 } 1676 END 1678 7. Document Transfer Protocol Mappings 1680 This section describes how existing protocols such as HTTP [19,20] 1681 and FTP [21] can be mapped on the abstract Document Transfer Protocol 1682 (DTP) used within the definitions of the WWW MIB. Every mapping must 1683 define the identifier which is used to uniquely identify the transfer 1684 protocol. In addition, the mappings must define how requests and 1685 responses are identified. 1687 7.1. The HyperText Transfer Protocol 1689 The HyperText Transfer Protocol (HTTP) [19,20] is an application- 1690 level protocol used to transfer hypermedia documents in a distributed 1691 networked environment. HTTP is based on the request/response paradigm 1692 and can be mapped on the abstract DTP easily. 1694 The HTTP protocol usually runs over TCP and uses the well-known TCP 1695 port 80. Therefore, the default value for the wwwServiceProtocol 1696 object is { applTCPProtoID 80 }. 1698 HTTP allows for both requests and responses and an open-ended set of 1699 message types. The general message syntax of HTTP is therefore used 1700 for the protocol mapping. The BNF specification of the general HTTP 1701 message syntax as defined in [8] is as follows: 1703 HTTP-message = start-line 1704 *message-header 1705 CRLF 1706 [ message-body ] 1708 start-line = Request-Line | Status-Line 1710 Request-Line = Method SP Request-URI SP HTTP-Version CRLF 1712 Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF 1714 Every HTTP-message where the start-line is a Request-Line is 1715 considered a request in the abstract DTP. Every HTTP-message where 1716 the start-line is a Status-Line is considered a response in the 1717 abstract DTP. The mappings of wwwRequestType and wwwResponseType are 1718 defined as follows: 1720 o The wwwRequestType corresponds to the method token in the 1721 Request-Line. 1723 o The wwwResponseType corresponds to the Status-Code in the 1724 Status-Line. 1726 7.2. The File Transfer Protocol 1728 The File Transfer Protocol (FTP) [21] is an application-level 1729 protocol used to transfer files between hosts connected by the TCP/IP 1730 suite of protocols. FTP is based on a request/response paradigm and 1731 is mapped on the abstract DTP as defined in this section. The FTP 1732 model as defined in [21] is depicted below. 1734 ------------- 1735 |+---------+| 1736 || User || -------- 1737 ||Interface|<--->| User | 1738 |+----|----+| -------- 1739 ---------- | | | 1740 |+------+| control connection |+----|----+| 1741 ||Server|<------------------->|| Client || 1742 || PI || Commands/Replies || PI || 1743 |+--|---+| |+----|----+| 1744 | | | | | | 1745 -------- |+--|---+| Data |+----|----+| -------- 1746 | File |<--->|Server|<------------------->|| Client |<--->| File | 1747 |System| || DTP || Connection || DTP || |System| 1748 -------- |+------+| |+---------+| -------- 1749 ---------- ------------- 1751 FTP uses two different connection types between a client and a server 1752 to transfer files. The control connection is persistent during a FTP 1753 session and used to exchange FTP commands and associated replies. The 1754 data connection is only available when bulk data has to be 1755 transferred. 1757 The FTP protocol usually runs over TCP and uses the well-known TCP 1758 port 21 to setup the control connection. Therefore, the default value 1759 for the wwwServiceProtocol object is { applTCPProtoID 21 }. 1761 Every FTP command is considered a request in the abstract DTP. Every 1762 FTP reply is considered a response in the abstract DTP. It should be 1763 noted that a single FTP command can result in multiple FTP replies 1764 (e.g. preliminary positive replies). The primary response for a FTP 1765 request contains a status code of the form 2xy, 3xy, 4xy or 5xy. See 1766 section 4.2 in [21] for the exact meaning of these status codes. The 1767 mappings for wwwRequestType and wwwResponseType are defined as 1768 follows: 1770 o The wwwRequestType corresponds to the FTP command token. 1772 o The wwwResponseType corresponds to the three-digit code which 1773 starts a reply. Multi-line replies with the same three-digit 1774 code are counted as a single DTP response. 1776 8. Security Considerations 1778 The MIB objects defined in the memo might disclose information that 1779 should be protected. In particular, the document statistics group 1780 contains traffic information, which includes the names of documents 1781 that were a target of protocol operations. It is therefore advisable 1782 to use SNMP access control and SNMP security mechanism (where 1783 available) in order to protect this information in sensitive 1784 environments. 1786 The protocol statistics are less sensitive, because they do not 1787 contain details about the target of individual requests/responses. 1788 However, it is suggested that sites configure MIB views so that a 1789 user of this MIB can only see the portion of the statistics that 1790 belong to the WWW services managed by that user. 1792 9. Intellectual Property 1794 The IETF takes no position regarding the validity or scope of any 1795 intellectual property or other rights that might be claimed to 1796 pertain to the implementation or use of the technology described in 1797 this document or the extent to which any license under such rights 1798 might or might not be available; neither does it represent that it 1799 has made any effort to identify any such rights. Information on the 1800 IETF's procedures with respect to rights in standards-track and 1801 standards-related documentation can be found in BCP-11. Copies of 1802 claims of rights made available for publication and any assurances of 1803 licenses to be made available, or the result of an attempt made to 1804 obtain a general license or permission for the use of such 1805 proprietary rights by implementors or users of this specification can 1806 be obtained from the IETF Secretariat. 1808 The IETF invites any interested party to bring to its attention any 1809 copyrights, patents or patent applications, or other proprietary 1810 rights which may cover technology that may be required to practice 1811 this standard. Please address the information to the IETF Executive 1812 Director. 1814 10. Acknowledgments 1816 This document was produced by the Application MIB working group. The 1817 editors gratefully acknowledge the comments of the following 1818 individuals: 1820 Mark Gamble, Cheryl Krupczak, Randy Preshun, John Saperia, 1821 Bob Stewart, Martin Toet, Chris Wellens 1823 11. Editors' Addresses 1825 Harrie Hazewinkel Email: harrie.hazewinkel@jrc.it 1826 Joint Research Centre of the E.C. Tel: +39 (0)332 786322 1827 via Fermi - Ispra 21020 (VA) Fax: +39 (0)332 785641 1828 Italy 1830 Carl W. Kalbfleisch Email: cwk@verio.net 1831 Verio, Inc. Tel: +1 972 238-8303 1832 1950 Stemmons Frwy Fax: +1 972 238-0268 1833 2004 INFOMART 1834 Dallas, TX 75207 1835 USA 1837 Juergen Schoenwaelder Email: schoenw@ibr.cs.tu-bs.de 1838 TU Braunschweig Tel: +49 531 391-3683 1839 Bueltenweg 74/75 Fax: +49 531 489-5936 1840 38106 Braunschweig 1841 Germany 1843 12. References 1845 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1846 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1847 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1848 January 1998 1850 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1851 Management Information for TCP/IP-based Internets", RFC 1155, 1852 Performance Systems International, Hughes LAN Systems, May 1990 1854 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1855 Performance Systems International, Hughes LAN Systems, March 1991 1857 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1858 RFC 1215, Performance Systems International, March 1991 1860 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1861 of Management Information for Version 2 of the Simple Network 1862 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 1863 Systems, Inc., Dover Beach Consulting, Inc., International Network 1864 Services, January 1996. 1866 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1867 Conventions for Version 2 of the Simple Network Management Protocol 1868 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1869 Dover Beach Consulting, Inc., International Network Services, 1870 January 1996. 1872 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 1873 Statements for Version 2 of the Simple Network Management Protocol 1874 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 1875 Dover Beach Consulting, Inc., International Network Services, 1876 January 1996. 1878 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1879 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1880 International, Performance Systems International, MIT Laboratory 1881 for Computer Science, May 1990. 1883 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1884 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1885 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1886 International Network Services, January 1996. 1888 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1889 Mappings for Version 2 of the Simple Network Management Protocol 1890 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1891 Dover Beach Consulting, Inc., International Network Services, 1892 January 1996. 1894 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1895 Processing and Dispatching for the Simple Network Management 1896 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1897 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1899 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1900 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1901 2274, IBM T. J. Watson Research, January 1998. 1903 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1904 Operations for Version 2 of the Simple Network Management Protocol 1905 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1906 Dover Beach Consulting, Inc., International Network Services, 1907 January 1996. 1909 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1910 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1911 Systems, January 1998 1913 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1914 Control Model (VACM) for the Simple Network Management Protocol 1915 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1916 Cisco Systems, Inc., January 1998 1918 [16] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 1919 Standards Process", BCP 11, RFC 2028, October 1996. 1921 [17] T. Berners-Lee, "Universal Resource Identifiers in WWW", RFC 1630, 1922 CERN, June 1994. 1924 [18] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource 1925 Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of 1926 Minnesota, December 1994. 1928 [19] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext Transfer 1929 Protocol -- HTTP/1.0", RFC 1945, MIT/LCS, UC Irvine, MIT/LCS, May 1930 1996. 1932 [20] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners- 1933 Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, UC 1934 Irvine, DEC, DEC, MIT/LCS, January 1997. 1936 [21] Postel, J., and J.K. Reynolds, "File Transfer Protocol (FTP)", STD 1937 9, RFC 959, USC/ISI, October 1985. 1939 [22] C. Kalbfleisch, "Applicability of Standards Track MIBs to 1940 Management of World Wide Web Servers", RFC 2039, OnRamp 1941 Technologies, November 1996. 1943 [23] Krupczak, C., and J. Saperia, "Definitions of System-Level Managed 1944 Objects for Applications", RFC 2287, Empire Technologies, BGS 1945 Systems, February 1998. 1947 [24] Kalbfleisch, C., Krupczak, C., Preshun, R., and J. Saperia, 1948 "Application Management MIB", draft-ietf-applmib-mib-08.txt, Verio, 1949 Empire Technologies, BMC Software, BGS Systems, July 1998. 1951 [25] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A 1952 Proposed Standard for the Stream-Based Transmission of News", RFC 1953 977, UC San Diego & UC Berkeley, February 1986. 1955 [26] Callaghan, B., "WebNFS Client Specification", RFC 2054, Sun 1956 Microsystems, October 1996 1958 [27] Callaghan, B., "WebNFS Server Specification", RFC 2055, Sun 1959 Microsystems, October 1996 1961 13. Full Copyright Statement 1963 Copyright (C) The Internet Society (1998). All Rights Reserved. 1965 This document and translations of it may be copied and furnished to 1966 others, and derivative works that comment on or otherwise explain it 1967 or assist in its implementation may be prepared, copied, published 1968 and distributed, in whole or in part, without restriction of any 1969 kind, provided that the above copyright notice and this paragraph are 1970 included on all such copies and derivative works. However, this 1971 document itself may not be modified in any way, such as by removing 1972 the copyright notice or references to the Internet Society or other 1973 Internet organizations, except as needed for the purpose of 1974 developing Internet standards in which case the procedures for 1975 copyrights defined in the Internet Standards process must be 1976 followed, or as required to translate it into languages other than 1977 English. 1979 The limited permissions granted above are perpetual and will not be 1980 revoked by the Internet Society or its successors or assigns. 1982 This document and the information contained herein is provided on an 1983 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1984 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1985 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1986 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1987 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1989 Table of Contents 1991 1 Abstract ..................................................... 2 1992 2 The SNMP Management Framework ................................ 2 1993 3 Terminology .................................................. 3 1994 4 Overview ..................................................... 4 1995 4.1 Purpose and Requirements ................................... 5 1996 4.2 Relationship to other Standards Efforts .................... 5 1997 4.3 WWW Services ............................................... 5 1998 4.4 Document Transfer Protocol ................................. 6 1999 5 Structure of the MIB ......................................... 7 2000 5.1 Service Information Group .................................. 7 2001 5.2 Protocol Statistics Group .................................. 8 2002 5.3 Document Statistics Group .................................. 8 2003 6 Definitions .................................................. 11 2004 7 Document Transfer Protocol Mappings .......................... 38 2005 7.1 The HyperText Transfer Protocol ............................ 38 2006 7.2 The File Transfer Protocol ................................. 39 2007 8 Security Considerations ...................................... 40 2008 9 Intellectual Property ........................................ 40 2009 10 Acknowledgments ............................................. 41 2010 11 Editors' Addresses .......................................... 41 2011 12 References .................................................. 42 2012 13 Full Copyright Statement .................................... 45