Cisco Systems NetFlow Services Export Version 9 Transport
draft-djernaes-netflow-9-transport-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Djernaes | ||
| Last updated | 2003-02-27 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
NetFlow Export Version 9 Export is defined in the internet draft draft-claise-netflow-9 [NFv9], which describes how to transport NetFlow over UDP [RFC768]. This document describes how NetFlow would use SCTP [RFC2960] as a transport protocol. Traditionally NetFlow was transmitted over UDP to a physically closely located collector. As the networks grow this is not necessarily the case any longer, so issues like congestion avoidance and reliability are becoming an increasing issue for applications using NetFlow. This document addresses these issues in a simple way using the SCTP protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)