[OPSAWG]Fw: New Version Notification for draft-claise-opsawg-ipfix-ordered-ie-01.txt

["Aitken, Paul" <[e-mail]>]

IPFIX and OPS,

We have updated this draft with the feedback from Joe Clarke and Timmy Schueller.

Please review and provide your feedback to the OPSAWG mailing list.

Thanks,
Paul and Benoit

________________________________
From: [e-mail] <[e-mail]>
Sent: Monday, July 06, 2026 21:10
To: Benoit Claise <[e-mail]>; Holger Keller <[e-mail]>; Aitken, Paul <[e-mail]>; Yao Liu <[e-mail]>
Subject: New Version Notification for draft-claise-opsawg-ipfix-ordered-ie-01.txt

A new version of Internet-Draft draft-claise-opsawg-ipfix-ordered-ie-01.txt
has been successfully submitted by Paul Aitken and posted to the
IETF repository.

Name:     draft-claise-opsawg-ipfix-ordered-ie
Revision: 01
Title:    Ordered Information Element Export in IP Flow Information Export (IPFIX)
Date:     2026-07-06
Group:    Individual Submission
Pages:    38
URL:      https://www.ietf.org/archive/id/draft-claise-opsawg-ipfix-ordered-ie-01.txt<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-claise-opsawg-ipfix-ordered-ie-01.txt__;!!OSsGDw!Mo4WOCMG7WVqUj__OJw4fRzXPCbGjUYbR_IKoMKH0B_1HVgj6ntmnXOCxe5_IT_1oUvfQ2PIvO6lFK0cx5sQYEk$>
Status:   https://datatracker.ietf.org/doc/draft-claise-opsawg-ipfix-ordered-ie<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-claise-opsawg-ipfix-ordered-ie/__;!!OSsGDw!Mo4WOCMG7WVqUj__OJw4fRzXPCbGjUYbR_IKoMKH0B_1HVgj6ntmnXOCxe5_IT_1oUvfQ2PIvO6lFK0ck7wSoT8$>
HTML:     https://www.ietf.org/archive/id/draft-claise-opsawg-ipfix-ordered-ie-01.html<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-claise-opsawg-ipfix-ordered-ie-01.html__;!!OSsGDw!Mo4WOCMG7WVqUj__OJw4fRzXPCbGjUYbR_IKoMKH0B_1HVgj6ntmnXOCxe5_IT_1oUvfQ2PIvO6lFK0c-Aw161o$>
HTMLized: https://datatracker.ietf.org/doc/html/draft-claise-opsawg-ipfix-ordered-ie<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-claise-opsawg-ipfix-ordered-ie__;!!OSsGDw!Mo4WOCMG7WVqUj__OJw4fRzXPCbGjUYbR_IKoMKH0B_1HVgj6ntmnXOCxe5_IT_1oUvfQ2PIvO6lFK0cjHwOMkU$>
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-claise-opsawg-ipfix-ordered-ie-01<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-claise-opsawg-ipfix-ordered-ie-01__;!!OSsGDw!Mo4WOCMG7WVqUj__OJw4fRzXPCbGjUYbR_IKoMKH0B_1HVgj6ntmnXOCxe5_IT_1oUvfQ2PIvO6lFK0cvWyaljY$>

Abstract:

   The IP Flow Information Export (IPFIX) protocol allows the same
   Information Element to appear multiple times in a Template Record.
   RFC 7011 states that multiple occurrences of the same Information
   Element SHOULD follow the logical order of their treatments by the
   Metering Process; however, no protocol mechanism exists for the
   Exporting Process to explicitly signal to the Collecting Process that
   this ordering is guaranteed.  Without such a guarantee, the
   Collecting Process cannot safely interpret repeated Information
   Elements as ordered observations.  This document describes the
   problem, presents use cases, analyzes candidate solutions, and
   specifies a mechanism -- a new Ordered Set type -- that establishes
   an end-to-end ordering guarantee: the Metering Process records
   repeated Information Element values in the order the corresponding
   observations are made, the Exporting Process preserves and signals
   this guarantee, and the Collecting Process interprets the n-th
   occurrence of an Information Element as corresponding to the n-th
   observation by the Metering Process at the Observation Point.  This
   document updates RFC 7011, RFC 5476, and RFC 6183.



The IETF Secretariat