Re: [IPFIX] exporting ranges in IPFIX

Andrew Feren <andrewf@plixer.com> Tue, 05 June 2012 15:35 UTC

Return-Path: <andrewf@plixer.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 35DAF21F86A1 for <ipfix@ietfa.amsl.com>; Tue, 5 Jun 2012 08:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 KQzz4G5zlpe9 for <ipfix@ietfa.amsl.com>; Tue, 5 Jun 2012 08:35:27 -0700 (PDT)
Received: from smtp.plixer.com (smtp.plixer.com [66.186.184.193]) by ietfa.amsl.com (Postfix) with ESMTP id 48C6921F86B0 for <ipfix@ietf.org>; Tue, 5 Jun 2012 08:35:27 -0700 (PDT)
Received: from [10.100.1.132] ([66.186.184.193]) by smtp.plixer.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 5 Jun 2012 11:35:26 -0400
Message-ID: <4FCE273E.4040500@plixer.com>
Date: Tue, 05 Jun 2012 11:35:26 -0400
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/15.0 Thunderbird/15.0a1
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
References: <4FCE149B.8010802@cisco.com> <4FCE168A.6020603@cisco.com> <4FCE25CB.5020508@cisco.com>
In-Reply-To: <4FCE25CB.5020508@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jun 2012 15:35:26.0419 (UTC) FILETIME=[D4606230:01CD4330]
Cc: IETF IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [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:35:28 -0000

Hi Paul,

This seems useful, but out of curiousity, why "Number of ports in block" 
instead of "Port block end".

-Andrew

On 06/05/2012 11:29 AM, Paul Aitken wrote:
> 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.
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix