JK Lee

@rsivakolundu @mhira1 @mickeyspiegel We can merge this change first, create a v1.x cut, advance INT.mdk to version 2 and merge the two other changes. One thing we need to discuss...

@jafingerhut https://github.com/opennetworkinglab/onos/blob/master/pipelines/basic/src/main/resources/int.p4 This implementation in the ONF repo might be the closest. It implements INT v1.0 using p4_16. I think it works with the BMv2 target too. @JonghwanHyun is the...

@jafingerhut Thanks for the great summary. These all make sense. One question: does PSA define the unit of time (hence timestamp)? Exactly where the ingress/egress tstamps are taken in the...

I see. Some architecture may have a h/w logic to compensate the frequency difference btw the oscillator and the timestamp clock, some may not, hence the P4 level solution was...

@jafingerhut As we discussed, these queueing system intrinsic metadata available at egress would be great additions for telemetry and other use cases. - queue ID - queueing latency - enqueue-time...

That's right. The Apps WG started a YANG model for each vendor to be able to specify implementation-specific metadata semantics. https://github.com/p4lang/p4-applications/blob/master/telemetry/code/models/p4-dtel-metadata-semantics.yang The model may evolve to specify each field format,...