Hi all, The syslog-sign ID refers to UDP in several places. I wonder if this is by intension. I don't see any reason why we should limit it to UDP tranport and outrule TCP. Shouldn't it be better transport-independent?
As actual example, I do not see any reason why syslog-sign should NOT travel over RFC 3195/RAW. Of course, with COOKED, there are some issues, but RAW would be a big advantage. As of now, I think we could not do a standard-compliant sign via RAW implementation. Comments? Many thanks, Rainer Gerhards
