[sip-clf] Advantages of using an IPFIX File Format for SIPCLF

"Saverio Niccolini" <Saverio.Niccolini@nw.neclab.eu> Tue, 09 February 2010 12:59 UTC

Return-Path: <Saverio.Niccolini@nw.neclab.eu>
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 16FA83A7579 for <sip-clf@core3.amsl.com>; Tue, 9 Feb 2010 04:59:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 DsSB2YdJQ2gX for <sip-clf@core3.amsl.com>; Tue, 9 Feb 2010 04:59:25 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id CA5C63A702D for <sip-clf@ietf.org>; Tue, 9 Feb 2010 04:59:24 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id D1B622C00C52C for <sip-clf@ietf.org>; Tue, 9 Feb 2010 14:00:30 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uf1bHtDVDYFo for <sip-clf@ietf.org>; Tue, 9 Feb 2010 14:00:30 +0100 (CET)
Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id B22952C000352 for <sip-clf@ietf.org>; Tue, 9 Feb 2010 14:00:25 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 9 Feb 2010 14:00:24 +0100
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_005B_01CAA990.39FB5D80"
Message-ID: <547F018265F92642B577B986577D671C011662CA@VENUS.office>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Advantages of using an IPFIX File Format for SIPCLF
Thread-Index: Acqph9gyRyb1K883R26Ur8K+sWMfFw==
From: "Saverio Niccolini" <Saverio.Niccolini@nw.neclab.eu>
To: "SIP-CLF Mailing List" <sip-clf@ietf.org>
Subject: [sip-clf] Advantages of using an IPFIX File Format for SIPCLF
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: Tue, 09 Feb 2010 12:59:26 -0000

Dear all,

as promised some time ago, I have just submitted a draft (coauthored
by Benoit, Brian and Hadriel) entitled:

Advantages of using an IPFIX File Format for SIPCLF
http://www.ietf.org/id/draft-niccolini-sipclf-ipfix-00.txt

I hope this draft can be used for discussion of the advantages
of choosing one format with respect to others for SIPCLF.

Please note that we tried to give an example for how an IPFIX
file format would look like just to give you an idea of that, 
the Information Elements needs careful discussion inside the WG
that will need to happen, thus please refrain yourself from bashing 
on that right now.

Let us know if you have comments,
Saverio

============================================================
Dr. Saverio Niccolini
Manager, Real-Time Communications Group
NEC Laboratories Europe, Network Research Division     
Kurfuerstenanlage 36, D-69115 Heidelberg
Tel.     +49 (0)6221 4342-118
Fax:     +49 (0)6221 4342-155
e-mail:  saverio.niccolini@nw.neclab.eu
============================================================
NEC Europe Limited Registered Office: NEC House, 1 Victoria
Road, London W3 6BL Registered in England 2832014