Balazs Scheidler wrote:
> The description should focus on the means of encapsulating one single
> message into the TCP stream, where the message has the same format as the
> UDP packet in RFC3164.
Actually, that was the intention of syslog-reliable raw mode. The
protocol has restrictions in the RFC to cope with the charter of the WG,
but certainly the transport of the messages themselves is independent of
the (for example) format of the datestamps. It also handles the
pull/push dichotomy.
In terms of having better date stamps, tracking of which hosts the
message had been relayed through, etc, syslog-reliable/cooked is
designed to do that flexibly and informatively and still in a way
compatible with syslog-signed. I.e., it adds all that information
without actually changing the body of the message, so signatures don't
get corrupted and so on.
Just FYI. The problem *has* been solved. :-)
--
Darren New
San Diego, CA, USA (PST)
"I'm allergic to antihistamines."
"Oh? What do you break out in?"
