On Fri, Dec 22, 2006 at 07:17:18PM +0100, tom.petch wrote: > I am not convinced that the proposed solutions match the underlying problem. > > Syslog: > - can be -protocol or RFC3164 (or RFC3164bis or ...) > - may be signed. > - may be secured with TLS (or SSH or DTLS or ...) > - could run over UDP or TCP (or SCTP or ..) > > What we have then done is to bind -protocol to TLS to TCP in a > package and asked IANA for a port number less that 1024 for that > combination > > So I think that trying to analyse it in terms of, eg, InetAddressType, > InetAddress, InetPortNumber and SyslogEncapsulation won't work.
I don't get your message - can you enlighten us please? /js -- Juergen Schoenwaelder {International|Jacobs} University Bremen <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog