IETF Logo Mail Archive

Re: [IPFIX] Winding down the ipfix working group.

Benoit Claise <bclaise@cisco.com> Wed, 17 December 2014 09:06 UTC

Return-Path: <bclaise@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 178C41A1BDC for <ipfix@ietfa.amsl.com>; Wed, 17 Dec 2014 01:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 gD1rAI7Mzga1 for <ipfix@ietfa.amsl.com>; Wed, 17 Dec 2014 01:06:41 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5CE11A2119 for <ipfix@ietf.org>; Wed, 17 Dec 2014 01:06:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12719; q=dns/txt; s=iport; t=1418807201; x=1420016801; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=a40AhfUMNVdczhMmHnAOu3NaD1kXWQksjTbVHtSe/HA=; b=VZZCzVX2j+ZvZDvQ5+tK+p7Gk5IAXPFh5qz33/LS98m2AKwSc6+wGEtu LT119p6hLBYR5+oq+ZJ+KqY2/E0MA7wzmxuPsx8sQp8F304drk+GxZCrk qlEU/rtyXl0T7H2Yyfg/NvJ/3jtoegUOjLRYynVzQDnW0aZ9M9Lc6WDsz M=;
X-IronPort-AV: E=Sophos;i="5.07,592,1413244800"; d="scan'208,217";a="277397530"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 17 Dec 2014 09:06:36 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sBH96aSo026054; Wed, 17 Dec 2014 09:06:36 GMT
Message-ID: <5491479B.6060305@cisco.com>
Date: Wed, 17 Dec 2014 10:06:35 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: stbryant@cisco.com, Andrew Feren <andrewf@plixer.com>
References: <5435D840.1090108@bogus.com> <5487A31D.5040304@bogus.com> <548B4AA0.4000905@bogus.com> <9904FB1B0159DA42B0B887B7FA8119CA5C92F0DE@AZ-FFEXMB04.global.avaya.com>, <548ECA8F.7030209@cisco.com> <08A9E6AF-F505-4D5D-AC9C-E35D2AF8E08D@plixer.com> <548ED9CF.8070309@cisco.com>
In-Reply-To: <548ED9CF.8070309@cisco.com>
Content-Type: multipart/alternative; boundary="------------030900060207000201000209"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/GQg2tqrL5wqWaW762onOTmsgamQ
Cc: joel jaeggli <joelja@bogus.com>, IPFIX Working Group <ipfix@ietf.org>, "ipfix-chairs@tools.ietf.org" <ipfix-chairs@tools.ietf.org>
Subject: Re: [IPFIX] Winding down the ipfix working group.
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: Wed, 17 Dec 2014 09:06:44 -0000

On 15/12/2014 13:53, Stewart Bryant wrote:
> On 15/12/2014 11:57, Andrew Feren wrote:
>> Are you talking about adding IEs or something more?
>>
>> If more than just new IEs can you give an example?  I've used IPFIX 
>> for transport of more than just network management information. I'm 
>> curious what is missing for your use cases.
>>
>
> Well a bit off the cuff, but how about pre-registered templates rather 
> than refreshed templates so that IOT devices don't need to use energy 
> or bandwidth to transmit them?
So going back to NetFlow v5? :-)
As you know, we had to move away from v5 to v9 to solve a real problem.

Regards, Benoit

> Are there any additional protocol considerations associated with 
> privacy, authentication and resilience when IPFIX is used over the 
> wide area? For example authenticated data merging?
>
> - Stewart
>
>
>> -Andrew
>>
>> On Dec 15, 2014, at 6:47 AM, Stewart Bryant <stbryant@cisco.com 
>> <mailto:stbryant@cisco.com>> wrote:
>>
>>> As many of you know I have concerns about closing IPFIX.
>>>
>>> Whilst IPFIX may have completed sufficient of its work in support
>>> of network management, the protocol has much to offer in terms
>>> of use as a mass data collection protocol particularly in the IOT space.
>>> I thus have some reservations about terminating the work as
>>> opposed to moving it to another area.
>>>
>>> - Stewart
>>>
>>>>> -----Original Message-----
>>>>> From: IPFIX [mailto:ipfix-bounces@ietf.org] On Behalf Of joel jaeggli
>>>>> Sent: Friday, December 12, 2014 10:06 PM
>>>>> To: IPFIX Working Group
>>>>> Cc: ipfix-chairs@tools.ietf.org <mailto:ipfix-chairs@tools.ietf.org>
>>>>> Subject: [IPFIX] Winding down the ipfix working group.
>>>>>
>>>>>
>>>>> Greetings,
>>>>>
>>>>> The chairs and my co-AD and I have decided it's time to window 
>>>>> down the
>>>>> ipfix working group. Our major milestones are completed and we 
>>>>> should be
>>>>> pleased with the results.
>>>>>
>>>>> We have one remaining active document
>>>>>
>>>>> draft-ietf-ipfix-mib-variable-export
>>>>>
>>>>> which I will be happy to AD sponsor. Barring significant commentary to
>>>>> contrary I will close the working-group on friday december 19th 
>>>>> and we will
>>>>> retain the mailing list for some time after that.
>>>>>
>>>>> Thanks and congratulations.
>>>>> Joel
>>>
>>> _______________________________________________
>>> IPFIX mailing list
>>> IPFIX@ietf.org <mailto:IPFIX@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/ipfix
>
>
> -- 
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix

v2.23.0 | Report a Bug | By Email