The exact order of future development has not yet been decided, but
it is likely that it will be close in the way the topics are ordered in this
list:

• Implementation of a BEEP XML parser. This is needed to fully support BEEP channel 0
  protocol. DONE
  
• Implementation of support for listener profiles. DONE
  
• Support for a higher-lever representation of the syslog message as an easy to deal with
  object in its own right. DONE
  
• client-side support for RFC 3195 / COOKED DONE
  
• Inclusion of the client-side functionality in Adiscon's MonitorWare line of products.
  partly DONE
  
• Inclusion of the server-side functionality in Adiscon's MonitorWare line of products.
  partly DONE
  
• inclusion of traditional UDP based syslog
  
• Test-implementation of syslog-international (also to see if syslog-international
  can easily enough be put in code).
  
• inclusion of syslog-sign
  
• server-side support for RFC 3195 / COOKED
  
• relay support for RFC 3195 / COOKED
  
• Improvments to the server-side API
  
• Eventually support for tuning profiles, which will provide encryption. This will be done
  with the help of openssl.
  
• inclusion of relay functionality of RFC 3195 / COOKED
  
• the creation of a drop-in API replacement for the BSD syslog calls
  

We are also looking into the IETF intrusion detection WGs - there is some interesting
work going on which could eventually be included in liblogging.

The information is current as of 2003-08-03. If you would like to contact the author,
please email Rainer Gerhards and watch for the reply with
information on how to get to his real mail box. (The mailto is just a fake to feed the spammers ;)).

Email to a friend  | Print this article