Reviewer: Linda Dunbar Review result: Has Nits I have reviewed this document as part of the Ops area directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Ops area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This document specifies an IOAM encoding (Direct Export Option) to trigger IOAM data to be directly exported or locally aggregated without being pushed into in-flight data packets. I think the document is READY with some nits: >From the operation point of view, can the "entity" that the IOAM is directed by DEX Option send an explicit request to all the nodes for the IOAM to be exported to them? instead of asking the DEX encapsulating node to encode the DEX in some data packet? If not, why? If yes, can you add a comparison of those two approaches? Thank you very much Linda Dunbar -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
