Textual Representation of IPFIX Abstract Data Types
draft-ietf-ipfix-text-adt-04
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (ipfix WG)
|
|
Last updated |
|
2014-05-12
(latest revision 2014-04-16)
|
|
Replaces |
|
draft-trammell-ipfix-text-adt
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Juergen Quittek
|
|
Shepherd write-up |
|
Show
(last changed 2014-05-06)
|
IESG |
IESG state |
|
AD Evaluation
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
BenoƮt Claise
|
|
Send notices to |
|
ipfix-chairs@tools.ietf.org, draft-ietf-ipfix-text-adt@tools.ietf.org
|
IPFIX Working Group B. Trammell
Internet-Draft ETH Zurich
Intended status: Informational April 16, 2014
Expires: October 18, 2014
Textual Representation of IPFIX Abstract Data Types
draft-ietf-ipfix-text-adt-04.txt
Abstract
This document defines UTF-8 representations for IPFIX abstract data
types, to support interoperable usage of the IPFIX Information
Elements with protocols based on textual encodings.
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 October 18, 2014.
Copyright Notice
Copyright (c) 2014 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.
Trammell Expires October 18, 2014 [Page 1]
Internet-Draft IPFIX Text Types April 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Identifying Information Elements . . . . . . . . . . . . . . 3
4. Data Type Encodings . . . . . . . . . . . . . . . . . . . . . 3
4.1. octetArray . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. unsigned8, unsigned16, unsigned32, and unsigned64 . . . . 4
4.3. signed8, signed16, signed32, and signed64 . . . . . . . . 5
4.4. float32 and float64 . . . . . . . . . . . . . . . . . . . 6
4.5. boolean . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.6. macAddress . . . . . . . . . . . . . . . . . . . . . . . 7
4.7. string . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.8. dateTime* . . . . . . . . . . . . . . . . . . . . . . . . 7
4.9. ipv4Address . . . . . . . . . . . . . . . . . . . . . . . 8
4.10. ipv6Address . . . . . . . . . . . . . . . . . . . . . . . 8
4.11. basicList, subTemplateList, and subTemplateMultiList . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The IPFIX Information Model[RFC7012] provides a set of abstract data
types for the IANA IPFIX Information Element Registry [IANA-IPFIX],
which contains a rich set of Information Elements for description of
information about network entities and network traffic data, and
abstract data types for these Information Elements. The IPFIX
Protocol Specification [RFC7011], in turn, defines a big-endian
binary encoding for these abstract data types suitable for use with
the IPFIX Protocol.
However, present and future operations and management protocols and
applications may use textual encodings, and generic framing and
structure, as in JSON or XML. A definition of canonical textual
encodings for the IPFIX abstract data types would allow this set of
Information Elements to be used for such applications, and for these
applications to interoperate with IPFIX applications at the
Information Element definition level.
In most cases where a textual representation will be used, an
explicit tradeoff is made for human readability or manipulability
Trammell Expires October 18, 2014 [Page 2]
Show full document text