Re: [netmod] I-D Action: draft-ietf-netmod-syslog-model-08.txt

[Mahesh Jethanandani]

> On May 10, 2016, at 2:22 PM, Clyde Wildes (cwildes)  wrote:
> 
> Hi,
> 
> This update to the draft-ietf-netmod-syslog-model-08 incorporates the changes 
> listed below based on feedback received.
> 
> An additional revision to this draft will be necessary to finalize TLS 
> configuration leaves once the ietf-tls-client-server-model that the NETCONF 
> WG plans to spin out of the netconf-server-model draft is available.
> 
> Changes from feedback from Mahesh J:
> - added support for configuring a syslog server

Did I? Sorry, if there was a miscommunication. I thought the rational that 
networks devices are rarely configured as syslog servers made sense. I will let 
the WG decide if they want to keep syslog server configuration. 

We were discussing ssh server and client configuration and the desire to 
include that as part of the work (being done by Kent and others in NETCONF WG).

Cheers

Mahesh Jethanandani
mjethanand...@gmail.com

> 
> Changes from feedback from Tom P.:
> - removed four features for log action leaves console, buffer, terminal and 
> session since they are implemented by multiple vendors. Lack of support for 
> these actions can be indicated using a deviation.
> - removed feature buffer-limit-messages since implementation by any vendor is 
> unknown
> - renamed feature terminal-facility-user-logging-config to 
> terminal-facility-device-logging to shorten the name and to clarify
> - renamed feature session-facility-user-logging-config to 
> session-facility-user-logging to shorten the name
> - renamed feature selector-sevop-config to feature select-sev-compare to 
> shorten the name
> - renamed feature selector-match-config to feature select-match to shorten 
> the name
> - renamed feature structured-data-config to feature structured-data to 
> shorten the name
> - renamed feature signed-messages-config to feature signed-messages to 
> shorten the name
> - removed the log-buffer list and name from log-action buffer since 
> implementation by any vendor is unknown
> - removed the word draft from section 1
> - updated the copyright dates and the revision dates in the models
> - moved the example to an Appendix
> - removed e-mail addresses from the acknowledgement section
> 
> Changes from feedback from Benoit:
> - rename module vendor-syslog-types to module vendor-syslog-types-example
> 
> 
> Thanks,
> 
> Kiran and Clyde
> 
> 
> 
> 
>> On 5/10/16, 2:14 PM, "netmod on behalf of internet-dra...@ietf.org" 
>>  wrote:
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the NETCONF Data Modeling Language of the IETF.
>> 
>>   Title   : SYSLOG YANG Model
>>   Authors : Clyde Wildes
>> Kiran Koushik
>>Filename: draft-ietf-netmod-syslog-model-08.txt
>>Pages   : 35
>>Date: 2016-05-10
>> 
>> Abstract:
>>  This document describes a data model for the Syslog protocol which is
>>  used to convey event notification messages.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/
>> 
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-netmod-syslog-model-08
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-syslog-model-08
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> ___
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] "A YANG Data Model for Routing Management" Modifications

[Juergen Schoenwaelder]

On Sat, May 28, 2016 at 02:17:27PM +, Acee Lindem (acee) wrote:
> 
> 
> On 5/28/16, 9:31 AM, "Juergen Schoenwaelder"
>  wrote:
> 
> >On Fri, May 27, 2016 at 09:14:23PM +, Acee Lindem (acee) wrote:
> >> Hi Lada, Juergen,
> >> 
> >> On 5/27/16, 1:26 PM, "Juergen Schoenwaelder"
> >>  wrote:
> >> 
> >> >On Fri, May 27, 2016 at 11:42:08AM +0200, Ladislav Lhotka wrote:
> >> >> Hi Acee,
> >> >> 
> >> >> I have a couple of questions:
> >> >> 
> >> >> 1. I changed "routing-protocol" -> "control-plane-protocol" (this is
> >> >>already in GitHub). As for identities, I introduced a new base
> >> >>identity "control-plane-protocol", and derived "routing-protocol"
> >> >>from it. So the idea is that routing protocols will still use
> >> >>"routing-protocol" as their base. Is it OK?
> >> 
> >> We would like to have a single list rather than multiple lists. By
> >> generalizing “control-plane-protocols” we have one list per device, LNE,
> >> or NI. That is the goal.
> >> 
> >> >>
> >> >
> >> >So what is a routing protocol and what is a control plane protocol?
> >> 
> >> A routing protocol is a RIB client. A control plane protocol is more
> >> general.
> >
> >A RIB client?
> 
> A protocol that installs routes in one of the AF RIBs.
> 
> 
> > 
> >> >Or
> >> >what turns a control plane protocol into a routing protocol? Will this
> >> >distinction make network management simpler?
> >> 
> >> It will give us a place to put control plane protocols.
> >>
> >
> >I do not see yet why this is the scope of this effort. Perhaps I do not
> >understand what is proposed here:
> >
> >a) a change of the identity routing-protocol
> >
> >b) a change of the container routing-protocols
> >
> >c) a change of the list routing-protocol
> 
> 
> d) All of the above
>

Then this does not make sense to me. You apparently propose to
change

   +--rw routing
   |  +--rw router-id?
   |  +--rw routing-protocols
   |  +--rw routing-protocol* [type name]
   |
   |
   +--rw ribs
  +--rw rib* [name]

to

   +--rw routing
   |  +--rw router-id?
   |  +--rw control-plane-protocols
   |  +--rw control-plane-protocol* [type name]
   |
   |
   +--rw ribs
  +--rw rib* [name]

and I think this is wrong since there are control plane protocols that
have nothing to do with routing and I also do not think the WG is
chartered to provide a model or infrastructure for arbitrary
control-plane data models. Perhaps you propose something else but then
please make it clear what is expected to be changed so that I can
understand.

/js

-- 
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-syslog-model-08.txt

[t . petch]

Tom Petch


- Original Message -
From: "Sterne, Jason (Nokia - CA)" 
Sent: Friday, May 27, 2016 8:30 PM

> Hi Clyde,
>
> I was a bit surprised to see the receiver/server side config in here
(log-input-transports).  That seems to be a somewhat significant change
in scope.  I thought the focus of this was more on the generation &
distribution.  Do many implementations have functionality that maps to
this log-input-transports ?   In any case the pyang tree has
log-input-transports but it doesn't seem to be down in the actual model
itself.  But I'd be inclined to just remove this from the model.  Maybe
Mahesh has some thoughts here (I didn't see a posting about this in the
mailing list).
>
> I agree there are multiple implementations of console, buffer and
session logs.  But maybe 'terminal' should be removed or an if-feature ?
I'm not sure that one is so widespread (not in JUNOS, not in SR OS).
>
> Buffer-limit-messages and having multiple log buffers are both
supported by Nokia SR OS. I would think that both of those would have
support in other logging implementations as well.  I'm not sure if Tom
P. was really concluding that there are no implementations of these in
his email.  Do we have multiple examples of implementations that limit
log buffers using bytes ?
>

My comment was more on the complexity that results from having so many
options.  Other models are worse - some of the routing ones I find
unintelligible as a result - but I raised the issue on this model
because it is being discussed on this list where (almost) all the
expertise in these matters resides to see if anyone else would bite.

I believe we will regret this complexity some years down the line but
see no way of forestalling this:-(

I don't have direct knowledge of whether or not this feature is
widespread.

Tom Petch

> Buffer-limit-messages would be easy to do as an augmentation but
making the log-buffer a list is probably something we should just do
from the start.  That is also consistent with all the other types of
actions (except console of 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-
> From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of EXT Clyde
Wildes (cwildes)
> Sent: Tuesday, May 10, 2016 17:23
> To: netmod@ietf.org
> Subject: Re: [netmod] I-D Action:
draft-ietf-netmod-syslog-model-08.txt
>
> Hi,
>
> This update to the draft-ietf-netmod-syslog-model-08 incorporates the
changes listed below based on feedback received.
>
> An additional revision to this draft will be necessary to finalize TLS
configuration leaves once the ietf-tls-client-server-model that the
NETCONF WG plans to spin out of the netconf-server-model draft is
available.
>
> Changes from feedback from Mahesh J:
> - added support for configuring a syslog server
>
> Changes from feedback from Tom P.:
> - removed four features for log action leaves console, buffer,
terminal and session since they are implemented by multiple vendors.
Lack of support for these actions can be indicated using a deviation.
> - removed feature buffer-limit-messages since implementation by any
vendor is unknown
> - renamed feature terminal-facility-user-logging-config to
terminal-facility-device-logging to shorten the name and to clarify
> - renamed feature session-facility-user-logging-config to
session-facility-user-logging to shorten the name
> - renamed feature selector-sevop-config to feature select-sev-compare
to shorten the name
> - renamed feature selector-match-config to feature select-match to
shorten the name
> - renamed feature structured-data-config to feature structured-data to
shorten the name
> - renamed feature signed-messages-config to feature signed-messages to
shorten the name
> - removed the log-buffer list and name from log-action buffer since im
plementation by any vendor is unknown
> - removed the word draft from section 1
> - updated the copyright dates and the revision dates in the models
> - moved the example to an Appendix
> - removed e-mail addresses from the acknowledgement section
>
> Changes from feedback from Benoit:
> - rename module vendor-syslog-types to module
vendor-syslog-types-example
>
>
> Thanks,
>
> Kiran and Clyde
>
>
>
>
> On 5/10/16, 2:14 PM, "netmod on behalf of internet-dra...@ietf.org"
 wrote:
>
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> >This draft is a work item of the NETCONF Data Modeling Language of
the IETF.
> >
> >Title   : SYSLOG YANG Model
> >Authors : Clyde Wildes
> >  Kiran Koushik
> > Filename: draft-ietf-netmod-syslog-model-08.txt
> > Pages   : 35
> > Date: 2016-05-10
> >
> >Abstract:
> >   This document describes a data model for the Syslog protocol which
is
> >   used