> > RFC 3881 is transport agnostic. However, DICOM Supplement 99 and the IHE > technical framework that specify its implementations currently require > Reliable Syslog COOKED. The issue is the maximum supported length. RFC > 3195 does not specify a limit. So the issue is what that limit should be.
Well whoever wrote DICOM Supplement 99 and the IHE technical framework should be told they screwed up in deciding that this was the way to go and implementors should use something else that makes sense. > Many of the medical devices that implement an audit capability are not > general-purpose computers, e.g., radiological modalities. A simple protocol > stack like BEEP is preferable, for a variety of good reasons, for those > cases. BEEP is NOT simple. BEEP is extraordinarily complex solution for what is a very simple problem. If it was simple syslog over TCP, today, would use it. In open source, people vote with their feet (or their code) and the result of that poll is that BEEP for syslog over TCP is a failure. BEEP and syslog is like an orphan looking for someone or something to make it feel loved. Darren _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
