[IPFIX] Interpretation of sequence number handling
Rick Hofstede <[email protected]> Fri, 19 Jun 2015 10:37:02 +0200
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <[email protected]> |
--===============2213610212896200556== Content-Type: multipart/alternative; boundary="Apple-Mail=_CF17BE38-1230-4706-9194-A5834C8DD8DD" --Apple-Mail=_CF17BE38-1230-4706-9194-A5834C8DD8DD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Dear list, RFC 7011 defines the following regarding sequence numbers in Message = headers (Section 3.1 =E2=80=94 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 =E2=80=94 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, =E2=80=94 Rick Hofstede= --Apple-Mail=_CF17BE38-1230-4706-9194-A5834C8DD8DD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">Dear list,<div class=3D""><br class=3D""></div><div = class=3D"">RFC 7011 defines the following regarding sequence numbers in = Message headers (Section 3.1 =E2=80=94 Message Header Format): <i = class=3D"">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.</i></div><div class=3D""><br = class=3D""></div><div class=3D"">This can however be interpreted in two = ways:</div><div class=3D""><br class=3D""></div><div class=3D"">(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.</div><div class=3D"">(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.</div><div = class=3D""><br class=3D""></div><div class=3D"">It seems that only = Section 10.3.2 =E2=80=94 Reliability explains which of the two = interpretations is right: <i class=3D"">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.</i></div><div class=3D""><br class=3D""></div><div = class=3D"">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.</div><div = class=3D""><br class=3D""></div><div class=3D"">Best regards,</div><div = class=3D""><br class=3D""></div><div class=3D"">=E2=80=94</div><div = class=3D"">Rick Hofstede</div></body></html>= --Apple-Mail=_CF17BE38-1230-4706-9194-A5834C8DD8DD-- --===============2213610212896200556== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipfix --===============2213610212896200556==--