Re: [IPFIX] IANA IPFIX registry

Paul Aitken <paitken@cisco.com> Thu, 07 October 2010 18:14 UTC

Return-Path: <paitken@cisco.com>
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B987E3A6F75 for <ipfix@core3.amsl.com>; Thu, 7 Oct 2010 11:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 vUD7rWwr8KgU for <ipfix@core3.amsl.com>; Thu, 7 Oct 2010 11:14:49 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 4F18F3A6EC6 for <ipfix@ietf.org>; Thu, 7 Oct 2010 11:14:49 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMeqrUxAZnwN/2dsb2JhbACiRXGvTpxehUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,298,1283731200"; d="scan'208";a="167952620"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 07 Oct 2010 18:15:51 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o97IFpfI001372; Thu, 7 Oct 2010 18:15:51 GMT
Received: from [10.55.94.52] (dhcp-10-55-94-52.cisco.com [10.55.94.52]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o97IFn806655; Thu, 7 Oct 2010 19:15:49 +0100 (BST)
Message-ID: <4CAE0E50.7050005@cisco.com>
Date: Thu, 07 Oct 2010 19:15:44 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Brian Trammell <brian@trammell.ch>
References: <AANLkTimaVEX=cNRQn0RB5_iJJJc0O30sw4ghrCSN2GzB@mail.gmail.com>
In-Reply-To: <AANLkTimaVEX=cNRQn0RB5_iJJJc0O30sw4ghrCSN2GzB@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ipfix@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [IPFIX] IANA IPFIX registry
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 07 Oct 2010 18:14:51 -0000

Brian,

There's currently no way to know what was added to the registry when,
which I think will be important in future for the reasons below.

So I'd like to see something added ASAP.

It could be as simple as recording the date and a list of fields added, 
modified or removed.

BTW, I do plan on reviewing the IE doctors draft.

P.


On 07/10/10 14:43, Brian Trammell wrote:
> Hi, Paul,
>
> Good idea. Have a look at the recently submitted
> draft-trammell-ipfix-ie-doctors; we don't currently specify
> versioning, but specifying (or, if we want to bring versioning online
> in less time than it takes to publish a draft, explaining and
> referencing) a policy for that would fit very nicely in a future
> version thereof...
>
> Cheers,
>
> Brian
>
> --- On Oct 7, 2010, at 3:36 PM, Paul Aitken wrote: ---
>
> Dear all,
>
> I've been requesting new IPFIX Information Elements from IANA. And I
> realised that there's a problem: there are no details of changes in
> the registry.
>
> So I think that the registry should include a version number and
> revision history that's updated with each new field.
>
> Then one can claim their implementation is compatible with v123, and
> quickly see what needs to be done to be compatible with v456.
>
> Or an exporter and a collector can quickly and easily be compared to
> ensure they support the same elements, or at least a common set of
> elements required for a particular application.
>
> P.
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix