Dbh Yes, another lucid explanation of a tricky subject.
The issue I wish I had never raised :-) was a response to Juergen saying > The combination of > syslogEntityControlBindAddr InetAddress > syslogEntityControlTransportDomain TransportDomain > syslogEntityControlService SyslogService > > looks a bit crazy to me. > > - Why have both InetAddressType and TransportDomain? > > - Why not simply use (InetAddressType,InetAddress,InetPortNumber) or > (TansportAddressType,TransportAddress)? > > - What is the value of saying the service name is "xyz", which has > only local significance? > > - How do I find out which encapsulations are supported (plain, beep, tls, ...)? > > /js which mostly I agree with. But I think that there is no answer to finding out which encapsulations are supported because I do not think that the way in which syslog is put together has the concept of encapsulation; rather we have packages, bundles, like RFC3164/-sign/UDP RFC3195/BEEP RAW/TCP -protocol/TLS/TCP So by all means ask the editor of -mib to change it to use InetAddressType/InetAddress/InetPortNumber but I do not expect to see an answer there as to which encapsulations are supported. Tom Petch. <snip> _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
