Re: [netmod] Alexey Melnikov's No Objection on draft-ietf-netmod-syslog-model-23: (with COMMENT)

[Warren Kumari <[e-mail]>]

On Wed, Mar 7, 2018 at 9:17 AM, Benoit Claise <[e-mail]> wrote:
> Hi Alexey, Warren,
>>
>> Alexey Melnikov has entered the following ballot position for
>> draft-ietf-netmod-syslog-model-23: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Thank you for this document.
>>
>> I also prefer for TCP to be documented, if used in real world.
>
> I've seen this comment in Warren's comment at
> https://datatracker.ietf.org/doc/draft-ietf-netmod-syslog-model/ballot/#warren-kumari.
> However, I can't find his ballot in email.

That's because of my cunning plan of not clicking the Send Mail button.

I'd viewed my comments as just informational / preferences and not
worth cluttering up people's mail.

> So let me reply to both of you here.
>
> This was discussed on the NETMOD mailing list. See subject "I-D Action:
> draft-ietf-netmod-syslog-model-19.txt"
> The fact is that RFC 6587 is now historic, implying a historic downref.
>
> I'm in favor to publish the document as it is right now, whose 00 WG doc.
> version dates from Nov 2014.

SGTM!
W

> Augmenting a YANG module, if TCP is required, is not that hard.
>
> Regards, Benoit
>>
>>
>> Some minor comments:
>>
>> 1) Please add a Normative Reference for the file: URI RFC (RFC 8089) when
>> you
>> mention it for the first time.
>>
>> 2) On page 19:
>>
>> Example: compare->equals and action->no-match means
>> messages that have a severity that is not equal to the
>> specified severity will be logged.";
>>
>> Do you mean "action->block" instead of "action->no-match"?
>>
>> 3) When logging to file: how is the file name constructed from the name
>> file:
>> URI if multiple files are preserved by the system? E.g. if the log file is
>> rotated daily and 5 last files are preserved, how does each individual
>> filename
>> look? If I understood how this is used, this needs more clarification.
>>
>> 4) Nit: on page 18, typo in "spectify"
>>
>>
>> .
>>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf