[IPFIX] Interpretation of sequence number handling

Rick Hofstede <r.j.hofstede@utwente.nl> Fri, 19 June 2015 08:37 UTC

Return-Path: <r.j.hofstede@utwente.nl>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3E191A874B for <ipfix@ietfa.amsl.com>; Fri, 19 Jun 2015 01:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id png7G9m0Jom9 for <ipfix@ietfa.amsl.com>; Fri, 19 Jun 2015 01:37:06 -0700 (PDT)
Received: from out27-ams.mf.surf.net (out27-ams.mf.surf.net [145.0.1.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61CA81A874A for <ipfix@ietf.org>; Fri, 19 Jun 2015 01:37:05 -0700 (PDT)
Received: from smtps.utwente.nl (smtp-o1.utsp.utwente.nl [130.89.2.9]) by outgoing1-ams.mf.surf.net (8.14.4/8.14.4/Debian-4) with ESMTP id t5J8b30A003856 for <ipfix@ietf.org>; Fri, 19 Jun 2015 10:37:03 +0200
Received: from rh-macmini.ewi.utwente.nl (rh-macmini.ewi.utwente.nl [130.89.13.224]) by smtps.utwente.nl (8.13.8) with ESMTP id t5J8b2Ei006798 for <ipfix@ietf.org>; Fri, 19 Jun 2015 10:37:03 +0200
From: Rick Hofstede <r.j.hofstede@utwente.nl>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CF17BE38-1230-4706-9194-A5834C8DD8DD"
Message-Id: <CDC9C068-4864-44F8-9EE5-326FA1658DF4@utwente.nl>
Date: Fri, 19 Jun 2015 10:37:02 +0200
To: ipfix@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Mailer: Apple Mail (2.2098)
X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN)
X-CanIt-Geo: ip=130.89.2.9; country=NL; region=Provincie Overijssel; city=Enschede; latitude=52.2183; longitude=6.8958; http://maps.google.com/maps?q=52.2183,6.8958&z=6
X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default)
X-Canit-Stats-ID: 0uOG8B39P - 4fceb5cedcd3 - 20150619 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipfix/AQKObQ2WA_zIXgRzdxRsDrIWjx0>
Subject: [IPFIX] Interpretation of sequence number handling
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2015 08:37:08 -0000

Dear list,

RFC 7011 defines the following regarding sequence numbers in Message headers (Section 3.1 — Message Header Format): Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process.

This can however be interpreted in two ways:

(1) Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process *up to* this Message.
(2) Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process *up to and including* this Message.

It seems that only Section 10.3.2 — Reliability explains which of the two interpretations is right: In the case of UDP, the IPFIX Sequence Number contains the total number of IPFIX Data Records sent for the Transport Session *prior* to the receipt of this IPFIX Message, modulo 2^32.

In my opinion, it would be good to clarify the use of sequence numbers in Message headers already in the definition of sequence numbers in RFC 7011, namely in Section 3.1.

Best regards,

—
Rick Hofstede