I reviewed draft-ietf-ippm-ioam-integrity-yang-06.
Overall, I think the document is ready with some nits. The model is straightforward: it augments the RFC 9617 IOAM YANG model with integrity-protected profiles and defines the companion IANA-maintained YANG module for integrity protection method identifiers.

I do not have any major technical concerns.

Nits

1: 
It would help readers if the document explicitly stated why there is no integrity-protected Direct Export profile. RFC 9617 covers five IOAM options, while this document models four integrity-protected profiles. The companion integrity specification makes DEX out of scope because DEX does not carry IOAM-Data-Fields. A short explanatory sentence in the Introduction or Section 3.1 would avoid confusion.

2: 
Section 6.1 and Appendix A still contain unresolved template placeholders which need to be completed with the actual registry name and the final IANA reference.