draft-ietf-netmod-syslog-model-07.txt   draft-ietf-netmod-syslog-model-08.txt 
NETMOD WG C. Wildes, Ed. NETMOD WG C. Wildes, Ed.
Internet-Draft K. Koushik, Ed. Internet-Draft K. Koushik, Ed.
Intended status: Standards Track Cisco Systems Inc. Intended status: Standards Track Cisco Systems Inc.
Expires: September 21, 2016 March 20, 2016 Expires: November 11, 2016 May 10, 2016
SYSLOG YANG Model SYSLOG YANG Model
draft-ietf-netmod-syslog-model-07 draft-ietf-netmod-syslog-model-08
Abstract Abstract
This document describes a data model for the Syslog protocol which is This document describes a data model for the Syslog protocol which is
used to convey event notification messages. used to convey event notification messages.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 21, 2016. This Internet-Draft will expire on November 11, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 11 skipping to change at page 2, line 11
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
3. Design of the SYSLOG Model . . . . . . . . . . . . . . . . . 3 3. Design of the SYSLOG Model . . . . . . . . . . . . . . . . . 3
3.1. SYSLOG Module . . . . . . . . . . . . . . . . . . . . . . 6 3.1. SYSLOG Module . . . . . . . . . . . . . . . . . . . . . . 5
4. SYSLOG YANG Models . . . . . . . . . . . . . . . . . . . . . 9 4. SYSLOG YANG Models . . . . . . . . . . . . . . . . . . . . . 9
4.1. SYSLOG-TYPES Module . . . . . . . . . . . . . . . . . . . 9 4.1. SYSLOG-TYPES Module . . . . . . . . . . . . . . . . . . . 9
4.2. Syslog Module . . . . . . . . . . . . . . . . . . . . . . 15 4.2. Syslog Module . . . . . . . . . . . . . . . . . . . . . . 14
4.3. A Syslog Example . . . . . . . . . . . . . . . . . . . . 29 4.3. A Syslog Example . . . . . . . . . . . . . . . . . . . . 29
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
7. Security Considerations . . . . . . . . . . . . . . . . . . . 32 7. Security Considerations . . . . . . . . . . . . . . . . . . . 31
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1. Normative References . . . . . . . . . . . . . . . . . . 32 8.1. Normative References . . . . . . . . . . . . . . . . . . 32
8.2. Informative References . . . . . . . . . . . . . . . . . 33 8.2. Informative References . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Appendix A. Implementor Guidelines . . . . . . . . . . . . . . . 33
A.1. Extending Facilities . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
Operating systems, processes and applications generate messages Operating systems, processes and applications generate messages
indicating their own status or the occurrence of events. These indicating their own status or the occurrence of events. These
messages are useful for managing and/or debugging the network and its messages are useful for managing and/or debugging the network and its
services. The BSD Syslog protocol is a widely adopted protocol that services. The BSD Syslog protocol is a widely adopted protocol that
is used for transmission and processing of the messages. is used for transmission and processing of the messages.
Since each process, application and operating system was written Since each process, application and operating system was written
skipping to change at page 2, line 48 skipping to change at page 2, line 50
Essentially, a Syslog process receives messages (from the kernel, Essentially, a Syslog process receives messages (from the kernel,
processes, applications or other Syslog processes) and processes processes, applications or other Syslog processes) and processes
those. The processing involves logging to a local file, displaying those. The processing involves logging to a local file, displaying
on console, user terminal, and/or relaying to syslog processes on on console, user terminal, and/or relaying to syslog processes on
other machines. The processing is determined by the "facility" that other machines. The processing is determined by the "facility" that
originated the message and the "severity" assigned to the message by originated the message and the "severity" assigned to the message by
the facility. the facility.
We are using definitions of Syslog protocol from [RFC5424] in this We are using definitions of Syslog protocol from [RFC5424] in this
draft. RFC.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Problem Statement 2. Problem Statement
This document defines a YANG [RFC6020] configuration data model that This document defines a YANG [RFC6020] configuration data model that
skipping to change at page 3, line 36 skipping to change at page 3, line 36
3. Design of the SYSLOG Model 3. Design of the SYSLOG Model
The syslog model was designed by comparing various syslog features The syslog model was designed by comparing various syslog features
implemented by various vendors' in different implementations. implemented by various vendors' in different implementations.
This draft addresses the common leafs between implementations and This draft addresses the common leafs between implementations and
creates a common model, which can be augmented with proprietary creates a common model, which can be augmented with proprietary
features, if necessary. The base model is designed to be very simple features, if necessary. The base model is designed to be very simple
for maximum flexibility. for maximum flexibility.
Many vendors extend the list of facilities available for logging in
their implementation. Here is an example that shows how additional
facilities could be added to the list of available facilities (in
this case two facilities are added):
module vendor-syslog-types {
namespace "urn:vendor:params:xml:ns:yang:vendor-syslog-types";
prefix vendor-syslogtypes;
import ietf-syslog-types {
prefix syslogtypes;
}
organization "Vendor, Inc.";
contact
"Vendor, Inc.
Customer Service
E-mail: syslog-yang@vendor.com";
description
"This module contains a collection of vendor-sprecific YANG type
definitions for SYSLOG.";
revision 2016-03-20 {
description
"Version 1.0";
reference
"Vendor SYSLOG Types: SYSLOG YANG Model";
}
identity vendor_specific_type_1 {
base syslogtypes:syslog-facility;
}
identity vendor_specific_type_2 {
base syslogtypes:syslog-facility;
}
}
Syslog consists of message originators, and message distributors. Syslog consists of message originators, and message distributors.
The following digram shows syslog messages flowing from a message The following digram shows syslog messages flowing from a message
originator, to message distributors where suppression filtering can originator, to message distributors where suppression filtering can
take place. take place.
Many vendors extend the list of facilities available for logging in
their implementation. An example is included in Extending Facilities
(Appendix A.1).
Message Originators Message Originators
+-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+
| Various | | OS | | | | Remote | | Various | | OS | | | | Remote |
| Components | | Kernel | | Line Cards | | Servers | | Components | | Kernel | | Line Cards | | Servers |
+-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+
+-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+
| SNMP | | Interface | | Standby | | Syslog | | SNMP | | Interface | | Standby | | Syslog |
| Events | | Events | | Supervisor | | Itself | | Events | | Events | | Supervisor | | Itself |
+-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+
skipping to change at page 5, line 27 skipping to change at page 4, line 27
+----------------------------------------------------------------+ +----------------------------------------------------------------+
| |
| |
| |
| |
+-----------+------------+--------------+ +-----------+------------+--------------+
| | | | | | | |
v v v | v v v |
Message Distributors | Message Distributors |
+----------+ +----------+ +----------+ | +----------+ +----------+ +----------+ |
| | | Log | | Log | | | | | Log | | Log | |
| Console | | Buffer(s)| | File(s) | | | Console | | Buffer | | File(s) | |
+----------+ +----------+ +----------+ | +----------+ +----------+ +----------+ |
| |
+-------------+-------------+ +-------------+-------------+
| | | | | |
v v v v v v
+----------------+ +-----------+ +-----------+ +----------------+ +-----------+ +-----------+
|Remote Relay(s)/| | | |User | |Remote Relay(s)/| | | |User |
|Collectors(s) | |Terminal(s)| |Sessions(s)| |Collectors(s) | |Terminal(s)| |Sessions(s)|
+----------------+ +-----------+ +-----------+ +----------------+ +-----------+ +-----------+
The leaves in the base syslog model log-input-transports container
correspond to remote message originators or remote message relays.
The leaves in the base syslog model log-actions container correspond The leaves in the base syslog model log-actions container correspond
to each message distributor: to each message distributor:
console console
log buffer(s) log buffer
log file(s) log file(s)
remote relay(s)/collector(s) remote relay(s)/collector(s)
terminal(s) terminal(s)
user session(s). user session(s).
Optional features are used to specified functionality that is present Optional features are used to specified functionality that is present
in specific vendor configurations. in specific vendor configurations.
3.1. SYSLOG Module 3.1. SYSLOG Module
skipping to change at page 6, line 52 skipping to change at page 6, line 7
<type> is the name of the type for leafs and leaf-lists <type> is the name of the type for leafs and leaf-lists
If the type is a leafref, the type is printed as "-> TARGET", where If the type is a leafref, the type is printed as "-> TARGET", where
TARGET is either the leafref path, with prefixed removed if possible. TARGET is either the leafref path, with prefixed removed if possible.
<if-features> is the list of features this node depends on, printed <if-features> is the list of features this node depends on, printed
within curly brackets and a question mark "{...}?" within curly brackets and a question mark "{...}?"
module: ietf-syslog module: ietf-syslog
+--rw syslog +--rw syslog
+--rw log-input-transports {syslog-relay}?
| +--rw receiver* [name]
| +--rw name string
| +--rw (transport)
| | +--:(tcp)
| | | +--rw tcp
| | | +--rw address? inet:host
| | | +--rw port? inet:port-number
| | +--:(udp)
| | | +--rw udp
| | | +--rw address? inet:host
| | | +--rw port? inet:port-number
| | +--:(tls)
| | +--rw tls
| | +--rw address? inet:host
| | +--rw port? inet:port-number
| +--rw structured-data? boolean {structured-data}?
| +--rw syslog-sign! {signed-messages}?
+--rw log-actions +--rw log-actions
+--rw console! {console-action}? +--rw console!
| +--rw log-selector | +--rw log-selector
| +--rw (selector-facility) | +--rw (selector-facility)
| | +--:(no-log-facility) | | +--:(no-log-facility)
| | | +--rw no-facilities? empty | | | +--rw no-facilities? empty
| | +--:(log-facility) | | +--:(log-facility)
| | +--rw log-facility* [facility] | | +--rw log-facility* [facility]
| | +--rw facility union | | +--rw facility union
| | +--rw severity union | | +--rw severity union
| | +--rw severity-operator? enumeration {selector-sevop-config}? | | +--rw compare-op? enumeration {select-sev-compare}?
| +--rw pattern-match? string {selector-match-config}? | +--rw pattern-match? string {select-match}?
+--rw buffer {buffer-action}? +--rw buffer
| +--rw log-buffer* [name] | +--rw log-selector
| +--rw name string | | +--rw (selector-facility)
| +--rw log-selector | | | +--:(no-log-facility)
| | +--rw (selector-facility) | | | | +--rw no-facilities? empty
| | | +--:(no-log-facility) | | | +--:(log-facility)
| | | | +--rw no-facilities? empty | | | +--rw log-facility* [facility]
| | | +--:(log-facility) | | | +--rw facility union
| | | +--rw log-facility* [facility] | | | +--rw severity union
| | | +--rw facility union | | | +--rw compare-op? enumeration {select-sev-compare}?
| | | +--rw severity union | | +--rw pattern-match? string {select-match}?
| | | +--rw severity-operator? enumeration {selector-sevop-config}? | +--rw buffer-size-bytes? uint64 {buffer-limit-bytes}?
| | +--rw pattern-match? string {selector-match-config}? | +--rw structured-data? boolean {structured-data}?
| +--rw buffer-size-bytes? uint64 {buffer-limit-bytes}?
| +--rw buffer-size-messages? uint64 {buffer-limit-messages}?
| +--rw structured-data? boolean {structured-data-config}?
+--rw file +--rw file
| +--rw log-file* [name] | +--rw log-file* [name]
| +--rw name inet:uri | +--rw name inet:uri
| +--rw log-selector | +--rw log-selector
| | +--rw (selector-facility) | | +--rw (selector-facility)
| | | +--:(no-log-facility) | | | +--:(no-log-facility)
| | | | +--rw no-facilities? empty | | | | +--rw no-facilities? empty
| | | +--:(log-facility) | | | +--:(log-facility)
| | | +--rw log-facility* [facility] | | | +--rw log-facility* [facility]
| | | +--rw facility union | | | +--rw facility union
| | | +--rw severity union | | | +--rw severity union
| | | +--rw severity-operator? enumeration {selector-sevop-config}? | | | +--rw compare-op? enumeration {select-sev-compare}?
| | +--rw pattern-match? string {selector-match-config}? | | +--rw pattern-match? string {select-match}?
| +--rw structured-data? boolean {structured-data-config}? | +--rw structured-data? boolean {structured-data}?
| +--rw file-archive | +--rw file-archive
| +--rw number-of-files? uint32 {file-limit-size}? | +--rw number-of-files? uint32 {file-limit-size}?
| +--rw max-file-size? uint64 {file-limit-size}? | +--rw max-file-size? uint64 {file-limit-size}?
| +--rw rollover? uint32 {file-limit-duration}? | +--rw rollover? uint32 {file-limit-duration}?
| +--rw retention? uint16 {file-limit-duration}? | +--rw retention? uint16 {file-limit-duration}?
+--rw remote +--rw remote
| +--rw destination* [name] | +--rw destination* [name]
| +--rw name string | +--rw name string
| +--rw (transport) | +--rw (transport)
| | +--:(tcp) | | +--:(tcp)
skipping to change at page 8, line 24 skipping to change at page 7, line 42
| | +--:(tls) | | +--:(tls)
| | +--rw tls | | +--rw tls
| | +--rw address? inet:host | | +--rw address? inet:host
| | +--rw port? inet:port-number | | +--rw port? inet:port-number
| +--rw log-selector | +--rw log-selector
| | +--rw (selector-facility) | | +--rw (selector-facility)
| | | +--:(no-log-facility) | | | +--:(no-log-facility)
| | | | +--rw no-facilities? empty | | | | +--rw no-facilities? empty
| | | +--:(log-facility) | | | +--:(log-facility)
| | | +--rw log-facility* [facility] | | | +--rw log-facility* [facility]
| | | +--rw facility union | | | +--rw facility union
| | | +--rw severity union | | | +--rw severity union
| | | +--rw severity-operator? enumeration {selector-sevop-config}? | | | +--rw compare-op? enumeration {select-sev-compare}?
| | +--rw pattern-match? string {selector-match-config}? | | +--rw pattern-match? string {select-match}?
| +--rw destination-facility? identityref | +--rw destination-facility? identityref
| +--rw source-interface? if:interface-ref | +--rw source-interface? if:interface-ref
| +--rw structured-data? boolean {structured-data-config}? | +--rw structured-data? boolean {structured-data}?
| +--rw syslog-sign! {signed-messages-config}? | +--rw syslog-sign! {signed-messages}?
| +--rw cert-initial-repeat uint16 | +--rw cert-initial-repeat uint16
| +--rw cert-resend-delay uint16 | +--rw cert-resend-delay uint16
| +--rw cert-resend-count uint16 | +--rw cert-resend-count uint16
| +--rw sig-max-delay uint16 | +--rw sig-max-delay uint16
| +--rw sig-number-resends uint16 | +--rw sig-number-resends uint16
| +--rw sig-resend-delay uint16 | +--rw sig-resend-delay uint16
| +--rw sig-resend-count uint16 | +--rw sig-resend-count uint16
+--rw terminal {terminal-action}? +--rw terminal
| +--rw all-terminals! | +--rw all-terminals!
| | +--rw log-selector | | +--rw log-selector
| | +--rw (selector-facility) | | +--rw (selector-facility)
| | | +--:(no-log-facility) | | | +--:(no-log-facility)
| | | | +--rw no-facilities? empty | | | | +--rw no-facilities? empty
| | | +--:(log-facility) | | | +--:(log-facility)
| | | +--rw log-facility* [facility] | | | +--rw log-facility* [facility]
| | | +--rw facility union | | | +--rw facility union
| | | +--rw severity union | | | +--rw severity union
| | | +--rw severity-operator? enumeration {selector-sevop-config}? | | | +--rw compare-op? enumeration {select-sev-compare}?
| | +--rw pattern-match? string {selector-match-config}? | | +--rw pattern-match? string {select-match}?
| +--rw terminal* [name] {terminal-facility-user-logging-config}? | +--rw terminal* [name] {terminal-facility-device-logging}?
| +--rw name string | +--rw name string
| +--rw log-selector | +--rw log-selector
| +--rw (selector-facility) | +--rw (selector-facility)
| | +--:(no-log-facility) | | +--:(no-log-facility)
| | | +--rw no-facilities? empty | | | +--rw no-facilities? empty
| | +--:(log-facility) | | +--:(log-facility)
| | +--rw log-facility* [facility] | | +--rw log-facility* [facility]
| | +--rw facility union | | +--rw facility union
| | +--rw severity union | | +--rw severity union
| | +--rw severity-operator? enumeration {selector-sevop-config}? | | +--rw compare-op? enumeration {select-sev-compare}?
| +--rw pattern-match? string {selector-match-config}? | +--rw pattern-match? string {select-match}?
+--rw session {session-action}? +--rw session
+--rw all-users! +--rw all-users!
| +--rw log-selector | +--rw log-selector
| +--rw (selector-facility) | +--rw (selector-facility)
| | +--:(no-log-facility) | | +--:(no-log-facility)
| | | +--rw no-facilities? empty | | | +--rw no-facilities? empty
| | +--:(log-facility) | | +--:(log-facility)
| | +--rw log-facility* [facility] | | +--rw log-facility* [facility]
| | +--rw facility union | | +--rw facility union
| | +--rw severity union | | +--rw severity union
| | +--rw severity-operator? enumeration {selector-sevop-config}? | | +--rw compare-op? enumeration {select-sev-compare}?
| +--rw pattern-match? string {selector-match-config}? | +--rw pattern-match? string {select-match}?
+--rw user* [name] {session-facility-user-logging-config}? +--rw user* [name] {session-facility-user-logging}?
+--rw name string +--rw name string
+--rw log-selector +--rw log-selector
+--rw (selector-facility) +--rw (selector-facility)
| +--:(no-log-facility) | +--:(no-log-facility)
| | +--rw no-facilities? empty | | +--rw no-facilities? empty
| +--:(log-facility) | +--:(log-facility)
| +--rw log-facility* [facility] | +--rw log-facility* [facility]
| +--rw facility union | +--rw facility union
| +--rw severity union | +--rw severity union
| +--rw severity-operator? enumeration {selector-sevop-config}? | +--rw compare-op? enumeration {select-sev-compare}?
+--rw pattern-match? string {selector-match-config}? +--rw pattern-match? string {select-match}?
4. SYSLOG YANG Models 4. SYSLOG YANG Models
4.1. SYSLOG-TYPES Module 4.1. SYSLOG-TYPES Module
<CODE BEGINS> file "ietf-syslog-types.yang" <CODE BEGINS> file "ietf-syslog-types.yang"
module ietf-syslog-types { module ietf-syslog-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-syslog-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-syslog-types";
prefix syslogtypes; prefix syslogtypes;
skipping to change at page 10, line 25 skipping to change at page 9, line 43
Editor: Kiran Agrahara Sreenivasa Editor: Kiran Agrahara Sreenivasa
<mailto:kkoushik@cisco.com> <mailto:kkoushik@cisco.com>
Editor: Clyde Wildes Editor: Clyde Wildes
<mailto:cwildes@cisco.com>"; <mailto:cwildes@cisco.com>";
description description
"This module contains a collection of YANG type definitions for "This module contains a collection of YANG type definitions for
SYSLOG. SYSLOG.
Copyright (c) 2015 IETF Trust and the persons identified as Copyright (c) 2016 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and
'OPTIONAL' in the module text are to be interpreted as described 'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119). in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices."; full legal notices.";
reference reference
skipping to change at page 10, line 47 skipping to change at page 10, line 16
'OPTIONAL' in the module text are to be interpreted as described 'OPTIONAL' in the module text are to be interpreted as described
in RFC 2119 (http://tools.ietf.org/html/rfc2119). in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(http://tools.ietf.org/html/rfcXXXX); see the RFC itself for (http://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices."; full legal notices.";
reference reference
"RFC 5424: The Syslog Protocol"; "RFC 5424: The Syslog Protocol";
revision 2016-03-20{ revision 2016-05-10 {
description description
"Initial Revision"; "Initial Revision";
reference reference
"RFC XXXX: SYSLOG YANG Model"; "RFC XXXX: SYSLOG YANG Model";
} }
typedef severity { typedef severity {
type enumeration { type enumeration {
enum "emergency" { enum "emergency" {
value 0; value 0;
description description
"Emergency Level Msg"; "Emergency Level Msg";
} }
enum "alert" { enum "alert" {
skipping to change at page 31, line 14 skipping to change at page 30, line 34
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/> <ok/>
</rpc-reply> </rpc-reply>
5. Acknowledgements 5. Acknowledgements
The authors wish to thank the following who commented on versions 01 The authors wish to thank the following who commented on versions 01
through 06 of this proposal: through 06 of this proposal:
Martin Bjorklund <mbjorklu@cisco.com> Martin Bjorklund
Jim Gibson <gibson@cisco.com> Jim Gibson
Jeffrey Haas <jhaas@pfrc.org> Jeffrey Haas
John Heasley <heas@shrubbery.net> John Heasley
Giles Heron <giheron@cisco.com> Giles Heron
Lisa Huang <yihuan@cisco.com> Lisa Huang
Jeffrey K Lange <jeffrey.K.lange@ge.com> Mahesh Jethanandani
Jan Lindblad <jlindbla@cisco.com> Jeffrey K Lange
Chris Lonvick <lonvick@gmail.com> Jan Lindblad
Tom Petch <ietfc@btconnect.com> Chris Lonvick
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tom Petch
Jason Sterne <jason.sterne@alcatel-lucent.com> Juergen Schoenwaelder
Peter Van Horne <petervh@cisco.com> Jason Sterne
Bert Wijnen <bertietf@bwijnen.net> Peter Van Horne
Aleksandr Zhdankin <azhdanki@cisco.com> Bert Wijnen
Aleksandr Zhdankin
6. IANA Considerations 6. IANA Considerations
This document registers two URIs in the IETF XML registry [RFC3688]. This document registers two URIs in the IETF XML registry [RFC3688].
Following the format in RFC 3688, the following registration is Following the format in RFC 3688, the following registration is
requested to be made: requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-syslog-types URI: urn:ietf:params:xml:ns:yang:ietf-syslog-types
skipping to change at page 32, line 18 skipping to change at page 31, line 40
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names This document registers a YANG module in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-syslog namespace: urn:ietf:params:xml:ns:yang:ietf-syslog name: ietf-syslog namespace: urn:ietf:params:xml:ns:yang:ietf-syslog
prefix: ietf-syslog reference: RFC XXXX prefix: ietf-syslog
reference: RFC XXXX
7. Security Considerations 7. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The NETCONF access control model transport is SSH [RFC6242]. The NETCONF access control model
[RFC6536] provides the means to restrict access for particular [RFC6536] provides the means to restrict access for particular
NETCONF users to a pre-configured subset of all available NETCONF NETCONF users to a pre-configured subset of all available NETCONF
protocol operations and content. protocol operations and content.
skipping to change at page 33, line 42 skipping to change at page 33, line 16
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
Appendix A. Implementor Guidelines
A.1. Extending Facilities
Many vendors extend the list of facilities available for logging in
their implementation. Here is an example that shows how additional
facilities could be added to the list of available facilities (in
this case two facilities are added):
module vendor-syslog-types-example {
namespace "urn:vendor:params:xml:ns:yang:vendor-syslog-types";
prefix vendor-syslogtypes;
import ietf-syslog-types {
prefix syslogtypes;
}
organization "Vendor, Inc.";
contact
"Vendor, Inc.
Customer Service
E-mail: syslog-yang@vendor.com";
description
"This module contains a collection of vendor-sprecific YANG type
definitions for SYSLOG.";
revision 2016-03-20 {
description
"Version 1.0";
reference
"Vendor SYSLOG Types: SYSLOG YANG Model";
}
identity vendor_specific_type_1 {
base syslogtypes:syslog-facility;
}
identity vendor_specific_type_2 {
base syslogtypes:syslog-facility;
}
}
Authors' Addresses Authors' Addresses
Clyde Wildes (editor) Clyde Wildes (editor)
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Phone: +1 408 527-2672 Phone: +1 408 527-2672
Email: cwildes@cisco.com Email: cwildes@cisco.com
 End of changes. 32 change blocks. 
124 lines changed or deleted 153 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/