Syslog Management Information Base
draft-tsuno-syslog-mib-05

Document Type Active Internet-Draft (individual)
Last updated 2017-10-17
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         H. Tsunoda
Internet-Draft                            Tohoku Institute of Technology
Intended status: Standards Track                                G. Keeni
Expires: April 21, 2018                             Cyber Solutions Inc.
                                                        October 18, 2017

                   Syslog Management Information Base
                     draft-tsuno-syslog-mib-05.txt

Abstract

   This memo defines a portion of the Management Information Base (MIB),
   the SYSLOG-MIB, for use with network management protocols in the
   Internet community.  In particular, the SYSLOG-MIB will be used to
   monitor and control syslog applications.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 21, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.

Tsunoda & Keeni          Expires April 21, 2018                 [Page 1]
Internet-Draft                  syslogMIB                   October 2017

Table of Contents

   1.  The Internet-Standard Management Framework  . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Managing syslog . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  The MIB Design  . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  The Syslog MIB  . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  34
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  37
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  37
   9.  APPENDIX  . . . . . . . . . . . . . . . . . . . . . . . . . .  37
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  38
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  38
     10.2.  Informative References . . . . . . . . . . . . . . . . .  39
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  39

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).

   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

2.  Background

   Operating systems, processes and applications, collectively termed
   "facilities" in the following, generate messages indicating their own
   status or the occurrence of events.  These messages are handled by
   what has come to be known as the syslog application [RFC5424].  A
   syslog application sends and/or receives syslog messages.  The reader
   is referred to [RFC5424] for a description of the various roles of a
   syslog application viz. "sender", "receiver" and "relay".  The
   discussion in this document, in general, applies to a generic syslog

Tsunoda & Keeni          Expires April 21, 2018                 [Page 2]
Internet-Draft                  syslogMIB                   October 2017

   application.  For special cases the specific role of the syslog
Show full document text