Reporting Unobserved Fields in IPFIX
draft-aitken-ipfix-unobserved-fields-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Paul Aitken | ||
| Last updated | 2015-01-05 (Latest revision 2014-07-04) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-aitken-ipfix-unobserved-fields-03.txt
https://www.ietf.org/archive/id/draft-aitken-ipfix-unobserved-fields-03.txt
Abstract
The IPFIX protocol is designed to export information about observations, and lacks a method for reporting that observations are unavailable. This document discusses several methods for reporting when fields are unavailable, reviews the advantages and disadvantage of each, and recommends methods which should be used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)