Reliability Extension for IPFIX
draft-ietf-ipfix-reliability-template-ext-00
Document | Type |
Expired Internet-Draft
(ipfix WG)
Expired & archived
|
|
---|---|---|---|
Author | Sujay Gupta | ||
Last updated | 2009-12-04 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
IPFIX[RFC3917] mandates the IPFIX device should be reliable.To be reliable the individual components like the Metering process or the Exporting process should not fail to meter & export the flow information to the collector, else indicate its incapability explicitly. Currently, IPFIX transmits failure by sending count of packets,flows it failed to process along with the duration of the failure. This document outlines some of the limitations an IPFIX device may have and suggests solutions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)