< draft-ietf-applmib-wwwmib-10.txt		draft-ietf-applmib-wwwmib-11.txt >
	Network Working Group Harrie Hazewinkel		Network Working Group Harrie Hazewinkel
	Internet-Draft Joint Research Centre of the E.C.		Internet-Draft Joint Research Centre of the E.C.
	Expires April 1999 Carl W. Kalbfleisch		Expires August 1999 Carl W. Kalbfleisch
	Verio, Inc.		Verio, Inc.
	Juergen Schoenwaelder		Juergen Schoenwaelder
	TU Braunschweig		TU Braunschweig
	27 October 1998		25 February 1999
	Definitions of Managed Objects for WWW Services		Definitions of Managed Objects for WWW Services
	<draft-ietf-applmib-wwwmib-10.txt>		<draft-ietf-applmib-wwwmib-11.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft and is in full conformance with
	documents of the Internet Engineering Task Force (IETF), its areas,		all provisions of Section 10 of RFC 2026. Internet-Drafts are
	and its working groups. Note that other groups may also distribute		working documents of the Internet Engineering Task Force (IETF), its
	working documents as Internet-Drafts.		areas, and its working groups. Note that other groups may also
			distribute working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as ``work in progress.''		material or to cite them other than as "work in progress."
	To view the entire list of current Internet-Drafts, please check the		The list of current Internet-Drafts can be accessed at
	"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow		http://www.ietf.org/ietf/1id-abstracts.txt
	Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
	Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific		The list of Internet-Draft Shadow Directories can be accessed at
	Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).		http://www.ietf.org/shadow.html.
	Distribution of this document is unlimited. Please send comments to		Distribution of this document is unlimited. Please send comments to
	the Application MIB Working Group, <applmib@ietf.verio.net>.		the Application MIB Working Group, <applmib@ietf.verio.net>.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (1998). All Rights Reserved.		Copyright (C) The Internet Society (1999). All Rights Reserved.
	Abstract		Abstract
	This memo defines an experimental portion of the Management		This memo defines an experimental portion of the Management
	Information Base (MIB) for use with network management protocols in		Information Base (MIB) for use with network management protocols in
	the Internet Community. In particular it describes a set of objects		the Internet Community. In particular it describes a set of objects
	for managing World Wide Web (WWW) services.		for managing World Wide Web (WWW) services.
	Table of Contents		Table of Contents
	skipping to change at page 12, line 30 ¶		skipping to change at page 12, line 30 ¶
	TEXTUAL-CONVENTION, DisplayString, DateAndTime, TimeInterval		TEXTUAL-CONVENTION, DisplayString, DateAndTime, TimeInterval
	FROM SNMPv2-TC		FROM SNMPv2-TC
	MODULE-COMPLIANCE, OBJECT-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP
	FROM SNMPv2-CONF		FROM SNMPv2-CONF
	Utf8String		Utf8String
	FROM SYSAPPL-MIB;		FROM SYSAPPL-MIB;
	wwwMIB MODULE-IDENTITY		wwwMIB MODULE-IDENTITY
	LAST-UPDATED "9810270000Z"		LAST-UPDATED "9902251400Z"
	ORGANIZATION "IETF Application MIB Working Group"		ORGANIZATION "IETF Application MIB Working Group"
	CONTACT-INFO		CONTACT-INFO
	" Harrie Hazewinkel		" Harrie Hazewinkel
	Postal: Joint Research Centre of the E.C.		Postal: Joint Research Centre of the E.C.
	via Fermi - Ispra 21020 (VA)		via Fermi - Ispra 21020 (VA)
	Italy		Italy
	Tel: +39+(0)332 786322		Tel: +39+(0)332 786322
	Fax: +39+(0)332 785641		Fax: +39+(0)332 785641
	skipping to change at page 15, line 31 ¶		skipping to change at page 15, line 31 ¶
	wwwServiceContact Utf8String,		wwwServiceContact Utf8String,
	wwwServiceProtocol OBJECT IDENTIFIER,		wwwServiceProtocol OBJECT IDENTIFIER,
	wwwServiceName DisplayString,		wwwServiceName DisplayString,
	wwwServiceType INTEGER,		wwwServiceType INTEGER,
	wwwServiceStartTime DateAndTime,		wwwServiceStartTime DateAndTime,
	wwwServiceOperStatus WwwOperStatus,		wwwServiceOperStatus WwwOperStatus,
	wwwServiceLastChange DateAndTime		wwwServiceLastChange DateAndTime
	}		}
	wwwServiceIndex OBJECT-TYPE		wwwServiceIndex OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An integer used to uniquely identify a WWW service. The		"An integer used to uniquely identify a WWW service. The
	value must be the same as the corresponding value of the		value must be the same as the corresponding value of the
	applSrvInst defined in the Application Management MIB		applSrvInst defined in the Application Management MIB
	(APPLICATION-MIB) if the applSrvIndex object is available.		(APPLICATION-MIB) if the applSrvIndex object is available.
	It might be necessary to manually configure sub-agents in		It might be necessary to manually configure sub-agents in
	order to meet this requirement."		order to meet this requirement."
	::= { wwwServiceEntry 1 }		::= { wwwServiceEntry 1 }
	skipping to change at page 28, line 14 ¶		skipping to change at page 28, line 14 ¶
	wwwDocLastNIndex Unsigned32,		wwwDocLastNIndex Unsigned32,
	wwwDocLastNName WwwDocName,		wwwDocLastNName WwwDocName,
	wwwDocLastNTimeStamp DateAndTime,		wwwDocLastNTimeStamp DateAndTime,
	wwwDocLastNRequestType WwwRequestType,		wwwDocLastNRequestType WwwRequestType,
	wwwDocLastNResponseType WwwResponseType,		wwwDocLastNResponseType WwwResponseType,
	wwwDocLastNStatusMsg Utf8String,		wwwDocLastNStatusMsg Utf8String,
	wwwDocLastNBytes Unsigned32		wwwDocLastNBytes Unsigned32
	}		}
	wwwDocLastNIndex OBJECT-TYPE		wwwDocLastNIndex OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An arbitrary monotonically increasing integer number used		"An arbitrary monotonically increasing integer number used
	for indexing the wwwDocLastNTable. The first document		for indexing the wwwDocLastNTable. The first document
	accessed appears in the table with this index value equal		accessed appears in the table with this index value equal
	to one. Each subsequent document is indexed with the next		to one. Each subsequent document is indexed with the next
	sequential index value. The Nth document accessed will be		sequential index value. The Nth document accessed will be
	indexed by N. This table presents a sliding window of the		indexed by N. This table presents a sliding window of the
	last N documents accessed where N is the value of		last wwwDocCtrlLastNSize documents accessed. Thus, entries
	wwwDocCtrlLastNSize. Thus at any given time, the entries in		in this table will be indexed by N-wwwDocCtrlLastNSize
	this table will be indexed by N-wwwDocCtrlLastNSize thru		thru N if N > wwwDocCtrlLastNSize and 1 thru N if
	N. The wwwDocCtrlLastNLock attribute can be used to lock		N <= wwwDocCtrlLastNSize.
			The wwwDocCtrlLastNLock attribute can be used to lock
	this table to allow the manager to read its contents."		this table to allow the manager to read its contents."
	::= { wwwDocLastNEntry 1 }		::= { wwwDocLastNEntry 1 }
	wwwDocLastNName OBJECT-TYPE		wwwDocLastNName OBJECT-TYPE
	SYNTAX WwwDocName		SYNTAX WwwDocName
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The name of the document for which access was attempted."		"The name of the document for which access was attempted."
	::= { wwwDocLastNEntry 2 }		::= { wwwDocLastNEntry 2 }
	skipping to change at page 30, line 28 ¶		skipping to change at page 30, line 30 ¶
	WwwDocBucketEntry ::= SEQUENCE {		WwwDocBucketEntry ::= SEQUENCE {
	wwwDocBucketIndex Unsigned32,		wwwDocBucketIndex Unsigned32,
	wwwDocBucketTimeStamp DateAndTime,		wwwDocBucketTimeStamp DateAndTime,
	wwwDocBucketAccesses Unsigned32,		wwwDocBucketAccesses Unsigned32,
	wwwDocBucketDocuments Unsigned32,		wwwDocBucketDocuments Unsigned32,
	wwwDocBucketBytes Unsigned32		wwwDocBucketBytes Unsigned32
	}		}
	wwwDocBucketIndex OBJECT-TYPE		wwwDocBucketIndex OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An arbitrary monotonically increasing integer number		"An arbitrary monotonically increasing integer number
	used for indexing the wwwDocBucketTable. The index number		used for indexing the wwwDocBucketTable. The index number
	wraps to 1 whenever the maximum value is reached."		wraps to 1 whenever the maximum value is reached."
	::= { wwwDocBucketEntry 1 }		::= { wwwDocBucketEntry 1 }
	wwwDocBucketTimeStamp OBJECT-TYPE		wwwDocBucketTimeStamp OBJECT-TYPE
	SYNTAX DateAndTime		SYNTAX DateAndTime
	skipping to change at page 32, line 14 ¶		skipping to change at page 32, line 16 ¶
	WwwDocAccessTopNEntry ::= SEQUENCE {		WwwDocAccessTopNEntry ::= SEQUENCE {
	wwwDocAccessTopNIndex Unsigned32,		wwwDocAccessTopNIndex Unsigned32,
	wwwDocAccessTopNName WwwDocName,		wwwDocAccessTopNName WwwDocName,
	wwwDocAccessTopNAccesses Unsigned32,		wwwDocAccessTopNAccesses Unsigned32,
	wwwDocAccessTopNBytes Unsigned32,		wwwDocAccessTopNBytes Unsigned32,
	wwwDocAccessTopNLastResponseType WwwResponseType		wwwDocAccessTopNLastResponseType WwwResponseType
	}		}
	wwwDocAccessTopNIndex OBJECT-TYPE		wwwDocAccessTopNIndex OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An arbitrary monotonically increasing integer number		"An arbitrary monotonically increasing integer number
	used for indexing the wwwDocAccessTopNTable. The index is		used for indexing the wwwDocAccessTopNTable. The index is
	inversely correlated to the sorting order of the table. The		inversely correlated to the sorting order of the table. The
	document with the highest access count will get the index		document with the highest access count will get the index
	value 1."		value 1."
	::= { wwwDocAccessTopNEntry 1 }		::= { wwwDocAccessTopNEntry 1 }
	skipping to change at page 33, line 45 ¶		skipping to change at page 33, line 48 ¶
	WwwDocBytesTopNEntry ::= SEQUENCE {		WwwDocBytesTopNEntry ::= SEQUENCE {
	wwwDocBytesTopNIndex Unsigned32,		wwwDocBytesTopNIndex Unsigned32,
	wwwDocBytesTopNName WwwDocName,		wwwDocBytesTopNName WwwDocName,
	wwwDocBytesTopNAccesses Unsigned32,		wwwDocBytesTopNAccesses Unsigned32,
	wwwDocBytesTopNBytes Unsigned32,		wwwDocBytesTopNBytes Unsigned32,
	wwwDocBytesTopNLastResponseType WwwResponseType		wwwDocBytesTopNLastResponseType WwwResponseType
	}		}
	wwwDocBytesTopNIndex OBJECT-TYPE		wwwDocBytesTopNIndex OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An arbitrary monotonically increasing integer number		"An arbitrary monotonically increasing integer number
	used for indexing the wwwDocBytesTopNTable. The index is		used for indexing the wwwDocBytesTopNTable. The index is
	inversely correlated to the sorting order of the table. The		inversely correlated to the sorting order of the table. The
	document with the highest byte count will get the index		document with the highest byte count will get the index
	value 1."		value 1."
	::= { wwwDocBytesTopNEntry 1 }		::= { wwwDocBytesTopNEntry 1 }
	skipping to change at page 40, line 28 ¶		skipping to change at page 40, line 28 ¶
	networked environment. HTTP is based on the request/response paradigm		networked environment. HTTP is based on the request/response paradigm
	and can be mapped on the abstract DTP easily.		and can be mapped on the abstract DTP easily.
	The HTTP protocol usually runs over TCP and uses the well-known TCP		The HTTP protocol usually runs over TCP and uses the well-known TCP
	port 80. Therefore, the default value for the wwwServiceProtocol		port 80. Therefore, the default value for the wwwServiceProtocol
	object is { applTCPProtoID 80 }.		object is { applTCPProtoID 80 }.
	HTTP allows for both requests and responses and an open-ended set of		HTTP allows for both requests and responses and an open-ended set of
	message types. The general message syntax of HTTP is therefore used		message types. The general message syntax of HTTP is therefore used
	for the protocol mapping. The BNF specification of the general HTTP		for the protocol mapping. The BNF specification of the general HTTP
	message syntax as defined in [8] is as follows:		message syntax as defined in [20] is as follows:
	HTTP-message = start-line		generic-message = start-line
	*message-header		*message-header
	CRLF		CRLF
	[ message-body ]		[ message-body ]
	start-line = Request-Line | Status-Line		start-line = Request-Line | Status-Line
	Request-Line = Method SP Request-URI SP HTTP-Version CRLF		Request-Line = Method SP Request-URI SP HTTP-Version CRLF
	Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF		Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
	Every HTTP-message where the start-line is a Request-Line is		Every HTTP-message where the start-line is a Request-Line is
	considered a request in the abstract DTP. Every HTTP-message where		considered a request in the abstract DTP. Every HTTP-message where
	the start-line is a Status-Line is considered a response in the		the start-line is a Status-Line is considered a response in the
	abstract DTP. The mappings of wwwRequestType and wwwResponseType are		abstract DTP. The mappings of WwwRequestType and WwwResponseType are
	defined as follows:		defined as follows:
	o The wwwRequestType corresponds to the method token in the		o The WwwRequestType corresponds to the method token in the
	Request-Line.		Request-Line.
	o The wwwResponseType corresponds to the Status-Code in the		o The WwwResponseType corresponds to the Status-Code in the
	Status-Line.		Status-Line.
	7.2. The File Transfer Protocol		7.2. The File Transfer Protocol
	The File Transfer Protocol (FTP) [21] is an application-level		The File Transfer Protocol (FTP) [21] is an application-level
	protocol used to transfer files between hosts connected by the TCP/IP		protocol used to transfer files between hosts connected by the TCP/IP
	suite of protocols. FTP is based on a request/response paradigm and		suite of protocols. FTP is based on a request/response paradigm and
	is mapped on the abstract DTP as defined in this section. The FTP		is mapped on the abstract DTP as defined in this section. The FTP
	model as defined in [21] is depicted below.		model as defined in [21] is depicted below.
	skipping to change at page 41, line 49 ¶		skipping to change at page 41, line 49 ¶
	The FTP protocol usually runs over TCP and uses the well-known TCP		The FTP protocol usually runs over TCP and uses the well-known TCP
	port 21 to setup the control connection. Therefore, the default value		port 21 to setup the control connection. Therefore, the default value
	for the wwwServiceProtocol object is { applTCPProtoID 21 }.		for the wwwServiceProtocol object is { applTCPProtoID 21 }.
	Every FTP command is considered a request in the abstract DTP. Every		Every FTP command is considered a request in the abstract DTP. Every
	FTP reply is considered a response in the abstract DTP. It should be		FTP reply is considered a response in the abstract DTP. It should be
	noted that a single FTP command can result in multiple FTP replies		noted that a single FTP command can result in multiple FTP replies
	(e.g. preliminary positive replies). The primary response for a FTP		(e.g. preliminary positive replies). The primary response for a FTP
	request contains a status code of the form 2xy, 3xy, 4xy or 5xy. See		request contains a status code of the form 2xy, 3xy, 4xy or 5xy. See
	section 4.2 in [21] for the exact meaning of these status codes. The		section 4.2 in [21] for the exact meaning of these status codes. The
	mappings for wwwRequestType and wwwResponseType are defined as		mappings for WwwRequestType and WwwResponseType are defined as
	follows:		follows:
	o The wwwRequestType corresponds to the FTP command token.		o The WwwRequestType corresponds to the FTP command token.
	o The wwwResponseType corresponds to the three-digit code which		o The WwwResponseType corresponds to the three-digit code which
	starts a reply. Multi-line replies with the same three-digit		starts a reply. Multi-line replies with the same three-digit
	code are counted as a single DTP response.		code are counted as a single DTP response.
	8. Security Considerations		8. Security Considerations
	There are a number of management objects defined in this MIB module		There are a number of management objects defined in this MIB module
	that have a MAX-ACCESS clause of read-write. Such objects may be		that have a MAX-ACCESS clause of read-write. Such objects may be
	considered sensitive or vulnerable in some network environments. The		considered sensitive or vulnerable in some network environments. The
	support for write operations in a non-secure environment without		support for write operations in a non-secure environment without
	proper protection can have a negative effect on network operations.		proper protection can have a negative effect on network operations.
	skipping to change at page 43, line 39 ¶		skipping to change at page 43, line 39 ¶
	rights which may cover technology that may be required to practice		rights which may cover technology that may be required to practice
	this standard. Please address the information to the IETF Executive		this standard. Please address the information to the IETF Executive
	Director.		Director.
	10. Acknowledgments		10. Acknowledgments
	This document was produced by the Application MIB working group. The		This document was produced by the Application MIB working group. The
	editors gratefully acknowledge the comments of the following		editors gratefully acknowledge the comments of the following
	individuals:		individuals:
	Mark Gamble, Cheryl Krupczak, Randy Preshun, John Saperia,		Mark Gamble, Cheryl Krupczak, Randy Preshun, Jon Saperia,
	Bob Stewart, Martin Toet, Chris Wellens, Kenneth White		Bob Stewart, Martin Toet, Chris Wellens, Kenneth White
	11. Editors' Addresses		11. Editors' Addresses
	Harrie Hazewinkel Email: harrie.hazewinkel@jrc.it		Harrie Hazewinkel Email: harrie.hazewinkel@jrc.it
	Joint Research Centre of the E.C. Tel: +39 (0)332 786322		Joint Research Centre of the E.C. Tel: +39 (0)332 786322
	via Fermi - Ispra 21020 (VA) Fax: +39 (0)332 785641		via Fermi - Ispra 21020 (VA) Fax: +39 (0)332 785641
	Italy		Italy
	Carl W. Kalbfleisch Email: cwk@verio.net		Carl W. Kalbfleisch Email: cwk@verio.net
	Verio, Inc. Tel: +1 972 238-8303		Verio, Inc. Tel: +1 972 238-8303
	skipping to change at page 47, line 17 ¶		skipping to change at page 47, line 17 ¶
	[22] C. Kalbfleisch, "Applicability of Standards Track MIBs to		[22] C. Kalbfleisch, "Applicability of Standards Track MIBs to
	Management of World Wide Web Servers", RFC 2039, OnRamp		Management of World Wide Web Servers", RFC 2039, OnRamp
	Technologies, November 1996.		Technologies, November 1996.
	[23] Krupczak, C., and J. Saperia, "Definitions of System-Level Managed		[23] Krupczak, C., and J. Saperia, "Definitions of System-Level Managed
	Objects for Applications", RFC 2287, Empire Technologies, BGS		Objects for Applications", RFC 2287, Empire Technologies, BGS
	Systems, February 1998.		Systems, February 1998.
	[24] Kalbfleisch, C., Krupczak, C., Preshun, R., and J. Saperia,		[24] Kalbfleisch, C., Krupczak, C., Preshun, R., and J. Saperia,
	"Application Management MIB", draft-ietf-applmib-mib-10.txt, Verio,		"Application Management MIB", draft-ietf-applmib-mib-11.txt, Verio,
	Empire Technologies, BMC Software, BGS Systems, August 1998.		Empire Technologies, BMC Software, BGS Systems, November 1998.
	[25] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A		[25] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A
	Proposed Standard for the Stream-Based Transmission of News", RFC		Proposed Standard for the Stream-Based Transmission of News", RFC
	977, UC San Diego & UC Berkeley, February 1986.		977, UC San Diego & UC Berkeley, February 1986.
	[26] Callaghan, B., "WebNFS Client Specification", RFC 2054, Sun		[26] Callaghan, B., "WebNFS Client Specification", RFC 2054, Sun
	Microsystems, October 1996		Microsystems, October 1996
	[27] Callaghan, B., "WebNFS Server Specification", RFC 2055, Sun		[27] Callaghan, B., "WebNFS Server Specification", RFC 2055, Sun
	Microsystems, October 1996		Microsystems, October 1996
	13. Full Copyright Statement		13. Full Copyright Statement
	Copyright (C) The Internet Society (1998). All Rights Reserved.		Copyright (C) The Internet Society (1999). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
End of changes. 25 change blocks.
	39 lines changed or deleted		42 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/