> > If we go for framing, we must use byte-couting, because we have not > > outruled any sequence. If we go for octet-stuffing, we must > define an > > escape mechanism. Any of this would be helpful for plain > tcp syslog, but > > that is definitely a big departure from current syslog. > Please note that > > currently many syslogds do octet-stuffing and the message > TRAILER is LF. > > That's unfortunate :(
I agree, but that's the way it is in current (non-standard) implementations. > > In nearly all IETF protocols, the message trailer or EOL > marker is CR-LF. If we go for a very simplistic tcp transport, there is nothing that hinders us in chaning it to CR-LF. That would also be compatible to existing receivers, as LF thankfully comes after CR... Rainer _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
