[Syslog-sec] Required transport

["Anton Okmianski" <aokmians@cisco.com>]

Hi!

I am doing final edits to the new revision of udp transport draft. I want to return to one issue we touched upon before. We have stated this in the past: 

"This transport protocol is REQUIRED for all syslog protocol implementations."

I am not 100% comfortable with this. I am looking at syslog as a protocol which is often embedded in the application, not general purpose re-usable syslog libraries which some people have in mind. If my application only want to send syslog messages via some TCP mapping, why should it be required to implement the UDP part which it does not intend to use?

Same thing on the receiver.  I understand the use case of general purpose syslog receiver.  However, if I have special purpose application to listen to faults from a given other application, why must I implement udp mapping?  

I have indeed worked on applications which fall into the above two scenarios. The sending one did indeed use UDP. But if we have chosen TCP, I don't see how the UDP transport requirement would have applied to us.  

Any sentiments against striking this requirement?

Thanks,
Anton. 


_______________________________________________
Syslog-sec mailing list
Syslog-sec@www.employees.org
http://www.employees.org/mailman/listinfo/syslog-sec