Re: [IPFIX] Interpretation of sequence number handling

--===============7975255346748290419==
Content-Type: multipart/signed;
 boundary="Apple-Mail=_67F1D8AA-9A16-4DDE-82FA-D817F682E5DB";
 protocol="application/pgp-signature"; micalg=pgp-sha512


--Apple-Mail=_67F1D8AA-9A16-4DDE-82FA-D817F682E5DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Rick,

Yep, this is a good point. Could you file an editorial erratum?

Thanks, cheers,

Brian

> On 19 Jun 2015, at 10:37, Rick Hofstede <[email protected]> =
wrote:
>=20
> Dear list,
>=20
> 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.
>=20
> This can however be interpreted in two ways:
>=20
> (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.
>=20
> 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.
>=20
> 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.
>=20
> Best regards,
>=20
> =E2=80=94
> Rick Hofstede
> _______________________________________________
> IPFIX mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipfix


--Apple-Mail=_67F1D8AA-9A16-4DDE-82FA-D817F682E5DB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJVg9UuAAoJENt3nsOmbNJcOlAIALCfPiyxchLk44X90EmSN+64
srm7UwG8vFjldUlr/JmUzMMeiVjI0fapOsAdNUt2lAxmI7zb2GOx7JCorZpijjf+
GRYZEpS/dJuim3AEJ4IHvnnc6JkG3a7waK62IK/Ld+xhUXL/4Q1uCshUtkGnFQB0
lYqbb2jhRTJ5DlRl/5NUoJ5A9rfdIzELqGGPymn4zXolLAij2TPdMAnvHf515vkg
+D0zQNDJdS1W2lOf+V6p8gawLT9BG5A++zyWOuCw8TJMLMb5k4Tht5XEonrM3TZp
xCk22a/h5ug2onAFG4aCh5XdL7830XHGRLumBmtQln+TP1xC4O6OZZb9Qd/Pw5E=
=pjEk
-----END PGP SIGNATURE-----

--Apple-Mail=_67F1D8AA-9A16-4DDE-82FA-D817F682E5DB--


--===============7975255346748290419==
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

--===============7975255346748290419==--