RFC 5103: Bidirectional Flow Export Using IP Flow Information Export (IPFIX)
In plain English — editorial summary, not part of the RFC
This document describes an efficient method for exporting bidirectional flow (Biflow) information using the IP Flow Information Export (IPFIX) protocol, representing each Biflow using a single Flow Record. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5103
- Published
- January 2008
- Authors
- B. Trammell; E. Boschi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9487Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)Current
November 2023
- RFC 5102Information Model for IP Flow Information ExportObsoleted
January 2008
- RFC 5101Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow InformationObsoleted
January 2008
- RFC 5098Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)Updated
February 2008
- RFC 5110Overview of the Internet Multicast Routing ArchitectureCurrent
January 2008
- RFC 5132IP Multicast MIBCurrent
December 2007
- RFC 5136Defining Network CapacityCurrent
February 2008
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
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?