RFC 6526: IP Flow Information Export (IPFIX) Per Stream Control Transmission Protocol (SCTP) Stream
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the specifications in RFC 5101, IP Flow Information Export (IPFIX), when using the Partial Reliability extension of SCTP (PR-SCTP, Partial Reliability Stream Control Transmission Protocol). When implemented at both the Exporting Process and Collecting Process, this method offers several advantages, such as the ability to calculate Data Record losses for PR-SCTP per Template, immediate export of Template Withdrawal Messages, immediate reuse of Template IDs within an SCTP stream, reduced likelihood of Data Record loss, and reduced demands on the Collecting Process. When implemented in only the Collecting Process or Exporting Process, then normal IPFIX behavior will be seen without all of the additional benefits. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6526
- Published
- March 2012
- Authors
- B. Claise; P. Aitken; A. Johnson; G. Muenz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6534Loss Episode Metrics for IP Performance Metrics (IPPM)Current
May 2012
- RFC 6536Network Configuration Protocol (NETCONF) Access Control ModelObsoleted
March 2012
- RFC 6555Happy Eyeballs: Success with Dual-Stack HostsObsoleted
April 2012
- RFC 6576IP Performance Metrics (IPPM) Standard Advancement TestingCurrent
March 2012
- RFC 6470Network Configuration Protocol (NETCONF) Base NotificationsCurrent
February 2012
- RFC 6583Operational Neighbor Discovery ProblemsCurrent
March 2012
- RFC 6589Considerations for Transitioning Content to IPv6Current
April 2012
- RFC 6459IPv6 in 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS)Current
January 2012
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?