A new Request for Comments is now available in online RFC libraries.



        RFC 1697:

        Title:      Relational Database Management System (RDBMS)
                    Management Information Base (MIB) using SMIv2
        Author:     D. Brower, Editor, B. Purvy, RDBMSMIB Working
                    Group Chair, A. Daniel, M. Sinykin & J. Smith
        Mailbox:    daveb@ingres.com, bpurvy@us.oracle.com,
                    anthony@informix.com, msinykin@us.oracle.com, 
                    jaysmith@us.oracle.com
        Pages:      38
        Characters: 76,202
        Updates/Obsoletes:  none


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 used for managing
relational database (RDBMS) implementations.  This RFC is a product of
the Relational Database Management Systems 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 IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute