Re: [IPFIX] IPFIX at IETF 89, London

Andrew Feren <andrewf@plixer.com> Tue, 11 February 2014 21:44 UTC

Return-Path: <andrewf@plixer.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 C91171A0776 for <ipfix@ietfa.amsl.com>; Tue, 11 Feb 2014 13:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level:
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RP_MATCHES_RCVD=-0.548] 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 50PAdVTZLgfh for <ipfix@ietfa.amsl.com>; Tue, 11 Feb 2014 13:43:59 -0800 (PST)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id 84E951A0771 for <ipfix@ietf.org>; Tue, 11 Feb 2014 13:43:59 -0800 (PST)
Received: from PLXRDC01.plxr.local ([::1]) by PLXRDC01.plxr.local ([::1]) with mapi id 14.03.0158.001; Tue, 11 Feb 2014 16:43:58 -0500
From: Andrew Feren <andrewf@plixer.com>
To: Benoit Claise <bclaise@cisco.com>, Paul Aitken <paitken@cisco.com>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, IPFIX Working Group <ipfix@ietf.org>
Thread-Topic: [IPFIX] IPFIX at IETF 89, London
Thread-Index: AQHPILc0AfhsOV5eaE+OBCYr2tRDipqjqu8AgApAxACAAL1ygIAAtZoAgAAYQoCAACHdgIAA93xg
Date: Tue, 11 Feb 2014 21:43:57 +0000
Message-ID: <8E7542283B89BB4DB672EB49CEE5AAB7054010B8@PLXRDC01.plxr.local>
References: <52EF4E92.3040906@auckland.ac.nz> <52EF71FA.3090005@cisco.com> <52F80BCA.2030408@auckland.ac.nz> <52F8AAB5.5050604@cisco.com> <52F9430C.3040909@cisco.com> <52F95765.50902@cisco.com>, <52F973CD.80607@cisco.com>
In-Reply-To: <52F973CD.80607@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [24.91.78.244]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 11 Feb 2014 21:44:03 -0000

Hi Benoit,

I think both topics are interesting, but if I had to pick one to put some work into it would be the unobserved fields draft.  There is a need to communicate this information (or lack of information ;-).  I am already starting to see exports where different vendors are choosing different ad hoc methods to communicate N/A for the same IEs.

As for draft-aitken-ipfix-equivalent-ies and draft-inacio-ipfix-penie, I'm mostly interested in anything that encourages exporters to "publish" info about the IEs they export.  Given the lack of uptake for 5610 I'm not optimistic that an alternate/updated version of 5610 will get any more traction.  Most of the time I'd be happy to get a text file with 7013 style Information Element Specifiers.

Just my 2 cents,
-Andrew
________________________________________
From: Benoit Claise [bclaise@cisco.com]
Sent: Monday, February 10, 2014 7:50 PM
To: Paul Aitken; Nevil Brownlee; Andrew Feren; IPFIX Working Group
Cc: ipfix-ads@tools.ietf.org; ipfix-chairs@tools.ietf.org
Subject: Re: [IPFIX] IPFIX at IETF 89, London

Paul,

At this point, I will be listening to the chairs to see  ...
     if this is really "interesting",
     if there is enough support from the IPFIX community,
     if there is enough discussion on it,
     and if this work could be done in the decent time.

(*) I guess that I'm so much involved in IPFIX that I have strong
opinions about your drafts. That's the price you pay for an AD who knows
IPFIX by heart.

Regards, Benoit
> 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.
> .
>