[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
"nFlow is a new flow format characterized by the following properties:
1. superset of Cisco NetFlow v5 in order to ease the migration
Why isn't your work based on NetFlow v9, which is extensible? See the
latest PSAMP minutes:
"Also mutual re-use of technologies is possible. The IPFIX WG
has chosen NetFlow version 9 as starting point for protocol
development. NetFlow v9 is template-based."
A Sex, 2003-05-23 às 08:58, Luca Deri escreveu:
> Dear all,
> it's a while I follow the activities of this group. I have decided to
> define a new flow format named nFlow (see http://www.nflow.org/) that
> extends the NetFlow format adding new features such as:
> - support of both IPv4 and IPv6.
> - compressed (RFC 1950, 1952) flow format for reducing network traffic.
> - flow authentication, protection against forging, and non repudiation
> (RFC 1321).
> - flow payload information.
> - accurate ICMP access.
> - packet sampling for easing probe scalability.
> - performance (network and application) information.
> - MPLS and VLAN tag info.
> I have defined it mostly because NetFlow is not rich enough for ntop (a
> GPL passive network monitoring tool). Currently I have a GPL software
> Netflow+nFlow probe (http://www.ntop.org/nProbe.html) and a collector
> available. I plan to make ntop nFlow-aware in the near future.
> I would like to know (I have asked this Juergen a while ago but
> unfortunately I have not received a reply so far) whether:
> - we could work together so that IPFIX and nFlow could merge
> - I could show up at the next IETF meeting in Vienna and present nFlow
> Your feedback is appreciated.
> Regards, Luca
Gustavo João Alves Marques Carneiro
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.
- From: Luca Deri <email@example.com>