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

Dan Burnett <dburnett@voxeo.com> Thu, 11 November 2010 02:10 UTC

Return-Path: <dburnett@voxeo.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 926F63A6904 for <sip-clf@core3.amsl.com>; Wed, 10 Nov 2010 18:10:51 -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 qXo5qU7mWnvg for <sip-clf@core3.amsl.com>; Wed, 10 Nov 2010 18:10:48 -0800 (PST)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with ESMTP id 8B6563A68CF for <sip-clf@ietf.org>; Wed, 10 Nov 2010 18:10:48 -0800 (PST)
Received: from [209.237.233.21] (account dburnett@voxeo.com HELO vpn-cust-10-208-1-170.witopia.net) by voxeo.com (CommuniGate Pro SMTP 5.3.8) with ESMTPSA id 74927457; Thu, 11 Nov 2010 02:11:16 +0000
Message-Id: <2011B29E-F386-45F9-BF31-13AE07DC92A0@voxeo.com>
From: Dan Burnett <dburnett@voxeo.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <A9D693D6-3B7E-40D9-BC3F-BC0CED6A3C42@magorcorp.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 10 Nov 2010 21:11:10 -0500
References: <A9D693D6-3B7E-40D9-BC3F-BC0CED6A3C42@magorcorp.com>
X-Mailer: Apple Mail (2.936)
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: Thu, 11 Nov 2010 02:10:51 -0000

While a -1 would generate more interesting emails, I also have a +1 on  
this approach -- extending the charter makes more sense and may  
simplify keeping the two formats aligned.

-- dan

On Nov 9, 2010, at 4:43 PM, Peter Musgrave wrote:

> 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