draft-ietf-netmod-syslog-model-23.txt   draft-ietf-netmod-syslog-model-24.txt 
NETMOD WG C. Wildes, Ed. NETMOD WG C. Wildes, Ed.
Internet-Draft Cisco Systems Inc. Internet-Draft Cisco Systems Inc.
Intended status: Standards Track K. Koushik, Ed. Intended status: Standards Track K. Koushik, Ed.
Expires: September 2, 2018 Verizon Wireless Expires: September 07, 2018 Verizon Wireless
March 01, 2018 March 08, 2018
A YANG Data Model for Syslog Configuration A YANG Data Model for Syslog Configuration
draft-ietf-netmod-syslog-model-23 draft-ietf-netmod-syslog-model-24
Abstract Abstract
This document defines a YANG data model for the configuration of a This document defines a YANG data model for the configuration of a
syslog process. It is intended this model be used by vendors who syslog process. It is intended this model be used by vendors who
implement syslog in their systems. implement syslog in their systems.
The YANG model in this document conforms to the Network Management The YANG model in this document conforms to the Network Management
Datastore Architecture defined in [draft-ietf-netmod-revised- Datastore Architecture defined in [draft-ietf-netmod-revised-
datastores]. datastores].
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.
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 https://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 2, 2018. This Internet-Draft will expire on September 07, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as 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 . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.3. NDMA Compliance . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4 3. Design of the Syslog Model . . . . . . . . . . . . . . . . . . 4
3. Design of the Syslog Model . . . . . . . . . . . . . . . . . 4 3.1. Syslog Module . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Syslog Module . . . . . . . . . . . . . . . . . . . . . . 6 4. Syslog YANG Module . . . . . . . . . . . . . . . . . . . . . . 7
4. Syslog YANG Module . . . . . . . . . . . . . . . . . . . . . 8 4.1. The ietf-syslog Module . . . . . . . . . . . . . . . . . . 8
4.1. The ietf-syslog Module . . . . . . . . . . . . . . . . . 8 5. Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . 25
5. Usage Examples . . . . . . . . . . . . . . . . . . . . . . . 27 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 26
7.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 28 7.2. The YANG Module Names Registry . . . . . . . . . . . . . . 26
7.2. The YANG Module Names Registry . . . . . . . . . . . . . 28 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26
8. Security Considerations . . . . . . . . . . . . . . . . . . . 28 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 9.1. Normative References . . . . . . . . . . . . . . . . . . . 27
9.1. Normative References . . . . . . . . . . . . . . . . . . 29 9.2. Informative References . . . . . . . . . . . . . . . . . . 28
9.2. Informative References . . . . . . . . . . . . . . . . . 31 Appendix A. Implementor Guidelines . . . . . . . . . . . . . . . . 29
Appendix A. Implementor Guidelines . . . . . . . . . . . . . . . 32 Appendix A.1. Extending Facilities . . . . . . . . . . . . . . 29
A.1. Extending Facilities . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
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 message. is used for transmission and processing of the message.
Since each process, application and operating system was written Since each process, application and operating system was written
somewhat independently, there is little uniformity to the content of somewhat independently, there is little uniformity to the content of
syslog messages. For this reason, no assumption is made upon the syslog messages. For this reason, no assumption is made upon the
formatting or contents of the messages. The protocol is simply formatting or contents of the messages. The protocol is simply
designed to transport these event messages. No acknowledgement of designed to transport these event messages. No acknowledgment of the
the receipt is made. receipt is made.
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
them. The processing may involve logging to a local file, and/or them. The processing may involve logging to a local file, and/or
displaying on console, and/or relaying to syslog processes on other displaying on console, and/or relaying to syslog processes on other
machines. The processing is determined by the "facility" that 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
skipping to change at page 5, line 25 skipping to change at page 5, line 4
| | | |
+----------------------------------------------------------------+ +----------------------------------------------------------------+
| |
| |
| |
| |
+-------------+--------------+ +-------------+--------------+
| | | | | |
v v v v v v
Collectors Collectors
+----------+ +----------+ +----------------+ +----------+ +----------+ +----------------+
| | | Log | |Remote Relay(s)/| | | | Log | |Remote Relay(s)/|
| Console | | File(s) | |Collector(s) | | Console | | File(s) | |Collector(s) |
+----------+ +----------+ +----------------+ +----------+ +----------+ +----------------+
Figure 1. Syslog Processing Flow Figure 1. Syslog Processing Flow
Collectors are configured using the leaves in the syslog model Collectors are configured using the leaves in the syslog model
"actions" container which correspond to each message collector: "actions" container which correspond to each message collector:
console console
log file(s) log file(s)
remote relay(s)/collector(s) remote relay(s)/collector(s)
Within each action, a selector is used to filter syslog messages. A Within each action, a selector is used to filter syslog messages. A
selector consists of a list of one or more facility-severity matches, selector consists of a list of one or more filters specified by
and, if supported via the select-match feature, an optional regular facility-severity pairs, and, if supported via the select-match
expression pattern match that is performed on the [RFC5424] field. feature, an optional regular expression pattern match that is
performed on the [RFC5424] field.
A syslog message is processed if: A syslog message is processed if:
There is an element of facility-list (F, S) where There is an element of facility-list (F, S) where
the message facility matches F the message facility matches F
and the message severity matches S and the message severity matches S
and/or the message text matches the regex pattern (if it and/or the message text matches the regex pattern (if it
is present) is present)
The facility is one of a specific syslog-facility, or all facilities. The facility is one of a specific syslog-facility, or all facilities.
The severity is one of type syslog-severity, all severities, or none. The severity is one of type syslog-severity, all severities, or none.
None is a special case that can be used to disable a filter. When None is a special case that can be used to disable a filter. When
filtering severity, the default comparison is that messages of the filtering severity, the default comparison is that messages of the
specified severity and higher are selected to be logged. This is specified severity and higher are selected to be logged. This is
shown in the model as "default equals-or-higher". This behavior can shown in the model as "default equals-or-higher". This behavior can
be altered if the select-adv-compare feature is enabled to specify a be altered if the select-adv-compare feature is enabled to specify a
compare operation and an action. Compare operations are: "equals" to compare operation and an action. Compare operations are: "equals" to
skipping to change at page 6, line 32 skipping to change at page 5, line 57
used to log the message or block the message from being logged. used to log the message or block the message from being logged.
Many vendors extend the list of facilities available for logging in Many vendors extend the list of facilities available for logging in
their implementation. An example is included in Extending Facilities their implementation. An example is included in Extending Facilities
(Appendix A.1). (Appendix A.1).
3.1. Syslog Module 3.1. Syslog Module
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. Please see [I-D.ietf-netmod-yang-tree-diagrams] for this document. Please see [I-D.ietf-netmod-yang-tree-diagrams] for
tree diagram notation. tree diagram notation, and [RFC8089] for URI notation.
module: ietf-syslog module: ietf-syslog
+--rw syslog! +--rw syslog!
+--rw actions +--rw actions
+--rw console! {console-action}? +--rw console! {console-action}?
| +--rw facility-filter | +--rw facility-filter
| | +--rw facility-list* [facility severity] | | +--rw facility-list* [facility severity]
| | +--rw facility union | | +--rw facility union
| | +--rw severity union | | +--rw severity union
| | +--rw advanced-compare {select-adv-compare}? | | +--rw advanced-compare {select-adv-compare}?
skipping to change at page 8, line 43 skipping to change at page 8, line 4
+--rw cert-resend-delay? uint32 +--rw cert-resend-delay? uint32
+--rw cert-resend-count? uint32 +--rw cert-resend-count? uint32
+--rw sig-max-delay? uint32 +--rw sig-max-delay? uint32
+--rw sig-number-resends? uint32 +--rw sig-number-resends? uint32
+--rw sig-resend-delay? uint32 +--rw sig-resend-delay? uint32
+--rw sig-resend-count? uint32 +--rw sig-resend-count? uint32
Figure 2. ietf-syslog Module Tree Figure 2. ietf-syslog Module Tree
4. Syslog YANG Module 4. Syslog YANG Module
4.1. The ietf-syslog Module 4.1. The ietf-syslog Module
This module imports typedefs from [RFC7223], groupings from This module imports typedefs from [RFC7223], groupings from
[I-D.ietf-netconf-keystore], and [I-D.ietf-netconf-keystore],
[I-D.ietf-netconf-tls-client-server], and it references [RFC5424], and [I-D.ietf-netconf-tls-client-server], and it references
[RFC5425], [RFC5426], and [RFC5848] and [Std-1003.1-2008]. [RFC5424], [RFC5425], [RFC5426], [RFC5848], and [RFC8174], and
[Std-1003.1-2008].
<CODE BEGINS> file "ietf-syslog@2018-03-01.yang" <CODE BEGINS> file "ietf-syslog@2018-03-08.yang"
module ietf-syslog { module ietf-syslog {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-syslog"; namespace "urn:ietf:params:xml:ns:yang:ietf-syslog";
prefix syslog; prefix syslog;
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: INET Types Model"; "RFC 6991: INET Types Model";
skipping to change at page 10, line 24 skipping to change at page 10, line 19
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 'OPTIONAL' in the module text are to be interpreted as
described in RFC 2119 (http://tools.ietf.org/html/rfc2119). described in RFC 2119 (http://tools.ietf.org/html/rfc2119).
This version of this YANG module is part of RFC zzzz This version of this YANG module is part of RFC zzzz
(http://tools.ietf.org/html/rfczzzz); see the RFC itself for (http://tools.ietf.org/html/rfczzzz); see the RFC itself for
full legal notices."; full legal notices.";
revision 2018-03-01 { revision 2018-03-08 {
description description
"Initial Revision"; "Initial Revision";
reference reference
"RFC zzzz: Syslog YANG Model"; "RFC zzzz: Syslog YANG Model";
} }
feature console-action { feature console-action {
description description
"This feature indicates that the local console action is "This feature indicates that the local console action is
supported."; supported.";
skipping to change at page 12, line 51 skipping to change at page 12, line 35
message."; message.";
} }
enum "debug" { enum "debug" {
value 7; value 7;
description description
"The severity level 'Debug' indicating a debug-level "The severity level 'Debug' indicating a debug-level
message."; message.";
} }
} }
description description
"The definitions for Syslog message severity."; "The definitions for Syslog message severity.
Note that a lower value is a higher severity. Comparisons of
reference equal-or-higher severity mean equal or lower numeric value";
reference
"RFC 5424: The Syslog Protocol"; "RFC 5424: The Syslog Protocol";
} }
identity syslog-facility { identity syslog-facility {
description description
"This identity is used as a base for all syslog facilities."; "This identity is used as a base for all syslog facilities.";
reference reference
"RFC 5424: The Syslog Protocol"; "RFC 5424: The Syslog Protocol";
} }
skipping to change at page 18, line 45 skipping to change at page 17, line 49
true the message will be logged."; true the message will be logged.";
} }
enum block { enum block {
description description
"This enum specifies that if the compare operation is "This enum specifies that if the compare operation is
true the message will not be logged."; true the message will not be logged.";
} }
} }
default log; default log;
description description
"The action can be used to spectify if the message should "The action can be used to specify if the message should
be logged or blocked based on the outcome of the compare be logged or blocked based on the outcome of the compare
operation."; operation.";
} }
description description
"This container describes additional severity compare "This container describes additional severity compare
operations that can be used in place of the default operations that can be used in place of the default
severity comparison. The compare leaf specifies the type of severity comparison. The compare leaf specifies the type of
the compare that is done and the action leaf specifies the the compare that is done and the action leaf specifies the
intended result. intended result.
Example: compare->equals and action->no-match means Example: compare->equals and action->no-match means
skipping to change at page 28, line 5 skipping to change at page 26, line 5
</actions> </actions>
</syslog> </syslog>
Figure 4. ietf-syslog Examples Figure 4. ietf-syslog Examples
6. Acknowledgements 6. Acknowledgements
The authors wish to thank the following who commented on this The authors wish to thank the following who commented on this
proposal: proposal:
Andy Bierman, Martin Bjorklund, Alex Campbell, Alex Clemm, Jim Andy Bierman, Martin Bjorklund, Alex Campbell, Alex Clemm, Francis
Gibson, Jeffrey Haas, John Heasley, Giles Heron, Lisa Huang, Mahesh Dupont, Jim Gibson, Jeffrey Haas, Bob Harold, John Heasley, Giles
Jethanandani, Jeffrey K Lange, Jan Lindblad, Chris Lonvick, Tom Heron, Lisa Huang, Mahesh Jethanandani, Warren Kumari, Jeffrey K
Petch, Juergen Schoenwaelder, Phil Shafer, Yaron Sheffer, Jason Lange, Jan Lindblad, Chris Lonvick, Alexey Melnikov, Kathleen
Sterne, Peter Van Horne, Kent Watsen, Bert Wijnen, Dale R Worley, Moriarty, Tom Petch, Juergen Schoenwaelder, Phil Shafer, Yaron
Aleksandr Zhdankin Sheffer, Jason Sterne, Peter Van Horne, Kent Watsen, Bert Wijnen,
Dale R Worley, and Aleksandr Zhdankin.
7. IANA Considerations 7. IANA Considerations
7.1. The IETF XML Registry 7.1. The IETF XML Registry
This document registers one URI in the IETF XML registry [RFC3688]. This document registers one URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registration is Following the format in [RFC3688], the following registration is
requested: requested:
URI: urn:ietf:params:xml:ns:yang:ietf-syslog URI: urn:ietf:params:xml:ns:yang:ietf-syslog
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.
7.2. The YANG Module Names Registry 7.2. The YANG Module Names Registry
This document registers one YANG module in the YANG Module Names This document registers one YANG module in the YANG Module Names
registry [RFC7895]. Following the format in [RFC7950], the following registry [RFC7895]. Following the format in [RFC7950], the following
registration is requested: registration is requested:
name: ietf-syslog name: ietf-syslog
namespace: urn:ietf:params:xml:ns:yang:ietf-syslog namespace: urn:ietf:params:xml:ns:yang:ietf-syslog
prefix: ietf-syslog prefix: ietf-syslog
skipping to change at page 28, line 50 skipping to change at page 27, line 8
implement secure transport layers (e.g., SSH, TLS) with mutual implement secure transport layers (e.g., SSH, TLS) with mutual
authentication. authentication.
The NETCONF access control model (NACM) [RFC6536] provides the means The NETCONF access control model (NACM) [RFC6536] provides the means
to restrict access for particular users to a pre-configured subset of to restrict access for particular users to a pre-configured subset of
all available protocol operations and content. all available protocol operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes should be considered sensitive or default). These data nodes should be considered sensitive or
vulnerable in all network environments. Write operations (e.g., vulnerable in all network environments. Logging in particular is
edit-config) to these data nodes without proper protection can have a used to assess the state of systems and can be used to indicate a
negative effect on network operations and on network security. network compromise. If logging were to be disabled through malicious
means, attacks may not be readily detectable. Therefore write
operations (e.g., edit-config) to these data nodes without proper
protection can have a negative effect on network operations and on
network security.
In addition there are data nodes that require careful analysis and In addition there are data nodes that require careful analysis and
review. These are the subtrees and data nodes and their sensitivity/ review. These are the subtrees and data nodes and their sensitivity/
vulnerability: vulnerability:
facility-filter/pattern-match: When writing this node, facility-filter/pattern-match: When writing this node,
implementations MUST ensure that the regular expression pattern implementations MUST ensure that the regular expression pattern
match is not constructed to cause a regular expression denial match is not constructed to cause a regular expression denial
of service attack due to a pattern that causes the regular of service attack due to a pattern that causes the regular
expression implementation to work very slowly (exponentially expression implementation to work very slowly (exponentially
related to input size). related to input size).
remote/destination/signing/cert-signer: When writing this remote/destination/signing/cert-signer: When writing this subtree,
subtree, implementations MUST NOT specify a private key that is implementations MUST NOT specify a private key that is used for
used for any other purpose. any other purpose.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
remote/destination/transport: This subtree contains information remote/destination/transport: This subtree contains information
about other hosts in the network, and the TLS transport about other hosts in the network, and the TLS transport
certificate properties if TLS is selected as the transport certificate properties if TLS is selected as the transport
protocol. protocol.
remote/destination/signing: This subtree contains information remote/destination/signing: This subtree contains information
about the syslog message signing properties including signing about the syslog message signing properties including signing
certificate information. certificate information.
There are no RPC operations defined in this YANG module. There are no RPC operations defined in this YANG module.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-netconf-keystore] [I-D.ietf-netconf-keystore]
Watsen, K., "YANG Data Model for a "Keystore" Mechanism", Watsen, K., "YANG Data Model for a "Keystore" Mechanism",
draft-ietf-netconf-keystore-04 (work in progress), October Internet-Draft draft-ietf-netconf-keystore-04, October
2017. 2017.
[I-D.ietf-netconf-tls-client-server] [I-D.ietf-netconf-tls-client-server]
Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and
TLS Servers", draft-ietf-netconf-tls-client-server-05 TLS Servers", Internet-Draft draft-ietf-netconf-tls-
(work in progress), October 2017. client-server-05, October 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
DOI 10.17487/RFC2119, March 1997, RFC2119, March 1997, <http://www.rfc-editor.org/info/
<https://www.rfc-editor.org/info/rfc2119>. rfc2119>.
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, DOI
DOI 10.17487/RFC5424, March 2009, 10.17487/RFC5424, March 2009, <http://www.rfc-editor.org/
<https://www.rfc-editor.org/info/rfc5424>. info/rfc5424>.
[RFC5425] Miao, F., Ed., Ma, Y., Ed., and J. Salowey, Ed., [RFC5425] Miao, F., Ed., Ma, Y.Ed., and J. Salowey, Ed., "Transport
"Transport Layer Security (TLS) Transport Mapping for Layer Security (TLS) Transport Mapping for Syslog", RFC
Syslog", RFC 5425, DOI 10.17487/RFC5425, March 2009, 5425, DOI 10.17487/RFC5425, March 2009, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc5425>. editor.org/info/rfc5425>.
[RFC5426] Okmianski, A., "Transmission of Syslog Messages over UDP", [RFC5426] Okmianski, A., "Transmission of Syslog Messages over UDP",
RFC 5426, DOI 10.17487/RFC5426, March 2009, RFC 5426, DOI 10.17487/RFC5426, March 2009, <http://www
<https://www.rfc-editor.org/info/rfc5426>. .rfc-editor.org/info/rfc5426>.
[RFC5848] Kelsey, J., Callas, J., and A. Clemm, "Signed Syslog [RFC5848] Kelsey, J., Callas, J. and A. Clemm, "Signed Syslog
Messages", RFC 5848, DOI 10.17487/RFC5848, May 2010, Messages", RFC 5848, DOI 10.17487/RFC5848, May 2010,
<https://www.rfc-editor.org/info/rfc5848>. <http://www.rfc-editor.org/info/rfc5848>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<https://www.rfc-editor.org/info/rfc7223>. <http://www.rfc-editor.org/info/rfc7223>.
[RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module [RFC7895] Bierman, A., Bjorklund, M. and K. Watsen, "YANG Module
Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, Library", RFC 7895, DOI 10.17487/RFC7895, June 2016,
<https://www.rfc-editor.org/info/rfc7895>. <http://www.rfc-editor.org/info/rfc7895>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016, <http://www
<https://www.rfc-editor.org/info/rfc7950>. .rfc-editor.org/info/rfc7950>.
[RFC8089] Kerwin, M., "The "file" URI Scheme", RFC 8089, DOI
10.17487/RFC8089, February 2017, <https://www.rfc-
editor.org/info/rfc8089>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <http://www.rfc-editor.org/info/rfc8174>.
[Std-1003.1-2008] [Std-1003.1-2008]
The Open Group, ""Chapter 9: Regular Expressions". The The Open Group, ""Chapter 9: Regular Expressions". The
Open Group Base Specifications Issue 6, IEEE Std Open Group Base Specifications Issue 6, IEEE Std
1003.1-2008, 2016 Edition.", September 2016, 1003.1-2008, 2016 Edition.", September 2016, <http://
<http://pubs.opengroup.org/onlinepubs/9699919799/>. pubs.opengroup.org/onlinepubs/9699919799/>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-netmod-revised-datastores] [I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-10 Architecture", Internet-Draft draft-ietf-netmod-revised-
(work in progress), January 2018. datastores-10, January 2018.
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams",
ietf-netmod-yang-tree-diagrams-06 (work in progress), Internet-Draft draft-ietf-netmod-yang-tree-diagrams-06,
February 2018. February 2018.
[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-
<https://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <http://www.rfc-editor.org/info/rfc6241>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536, DOI
DOI 10.17487/RFC6536, March 2012, 10.17487/RFC6536, March 2012, <https://www.rfc-editor.org/
<https://www.rfc-editor.org/info/rfc6536>. info/rfc6536>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M. and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
Appendix A. Implementor Guidelines Appendix A. Implementor Guidelines
A.1. Extending Facilities Appendix A.1. Extending Facilities
Many vendors extend the list of facilities available for logging in Many vendors extend the list of facilities available for logging in
their implementation. Additional facilities may not work with the their implementation. Additional facilities may not work with the
syslog protocol as defined in [RFC5424] and hence such facilities syslog protocol as defined in [RFC5424] and hence such facilities
apply for local syslog-like logging functionality. apply for local syslog-like logging functionality.
The following is an example that shows how additional facilities The following is an example that shows how additional facilities
could be added to the list of available facilities (in this example could be added to the list of available facilities (in this example
two facilities are added): two facilities are added):
skipping to change at page 34, line 4 skipping to change at page 30, line 45
} }
identity vendor_specific_type_2 { identity vendor_specific_type_2 {
base syslogtypes:syslog-facility; base syslogtypes:syslog-facility;
description description
"Adding vendor specific type 2 to syslog-facility"; "Adding vendor specific type 2 to 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
Kiran Koushik, editor
Kiran Koushik (editor)
Verizon Wireless Verizon Wireless
500 W Dove Rd. 500 W Dove Rd.
Southlake, TX 76092 Southlake, TX 76092
US US
Phone: +1 512 650-0210 Phone: +1 512 650-0210
EMail: kirankoushik.agraharasreenivasa@verizonwireless.com Email: kirankoushik.agraharasreenivasa@verizonwireless.com
 End of changes. 55 change blocks. 
123 lines changed or deleted 133 lines changed or added

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