idnits 2.17.1 draft-ietf-entmib-sensor-mib-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3433 5 Title: Entity Sensor Management Information Base 6 Author(s): A. Bierman, D. Romascanu, K.C. Norseth 7 Status: Standards Track 8 Date: December 2002 9 Mailbox: abierman@cisco.com, dromasca@avaya.com, 10 kenyon.c.norseth@L-3com.com 11 Pages: 17 12 Characters: 31857 13 Updates/Obsoletes/See Also: None 15 I-D Tag: draft-ietf-entmib-sensor-mib-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3433.txt 19 This memo defines a portion of the Management Information Base (MIB) 20 for use with network management protocols in the Internet community. 21 In particular, it describes managed objects for extending the Entity 22 MIB (RFC 2737) to provide generalized access to information related to 23 physical sensors, which are often found in networking equipment (such 24 as chassis temperature, fan RPM, power supply voltage). 26 This document is a product of the Entity MIB Working Group of the 27 IETF. 29 This is now a Proposed Standard Protocol. 31 This document specifies an Internet standards track protocol for 32 the Internet community, and requests discussion and suggestions 33 for improvements. Please refer to the current edition of the 34 "Internet Official Protocol Standards" (STD 1) for the 35 standardization state and status of this protocol. Distribution 36 of this memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.