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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 04 February 2010 04:16 UTC

Return-Path: <HKaplan@acmepacket.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 294823A69B3 for <sip-clf@core3.amsl.com>; Wed, 3 Feb 2010 20:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level:
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012, 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 Z8kaYSOmdb-S for <sip-clf@core3.amsl.com>; Wed, 3 Feb 2010 20:16:08 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 5E2713A68CC for <sip-clf@ietf.org>; Wed, 3 Feb 2010 20:16:08 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 3 Feb 2010 23:16:50 -0500
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 3 Feb 2010 23:16:50 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Cullen Jennings <fluffy@cisco.com>, David B Harrington <dbharrington@comcast.net>
Date: Wed, 3 Feb 2010 23:16:45 -0500
Thread-Topic: [sip-clf] A syslog approach to sip logging
Thread-Index: AcqlKjTIWhHobdjnTeOJJVFg2KKMkQAJk1Nw
Message-ID: <430FC6BDED356B4C8498F634416644A917E5E0E07F@mail>
References: <013201caa438$f19aac50$0600a8c0@china.huawei.com> <4D9AD174-7E0A-4E47-BB53-32428C4803A9@cisco.com>
In-Reply-To: <4D9AD174-7E0A-4E47-BB53-32428C4803A9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 04:16:10 -0000

> -----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).

-hadriel