A YANG Data Model for Syslog Configuration
draft-ietf-netmod-syslog-model-15

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15

draft-ietf-netmod-syslog-model-15.txt:
xym 0.3.2:
Extracting 'ietf-syslog.yang'
Extracting 'vendor-syslog-types-example'


ietf-syslog.yang:
pyang 1.7.2: pyang --verbose --ietf -p {libs} {model}:
/a/www/ietf-ftp/yang/draftmod/ietf-netconf-acm@2017-05-29.yang:1: error: unexpected latest revision "2017-06-27" in /a/www/ietf-ftp/yang/draftmod/ietf-netconf-acm@2017-05-29.yang, should be 2017-05-29

yanglint 0.12.183: yanglint --verbose -p {rfclib} -p {draftlib} {model}:
No validation errors

NETMOD WG                                                 C. Wildes, Ed.
Internet-Draft                                        Cisco Systems Inc.
Intended status: Standards Track                         K. Koushik, Ed.
Expires: December 07, 2017                              Verizon Wireless
                                                           June 07, 2017

               A YANG Data Model for Syslog Configuration
                   draft-ietf-netmod-syslog-model-15

Abstract

   This document describes a data model for the configuration of syslog.

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 December 07, 2017.

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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  2
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Problem Statement  . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Design of the Syslog Model . . . . . . . . . . . . . . . . . .  3
     3.1.  Syslog Module  . . . . . . . . . . . . . . . . . . . . . .  5

Wildes & Koushik       Expires December 07, 2017                [Page 1]
Internet-Draft             Syslog Management                   June 2017

   4.  Syslog YANG Module . . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  The ietf-syslog Module . . . . . . . . . . . . . . . . . .  7
   5.  Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . 23
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 25
     8.1.  Resource Constraints . . . . . . . . . . . . . . . . . . . 26
     8.2.  Inappropriate Configuration  . . . . . . . . . . . . . . . 26
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 26
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 27
   Appendix A. Implementor Guidelines . . . . . . . . . . . . . . . . 27
     Appendix A.1.  Extending Facilities  . . . . . . . . . . . . . . 27
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28

1.  Introduction

   Operating systems, processes and applications generate messages
   indicating their own status or the occurrence of events.  These
   messages are useful for managing and/or debugging the network and its
   services.  The BSD syslog protocol is a widely adopted protocol that
   is used for transmission and processing of the messages.

   Since each process, application and operating system was written
   somewhat independently, there is little uniformity to the content of
   syslog messages.  For this reason, no assumption is made upon the
   formatting or contents of the messages.  The protocol is simply
   designed to transport these event messages.  No acknowledgement of
   the receipt is made.

   Essentially, a syslog process receives messages (from the kernel,
   processes, applications or other syslog processes) and processes
   those.  The processing involves logging to a local file, displaying
   on console, and/or relaying to syslog processes on other machines.
   The processing is determined by the "facility" that originated the
   message and the "severity" assigned to the message by the facility.

   We are using definitions of syslog protocol from RFC5424 [RFC5424] in