Subject: AW: Re: [Syslog] Notes on TLS transport

From: "Rainer Gerhards" <[email-masked]>
Date: Sun, 13 Aug 2006 16:43:05 +0200

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-masked]>
An: "Miao Fuyou" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Gesendet: 07.08.06 19:39
Betreff: Re: [Syslog] Notes on TLS transport 

Miao Fuyou <[email-masked]> 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-masked]
https://www1.ietf.org/mailman/listinfo/syslog
_______________________________________________
Syslog mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/syslog