IPFIX Export per SCTP Stream
draft-claise-ipfix-export-per-sctp-stream-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Benoît Claise | ||
| Last updated | 2012-10-29 (Latest revision 2008-02-25) | ||
| Replaced by | draft-ietf-ipfix-export-per-sctp-stream | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ipfix-export-per-sctp-stream | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies an improvement to the use of SCTP as specified in the IPFIX specifications in order to be able to deduce the data record loss per template record in case of partially-reliable SCTP export. This specification offers several extra advantages: immediate export of the template withdrawal message, immediate reuse of template ID within a stream, and the collecting process's job is easier.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)