Carmelo Cascone

We have methods to reset registers to 0 (at least for pipe 0). Should we use that to clean up filters after each test?

Any chance we can make ONOS remove extraneous groups?

Following the RFC means having the final IP TTL decremented by the number of hops inside the fabric (e.g, `ttl = ttl - 2` for packets going from one leaf...

Yes, it should be `-3`... I just realized that since we do penultimate hop popping (i.e., spine pops MPLS), without copying the TTL between MPLS and IP, we cannot prevent...

I agree that we don't have strong reasons to do this change. I just wanted to voice my concern. I will make the change to fix the TTL behavior such...

Or using parser value sets to match on IP dst and ingress port? Similarly to how we use the interface table for uplink traffic. If IP dst is the UPF...

We could avoid inserting/deleting the same entries over and over for the same test class. Today most test classes use the following pattern where we `@autocleanup` after each invocation of...

I'm still observing this issue on the staging pod, I have attached a PCAP with the UDP packets sent to the switch. [iperf-udp.pcap.zip](https://github.com/stratum/fabric-tna/files/6233341/iperf-udp.pcap.zip)

That long list of annotations is not very appealing. It looks like we are defining a meta-language, which can easily become unmanageable. How about we define a common structure for...

Confirming that this issue still exists. I observed it happening on staging when using `iperf3` in TCP mode with max bandwidth 10Mb/s. We should try to reproduce on FLiRT. Attached...