Re: [sip-clf] A syslog approach to sip logging

"Rainer Gerhards" <rgerhards@hq.adiscon.com> Thu, 04 February 2010 11:54 UTC

Return-Path: <rgerhards@hq.adiscon.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DD923A6C05 for <sip-clf@core3.amsl.com>; Thu, 4 Feb 2010 03:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level:
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0t5WwfTEftcv for <sip-clf@core3.amsl.com>; Thu, 4 Feb 2010 03:54:52 -0800 (PST)
Received: from mailin.adiscon.com (hetzner.adiscon.com [85.10.198.18]) by core3.amsl.com (Postfix) with ESMTP id 998493A6AF0 for <sip-clf@ietf.org>; Thu, 4 Feb 2010 03:54:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailin.adiscon.com (Postfix) with ESMTP id 9A518241C005; Thu, 4 Feb 2010 12:41:25 +0100 (CET)
Received: from mailin.adiscon.com ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXjKMbTGz9JP; Thu, 4 Feb 2010 12:41:25 +0100 (CET)
Received: from GRFEXC.intern.adiscon.com (pd95c774a.dip0.t-ipconnect.de [217.92.119.74]) by mailin.adiscon.com (Postfix) with ESMTP id 20E4B241C004; Thu, 4 Feb 2010 12:41:25 +0100 (CET)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 4 Feb 2010 12:55:35 +0100
Message-ID: <9B6E2A8877C38245BFB15CC491A11DA710380A@GRFEXC.intern.adiscon.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sip-clf] A syslog approach to sip logging
Thread-Index: AcqlKjTIWhHobdjnTeOJJVFg2KKMkQAJk1NwABABUkA=
References: <013201caa438$f19aac50$0600a8c0@china.huawei.com><4D9AD174-7E0A-4E47-BB53-32428C4803A9@cisco.com> <430FC6BDED356B4C8498F634416644A917E5E0E07F@mail>
From: "Rainer Gerhards" <rgerhards@hq.adiscon.com>
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>, "Cullen Jennings" <fluffy@cisco.com>, "David B Harrington" <dbharrington@comcast.net>
Cc: SIP-CLF Mailing List <sip-clf@ietf.org>
Subject: Re: [sip-clf] A syslog approach to sip logging
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 11:54:53 -0000

> -----Original Message-----
> From: sip-clf-bounces@ietf.org [mailto:sip-clf-bounces@ietf.org] On
> Behalf Of Hadriel Kaplan
> Sent: Thursday, February 04, 2010 5:17 AM
> To: Cullen Jennings; David B Harrington
> Cc: 'SIP-CLF Mailing List'
> Subject: Re: [sip-clf] A syslog approach to sip logging
> 
> 
> 
> > -----Original Message-----
> > From: sip-clf-bounces@ietf.org [mailto:sip-clf-bounces@ietf.org] On
> Behalf
> > Of Cullen Jennings
> > Sent: Wednesday, February 03, 2010 6:39 PM
> >
> > One requirement that I suspect you will find fairly universal about
> > transporting around SIP log like informations is that
> >
> > 1) it is reliable
> >
> > 2) we can include complete SIP messages. These can get very large.
> (Magnus
> > posted a 40k SDP to the mmusic awhile back, don't even ask how large
> > MESSAGE messages get in the wild)
> 
> Also, if it is required for it to support including complete SIP
> messages, then it has to support binary content, since those can be in
> SIP message bodies (e.g., ISUP, QSIG).

This is problematic, but could be done with some transformation rules. syslog
is *not* designed as a transfer protocol for binary data, even though it may
occasionally support it. If sip clf has a large binary content part, syslog
is probably wrong. Apache clf is a text format, so I did not yet think this
may be a problem.

How do you so far intended to write them out? My understanding so far was
that a sip clf log entry would be a set of values, terminated by a LF. But
binary data may contain LF. So don't you need to encode it in any case?

Rainer