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

Vijay Gurbani <vkg@alcatel-lucent.com> Thu, 30 July 2009 15:06 UTC

Return-Path: <vkg@alcatel-lucent.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 EF91928C1CF for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.163, 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 PasNWad6T-rD for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:06:06 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id A2E2D28C1DB for <sip-clf@ietf.org>; Thu, 30 Jul 2009 08:06:06 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n6UF65l5000044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jul 2009 10:06:05 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6UF64Vl014310; Thu, 30 Jul 2009 10:06:05 -0500 (CDT)
Message-ID: <4A71B709.4050805@alcatel-lucent.com>
Date: Thu, 30 Jul 2009 10:06:49 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
References: <4A71A239.4090806@cisco.com>
In-Reply-To: <4A71A239.4090806@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
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:06:08 -0000

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.  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
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg