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

Brian Trammell <trammell@tik.ee.ethz.ch> Thu, 11 November 2010 00:29 UTC

Return-Path: <trammell@tik.ee.ethz.ch>
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 058703A686E for <sip-clf@core3.amsl.com>; Wed, 10 Nov 2010 16:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 3JfGwdS7k9he for <sip-clf@core3.amsl.com>; Wed, 10 Nov 2010 16:29:01 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by core3.amsl.com (Postfix) with ESMTP id 0A5863A67E1 for <sip-clf@ietf.org>; Wed, 10 Nov 2010 16:29:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 203D5D9373; Thu, 11 Nov 2010 01:29:28 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8VwS8xv3so8q; Thu, 11 Nov 2010 01:29:27 +0100 (MET)
Received: from [172.31.14.241] (unknown [211.154.201.18]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 253DAD936B; Thu, 11 Nov 2010 01:29:25 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <3FC0CEFC-3BAC-474A-98A1-CBE7729641E9@cisco.com>
Date: Thu, 11 Nov 2010 08:29:21 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <29BA7142-4A7D-45AF-9F7F-83F03BA5EFA2@tik.ee.ethz.ch>
References: <A9D693D6-3B7E-40D9-BC3F-BC0CED6A3C42@magorcorp.com> <3FC0CEFC-3BAC-474A-98A1-CBE7729641E9@cisco.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
X-Mailer: Apple Mail (2.1081)
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 00:29:02 -0000

I'll throw an unsurprising +1 in here.

Cheers,

Brian

On Nov 11, 2010, at 8:05 AM, Gonzalo Salgueiro wrote:

> 
> 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?
>> 
> 
> A simple recharter seems a much more reasonable and efficient approach to get this work done.
> 
> Regards,
> 
> Gonzalo
> 
> 
>> Regards, 
>> 
>> Peter Musgrave
>> (as co-chair)
>> 
>> 
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
> 
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf