> Hi, > > OK - sorry 'bout that. > > Glenn - please update it and get it into the ID repository. > > All - who will commit to reviewing this document? I will > need someone to > commit to this before I put it into the proposed charter.
I can look at the syslog side of it, but I am far from being an SNMP expert. I think we need at least one such expert to review it. So count' me as half a volunteer ;) Rainer > > Thanks, > Chris > > > > On Thu, 24 Nov 2005, Rainer Gerhards wrote: > > > Oops, I have overlooked that one. I agree with Glenn that > this should be > > in the charter. > > > > Rainer > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of Glenn > >> Mansfield Keeni > >> Sent: Thursday, November 24, 2005 11:33 AM > >> To: [EMAIL PROTECTED] > >> Subject: Re: [Syslog] Revised proposed charter > >> > >> Chris, > >> You seem to have dropped the last deliverable which is > >> in good shape > >> > >>> - A MIB definition for syslog will be produced. > >> > >> I would strongly recommend that we include it. It is an > >> important aspect > >> of the protocol. Some effort has gone into it. And it is the least > >> controversial [there are no issues of backward > compatibility]. And it > >> is very close to completion. > >> > >> Glenn > >> > >> Chris Lonvick wrote: > >>> Hi All, > >>> > >>> ==== v2 of proposed charter === > >>> > >>> Syslog is a de-facto standard for logging system events. > >> However, the > >>> protocol component of this event logging system has not > >> been formally > >>> documented. While the protocol has been very useful and > >> scalable, it > >>> has some known security problems which were documented in > RFC 3164. > >>> > >>> The goal of this working group is to address the security > >> and integrity > >>> problems, and to standardize the syslog protocol, transport, and a > >>> select set of mechanisms in a manner that considers the ease of > >>> migration between and the co-existence of existing > versions and the > >>> standard. > >>> > >>> syslog has traditionally been transported over UDP and this WG has > >>> already defined RFC 3195 for the reliable transport for the syslog > >>> messages. The WG will separate the UDP transport from the > >> protocol so > >>> that others may define additional transports in the future. > >>> > >>> > >>> - A document will be produced that describes a standardized syslog > >>> protocol. A mechanism will also be defined in this document > >>> that will provide a means to convey structured data. > >>> > >>> - A document will be produced that describes a standardized UDP > >>> transport for syslog. > >>> > >>> - A document will be produced that describes a standardized > >> mechanism > >>> to sign syslog messages to provide integrity checking and source > >>> authentication. > >>> > >>> > >>> === === > >>> > >>> Comments please. > >>> > >>> Thanks, > >>> Chris > >>> > >>> _______________________________________________ > >>> Syslog mailing list > >>> Syslog@lists.ietf.org > >>> https://www1.ietf.org/mailman/listinfo/syslog > >> > >> > >> > >> > >> _______________________________________________ > >> Syslog mailing list > >> Syslog@lists.ietf.org > >> https://www1.ietf.org/mailman/listinfo/syslog > >> > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
