RFC 7373: Textual Representation of IP Flow Information Export (IPFIX) Abstract Data Types
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7373
- Published
- September 2014
- Authors
- B. Trammell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5472IP Flow Information Export (IPFIX) ApplicabilityCurrent
March 2009
- RFC 7613Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsObsoleted
August 2015
- RFC 8265Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsCurrent
October 2017
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 5892The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)Updated
August 2010
- RFC 5335Internationalized Email HeadersObsoleted
September 2008
- RFC 5137ASCII Escaping of Unicode CharactersCurrent
February 2008
- RFC 9839Unicode Character Repertoire SubsetsCurrent
August 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?