Rahman
Sent: Tuesday, March 19, 2024 12:46 PM
To: i...@ietf.org; opsawg@ietf.org; justin.iur...@uliege.be; Graf Thomas,
INI-NET-VNC-HCS
Subject: Re: [OPSAWG] draft-spiegel-ippm-ioam-rawexport
Be aware: This is an external email.
Hi Thomas,
By "IOAM dimension fields", are you referring
Hi all,
I also support these documents proposing to export metrics through IPFIX,
however not the way draft-spiegel-ippm-ioam-rawexport is implemented.
The advantage of IPFIX is aggregation directly at the node. The proposal in
draft-spiegel-ippm-ioam-rawexport is exporting directly the raw
Hi Thomas,
By "IOAM dimension fields", are you referring to fields such as ingress/egress
intf id etc in IOAM data? And you are requesting for these fields to be
included to facilitate aggregation by another entity (e.g the aggregating
mediator in RFC7015)? i.e you are not requesting for the
Dear Justin, Dear OPSAWG and IPPM working groups
Thanks a lot for the presentation at IPPM. I believe that this work needs
further refinement by defining also IPFIX entities for IOAM which allow a
decomposition of each IOAM dimension fields, thus enabling IPFIX Flow
Aggregation as described in
