> * My opinion about BEEP that it is an overkill. BEEP is simply too > complicated, that's why it is not yet supported by > syslog-ng. TCP transport > solves most problems we had with UDP, and using BEEP doesn't give us > anything new or exciting. Encryption can simply be carried > out by wrapping > the TCP stream into SSL. I know there are key people involved with the syslog RFC on this list. Do they see any chance for a "SSYSLOG" protocol - meaning a "simple" syslog protocol based on TCP but the focus being on simple, that is no beep and the like. I am getting more and more the impression this is what people are really looking for and most implementors (us included) are not really happy with the new RFCs. Yes, sure we could have commented on the RFCs before they became a standard - agreed. In my case, I was simply too late ;) As an other choice, would it may be possible to think about somthing like a new protocol for network event loging, based on the idea of syslog but with the enhancements we all would like to see... Rainer Gerhards Adiscon _______________________________________________ LogAnalysis mailing list LogAnalysisat_private http://lists.shmoo.com/mailman/listinfo/loganalysis
This archive was generated by hypermail 2b30 : Wed Dec 11 2002 - 01:47:24 PST