draft-ietf-netmod-syslog-model-25.txt | draft-ietf-netmod-syslog-model-26.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 13, 2018 Verizon Wireless | Expires: September 14, 2018 Verizon Wireless | |||
March 14, 2018 | March 15, 2018 | |||
A YANG Data Model for Syslog Configuration | A YANG Data Model for Syslog Configuration | |||
draft-ietf-netmod-syslog-model-25 | draft-ietf-netmod-syslog-model-26 | |||
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 | ||||
Datastore Architecture defined in [draft-ietf-netmod-revised- | ||||
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 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 13, 2018. | This Internet-Draft will expire on September 14, 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 (http://trustee.ietf.org/ | Provisions Relating to IETF Documents (http://trustee.ietf.org/ | |||
license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
skipping to change at page 2, line 54 ¶ | skipping to change at page 2, line 50 ¶ | |||
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. | |||
Such definitions of syslog protocol are defined in [RFC5424], and are | Such definitions of syslog protocol are defined in [RFC5424], and are | |||
used in this RFC. | used in this RFC. | |||
The YANG model in this document conforms to the Network Management | ||||
Datastore Architecture defined in [draft-ietf-netmod-revised- | ||||
datastores]. | ||||
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", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
"OPTIONAL" in this document are to be interpreted as described in BCP | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
14 [RFC2119] [RFC8174] when, and only when, they appear in all | 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
capitals, as shown here. | capitals, as shown here. | |||
1.2. Terminology | 1.2. Terminology | |||
The term "originator" is defined in [RFC5424]: an "originator" | The term "originator" is defined in [RFC5424]: an "originator" | |||
skipping to change at page 9, line 5 ¶ | skipping to change at page 9, line 5 ¶ | |||
3. Syslog YANG Module | 3. Syslog YANG Module | |||
3.1. The ietf-syslog Module | 3.1. The ietf-syslog Module | |||
This module imports typedefs from [RFC6991], | This module imports typedefs from [RFC6991], | |||
[I-D.ietf-netmod-rfc7223bis], groupings from | [I-D.ietf-netmod-rfc7223bis], groupings from | |||
[I-D.ietf-netconf-keystore], and | [I-D.ietf-netconf-keystore], and | |||
[I-D.ietf-netconf-tls-client-server], and it references [RFC5424], | [I-D.ietf-netconf-tls-client-server], and it references [RFC5424], | |||
[RFC5425], [RFC5426], [RFC5848], [RFC8089], [RFC8174], and | [RFC5425], [RFC5426], [RFC5848], [RFC8089], [RFC8174], and | |||
[Std-1003.1-2008]. | [Std-1003.1-2008]. | |||
<CODE BEGINS> file "ietf-syslog@2018-03-14.yang" | <CODE BEGINS> file "ietf-syslog@2018-03-15.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: Common YANG Data Types"; | "RFC 6991: Common YANG Data Types"; | |||
skipping to change at page 10, line 21 ¶ | skipping to change at page 10, line 21 ¶ | |||
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-14 { | revision 2018-03-15 { | |||
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 31, line 8 ¶ | skipping to change at page 31, line 8 ¶ | |||
The syslog/file/log-file/file-rotation container contains | The syslog/file/log-file/file-rotation container contains | |||
configuration parameters for syslog file rotation. This section | configuration parameters for syslog file rotation. This section | |||
describes how these fields might be used by an implementer to name | describes how these fields might be used by an implementer to name | |||
syslog files in a rotation process. This information is offered as | syslog files in a rotation process. This information is offered as | |||
an informative guide only. | an informative guide only. | |||
When an active syslog file with a name specified by log-file/name, | When an active syslog file with a name specified by log-file/name, | |||
reaches log-file/max-file-size and/or syslog events arrive after the | reaches log-file/max-file-size and/or syslog events arrive after the | |||
period specified by log-file/rollover, the logging system can close | period specified by log-file/rollover, the logging system can close | |||
the file, can compresses it, and can name the archive file <log-file/ | the file, can compress it, and can name the archive file <log-file/ | |||
name>.0.gz. The logging system can then open a new active syslog | name>.0.gz. The logging system can then open a new active syslog | |||
file <log-file/name>. | file <log-file/name>. | |||
When the new syslog file reaches either of the size limits referenced | When the new syslog file reaches either of the size limits referenced | |||
above, <log-file/name>.0.gz can be renamed <log-file/name>.1.gz and | above, <log-file/name>.0.gz can be renamed <log-file/name>.1.gz and | |||
the new syslog file can be closed, compressed and renamed <log-file/ | the new syslog file can be closed, compressed and renamed <log-file/ | |||
name>.0.gz. Each time that a new syslog file is closed, each of the | name>.0.gz. Each time that a new syslog file is closed, each of the | |||
prior syslog archive files named <log-file/name>.<n>.gz can be | prior syslog archive files named <log-file/name>.<n>.gz can be | |||
renamed to <log-file/name>.<n + 1>.gz. | renamed to <log-file/name>.<n + 1>.gz. | |||
Removal of archive log files could occur when either or both: | Removal of archive log files could occur when either or both: | |||
- log-file/number-of-files specified - the logging system can create | - log-file/number-of-files specified - the logging system can create | |||
up to log-file/number-of-files syslog archive files after which, the | up to log-file/number-of-files syslog archive files after which, the | |||
contents of the last archived file could be overwritten. | contents of the oldest archived file could be overwritten. | |||
- log-file/retention specified - the logging system can remove those | - log-file/retention specified - the logging system can remove those | |||
syslog archive files whose file expiration time (file creation time | syslog archive files whose file expiration time (file creation time | |||
plus the specified log-file/retention time) is prior to the current | plus the specified log-file/retention time) is prior to the current | |||
time. | time. | |||
Authors' Addresses | Authors' Addresses | |||
Clyde Wildes, editor | Clyde Wildes, editor | |||
Cisco Systems Inc. | Cisco Systems Inc. | |||
End of changes. 9 change blocks. | ||||
12 lines changed or deleted | 12 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/ |