Re: [Syslog] RFC 3164 in syslog-sign?

On Wed, 2006-12-20 at 18:19 -0800, Chris Lonvick wrote: > Hi, > > We started syslog-sign before we had Structured Data, and the original > author was creating a mechanism that could be used within the RFC 3164 > framework. However, times have changed. We now have syslog-protocol with > SDs. >

RE: APP-NAME, PROCID and MSGID in syslog sign - was: RE: [Syslog] clonvick WGLCReview of draft-ietf-syslog-sign-20.txt

Hi Chris, Rainer, others from my perspective, I do believe it is important to be able to easily tell apart a syslog-sign message from another message. It is true and I agree with you that SD-ID can be legitimately used for that purpose, although I do consider it a bit of an "overloading" of what

RE: APP-NAME, PROCID and MSGID in syslog sign - was: RE: [Syslog] clonvick WGLCReview of draft-ietf-syslog-sign-20.txt

Alex, thanks for your well thought-out reply. I am just commenting on one sentence (below), because this is IMHO the key issue... > -Original Message- > From: Alexander Clemm (alex) [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 21, 2006 10:52 AM > To: Rainer Gerhards; Chris Lonvick

[Syslog] WGLC -sign-20 rgerhards review

Hi all, finally, I have managed to do a thourough review. I have not excessively commented on issues that are already being discussed on list. All in all, the document is fine work and in good shape. My issues are mostly small nits and many of them connected to support for 3164 and 3195 (oh yes,

Re: [Syslog] Submission of draft-ietf-syslog-device-mib-12.txt

On Thu, Dec 21, 2006 at 02:49:53PM +0900, Glenn M. Keeni wrote: >Attached please find the updated ID > draft-ietf-syslog-device-mib-12.txt The combination of syslogEntityControlBindAddrType InetAddressType syslogEntityControlBindAddr InetAddress syslogEntityCo

RE: [Syslog] WGLC -sign-20 rgerhards review

I would like to plea with the group to figure out ways to stop using the legacy MTU as a reason to constrain new standards. I would rather see syslog-sign not support 3164 than for it to be constrained to 1024 bytes because of some belief that it needs to support a non-normative RFC. My recommenda

RE: [Syslog] RFC 3164

Rainer: I think it should be marked as obsoleted by the new RFC, which I believe is commonly done. Why bother updating an obsoleted document? How much common will you find in the wild aside from PRI? Thanks, Anton. > -Original Message- > From: Rainer Gerhards [mailto:[EMAIL PROTECTED

[Syslog] I-D ACTION:draft-ietf-syslog-device-mib-12.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Security Issues in Network Event Logging Working Group of the IETF. Title : Syslog Management Information Base Author(s) : G. Keeni Filename

[Syslog] Re: Mib-12

Hi, draft-ietf-syslog-device-mib-12.txt has been posted. The current status wrt the sets of comments in Dbh re-Review of -mib-11, part 1,2,3 given below. There are three areas of work: a. terminology. (1.1, 1.2, 1.3, 1.4) We need to arrive at a consensus b. TransportDomain matter: I

TransportDomain. Was: Re: [Syslog] Submission of draft-ietf-syslog-device-mib-12.txt

Juergen, Juergen Schoenwaelder wrote: On Thu, Dec 21, 2006 at 02:49:53PM +0900, Glenn M. Keeni wrote: Attached please find the updated ID draft-ietf-syslog-device-mib-12.txt The combination of syslogEntityControlBindAddrType InetAddressType syslogEntityControlBindAddr

RE: [Syslog] RFC 3164

Andrew, Anton, I am using Andrew's message to reply to both. I concur with Andrew, please see below... > -Original Message- > From: Andrew Ross [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 21, 2006 10:53 PM > To: Rainer Gerhards > Subject: RE: [Syslog] RFC 3164 > > > Hi Rainer,