Re: [sip-clf] SIP CLF -> IPFIX?

Benoit Claise <bclaise@cisco.com> Thu, 30 July 2009 15:14 UTC

Return-Path: <bclaise@cisco.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 0E03228C114 for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.416
X-Spam-Level:
X-Spam-Status: No, score=-2.416 tagged_above=-999 required=5 tests=[AWL=0.183, 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 NVuO5qAnbbHL for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:14:49 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 173473A6933 for <sip-clf@ietf.org>; Thu, 30 Jul 2009 08:14:48 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6UFElK4001547; Thu, 30 Jul 2009 17:14:47 +0200 (CEST)
Received: from [10.61.101.211] (dhcp-10-61-101-211.cisco.com [10.61.101.211]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6UFEkST008866; Thu, 30 Jul 2009 17:14:47 +0200 (CEST)
Message-ID: <4A71B8E6.7060601@cisco.com>
Date: Thu, 30 Jul 2009 17:14:46 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Vijay Gurbani <vkg@alcatel-lucent.com>
References: <4A71A239.4090806@cisco.com> <4A71B709.4050805@alcatel-lucent.com>
In-Reply-To: <4A71B709.4050805@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] SIP CLF -> IPFIX?
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, 30 Jul 2009 15:14:50 -0000

Vijay,

> Benoit Claise wrote:
>> Hi Vijay,
>
> Benoit: Thanks for your interest in this.  One quick clarification
> inline.
>
>> During the OPSAREA, I asked you the following questions regarding 
>> your work at http://www.ietf.org/proceedings/75/slides/opsarea-2.pdf
>>
>> QUESTION: if I understand correctly, you want a way to define 
>> Information Element types?
>>
>>            Answer: Yes
>
> Just to be sure, we want to define a logging format -- which fields
> to include, how to ensure extensibility for future fields, etc.
> In that vein, it is not so much about Information Element *types*
> as it is about the choice and representation of the Information
> Elements themselves.
Sure. My mistake in choosing words

Regards, Benoit.
> I don't know if that is too fine a distinction
> or not, but probably worth a clarification.
>
> Once again, thank you for indulging us.
>
> - vijay