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.
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. Glen Marshall -----Original Message----- From: Darren Reed [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 18, 2005 10:23 AM To: Marshall Glen Cc: [EMAIL PROTECTED]; 'Rainer Gerhards'; [EMAIL PROTECTED] Subject: Re: [Syslog] plain tcp syslog > > I'd like to see that too, although I think the length needs to be 32K for > healthcare audit records (see RFC 3881). Why ? RFC 3881 doesn't specify that syslog needs to be anywhere. If you've got long records that need to be saved for audit purposes then perhaps a protocol other than syslog should be used for this ? Just because you have a hammer doesn't make everything you want to fix a nail. (or however it goes :) Darren ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
