[rfc-dist] RFC 5676 on Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications

[rfc-editor at rfc-editor.org ([e-mail])]

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

        
        RFC 5676

        Title:      Definitions of Managed Objects for 
                    Mapping SYSLOG Messages to Simple Network 
                    Management Protocol (SNMP) Notifications 
        Author:     J. Schoenwaelder, A. Clemm,
                    A. Karmakar
        Status:     Standards Track
        Date:       October 2009
        Mailbox:    j.schoenwaelder at jacobs-university.de, 
                    alex at cisco.com, 
                    akarmaka at cisco.com
        Pages:      22
        Characters: 43160
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-syslog-msg-mib-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5676.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 defines a mapping of SYSLOG messages to Simple
Network Management Protocol (SNMP) notifications.  [STANDARDS TRACK]

This document is a product of the Operations and Management Area Working Group Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute