Utilizing Pre-defined Templates with IPFIX
draft-aitken-ipfix-pre-defined-templates-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) P. Aitken
Internet-Draft Brocade Communications Systems, Inc.
Intended status: Standards Track March 1, 2017
Expires: September 2, 2017
Utilizing Pre-defined Templates with IPFIX
draft-aitken-ipfix-pre-defined-templates-00
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 2, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Aitken Expires September 2, 2017 [Page 1]
Internet-Draft IPFIX pre-defined Templates March 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Set Header Format . . . . . . . . . . . . . . . . . . . . . . 3
5. Template Record Format . . . . . . . . . . . . . . . . . . . 5
6. Data Record Format . . . . . . . . . . . . . . . . . . . . . 6
7. Options Template Record Format . . . . . . . . . . . . . . . 7
8. Options Data Record Format . . . . . . . . . . . . . . . . . 9
9. The Exporter's Side . . . . . . . . . . . . . . . . . . . . . 10
10. The Collector's Side . . . . . . . . . . . . . . . . . . . . 10
11. Template Management . . . . . . . . . . . . . . . . . . . . . 11
11.1. Template Withdrawal . . . . . . . . . . . . . . . . . . 11
12. Security Considerations . . . . . . . . . . . . . . . . . . . 11
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
14.1. Normative References . . . . . . . . . . . . . . . . . . 11
14.2. Informative References . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
IPFIX Exporters send Templates containing an ordered sequence of
<type, length> pairs which specify the data to be communicated from
the IPFIX Exporter to an IPFIX Collector.
Templates are useful when the IPFIX Exporter is configurable in the
field, such that the data it will export cannot be known beforehand.
However, many devices are deployed with fixed configurations,
particularly IoT devices, sensors, and smart meters. Nevertheless,
the IPFIX Protocol [RFC7011] requires such devices to export a
Template defining the data to be Exported - which is wasteful since
the data format is fixed and well-known ahead of time, and each
device exports exactly the same data. Additional export bandwidth is
consumed by the Template export, and the IPFIX Collector will receive
the same Template from multiple devices.
The bandwidth overhead is particularly inefficient in the case of
short-lived export streams, where the Exporter creates a new export
session containing a Template and a few Data Records. In the worst
case, every Data Record is preceded by the corresponding Template.
This inefficiency can easily be avoided if the Template is well-known
before the device is even deployed in the field.
Show full document text