Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 06 Sep 2009 18:25:23 -0700
From:      Julian Elischer <julian@elischer.org>
To:        grarpamp <grarpamp@gmail.com>
Cc:        freebsd-isp@freebsd.org, freebsd-net@freebsd.org
Subject:   Re: Call for testers: ng_netflow with v9 and IPv6 support
Message-ID:  <4AA46103.9000108@elischer.org>
In-Reply-To: <d2e731a10909061511q35447425s6cec18460fb48bd1@mail.gmail.com>
References:  <d2e731a10909061511q35447425s6cec18460fb48bd1@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

if you have time it sounds like you know enough about it to be 
useful.. get involved :-)


> 
> =========================================================================
> 
> 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...
> 
> =========================================================================
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AA46103.9000108>