idnits 2.17.1 draft-hazewinkel-rsmib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-23) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == Mismatching filename: the document gives the document name as 'draft-hazewinkel-rsmib-01', but the file name used is 'draft-hazewinkel-rsmib-00' == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** There are 223 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 22, 1996) is 10228 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '3' is defined on line 430, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 434, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 438, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 442, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 446, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '3') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1904 (ref. '5') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '6') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '7') Summary: 17 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Retrieval Service MIB April 22, 1996 3 Definitions of Managed Objects for an Information Retrieval Service 5 April 22, 1996 7 9 Harrie Hazewinkel 10 University of Twente 11 hazewink@cs.utwente.nl 13 Eric van Hengstum 14 University of Twente 15 hengstum@cs.utwente.nl 17 Aiko Pras 18 University of Twente 19 pras@cs.utwente.nl 21 Status of this Memo 23 This document is an Internet-Draft. Internet-Drafts are working 24 documents of the Internet Engineering Task Force (IETF), its 25 areas, and its working groups. Note that other groups may also 26 distribute working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six 29 months and may be updated, replaced, or obsoleted by other 30 documents at any time. It is inappropriate to use Internet- 31 Drafts as reference material or to cite them other than as ``work 32 in progress.'' 34 To learn the current status of any Internet-Draft, please check 35 the ``1id-abstracts.txt'' listing contained in the Internet- 36 Drafts Shadow Directories on ds.internic.net (US East Coast), 37 nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or 38 munnari.oz.au (Pacific Rim). 40 1. Abstract 42 This memo defines a MIB for use with managing information services. 43 The term "information services" is construed to mean any information 44 providing application, such as World Wide Web (WWW), File Transfer 45 Protocol (FTP), and Gopher. The retrieval service is an abstraction 46 for the information transport protocol. The retrieval service which 47 is a connection-less service can by instantiate by, for instance, the 48 Hyper Text Transfer Protocol, or the File Transfer Protocol. 50 2. The SNMPv2 Network Management Framework 52 The SNMPv2 Network Management Framework consists of four major 53 components. They are: 55 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 56 objects for the Internet suite of protocols. 58 o RFC 1901 Introduction to Community-based SNMPv2 60 o RFC 1902 Structure of Management Information for Version 2 of 61 the Simple Network Management Protocol (SNMPv2) 63 o RFC 1903 Textual Conventions for Version 2 of the Simple 64 Network Management Protocol (SNMPv2) 66 o RFC 1904 Conformance Statements for Version 2 of the Simple 67 Network Management Protocol (SNMPv2) 69 o RFC 1907 Management Information Base for Version 2 of the 70 Simple Network Management Protocol (SNMPv2) 72 o RFC 1908 Coexistence between Version 1 and Version 2 of the 73 Internet-standard Network Management Framework 75 The Framework permits new objects to be defined for the purpose of 76 experimentation and evaluation. 78 2.1. Object Definitions 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the MIB 82 are defined using the subset of Abstract Syntax Notation One 83 (ASN.1) defined in the SMI[1]. In particular, each object type is 84 named by an OBJECT IDENTIFIER, an administratively assigned name. 85 The object type together with an object instance serves to 86 uniquely identify a specific instantiation of the object. For 87 human convenience, we often use a textual string, termed the 88 object descriptor, to refer to the object type. 90 3. Introduction. 92 The Retrieval Service is a connection-less service providing 93 transport of information between a client and a server. The service 94 is an abstraction of the information transport protocol used. 95 The Retrieval Service MIB module contains network management 96 information about a provided service. Because the Retrieval Service 97 is an abstraction of the information transport service used in, for 98 instance, the World Wide Web, details of the transport protocol 99 providing this service are of no importance to the users of the 100 Retrieval Service. 102 The work performed for this MIB is a result of a project executed for 103 the Centre of Earth Observations. It is not seen as complete, but it 104 should be a first step in an effort to manage the WWW application. 105 An implementation of this MIB already exists. Due to the use of a 106 commercial development package it cannot be distributed. However, a 107 public domain version is now developed. 109 4. Retrieval Service MIB structure 111 The Retrieval Service module contains the following groups: 112 1. service primitives/ statistics, 113 2. quality of service. 115 4.1. Statistics group 117 Communication via the Retrieval Service takes place by means of 118 service primitives used by the connection-less service. The statistics 119 group contains statistical information concerning the service 120 primitives passed over the Service Access Point (SAP). The variables 121 of this group count the number of service primitives executed on the 122 retrieval service. 124 Two possible solutions were seen to define these counters: 125 1. The total numbers of service primitives are counted by type. 126 For each service primitive type used by the retrieval service 127 a managed object has to be defined. 128 2. The total number of service primitives related to a remote host 129 and service primitive-type are counted. This results in a 130 conceptual table; for each service primitive type used by the 131 retrieval service a table has to be defined, indexed with the 132 IpAddress of the remote host. The remote host is a parameter of 133 the service primitive. 135 It was decided that the simplicity of the first solution outweighed 136 the increased information present in the second. 138 4.2. Quality of Service group 140 The Quality of Service QoS group contains network management 141 information about the quality of the retrieval service. The 142 information in this group provides the network manager with 143 visibility of the performance of the underlying network. 145 The recognized QoS parameters are: 147 - The transport delay is defined as a table. The table is indexed 148 with the source and destination addresses of the delay. 150 The total round trip delay can be computed by the Network 151 Management System user. 153 - The number of errors variable provides information on errors 154 which have occurred in the retrieval service. 155 - The number of timeouts variable provides information on timeouts 156 which have occurred in the retrieval service. 157 - The throughput table provides information on the speed of the 158 network with a given client. The address of the client is used 159 to index the table. 161 5. Retrieval Service MIB definition 163 RS-MIB DEFINITIONS ::= 164 BEGIN 166 IMPORTS 167 enterprises, MODULE-IDENTITY, OBJECT-TYPE, Counter32, TimeTicks, 168 IpAddress 169 FROM SNMPv2-SMI 170 MODULE-COMPLIANCE, OBJECT-GROUP 171 FROM SNMPv2-CONF; 173 rsMIB MODULE-IDENTITY 174 LAST-UPDATED "9601251800Z" 175 ORGANIZATION "University Of Twente" 176 CONTACT-INFO 177 " Harrie Hazewinkel 178 Postal: Centre of Telematics and 179 Information Technology 180 University Of Twente 181 POBox 217 182 7500 AE Enschede 183 The Netherlands 184 phone : +31 53 8943746 185 E-mail: H.Hazewinkel@cs.utwente.nl 187 This document benefited greatly from the comments of 188 all participants in the CEO project for management of 189 World Wide Web Servers." 190 DESCRIPTION 191 "A MIB module for the retrieval service. The retrieval 192 service is a service providing the capability of 193 information transport via a network. 195 It provides management information about an 196 information transport, which is exactly describing 197 what the transport provider is doing for the user, 198 without showing detailed information from inside 199 the transport provider, HTTP." 200 ::= { enterprises universityOfTwente(785) 3 } 202 rsMIBObjects OBJECT IDENTIFIER ::= { rsMIB 1 } 203 rsMIBConformance OBJECT IDENTIFIER ::= { rsMIB 2 } 204 rsMIBCompliances OBJECT IDENTIFIER ::= { rsMIBConformance 1 } 205 rsMIBGroups OBJECT IDENTIFIER ::= { rsMIBConformance 2 } 206 -- 207 -- The service statistics provides management 208 -- information about the service primitives that are 209 -- executed on the HTTP Service Provider. 210 -- 212 rsStatistics OBJECT IDENTIFIER ::= { rsMIBObjects 1 } 214 rsTotalRequests OBJECT-TYPE 215 SYNTAX Counter32 216 MAX-ACCESS read-only 217 STATUS current 218 DESCRIPTION 219 "The total number of requests that have been executed 220 on the HTTP service provider. 222 This field is only interesting when management 223 functions are implemented at the client side." 224 ::= { rsStatistics 1 } 225 -- Instrumentation: client 227 rsTotalIndications OBJECT-TYPE 228 SYNTAX Counter32 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The total number of indications that have been executed 233 on the HTTP service provider." 234 ::= { rsStatistics 2 } 235 -- Instrumentation: logfile 237 rsTotalResponses OBJECT-TYPE 238 SYNTAX Counter32 239 MAX-ACCESS read-only 240 STATUS current 241 DESCRIPTION 242 "The total number of responses that have been executed 243 on the HTTP service provider." 244 ::= { rsStatistics 3 } 245 -- Instrumentation: logfile 247 rsTotalConfirmations OBJECT-TYPE 248 SYNTAX Counter32 249 MAX-ACCESS read-only 250 STATUS current 251 DESCRIPTION 252 "The total number of confirmations that have been 253 executed on the HTTP service provider. 255 This field is only interesting when management 256 functions are implemented at the client side." 257 ::= { rsStatistics 4 } 258 -- Instrumentation: client 259 -- 260 -- The provided QoS of the service provider. 261 -- 263 rsQoS OBJECT IDENTIFIER ::= { rsMIBObjects 2 } 265 rsDelayTable OBJECT-TYPE 266 SYNTAX SEQUENCE OF RsDelayEntry 267 MAX-ACCESS not-accessible 268 STATUS current 269 DESCRIPTION 270 "The table of the delay between source and destination." 271 ::= { rsQoS 1 } 273 rsDelayEntry OBJECT-TYPE 274 SYNTAX RsDelayEntry 275 MAX-ACCESS not-accessible 276 STATUS current 277 DESCRIPTION 278 "Details of a particular http Server or Client." 279 INDEX { rsSource, rsDestination } 280 ::= { rsDelayTable 1 } 282 RsDelayEntry ::= 283 SEQUENCE { 284 rsSource DisplayString, 285 rsDestination DisplayString, 286 rsDelay TimeInterval 287 } 289 rsSource OBJECT-TYPE 290 SYNTAX DisplayString 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "The DNS name of the source." 295 ::= { rsDelayEntry 1 } 296 -- Instrumentation: logfile / own system 298 rsDestination OBJECT-TYPE 299 SYNTAX DisplayString 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "The DNSname of the destination." 304 ::= { rsDelayEntry 2 } 305 -- Instrumentation: logfile / own system 306 rsDelay OBJECT-TYPE 307 SYNTAX TimeInterval 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "The delay which occured during transport of information 312 from source to destination." 313 ::= { rsDelayEntry 3 } 314 -- Instrumentation: client / server 316 rsNumberOfErrors OBJECT-TYPE 317 SYNTAX Counter32 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION 321 "The number of errors that have been occured." 322 ::= { rsQoS 2 } 323 -- Instrumentation: client 325 rsNumberOfTimeouts OBJECT-TYPE 326 SYNTAX Counter32 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION 330 "The number of time-outs that have been occured." 331 ::= { rsQoS 3 } 332 -- Instrumentation: logfile 334 rsTroughputTable OBJECT-TYPE 335 SYNTAX SEQUENCE OF RsTroughputEntry 336 MAX-ACCESS not-accessible 337 STATUS current 338 DESCRIPTION 339 "The table of the throughput with a certain client." 340 ::= { rsQoS 4 } 342 rsTroughputEntry OBJECT-TYPE 343 SYNTAX RsTroughputEntry 344 MAX-ACCESS not-accessible 345 STATUS current 346 DESCRIPTION 347 "Details of a particular http Server or Client." 348 INDEX { rsClient } 349 ::= { rsTroughputTable 1 } 351 RsTroughputEntry ::= 352 SEQUENCE { 353 rsClient DisplayString, 354 rsThroughput INTEGER 355 } 356 rsClient OBJECT-TYPE 357 SYNTAX DisplayString 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The DNS name of the client." 362 ::= { rsTroughputEntry 1 } 363 -- Instrumentation: logfile 365 rsThroughput OBJECT-TYPE 366 SYNTAX INTEGER (1..2147483647) 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "The throughput of data with the client." 371 ::= { rsTroughputEntry 2 } 372 -- Instrumentation: direct access 374 -- 375 -- Conformance and compliance definitions. 376 -- 378 rsMIBCompliance MODULE-COMPLIANCE 379 STATUS current 380 DESCRIPTION 381 "The compliance statements for http service 382 which implement the HTTP MIB" 383 MODULE 384 MANDATORY-GROUPS { rsGroup } 385 ::= { rsMIBCompliances 1 } 387 rsMIBGroup OBJECT-GROUP 388 OBJECTS { rsTotalRequests, rsTotalIndications, 389 rsTotalResponses, rsTotalConfirmations, 390 rsSource, rsDestination, rsDelay, 391 rsNumberOfErrors, 392 rsNumberOfTimeouts, 393 rsClient,rsThroughput } 394 STATUS current 395 DESCRIPTION 396 "The rsGroup defines the objects 397 of the retrieval service." 398 ::= { rsMIBGroups 1 } 400 END 401 6. Acknowledgments 403 This document has been produced by the University of Twente 404 (The Netherlands), together with ESYS Limited (The United Kingdom), 405 as part of a `proof of concept' study for the `Centre of Earth 406 Observation' (CEO) of the `Joint Research Centre' (JRC) of the 407 European Community. This document has benefited greatly to the 408 comments of: 410 Mark Gamble 411 413 Rui Meneses 414 416 Juergen Schoenwaelder 417 418 7. References 420 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 421 S. Waldbusser, "Structure of Management Information for version 2 422 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 423 January 1996. 425 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 426 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 427 RFC 1213, Hughes LAN Systems, Performance Systems International, 428 March 1991. 430 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 431 S. Waldbusser, "Textual Conventions for version 2 of the Simple 432 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 434 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 435 S. Waldbusser, "Protocol Operations for version 2 of the Simple 436 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 438 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 439 S. Waldbusser, "Conformance Statements for version 2 of the Simple 440 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 442 [6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 443 Management Protocol", RFC 1157, SNMP Research, Performance Systems 444 International, MIT Laboratory for Computer Science, May 1990. 446 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 447 S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 448 January 1996. 450 8. Security Considerations 452 Security issues are not discussed in this memo. 454 9. Authors' Addresses 456 Harrie Hazewinkel / Eric van Hengstum / Aiko Pras 457 University of Twente 458 Centre for Telematics and Information Technology (CTIT) 459 POBox 217 460 7500 AE Enschede, The Netherlands 461 Phone: +31-53-4893778 462 Email: hazewink@cs.utwente.nl 463 hengstum@cs.utwente.nl 464 pras@cs.utwente.nl 466 Table of Contents 468 1 Abstract .................................................. 2 469 2 The SNMPv2 Network Management Framework ................... 3 470 2.1 Object Definitions ...................................... 3 471 3 Introduction .............................................. 4 472 4 Retrieval Service MIB structure ........................... 5 473 4.1 Statistics group ........................................ 5 474 4.2 Quality of Service group ................................ 5 475 5 Retrieval Service MIB definition .......................... 6 476 6 Acknowledgements .......................................... 11 477 7 References ................................................ 12 478 8 Security Considerations ................................... 12 479 9 Authors' Addresses ........................................ 12