[IPFIX] exporting ranges in IPFIX

Paul Aitken <paitken@cisco.com> Tue, 05 June 2012 15:29 UTC

Return-Path: <paitken@cisco.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C866521F8656 for <ipfix@ietfa.amsl.com>; Tue, 5 Jun 2012 08:29:11 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLSyz+ntbYf0 for <ipfix@ietfa.amsl.com>; Tue, 5 Jun 2012 08:29:11 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id C37F621F8682 for <ipfix@ietf.org>; Tue, 5 Jun 2012 08:29:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=paitken@cisco.com; l=877; q=dns/txt; s=iport; t=1338910150; x=1340119750; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=kTqv8UM/LmnePZNJhE3d3NmE8wYSSBWuCkrYTCG2kuA=; b=Cc55CQmwRJjSceEq0HGRolYnRs2EbTTZun5OTc+98C7hYg92QKa5FJlv pne+vtzuqRTFQn0N8zk/IFc8MIXLXww7MjQiDb1zxX4i8bMDYB5WShevQ uaeGWlzTBZPp+vtOXk67G1RKctcSbsyEhDPbdbZ72EPFSbn2m7iOTJvDI o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGYlzk+Q/khM/2dsb2JhbABFtDmBB4IZAQEEEgElMw0RLBYPCQMCAQIBRQYNCAEBHodpC5ctoAqRIwOVG4EPhEGIQIFmgmE
X-IronPort-AV: E=Sophos;i="4.75,718,1330905600"; d="scan'208";a="5401987"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 05 Jun 2012 15:29:09 +0000
Received: from [10.61.102.112] (dhcp-10-61-102-112.cisco.com [10.61.102.112]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q55FT9j9010441 for <ipfix@ietf.org>; Tue, 5 Jun 2012 15:29:09 GMT
Message-ID: <4FCE25CB.5020508@cisco.com>
Date: Tue, 05 Jun 2012 16:29:15 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF IPFIX Working Group <ipfix@ietf.org>
References: <4FCE149B.8010802@cisco.com> <4FCE168A.6020603@cisco.com>
In-Reply-To: <4FCE168A.6020603@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [IPFIX] exporting ranges in IPFIX
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Jun 2012 15:29:11 -0000

Dear IPFIX experts,

As far as I know, IPFIX doesn't have a generic mechanism for reporting 
ranges.

I'm looking for a way to report bulk port allocation per section 5 of 
http://tools.ietf.org/html/draft-ietf-behave-lsn-requirements-05.

This method would be useful for reporting port ranges in 
draft-tsou-behave-natx4-log-reduction-02 and draft-bajko-pripaddrassign-04.

So I propose to request three new IPFIX Information Elements:

    Port block start:           16 bits
    Port block step size         8 bits
    Number of ports in block    16 bits


However, there could be better ways to export a "range" which don't 
require three new IEs each time. Do you forsee a need for a such a 
mechanism?

Shall I proceed with my request to IANA? If so, should I write a short 
ID explaining how the three IEs should be used together?

Thanks,
P.