Definitions of Managed Objects for WWW Services
RFC 2594
|
| Document |
Type |
|
RFC - Proposed Standard
(May 1999; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 2594 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group H. Hazewinkel
Request for Comments: 2594 Joint Research Centre of the E.C.
Category: Standards Track C. Kalbfleisch
Verio, Inc.
J. Schoenwaelder
TU Braunschweig
May 1999
Definitions of Managed Objects for WWW Services
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet Community.
In particular it describes a set of objects for managing World Wide
Web (WWW) services.
Table of Contents
1 Introduction ................................................. 1
2 The SNMP Management Framework ................................ 2
3 Terminology .................................................. 3
4 Overview ..................................................... 4
4.1 Purpose and Requirements ................................... 4
4.2 Relationship to other Standards Efforts .................... 5
4.3 WWW Services ............................................... 5
4.4 Document Transfer Protocol ................................. 6
5 Structure of the MIB ......................................... 7
5.1 Service Information Group .................................. 7
5.2 Protocol Statistics Group .................................. 7
5.3 Document Statistics Group .................................. 8
6 Definitions .................................................. 10
7 Document Transfer Protocol Mappings .......................... 36
7.1 The HyperText Transfer Protocol ............................ 36
7.2 The File Transfer Protocol ................................. 37
8 Security Considerations ...................................... 38
9 Intellectual Property ........................................ 39
10 Acknowledgments ............................................. 39
Hazewinkel, et al. Standards Track [Page 1]
RFC 2594 WWW Service MIB May 1999
11 Editors' Addresses .......................................... 39
12 References .................................................. 40
13 Full Copyright Statement .................................... 43
1. Introduction
This memo defines a set of objects for managing World Wide Web (WWW)
services. This MIB extends the application management framework
defined by the System Application Management MIB (SYSAPPL-MIB) [23]
and the Application Management MIB (APPLICATION-MIB) [24]. The MIB is
also self-contained so that it can be implemented and used without
having to implement or install the APPLICATION-MIB or the SYSAPPL-
MIB.
The protocol statistics defined in the WWW Service MIB are based on
an abstract document transfer protocol (DTP). This memo also defines
a mapping of the abstract DTP to HTTP and FTP. Additional mappings
may be defined in the future in order to use this MIB with other
document transfer protocols. It is anticipated that such future
mappings will be defined in separate RFCs.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [17].
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
second version, called SMIv2, is described in STD 58, RFC 2578
[5], RFC 2579 [6] and RFC 2580 [7].
Show full document text