Re: [sip-clf] Extend Charter to Include IPFIX streaming?

Benoit Claise <bclaise@cisco.com> Wed, 10 November 2010 00:03 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 22ED93A6A21 for <sip-clf@core3.amsl.com>; Tue, 9 Nov 2010 16:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level:
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 YxjE0-os1Osp for <sip-clf@core3.amsl.com>; Tue, 9 Nov 2010 16:03:08 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 094C23A69FB for <sip-clf@ietf.org>; Tue, 9 Nov 2010 16:03:07 -0800 (PST)
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 oA9NxlgX006735; Wed, 10 Nov 2010 00:59:48 +0100 (CET)
Received: from [10.68.20.224] (sin-vpn-client-20-224.cisco.com [10.68.20.224]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA9NxiIb010895; Wed, 10 Nov 2010 00:59:46 +0100 (CET)
Message-ID: <4CD9E06F.1020603@cisco.com>
Date: Wed, 10 Nov 2010 07:59:43 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Peter Musgrave <peter.musgrave@magorcorp.com>
References: <A9D693D6-3B7E-40D9-BC3F-BC0CED6A3C42@magorcorp.com>
In-Reply-To: <A9D693D6-3B7E-40D9-BC3F-BC0CED6A3C42@magorcorp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: List SIP-CLF Mailing <sip-clf@ietf.org>
Subject: Re: [sip-clf] Extend Charter to Include IPFIX streaming?
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: Wed, 10 Nov 2010 00:03:09 -0000

Hi Peter,

It seems like a good idea/compromise to me.

I remember Daryl's draft about performance metrics that went all over 
the place because every WG said: "not in my yard!"
He started in which date? Answered at 
http://tools.ietf.org/html/draft-malas-performance-metrics-00 to finally 
end up in PMOL, and it's just almost over.

It seems so easy for me to simply to update the SIPCLF charter, to add 
the item, to get it done with the same people/interest and at the same 
time as the ASCII file... and to move on.

Regards, Benoit.
> All,
>
> As discussed in the consensus call to choose ASCII thread, there was agreement that IPFIX was not motivated to log into files.
>
> Is there interest in this group extending it's charter to allow the IPFIX streaming work to be specified here?
>
> I wanted to get a sense for this before embarking on specific charter text changes.
>
> As I see it the IPFIX work is well known by this group and makes reference to the data model specified here.
>
> I would see two work items:
> - specification of and IANA registration for elements to be logged (all are in the current problem statement)
> - a doc which indicates how signalling flows can be linked with existing data flows already reported with IPFIX mechanisms (this might just be an addition to the existing doc)
>
> Speaking personally, I think it makes sense to continue the discussion with this group and avoid the admin overhead of creating another one via dispatch.
>
> We have a group of IPFIX contributors who have shown their continued willingness to do the work necessary to make this happen (and in fact the first work item has seen lots of work, and two implementations are known to exist).
>
> Opinions?
>
> Regards,
>
> Peter Musgrave
> (as co-chair)
>
>
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf