Lada,
Thanks for your review.
All was not added to the syslogtypes:severity because that would alter the
definition of severity as specified by RFC 5424 in Table 2 on page 10. I agree
that it will simplify the model to do so.
Please advise.
Thanks,
Clyde
On 7/14/15, 6:57 AM, netmod on
Wildes (cwildes) cwil...@cisco.com wrote:
Lada,
Thanks for your review.
All was not added to the syslogtypes:severity because that would alter the
definition of severity as specified by RFC 5424 in Table 2 on page 10. I
agree that it will simplify the model to do so.
The description
Carl,
Thanks for your question in the Netmod meeting during the review of the
ietf-syslog model.
Regarding the model implementation: the model has been implemented in ODL and
internally in Cisco's NXOS.
Thanks,
Clyde
___
netmod mailing list
Hi,
This e-mail summarizes the changes that have been made to the proposed
ietf-syslog.yang model since the July meeting when the previous 04 draft was
published. The changes are based on feedback received after the last meeting
from Martin Bjorklund, Lada Lhotka, Jason Sterne, and Mahesh
Jason,
We are about to publish draft-ietf-netmod-syslog-06 which separates terminal
logging from session logging. We appreciate your feedback.
Thanks,
Clyde
From: netmod > on
behalf of "Sterne, Jason (Jason)"
Jason,
We are about to publish draft-ietf-netmod-syslog-model-06 which incorporates
your feedback below.
Thanks,
Clyde
From: netmod > on
behalf of "Sterne, Jason (Jason)"
;course). The use case for multiple log buffers is that you might sort/filter
>different types of log events into different circular buffers (i.e. have one
>for really critical log events, etc) for viewing on the node.
>
>Regards,
>Jason
>
>-Original Message-
>Fro
Dmytro,
RFC 5424 The Syslog Protocol, defines the message format for syslog messages
and the proposed ietf-syslog.yang model supports both free form and structured
data format Syslog messages as specified by RFC 5424.
TIMESTAMP is described in section 6.2.3 of the RFC. Sequence number could be
No, I'm not aware of any IPR that applies to this draft
Clyde
On 2/22/16, 5:22 PM, "Lou Berger" wrote:
>Authors, Contributors, WG,
>
>As part of the preparation for WG Last Call
>
>Are you aware of any IPR that applies to draft identified above?
>
>Please state either:
>
Lou,
We are working on a revision to the document to address the concerns that
Martin and Tom raised.
There is one issue that I need to raise to the Netmod chairs for advice: all
our drafts since the original draft have "Intended status: Informational" at
the top of the draft. Martin
<ie...@btconnect.com> wrote:
>
>- Original Message -----
>From: "Clyde Wildes (cwildes)" <cwil...@cisco.com>
>To: <netmod@ietf.org>
>Cc: "Martin Bjorklund" <m...@tail-f.com>; "t.petch"
><ie...@btconnect.com>; "Ki
Patrick,
Thanks for your review.
Regarding the severity leaf: multiple severities are already covered when
severity is specified because the default severity comparison is all messages
of the specified severity and greater. You can use of the optional
pattern-match string to select a message
Juergen,
Thanks for your detailed review!
I addressed all of your comments in the latest draft.
Regards,
Clyde
On 6/15/16, 8:29 AM, "netmod on behalf of Juergen Schoenwaelder"
wrote:
>Hi,
>
>Dan Romascanu
pes of log events into
>different circular buffers (i.e. have one for really critical log
>events, etc) for viewing on the node.
>>
>> Regards,
>> Jason
>>
>> -Original Message-
>> From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of EXT Clyde
>
-12=--hwdiff
Please review and comment.
Thanks,
Clyde
From: "Clyde Wildes (cwildes)" <cwil...@cisco.com>
Date: Wednesday, January 11, 2017 at 2:54 PM
To: Andy Bierman <a...@yumaworks.com>
Cc: Alex Campbell <alex.campb...@aviatnet.com>, "netmod@ietf.org"
<
I think it was accidently dropped
due to some confusion over some "if-feature" comments from Tom P at one point.
(note - also add (s) to buffer to make it buffer(s) in a couple of places
in section 3).
Regards,
Jason
-Original Message-
From: netmod [m
- CA)" <jason.ste...@nokia.com>
Date: Monday, November 14, 2016 at 7:58 PM
To: "Clyde Wildes (cwildes)" <cwil...@cisco.com>, "netmod@ietf.org"
<netmod@ietf.org>
Subject: RE: syslog-model-11 single buffer vs list
Hi Clyde,
Most implementations probably have lim
Hi,
This draft addresses Phil Shafer’s comments and also removes references to TLS
for now.
Thanks,
Clyde
On 11/13/16, 3:47 PM, "netmod on behalf of internet-dra...@ietf.org"
wrote:
A New Internet-Draft is available
10:37:06PM +0000, Clyde Wildes (cwildes) wrote:
> Juergen,
>
> Thanks for your detailed review!
>
> I addressed all of your comments in the latest draft.
Thanks for the update. As my role as a YANG doctoc and someone
generally interested, I took anoth
Hi Phil,
Thanks for your review. My comments inline as [clyde].
On 10/31/16, 5:45 PM, "netmod on behalf of Phil Shafer"
wrote:
>Title : A YANG Data Model for Syslog Configuration
I've a few questions:
Kent,
No, I'm not aware of any IPR that applies to this draft
Thanks,
Clyde
On 12/13/16, 4:15 PM, "Kent Watsen" wrote:
Authors, Contributors, WG,
This IPR disclosure requests is being made as part of the preparation
for WG Last Call of
Hi Alex,
Thanks for your review. My comments are inline as [clyde]…
On 12/13/16, 8:16 PM, "netmod on behalf of Alex Campbell"
wrote:
I am considering to implement the data model in this draft.
I have reviewed this
Kent,
I will respond to Andy’s comments this morning and publish a new draft ASAP. It
would be very helpful if Andy and Alex could work with me on the new draft.
Thanks,
Clyde
On 1/10/17, 11:34 AM, "Kent Watsen" wrote:
Hi Clyde,
The LC period has ended.
Any
My comments inline as [clyde2]…
From: Andy Bierman <a...@yumaworks.com>
Date: Saturday, December 31, 2016 at 8:24 AM
To: "Clyde Wildes (cwildes)" <cwil...@cisco.com>
Cc: Alex Campbell <alex.campb...@aviatnet.com>, "netmod@ietf.org"
<netmod@iet
Hi Andy,
Thanks for taking the time to review the model.
My comments are inline as [clyde]…
From: netmod on behalf of Andy Bierman
Date: Tuesday, December 27, 2016 at 3:04 PM
To: Alex Campbell
Cc: "netmod@ietf.org"
Tom,
Inline…
On 3/16/17, 10:04 AM, "t.petch" <ie...@btconnect.com> wrote:
- Original Message -
From: "Clyde Wildes (cwildes)" <cwil...@cisco.com>
Sent: Monday, March 13, 2017 6:11 PM
> Tom,
>
> The next revision of th
Tom,
The next revision of the draft-ietf-netmod-syslog-model includes a change to
the Yang tree diagram explanation to include the text from RFC6087bis.
RFC5426 is referenced in the model where "Transmission of Syslog Messages over
UDP” occurs:
case udp {
Dale,
Thanks for the simplification. I have incorporated this in the next
draft-ietf-netmod-syslog-model revision.
Regards,
Clyde
On 3/6/17, 12:53 PM, "Dale R. Worley" wrote:
(We seem to be well beyond the original LC date, but this is only an
editorial
Kent,
Thanks for your exhaustive review. I will be publishing the revised model
momentarily.
Comments inline as [clyde].
On 7/12/17, 2:55 PM, "netmod on behalf of Kent Watsen" wrote:
As shepherd, yang doctor, and individual
Kent,
Comments inline as [clyde]…
On 8/14/17, 6:53 AM, "Kent Watsen" wrote:
>5. S1 as a whole. I'm a bit unclear what this section is doing. It
>seems to be a general summary of Syslog (RFC5424). Do we need this
here?
>
> [clyde]
Juergen and Alex,
The choice of Posix 1003.2 regular expressions was because of multiple vendors
who supported same and asked for model support:
http://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/syslog-edit-system.html
Hi Alex,
Answers inline as [clyde]…
On 7/17/17, 4:20 PM, "netmod on behalf of Alex Campbell"
wrote:
I am considering to implement the data model in this draft. (dependent on
business priorities of course)
I have
to
an IP address? If so, the answer is yes.
TLS was added as a destination transport choice in revision 14 of the draft.
Regards,
Clyde
From: "Zhengguangying (Walker)" <zhengguangy...@huawei.com>
Date: Tuesday, June 27, 2017 at 11:25 PM
To: "Clyde Wildes (cwildes
.
This might be a challenge for the RFC Editor.
Tom Petch
- Original Message -----
From: "Clyde Wildes (cwildes)" <cwil...@cisco.com>
Sent: Wednesday, July 19, 2017 6:48 PM
> Hi Alex,
>
> Answers inline as [cl
Tom,
I am working with Mahesh to fix the Normative References.
Regarding line length: I am using pyang 1.7.3 which is not complaining about
line length in the model. But when I look at the draft I see that both the tree
and the model exceed 80 characters. I will make a pass to shorten lines.
Hi,
As part of the last few steps before again calling for last call for
draft-ietf-netmod-syslog-model-14, we are adding certificate support to the
signing-options container. RFC 5848: Signed Syslog Messages is the RFC that
governs this section.
The signing-options container resides within
Kent,
Yes! Sorry for the delay.
Clyde
On 6/7/17, 11:13 AM, "Kent Watsen" wrote:
Hi Clyde,
Since no concerns have been raised, should we be expecting an updated
syslog draft shortly?
Kent // as shepherd
--
Hi,
As part of
Hi,
The latest draft-ietf-netmod-syslog-model-15 contains updates to the
signing-options container as a result of a review by Kent Watsen and Alex Clemm.
Diffs can be seen at:
https://www.ietf.org/rfcdiff?url1=draft-ietf-netmod-syslog-model-14=draft-ietf-netmod-syslog-model-15
Thanks,
Clyde
Benoit,
There were approximately 24 changes requested from you, Kent, Robert Wilton,
and Tom Petch. I have made approximately half of them and will try to finish
another revision of the draft by Friday.
Thanks,
Clyde
On 9/27/17, 3:24 AM, "Benoit Claise (bclaise)" wrote:
@btconnect.com> wrote:
Clyde
A quick glance at -18 shows that there is now a Normative Reference for
Posix - good- but I do not see it referenced - not so good:-(
I think that there needs to be a reference in 4.1
Tom Petch
- Original Message -----
Kent,
I will remove TLS if that is the preference of the chair and the working group.
RFC 6587 can be made Informational.
Working with an editor might help to avoid additional revisions.
Unless I hear otherwise I will post another update on Friday with TLS, and its
references, removed as well
Kent, Tom, Yaron, and Ron,
A new version of the draft-ietf-netmod-syslog-model has been published that
addresses your concerns.
Thanks,
Clyde
On 2/20/18, 9:06 AM, "netmod on behalf of Kent Watsen" wrote:
> Kent
Yaron,
Thanks for your review. My answers are inline as [clw1].
On 2/18/18, 6:31 AM, "Yaron Sheffer" wrote:
Reviewer: Yaron Sheffer
Review result: Has Issues
General Comments
* The semantics of pattern matching is not clear: "and/or the message
Kent,
I published a new draft that fixes the last two points.
Thanks,
Clyde
From: Kent Watsen
Date: Wednesday, February 28, 2018 at 10:11 AM
To: Mahesh Jethanandani
Cc: Clyde Wildes , "t.petch" , Yaron
Adam,
An earlier version of the model (draft-ietf-netmod-syslog-model-08 and prior)
included “terminal” as a syslog destination which addresses your requirement
below:
+--rw terminal {terminal-action}?
| +--rw all-terminals!
| | +--rw log-selector
Alexey,
Your minor comments are addressed below…
On 3/6/18, 12:06 PM, "Alexey Melnikov" wrote:
Alexey Melnikov has entered the following ballot position for
draft-ietf-netmod-syslog-model-23: No Objection
When responding, please keep the subject line
Alexey,
I believe that I have addressed both of your concerns in the about to be
published draft.
Thanks,
Clyde
On 3/9/18, 6:44 AM, "Alexey Melnikov" <aamelni...@fastmail.fm> wrote:
Hi Clyde,
On Thu, Mar 8, 2018, at 9:28 PM, Clyde Wildes (cwildes) wro
Adam,
A new draft will be published soon that addresses your concern and I have used
your wording.
Thanks,
Clyde
On 3/9/18, 6:09 AM, "Benoit Claise (bclaise)" <bcla...@cisco.com> wrote:
On 3/9/2018 2:27 AM, Adam Roach wrote:
> On 3/8/18 12:18 PM, Clyde Wil
log-model-23
On Fri, Mar 2, 2018 at 5:13 PM, Clyde Wildes (cwildes)
<cwil...@cisco.com<mailto:cwil...@cisco.com>> wrote:
Bob,
Syslog message severity is set in RFC 5424 Table 2. The model in
draft-ietf-netmod-syslog-model-23 conforms to that specification. A lower
number means higher
Bob,
Syslog message severity is set in RFC 5424 Table 2. The model in
draft-ietf-netmod-syslog-model-23 conforms to that specification. A lower
number means higher severity.
The severity-filter specifies that “all messages of the specified severity and
greater match” and therefore will be
50 matches
Mail list logo