IETF Logo Mail Archive

RE: [Syslog] delineated datagrams

"Rainer Gerhards" <rgerhards@hq.adiscon.com> Fri, 11 August 2006 04:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBOgt-0002Xq-BD; Fri, 11 Aug 2006 00:32:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBOgs-0002Xi-Ev for syslog@ietf.org; Fri, 11 Aug 2006 00:32:10 -0400
Received: from mail.hq.adiscon.com ([84.245.151.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBOgr-0004sJ-4i for syslog@ietf.org; Fri, 11 Aug 2006 00:32:10 -0400
Received: from localhost (localhost [127.0.0.1]) by mail.hq.adiscon.com (Postfix) with ESMTP id 360389C00D; Fri, 11 Aug 2006 06:33:06 +0200 (CEST)
Received: from mail.hq.adiscon.com ([127.0.0.1]) by localhost (mail.grf.adiscon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13962-05; Fri, 11 Aug 2006 06:33:02 +0200 (CEST)
Received: from grfint2.intern.adiscon.com (grfint2 [172.19.0.6]) by mail.hq.adiscon.com (Postfix) with ESMTP id 786C79C00B; Fri, 11 Aug 2006 06:33:02 +0200 (CEST)
Subject: RE: [Syslog] delineated datagrams
Date: Fri, 11 Aug 2006 06:21:50 +0200
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA174DE1@grfint2.intern.adiscon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1155198633.6525.1.camel@bzorp.balabit>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-class: urn:content-classes:message
Thread-Topic: [Syslog] delineated datagrams
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Index: Aca8We44KDRAF0sETvmLoLVEiES1iQAopC+g
From: Rainer Gerhards <rgerhards@hq.adiscon.com>
To: Balazs Scheidler <bazsi@balabit.hu>
X-Virus-Scanned: by amavisd-new-2.3.3 (20050822) (Debian) at adiscon.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: syslog@ietf.org, Tom Petch <nwnetworks@dial.pipex.com>
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog@lists.ietf.org>
List-Help: <mailto:syslog-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=subscribe>
Errors-To: syslog-bounces@lists.ietf.org

> Maybe this already has been said ;)
> 
> This makes sense. What about other control characters?
> 


We need to differentiate between on-the-wire format and storage format.
On-the-wire, I would escape only LF and the escape character. In
storage, I would escape any control character (which can be quite tricky
with Unicode). Our current scope (and IETF scope) is on-the-wire. So I
propose not to mangle any more characters than absolutely necessary.

Rainer

_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog

v2.23.0 | Report a Bug | By Email