Re: [IPFIX] IPFIX at IETF 89, London

Paul Aitken <paitken@cisco.com> Mon, 10 February 2014 22:49 UTC

Return-Path: <paitken@cisco.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF231A08A8 for <ipfix@ietfa.amsl.com>; Mon, 10 Feb 2014 14:49:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level:
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GMipP5Y96Wb for <ipfix@ietfa.amsl.com>; Mon, 10 Feb 2014 14:49:46 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 38B4F1A0488 for <ipfix@ietf.org>; Mon, 10 Feb 2014 14:49:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=800; q=dns/txt; s=iport; t=1392072586; x=1393282186; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=YWjvMlPHBly2phxDp/T/TNwbOnlddpbhyxM+jbGDU3M=; b=D3i1uCdwJu9YnTsR1x72joSRw09IN3I2JHTrg/+BJa7Utgdu/EOzY0ew bvrAPVwomTcabJ3h2xvzqjij9bsZ6TquzUWf5JTnqNinmOgpImVDAJ+BQ vfVZ68EI5fRlfCSmKywc5nHOwsttkT9IBAiNyd1hZ/tLm4b/TB1Fb2//D I=;
X-IronPort-AV: E=Sophos;i="4.95,820,1384300800"; d="scan'208";a="4859731"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 10 Feb 2014 22:49:45 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1AMniaU029320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Feb 2014 22:49:45 GMT
Received: from [10.61.101.158] (dhcp-10-61-101-158.cisco.com [10.61.101.158]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s1AMndIZ024967; Mon, 10 Feb 2014 22:49:39 GMT
Message-ID: <52F95765.50902@cisco.com>
Date: Mon, 10 Feb 2014 22:49:09 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, Andrew Feren <andrewf@plixer.com>, IPFIX Working Group <ipfix@ietf.org>
References: <52EF4E92.3040906@auckland.ac.nz> <52EF71FA.3090005@cisco.com> <52F80BCA.2030408@auckland.ac.nz> <52F8AAB5.5050604@cisco.com> <52F9430C.3040909@cisco.com>
In-Reply-To: <52F9430C.3040909@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "ipfix-ads@tools.ietf.org" <ipfix-ads@tools.ietf.org>, "ipfix-chairs@tools.ietf.org" <ipfix-chairs@tools.ietf.org>
Subject: Re: [IPFIX] IPFIX at IETF 89, London
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 22:49:52 -0000

Benoit,

>> I've presented these ideas in previous WG meetings, where the 
>> consensus was to wait for the next re-charter.
> Consensus, sure?

Yes: the work was interesting, but not relevant to the current charter. 
So, bring it up at the next recharter - which hasn't happened yet.


> I checked the meeting minutes and I don't see that.
> What I recall is that two different proposals were discussed 
> (draft-aitken-ipfix-equivalent-ies and draft-inacio-ipfix-penie-00), 
> with no clear winner.

Sure; each of these drafts has different merits. It would be up to the 
WG to decide on the best solution.

Look, here's a real problem in IPFIX which has resulted in not one but 
*two* different drafts trying to solve it in different ways. Do you 
propose to ignore it?

P.