Based on the discussions of the past few days, the one detail that I would add to the charter is about <PRI> and backward compatability, something along the lines of
While compatability with existing syslog systems is desirable, research shows that these are so diverse that there is nothing in common amongst them apart from <PRI> so that whilst that field will be retained, other fields may not be. added to the paragraph on syslog protocol. And yes, IESG and the ietf list will doubtless want to know why we regard that as acceptable. Tom Petch ----- Original Message ----- From: "Chris Lonvick" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 23, 2005 6:05 PM Subject: [Syslog] Revised proposed charter > 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 > [email protected] > https://www1.ietf.org/mailman/listinfo/syslog _______________________________________________ Syslog mailing list [email protected] https://www1.ietf.org/mailman/listinfo/syslog
