Biflow implementation support in IPFIX
draft-boschi-ipfix-biflow-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Elisa Boschi , Brian Trammell | ||
| Last updated | 2008-04-17 (Latest revision 2005-10-27) | ||
| Replaced by | draft-ietf-ipfix-biflow | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ipfix-biflow | |
| 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
This document describes how bidirectional flows (biflows) can be implemented in the IP Flow Information Export (IPFIX) protocol. We propose a variety of methods for biflow export, including an extension to the IPFIX Information Model that allows the specification of biflow semantics and a set of counters needed for biflow processing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)