IP Flow Information Export (IPFIX) Per Stream Control Transmission Protocol (SCTP) Stream
RFC 6526
Document | Type | RFC - Proposed Standard (March 2012; No errata) | |
---|---|---|---|
Authors | BenoƮt Claise , Paul Aitken , Andrew Johnson , Gerhard Muenz | ||
Last updated | 2018-12-20 | ||
Replaces | draft-claise-ipfix-export-per-sctp-stream | ||
Stream | Internet Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6526 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Dan Romascanu | ||
IESG note | This document was already reviewed and approved by the IESG. The IETF Last Call is redone for Proposed Status following the DISCUSS by Alexey. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) B. Claise Request for Comments: 6526 P. Aitken Category: Standards Track A. Johnson ISSN: 2070-1721 Cisco Systems, Inc. G. Muenz TU Muenchen March 2012 IP Flow Information Export (IPFIX) Per Stream Control Transmission Protocol (SCTP) Stream Abstract 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. 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/rfc6526. Claise, et al. Standards Track [Page 1] RFC 6526 IPFIX Per SCTP Stream March 2012 Copyright Notice Copyright (c) 2012 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. Claise, et al. Standards Track [Page 2] RFC 6526 IPFIX Per SCTP Stream March 2012 Table of Contents 1. Introduction ....................................................3 1.1. Relationship with IPFIX and PSAMP ..........................4 1.2. Applicability ..............................................5 1.3. Limitations ................................................5 2. Terminology .....................................................6 2.1. Conventions Used in This Document ..........................6 2.2. IPFIX Documents Overview ...................................6 2.3. PSAMP Documents Overview ...................................7 3. IPFIX Protocol Specifications: Limitations and Improvements .....7 3.1. Data Record Loss Calculated Per Template ...................7 3.1.1. IPFIX Protocol Specifications: Limitation ...........7 3.1.2. IPFIX Export Per SCTP Stream: Advantage .............8 3.2. Immediate Template Withdrawal and Reuse ....................8 3.2.1. IPFIX Protocol Specifications: Limitation ...........8 3.2.2. IPFIX Export Per SCTP Stream: Advantages ............9 3.3. Requirement for Data Set Buffering .........................9 3.3.1. IPFIX Protocol Specifications: Limitation ...........9 3.3.2. IPFIX Export Per SCTP Stream: Advantages ...........10 4. Specifications .................................................10 4.1. New Information Element ...................................10 4.2. Template Management .......................................11 4.3. SCTP ......................................................12 4.4. Template Withdrawal Message ...............................13 4.5. The Collecting Process's Side .............................14 4.5.1. SCTP ...............................................14 4.5.2. Enabling the Per-SCTP-Stream Extension .............14 4.5.3. Disabling the Per-SCTP-Stream Extension ............15Show full document text