--- 1/draft-ietf-netmod-syslog-model-22.txt 2018-03-01 08:14:09.517887978 -0800 +++ 2/draft-ietf-netmod-syslog-model-23.txt 2018-03-01 08:14:09.593889776 -0800 @@ -1,19 +1,19 @@ NETMOD WG C. Wildes, Ed. Internet-Draft Cisco Systems Inc. Intended status: Standards Track K. Koushik, Ed. -Expires: August 25, 2018 Verizon Wireless - February 21, 2018 +Expires: September 2, 2018 Verizon Wireless + March 01, 2018 A YANG Data Model for Syslog Configuration - draft-ietf-netmod-syslog-model-22 + draft-ietf-netmod-syslog-model-23 Abstract This document defines a YANG data model for the configuration of a syslog process. It is intended this model be used by vendors who implement syslog in their systems. The YANG model in this document conforms to the Network Management Datastore Architecture defined in [draft-ietf-netmod-revised- datastores]. @@ -26,21 +26,21 @@ 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 https://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 August 25, 2018. + This Internet-Draft will expire on September 2, 2018. Copyright Notice Copyright (c) 2018 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -49,21 +49,21 @@ 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 . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.3. NDMA Compliance . . . . . . . . . . . . . . . . . . . . . 3 - 1.4. Editorial Note (To be removed by RFC) Editor) . . . . . . 3 + 1.4. Editorial Note (To be removed by RFC Editor) . . . . . . 3 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4 3. Design of the Syslog Model . . . . . . . . . . . . . . . . . 4 3.1. Syslog Module . . . . . . . . . . . . . . . . . . . . . . 6 4. Syslog YANG Module . . . . . . . . . . . . . . . . . . . . . 8 4.1. The ietf-syslog Module . . . . . . . . . . . . . . . . . 8 5. Usage Examples . . . . . . . . . . . . . . . . . . . . . . . 27 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 28 7.2. The YANG Module Names Registry . . . . . . . . . . . . . 28 @@ -123,40 +123,40 @@ The term "action" refers to the processing that takes place for each syslog message received. 1.3. NDMA Compliance The YANG model in this document conforms to the Network Management Datastore Architecture defined in I-D.ietf-netmod-revised-datastores [I-D.ietf-netmod-revised-datastores]. -1.4. Editorial Note (To be removed by RFC) Editor) +1.4. Editorial Note (To be removed by RFC Editor) This document contains many placeholder values that need to be replaced with finalized values at the time of publication. This note summarizes all of the substitutions that are needed. No other RFC Editor instructions are specified elsewhere in this document. Artwork in this document contains shorthand references to drafts in progress. Please apply the following replacements: o "I-D.ietf-netconf-keystore" --> the assigned RFC value for draft- ietf-netconf-keystore o "I-D.ietf-netconf-tls-client-server" --> the assigned RFC value for draft-ietf-netconf-tls-client-server o "zzzz" --> the assigned RFC value for this draft - o draft-ietf-netmod-revised-datastores --> the assigned RFC value - for I-D.ietf-netmod-revised-datastores + o I-D.ietf-netmod-revised-datastores --> the assigned RFC value for + draft-ietf-netmod-revised-datastores 2. Problem Statement This document defines a YANG [RFC7950] configuration data model that may be used to configure the syslog feature running on a system. YANG models can be used with network management protocols such as NETCONF [RFC6241] to install, manipulate, and delete the configuration of network devices. The data model makes use of the YANG "feature" construct which allows @@ -363,21 +363,21 @@ 4. Syslog YANG Module 4.1. The ietf-syslog Module This module imports typedefs from [RFC7223], groupings from [I-D.ietf-netconf-keystore], and [I-D.ietf-netconf-tls-client-server], and it references [RFC5424], [RFC5425], [RFC5426], and [RFC5848] and [Std-1003.1-2008]. - file "ietf-syslog@2018-02-21.yang" + file "ietf-syslog@2018-03-01.yang" module ietf-syslog { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-syslog"; prefix syslog; import ietf-inet-types { prefix inet; reference "RFC 6991: INET Types Model"; @@ -431,21 +431,21 @@ The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in the module text are to be interpreted as described in RFC 2119 (http://tools.ietf.org/html/rfc2119). This version of this YANG module is part of RFC zzzz (http://tools.ietf.org/html/rfczzzz); see the RFC itself for full legal notices."; - revision 2018-02-21 { + revision 2018-03-01 { description "Initial Revision"; reference "RFC zzzz: Syslog YANG Model"; } feature console-action { description "This feature indicates that the local console action is supported."; @@ -1233,44 +1233,43 @@ } Figure 3. ietf-syslog Module 5. Usage Examples Requirement: Enable console logging of syslogs of severity critical - Here is the example syslog configuration xml: all critical Enable remote logging of syslogs to udp destination - 2001:db8:a0b:12f0::1 for facility auth, severity error + foo.example.com for facility auth, severity error remote1 -
2001:db8:a0b:12f0::1
+
foo.example.com
 auth error