| 1 |
<pre>Network Working Group H. Hazewinkel |
| 2 |
Request for Comments: 2594 Joint Research Centre of the E.C. |
| 3 |
Category: Standards Track C. Kalbfleisch |
| 4 |
Verio, Inc. |
| 5 |
J. Schoenwaelder |
| 6 |
TU Braunschweig |
| 7 |
May 1999 |
| 8 |
|
| 9 |
<span class="h1">Definitions of Managed Objects for WWW Services</span> |
| 10 |
|
| 11 |
Status of this Memo |
| 12 |
|
| 13 |
This document specifies an Internet standards track protocol for the |
| 14 |
Internet community, and requests discussion and suggestions for |
| 15 |
improvements. Please refer to the current edition of the "Internet |
| 16 |
Official Protocol Standards" (STD 1) for the standardization state |
| 17 |
and status of this protocol. Distribution of this memo is unlimited. |
| 18 |
|
| 19 |
Copyright Notice |
| 20 |
|
| 21 |
Copyright (C) The Internet Society (1999). All Rights Reserved. |
| 22 |
|
| 23 |
Abstract |
| 24 |
|
| 25 |
This memo defines a portion of the Management Information Base (MIB) |
| 26 |
for use with network management protocols in the Internet Community. |
| 27 |
In particular it describes a set of objects for managing World Wide |
| 28 |
Web (WWW) services. |
| 29 |
|
| 30 |
Table of Contents |
| 31 |
|
| 32 |
<a href="#section-1">1</a> Introduction ................................................. <a href="#page-1">1</a> |
| 33 |
<a href="#section-2">2</a> The SNMP Management Framework ................................ <a href="#page-2">2</a> |
| 34 |
<a href="#section-3">3</a> Terminology .................................................. <a href="#page-3">3</a> |
| 35 |
<a href="#section-4">4</a> Overview ..................................................... <a href="#page-4">4</a> |
| 36 |
<a href="#section-4.1">4.1</a> Purpose and Requirements ................................... <a href="#page-4">4</a> |
| 37 |
<a href="#section-4.2">4.2</a> Relationship to other Standards Efforts .................... <a href="#page-5">5</a> |
| 38 |
<a href="#section-4.3">4.3</a> WWW Services ............................................... <a href="#page-5">5</a> |
| 39 |
<a href="#section-4.4">4.4</a> Document Transfer Protocol ................................. <a href="#page-6">6</a> |
| 40 |
<a href="#section-5">5</a> Structure of the MIB ......................................... <a href="#page-7">7</a> |
| 41 |
<a href="#section-5.1">5.1</a> Service Information Group .................................. <a href="#page-7">7</a> |
| 42 |
<a href="#section-5.2">5.2</a> Protocol Statistics Group .................................. <a href="#page-7">7</a> |
| 43 |
<a href="#section-5.3">5.3</a> Document Statistics Group .................................. <a href="#page-8">8</a> |
| 44 |
<a href="#section-6">6</a> Definitions .................................................. <a href="#page-10">10</a> |
| 45 |
<a href="#section-7">7</a> Document Transfer Protocol Mappings .......................... <a href="#page-36">36</a> |
| 46 |
<a href="#section-7.1">7.1</a> The HyperText Transfer Protocol ............................ <a href="#page-36">36</a> |
| 47 |
<a href="#section-7.2">7.2</a> The File Transfer Protocol ................................. <a href="#page-37">37</a> |
| 48 |
<a href="#section-8">8</a> Security Considerations ...................................... <a href="#page-38">38</a> |
| 49 |
<a href="#section-9">9</a> Intellectual Property ........................................ <a href="#page-39">39</a> |
| 50 |
<a href="#section-10">10</a> Acknowledgments ............................................. <a href="#page-39">39</a> |
| 51 |
|
| 52 |
|
| 53 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 1]</span></pre> |
| 54 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 55 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 56 |
|
| 57 |
|
| 58 |
<a href="#section-11">11</a> Editors' Addresses .......................................... <a href="#page-39">39</a> |
| 59 |
<a href="#section-12">12</a> References .................................................. <a href="#page-40">40</a> |
| 60 |
<a href="#section-13">13</a> Full Copyright Statement .................................... <a href="#page-43">43</a> |
| 61 |
|
| 62 |
|
| 63 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 64 |
|
| 65 |
This memo defines a set of objects for managing World Wide Web (WWW) |
| 66 |
services. This MIB extends the application management framework |
| 67 |
defined by the System Application Management MIB (SYSAPPL-MIB) [<a href="#ref-23" title=""Definitions of System-Level Managed Objects for Applications"">23</a>] |
| 68 |
and the Application Management MIB (APPLICATION-MIB) [<a href="#ref-24" title=""Application Management MIB"">24</a>]. The MIB is |
| 69 |
also self-contained so that it can be implemented and used without |
| 70 |
having to implement or install the APPLICATION-MIB or the SYSAPPL- |
| 71 |
MIB. |
| 72 |
|
| 73 |
The protocol statistics defined in the WWW Service MIB are based on |
| 74 |
an abstract document transfer protocol (DTP). This memo also defines |
| 75 |
a mapping of the abstract DTP to HTTP and FTP. Additional mappings |
| 76 |
may be defined in the future in order to use this MIB with other |
| 77 |
document transfer protocols. It is anticipated that such future |
| 78 |
mappings will be defined in separate RFCs. |
| 79 |
|
| 80 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 81 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 82 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-17" title=""Key words for use in RFCs to Indicate Requirement Levels"">17</a>]. |
| 83 |
|
| 84 |
|
| 85 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMP Management Framework</span> |
| 86 |
|
| 87 |
The SNMP Management Framework presently consists of five major |
| 88 |
components: |
| 89 |
|
| 90 |
o An overall architecture, described in <a href="./rfc2571">RFC 2571</a> [<a href="#ref-1" title=""An Architecture for Describing SNMP Management Frameworks"">1</a>]. |
| 91 |
|
| 92 |
o Mechanisms for describing and naming objects and events for the |
| 93 |
purpose of management. The first version of this Structure of |
| 94 |
Management Information (SMI) is called SMIv1 and described in |
| 95 |
STD 16, <a href="./rfc1155">RFC 1155</a> [<a href="#ref-2" title=""Structure and Identification of Management Information for TCP/IP-based Internets"">2</a>], STD 16, <a href="./rfc1212">RFC 1212</a> [<a href="#ref-3" title=""Concise MIB Definitions"">3</a>] and <a href="./rfc1215">RFC 1215</a> [<a href="#ref-4" title=""A Convention for Defining Traps for use with the SNMP"">4</a>]. The |
| 96 |
second version, called SMIv2, is described in STD 58, <a href="./rfc2578">RFC 2578</a> |
| 97 |
[<a href="#ref-5" title=""Structure of Management Information Version 2 (SMIv2)"">5</a>], <a href="./rfc2579">RFC 2579</a> [<a href="#ref-6" title=""Textual Conventions for SMIv2"">6</a>] and <a href="./rfc2580">RFC 2580</a> [<a href="#ref-7" title=""Conformance Statements for SMIv2"">7</a>]. |
| 98 |
|
| 99 |
o Message protocols for transferring management information. The |
| 100 |
first version of the SNMP message protocol is called SNMPv1 and |
| 101 |
described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title=""Simple Network Management Protocol"">8</a>]. A second version of the SNMP |
| 102 |
message protocol, which is not an Internet standards track |
| 103 |
protocol, is called SNMPv2c and described in <a href="./rfc1901">RFC 1901</a> [<a href="#ref-9" title=""Introduction to Community-based SNMPv2"">9</a>] and |
| 104 |
<a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title=""Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)"">10</a>]. The third version of the message protocol is |
| 105 |
called SNMPv3 and described in <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title=""Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)"">10</a>], <a href="./rfc2572">RFC 2572</a> [<a href="#ref-11" title=""Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)"">11</a>] and |
| 106 |
<a href="./rfc2574">RFC 2574</a> [<a href="#ref-12" title=""User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)"">12</a>]. |
| 107 |
|
| 108 |
|
| 109 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 2]</span></pre> |
| 110 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 111 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 112 |
|
| 113 |
|
| 114 |
o Protocol operations for accessing management information. The |
| 115 |
first set of protocol operations and associated PDU formats is |
| 116 |
described in <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title=""Simple Network Management Protocol"">8</a>]. A second set of protocol operations |
| 117 |
and associated PDU formats is described in <a href="./rfc1905">RFC 1905</a> [<a href="#ref-13" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">13</a>]. |
| 118 |
|
| 119 |
o A set of fundamental applications described in <a href="./rfc2573">RFC 2573</a> [<a href="#ref-14" title=""SNMP Applications"">14</a>] and |
| 120 |
the view-based access control mechanism described in <a href="./rfc2575">RFC 2575</a> |
| 121 |
[<a href="#ref-15" title=""View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)"">15</a>]. |
| 122 |
|
| 123 |
Managed objects are accessed via a virtual information store, termed |
| 124 |
the Management Information Base or MIB. Objects in the MIB are |
| 125 |
defined using the mechanisms defined in the SMI. |
| 126 |
|
| 127 |
This memo specifies a MIB module that is compliant to the SMIv2. A |
| 128 |
MIB conforming to the SMIv1 can be produced through the appropriate |
| 129 |
translations. The resulting translated MIB must be semantically |
| 130 |
equivalent, except where objects or events are omitted because no |
| 131 |
translation is possible (use of Counter64). Some machine readable |
| 132 |
information in SMIv2 will be converted into textual descriptions in |
| 133 |
SMIv1 during the translation process. However, this loss of machine |
| 134 |
readable information is not considered to change the semantics of the |
| 135 |
MIB. |
| 136 |
|
| 137 |
|
| 138 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span> |
| 139 |
|
| 140 |
This section defines the terminology used throughout this document. |
| 141 |
|
| 142 |
o The 'World Wide Web' (WWW) is a world wide information system |
| 143 |
which is based on the concept of documents that are linked |
| 144 |
together by embedding references (links) to other local or |
| 145 |
remote documents. |
| 146 |
|
| 147 |
o A 'document' is a coherent piece of data which is accessible in |
| 148 |
the World Wide Web. No assumptions are made about the content or |
| 149 |
the type of a document. |
| 150 |
|
| 151 |
o A 'Uniform Resource Locator' (URL) is a formatted string |
| 152 |
representation for a document available via the Internet. URLs |
| 153 |
are used to express references between documents. For the syntax |
| 154 |
and semantics of the URL string representation refer to <a href="./rfc2396">RFC 2396</a> |
| 155 |
[<a href="#ref-18" title=""Uniform Resource Identifiers (URI): Generic Syntax"">18</a>] |
| 156 |
|
| 157 |
o A 'Document Transfer Protocol' (DTP) is a protocol used within |
| 158 |
the World Wide Web to invoke actions on documents. The DTP is an |
| 159 |
abstraction from real protocols, such as HTTP [<a href="#ref-19" title=""Hypertext Transfer Protocol -- HTTP/1.0"">19</a>,<a href="#ref-20" title=""Hypertext Transfer Protocol -- HTTP/1.1"">20</a>] or FTP |
| 160 |
[<a href="#ref-21" title=""File Transfer Protocol (FTP)"">21</a>]. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
|
| 165 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 3]</span></pre> |
| 166 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 167 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 168 |
|
| 169 |
|
| 170 |
o A 'request' is a DTP protocol operation which is targeted to a |
| 171 |
'document' and invokes an action on the target document. The |
| 172 |
request type specifies the action that should be performed. A |
| 173 |
request can have a document associated with it. |
| 174 |
|
| 175 |
o A 'response' is a DTP protocol operation which is returned as a |
| 176 |
result of a previous (and associated) request. The response |
| 177 |
status indicates if the requested action was successful or if |
| 178 |
errors occurred. A response can have a document associated with |
| 179 |
it. |
| 180 |
|
| 181 |
o A 'WWW service' is a set of actions that can be invoked on a |
| 182 |
document. Typical actions are the transfer of documents or the |
| 183 |
retrieval of administrative information about documents. WWW |
| 184 |
services are provided by means of a DTP. A WWW service can be |
| 185 |
identified by the DTP protocol used to invoke services and the |
| 186 |
transport endpoint used by that protocol. |
| 187 |
|
| 188 |
o A 'client' is a program which establishes connections for the |
| 189 |
purpose of sending requests and receiving responses. |
| 190 |
|
| 191 |
o A 'server' is a program that accepts connections in order to |
| 192 |
service requests by sending back responses. |
| 193 |
|
| 194 |
o A 'proxy' is an intermediary program which acts as both a server |
| 195 |
and a client for the purpose of making requests on behalf of |
| 196 |
other clients. Requests are serviced internally or by passing |
| 197 |
them on, with possible translation, to other servers. |
| 198 |
|
| 199 |
o A 'caching proxy' is a proxy with the capability of locally |
| 200 |
storing responses to associated requests. A caching proxy can |
| 201 |
respond to similar requests with a previously stored response. |
| 202 |
|
| 203 |
|
| 204 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span> |
| 205 |
|
| 206 |
The World Wide Web (WWW) is a global network of information. |
| 207 |
Information is stored in documents, which can have various formats, |
| 208 |
including hyper-text and multi-media documents. Access to these |
| 209 |
documents is provided by servers which are located all around the |
| 210 |
world and are linked to each other via hyper-links embedded in |
| 211 |
documents. |
| 212 |
|
| 213 |
The usability of the World Wide Web depends largely on the |
| 214 |
performance of the services realized by these servers. The services |
| 215 |
are typically monitored through log files. This becomes a difficult |
| 216 |
task when a single organization is responsible for a large number of |
| 217 |
services. It is therefore desirable to treat WWW services as objects |
| 218 |
that can be managed by using the Internet network management |
| 219 |
framework [<a href="#ref-22" title=""Applicability of Standards Track MIBs to Management of World Wide Web Servers"">22</a>]. |
| 220 |
|
| 221 |
|
| 222 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 4]</span></pre> |
| 223 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 224 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 225 |
|
| 226 |
|
| 227 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Purpose and Requirements</span> |
| 228 |
|
| 229 |
The goal of this MIB is to define a standardized set of objects which |
| 230 |
lead to integrated and improved performance and fault management in a |
| 231 |
heterogeneous environment of WWW services. This MIB focuses on the |
| 232 |
service-oriented view. It does not deal with the process oriented |
| 233 |
view, which is covered by the System Application MIB [<a href="#ref-23" title=""Definitions of System-Level Managed Objects for Applications"">23</a>] and the |
| 234 |
Application MIB [<a href="#ref-24" title=""Application Management MIB"">24</a>]. |
| 235 |
|
| 236 |
This document defines a set of managed objects to monitor WWW |
| 237 |
services for short-term operational purposes, such as problem |
| 238 |
detection and troubleshooting. No attempts are made here to cover |
| 239 |
accounting or hit metering issues. |
| 240 |
|
| 241 |
The scope of the MIB is further limited by the requirement that an |
| 242 |
implementation conforming to this MIB must be possible without |
| 243 |
putting a huge CPU or memory burden on the WWW server implementation. |
| 244 |
|
| 245 |
In addition, this MIB does not cover WWW service configuration. |
| 246 |
Server software has become an open market where competing vendors |
| 247 |
constantly invent new features in order to shape their products. It |
| 248 |
is therefore not possible to reach consensus on a common way to |
| 249 |
configure WWW services at this point in time. |
| 250 |
|
| 251 |
|
| 252 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Relationship to other Standards Efforts</span> |
| 253 |
|
| 254 |
The WWW Service MIB fits into the application management architecture |
| 255 |
defined in the System Application MIB [<a href="#ref-23" title=""Definitions of System-Level Managed Objects for Applications"">23</a>]. The System Application |
| 256 |
MIB and the Application MIB [<a href="#ref-24" title=""Application Management MIB"">24</a>] use a process-oriented view, where |
| 257 |
an application is viewed as a collection of processes. The WWW |
| 258 |
Service MIB described in this memo uses a service-oriented view, |
| 259 |
which looks at the services provided by a set of processes. |
| 260 |
|
| 261 |
The relationship between the process-oriented view and the service- |
| 262 |
oriented view is a many-to-many relationship, because one process can |
| 263 |
implement multiple services and multiple services can be implemented |
| 264 |
by a single set of processes. The Application Management MIB [<a href="#ref-24" title=""Application Management MIB"">24</a>] |
| 265 |
contains generic mapping tables, which map back and forth between |
| 266 |
both views. |
| 267 |
|
| 268 |
The WWW Service MIB interfaces to the Application MIB [<a href="#ref-24" title=""Application Management MIB"">24</a>] by using |
| 269 |
the service instance identifier (applSrvIndex) for wwwServiceIndex if |
| 270 |
an applicable instance of applSrvIndex is available. The WWW Service |
| 271 |
MIB is self-contained and can be implemented as a stand-alone module |
| 272 |
if the service-level tables in the Application MIB are not available. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
|
| 277 |
|
| 278 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 5]</span></pre> |
| 279 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 280 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 281 |
|
| 282 |
|
| 283 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. WWW Services</span> |
| 284 |
|
| 285 |
The MIB is organized around the concept of WWW services. WWW services |
| 286 |
are a set of actions that can be invoked on a document. A WWW service |
| 287 |
is provided or used by either a client, a server or a proxy. Clients |
| 288 |
send out requests for information to server or proxy server. Servers |
| 289 |
receive, process and respond to requests received from clients. |
| 290 |
Servers usually have access to local documents, which can be |
| 291 |
transferred to clients. |
| 292 |
|
| 293 |
A proxy is a special server, who acts as both a server and a client |
| 294 |
for the purpose of making requests on behalf of other clients. A |
| 295 |
proxy is able to translate between the client and the origin server. |
| 296 |
A proxy might also interact with other information retrieval system, |
| 297 |
like for example databases. |
| 298 |
|
| 299 |
The MIB defined in this memo distinguishes between outgoing and |
| 300 |
incoming requests and responses. This makes it possible to obtain |
| 301 |
statistics for clients, servers and proxies with a single set of |
| 302 |
objects. |
| 303 |
|
| 304 |
A special proxy server is the caching proxy, which maintains a cache |
| 305 |
of previously received documents in order to reduce the bandwidth |
| 306 |
used by World Wide Web clients. One interesting piece of management |
| 307 |
information is the percentage of requests that were served from the |
| 308 |
cache of the caching proxy (hits/miss-ratio). This ratio is not |
| 309 |
contained explicitly in this MIB. Instead, the ratio can be derived |
| 310 |
from the objects that count incoming and outgoing requests and |
| 311 |
responses. |
| 312 |
|
| 313 |
|
| 314 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Document Transfer Protocol</span> |
| 315 |
|
| 316 |
The MIB is based on the concept of an abstract document transfer |
| 317 |
protocol (DTP). The purpose of the abstract document transfer |
| 318 |
protocol is to make the MIB definitions independent from concrete |
| 319 |
protocols, like the Hypertext Transfer Protocol (HTTP) [<a href="#ref-19" title=""Hypertext Transfer Protocol -- HTTP/1.0"">19</a>,<a href="#ref-20" title=""Hypertext Transfer Protocol -- HTTP/1.1"">20</a>] or the |
| 320 |
File Transfer Protocol (FTP) [<a href="#ref-21" title=""File Transfer Protocol (FTP)"">21</a>]. |
| 321 |
|
| 322 |
The abstract document transfer protocol makes the following |
| 323 |
assumptions about a concrete transfer protocol: |
| 324 |
|
| 325 |
o The transfer protocol uses a request/response style of |
| 326 |
interactions. |
| 327 |
|
| 328 |
o Every request contains a request type, which defines the |
| 329 |
operations performed by the receiving server. The request type |
| 330 |
is represented by an OCTET STRING. It might be necessary to |
| 331 |
define a translation into an OCTET STRING value for protocols |
| 332 |
that use numbers to identify request types. |
| 333 |
|
| 334 |
|
| 335 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 6]</span></pre> |
| 336 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 337 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 338 |
|
| 339 |
|
| 340 |
o A response contains a status code, which indicates if the |
| 341 |
request was processed successfully or which error occurred. The |
| 342 |
status code is represented as an INTEGER value. It might be |
| 343 |
necessary to define a mapping for protocols that do not use an |
| 344 |
INTEGER status code. |
| 345 |
|
| 346 |
o A transfer protocol can send multiple responses for a single |
| 347 |
request. Multiple responses are counted separately in the |
| 348 |
protocol statistics group. |
| 349 |
|
| 350 |
A primary response has to be identified for the document |
| 351 |
statistics. The primary response is the response that indicates |
| 352 |
whether the request was successful. |
| 353 |
|
| 354 |
<a href="#section-7">Section 7</a> of this memo defines a mapping of the document transfer |
| 355 |
protocol to the HTTP protocol and the FTP protocol. Mappings to other |
| 356 |
protocols, like NNTP [<a href="#ref-25" title=""Network News Transfer Protocol: A Proposed Standard for the Stream-Based Transmission of News"">25</a>] or WebNFS [<a href="#ref-26" title=""WebNFS Client Specification"">26</a>,<a href="#ref-27" title=""WebNFS Server Specification"">27</a>] might be defined in the |
| 357 |
future. |
| 358 |
|
| 359 |
|
| 360 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Structure of the MIB</span> |
| 361 |
|
| 362 |
This section presents the structure of the MIB. The objects are |
| 363 |
arranged into the following groups: |
| 364 |
|
| 365 |
o service information |
| 366 |
|
| 367 |
o protocol statistics |
| 368 |
|
| 369 |
o document statistics |
| 370 |
|
| 371 |
|
| 372 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Service Information Group</span> |
| 373 |
|
| 374 |
The service information group consists of a single table describing |
| 375 |
all the WWW services managed by the SNMP agent. The service table |
| 376 |
contains administrative network management information for |
| 377 |
(potentially) multiple WWW services running on a single host. It also |
| 378 |
contains information for all services within virtual domains of a |
| 379 |
host. The columnar objects in the table can be divided into two main |
| 380 |
groups: |
| 381 |
|
| 382 |
o global administrative information of the service, such as |
| 383 |
service contact person, and |
| 384 |
|
| 385 |
o network information, such as the transfer protocol. |
| 386 |
|
| 387 |
|
| 388 |
|
| 389 |
|
| 390 |
|
| 391 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 7]</span></pre> |
| 392 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 393 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 394 |
|
| 395 |
|
| 396 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Protocol Statistics Group</span> |
| 397 |
|
| 398 |
The protocol statistics group provides network management information |
| 399 |
about the traffic received or transmitted by a WWW service. This |
| 400 |
group contains counters related to DTP protocol operations and |
| 401 |
consists of five tables: |
| 402 |
|
| 403 |
o The wwwSummaryTable contains a set of network traffic related |
| 404 |
counters. The table provides a summarization of the network |
| 405 |
traffic and protocol operations related to a WWW service. It is |
| 406 |
well recognized that certain variables are redundant with |
| 407 |
respect to the request and response tables, but they are added |
| 408 |
to provide an operator a quick overview and to reduce SNMP |
| 409 |
network traffic. |
| 410 |
|
| 411 |
o The wwwRequestInTable contains detailed information about |
| 412 |
incoming requests. Every particular request type is counted |
| 413 |
separately. |
| 414 |
|
| 415 |
o The wwwRequestOutTable contains detailed information about |
| 416 |
outgoing requests. Every particular request type is counted |
| 417 |
separately. |
| 418 |
|
| 419 |
o The wwwResponseInTable contains detailed information about |
| 420 |
incoming responses. Every particular response type is counted |
| 421 |
separately. |
| 422 |
|
| 423 |
o The wwwResponseOutTable contains detailed information about |
| 424 |
outgoing responses. Every particular response type is counted |
| 425 |
separately. |
| 426 |
|
| 427 |
|
| 428 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Document Statistics Group</span> |
| 429 |
|
| 430 |
The document group contains information about the documents which |
| 431 |
were accessed in the past. The group provides four types of |
| 432 |
statistics. |
| 433 |
|
| 434 |
1. Details about the last N attempts to invoke actions on |
| 435 |
documents. |
| 436 |
|
| 437 |
2. The Top N documents sorted by the number of actions invoked on |
| 438 |
them computed over a time interval. |
| 439 |
|
| 440 |
3. The Top N documents sorted by the number of content bytes |
| 441 |
transferred computed over a time interval. |
| 442 |
|
| 443 |
4. Summary statistics computed over a time interval. |
| 444 |
|
| 445 |
|
| 446 |
|
| 447 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 8]</span></pre> |
| 448 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 449 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 450 |
|
| 451 |
|
| 452 |
The Top N document statistics are collected in buckets in order to |
| 453 |
reduce agent resources and to allow a manager to detect changes in |
| 454 |
the service usage pattern. Buckets are filled over a configurable |
| 455 |
time interval. The agent computes the Top N statistics and starts a |
| 456 |
new bucket once the time interval for the bucket has passed. The time |
| 457 |
interval is configurable for each WWW service. |
| 458 |
|
| 459 |
The document statistics group associates a response type to the |
| 460 |
request which invoked an action. In case a DTP sends multiple |
| 461 |
responses, the primary response must be used to derive the response |
| 462 |
type of the request/response interaction. |
| 463 |
|
| 464 |
The group consist of the following tables: |
| 465 |
|
| 466 |
o The wwwDocCtrlTable provides the manager a means to limit the |
| 467 |
document statistic tables in size and to control the expiration |
| 468 |
and creation of buckets. |
| 469 |
|
| 470 |
o The wwwDocLastNTable provides the manager information about the |
| 471 |
last N documents which where accessed. The table lists the |
| 472 |
documents for which access was attempted along with the request |
| 473 |
and response type of the DTP and a status message. The request |
| 474 |
and response types provide a manager information of how attempts |
| 475 |
to invoke actions were handled by the DTP. The status message |
| 476 |
object provides human readable text to further describe the |
| 477 |
response type. |
| 478 |
|
| 479 |
The number of documents in the wwwDocLastNTable is controlled by |
| 480 |
the wwwDocCtrlLastNSize object in the wwwDocCtrlTable. The |
| 481 |
wwwDocCtrlLastNLock object of the wwwDocCtrlTable allows a |
| 482 |
management application to lock the wwwDocLastNTable in order to |
| 483 |
retrieve a consistent snapshot of the fast changing |
| 484 |
wwwDocLastNTable. |
| 485 |
|
| 486 |
o The wwwDocBucketTable lists the buckets of statistical |
| 487 |
information that have been collected. An entry in the |
| 488 |
wwwDocBucketTable contains the creation timestamp of the bucket |
| 489 |
as well as summary information (number of accesses, number of |
| 490 |
documents accessed and number of bytes transferred). |
| 491 |
|
| 492 |
The time interval is controlled by the |
| 493 |
wwwDocCtrlBucketTimeInterval object of the wwwDocCtrlTable. The |
| 494 |
maximum number of buckets maintained by the SNMP agent for a |
| 495 |
particular WWW service is controlled by the wwwDocCtrlBuckets |
| 496 |
object of the wwwDocCtrlTable. |
| 497 |
|
| 498 |
o The wwwDocAccessTopNTable provides the manager an overview of |
| 499 |
the top N documents which were accessed while statistics were |
| 500 |
collected for a particular bucket. The wwwDocAccessTopNTable is |
| 501 |
|
| 502 |
|
| 503 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 9]</span></pre> |
| 504 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 505 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 506 |
|
| 507 |
|
| 508 |
sorted by the number of read attempts per document. The maximum |
| 509 |
number of entries in the wwwDocAccessTopNTable is controlled by |
| 510 |
the wwwDocCtrlTopNSize object. |
| 511 |
|
| 512 |
o The wwwDocBytesTopNTable provides the manager an overview of the |
| 513 |
top N documents which caused most of the network traffic while |
| 514 |
statistics were collected for a particular bucket. The |
| 515 |
wwwDocBytesTopNTable is sorted by the number of bytes |
| 516 |
transferred. The maximum number of entries in the |
| 517 |
wwwDocBytesTopNTable is controlled by the wwwDocCtrlTopNSize |
| 518 |
object. |
| 519 |
|
| 520 |
|
| 521 |
The Top N statistics and the parameters of the underlying bucket are |
| 522 |
not visible in the MIB as long as the bucket is filling up. Instead, |
| 523 |
the following steps must be taken when the time interval for a |
| 524 |
buckets has passed: |
| 525 |
|
| 526 |
|
| 527 |
1. A new entry in the wwwDocBucketTable is created to summarize the |
| 528 |
document statistics for that time interval. |
| 529 |
|
| 530 |
2. The corresponding entries in the wwwDocAccessTopNTable and the |
| 531 |
wwwDocBytesTopNTable are computed and made available. |
| 532 |
|
| 533 |
3. If the resulting number of entries in the wwwDocBucketTable for |
| 534 |
the WWW service now exceeds wwwDocCtrlBuckets, then the oldest |
| 535 |
bucket for this WWW service and all corresponding entries in the |
| 536 |
wwwDocBucketTable, wwwDocAccessTopNTable, and |
| 537 |
wwwDocBytesTopNTable are deleted. |
| 538 |
|
| 539 |
|
| 540 |
Note that a bucket usually contains much more data than displayed in |
| 541 |
the Top N tables. The number of entries in the Top N table for a |
| 542 |
bucket is controlled by wwwDocCtrlTopNSize, while the number of |
| 543 |
entries in a bucket depends on the number of actions invoked on |
| 544 |
documents within the time interval over which a bucket is filled up. |
| 545 |
It is therefore suggested to discard the data associated with a |
| 546 |
bucket once the entries for the wwwDocBucketTable, |
| 547 |
wwwDocAccessTopNTable and wwwDocBytesTopNTable have been calculated. |
| 548 |
|
| 549 |
|
| 550 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Definitions</span> |
| 551 |
|
| 552 |
WWW-MIB DEFINITIONS ::= BEGIN |
| 553 |
|
| 554 |
IMPORTS |
| 555 |
MODULE-IDENTITY, OBJECT-TYPE, mib-2, |
| 556 |
Counter32, Counter64, Integer32, Unsigned32, TimeTicks |
| 557 |
FROM SNMPv2-SMI |
| 558 |
|
| 559 |
|
| 560 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 10]</span></pre> |
| 561 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 562 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 563 |
|
| 564 |
|
| 565 |
TEXTUAL-CONVENTION, DisplayString, DateAndTime, TimeInterval |
| 566 |
FROM SNMPv2-TC |
| 567 |
|
| 568 |
MODULE-COMPLIANCE, OBJECT-GROUP |
| 569 |
FROM SNMPv2-CONF |
| 570 |
|
| 571 |
Utf8String |
| 572 |
FROM SYSAPPL-MIB; |
| 573 |
|
| 574 |
wwwMIB MODULE-IDENTITY |
| 575 |
LAST-UPDATED "9902251400Z" |
| 576 |
ORGANIZATION "IETF Application MIB Working Group" |
| 577 |
CONTACT-INFO |
| 578 |
" Harrie Hazewinkel |
| 579 |
|
| 580 |
Postal: Joint Research Centre of the E.C. |
| 581 |
via Fermi - Ispra 21020 (VA) |
| 582 |
Italy |
| 583 |
|
| 584 |
Tel: +39+(0)332 786322 |
| 585 |
Fax: +39+(0)332 785641 |
| 586 |
E-mail: [email protected] |
| 587 |
|
| 588 |
Carl W. Kalbfleisch |
| 589 |
|
| 590 |
Postal: Verio, Inc. |
| 591 |
1950 Stemmons Freeway |
| 592 |
Suite 2006 |
| 593 |
Dallas, TX 75207 |
| 594 |
US |
| 595 |
|
| 596 |
Tel: +1 214 290-8653 |
| 597 |
Fax: +1 214 744-0742 |
| 598 |
E-mail: [email protected] |
| 599 |
|
| 600 |
Juergen Schoenwaelder |
| 601 |
|
| 602 |
Postal: TU Braunschweig |
| 603 |
Bueltenweg 74/75 |
| 604 |
38106 Braunschweig |
| 605 |
Germany |
| 606 |
|
| 607 |
Tel: +49 531 391-3683 |
| 608 |
Fax: +49 531 489-5936 |
| 609 |
E-mail: [email protected]" |
| 610 |
DESCRIPTION |
| 611 |
"This WWW service MIB module is applicable to services |
| 612 |
realized by a family of 'Document Transfer Protocols' |
| 613 |
(DTP). Examples of DTPs are HTTP and FTP." |
| 614 |
|
| 615 |
|
| 616 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 11]</span></pre> |
| 617 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 618 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 619 |
|
| 620 |
|
| 621 |
-- revision history |
| 622 |
|
| 623 |
REVISION "9902251400Z" |
| 624 |
DESCRIPTION "Initial version, published as <a href="./rfc2594">RFC2594</a>." |
| 625 |
|
| 626 |
::= { mib-2 65 } |
| 627 |
|
| 628 |
-- |
| 629 |
-- Object Identifier Assignments |
| 630 |
-- |
| 631 |
|
| 632 |
wwwMIBObjects OBJECT IDENTIFIER ::= { wwwMIB 1 } |
| 633 |
wwwMIBConformance OBJECT IDENTIFIER ::= { wwwMIB 2 } |
| 634 |
|
| 635 |
-- |
| 636 |
-- Textual Conventions |
| 637 |
-- |
| 638 |
|
| 639 |
WwwRequestType ::= TEXTUAL-CONVENTION |
| 640 |
STATUS current |
| 641 |
DESCRIPTION |
| 642 |
"The WwwRequestType defines the textual identification of |
| 643 |
request types used by a document transfer protocol. For |
| 644 |
the proper values for a given DTP, refer to the protocol |
| 645 |
mappings for that DTP." |
| 646 |
SYNTAX OCTET STRING (SIZE (1..40)) |
| 647 |
|
| 648 |
WwwResponseType ::= TEXTUAL-CONVENTION |
| 649 |
STATUS current |
| 650 |
DESCRIPTION |
| 651 |
"The WwwResponseType defines the different response values |
| 652 |
used by document transfer protocols. For the proper values |
| 653 |
for a given DTP, refer to the protocol mappings for that |
| 654 |
DTP." |
| 655 |
SYNTAX Integer32 (0..2147483647) |
| 656 |
|
| 657 |
WwwOperStatus ::= TEXTUAL-CONVENTION |
| 658 |
STATUS current |
| 659 |
DESCRIPTION |
| 660 |
"The operational status of a WWW service. 'down' indicates |
| 661 |
that the service is not available. 'running' indicates |
| 662 |
that the service is operational and available. 'halted' |
| 663 |
indicates that the service is operational but not |
| 664 |
available. 'congested' indicates that the service is |
| 665 |
operational but no additional inbound associations can be |
| 666 |
accommodated. 'restarting' indicates that the service is |
| 667 |
currently unavailable but is in the process of restarting |
| 668 |
and will be available soon." |
| 669 |
SYNTAX INTEGER { |
| 670 |
down(1), |
| 671 |
|
| 672 |
|
| 673 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 12]</span></pre> |
| 674 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 675 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 676 |
|
| 677 |
|
| 678 |
running(2), |
| 679 |
halted(3), |
| 680 |
congested(4), |
| 681 |
restarting(5) |
| 682 |
} |
| 683 |
|
| 684 |
WwwDocName ::= TEXTUAL-CONVENTION |
| 685 |
DISPLAY-HINT "255a" |
| 686 |
STATUS current |
| 687 |
DESCRIPTION |
| 688 |
"The server relative name of a document. If the URL were |
| 689 |
<a href="http://www.x.org/standards/search/search.cgi?string=test">http://www.x.org/standards/search/search.cgi?string=test</a> |
| 690 |
then the value of this textual convention would resolve |
| 691 |
to '/standards/search/search.cgi'. This textual convention |
| 692 |
uses the character set for URIs as defined in <a href="./rfc2396#section-2">RFC 2396 |
| 693 |
section 2</a>." |
| 694 |
SYNTAX OCTET STRING (SIZE (0..255)) |
| 695 |
|
| 696 |
|
| 697 |
-- The WWW Service Information Group |
| 698 |
-- |
| 699 |
-- The WWW service information group contains information about |
| 700 |
-- the WWW services known by the SNMP agent. |
| 701 |
|
| 702 |
wwwService OBJECT IDENTIFIER ::= { wwwMIBObjects 1 } |
| 703 |
|
| 704 |
wwwServiceTable OBJECT-TYPE |
| 705 |
SYNTAX SEQUENCE OF WwwServiceEntry |
| 706 |
MAX-ACCESS not-accessible |
| 707 |
STATUS current |
| 708 |
DESCRIPTION |
| 709 |
"The table of the WWW services known by the SNMP agent." |
| 710 |
::= { wwwService 1 } |
| 711 |
|
| 712 |
wwwServiceEntry OBJECT-TYPE |
| 713 |
SYNTAX WwwServiceEntry |
| 714 |
MAX-ACCESS not-accessible |
| 715 |
STATUS current |
| 716 |
DESCRIPTION |
| 717 |
"Details about a particular WWW service." |
| 718 |
INDEX { wwwServiceIndex } |
| 719 |
::= { wwwServiceTable 1 } |
| 720 |
|
| 721 |
WwwServiceEntry ::= SEQUENCE { |
| 722 |
wwwServiceIndex Unsigned32, |
| 723 |
wwwServiceDescription Utf8String, |
| 724 |
wwwServiceContact Utf8String, |
| 725 |
wwwServiceProtocol OBJECT IDENTIFIER, |
| 726 |
wwwServiceName DisplayString, |
| 727 |
wwwServiceType INTEGER, |
| 728 |
|
| 729 |
|
| 730 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 13]</span></pre> |
| 731 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 732 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 733 |
|
| 734 |
|
| 735 |
wwwServiceStartTime DateAndTime, |
| 736 |
wwwServiceOperStatus WwwOperStatus, |
| 737 |
wwwServiceLastChange DateAndTime |
| 738 |
} |
| 739 |
|
| 740 |
wwwServiceIndex OBJECT-TYPE |
| 741 |
SYNTAX Unsigned32 (1..4294967295) |
| 742 |
MAX-ACCESS not-accessible |
| 743 |
STATUS current |
| 744 |
DESCRIPTION |
| 745 |
"An integer used to uniquely identify a WWW service. The |
| 746 |
value must be the same as the corresponding value of the |
| 747 |
applSrvIndex defined in the Application Management MIB |
| 748 |
(APPLICATION-MIB) if the applSrvIndex object is available. |
| 749 |
It might be necessary to manually configure sub-agents in |
| 750 |
order to meet this requirement." |
| 751 |
::= { wwwServiceEntry 1 } |
| 752 |
|
| 753 |
wwwServiceDescription OBJECT-TYPE |
| 754 |
SYNTAX Utf8String |
| 755 |
MAX-ACCESS read-only |
| 756 |
STATUS current |
| 757 |
DESCRIPTION |
| 758 |
"Textual description of the WWW service. This shall include |
| 759 |
at least the vendor and version number of the application |
| 760 |
realizing the WWW service. In a minimal case, this might |
| 761 |
be the Product Token (see <a href="./rfc2068">RFC 2068</a>) for the application." |
| 762 |
::= { wwwServiceEntry 2 } |
| 763 |
|
| 764 |
wwwServiceContact OBJECT-TYPE |
| 765 |
SYNTAX Utf8String |
| 766 |
MAX-ACCESS read-only |
| 767 |
STATUS current |
| 768 |
DESCRIPTION |
| 769 |
"The textual identification of the contact person for this |
| 770 |
service, together with information on how to contact this |
| 771 |
person. For instance, this might be a string containing an |
| 772 |
email address, e.g. '<[email protected]>'." |
| 773 |
::= { wwwServiceEntry 3 } |
| 774 |
|
| 775 |
wwwServiceProtocol OBJECT-TYPE |
| 776 |
SYNTAX OBJECT IDENTIFIER |
| 777 |
MAX-ACCESS read-only |
| 778 |
STATUS current |
| 779 |
DESCRIPTION |
| 780 |
"An identification of the primary protocol in use by this |
| 781 |
service. For Internet applications, the IANA maintains |
| 782 |
a registry of the OIDs which correspond to well-known |
| 783 |
application protocols. If the application protocol is not |
| 784 |
listed in the registry, an OID value of the form |
| 785 |
|
| 786 |
|
| 787 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 14]</span></pre> |
| 788 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 789 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 790 |
|
| 791 |
|
| 792 |
{applTCPProtoID port} or {applUDPProtoID port} are used for |
| 793 |
TCP-based and UDP-based protocols, respectively. In either |
| 794 |
case 'port' corresponds to the primary port number being |
| 795 |
used by the protocol." |
| 796 |
REFERENCE |
| 797 |
"The OID values applTCPProtoID and applUDPProtoID are |
| 798 |
defined in the NETWORK-SERVICES-MIB (<a href="./rfc2248">RFC 2248</a>)." |
| 799 |
::= { wwwServiceEntry 4 } |
| 800 |
|
| 801 |
wwwServiceName OBJECT-TYPE |
| 802 |
SYNTAX DisplayString |
| 803 |
MAX-ACCESS read-only |
| 804 |
STATUS current |
| 805 |
DESCRIPTION |
| 806 |
"The fully qualified domain name by which this service is |
| 807 |
known. This object must contain the virtual host name if |
| 808 |
the service is realized for a virtual host." |
| 809 |
::= { wwwServiceEntry 5 } |
| 810 |
|
| 811 |
wwwServiceType OBJECT-TYPE |
| 812 |
SYNTAX INTEGER { |
| 813 |
wwwOther(1), |
| 814 |
wwwServer(2), |
| 815 |
wwwClient(3), |
| 816 |
wwwProxy(4), |
| 817 |
wwwCachingProxy(5) |
| 818 |
} |
| 819 |
MAX-ACCESS read-only |
| 820 |
STATUS current |
| 821 |
DESCRIPTION |
| 822 |
"The application type using or realizing this WWW service." |
| 823 |
::= { wwwServiceEntry 6 } |
| 824 |
|
| 825 |
wwwServiceStartTime OBJECT-TYPE |
| 826 |
SYNTAX DateAndTime |
| 827 |
MAX-ACCESS read-only |
| 828 |
STATUS current |
| 829 |
DESCRIPTION |
| 830 |
"The date and time when this WWW service was last started. |
| 831 |
The value SHALL be '0000000000000000'H if the last start |
| 832 |
time of this WWW service is not known." |
| 833 |
::= { wwwServiceEntry 7 } |
| 834 |
|
| 835 |
wwwServiceOperStatus OBJECT-TYPE |
| 836 |
SYNTAX WwwOperStatus |
| 837 |
MAX-ACCESS read-only |
| 838 |
STATUS current |
| 839 |
DESCRIPTION |
| 840 |
"Indicates the operational status of the WWW service." |
| 841 |
::= { wwwServiceEntry 8 } |
| 842 |
|
| 843 |
|
| 844 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 15]</span></pre> |
| 845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 846 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 847 |
|
| 848 |
|
| 849 |
wwwServiceLastChange OBJECT-TYPE |
| 850 |
SYNTAX DateAndTime |
| 851 |
MAX-ACCESS read-only |
| 852 |
STATUS current |
| 853 |
DESCRIPTION |
| 854 |
"The date and time when this WWW service entered its current |
| 855 |
operational state. The value SHALL be '0000000000000000'H if |
| 856 |
the time of the last state change is not known." |
| 857 |
::= { wwwServiceEntry 9 } |
| 858 |
|
| 859 |
|
| 860 |
-- The WWW Protocol Statistics Group |
| 861 |
-- |
| 862 |
-- The WWW protocol statistics group contains statistics about |
| 863 |
-- the DTP requests and responses sent or received. |
| 864 |
|
| 865 |
wwwProtocolStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 2 } |
| 866 |
|
| 867 |
wwwSummaryTable OBJECT-TYPE |
| 868 |
SYNTAX SEQUENCE OF WwwSummaryEntry |
| 869 |
MAX-ACCESS not-accessible |
| 870 |
STATUS current |
| 871 |
DESCRIPTION |
| 872 |
"The table providing overview statistics for the |
| 873 |
WWW services on this system." |
| 874 |
::= { wwwProtocolStatistics 1 } |
| 875 |
|
| 876 |
wwwSummaryEntry OBJECT-TYPE |
| 877 |
SYNTAX WwwSummaryEntry |
| 878 |
MAX-ACCESS not-accessible |
| 879 |
STATUS current |
| 880 |
DESCRIPTION |
| 881 |
"Overview statistics for an individual service." |
| 882 |
INDEX { wwwServiceIndex } |
| 883 |
::= { wwwSummaryTable 1 } |
| 884 |
|
| 885 |
WwwSummaryEntry ::= SEQUENCE { |
| 886 |
wwwSummaryInRequests Counter32, |
| 887 |
wwwSummaryOutRequests Counter32, |
| 888 |
wwwSummaryInResponses Counter32, |
| 889 |
wwwSummaryOutResponses Counter32, |
| 890 |
wwwSummaryInBytes Counter64, |
| 891 |
wwwSummaryInLowBytes Counter32, |
| 892 |
wwwSummaryOutBytes Counter64, |
| 893 |
wwwSummaryOutLowBytes Counter32 |
| 894 |
} |
| 895 |
|
| 896 |
wwwSummaryInRequests OBJECT-TYPE |
| 897 |
SYNTAX Counter32 |
| 898 |
MAX-ACCESS read-only |
| 899 |
|
| 900 |
|
| 901 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 16]</span></pre> |
| 902 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 903 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 904 |
|
| 905 |
|
| 906 |
STATUS current |
| 907 |
DESCRIPTION |
| 908 |
"The number of requests successfully received." |
| 909 |
::= { wwwSummaryEntry 1 } |
| 910 |
|
| 911 |
wwwSummaryOutRequests OBJECT-TYPE |
| 912 |
SYNTAX Counter32 |
| 913 |
MAX-ACCESS read-only |
| 914 |
STATUS current |
| 915 |
DESCRIPTION |
| 916 |
"The number of requests generated." |
| 917 |
::= { wwwSummaryEntry 2 } |
| 918 |
|
| 919 |
wwwSummaryInResponses OBJECT-TYPE |
| 920 |
SYNTAX Counter32 |
| 921 |
MAX-ACCESS read-only |
| 922 |
STATUS current |
| 923 |
DESCRIPTION |
| 924 |
"The number of responses successfully received." |
| 925 |
::= { wwwSummaryEntry 3 } |
| 926 |
|
| 927 |
wwwSummaryOutResponses OBJECT-TYPE |
| 928 |
SYNTAX Counter32 |
| 929 |
MAX-ACCESS read-only |
| 930 |
STATUS current |
| 931 |
DESCRIPTION |
| 932 |
"The number of responses generated." |
| 933 |
::= { wwwSummaryEntry 4 } |
| 934 |
|
| 935 |
wwwSummaryInBytes OBJECT-TYPE |
| 936 |
SYNTAX Counter64 |
| 937 |
MAX-ACCESS read-only |
| 938 |
STATUS current |
| 939 |
DESCRIPTION |
| 940 |
"The number of content bytes received." |
| 941 |
::= { wwwSummaryEntry 5 } |
| 942 |
|
| 943 |
wwwSummaryInLowBytes OBJECT-TYPE |
| 944 |
SYNTAX Counter32 |
| 945 |
MAX-ACCESS read-only |
| 946 |
STATUS current |
| 947 |
DESCRIPTION |
| 948 |
"The lowest thirty-two bits of wwwSummaryInBytes." |
| 949 |
::= { wwwSummaryEntry 6 } |
| 950 |
|
| 951 |
wwwSummaryOutBytes OBJECT-TYPE |
| 952 |
SYNTAX Counter64 |
| 953 |
MAX-ACCESS read-only |
| 954 |
STATUS current |
| 955 |
DESCRIPTION |
| 956 |
|
| 957 |
|
| 958 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 17]</span></pre> |
| 959 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 960 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 961 |
|
| 962 |
|
| 963 |
"The number of content bytes transmitted." |
| 964 |
::= { wwwSummaryEntry 7 } |
| 965 |
|
| 966 |
wwwSummaryOutLowBytes OBJECT-TYPE |
| 967 |
SYNTAX Counter32 |
| 968 |
MAX-ACCESS read-only |
| 969 |
STATUS current |
| 970 |
DESCRIPTION |
| 971 |
"The lowest thirty-two bits of wwwSummaryOutBytes." |
| 972 |
::= { wwwSummaryEntry 8 } |
| 973 |
|
| 974 |
-- The WWW request tables contain detailed information about |
| 975 |
-- requests send or received by WWW services. |
| 976 |
|
| 977 |
wwwRequestInTable OBJECT-TYPE |
| 978 |
SYNTAX SEQUENCE OF WwwRequestInEntry |
| 979 |
MAX-ACCESS not-accessible |
| 980 |
STATUS current |
| 981 |
DESCRIPTION |
| 982 |
"The table providing detailed statistics for requests |
| 983 |
received by WWW services on this system." |
| 984 |
::= { wwwProtocolStatistics 2 } |
| 985 |
|
| 986 |
wwwRequestInEntry OBJECT-TYPE |
| 987 |
SYNTAX WwwRequestInEntry |
| 988 |
MAX-ACCESS not-accessible |
| 989 |
STATUS current |
| 990 |
DESCRIPTION |
| 991 |
"Request statistics for an individual service." |
| 992 |
INDEX { wwwServiceIndex, wwwRequestInIndex } |
| 993 |
::= { wwwRequestInTable 1 } |
| 994 |
|
| 995 |
WwwRequestInEntry ::= SEQUENCE { |
| 996 |
wwwRequestInIndex WwwRequestType, |
| 997 |
wwwRequestInRequests Counter32, |
| 998 |
wwwRequestInBytes Counter32, |
| 999 |
wwwRequestInLastTime DateAndTime |
| 1000 |
} |
| 1001 |
|
| 1002 |
wwwRequestInIndex OBJECT-TYPE |
| 1003 |
SYNTAX WwwRequestType |
| 1004 |
MAX-ACCESS not-accessible |
| 1005 |
STATUS current |
| 1006 |
DESCRIPTION |
| 1007 |
"The particular request type the statistics apply to." |
| 1008 |
::= { wwwRequestInEntry 1 } |
| 1009 |
|
| 1010 |
wwwRequestInRequests OBJECT-TYPE |
| 1011 |
SYNTAX Counter32 |
| 1012 |
MAX-ACCESS read-only |
| 1013 |
|
| 1014 |
|
| 1015 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 18]</span></pre> |
| 1016 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1017 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1018 |
|
| 1019 |
|
| 1020 |
STATUS current |
| 1021 |
DESCRIPTION |
| 1022 |
"The number of requests of this type received by this |
| 1023 |
WWW service." |
| 1024 |
::= { wwwRequestInEntry 2 } |
| 1025 |
|
| 1026 |
wwwRequestInBytes OBJECT-TYPE |
| 1027 |
SYNTAX Counter32 |
| 1028 |
MAX-ACCESS read-only |
| 1029 |
STATUS current |
| 1030 |
DESCRIPTION |
| 1031 |
"The number of content bytes per request type received |
| 1032 |
by this WWW service." |
| 1033 |
::= { wwwRequestInEntry 3 } |
| 1034 |
|
| 1035 |
wwwRequestInLastTime OBJECT-TYPE |
| 1036 |
SYNTAX DateAndTime |
| 1037 |
MAX-ACCESS read-only |
| 1038 |
STATUS current |
| 1039 |
DESCRIPTION |
| 1040 |
"The date and time when the last byte of the last complete |
| 1041 |
request of this type was received by this WWW service. The |
| 1042 |
value SHALL be '0000000000000000'H if no request of this |
| 1043 |
type has been received yet." |
| 1044 |
::= { wwwRequestInEntry 4 } |
| 1045 |
|
| 1046 |
wwwRequestOutTable OBJECT-TYPE |
| 1047 |
SYNTAX SEQUENCE OF WwwRequestOutEntry |
| 1048 |
MAX-ACCESS not-accessible |
| 1049 |
STATUS current |
| 1050 |
DESCRIPTION |
| 1051 |
"The table providing detailed statistics for requests |
| 1052 |
generated by the services on this system." |
| 1053 |
::= { wwwProtocolStatistics 3 } |
| 1054 |
|
| 1055 |
wwwRequestOutEntry OBJECT-TYPE |
| 1056 |
SYNTAX WwwRequestOutEntry |
| 1057 |
MAX-ACCESS not-accessible |
| 1058 |
STATUS current |
| 1059 |
DESCRIPTION |
| 1060 |
"Request statistics for an individual service." |
| 1061 |
INDEX { wwwServiceIndex, wwwRequestOutIndex } |
| 1062 |
::= { wwwRequestOutTable 1 } |
| 1063 |
|
| 1064 |
WwwRequestOutEntry ::= SEQUENCE { |
| 1065 |
wwwRequestOutIndex WwwRequestType, |
| 1066 |
wwwRequestOutRequests Counter32, |
| 1067 |
wwwRequestOutBytes Counter32, |
| 1068 |
wwwRequestOutLastTime DateAndTime |
| 1069 |
} |
| 1070 |
|
| 1071 |
|
| 1072 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 19]</span></pre> |
| 1073 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1074 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1075 |
|
| 1076 |
|
| 1077 |
wwwRequestOutIndex OBJECT-TYPE |
| 1078 |
SYNTAX WwwRequestType |
| 1079 |
MAX-ACCESS not-accessible |
| 1080 |
STATUS current |
| 1081 |
DESCRIPTION |
| 1082 |
"The particular request type the statistics apply to." |
| 1083 |
::= { wwwRequestOutEntry 1 } |
| 1084 |
|
| 1085 |
wwwRequestOutRequests OBJECT-TYPE |
| 1086 |
SYNTAX Counter32 |
| 1087 |
MAX-ACCESS read-only |
| 1088 |
STATUS current |
| 1089 |
DESCRIPTION |
| 1090 |
"The number of requests of this type generated by this |
| 1091 |
WWW service." |
| 1092 |
::= { wwwRequestOutEntry 2 } |
| 1093 |
|
| 1094 |
wwwRequestOutBytes OBJECT-TYPE |
| 1095 |
SYNTAX Counter32 |
| 1096 |
MAX-ACCESS read-only |
| 1097 |
STATUS current |
| 1098 |
DESCRIPTION |
| 1099 |
"The number of content bytes per requests type generated |
| 1100 |
by this WWW service." |
| 1101 |
::= { wwwRequestOutEntry 3 } |
| 1102 |
|
| 1103 |
wwwRequestOutLastTime OBJECT-TYPE |
| 1104 |
SYNTAX DateAndTime |
| 1105 |
MAX-ACCESS read-only |
| 1106 |
STATUS current |
| 1107 |
DESCRIPTION |
| 1108 |
"The date and time when the first byte of the last request |
| 1109 |
of this type was send by this WWW service. The value SHALL |
| 1110 |
be '0000000000000000'H if no request of this type has been |
| 1111 |
send yet." |
| 1112 |
::= { wwwRequestOutEntry 4 } |
| 1113 |
|
| 1114 |
-- The WWW response tables contain detailed information about |
| 1115 |
-- responses sent or received by WWW services. |
| 1116 |
|
| 1117 |
wwwResponseInTable OBJECT-TYPE |
| 1118 |
SYNTAX SEQUENCE OF WwwResponseInEntry |
| 1119 |
MAX-ACCESS not-accessible |
| 1120 |
STATUS current |
| 1121 |
DESCRIPTION |
| 1122 |
"The table providing detailed statistics for responses |
| 1123 |
received by WWW services on this system." |
| 1124 |
::= { wwwProtocolStatistics 4 } |
| 1125 |
|
| 1126 |
wwwResponseInEntry OBJECT-TYPE |
| 1127 |
|
| 1128 |
|
| 1129 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 20]</span></pre> |
| 1130 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1131 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1132 |
|
| 1133 |
|
| 1134 |
SYNTAX WwwResponseInEntry |
| 1135 |
MAX-ACCESS not-accessible |
| 1136 |
STATUS current |
| 1137 |
DESCRIPTION |
| 1138 |
"Response statistics for an individual service." |
| 1139 |
INDEX { wwwServiceIndex, wwwResponseInIndex } |
| 1140 |
::= { wwwResponseInTable 1 } |
| 1141 |
|
| 1142 |
WwwResponseInEntry ::= SEQUENCE { |
| 1143 |
wwwResponseInIndex WwwResponseType, |
| 1144 |
wwwResponseInResponses Counter32, |
| 1145 |
wwwResponseInBytes Counter32, |
| 1146 |
wwwResponseInLastTime DateAndTime |
| 1147 |
} |
| 1148 |
|
| 1149 |
wwwResponseInIndex OBJECT-TYPE |
| 1150 |
SYNTAX WwwResponseType |
| 1151 |
MAX-ACCESS not-accessible |
| 1152 |
STATUS current |
| 1153 |
DESCRIPTION |
| 1154 |
"The particular response type the statistics apply to." |
| 1155 |
::= { wwwResponseInEntry 1 } |
| 1156 |
|
| 1157 |
wwwResponseInResponses OBJECT-TYPE |
| 1158 |
SYNTAX Counter32 |
| 1159 |
MAX-ACCESS read-only |
| 1160 |
STATUS current |
| 1161 |
DESCRIPTION |
| 1162 |
"The number of responses of this type received by this |
| 1163 |
WWW service." |
| 1164 |
::= { wwwResponseInEntry 2 } |
| 1165 |
|
| 1166 |
wwwResponseInBytes OBJECT-TYPE |
| 1167 |
SYNTAX Counter32 |
| 1168 |
MAX-ACCESS read-only |
| 1169 |
STATUS current |
| 1170 |
DESCRIPTION |
| 1171 |
"The number of content bytes per response type received |
| 1172 |
by this WWW service." |
| 1173 |
::= { wwwResponseInEntry 3 } |
| 1174 |
|
| 1175 |
wwwResponseInLastTime OBJECT-TYPE |
| 1176 |
SYNTAX DateAndTime |
| 1177 |
MAX-ACCESS read-only |
| 1178 |
STATUS current |
| 1179 |
DESCRIPTION |
| 1180 |
"The date and time when the last byte of the last complete |
| 1181 |
response of this type was received by this WWW service. The |
| 1182 |
value SHALL be '0000000000000000'H if no response of this |
| 1183 |
type has been received yet." |
| 1184 |
|
| 1185 |
|
| 1186 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 21]</span></pre> |
| 1187 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1188 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1189 |
|
| 1190 |
|
| 1191 |
::= { wwwResponseInEntry 4 } |
| 1192 |
|
| 1193 |
wwwResponseOutTable OBJECT-TYPE |
| 1194 |
SYNTAX SEQUENCE OF WwwResponseOutEntry |
| 1195 |
MAX-ACCESS not-accessible |
| 1196 |
STATUS current |
| 1197 |
DESCRIPTION |
| 1198 |
"The table providing detailed statistics for responses |
| 1199 |
generated by services on this system." |
| 1200 |
::= { wwwProtocolStatistics 5 } |
| 1201 |
|
| 1202 |
wwwResponseOutEntry OBJECT-TYPE |
| 1203 |
SYNTAX WwwResponseOutEntry |
| 1204 |
MAX-ACCESS not-accessible |
| 1205 |
STATUS current |
| 1206 |
DESCRIPTION |
| 1207 |
"Response statistics for an individual service." |
| 1208 |
INDEX { wwwServiceIndex, wwwResponseOutIndex } |
| 1209 |
::= { wwwResponseOutTable 1 } |
| 1210 |
|
| 1211 |
WwwResponseOutEntry ::= SEQUENCE { |
| 1212 |
wwwResponseOutIndex WwwResponseType, |
| 1213 |
wwwResponseOutResponses Counter32, |
| 1214 |
wwwResponseOutBytes Counter32, |
| 1215 |
wwwResponseOutLastTime DateAndTime |
| 1216 |
} |
| 1217 |
|
| 1218 |
wwwResponseOutIndex OBJECT-TYPE |
| 1219 |
SYNTAX WwwResponseType |
| 1220 |
MAX-ACCESS not-accessible |
| 1221 |
STATUS current |
| 1222 |
DESCRIPTION |
| 1223 |
"The particular response type the statistics apply to." |
| 1224 |
::= { wwwResponseOutEntry 1 } |
| 1225 |
|
| 1226 |
wwwResponseOutResponses OBJECT-TYPE |
| 1227 |
SYNTAX Counter32 |
| 1228 |
MAX-ACCESS read-only |
| 1229 |
STATUS current |
| 1230 |
DESCRIPTION |
| 1231 |
"The number of responses of this type generated by this |
| 1232 |
WWW service." |
| 1233 |
::= { wwwResponseOutEntry 2 } |
| 1234 |
|
| 1235 |
wwwResponseOutBytes OBJECT-TYPE |
| 1236 |
SYNTAX Counter32 |
| 1237 |
MAX-ACCESS read-only |
| 1238 |
STATUS current |
| 1239 |
DESCRIPTION |
| 1240 |
"The number of content bytes per response type generated |
| 1241 |
|
| 1242 |
|
| 1243 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 22]</span></pre> |
| 1244 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1245 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1246 |
|
| 1247 |
|
| 1248 |
by this WWW service." |
| 1249 |
::= { wwwResponseOutEntry 3 } |
| 1250 |
|
| 1251 |
wwwResponseOutLastTime OBJECT-TYPE |
| 1252 |
SYNTAX DateAndTime |
| 1253 |
MAX-ACCESS read-only |
| 1254 |
STATUS current |
| 1255 |
DESCRIPTION |
| 1256 |
"The date and time when the first byte of the last response of |
| 1257 |
this type was sent by this WWW service. The value SHALL be |
| 1258 |
'0000000000000000'H if response of this type has been send |
| 1259 |
yet." |
| 1260 |
::= { wwwResponseOutEntry 4 } |
| 1261 |
|
| 1262 |
|
| 1263 |
-- The WWW Document Statistics Group |
| 1264 |
-- |
| 1265 |
-- The WWW document statistics group contains statistics about |
| 1266 |
-- document read attempts. |
| 1267 |
|
| 1268 |
wwwDocumentStatistics OBJECT IDENTIFIER ::= { wwwMIBObjects 3 } |
| 1269 |
|
| 1270 |
wwwDocCtrlTable OBJECT-TYPE |
| 1271 |
SYNTAX SEQUENCE OF WwwDocCtrlEntry |
| 1272 |
MAX-ACCESS not-accessible |
| 1273 |
STATUS current |
| 1274 |
DESCRIPTION |
| 1275 |
"A table which controls how the MIB implementation |
| 1276 |
collects and maintains document statistics." |
| 1277 |
::= { wwwDocumentStatistics 1 } |
| 1278 |
|
| 1279 |
wwwDocCtrlEntry OBJECT-TYPE |
| 1280 |
SYNTAX WwwDocCtrlEntry |
| 1281 |
MAX-ACCESS not-accessible |
| 1282 |
STATUS current |
| 1283 |
DESCRIPTION |
| 1284 |
"An entry used to configure the wwwDocLastNTable, |
| 1285 |
the wwwDocBucketTable, the wwwDocAccessTopNTable, |
| 1286 |
and the wwwDocBytesTopNTable." |
| 1287 |
INDEX { wwwServiceIndex } |
| 1288 |
::= { wwwDocCtrlTable 1 } |
| 1289 |
|
| 1290 |
WwwDocCtrlEntry ::= SEQUENCE { |
| 1291 |
wwwDocCtrlLastNSize Unsigned32, |
| 1292 |
wwwDocCtrlLastNLock TimeTicks, |
| 1293 |
wwwDocCtrlBuckets Unsigned32, |
| 1294 |
wwwDocCtrlBucketTimeInterval TimeInterval, |
| 1295 |
wwwDocCtrlTopNSize Unsigned32 |
| 1296 |
} |
| 1297 |
|
| 1298 |
|
| 1299 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 23]</span></pre> |
| 1300 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1301 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1302 |
|
| 1303 |
|
| 1304 |
wwwDocCtrlLastNSize OBJECT-TYPE |
| 1305 |
SYNTAX Unsigned32 |
| 1306 |
MAX-ACCESS read-write |
| 1307 |
STATUS current |
| 1308 |
DESCRIPTION |
| 1309 |
"The maximum number of entries in the wwwDocLastNTable." |
| 1310 |
DEFVAL { 25 } |
| 1311 |
::= { wwwDocCtrlEntry 1 } |
| 1312 |
|
| 1313 |
wwwDocCtrlLastNLock OBJECT-TYPE |
| 1314 |
SYNTAX TimeTicks |
| 1315 |
MAX-ACCESS read-write |
| 1316 |
STATUS current |
| 1317 |
DESCRIPTION |
| 1318 |
"This object allows a manager to lock the wwwDocLastNTable |
| 1319 |
in order to retrieve the wwwDocLastNTable in a consistent |
| 1320 |
state. The agent is expected to take a snapshot of the |
| 1321 |
wwwDocLastNTable when it is locked and to continue updating |
| 1322 |
the real wwwDocLastNTable table so that recent information is |
| 1323 |
available as soon as the wwwDocLastNTable is unlocked again. |
| 1324 |
|
| 1325 |
Setting this object to a value greater than 0 will lock |
| 1326 |
the table. The timer ticks backwards until it reaches 0. |
| 1327 |
The table unlocks automatically once the timer reaches 0 |
| 1328 |
and the timer stops ticking. |
| 1329 |
|
| 1330 |
A manager can increase the timer to request more time to |
| 1331 |
read the table. However, any attempt to decrease the timer |
| 1332 |
will fail with an inconsistentValue error. This rule ensures |
| 1333 |
that multiple managers can simultaneously lock and retrieve |
| 1334 |
the wwwDocLastNTable. Note that managers must cooperate in |
| 1335 |
using wwwDocCtrlLastNLock. In particular, a manager MUST not |
| 1336 |
keep the wwwDocLastNTable locked when it is not necessary to |
| 1337 |
finish a retrieval operation." |
| 1338 |
::= { wwwDocCtrlEntry 2 } |
| 1339 |
|
| 1340 |
wwwDocCtrlBuckets OBJECT-TYPE |
| 1341 |
SYNTAX Unsigned32 |
| 1342 |
MAX-ACCESS read-write |
| 1343 |
STATUS current |
| 1344 |
DESCRIPTION |
| 1345 |
"The maximum number of buckets maintained by the agent |
| 1346 |
before the oldest bucket is deleted. The buckets are |
| 1347 |
used to populate the wwwDocAccessTopNTable and the |
| 1348 |
wwwDocBytesTopNTable. The time interval captured in |
| 1349 |
each bucket can be configured by setting the |
| 1350 |
wwwDocCtrlBucketTimeInterval object." |
| 1351 |
DEFVAL { 4 } -- 4 buckets times 15 minutes = 1 hour |
| 1352 |
::= { wwwDocCtrlEntry 3 } |
| 1353 |
|
| 1354 |
|
| 1355 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 24]</span></pre> |
| 1356 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1357 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1358 |
|
| 1359 |
|
| 1360 |
wwwDocCtrlBucketTimeInterval OBJECT-TYPE |
| 1361 |
SYNTAX TimeInterval |
| 1362 |
MAX-ACCESS read-write |
| 1363 |
STATUS current |
| 1364 |
DESCRIPTION |
| 1365 |
"The time interval after which a new bucket is created. |
| 1366 |
Changing this object has no effect on existing buckets." |
| 1367 |
DEFVAL { 90000 } -- 15 minutes (resolution .01 s) |
| 1368 |
::= { wwwDocCtrlEntry 4 } |
| 1369 |
|
| 1370 |
wwwDocCtrlTopNSize OBJECT-TYPE |
| 1371 |
SYNTAX Unsigned32 |
| 1372 |
MAX-ACCESS read-write |
| 1373 |
STATUS current |
| 1374 |
DESCRIPTION |
| 1375 |
"The maximum number of entries shown in the |
| 1376 |
wwwDocAccessTopNTable and the wwwDocBytesTopNTable. |
| 1377 |
Changing this object has no effect on existing buckets." |
| 1378 |
DEFVAL { 25 } |
| 1379 |
::= { wwwDocCtrlEntry 5 } |
| 1380 |
|
| 1381 |
|
| 1382 |
wwwDocLastNTable OBJECT-TYPE |
| 1383 |
SYNTAX SEQUENCE OF WwwDocLastNEntry |
| 1384 |
MAX-ACCESS not-accessible |
| 1385 |
STATUS current |
| 1386 |
DESCRIPTION |
| 1387 |
"The table which logs the last N access attempts." |
| 1388 |
::= { wwwDocumentStatistics 2 } |
| 1389 |
|
| 1390 |
wwwDocLastNEntry OBJECT-TYPE |
| 1391 |
SYNTAX WwwDocLastNEntry |
| 1392 |
MAX-ACCESS not-accessible |
| 1393 |
STATUS current |
| 1394 |
DESCRIPTION |
| 1395 |
"An entry which describes a recent access attempt." |
| 1396 |
INDEX { wwwServiceIndex, wwwDocLastNIndex } |
| 1397 |
::= { wwwDocLastNTable 1 } |
| 1398 |
|
| 1399 |
WwwDocLastNEntry ::= SEQUENCE { |
| 1400 |
wwwDocLastNIndex Unsigned32, |
| 1401 |
wwwDocLastNName WwwDocName, |
| 1402 |
wwwDocLastNTimeStamp DateAndTime, |
| 1403 |
wwwDocLastNRequestType WwwRequestType, |
| 1404 |
wwwDocLastNResponseType WwwResponseType, |
| 1405 |
wwwDocLastNStatusMsg Utf8String, |
| 1406 |
wwwDocLastNBytes Unsigned32 |
| 1407 |
} |
| 1408 |
|
| 1409 |
wwwDocLastNIndex OBJECT-TYPE |
| 1410 |
|
| 1411 |
|
| 1412 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 25]</span></pre> |
| 1413 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1414 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1415 |
|
| 1416 |
|
| 1417 |
SYNTAX Unsigned32 (1..4294967295) |
| 1418 |
MAX-ACCESS not-accessible |
| 1419 |
STATUS current |
| 1420 |
DESCRIPTION |
| 1421 |
"An arbitrary monotonically increasing integer number used |
| 1422 |
for indexing the wwwDocLastNTable. The first document |
| 1423 |
accessed appears in the table with this index value equal |
| 1424 |
to one. Each subsequent document is indexed with the next |
| 1425 |
sequential index value. The Nth document accessed will be |
| 1426 |
indexed by N. This table presents a sliding window of the |
| 1427 |
last wwwDocCtrlLastNSize documents accessed. Thus, entries |
| 1428 |
in this table will be indexed by N-wwwDocCtrlLastNSize |
| 1429 |
thru N if N > wwwDocCtrlLastNSize and 1 thru N if |
| 1430 |
N <= wwwDocCtrlLastNSize. |
| 1431 |
|
| 1432 |
The wwwDocCtrlLastNLock attribute can be used to lock |
| 1433 |
this table to allow the manager to read its contents." |
| 1434 |
::= { wwwDocLastNEntry 1 } |
| 1435 |
|
| 1436 |
wwwDocLastNName OBJECT-TYPE |
| 1437 |
SYNTAX WwwDocName |
| 1438 |
MAX-ACCESS read-only |
| 1439 |
STATUS current |
| 1440 |
DESCRIPTION |
| 1441 |
"The name of the document for which access was attempted." |
| 1442 |
::= { wwwDocLastNEntry 2 } |
| 1443 |
|
| 1444 |
wwwDocLastNTimeStamp OBJECT-TYPE |
| 1445 |
SYNTAX DateAndTime |
| 1446 |
MAX-ACCESS read-only |
| 1447 |
STATUS current |
| 1448 |
DESCRIPTION |
| 1449 |
"The date and time of the last attempt to access this |
| 1450 |
document." |
| 1451 |
::= { wwwDocLastNEntry 3 } |
| 1452 |
|
| 1453 |
wwwDocLastNRequestType OBJECT-TYPE |
| 1454 |
SYNTAX WwwRequestType |
| 1455 |
MAX-ACCESS read-only |
| 1456 |
STATUS current |
| 1457 |
DESCRIPTION |
| 1458 |
"The protocol request type which was received by the |
| 1459 |
server when this document access was attempted." |
| 1460 |
::= { wwwDocLastNEntry 4 } |
| 1461 |
|
| 1462 |
wwwDocLastNResponseType OBJECT-TYPE |
| 1463 |
SYNTAX WwwResponseType |
| 1464 |
MAX-ACCESS read-only |
| 1465 |
STATUS current |
| 1466 |
DESCRIPTION |
| 1467 |
|
| 1468 |
|
| 1469 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 26]</span></pre> |
| 1470 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1471 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1472 |
|
| 1473 |
|
| 1474 |
"The protocol response type which was sent to the client |
| 1475 |
as a result of this attempt to access a document. This |
| 1476 |
object contains the type of the primary response if |
| 1477 |
there were multiple responses to a single request." |
| 1478 |
::= { wwwDocLastNEntry 5 } |
| 1479 |
|
| 1480 |
wwwDocLastNStatusMsg OBJECT-TYPE |
| 1481 |
SYNTAX Utf8String |
| 1482 |
MAX-ACCESS read-only |
| 1483 |
STATUS current |
| 1484 |
DESCRIPTION |
| 1485 |
"This object contains a human readable description of the |
| 1486 |
reason why the wwwDocLastNResponseType was returned to the |
| 1487 |
client. This object defines the implementation-specific |
| 1488 |
reason if the value of wwwDocLastNResponseType indicates |
| 1489 |
an error. For example, this object can indicate that the |
| 1490 |
requested document could not be transferred due to a |
| 1491 |
timeout condition or the document could not be transferred |
| 1492 |
because a 'soft link' pointing to the document could not be |
| 1493 |
resolved." |
| 1494 |
::= { wwwDocLastNEntry 6 } |
| 1495 |
|
| 1496 |
wwwDocLastNBytes OBJECT-TYPE |
| 1497 |
SYNTAX Unsigned32 |
| 1498 |
MAX-ACCESS read-only |
| 1499 |
STATUS current |
| 1500 |
DESCRIPTION |
| 1501 |
"The number of content bytes that were returned as a |
| 1502 |
result of this attempt to access a document." |
| 1503 |
::= { wwwDocLastNEntry 7 } |
| 1504 |
|
| 1505 |
|
| 1506 |
wwwDocBucketTable OBJECT-TYPE |
| 1507 |
SYNTAX SEQUENCE OF WwwDocBucketEntry |
| 1508 |
MAX-ACCESS not-accessible |
| 1509 |
STATUS current |
| 1510 |
DESCRIPTION |
| 1511 |
"This table provides administrative summary information for |
| 1512 |
the buckets maintained per WWW service." |
| 1513 |
::= { wwwDocumentStatistics 3 } |
| 1514 |
|
| 1515 |
wwwDocBucketEntry OBJECT-TYPE |
| 1516 |
SYNTAX WwwDocBucketEntry |
| 1517 |
MAX-ACCESS not-accessible |
| 1518 |
STATUS current |
| 1519 |
DESCRIPTION |
| 1520 |
"An entry which describes the parameters associated with a |
| 1521 |
particular bucket." |
| 1522 |
INDEX { wwwServiceIndex, wwwDocBucketIndex } |
| 1523 |
::= { wwwDocBucketTable 1 } |
| 1524 |
|
| 1525 |
|
| 1526 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 27]</span></pre> |
| 1527 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1528 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1529 |
|
| 1530 |
|
| 1531 |
WwwDocBucketEntry ::= SEQUENCE { |
| 1532 |
wwwDocBucketIndex Unsigned32, |
| 1533 |
wwwDocBucketTimeStamp DateAndTime, |
| 1534 |
wwwDocBucketAccesses Unsigned32, |
| 1535 |
wwwDocBucketDocuments Unsigned32, |
| 1536 |
wwwDocBucketBytes Unsigned32 |
| 1537 |
} |
| 1538 |
|
| 1539 |
wwwDocBucketIndex OBJECT-TYPE |
| 1540 |
SYNTAX Unsigned32 (1..4294967295) |
| 1541 |
MAX-ACCESS not-accessible |
| 1542 |
STATUS current |
| 1543 |
DESCRIPTION |
| 1544 |
"An arbitrary monotonically increasing integer number |
| 1545 |
used for indexing the wwwDocBucketTable. The index number |
| 1546 |
wraps to 1 whenever the maximum value is reached." |
| 1547 |
::= { wwwDocBucketEntry 1 } |
| 1548 |
|
| 1549 |
wwwDocBucketTimeStamp OBJECT-TYPE |
| 1550 |
SYNTAX DateAndTime |
| 1551 |
MAX-ACCESS read-only |
| 1552 |
STATUS current |
| 1553 |
DESCRIPTION |
| 1554 |
"The date and time when the bucket was made available." |
| 1555 |
::= { wwwDocBucketEntry 2 } |
| 1556 |
|
| 1557 |
wwwDocBucketAccesses OBJECT-TYPE |
| 1558 |
SYNTAX Unsigned32 |
| 1559 |
MAX-ACCESS read-only |
| 1560 |
STATUS current |
| 1561 |
DESCRIPTION |
| 1562 |
"The total number of access attempts for any document |
| 1563 |
provided by this WWW service during the time interval |
| 1564 |
over which this bucket was created." |
| 1565 |
::= { wwwDocBucketEntry 3 } |
| 1566 |
|
| 1567 |
wwwDocBucketDocuments OBJECT-TYPE |
| 1568 |
SYNTAX Unsigned32 |
| 1569 |
MAX-ACCESS read-only |
| 1570 |
STATUS current |
| 1571 |
DESCRIPTION |
| 1572 |
"The total number of different documents for which access |
| 1573 |
was attempted this this WWW service during the time interval |
| 1574 |
over which this bucket was created." |
| 1575 |
::= { wwwDocBucketEntry 4 } |
| 1576 |
|
| 1577 |
wwwDocBucketBytes OBJECT-TYPE |
| 1578 |
SYNTAX Unsigned32 |
| 1579 |
MAX-ACCESS read-only |
| 1580 |
STATUS current |
| 1581 |
|
| 1582 |
|
| 1583 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 28]</span></pre> |
| 1584 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1585 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1586 |
|
| 1587 |
|
| 1588 |
DESCRIPTION |
| 1589 |
"The total number of content bytes which were transferred |
| 1590 |
from this WWW service during the time interval over which |
| 1591 |
this bucket was created." |
| 1592 |
::= { wwwDocBucketEntry 5 } |
| 1593 |
|
| 1594 |
|
| 1595 |
wwwDocAccessTopNTable OBJECT-TYPE |
| 1596 |
SYNTAX SEQUENCE OF WwwDocAccessTopNEntry |
| 1597 |
MAX-ACCESS not-accessible |
| 1598 |
STATUS current |
| 1599 |
DESCRIPTION |
| 1600 |
"The table of the most frequently accessed documents in a |
| 1601 |
given bucket. This table is sorted by the column |
| 1602 |
wwwDocAccessTopNAccesses. Entries having the same number |
| 1603 |
of accesses are secondarily sorted by wwwDocAccessTopNBytes. |
| 1604 |
Entries with the same number of accesses and the same |
| 1605 |
number of bytes will have an arbitrary order." |
| 1606 |
::= { wwwDocumentStatistics 4 } |
| 1607 |
|
| 1608 |
wwwDocAccessTopNEntry OBJECT-TYPE |
| 1609 |
SYNTAX WwwDocAccessTopNEntry |
| 1610 |
MAX-ACCESS not-accessible |
| 1611 |
STATUS current |
| 1612 |
DESCRIPTION |
| 1613 |
"An entry in the top N table sorted by document accesses." |
| 1614 |
INDEX { wwwServiceIndex, wwwDocBucketIndex, |
| 1615 |
wwwDocAccessTopNIndex } |
| 1616 |
::= { wwwDocAccessTopNTable 1 } |
| 1617 |
|
| 1618 |
WwwDocAccessTopNEntry ::= SEQUENCE { |
| 1619 |
wwwDocAccessTopNIndex Unsigned32, |
| 1620 |
wwwDocAccessTopNName WwwDocName, |
| 1621 |
wwwDocAccessTopNAccesses Unsigned32, |
| 1622 |
wwwDocAccessTopNBytes Unsigned32, |
| 1623 |
wwwDocAccessTopNLastResponseType WwwResponseType |
| 1624 |
} |
| 1625 |
|
| 1626 |
wwwDocAccessTopNIndex OBJECT-TYPE |
| 1627 |
SYNTAX Unsigned32 (1..4294967295) |
| 1628 |
MAX-ACCESS not-accessible |
| 1629 |
STATUS current |
| 1630 |
DESCRIPTION |
| 1631 |
"An arbitrary monotonically increasing integer number |
| 1632 |
used for indexing the wwwDocAccessTopNTable. The index is |
| 1633 |
inversely correlated to the sorting order of the table. The |
| 1634 |
document with the highest access count will get the index |
| 1635 |
value 1." |
| 1636 |
::= { wwwDocAccessTopNEntry 1 } |
| 1637 |
|
| 1638 |
|
| 1639 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 29]</span></pre> |
| 1640 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1641 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1642 |
|
| 1643 |
|
| 1644 |
wwwDocAccessTopNName OBJECT-TYPE |
| 1645 |
SYNTAX WwwDocName |
| 1646 |
MAX-ACCESS read-only |
| 1647 |
STATUS current |
| 1648 |
DESCRIPTION |
| 1649 |
"The name of the document for which access was attempted." |
| 1650 |
::= { wwwDocAccessTopNEntry 2 } |
| 1651 |
|
| 1652 |
wwwDocAccessTopNAccesses OBJECT-TYPE |
| 1653 |
SYNTAX Unsigned32 |
| 1654 |
MAX-ACCESS read-only |
| 1655 |
STATUS current |
| 1656 |
DESCRIPTION |
| 1657 |
"The total number of access attempts for this document." |
| 1658 |
::= { wwwDocAccessTopNEntry 3 } |
| 1659 |
|
| 1660 |
wwwDocAccessTopNBytes OBJECT-TYPE |
| 1661 |
SYNTAX Unsigned32 |
| 1662 |
MAX-ACCESS read-only |
| 1663 |
STATUS current |
| 1664 |
DESCRIPTION |
| 1665 |
"The total number of content bytes that were transmitted |
| 1666 |
as a result of attempts to access this document." |
| 1667 |
::= { wwwDocAccessTopNEntry 4 } |
| 1668 |
|
| 1669 |
wwwDocAccessTopNLastResponseType OBJECT-TYPE |
| 1670 |
SYNTAX WwwResponseType |
| 1671 |
MAX-ACCESS read-only |
| 1672 |
STATUS current |
| 1673 |
DESCRIPTION |
| 1674 |
"The protocol response type which was sent to the client |
| 1675 |
as a result of the last attempt to access this document. |
| 1676 |
This object contains the type of the primary response if |
| 1677 |
there were multiple responses to a single request." |
| 1678 |
::= { wwwDocAccessTopNEntry 5 } |
| 1679 |
|
| 1680 |
|
| 1681 |
wwwDocBytesTopNTable OBJECT-TYPE |
| 1682 |
SYNTAX SEQUENCE OF WwwDocBytesTopNEntry |
| 1683 |
MAX-ACCESS not-accessible |
| 1684 |
STATUS current |
| 1685 |
DESCRIPTION |
| 1686 |
"The table of the documents which caused most network |
| 1687 |
traffic in a given bucket. This table is sorted by the |
| 1688 |
column wwwDocBytesTopNBytes. Entries having the same number |
| 1689 |
bytes are secondarily sorted by wwwDocBytesTopNAccesses. |
| 1690 |
Entries with the same number of accesses and the same |
| 1691 |
number of bytes will have an arbitrary order." |
| 1692 |
::= { wwwDocumentStatistics 5 } |
| 1693 |
|
| 1694 |
|
| 1695 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 30]</span></pre> |
| 1696 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1697 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1698 |
|
| 1699 |
|
| 1700 |
wwwDocBytesTopNEntry OBJECT-TYPE |
| 1701 |
SYNTAX WwwDocBytesTopNEntry |
| 1702 |
MAX-ACCESS not-accessible |
| 1703 |
STATUS current |
| 1704 |
DESCRIPTION |
| 1705 |
"An entry in the top N table sorted by network traffic." |
| 1706 |
INDEX { wwwServiceIndex, wwwDocBucketIndex, |
| 1707 |
wwwDocBytesTopNIndex } |
| 1708 |
::= { wwwDocBytesTopNTable 1 } |
| 1709 |
|
| 1710 |
WwwDocBytesTopNEntry ::= SEQUENCE { |
| 1711 |
wwwDocBytesTopNIndex Unsigned32, |
| 1712 |
wwwDocBytesTopNName WwwDocName, |
| 1713 |
wwwDocBytesTopNAccesses Unsigned32, |
| 1714 |
wwwDocBytesTopNBytes Unsigned32, |
| 1715 |
wwwDocBytesTopNLastResponseType WwwResponseType |
| 1716 |
} |
| 1717 |
|
| 1718 |
wwwDocBytesTopNIndex OBJECT-TYPE |
| 1719 |
SYNTAX Unsigned32 (1..4294967295) |
| 1720 |
MAX-ACCESS not-accessible |
| 1721 |
STATUS current |
| 1722 |
DESCRIPTION |
| 1723 |
"An arbitrary monotonically increasing integer number |
| 1724 |
used for indexing the wwwDocBytesTopNTable. The index is |
| 1725 |
inversely correlated to the sorting order of the table. The |
| 1726 |
document with the highest byte count will get the index |
| 1727 |
value 1." |
| 1728 |
::= { wwwDocBytesTopNEntry 1 } |
| 1729 |
|
| 1730 |
wwwDocBytesTopNName OBJECT-TYPE |
| 1731 |
SYNTAX WwwDocName |
| 1732 |
MAX-ACCESS read-only |
| 1733 |
STATUS current |
| 1734 |
DESCRIPTION |
| 1735 |
"The name of the document for which access was attempted." |
| 1736 |
::= { wwwDocBytesTopNEntry 2 } |
| 1737 |
|
| 1738 |
wwwDocBytesTopNAccesses OBJECT-TYPE |
| 1739 |
SYNTAX Unsigned32 |
| 1740 |
MAX-ACCESS read-only |
| 1741 |
STATUS current |
| 1742 |
DESCRIPTION |
| 1743 |
"The total number of access attempts for this document." |
| 1744 |
::= { wwwDocBytesTopNEntry 3 } |
| 1745 |
|
| 1746 |
wwwDocBytesTopNBytes OBJECT-TYPE |
| 1747 |
SYNTAX Unsigned32 |
| 1748 |
MAX-ACCESS read-only |
| 1749 |
STATUS current |
| 1750 |
|
| 1751 |
|
| 1752 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 31]</span></pre> |
| 1753 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1754 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1755 |
|
| 1756 |
|
| 1757 |
DESCRIPTION |
| 1758 |
"The total number of content bytes that were transmitted |
| 1759 |
as a result of attempts to access this document." |
| 1760 |
::= { wwwDocBytesTopNEntry 4 } |
| 1761 |
|
| 1762 |
wwwDocBytesTopNLastResponseType OBJECT-TYPE |
| 1763 |
SYNTAX WwwResponseType |
| 1764 |
MAX-ACCESS read-only |
| 1765 |
STATUS current |
| 1766 |
DESCRIPTION |
| 1767 |
"The protocol response type which was sent to the client |
| 1768 |
as a result of the last attempt to access this document. |
| 1769 |
This object contains the type of the primary response if |
| 1770 |
there were multiple responses to a single request." |
| 1771 |
::= { wwwDocBytesTopNEntry 5 } |
| 1772 |
|
| 1773 |
-- |
| 1774 |
-- Conformance Definitions |
| 1775 |
-- |
| 1776 |
|
| 1777 |
wwwMIBCompliances OBJECT IDENTIFIER ::= { wwwMIBConformance 1 } |
| 1778 |
wwwMIBGroups OBJECT IDENTIFIER ::= { wwwMIBConformance 2 } |
| 1779 |
|
| 1780 |
wwwMinimalCompliance MODULE-COMPLIANCE |
| 1781 |
STATUS current |
| 1782 |
DESCRIPTION |
| 1783 |
"The compliance statement for SNMP agents which implement |
| 1784 |
the minimal subset of the WWW-MIB. Implementors might |
| 1785 |
choose this subset for high-performance server where |
| 1786 |
full compliance might be to expensive." |
| 1787 |
MODULE -- this module |
| 1788 |
MANDATORY-GROUPS { |
| 1789 |
wwwServiceGroup, |
| 1790 |
wwwSummaryGroup |
| 1791 |
} |
| 1792 |
OBJECT wwwSummaryOutRequests |
| 1793 |
DESCRIPTION |
| 1794 |
"Instances of wwwSummaryOutRequests do not exist on pure |
| 1795 |
WWW server implementations." |
| 1796 |
OBJECT wwwSummaryInResponses |
| 1797 |
DESCRIPTION |
| 1798 |
"Instances of wwwSummaryOutRequests do not exist on pure |
| 1799 |
WWW server implementations." |
| 1800 |
OBJECT wwwSummaryInRequests |
| 1801 |
DESCRIPTION |
| 1802 |
"Instances of wwwSummaryInRequests do not exist on pure |
| 1803 |
WWW client implementations." |
| 1804 |
OBJECT wwwSummaryOutResponses |
| 1805 |
DESCRIPTION |
| 1806 |
"Instances of wwwSummaryOutResponses do not exist on pure |
| 1807 |
|
| 1808 |
|
| 1809 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 32]</span></pre> |
| 1810 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1811 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1812 |
|
| 1813 |
|
| 1814 |
WWW client implementations." |
| 1815 |
::= { wwwMIBCompliances 1 } |
| 1816 |
|
| 1817 |
wwwFullCompliance MODULE-COMPLIANCE |
| 1818 |
STATUS current |
| 1819 |
DESCRIPTION |
| 1820 |
"The compliance statement for SNMP agents which implement |
| 1821 |
the full WWW-MIB." |
| 1822 |
MODULE -- this module |
| 1823 |
MANDATORY-GROUPS { |
| 1824 |
wwwServiceGroup, |
| 1825 |
wwwSummaryGroup |
| 1826 |
} |
| 1827 |
GROUP wwwRequestInGroup |
| 1828 |
DESCRIPTION |
| 1829 |
"The wwwRequestInGroup is mandatory only for WWW server |
| 1830 |
or proxy server implementations." |
| 1831 |
GROUP wwwResponseOutGroup |
| 1832 |
DESCRIPTION |
| 1833 |
"The wwwResponseOutGroup is mandatory only for WWW server |
| 1834 |
or proxy server implementations." |
| 1835 |
GROUP wwwRequestOutGroup |
| 1836 |
DESCRIPTION |
| 1837 |
"The wwwRequestOutGroup is mandatory only for WWW client |
| 1838 |
or proxy server implementations." |
| 1839 |
GROUP wwwResponseInGroup |
| 1840 |
DESCRIPTION |
| 1841 |
"The wwwRequestOutGroup is mandatory only for WWW client |
| 1842 |
or proxy server implementations." |
| 1843 |
GROUP wwwDocumentGroup |
| 1844 |
DESCRIPTION |
| 1845 |
"The wwwDocumentGroup is mandatory only for WWW server |
| 1846 |
or proxy server implementations." |
| 1847 |
OBJECT wwwSummaryOutRequests |
| 1848 |
DESCRIPTION |
| 1849 |
"Instances of wwwSummaryOutRequests do not exist on pure |
| 1850 |
WWW server implementations." |
| 1851 |
OBJECT wwwSummaryInResponses |
| 1852 |
DESCRIPTION |
| 1853 |
"Instances of wwwSummaryOutRequests do not exist on pure |
| 1854 |
WWW server implementations." |
| 1855 |
OBJECT wwwSummaryInRequests |
| 1856 |
DESCRIPTION |
| 1857 |
"Instances of wwwSummaryInRequests do not exist on pure |
| 1858 |
WWW client implementations." |
| 1859 |
OBJECT wwwSummaryOutResponses |
| 1860 |
DESCRIPTION |
| 1861 |
"Instances of wwwSummaryOutResponses do not exist on pure |
| 1862 |
WWW client implementations." |
| 1863 |
::= { wwwMIBCompliances 2 } |
| 1864 |
|
| 1865 |
|
| 1866 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 33]</span></pre> |
| 1867 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1868 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1869 |
|
| 1870 |
|
| 1871 |
wwwServiceGroup OBJECT-GROUP |
| 1872 |
OBJECTS { |
| 1873 |
wwwServiceDescription, |
| 1874 |
wwwServiceContact, |
| 1875 |
wwwServiceProtocol, |
| 1876 |
wwwServiceName, |
| 1877 |
wwwServiceType, |
| 1878 |
wwwServiceStartTime, |
| 1879 |
wwwServiceOperStatus, |
| 1880 |
wwwServiceLastChange |
| 1881 |
} |
| 1882 |
STATUS current |
| 1883 |
DESCRIPTION |
| 1884 |
"A collection of objects providing information about |
| 1885 |
the WWW services known by the SNMP agent." |
| 1886 |
::= { wwwMIBGroups 1 } |
| 1887 |
|
| 1888 |
wwwSummaryGroup OBJECT-GROUP |
| 1889 |
OBJECTS { |
| 1890 |
wwwSummaryInRequests, |
| 1891 |
wwwSummaryOutRequests, |
| 1892 |
wwwSummaryInResponses, |
| 1893 |
wwwSummaryOutResponses, |
| 1894 |
wwwSummaryInBytes, |
| 1895 |
wwwSummaryInLowBytes, |
| 1896 |
wwwSummaryOutBytes, |
| 1897 |
wwwSummaryOutLowBytes |
| 1898 |
} |
| 1899 |
STATUS current |
| 1900 |
DESCRIPTION |
| 1901 |
"A collection of objects providing summary statistics |
| 1902 |
about requests and responses generated and received |
| 1903 |
by a WWW service." |
| 1904 |
::= { wwwMIBGroups 2 } |
| 1905 |
|
| 1906 |
wwwRequestInGroup OBJECT-GROUP |
| 1907 |
OBJECTS { |
| 1908 |
wwwRequestInRequests, |
| 1909 |
wwwRequestInBytes, |
| 1910 |
wwwRequestInLastTime |
| 1911 |
} |
| 1912 |
STATUS current |
| 1913 |
DESCRIPTION |
| 1914 |
"A collection of objects providing detailed statistics |
| 1915 |
about requests received by a WWW service." |
| 1916 |
::= { wwwMIBGroups 3 } |
| 1917 |
|
| 1918 |
wwwRequestOutGroup OBJECT-GROUP |
| 1919 |
OBJECTS { |
| 1920 |
wwwRequestOutRequests, |
| 1921 |
|
| 1922 |
|
| 1923 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 34]</span></pre> |
| 1924 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1925 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1926 |
|
| 1927 |
|
| 1928 |
wwwRequestOutBytes, |
| 1929 |
wwwRequestOutLastTime |
| 1930 |
} |
| 1931 |
STATUS current |
| 1932 |
DESCRIPTION |
| 1933 |
"A collection of objects providing detailed statistics |
| 1934 |
about requests generated by a WWW service." |
| 1935 |
::= { wwwMIBGroups 4 } |
| 1936 |
|
| 1937 |
wwwResponseInGroup OBJECT-GROUP |
| 1938 |
OBJECTS { |
| 1939 |
wwwResponseInResponses, |
| 1940 |
wwwResponseInBytes, |
| 1941 |
wwwResponseInLastTime |
| 1942 |
} |
| 1943 |
STATUS current |
| 1944 |
DESCRIPTION |
| 1945 |
"A collection of objects providing detailed statistics |
| 1946 |
about responses received by a WWW service." |
| 1947 |
::= { wwwMIBGroups 5 } |
| 1948 |
|
| 1949 |
wwwResponseOutGroup OBJECT-GROUP |
| 1950 |
OBJECTS { |
| 1951 |
wwwResponseOutResponses, |
| 1952 |
wwwResponseOutBytes, |
| 1953 |
wwwResponseOutLastTime |
| 1954 |
} |
| 1955 |
STATUS current |
| 1956 |
DESCRIPTION |
| 1957 |
"A collection of objects providing detailed statistics |
| 1958 |
about responses generated by a WWW service." |
| 1959 |
::= { wwwMIBGroups 6 } |
| 1960 |
|
| 1961 |
wwwDocumentGroup OBJECT-GROUP |
| 1962 |
OBJECTS { |
| 1963 |
wwwDocCtrlLastNSize, |
| 1964 |
wwwDocCtrlLastNLock, |
| 1965 |
wwwDocCtrlBuckets, |
| 1966 |
wwwDocCtrlBucketTimeInterval, |
| 1967 |
wwwDocCtrlTopNSize, |
| 1968 |
wwwDocLastNName, |
| 1969 |
wwwDocLastNTimeStamp, |
| 1970 |
wwwDocLastNRequestType, |
| 1971 |
wwwDocLastNResponseType, |
| 1972 |
wwwDocLastNStatusMsg, |
| 1973 |
wwwDocLastNBytes, |
| 1974 |
wwwDocBucketTimeStamp, |
| 1975 |
wwwDocBucketAccesses, |
| 1976 |
wwwDocBucketDocuments, |
| 1977 |
wwwDocBucketBytes, |
| 1978 |
|
| 1979 |
|
| 1980 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 35]</span></pre> |
| 1981 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1982 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 1983 |
|
| 1984 |
|
| 1985 |
wwwDocAccessTopNName, |
| 1986 |
wwwDocAccessTopNAccesses, |
| 1987 |
wwwDocAccessTopNBytes, |
| 1988 |
wwwDocAccessTopNLastResponseType, |
| 1989 |
wwwDocBytesTopNName, |
| 1990 |
wwwDocBytesTopNAccesses, |
| 1991 |
wwwDocBytesTopNBytes, |
| 1992 |
wwwDocBytesTopNLastResponseType |
| 1993 |
} |
| 1994 |
STATUS current |
| 1995 |
DESCRIPTION |
| 1996 |
"A collection of objects providing information about |
| 1997 |
accesses to documents." |
| 1998 |
::= { wwwMIBGroups 7 } |
| 1999 |
|
| 2000 |
END |
| 2001 |
|
| 2002 |
|
| 2003 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Document Transfer Protocol Mappings</span> |
| 2004 |
|
| 2005 |
This section describes how existing protocols such as HTTP [<a href="#ref-19" title=""Hypertext Transfer Protocol -- HTTP/1.0"">19</a>,<a href="#ref-20" title=""Hypertext Transfer Protocol -- HTTP/1.1"">20</a>] |
| 2006 |
and FTP [<a href="#ref-21" title=""File Transfer Protocol (FTP)"">21</a>] can be mapped on the abstract Document Transfer Protocol |
| 2007 |
(DTP) used within the definitions of the WWW MIB. Every mapping must |
| 2008 |
define the identifier which is used to uniquely identify the transfer |
| 2009 |
protocol. In addition, the mappings must define how requests and |
| 2010 |
responses are identified. |
| 2011 |
|
| 2012 |
|
| 2013 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. The HyperText Transfer Protocol</span> |
| 2014 |
|
| 2015 |
The HyperText Transfer Protocol (HTTP) [<a href="#ref-19" title=""Hypertext Transfer Protocol -- HTTP/1.0"">19</a>,<a href="#ref-20" title=""Hypertext Transfer Protocol -- HTTP/1.1"">20</a>] is an application- |
| 2016 |
level protocol used to transfer hypermedia documents in a distributed |
| 2017 |
networked environment. HTTP is based on the request/response paradigm |
| 2018 |
and can be mapped on the abstract DTP easily. |
| 2019 |
|
| 2020 |
The HTTP protocol usually runs over TCP and uses the well-known TCP |
| 2021 |
port 80. Therefore, the default value for the wwwServiceProtocol |
| 2022 |
object is { applTCPProtoID 80 }. |
| 2023 |
|
| 2024 |
HTTP allows for both requests and responses and an open-ended set of |
| 2025 |
message types. The general message syntax of HTTP is therefore used |
| 2026 |
for the protocol mapping. The BNF specification of the general HTTP |
| 2027 |
message syntax as defined in [<a href="#ref-20" title=""Hypertext Transfer Protocol -- HTTP/1.1"">20</a>] is as follows: |
| 2028 |
|
| 2029 |
generic-message = start-line |
| 2030 |
*message-header |
| 2031 |
CRLF |
| 2032 |
[ message-body ] |
| 2033 |
|
| 2034 |
start-line = Request-Line | Status-Line |
| 2035 |
|
| 2036 |
|
| 2037 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 36]</span></pre> |
| 2038 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2039 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2040 |
|
| 2041 |
|
| 2042 |
Request-Line = Method SP Request-URI SP HTTP-Version CRLF |
| 2043 |
|
| 2044 |
Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF |
| 2045 |
|
| 2046 |
Every HTTP-message where the start-line is a Request-Line is |
| 2047 |
considered a request in the abstract DTP. Every HTTP-message where |
| 2048 |
the start-line is a Status-Line is considered a response in the |
| 2049 |
abstract DTP. The mappings of WwwRequestType and WwwResponseType are |
| 2050 |
defined as follows: |
| 2051 |
|
| 2052 |
o The WwwRequestType corresponds to the method token in the |
| 2053 |
Request-Line. |
| 2054 |
|
| 2055 |
o The WwwResponseType corresponds to the Status-Code in the |
| 2056 |
Status-Line. |
| 2057 |
|
| 2058 |
|
| 2059 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. The File Transfer Protocol</span> |
| 2060 |
|
| 2061 |
The File Transfer Protocol (FTP) [<a href="#ref-21" title=""File Transfer Protocol (FTP)"">21</a>] is an application-level |
| 2062 |
protocol used to transfer files between hosts connected by the TCP/IP |
| 2063 |
suite of protocols. FTP is based on a request/response paradigm and |
| 2064 |
is mapped on the abstract DTP as defined in this section. The FTP |
| 2065 |
model as defined in [<a href="#ref-21" title=""File Transfer Protocol (FTP)"">21</a>] is depicted below. |
| 2066 |
|
| 2067 |
------------- |
| 2068 |
|+---------+| |
| 2069 |
|| User || -------- |
| 2070 |
||Interface|<--->| User | |
| 2071 |
|+----|----+| -------- |
| 2072 |
---------- | | | |
| 2073 |
|+------+| control connection |+----|----+| |
| 2074 |
||Server|<------------------->|| Client || |
| 2075 |
|| PI || Commands/Replies || PI || |
| 2076 |
|+--|---+| |+----|----+| |
| 2077 |
| | | | | | |
| 2078 |
-------- |+--|---+| Data |+----|----+| -------- |
| 2079 |
| File |<--->|Server|<------------------->|| Client |<--->| File | |
| 2080 |
|System| || DTP || Connection || DTP || |System| |
| 2081 |
-------- |+------+| |+---------+| -------- |
| 2082 |
---------- ------------- |
| 2083 |
|
| 2084 |
FTP uses two different connection types between a client and a server |
| 2085 |
to transfer files. The control connection is persistent during a FTP |
| 2086 |
session and used to exchange FTP commands and associated replies. The |
| 2087 |
data connection is only available when bulk data has to be |
| 2088 |
transferred. |
| 2089 |
|
| 2090 |
The FTP protocol usually runs over TCP and uses the well-known TCP |
| 2091 |
port 21 to setup the control connection. Therefore, the default value |
| 2092 |
|
| 2093 |
|
| 2094 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 37]</span></pre> |
| 2095 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2096 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2097 |
|
| 2098 |
|
| 2099 |
for the wwwServiceProtocol object is { applTCPProtoID 21 }. |
| 2100 |
|
| 2101 |
|
| 2102 |
Every FTP command is considered a request in the abstract DTP. Every |
| 2103 |
FTP reply is considered a response in the abstract DTP. It should be |
| 2104 |
noted that a single FTP command can result in multiple FTP replies |
| 2105 |
(e.g. preliminary positive replies). The primary response for a FTP |
| 2106 |
request contains a status code of the form 2xy, 3xy, 4xy or 5xy. See |
| 2107 |
section 4.2 in [<a href="#ref-21" title=""File Transfer Protocol (FTP)"">21</a>] for the exact meaning of these status codes. The |
| 2108 |
mappings for WwwRequestType and WwwResponseType are defined as |
| 2109 |
follows: |
| 2110 |
|
| 2111 |
o The WwwRequestType corresponds to the FTP command token. |
| 2112 |
|
| 2113 |
o The WwwResponseType corresponds to the three-digit code which |
| 2114 |
starts a reply. Multi-line replies with the same three-digit |
| 2115 |
code are counted as a single DTP response. |
| 2116 |
|
| 2117 |
|
| 2118 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 2119 |
|
| 2120 |
There are a number of management objects defined in this MIB module |
| 2121 |
that have a MAX-ACCESS clause of read-write. Such objects may be |
| 2122 |
considered sensitive or vulnerable in some network environments. The |
| 2123 |
support for write operations in a non-secure environment without |
| 2124 |
proper protection can have a negative effect on network operations. |
| 2125 |
|
| 2126 |
There are a number of managed objects in this MIB that may contain |
| 2127 |
sensitive information: |
| 2128 |
|
| 2129 |
o The document statistics group contains traffic information |
| 2130 |
including the names of documents that were a target of protocol |
| 2131 |
operations. This information is sensitive as it allows to obtain |
| 2132 |
access statistics for documents. |
| 2133 |
|
| 2134 |
o The protocol statistics are less sensitive, because they do not |
| 2135 |
contain details about the target of individual requests and |
| 2136 |
responses. However, traffic statistics and error counters still |
| 2137 |
provide usage information about WWW services and about the |
| 2138 |
overall quality of WWW services. It is suggested that sites |
| 2139 |
configure MIB views so that a user of this MIB can only access |
| 2140 |
the portion of the statistics that belong to the WWW services |
| 2141 |
managed by that user. |
| 2142 |
|
| 2143 |
o The service and the summary statistics groups provide |
| 2144 |
information about the existence of WWW services and condensed |
| 2145 |
usage statistics. Some sites may want to protect this |
| 2146 |
information as well, especially if they offer private WWW |
| 2147 |
services that should not be known by the outside world. |
| 2148 |
|
| 2149 |
|
| 2150 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 38]</span></pre> |
| 2151 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2152 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2153 |
|
| 2154 |
|
| 2155 |
SNMPv1 by itself is not a secure environment. Even if the network |
| 2156 |
itself is secure (for example by using IPSec), there is no control as |
| 2157 |
to who on the secure network is allowed to access |
| 2158 |
(read/change/create/delete) the objects in this MIB. |
| 2159 |
|
| 2160 |
|
| 2161 |
It is recommended that implementers consider the security features as |
| 2162 |
provided by the SNMPv3 framework. Specifically, the use of the |
| 2163 |
User-based Security Model <a href="./rfc2574">RFC 2574</a> [<a href="#ref-12" title=""User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)"">12</a>] and the View-based Access |
| 2164 |
Control Model <a href="./rfc2575">RFC 2575</a> [<a href="#ref-15" title=""View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)"">15</a>] is recommended. |
| 2165 |
|
| 2166 |
It is then a customer/user responsibility to ensure that the SNMP |
| 2167 |
entity giving access to an instance of this MIB is properly |
| 2168 |
configured to give access to the objects only to those principals |
| 2169 |
(users) that have legitimate rights to indeed read or write |
| 2170 |
(change/create/delete) them. |
| 2171 |
|
| 2172 |
|
| 2173 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Intellectual Property</span> |
| 2174 |
|
| 2175 |
The IETF takes no position regarding the validity or scope of any |
| 2176 |
intellectual property or other rights that might be claimed to |
| 2177 |
pertain to the implementation or use of the technology described in |
| 2178 |
this document or the extent to which any license under such rights |
| 2179 |
might or might not be available; neither does it represent that it |
| 2180 |
has made any effort to identify any such rights. Information on the |
| 2181 |
IETF's procedures with respect to rights in standards-track and |
| 2182 |
standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of |
| 2183 |
claims of rights made available for publication and any assurances of |
| 2184 |
licenses to be made available, or the result of an attempt made to |
| 2185 |
obtain a general license or permission for the use of such |
| 2186 |
proprietary rights by implementors or users of this specification can |
| 2187 |
be obtained from the IETF Secretariat. |
| 2188 |
|
| 2189 |
The IETF invites any interested party to bring to its attention any |
| 2190 |
copyrights, patents or patent applications, or other proprietary |
| 2191 |
rights which may cover technology that may be required to practice |
| 2192 |
this standard. Please address the information to the IETF Executive |
| 2193 |
Director. |
| 2194 |
|
| 2195 |
|
| 2196 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span> |
| 2197 |
|
| 2198 |
This document was produced by the Application MIB working group. The |
| 2199 |
editors gratefully acknowledge the comments of the following |
| 2200 |
individuals: |
| 2201 |
|
| 2202 |
Mark Gamble, Cheryl Krupczak, Randy Presuhn, Jon Saperia, |
| 2203 |
Bob Stewart, Martin Toet, Chris Wellens, Kenneth White. |
| 2204 |
|
| 2205 |
|
| 2206 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 39]</span></pre> |
| 2207 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2208 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2209 |
|
| 2210 |
|
| 2211 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Editors' Addresses</span> |
| 2212 |
|
| 2213 |
|
| 2214 |
Harrie Hazewinkel |
| 2215 |
Joint Research Centre of the E.C. |
| 2216 |
via Fermi - Ispra 21020 (VA) |
| 2217 |
Italy |
| 2218 |
|
| 2219 |
Phone: +39 0332786322 |
| 2220 |
Fax: +39 0332785641 |
| 2221 |
EMail: [email protected] |
| 2222 |
|
| 2223 |
|
| 2224 |
Carl W. Kalbfleisch |
| 2225 |
Verio, Inc. |
| 2226 |
1950 Stemmons Frwy |
| 2227 |
Suite 2006 |
| 2228 |
Dallas, TX 75207 |
| 2229 |
USA |
| 2230 |
|
| 2231 |
Phone: +1 214 290-8653 |
| 2232 |
Fax: +1 214 744-0742 |
| 2233 |
EMail: [email protected] |
| 2234 |
|
| 2235 |
|
| 2236 |
Juergen Schoenwaelder |
| 2237 |
TU Braunschweig |
| 2238 |
Bueltenweg 74/75 |
| 2239 |
38106 Braunschweig |
| 2240 |
Germany |
| 2241 |
|
| 2242 |
Phone: +49 531 391-3683 |
| 2243 |
Fax: +49 531 489-5936 |
| 2244 |
EMail: [email protected] |
| 2245 |
|
| 2246 |
|
| 2247 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span> |
| 2248 |
|
| 2249 |
[<a id="ref-1">1</a>] Wijnen,, B., Harrington, D. and R. Presuhn, "An Architecture for |
| 2250 |
Describing SNMP Management Frameworks", <a href="./rfc2571">RFC 2571</a>, April 1999. |
| 2251 |
|
| 2252 |
[<a id="ref-2">2</a>] Rose, M. and K. McCloghrie, "Structure and Identification of |
| 2253 |
Management Information for TCP/IP-based Internets", STD, 16, <a href="./rfc1155">RFC</a> |
| 2254 |
<a href="./rfc1155">1155</a>, May 1990. |
| 2255 |
|
| 2256 |
[<a id="ref-3">3</a>] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, <a href="./rfc1212">RFC</a> |
| 2257 |
<a href="./rfc1212">1212</a>, Performance Systems International, March 1991. |
| 2258 |
|
| 2259 |
[<a id="ref-4">4</a>] Rose, M., "A Convention for Defining Traps for use with the SNMP", |
| 2260 |
<a href="./rfc1215">RFC 1215</a>, March 1991. |
| 2261 |
|
| 2262 |
|
| 2263 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 40]</span></pre> |
| 2264 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2265 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2266 |
|
| 2267 |
|
| 2268 |
[<a id="ref-5">5</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. |
| 2269 |
and S. Waldbusser, "Structure of Management Information Version 2 |
| 2270 |
(SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999. |
| 2271 |
|
| 2272 |
[<a id="ref-6">6</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. |
| 2273 |
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC</a> |
| 2274 |
<a href="./rfc2579">2579</a>, April 1999. |
| 2275 |
|
| 2276 |
[<a id="ref-7">7</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. |
| 2277 |
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC</a> |
| 2278 |
<a href="./rfc2580">2580</a>, April 1999. |
| 2279 |
|
| 2280 |
[<a id="ref-8">8</a>] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network |
| 2281 |
Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, May 1990. |
| 2282 |
|
| 2283 |
[<a id="ref-9">9</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction |
| 2284 |
to Community-based SNMPv2", <a href="./rfc1901">RFC 1901</a>, January 1996. |
| 2285 |
|
| 2286 |
[<a id="ref-10">10</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport |
| 2287 |
Mappings for Version 2 of the Simple Network Management Protocol |
| 2288 |
(SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996. |
| 2289 |
|
| 2290 |
[<a id="ref-11">11</a>] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message |
| 2291 |
Processing and Dispatching for the Simple Network Management |
| 2292 |
Protocol (SNMP)", <a href="./rfc2572">RFC 2572</a>, April 1999. |
| 2293 |
|
| 2294 |
[<a id="ref-12">12</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for |
| 2295 |
version 3 of the Simple Network Management Protocol (SNMPv3)", <a href="./rfc2574">RFC</a> |
| 2296 |
<a href="./rfc2574">2574</a>, April 1999. |
| 2297 |
|
| 2298 |
[<a id="ref-13">13</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol |
| 2299 |
Operations for Version 2 of the Simple Network Management Protocol |
| 2300 |
(SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996. |
| 2301 |
|
| 2302 |
[<a id="ref-14">14</a>] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", <a href="./rfc2573">RFC 2573</a>, |
| 2303 |
April 1999. |
| 2304 |
|
| 2305 |
[<a id="ref-15">15</a>] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access |
| 2306 |
Control Model (VACM) for the Simple Network Management Protocol |
| 2307 |
(SNMP)", <a href="./rfc2575">RFC 2575</a>, April 1999. |
| 2308 |
|
| 2309 |
[<a id="ref-16">16</a>] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF |
| 2310 |
Standards Process", <a href="https://www.rfc-editor.org/bcp/bcp11">BCP 11</a>, <a href="./rfc2028">RFC 2028</a>, October 1996. |
| 2311 |
|
| 2312 |
|
| 2313 |
|
| 2314 |
|
| 2315 |
|
| 2316 |
|
| 2317 |
|
| 2318 |
|
| 2319 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 41]</span></pre> |
| 2320 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2321 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2322 |
|
| 2323 |
|
| 2324 |
[<a id="ref-17">17</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement |
| 2325 |
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 2326 |
|
| 2327 |
[<a id="ref-18">18</a>] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource |
| 2328 |
Identifiers (URI): Generic Syntax", <a href="./rfc2396">RFC 2396</a>, August 1998. |
| 2329 |
|
| 2330 |
[<a id="ref-19">19</a>] Berners-Lee, T., Fielding, R. and H. Frystyk, "Hypertext Transfer |
| 2331 |
Protocol -- HTTP/1.0", <a href="./rfc1945">RFC 1945</a>, May 1996. |
| 2332 |
|
| 2333 |
[<a id="ref-20">20</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T. Berners- |
| 2334 |
Lee, "Hypertext Transfer Protocol -- HTTP/1.1", <a href="./rfc2068">RFC 2068</a>, January |
| 2335 |
1997. |
| 2336 |
|
| 2337 |
[<a id="ref-21">21</a>] Postel, J. and J. Reynolds, "File Transfer Protocol (FTP)", STD 9, |
| 2338 |
<a href="./rfc959">RFC 959</a>, October 1985. |
| 2339 |
|
| 2340 |
[<a id="ref-22">22</a>] Kalbfleisch, C., "Applicability of Standards Track MIBs to |
| 2341 |
Management of World Wide Web Servers", <a href="./rfc2039">RFC 2039</a>, November 1996. |
| 2342 |
|
| 2343 |
[<a id="ref-23">23</a>] Krupczak, C. and J. Saperia, "Definitions of System-Level Managed |
| 2344 |
Objects for Applications", <a href="./rfc2287">RFC 2287</a>, February 1998. |
| 2345 |
|
| 2346 |
[<a id="ref-24">24</a>] Kalbfleisch, C., Krupczak, C., Presuhn, R. and J. Saperia, |
| 2347 |
"Application Management MIB", <a href="./rfc2564">RFC 2564</a>, May 1999. |
| 2348 |
|
| 2349 |
[<a id="ref-25">25</a>] Kantor, B. and P. Lapsley, "Network News Transfer Protocol: A |
| 2350 |
Proposed Standard for the Stream-Based Transmission of News", <a href="./rfc977">RFC</a> |
| 2351 |
<a href="./rfc977">977</a>, February 1986. |
| 2352 |
|
| 2353 |
[<a id="ref-26">26</a>] Callaghan, B., "WebNFS Client Specification", <a href="./rfc2054">RFC 2054</a>, October |
| 2354 |
1996 |
| 2355 |
|
| 2356 |
[<a id="ref-27">27</a>] Callaghan, B., "WebNFS Server Specification", <a href="./rfc2055">RFC 2055</a>, October |
| 2357 |
1996. |
| 2358 |
|
| 2359 |
|
| 2360 |
|
| 2361 |
|
| 2362 |
|
| 2363 |
|
| 2364 |
|
| 2365 |
|
| 2366 |
|
| 2367 |
|
| 2368 |
|
| 2369 |
|
| 2370 |
|
| 2371 |
|
| 2372 |
|
| 2373 |
|
| 2374 |
|
| 2375 |
<span class="grey">Hazewinkel, et al. Standards Track [Page 42]</span></pre> |
| 2376 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2377 |
<span class="grey"><a href="./rfc2594">RFC 2594</a> WWW Service MIB May 1999</span> |
| 2378 |
|
| 2379 |
|
| 2380 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Full Copyright Statement</span> |
| 2381 |
|
| 2382 |
Copyright (C) The Internet Society (1999). All Rights Reserved. |
| 2383 |
|
| 2384 |
This document and translations of it may be copied and furnished to |
| 2385 |
others, and derivative works that comment on or otherwise explain it |
| 2386 |
or assist in its implementation may be prepared, copied, published |
| 2387 |
and distributed, in whole or in part, without restriction of any |
| 2388 |
kind, provided that the above copyright notice and this paragraph are |
| 2389 |
included on all such copies and derivative works. However, this |
| 2390 |
document itself may not be modified in any way, such as by removing |
| 2391 |
the copyright notice or references to the Internet Society or other |
| 2392 |
Internet organizations, except as needed for the purpose of |
| 2393 |
developing Internet standards in which case the procedures for |
| 2394 |
copyrights defined in the Internet Standards process must be |
| 2395 |
followed, or as required to translate it into languages other than |
| 2396 |
English. |
| 2397 |
|
| 2398 |
The limited permissions granted above are perpetual and will not be |
| 2399 |
revoked by the Internet Society or its successors or assigns. |
| 2400 |
|
| 2401 |
This document and the information contained herein is provided on an |
| 2402 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 2403 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 2404 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 2405 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 2406 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 2407 |
|
| 2408 |
Acknowledgement |
| 2409 |
|
| 2410 |
Funding for the RFC Editor function is currently provided by the |
| 2411 |
Internet Society. |
| 2412 |
|
| 2413 |
|
| 2414 |
|
| 2415 |
|
| 2416 |
|
| 2417 |
|
| 2418 |
|
| 2419 |
|
| 2420 |
|
| 2421 |
|
| 2422 |
|
| 2423 |
|
| 2424 |
|
| 2425 |
|
| 2426 |
|
| 2427 |
|
| 2428 |
|
| 2429 |
|
| 2430 |
|
| 2431 |
Hazewinkel, et al. Standards Track [Page 43] |
| 2432 |
</pre> |