Fwd: RFC 3433 on Entity Sensor Management Information Base

FYI -- Our newest RFC!

Thanks to the everyone who worked on this -- especially
Andy, Dan and KC.

Margaret


>To: IETF-Announce
>From: [email protected]
>Date: Fri, 20 Dec 2002 16:40:04 -0800
>Subject: [Entmib] RFC 3433 on Entity Sensor Management Information Base
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 3433
>
>         Title:      Entity Sensor Management Information Base
>         Author(s):  A. Bierman, D. Romascanu, K.C. Norseth
>         Status:     Standards Track
>         Date:       December 2002
>         Mailbox:    [email protected], [email protected],
>                     [email protected]
>         Pages:      17
>         Characters: 31857
>         Updates/Obsoletes/See Also:   None
>
>         I-D Tag:    draft-ietf-entmib-sensor-mib-02.txt
>
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3433.txt
>
>
>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 managed objects for extending the Entity
>MIB (RFC 2737) to provide generalized access to information related to
>physical sensors, which are often found in networking equipment (such
>as chassis temperature, fan RPM, power supply voltage).
>
>This document is a product of the Entity MIB Working Group of the
>IETF.
>
>This is now a Proposed Standard Protocol.
>
>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.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to [email protected].  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to [email protected].
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to [email protected] with the message body
>help: ways_to_get_rfcs.  For example:
>
>         To: [email protected]
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to [email protected].  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.echo
>Submissions for Requests for Comments should be sent to
>[email protected].  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-Type: text/plain
>Content-ID: <[email protected]>
>
>RETRIEVE: rfc
>DOC-ID: rfc3433
>
><ftp://ftp.isi.edu/in-notes/rfc3433.txt>