Dear All,
I support the adoption of this draft.
I have a few very minor comments below.
Best,
Jean
Section 1, paragraph 4:
OLD
"Since these IPFIX IEs are performance metrics [RFC8911], they must be
registered as registered performance metrics [RFC8911] in the "IANA ..."
NEW
"Since these IPFIX IEs are performance metrics [RFC8911], they must be
registered in the "IANA ..."
Section 3.4.2
OLD
"For each <statistic>, Singleton one of the following [..] applies "
NEW
"For each <statistic> Singleton, one of the following [..] applies "
Section 3.4.2.3. (Max)
I would add the scope of n from RFC6049 after the formula
"where all packets n = 1 through N have finite singleton delays."
Section 6.2.X
"OctedDelta" is not defined, do you mean deltaCounter as in
https://www.rfc-editor.org/rfc/rfc7012#section-3.2.3
Section 7.2
Computing the average from PathDelaySumDeltaMicroseconds seems unecessary as
PathDelayMeanDeltaMicroseconds already exports it. Maybe state that the
advantage of pushing that computation to the collector is to avoid doing too
much computation in the router?
From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Tianran Zhou
Sent: Thursday 22 December 2022 02:26
To: opsawg@ietf.org
Cc: draft-tgraf-opsawg-ipfix-on-path-teleme...@ietf.org
Subject: [OPSAWG] WG Adoption Call for
draft-tgraf-opsawg-ipfix-on-path-telemetry-01
Hi WG,
This mail starts a WG Adoption Call for
draft-tgraf-opsawg-ipfix-on-path-telemetry-01.
https://datatracker.ietf.org/doc/draft-tgraf-opsawg-ipfix-on-path-telemetry/
Please reply your supports or objections.
We would really appreciate your comments.
Since there are holidays, this call will last for 3 weeks, and end on Thursday,
Jan 12, 2023.
Cheers,
Tianran (as co-chairs)
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
