This is the old issue of putting a syslog-stream between -protocol and -tls/-ssh/-whatever. It wont hurt packet based syslog. Has been objected so far. I guess it is too late to look at it once again...
Rainer ----- Ursprüngliche Nachricht ----- Von: "Eric Rescorla" <[EMAIL PROTECTED]> An: "Miao Fuyou" <[EMAIL PROTECTED]> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Gesendet: 07.08.06 19:39 Betreff: Re: [Syslog] Notes on TLS transport Miao Fuyou <[EMAIL PROTECTED]> wrote: > > > > > S 5.3: > > All Syslog messages MUST be sent as TLS "application data". There > > MAY be multiple Syslog message in the same TLS record. The > > application data is defined with the following ABNF [3] expression: > > > > TLS's abstraction is as a stream, so this isn't really the business > > of htis spec. > > > > I agree to Eric's opinion. If syslog procotol has a mechanism to delimit > message, we will never need to address same issue across different > documents: syslog-tls, syslog-ssh, or syslog-tcp etc (perhaps with different > mechanisms). Note, though, that you do need a mapping from syslog to DTLS because it's packetized. Same as you need a mapping from syslog to UDP. -Ekr _______________________________________________ Syslog mailing list [email protected] https://www1.ietf.org/mailman/listinfo/syslog
_______________________________________________ Syslog mailing list [email protected] https://www1.ietf.org/mailman/listinfo/syslog
