Utilizing Pre-defined Templates with IPFIX
draft-aitken-ipfix-pre-defined-templates-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-09-02 (latest revision 2017-03-01) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| 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-pre-defined-templates-00.txt
https://www.ietf.org/archive/id/draft-aitken-ipfix-pre-defined-templates-00.txt
Abstract
This document specifies a way to pre-define well-known IPFIX Templates which can be pre-shared with Collectors, thus avoiding the need for Exporters to send those Templates to Collectors. This saves export bandwidth and reduces Collector complexity.
Authors
Paul Aitken (paitken@brocade.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)