Cisco Systems NetFlow Services Export Version 9
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: RFC Editor <firstname.lastname@example.org> Cc: The IESG <email@example.com>, <firstname.lastname@example.org>, email@example.com Subject: Re: Informational RFC to be: draft-claise-netflow-9-09.txt The IESG has no problem with the publication of 'Cisco Systems NetFlow Services Export Version 9' <draft-claise-netflow-9-09.txt> as an Informational RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8869&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Bert Wijnen. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-claise-netflow-9-09.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary Describes Netflow Version 9 and served also as input for the IPFIX protocol evaluations effort. Working Group Summary This is an individual submission via RFC-Editor. It is intended to document the Netflow Version that was submitted to IPFIX WG for evaluation. At the same time it serves as a public documentation for NetFlow version 9. The IPFIX WG has evaluated this document and has no issue with publication as an informational RFC. Protocol Quality The document is an individual submision via RFC-Editor. Bert Wijnen has assured that: - it is not an end-run around IPFIX WG - IPFIX WG is OK with publication - it does not conflict with other IETF work RFC-Editor note Pls insert this IESG note on the front page: This RFC documents the Netflow protocol 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 in particular notes that it has not had complete IETF review for such things as security, congestion control or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. The IETF is working on a standardized protocol in the IPFIX (IP Flow Information eXport) Working Group.