Browse Prior Art Database

Textual Representation of IP Flow Information Export (IPFIX) Abstract Data Types (RFC7373)

IP.com Disclosure Number: IPCOM000239012D
Original Publication Date: 2014-Sep-01
Included in the Prior Art Database: 2014-Oct-01
Document File: 28 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Trammell: AUTHOR

Abstract

data type or Information Element. Values that are out of range are interpreted as clipped to the implicit range for the Information Element as defined by the abstract data type or to the explicit range of the Information Element if defined. Minimum and maximum values for abstract data types are shown in Table 1 below.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                       B. Trammell Request for Comments: 7373                                    ETH Zurich Category: Standards Track                                 September 2014 ISSN: 2070-1721

       Textual Representation of IP Flow Information Export (IPFIX)                           Abstract Data Types

Abstract

   This document defines UTF-8 representations for IP Flow Information    Export (IPFIX) abstract data types (ADTs) to support interoperable    usage of the IPFIX Information Elements with protocols based on    textual encodings.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7373.

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                     Standards Track                    [Page 1]
 RFC 7373                    IPFIX Text Types              September 2014

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3

   3.  Identifying Information Elements  . . . . . . . . . . . . . .   3

   4.  Data Type Encodings . . . . . . . . . . . . . . . . . . . . .   3

     4.1.  octetArray  . . . . . . . . . . . . . . . . . . . . . . .   4

     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 . . . . . . . . . . . . . . . . . . . . . . ....