Telechat Review of draft-ietf-nvo3-geneve-oam-13
review-ietf-nvo3-geneve-oam-13-opsdir-telechat-li-2025-01-02-00

OPSDIR Review of draft-ietf-nvo3-geneve-oam-13

Reviewer: Tony Li
Status:

Disclaimer: I am NOT a fan of Geneve and I will not attempt to hide my
disaffection for the underlying technoloyg. That said, I will try to
review this document on its own merits.

Overall: Ready, with nits

I found the document to be clear, concise and informative. It
accomplishes its goals.

I found that the document left me wanting more: if there is a
connectivity problem within a VNI and a ping fails, then how do I
track down and isolate the fault? Ok, yes, this is beyond the scope of
the document, but it is somewhat cruel to leave the reader
hanging. Section 2.2 sets up two scenarios but then never resolves
them. Did Alfred Hitchcock contribute?

Details:

Section 2.1:

Requirement 5 is a bit unclear. What do you mean by 'express entropy'?
I think you mean something like: "There must be a way to encode entopy
information into the underlay forwarding scheme so that OAM packets
take the same dataflow paths as the transit traffic flows

Section 2.2.1:

Nit: s/) ,/),/