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

Peter Musgrave <peter.musgrave@magorcorp.com> Tue, 09 November 2010 21:42 UTC

Return-Path: <peter.musgrave@magorcorp.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 B805D3A686D for <sip-clf@core3.amsl.com>; Tue, 9 Nov 2010 13:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level:
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 M2Alti3XCb2s for <sip-clf@core3.amsl.com>; Tue, 9 Nov 2010 13:42:44 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 79A823A6835 for <sip-clf@ietf.org>; Tue, 9 Nov 2010 13:42:44 -0800 (PST)
Received: by yxk8 with SMTP id 8so75199yxk.31 for <sip-clf@ietf.org>; Tue, 09 Nov 2010 13:43:09 -0800 (PST)
Received: by 10.150.50.4 with SMTP id x4mr11496781ybx.90.1289338989378; Tue, 09 Nov 2010 13:43:09 -0800 (PST)
Received: from dhcp-408b.meeting.ietf.org (dhcp-408b.meeting.ietf.org [130.129.64.139]) by mx.google.com with ESMTPS id h68sm1266033yha.15.2010.11.09.13.43.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Nov 2010 13:43:08 -0800 (PST)
From: Peter Musgrave <peter.musgrave@magorcorp.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Nov 2010 05:43:03 +0800
Message-Id: <A9D693D6-3B7E-40D9-BC3F-BC0CED6A3C42@magorcorp.com>
To: List SIP-CLF Mailing <sip-clf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [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: Tue, 09 Nov 2010 21:42:45 -0000

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)