grarpamp wrote:
Wouldn't it be better to support the obvious formal emergent standards
track protocol instead of the legacy informational one? Or to perform
both via sysctl or other arguments/defines, with the standard IPFIX
being the default mode? Have you reviewed the nProbe code for other
various ideas? Thanks for working on netflow :) And any form of v6
is good to have finally.
Thanks for pointing out those RFCs. We're still using v5 for accounting,
so my behavior was quite straightforward:
can v5 count ipv6 ? No, what's next netflow version can ? v9? Ok, let's
implement v9.
However, IPFIX seems to be very much like v9 at a first glance.
Moreover, ng_ksocket can handle udp/tcp/sctp exports.
=========================================================================
Network Working Group B. Claise, Ed.
Request for Comments: 5101 Cisco Systems, Inc.
Category: Standards Track January 2008
Specification of the IP Flow Information Export (IPFIX) Protocol
for the Exchange of IP Traffic Flow Information
This document specifies an Internet standards track protocol for the
Internet community
Network Working Group J. Quittek
Request for Comments: 5102 NEC
Category: Standards Track S. Bryant
B. Claise
P. Aitken
Cisco Systems, Inc.
J. Meyer
PayPal
January 2008
Information Model for IP Flow Information Export
This document specifies an Internet standards track protocol for the
Internet community
Network Working Group B. Trammell
Request for Comments: 5103 CERT/NetSA
Category: Standards Track E. Boschi
Hitachi Europe
January 2008
Bidirectional Flow Export Using IP Flow Information Export (IPFIX)
This document specifies an Internet standards track protocol for the
Internet community
Network Working Group E. Boschi
Request for Comments: 5153 Hitachi Europe
Category: Informational L. Mark
Fraunhofer FOKUS
J. Quittek
M. Stiemerling
NEC
P. Aitken
Cisco Systems, Inc.
April 2008
IP Flow Information Export (IPFIX) Implementation Guidelines
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind.
Network Working Group S. Leinen
Request for Comments: 3955 SWITCH
Category: Informational October 2004
Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX)
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind.
Network Working Group J. Quittek
Request for Comments: 3917 NEC Europe Ltd.
Category: Informational T. Zseby
Fraunhofer FOKUS
B. Claise
Cisco Systems
S. Zander
Swinburne University
October 2004
Requirements for IP Flow Information Export (IPFIX)
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind.
And others...
=========================================================================
Network Working Group B. Claise, Ed.
Request for Comments: 3954 Cisco Systems
Category: Informational October 2004
Cisco Systems NetFlow Services Export Version 9
This RFC documents the NetFlow services export protocol Version 9 as
it was when submitted to the IETF as a basis for further work in the
IPFIX WG.
This RFC itself is not a candidate for any level of Internet
Standard. The IETF disclaims any knowledge of the fitness of this
RFC for any purpose...
And others...
=========================================================================
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[email protected]"
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[email protected]"
