From owner-freebsd-isp@FreeBSD.ORG Sun Sep 6 22:31:53 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 453DF106566B; Sun, 6 Sep 2009 22:31:53 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id 9F5718FC08; Sun, 6 Sep 2009 22:31:52 +0000 (UTC) Received: by ewy4 with SMTP id 4so433236ewy.36 for ; Sun, 06 Sep 2009 15:31:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=sutaW3IPsfV3eys2+pVWlFqLpUnQfD8zn1Z8gPCXNog=; b=BtjNLnwqoBYhHiB4hkvApoioAS8G7+ZHzdM68wveZp5mx/ik876C9yy+8XSAh0OwPk 0ilg4Rklc9DI2SssxT7F7jQtIDuWshoFtjuf7yEY1dFlHIAvBt2fx3hVJhK3tHuh7Kro Nnmk8CtLz54+OAUogncF4EPcogbRd+9s1sK9A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=r5fKkDA/0on5BmEp88YiMvwY/+/m13sQ5QbHBCCpttZ/xrh+hqRRxeICl6ZWYvJWvs +1tWiF9ZjhpM+LxGb0i4u80Xv/CZhd4BXhuVI8CGrHL22LhFqebzaZmIZiJZOjeJfNvI vqZ82zTwAIUhMz/1QZog0Wj4XtcRK6RLS/QRA= MIME-Version: 1.0 Received: by 10.211.154.17 with SMTP id g17mr864569ebo.32.1252275070144; Sun, 06 Sep 2009 15:11:10 -0700 (PDT) Date: Sun, 6 Sep 2009 18:11:10 -0400 Message-ID: From: grarpamp To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-isp@freebsd.org Subject: Call for testers: ng_netflow with v9 and IPv6 support X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2009 22:31:53 -0000 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. ========================================================================= 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... =========================================================================