Re: [IPFIX] exporting ranges in IPFIX

Paul Aitken <[email protected]>
Newsgroups gmane.ietf.ipfix
Message-ID <[email protected]>
Dear all,

I've had two feedbacks requesting a range start / range end mechanism. 
So I propose to request four fields:

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

These can be reported in whatever way best matches the implementation.

eg, { start, step, number }, { start, end, step }, { start, end, number }.

The default step size will be 1, so { start, end } indicates a 
contiguous range.

Finally, I've upped the step size from 8 bits to 16 bits to allow step 
sizes > 255.

Any further feedback?

Thanks,
P.


On 05/06/12 16:29, 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipfix

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.