Hi,
This message officially starts the Syslog Working Group Last Call for
the following document:
Signed syslog Messages (draft-ietf-syslog-sign-22.txt)
http://www.ietf.org/internet-drafts/draft-ietf-syslog-sign-22.txt
The Working Group Last Call for these documents will end August 9.
This is a
Chris:
Can we ask Mangus to provide suggested text? He mentioned it is just a
paragraph. This would make it a bit easier to get to the point of
what/how he wants addressed and evaluate if we agree with it. If his
suggested text is not too demanding on implementations, but rather a
recommendation,
I think this protocol should only address the concerns for the syslog
messages delivered out from its originating box. We should not get into
the syslog application to regulate how it should behave. Besides, there
are typically syslog relay devices before the messages reach its target
receiver box
Chris Lonvick wrote:
Hi Folks,
Here is clarification of what Magnus wants. We have so far received
Eliot's proposal but I don't think that addresses the concern.
I agree. My concern was downstream resources. Magnus' concern is the
syslog "application". This is complex because there are
